I haven't implemented it yet, but you should be able to accomplish this with Puppet environments.
On Tue, May 27, 2014 at 7:31 AM, Chaos Golubitsky < [email protected]> wrote: > On Mon, 19 May, 2014 at 11:05:30 -0700, Brent Chapman wrote: > > > Google uses both of these patterns ("rate limit your rollouts" and "one, > > few, many") together in many of its systems; the value of these patterns > > has been proven many, many times in allowing us to catch "unexpected" > > failures ("it worked fine in testing, and in the first few hosts we > > updated, and in the first few clusters, but then it blew up...") before > > they swept through an entire service or the whole fleet. > > Out of curiosity, is anyone using config management tools to do this kind > of rate limiting or one/few/many rollout? In particular, while i've never > used Ansible, i gather some people choose it over other CM tools because > it has functionality for, at the very least, "roll out to N hosts at a > time" type updates. Is anyone using it (or any other open source tool) > to manage the logic of staged updates? If so, do you like it? > > Thanks. > > Chaos > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- Perfection is just a word I use occasionally with mustard. --Atom Powers--
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
