[Date Prev][Date Next]
Re: Fwd: Re: Obtain Schema files from a software client
Mike Jackson wrote:
Howard Chu (firstname.lastname@example.org) wrote:
This function exists in OpenLDAP 2.3. You can perform all of the server
administration and configuration via LDAP; you can add any definitions
via LDAP without requiring a server restart. In particular, for schema,
you can collect related schema together into a single LDAP entry and
propagate/replicate it to any other server; there is no need to dump it
all into a catch-all file.
Nice. And how does this support version control of schema? Say, for instance,
I want to upgrade my self-written "foo123" schema from version 1.98 to version
1.99, how do I do it? Do I need to put X-ORIGIN stamps on every attribute
and objectclass, and do a deletes/modifies, or what? Obviously, I would prefer
that the server would poll a filesystem directory, parse the new/updated file,
and either atomically load or reject it, then replicate it to all servers where
there are existing replication agreements in force.
The typical case is that a new schema version will bring some new attributes
and objectclasses, but not remove backward compatibility...
Version control is up to you.
At present (2.3.3beta), deletes are not supported for schema elements.
We have a plan to support fine-grain schema editing down the road. For
now all you can do is Add new definitions - adding new attributes and
objectclasses is fine, modifying the definitions of existing elements is
For example, I can create a schema set in a file "test.ldif" :
olcAttributeTypes: ( 22.214.171.124.4.1.4203.666.1.37 NAME 'testTime' EQUALITY gen
eralizedTimeMatch ORDERING generalizedTimeOrderingMatch SYNTAX
126.96.36.199.24 SINGLE-VALUE )
olcObjectClasses: ( 188.8.131.52.4.1.4203.666.1.38 NAME 'testPerson' SUP OpenLDA
Pperson STRUCTURAL MAY testTime )
and ldapadd it into a running slapd.
Later I could add new definitions to this entry with ldapmodify:
olcAttributeTypes: ( 184.108.40.206.4.1.4203.666.1.34 NAME 'x509CertificateIssuer'
DESC 'Aliasing attribute: Issuer, use' EQUALITY distinguishedNameMatch
X 220.127.116.11.4.1.1418.104.22.168.12 )
olcAttributeTypes: ( 22.214.171.124.4.1.4203.666.1.35 NAME 'x509CertificateSerial'
DESC 'Aliasing attribute: Serial, use' EQUALITY integerMatch SYNTAX
Automatically replicating the change to other servers is feasible, but
you have to go thru a bit of indirection to do it. The steps are still
being discussed on the -devel list.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support