Hi, [snip]
Very interesting that you should say that you created a Puppet master for > each environment ... it's the obvious way to accommodate the limits of RPM > packaging while retaining the ability to use Puppet in full agent mode. > > Is this considered a best practice? What other considerations drive the > decision to have a Puppet master per environment? > We are a hosting/service provider company and have a number of customers that have completely isolated setups. So a single puppetmaster was never really an option. We put some effort in the easy and automated creation of puppetmasters and module distribution (hence the RPMs :)), to be able to use Puppet agent mode. >From there on, the decision to split them per environment (only for large customers ofcourse), was trivial. And it indeed allows us to test upgrades of our masters, while protecting us from "development" code accidently ending up on production machines. Don't know if it's a best practice. There is the overhead of a number of puppetmasters, and some loss of centralizatiion (for reports, ...), but that is something we knew from the start. Kind regards, k -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
