Hi, I wonder are there any best practices for deployment of changes in a large puppet environment?
Once we change puppet code all changes are applied within 30 minutes on an environment of several thousand hosts across multiple geographical zones. An automation power in its scaring beauty. Surely it is tested in preproduction and dev envs before, but still, there is a risk when applying it on all zones almost the same time. What I look for is to deploy changes progressively per equivalent of Amazon's Availability Zone via a pipeline, in order to control the propagation of system changes. Surely it will make a change slower but it is a price to pay. Any best practice about it? Best regards, Iakov -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/18f24142-226b-4f10-98a5-6db992f4a005%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
