> :-) > >> OK, then I will stop working on a libconf >> > (http://qa.mandrakesoft.com/twiki/bin/view/Main/LibconfProject) >> backend for OpenLDAP > > > What you are working on, is it a way of storing the > configuration in LDAP instead of PERL? If that is the > case it is a very cool concept. >
No ... but I do want to see more configuration stored (possibly) in LDAP. For example, if you had an entry for all your Mandrake boxes in LDAP, and urpmi looked in LDAP for urpmi source configuration, you could upgrade a box from 9.1 to 9.2 by changing it membership (ie put it in cn=Mandrake9.2,ou=Hosts,dc=mylan,dc=net) of an LDAP entity/OU. The next run of a cron-scheduled (ie /etc/cron.daily) 'urpmi --auto-select' would upgrade it for you ... If you had specific groups of machines (ie office, cad, fem etc), then you could also specify what packages *must* be installed on each machine, so if you get a new fem preprocessor, you can just make a package in an internal urpmi medium, and add it to the list of packages that must be installed on the fem machines, and go home (and have it installed by cron overnight). > Or maybe I am totally confused. :-( > No, the libconf backend for LDAP I am working on now is just support for slapd.conf config file for libconf, so that we can start a UI for configuring LDAP (ie simple GUI to choose suffix, add LDAP slave, set basic ACLs, import user accounts etc). Regards, Buchan
