[chef-dev] Re: Re: Re: Re: Re: Re: Re: Fwd: How do I know if my application has really been "provisioned"? a suggestion

[AJ Christensen < >]

We've got Flock working for cross node-resource notifications, subscriptions, wait_for and wait_until (FYI)

--AJ

On 10 December 2012 12:22, Peter Donald < " target="_blank"> > wrote:

Hi,

On Mon, Dec 10, 2012 at 10:07 AM, Mark Van De Vyver < " target="_blank"> > wrote:

 Longer term I agree that something like the `ensure{}`

suggestion might work to allow one chef-solo/client run to coordinate

with another.  Irrespective of whether that other process/Chef-Solo run is on

another machine or the same machine.

I don't know of a good solution for coordination of chef across multiple nodes. We currently use a separate command and control service that orchestrates the updating of databags and the kick off of chef-client runs where appropriate. However I have been watching flock_of_chefs [1] which is a really interesting take on the whole deal. I am extremely interested in that sort of approach for more choreographed releases rather than orchestrated releases. No idea if it will eventuate or it is just an experiment but it is an interesting project to watch and the author usually writes good stuff.

[1] https://github.com/chrisroberts/flock_of_chefs

--
Cheers,

Peter Donald