In my opinion the most important, hard to attack, and even harder (impossible?) to disprove argument is: Transparency!
Call it strange, useless, insane, fine or whatever, but my customers (also anybody who's interested in using a distinct service) should be able to get a chance for a detailed view into the running configuration of each service - before and while using it. slapd's cn=config supports this, not perfectly but better than any other service I'm aware of. For further details see our paper from LDAPcon2011.
I don't understand the yearly, redundant, and just time consuming discussions regaring slapd.conf vs. cn=config.
cn=config represents, as Quanah said: "forward thinking". +1
So, please think about it.
On 15.09.2017 09:09, Michael Ströder wrote:
Quanah Gibson-Mount wrote:
I think it's a strong plus to be able to reconfigure a standalone server into an MMR cluster with zero downtime,
I don't buy this argument. If you're really eager reaching high availability you have to implement a decent load-balancer and test correct fail-over anyway. And then your MMR cluster will have zero down-time (seen from the LDAP clients) during re-configuration even when restarting the replicas one after another.
Ciao, Michael.