[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: cn=config: sharing, conditionals

--On Tuesday, May 26, 2009 8:35 PM -0700 Howard Chu <hyc@symas.com> wrote:

For example, we may have a cluster of servers in MMR with a pool of other
servers operating as slaves. We'd want the syncprov overlay active on all
of the masters, the syncrepl consumer active on all of the servers, and
the chain overlay active on all of the slaves. Setting olcServerMatch on
the syncprov and chain overlays would allow things to behave as desired,
without needing to create a parallel config tree just for the slaves.


I like it. One thing we've needed to do in the past is drop the replication configuration portions of a master (taking it to single-server mode). This would allow that. I would note it may be common (I certainly do so) to run the syncprov overlay on the replica as well, at least in a glue'd environment.

It sounds like it gracefully solves the ability of keeping both master and replica configurations around for the most part. What still remains sticky is ACLs. There are plenty of valid reasons for the master to have very different ACLs than the replicas do.



Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
Zimbra ::  the leader in open source messaging and collaboration