[chef] Re: Re: Re: How to coordinate restart across roles

[Jesse Nelson < >]

  Dooozer is not abandoned  There are a couple companies taking it up and collaborating on it. Last week they had a hangout and discussion on how to move forward.  ActiveState, Bitly, Soundcloud, Torbit, and the guys working on skynet are all contributing. The initial push is going to get doozer in the "ha" org to build on go. Each of the orgs I mentioned above all have their own versions that are more up to date and which have various features. We are using skynet version of doozerd internally for evaluation as a network lock service.

State of doozer discussion: 

https://groups.google.com/d/topic/doozer/fVcS0y3KuHQ/discussion

Notes from the meeting:

https://groups.google.com/d/topic/doozer/oUuhBwQ_Ga4/discussion

Skynet doozerd:

https://github.com/skynetservices/doozerd

On Sat, Mar 2, 2013 at 2:29 PM, Noah Kantrowitz < " target="_blank"> > wrote:

On Mar 2, 2013, at 2:17 PM, AJ Christensen wrote:

> I'd recommend looking at Chef + ZK.
>
> We have a rough implementation here that we've used for a few
> successful tests, but nothing major like coordinated rolling
> restarts.: https://github.com/chrisroberts/flock_of_chefs
>
> This is complex stuff. You should 'learn how to do this' first, so to
> speak! I'd recommend playing with tools like Doozer (Go), Paxos
> (multiple lang impls.), Celluloid and DCell too (in Ruby land)
>

As a warning, Doozerd is basically abandoned, though it looks like someone merged a few README fixes today after a year of nothing.

> It's much easier to coordinate processes while learning instead of
> trying to coordinate huge behemoth systems.

My personal fav for this kind of task if Fabric + PyChef :)

--Noah