On Jul 13, 6:54 am, Marco Marongiu <brontoli...@gmail.com> wrote: > Dear puppeteers > > I am trying to build a tree hierarchy of puppetmasters. The architecture > is aimed to distribute the load among a number of datacenters, while > keeping the puppetmasters in sync by means of puppet itself. > > The architecture I am trying to build is: > > - one "main puppetmaster"; > - many "distribution servers", that will be client of the main > puppetmaster, and masters to other clients > - plain clients > <snip> > Thanks in advance > > Ciao > --bronto
I suggest staying away from a hierarchical puppetmaster approach as it adds unneeded complexity. At a former employer we solved the problem of dealing with multiple datacenters or POP's by having a puppetmaster (or load balanced puppetmasters) in each POP. We then had a configuration file in our VCS that mapped POP's to branches in our VCS. The puppetmasters would check the contents of that file and if it changed they would do an svn switch to the new branch/tag. Through this architecture we were able to easily update the code used by the puppetmasters. This also gave us the ability to horizontally scale puppetmasters as appropriate at each POP. Working on having the code available on the Puppet Forge this week. -g -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
