On Tue, Oct 5, 2010 at 6:05 PM, Mohamed Lrhazi <[email protected]> wrote: > Hello all, > > This is not a puppet proper issue of course.. but I was wondering if > any of you could share some thoughts... > > When you deploy a system like Puppet at a large park of systems, you > instantly increase the efficacy of mistakes and bugs in destroying the > environment....
With great power comes great responsibility. > How do you deal with that? I would be interested in any experience or > input, especially puppet proper best practices... In addition to the other responses (testing, some more testing, and a well defined release process) I also recommend a "Big red stop button" of sorts. Few sites seem to employ this, but the ones who have have reported it to be incredibly useful when necessary and enjoy a little more peace of mind. The big red stop button can take many forms. I personally use a wrapper script to launch puppet agent runs from cron, so the stop button in my case could be a simple curl command before running puppet agent and the agent proceeds if and only if the curl command does not get a valid 200 response from the HTTP request. This allow you to quickly touch a file somewhere and know it will halt all puppet agents on all of your nodes. -- Jeff McCune http://www.puppetlabs.com/ -- 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.
