On Fri, 8 Jan 2010, Kenneth Holter wrote: > Do you mean running puppetmaster on different linux servers? It would > probably be the best solution, but I do think I prefer running multiple > puppetmasters on one linux server if possible.. How are other people > testing new puppetmasters? > > On Thu, Dec 31, 2009 at 6:42 PM, Scott Smith <sc...@ohlol.net> wrote: > Kenneth Holter wrote: > > > > We're look into ways to implement change management to our puppet > > configurations, and this approach is very interesting as it seems very > > > > Even easier: Maintain multiple Puppet infrastructures. Push your code to each > as it is ready. > > Dev puppetmaster, dev puppet clients. > Staging puppetmaster, staging puppet clients. > Production puppetmaster, production puppet clients. > > It also will enable you to maintain a staging environment that is as close to > prod as possible. > > -scott
We use multiple puppetmasters and branches. Virtualization makes it easy to spin up new puppetmasters. We have lab environments where we develop and test puppet code and each of those has its own puppetmaster and branch. Some admins have a personal puppetmaster and branch and we'll also spin masters for specific projects. After testing the code in a branch we merge to trunk. Dev and QA systems run off trunk and after the changes pass QA we merge to a prod branch. In the future we're going to take a tag off trunk and release that to the production puppetmasters. We've found that multiple branches can be tricky to keep in sync so we make a point of frequent merges to trunk and rebranching. Otherwise trunk and the branches get so out of sync that merging becomes a real chore. -Eric
-- 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.
