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

[Ranjib Dey < >]

Which tech stack you are using? Configure chef client as non daemon (i.e. chkconfig chef-client off. service chef-client stop), and use your language specific ssh library from ServerA to invoke `chef-client --once` on server B. You can use tools like capistrano for doing such stuff (if you are comfortable with ruby, or vanilla net/ssh library).

regards

ranjib

On Tue, Jul 5, 2011 at 6:42 AM, 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
>