I use two separate puppetmasters for lab and production. (The lab side has more of the "dratted commas" style of checkin.)
Testing changes to one particular type of server is where virtualization really shines. You can spin up a scratch virtual machine with the same manifests as your target host, snapshot the VM, and then apply your manifest changes. If the changes break you can revert the VM and fix your manifests. Once things are to your satisfaction you can commit to production. For VMWare I like snapshotting at the grub screen on each lab host on first boot (before the first puppet run), given that reverting to the last snapshot is higher priority than powering on. That way I have a server where I can conveniently start "clean" on every boot as long as I remember to scrub certs from the puppetmaster. On Tue, Oct 18, 2011 at 01:52:18AM -0700, Andreas Paul wrote: > Hi, > > we are currently managing our puppet modules with one SVN workspace for > each admin. > The post commit hook script updates /etc/puppet/ directory and triggers > the puppet kick of the correct server. > > The problem we have with this solution is that sometimes there are many > small checkins to one change, because the admin forgot to change small > details in the config file, e.g. forgot to change the access logfile name > of the vHost, forgot a redirect, misspelling in the comments etc. > > What we end up with are many micro checkins, which can be used to tell > every small mistake the admin has done. > > What we want is a solution which lets the admin test his changes on one > server without checking these changes into the "main" SVN repository. > So that the SVN repository only contains the final releases of the > changes. > > I have to say that we also manage the dev and QA servers with this > puppetmaster. Would dividing of these different stages into puppet > environments help us? > What I really want to know is, do you understand my problem and if you had > the same problem, how did you solve it? SVN branches? Multiple > puppetmasters, one to test with a dedicated test SVN repository? > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > [1]https://groups.google.com/d/msg/puppet-users/-/FLNYwiOI1fwJ. > 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. > > References > > Visible links > 1. https://groups.google.com/d/msg/puppet-users/-/FLNYwiOI1fwJ -- 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.
