[Date Prev][Date Next]
Re: cn=config: sharing, conditionals
----- "Quanah Gibson-Mount" <firstname.lastname@example.org> wrote:
> --On Tuesday, May 26, 2009 8:35 PM -0700 Howard Chu <email@example.com>
> > For example, we may have a cluster of servers in MMR with a pool of
> > 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,
> > the chain overlay active on all of the slaves. Setting
> olcServerMatch on
> > the syncprov and chain overlays would allow things to behave as
> > without needing to create a parallel config tree just for the
> > Comments?
> 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
> mode). This would allow that. I would note it may be common (I
> do so) to run the syncprov overlay on the replica as well, at least in
> glue'd environment.
> It sounds like it gracefully solves the ability of keeping both master
> replica configurations around for the most part. What still remains
> is ACLs. There are plenty of valid reasons for the master to have
> different ACLs than the replicas do.
I agree with Quanah too. Would these be a 2.5 features?
OpenLDAP Engineering Team.
Community developed LDAP software.