berber wrote: > This doesn't sound very professional. You would risk your production > environment because it's uncomfortable for the sys admin to remember > he needs to roll back a change in 10 minutes or 10 hours? > > Assume we are talking about a business that looses tens of thousands > of $$$ for any small downtime. Does this change the picture? >
How much money do you think one-off config file edit mistakes cost businesses every year? How much money do you think misconfigured applications or hosts cost businesses every year? You seem to be misunderstanding the notion of controlled change. Change is good. Preventing change actually causes more harm - it costs money in missed business opportunity, wasted employee resources, etc. The key part that you need to recognize is that it should be *controlled* change. With Puppet, this happens via deploying your manifests in the same way you deploy any other piece of software. You test it. You stage it. You roll it out in an iterative fashion to prod. You monitor it. -scott -- 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.
