On Tue, Oct 5, 2010 at 6:05 PM, Mohamed Lrhazi <lrh...@gmail.com> 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.... > How do you deal with that? I would be interested in any experience or > input, especially puppet proper best practices...
Lots of precommit hooks to catch the obvious human errors Easy to use testing environment so you can test your changes quickly. Strict release process. We follow unstable -> testing -> stable like Debian. You absolutely need to sort your release process out. > > BTW, does puppet have any means to say something like "don't ever do > anything that takes more than 5 minutes? or that involves more than > 1000 files/inodes? > > Thanks a lot. > Mohamed. > > -- > 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. > > -- nigel -- 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.
