[chef] Re: Run a recipe on another node

["John E. Vincent (lusis)" < >]

I'm as big a proponent of being able to do this as anyone but, as
Stanislaw said you have to be very careful about this. What you're
describing is what some folks refer to as orchestration.

One way to do it is described here -
https://www.speakerdeck.com/u/lusis/p/cross-node-orchestration-with-chef-and-noah
(full disclosure: that's my presentation). Another way that might be a
bit more simple is to simply block the run until search returns a
valid result that you like and then continue.

But as much of an automation fiend as I am, I acknowledge that you
could, without very careful planning and guarding, trigger a nasty
unexpected chain of events.

On Mon, Aug 20, 2012 at 9:22 AM, jfotop 
<
 >
 wrote:
> Hi to all,
> i have been searching for a way to make a recipe that is being run on one
> node's runlist trigger a recipe on another node/role runlist.
>
> The closest thing to what I want to accomplish, according to opscode
> documentation, is to "search" for all the nodes of a specific role, for
> example, all nodes of role apache, and based on the nodes found execute 
> what we
> want, using an array with all of the nodenames.
> The problem rises when, for example, continuing the new node configuration
> requires that the other node(the one that uses the search method and creates
> the array of nodes) must first be configured in order to continue the new 
> node
> configuration.
> That could be accomplished either by creating a recipe that would execute
> something on another node immediately (something like notify immediately
> some_recipe on_another_node), or by executing immediately the runlist of the
> other node before the completion of the running runlist of the new node and
> returning the exit status so that it could continue configuration.
> Of course there could be also more ways to do this.
> But the question is: is anything like this possible? ChefServer 
> version:10.12.0
>
> Thanks!