[chef] Re: Re: Can you recommend a command-and-control tool?

[Steven Dossett < >]

We had the same need so I wrote a tool for this in our environment. It allows us to update nodes explicitly and with a controlled pool of connections.

In our case, some of the heavy lifting is accomplished through capistrano using it more or less as a general purpose library for driving chef commands and responses. I also use the Chef exception handler capability to store error conditions and exception data back inside Chef as node data in addition to what we gather from the tool at runtime. The combination works well for us. 

On Mon, Jan 17, 2011 at 7:19 PM, John E. Vincent (lusis) <lusis.org+ "> > wrote:

Rundeck and mcollective will probably be your best bet. I'd love to recommend vogeler but I've had to time off from development for a while.

You can also look at func but it's pretty RHEL specific.

On Jan 17, 2011 7:14 PM, "John Vincent" <lusis.org@gmail.com> wrote:
> Rundeck and mcollective are in the top for the most part. I'd recommend
> Vogeler but I've had to take a break from development for a while. You can
> also look at function but it's pretty rhel specific.
> On Jan 17, 2011 7:10 PM, "Mike Williams" < " target="_blank"> >

> wrote:
>> I'm helping a client rebuild their configuration management and software
> deployment tooling, and we have Chef successfully doing both ... but only on
> a per-node basis. Now I'm looking to add a layer above Chef, to orchestrate
> software/platform updates across a data-center, in a controlled fashion.
>>
>> Any recommendations? Has anyone successfully used something like
> mcollective or nanite, with Chef, to do this kind of orchestration? Do
> recipes exist to install these? (The opscode repo contains a nanite
> cookbook, but it appears to be deprecated). Or, do most people find "knife
> exec" sufficient?
>>
>> --
>> cheers,
>> Mike Williams
>>