On Tue, Jun 23, 2009 at 3:11 PM, martin<[email protected]> wrote: > > I've been struggling to find a good way of preventing myself from > shooting myself in the foot when pushing new puppet profiles to my > servers. I try to do rigorous testing, but there is always the odd > system which was setup years ago and keels over when puppet makes the > changes. > > The approach I've taken is to run two puppetmasters[1] and only push > the changes to one of them at a time, and waiting for the changes to > stew before pushing to the other. This way I won't take down a whole > site at once. > > How have you solved this problem?
Why not use environments to actually have an unstable->testing->stable release process? Alternatively you could have a canary environment you push to first, and have a certain percentage of your clients, like 5%, randomly use the canary environment, that way you're only breaking 5% of your fleet at max when pushing a change. > > [1] <http://blogs.sun.com/martin> > > cheers, > /Martin > -- > Martin Englund, Security Engineer, Web Engineering, Sun Microsystems > Inc. > Email: [email protected] Time Zone: GMT+1 PGP: 1024D/AA514677 > "The question is not if you are paranoid, it is if you are paranoid > enough." > > > -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
