[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
replicated cn=config
- To: openldap-devel@OpenLDAP.org
- Subject: replicated cn=config
- From: Howard Chu <hyc@symas.com>
- Date: Fri, 29 Apr 2005 13:31:30 -0700
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050419
Quanah posed this question about how to set up a bunch of replica
servers that all use configurations replicated from the master as well.
It wasn't perfectly obvious at first, so I'm posting this note to
suggest an approach and get some reactions. I haven't tested this yet.
First of all, you cannot just replicate cn=config straight from a master
to a slave server, because the slave will wind up with an identical copy
of the master's configuration (and will then cease to be a slave). This
means you must use some alternate tree, and map it into the slave's
cn=config.
So here's a possible approach - on the master
database ldif
directory /some/path
suffix cn=replica-config
On each slave
database relay
suffix cn=replica-config
relay cn=config massage
Then either slurpd or syncrepl can be used to keep the slaves'
configurations up to date.
--
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
http://www.symas.com http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support