[Date Prev][Date Next]
Best Practices for configuration management with cn=config?
- To: firstname.lastname@example.org
- Subject: Best Practices for configuration management with cn=config?
- From: Jeff B <email@example.com>
- Date: Fri, 3 Feb 2012 12:57:29 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=TKDdgA1r5/ZF/9trRU1cYWITgnMZvBevYMThcLImD4M=; b=rQWuAYkvmn+grblU7pcT/y9K9kWapgF1b7WGzorXiZCiT8hZ/WTWItxdf9pyNfBLk2 VvrYYbjqzCmPPKeB7bt3sih7fFyMkmV2lFRNm2LajMxGUDcgHPxl6MrDq/QZoRSwyLkZ ccSFLvNLq+DoGjNZWw5vxcfSmBfE18aKcaFa8=
I'm using puppet for configuration management and with the slapd.conf
it was dumb simple to push configs to the master and the slave servers
and have the server reload when the config was updated.
However I'm running an overlay that pukes with a slapd.conf and had to
convert over to cn=config. Now I'm not sure how I want to manage
this. Can I safely modify the files while slapd is running? I
wouldn't expect it to pick up the config changes without a reload, but
if I want puppet to push configs and reload will this be a valid
Or do I need to do something with an LDIF of the config and have some
kind of ldapadd/ldapmodify mojo?
Are there any puppet modules for cn=config that I missed when I looked?