[chef] Re: Re: Forcing chef-client to run via API?


Chronological Thread 
  • From: Ranjib Dey < >
  • To:
  • Subject: [chef] Re: Re: Forcing chef-client to run via API?
  • Date: Sun, 6 Jan 2013 16:09:47 -0800

theres nothing out of the box. chef is pull only, the clients asks for recipes from the server, a server in itself can not enforce/dispatch a client run. you can use knife-ssh, ansible or mcollective for this.


On Sun, Jan 6, 2013 at 3:42 PM, Peter Donald < " target="_blank"> > wrote:
Hi,

On Mon, Jan 7, 2013 at 10:30 AM, Dane Elwell < " target="_blank"> > wrote:
I know this can be done using `knife ssh`, but I was hoping for something built-in that can handle this via a RESTful API call.

There is nothing that I know of. We use a combination of SSH and winrm to kickstart our converges after updating the central server. 

As most of our releases end up requiring multi-node coordination we tend to break releases into stages, then interleave updating of the central server with ssh/winrm calls out to the client nodes, testing the resultant converged and state and moving on to next stage in release.


--
Cheers,

Peter Donald




Archive powered by MHonArc 2.6.16.

§