[chef] Re: Re: Re: Re: Running chef-client from another server and waiting for a result

[Jeffrey E. Sussna < >]

The chef documentation is very bottom-up. It talks about nodes and roles and recipes and attributes and data bags. I think some more use-case driven documentation might help folks find their way around. 

On Jul 6, 2011, at 3:10 PM, andi abes wrote:

A simple way to do that is to use knife ssh:

knife ssh "name:<test-machine-name>" "chef-client"

For full details see http://wiki.opscode.com/display/chef/Knife#Knife-SSHSubcommand

This will basically ssh to the test machine, run chef-client and pipe  the results locally. when chef-client is done, this command will return.

On Mon, Jul 4, 2011 at 9:12 PM, Edward Sargisson < "> > wrote:

Hi Charles,
Thanks for the reply..

> What part of the process do you have questions about?

From serverA I want to tell serverB to run chef-client and tell
serverA when it's done.

The notification bit can probably be done in the report handler
(somehow) but how do I tell serverB to start chef-client?

Cheers,
Edard

On Mon, Jul 4, 2011 at 5:48 PM, Charles Duffy < "> > wrote:
> Yes, this certainly can be done -- in fact, I'll be doing the same thing in
> just a few weeks.
>
> What part of the process do you have questions about?
>
> On Jul 4, 2011 7:34 PM, "Edward Sargisson" < "> > wrote:
>> Hi all,
>> I am thinking of incorporating Chef into a continuous integration
>> server (in this case Bamboo but think Hudson/Jenkins).
>> I'd like to do a build, configure Chef properties for the new version,
>> then kick off chef-client on the test server. Once it's done, I want
>> the script to know about it so that integration tests can be run
>> against it.
>>
>> Is there a way to do this or am I using Chef beyond its purpose?
>>
>> Thanks in advance,
>> Edward
>