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

[Aaron Peterson < >]

Have you looked at our "Build a FOO" series
http://help.opscode.com/kb/otherhelp ?  There are several full stack
examples and a nagios quick start that show standing up actual
infrastructure.  Build it, then dive in to see how Chef was used to
automate what you just did.

We're definitely working on covering as many learning styles and
approaches as possible.  It's not an easy field(yet), infrastructure
automation!  I'd love feedback on how this approach works for folks.

-a
-- 
Aaron Peterson 
<
 >
Opscode Technical Evangelist



On Wed, Jul 6, 2011 at 13:17, Jeffrey E. Sussna 
<
 >
 wrote:
> 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
>> >
>
>
>