----- "Joel Merrick" <joel.merr...@gmail.com> wrote: > Hi Pupeteers! > > I have a few questions regarding workflow that I'd appreciate insight > from you guys on.. > > 1) How do people manage services that can't be affected all at once? > For instance, we run a number of DNS caches behind load balancers at > two different sites and (not that I'd do this!) if for example I set > bind to always be latest, how do I ensure that the puppet run doesn't > restart all my caches at once? Am I best to include the geographical > and logical information about what cluster they are in as data or > facts within the class, or is it better to subclass.. say > bind::cache::siteA etc..? Is there any kind of splay mechanism?
I use the mcollective method and often combine it by making my modules and package versions configurable using extlookup. Then I simply update extlookup for a specific location/client/environment to manage the roll outs. It's a bit more manual but you know what you get and when. avoid using ensure => latest. -- 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.
