You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Giampaolo Tomassoni <g....@libero.it> on 2005/09/12 17:34:21 UTC
ACIs update
Dears,
sorry for bothering you. I just registered to this mailing list and I'm approaching directory.apache.org because of some limits I'm facing with openldap.
Your code seems to overcame many of these limits (mostly regarding a dynamically-built tree based on content of other trees) while it seem to me not already mature for a production environment and borrowing some other limits.
The biggest limit (with respect to my purposes) I can actually see is the lack of ACIs implementation. Browsing this list it seems you are actually working on it. Am I right? Is there any non-stable release with ACI support?
Also, the available documentation seems to me scarce and obsolete: to start the server, in example, it suggests to specify a properties file and supplies an example. It seems to me, instead, that now the server needs an xml file to start, whose content is mostly undocumented (I did finally manage to start it with a couple of test tree, anyway).
Is there a site documenting this project a bit better?
Also, am I right in believing this project is aimed to produce a general-purpose (LDAP) directory server? Or are its purposes anything else (like being a piece of a bigger product)?
Thanks for your help,
-----------------------------------
Giampaolo Tomassoni - IT Consultant
Piazza VIII Aprile 1948, 4
I-53044 Chiusi (SI) - Italy
Ph: +39-0578-21100
R: ACIs update
Posted by Giampaolo Tomassoni <g....@libero.it>.
> -----Messaggio originale-----
> Da: Enrique Rodriguez [mailto:enriquer9@gmail.com]
>
> ...omissis...
>
> Regarding footprint size:
>
> The protocol providers are designed as "plugins" that sit between MINA's
> ServiceRegisty (networking front-end) and JNDI's InitialContextFactory
> (apacheds core). Other than the inclusion of schema specific to the
> protocols (krb5kdc.schema, apachedns.schema, and dhcp.schema), there is
> no other increase in footprint size to the core.
>
> Alex mentioned the protocols can be turned off if they are not needed.
> As plugins, they can be totally removed.
Well, I was talking about the whole system footprint: I bet there is also the need for a java runtime in order to run apacheDS. May I say that the ready-to-run apacheds footprint is around 25 MB? It is close to ten times the needs of openldap...
Also, memory consumption is probably greater in apacheds. My idle apacheds without Mitosis seems to sink about 20 MB of ram and Java servers are memory-hungry when serving requests. Openldap with syncrepl is around 16 MB and keeps this size more or less for its whole execution.
> Enrique
Thanks for replying,
Giampaolo
Re: ACIs update
Posted by Enrique Rodriguez <en...@gmail.com>.
Giampaolo Tomassoni wrote:
>>Da: Alex Karasulu [mailto:aok123@bellsouth.net]
>>Well Mitosis is a completed product and the ACI functionality will be
>>available with 0.9.3 in a week or two. That good?
>
>
> That's really good: this adds multi-master capabilities to the apacheDS, which is something missing by the openldap server.
>
> The two products (apacheDS and openldap) have probably different design targes (flexibility the first, performance and small footprint the latter) but for the 1-2 kEntries of my requirements, both performance and footprint size aren't going to be an issue.
Regarding footprint size:
The protocol providers are designed as "plugins" that sit between MINA's
ServiceRegisty (networking front-end) and JNDI's InitialContextFactory
(apacheds core). Other than the inclusion of schema specific to the
protocols (krb5kdc.schema, apachedns.schema, and dhcp.schema), there is
no other increase in footprint size to the core.
Alex mentioned the protocols can be turned off if they are not needed.
As plugins, they can be totally removed.
Enrique
R: R: ACIs update
Posted by Giampaolo Tomassoni <g....@libero.it>.
> Da: Alex Karasulu [mailto:aok123@bellsouth.net]
> Well Mitosis is a completed product and the ACI functionality will be
> available with 0.9.3 in a week or two. That good?
That's really good: this adds multi-master capabilities to the apacheDS, which is something missing by the openldap server.
The two products (apacheDS and openldap) have probably different design targes (flexibility the first, performance and small footprint the latter) but for the 1-2 kEntries of my requirements, both performance and footprint size aren't going to be an issue.
Let me have a try of mitosis...
> Alex
Thank you again,
Giampaolo
PS: It looks like you don't have time for documenting mitosis as well...
No surprise: have a look to my site http://www.tomassoni.biz :)
Re: R: ACIs update
Posted by Alex Karasulu <ao...@bellsouth.net>.
Giampaolo Tomassoni wrote:
>Thank you very much for kindly replying to my message.
>
>
>
np
...
>>Long story short ... ApacheDS will provide services similar to a Windows
>>Server except it is intended for any platform. This is for
>>facilitating a netork information system in a single server process
>>without having all the moving parts. Windows calls this the Domain
>>Controller. We, thanks to Enrique Rodriguez who coined the term, call
>>it the Realm Controller.
>>
>>
>
>Ok, that's really interesting. Of course it is due to the Realm Controller target, but also because this mean you will have to implement database replication, right?
>
>
We already implemented a replication module for ApacheDS here:
http://mitosis.safehaus.org
>Do you have any timeline for a more-fledged product (which means to me: LDAP with ACI and replication)?
>
>
Well Mitosis is a completed product and the ACI functionality will be
available with 0.9.3 in a week or two. That good?
Alex
R: ACIs update
Posted by Giampaolo Tomassoni <g....@libero.it>.
Thank you very much for kindly replying to my message.
> Da: Alex Karasulu [mailto:aok123@bellsouth.net]
>
> ...
>
> >Also, am I right in believing this project is aimed to produce a
> general-purpose (LDAP) directory server? Or are its purposes
> anything else (like being a piece of a bigger product)?
> >
> >
> Yes and yes to both questions. ApacheDS can server as a simple general
> purpose LDAP servber but it is much more than that. It is also a
> Kerberos server as well. Soon users will have the ability to toggle
> other services on as they need them like DNS, DHCP, Change password
> etc. If users need just a directory they can only turn on the LDAP
> service and other parts can be turned off.
That seems interesting to me: I would see a couple of usefull application for DNS-LDAP integration.
> Long story short ... ApacheDS will provide services similar to a Windows
> Server except it is intended for any platform. This is for
> facilitating a netork information system in a single server process
> without having all the moving parts. Windows calls this the Domain
> Controller. We, thanks to Enrique Rodriguez who coined the term, call
> it the Realm Controller.
Ok, that's really interesting. Of course it is due to the Realm Controller target, but also because this mean you will have to implement database replication, right?
I'm asking this because it is one importan feature with respect to my needs (a small ISP which would like to sell coordinated mail services) which seems to me actually not even touched in this mailing list.
Do you have any timeline for a more-fledged product (which means to me: LDAP with ACI and replication)?
>
> Alex
Thank you,
Giampaolo
Re: ACIs update
Posted by Alex Karasulu <ao...@bellsouth.net>.
Giampaolo Tomassoni wrote:
...
>The biggest limit (with respect to my purposes) I can actually see is the lack of ACIs implementation. Browsing this list it seems you are actually working on it.
>
Yes we are working on it.
>Am I right? Is there any non-stable release with ACI support?
>
>
>
Not yet we're still in the process of adding ACIs.
>Also, the available documentation seems to me scarce and obsolete: to start the server, in example, it suggests to specify a properties file and supplies an example. It seems to me, instead, that now the server needs an xml file to start, whose content is mostly undocumented (I did finally manage to start it with a couple of test tree, anyway).
>
>Is there a site documenting this project a bit better?
>
>
Unfortunately no it's not documented yet. We do not have time to
document with all the new features we're trying to add like ACI. Soon I
think we need to stop and seriously update the doco.
>Also, am I right in believing this project is aimed to produce a general-purpose (LDAP) directory server? Or are its purposes anything else (like being a piece of a bigger product)?
>
>
Yes and yes to both questions. ApacheDS can server as a simple general
purpose LDAP servber but it is much more than that. It is also a
Kerberos server as well. Soon users will have the ability to toggle
other services on as they need them like DNS, DHCP, Change password
etc. If users need just a directory they can only turn on the LDAP
service and other parts can be turned off.
Long story short ... ApacheDS will provide services similar to a Windows
Server except it is intended for any platform. This is for
facilitating a netork information system in a single server process
without having all the moving parts. Windows calls this the Domain
Controller. We, thanks to Enrique Rodriguez who coined the term, call
it the Realm Controller.
Alex