[chef] Re: Chef : the definitive date ?

[Torben Knerr < >]

Hi Philippe,

you might also be interested in the "Test-Driven Infrastructure with Chef (2nd Edition!)" book which was released just a few days ago.

Cheers,
Torben

On Oct 17, 2013 6:38 PM, "Philippe Bérard" < "> > wrote:

Hello all,

 

Is there any availability date for the « CHEF : the definitive guide » book, which seems to be delayed over and over ? There is still no complete and comprehensive guide on CHEF, and that’s a real pain for newcomers.

 

Thanks in advance for your answer.

 

Regards,

 

Philippe Bérard IT Manager
Tel : +33 (0)1 39 23 31 17 Mob : +33 (0)6 01 27 87 86 Fax : +33 (0)1 39 55 47 56
58, Rue Pottier 78150 Le Chesnay www.jalios.com

P Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité. 

 

De : Michael Hart [mailto: " target="_blank"> ]
Envoyé : jeudi 22 août 2013 02:45
À : < " target="_blank"> >
Objet : [chef] Re: how to know if a chef-client run is occuring

 

Thanks Daniel, the feature in Enterprise Chef sounds interesting. Do you know the timeline for this feature's release in Enterprise Chef?

 

cheers

mike

 

-- 

Michael Hart

Arctic Wolf Networks

M: 226.388.4773

 

On 2013-08-21, at 12:43 PM, Daniel DeLeo < " target="_blank"> > wrote:

 

On Wednesday, August 21, 2013 at 9:22 AM, Michael Hart wrote:

Is there a definitive way of querying the chef server to see if a chef-client run is occurring on a node? We've noticed that a "knife status" will return a timestamp of "382528 hours ago", or however many hours you are away from epoch, and but it's not entirely consistent and using that in code feels like a bit of a hack. Ideally I'd like an API to return true or false if a chef-client run is occurring. Thoughts?

Chef client communicates over HTTP, which is a stateless protocol, so there's no robust way for the server to know anything other than the last time a client made a request.

 

In Enterprise Chef (née Hosted and Private Chef), upcoming updates will include a node run history reporting feature that emulates the ability to track running clients by having them check in at the beginning and end of a run. How much of this makes it into the open source version and when is an open question at this point, but you could use a custom event dispatcher to track the state of clients in a similar way by integrating with a different system.

 

 

cheers

mike

 

-- 

Michael Hart

Arctic Wolf Networks

M: 226.388.4773

 

 

 

-- 

Daniel DeLeo