[GitHub] [directory-server] ben-manes commented on issue #13: WIP Attempt to move from ehcache to JCache+Caffeine
ben-manes commented on issue #13: WIP Attempt to move from ehcache to JCache+Caffeine URL: https://github.com/apache/directory-server/pull/13#issuecomment-478307418 Unless you intend to plug in alternative JCache providers, I'd recommend using the Caffeine APIs directly. I think they are more pleasant to work with and, personally, I find JCache frustrating. I chatted with @elecharny about this once for Mavibot, who was pretty positive but I don't think he got past a prototype. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: Existing ApacheDS containers?
> > > > There are many other images named "apacheds" [3] from other users, some > provide the source Dockerfile. > > As a general rule I avoid images from sources I don't trust so I thought I'd ask here first. > I think it would be nice to provide an offical Docker image, maybe with > the next release? > > I can't imagine the dockerfile its self to be that hard. We already have the infrastructure in place to scan containers against the CVE databases and trigger updates (as opposed to waiting for a new repo to be available). I'd be happy to let apacheds use that too with an "official" image. > > > https://github.com/apache/directory-fortress-core/blob/master/src/docker/apacheds-for-apache-fortress-tests/Dockerfile > [3] https://hub.docker.com/search?q=apacheds=image Thanks, this looks like a great start. I need some custom schema too (I need to be able to impersonate an Active Directory LDAPS interface from a schema standpoint).
Re: [directory-server] 01/02: Bumped up ehcache version to 3.6.1
On 30/03/2019 09:38, Stefan Seelmann wrote: On 1/21/19 5:04 AM, Emmanuel Lécharny wrote: On 21/01/2019 03:16, Richard Sand wrote: HI guys - I cloned master to start swapping the ehcahe3 to caffeine. But because caffeine is actually a bit more similar to ehcache2, I’m thinking of going back to AM25 and starting from there. What do you think? Sure ! There are not that many changes in trunk, merging your changes should be quite easy. I started an inital attempt, using JCache API and Caffeine, but with this combination I still have failing OSGi tests. I'll do another attempt to only use Caffeine without JCache. I think Caffeine only is good enough.
Re: Release train, soon...
On 3/30/19 9:34 AM, Emmanuel Lécharny wrote: > Hi all ! > > releases of the LDAP API and ApacheDS are slowly getting ready. We have > had to deal with various challenges ! > > - First, the LDAP API has been heavily refactored, for better > performance. The API itself will not change, this is the internal that > are changing. > > - We have had to wait for a MINA 2.1 release, which took quite some > time, and I'd like to go with a MINA 2.1.1 that is going to be released > somewhere next week: it simplifies greatly the way we deal with sent > messages, and we also have some SSL improvements in this coming reelease. > > - Once the LDAP API is released, we can move with a ApacheDS realase. > This time, it will contain some changes in the way we handle keystores, > support for transactions, and many other smaller improvements. One blocking issue is ehcache 3 which is not working with OSGi and Java 11. I started to check if replacement with Caffeine would work. > - In the same spirit, Fortress will benefit from the LDAP API and > ApacheDS release. It's a bit of work (not too much), but that would lead > to faster tests: the idea is to use transactions to improve the initial > data injections, which is quite costly. > > - Then will come Studio. I think Stefan has worked on migrating it to > the latest Eclipse version, which is becoming quite challenging, due to > the newest release strategy (a new version every 3 months). We also have > some fixes in the UI (connection testing, for instance) > > > That is going to be a pretty intense spring ! > > > More to come soon. >
Re: [directory-server] 01/02: Bumped up ehcache version to 3.6.1
On 1/21/19 5:04 AM, Emmanuel Lécharny wrote: > > On 21/01/2019 03:16, Richard Sand wrote: >> HI guys - >> >> I cloned master to start swapping the ehcahe3 to caffeine. But because >> caffeine is actually a bit more similar to ehcache2, I’m thinking of >> going back to AM25 and starting from there. What do you think? > > > Sure ! There are not that many changes in trunk, merging your changes > should be quite easy. I started an inital attempt, using JCache API and Caffeine, but with this combination I still have failing OSGi tests. I'll do another attempt to only use Caffeine without JCache. Kind Regards, Stefan [1] https://github.com/apache/directory-server/pull/13
Release train, soon...
Hi all ! releases of the LDAP API and ApacheDS are slowly getting ready. We have had to deal with various challenges ! - First, the LDAP API has been heavily refactored, for better performance. The API itself will not change, this is the internal that are changing. - We have had to wait for a MINA 2.1 release, which took quite some time, and I'd like to go with a MINA 2.1.1 that is going to be released somewhere next week: it simplifies greatly the way we deal with sent messages, and we also have some SSL improvements in this coming reelease. - Once the LDAP API is released, we can move with a ApacheDS realase. This time, it will contain some changes in the way we handle keystores, support for transactions, and many other smaller improvements. - In the same spirit, Fortress will benefit from the LDAP API and ApacheDS release. It's a bit of work (not too much), but that would lead to faster tests: the idea is to use transactions to improve the initial data injections, which is quite costly. - Then will come Studio. I think Stefan has worked on migrating it to the latest Eclipse version, which is becoming quite challenging, due to the newest release strategy (a new version every 3 months). We also have some fixes in the UI (connection testing, for instance) That is going to be a pretty intense spring ! More to come soon.
[GitHub] [directory-server] seelmann opened a new pull request #13: WIP Attempt to move from ehcache to JCache+Caffeine
seelmann opened a new pull request #13: WIP Attempt to move from ehcache to JCache+Caffeine URL: https://github.com/apache/directory-server/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: Existing ApacheDS containers?
On 30/03/2019 08:59, Stefan Seelmann wrote: On 3/29/19 9:21 PM, Marc Boorshtein wrote: All, I need a container that I can spin up quickly that i can just feed an LDIF file and be listening on 10636. Has anyone containerized apacheds? Can't imagine its hard but I thought I'd see if anyone else tried it already. There is no official one Docker image yet. In our DockerHub org [1] only images used for building and integration testing are available. One of them contains an ApacheDS, Dockerfile can be found at [2]. There are many other images named "apacheds" [3] from other users, some provide the source Dockerfile. I think it would be nice to provide an offical Docker image, maybe with the next release? Absolutely ! Regarding the release, I'll post another mail Emmanuel
Re: Existing ApacheDS containers?
On 3/29/19 9:21 PM, Marc Boorshtein wrote: > All, > > I need a container that I can spin up quickly that i can just feed an LDIF > file and be listening on 10636. Has anyone containerized apacheds? Can't > imagine its hard but I thought I'd see if anyone else tried it already. There is no official one Docker image yet. In our DockerHub org [1] only images used for building and integration testing are available. One of them contains an ApacheDS, Dockerfile can be found at [2]. There are many other images named "apacheds" [3] from other users, some provide the source Dockerfile. I think it would be nice to provide an offical Docker image, maybe with the next release? Kind Regards, Stefan [1] https://hub.docker.com/u/apachedirectory [2] https://github.com/apache/directory-fortress-core/blob/master/src/docker/apacheds-for-apache-fortress-tests/Dockerfile [3] https://hub.docker.com/search?q=apacheds=image
Re: Existing ApacheDS containers?
On 30/03/2019 00:24, Marc Boorshtein wrote: It generates a native binary and (according to doc) takes less time to start. But more than that we don't need to install JRE inside the container. Those are all at the moment appear to be good things, but haven't tested these in a container yet. Benefits are clear for a serverless app, not sure if thats going to be true for something like apacheds. I'd be very interested to see if there are any performance or size improvements. One aspect that may be problematic is that, AFAIU, reflection is not allowed in Quarkus. ApacheDS Configuration loading uses reflection, same thing for part of the schema...
