On 23/08/13 12:51 PM, Martin Langhoff wrote: > On Fri, Aug 23, 2013 at 12:03 PM, Paul Archer <geek65...@gmail.com > <mailto:geek65...@gmail.com>> wrote: > > I'm thinking about setting up a master in the colo with a slaved > master at each site, > > > I would strongly recommend using "master-less" recipes, which are > actually "a git repository as a master, and cronjobs running puppet > apply as client".
keep in mind if you implement a masterless setup that you can't aggregate values for other servers to consume (e.g. exported resources -- or option storeconfigs), so if you'd like to automate configuration of a service based on what is managed in other nodes, you're gonna have to find weird hacks to do this. an interesting read on masterless setups: http://current.workingdirectory.net/posts/2011/puppet-without-masters/ -- Gabriel Filion
signature.asc
Description: OpenPGP digital signature
