directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <>
Subject Re: Configuration objectclass
Date Tue, 23 May 2006 17:04:22 GMT

Again I'm going to ask you to start sharing some of what you're doing 
with the rest of the dev list.  Simply having an esoteric conversation 
between you and John is not enough to shed light on what is actually 
about to happen.

You need to bring the rest of us to this OSGi party if you're going to 
avoid -1 votes.  I already posted an email without getting a response to 
this dev list asking you to elaborate.  I have sent several private 
reminders to you to start sharing "your" OSGi aims with others.   I even 
called you on the phone.  If this conduct does not change, a veto is the 
least of your worries.  You're on the PMC, you should know how to engage 
this community properly.

Start explaining to the rest of us what is going on so a surprise is not 
sprung in the last minute.   Is this so hard?  It takes a few words to 
give all a heads up.  I hope you are not thinking you can just jam in 
the recent work on OSGi.  You're doing some good work but you're not 
acting in accordance with what a community member much less a PMC member 
should be doing. 

Expose the work being done so others can have a chance to participate.


Enrique Rodriguez wrote:
> John E. Conlon wrote:
>> Experimenting with the OSGi Configuration Admin implementation in
>> Enirique's sandbox/configuration.  Was able to upgrade it to use the
>> felix service binder and interact with the latest SNAPSHOT apacheds/mina
>> modules that I OSGi bundlized last week.  (Note: I haven't migrated to
>> the bundles Enrique committed in the trunks/apacheds/osgi yet.)
>> Nevertheless the cm bundle appears to be up, listening to the DIT for
>> events, and offering it's Service for client bundle configuration.
>> Next step is to add a configuration objectclass entry to the DIT so I
>> can actually store configurations. Is there a configuration schema
>> and/or a for doing this?
> Damn, I had a huge reply explaining this last night and Thunderbird 
> flashed-out - it's never done that before.  Here it is again.
> *** Keep in mind we agreed here, some time ago, to update these 
> services to OSGi R4 and to move them to Felix, so the SVN location 
> will change.
> The short answer is that the attributesType's and objectClass's you 
> are looking for are in the apache.schema.  We've typically put entries 
> in the apache.schema until such time as there are enough of them to 
> either warrant their own schema file or they justify their own OID range.
> The standard location for configuration in the DIT is under 
> ou=configuration,ou=system.  There should be this ou already, by default.
> The apacheServiceConfiguration and the apacheFactoryConfiguration 
> correspond to ManagedService's and ManageServiceFactory's, 
> respectively.  You use these in conjunction with ExtensibleObject 
> objectClass's to provide custom attributes.
> Looking this over now, I would change apacheServiceConfiguration and 
> apacheFactoryConfiguration from STRUCTURAL objectClass's to AUXILIARY 
> objectClass's.  Then you could use them as "marker" objectClass's and 
> add them to any DIT entry you so choose.  CM is going to return a set 
> of attributes, so the objectClass doesn't matter and I think this 
> would work and be more flexible.  I would still start searches below 
> ou=configuration,ou=system.  WDYT?
> I've included an example LDIF, below, of using this with the DNS 
> service.  Using a ManagedServiceFactory is the natural way to handle 
> multi-homed configurations, where you want to serve 1..n DIT locations 
> to a specific NIC.  A DNS spec uses the term "catalog":
> From RFC 1035:
> "... The catalog structure can be an almost static structure that
>      need change only when the system administrator changes the
>      zones supported by the server. ..."
> Example showing use with a DNS Server Factory:
> dn: cn=org.apache.dns.1,cn=dns,ou=services,ou=configuration,ou=system
> objectClass: apacheServiceConfiguration
> objectClass: extensibleObject
> cn: org.apache.dns.1
> ipAddress:
> ipPort: 53
> baseDn: dc=example,dc=com
> apacheServicePid: org.apache.dns.1
> apacheServiceFactoryPid: org.apache.dns.factory
> Relevant entries in the apache.schema:
> attributetype (
>     NAME 'apacheServicePid'
>     DESC 'A string up to 256 characters in length'
>     EQUALITY caseIgnoreIA5Match
> attributetype (
>     NAME 'apacheServiceFactoryPid'
>     DESC 'A string up to 256 characters in length'
>     EQUALITY caseIgnoreIA5Match
> objectclass (
>     NAME 'apacheServiceConfiguration'
>     SUP top
>     MUST ( cn $ apacheServicePid )
>     MAY ( apacheServiceFactoryPid ) )
> objectclass (
>     NAME 'apacheFactoryConfiguration'
>     SUP top
>     MUST ( cn $ apacheServicePid ) )
> Enrique

View raw message