[chef] Re: Re: Re: Re: node reboot in a chef recipe

[Jacobo García < >]

The handler strategy looks nice, I'll follow that path.

Thanks :)

Jacobo García López de Araujo

http://beattaster.com | http://robotplaysguitar.com | http://twitter.com/therobot 

On Wed, Aug 3, 2011 at 8:19 PM, Seth Chisamore < "> > wrote:

One elegant way you could solve this is to set a flag in node.run_state (inside of a recipe), then look for this flag in a chef report handler [0].

node.run_state[:reboot] = true

This would ensure the reboot happens only after a successful chef run.

Seth

--
Opscode, Inc.
Seth Chisamore, Software Design Engineer
IRC, Skype, Twitter, Github: schisamo


[0] http://wiki.opscode.com/display/chef/Exception+and+Report+Handlers

On Wednesday, August 3, 2011 at 2:09 PM, Jacobo García wrote:

> Nothing special needed,
>
> I have the belief that a server reboot in between a chef-run could be harmful. I will delay the reboot at the end of the chef run at least.
>
> Thanks for your help.
>
> Jacobo García López de Araujo
> http://beattaster.com | http://robotplaysguitar.com | http://twitter.com/therobot
>
>
>

> On Wed, Aug 3, 2011 at 7:25 PM, John E. Vincent (lusis) <lusis.org (http://lusis.org)+ "> (mailto: "> )> wrote:
> > On Wed, Aug 3, 2011 at 1:15 PM, Jacobo García < "> (mailto: "> )> wrote:
> > > Hello,
> > > I am looking for strategies on node rebooting within a recipe.
> > > I am aware of dreamcat4's restart cookbook, but I don't want to patch chef
> > > in order to make it work.
> >
> > Brian had it pretty much covered. Nothing "special" is required.
> >
> >  If you need a bit more "coordinated" reboot, the Webster-Clay guys
> >  created something called "dominodes" that uses a data bag as a mutex
> >  for coordination:
> >
> > https://github.com/websterclay/chef-dominodes