On Mittwoch, 16. Januar 2008, Michael Ströder wrote: > Ralf Haferkamp wrote: > >> For 1. I usually ask my customers how they are going to implement > >> the change management. After some discussion we usually end up > >> with text-based config managed with version control. Something > >> simple and handy. :-) > > > > Yes, I guess that this works pretty well when you deploy OpenLDAP > > (or basically any other software) at a single customer. It gets > > harder when you ship OpenLDAP as a part of a product, > > I already imagined what your aim is. ;-) Of course my aim is somewhat focused on what I am getting paid for, whose isn't? :) But additionally to that I was trying to find out if there is a general interest among the OpenLDAP Developers to have some kind of management tools/api. If there were, we could have started something that would serve both interests. I am trying to avoid a solution just specific to our products.
> > that is also used by people > > that are not too familiar with OpenLDAP. Ok, one might argue now, > > that people not really familiar with OpenLDAP should not use it, > > but I tend to disagree a bit here ;). > > It's always difficult to draw the line. At least the approach with > back-config makes it easier for a tool like yast to stay away from > configuration changes made by a sophisticated admin compared to > parsing full text files. -- Ralf
