[chef] Re: RE: RE: Re: Chef : the definitive date ?

[Ranjib Dey < >]

i dont find anything wrong in that. chef is still evolving rapidly. unlike puppet, chef has always grown as a tool, + community + various forms of extensions (cookbooks/knife plugins/handler etc). there are so many features, enhancements coming in every releases... that you may not want to publish a definitive guide so soon . .. also for one who is in dire need, there are ample stuff in wiki btw. learnchef, docs etc.

i recently did a review on one of the book, and this was very evident. most of the books that u'll have now will not cover lot of new stuff.  without that you can not call a book definitive guide. or pro chef (whatever).

again, i am not sure if this is the case here (may be something totally different), only he can answer that. but my point is , given if we need something, we must do it ourselves, or help some one who doing it.

we did a foodfightshow on the same. i think we need more concrete stuff . we can have an opensource Chef book, that community can write collaboratively :-)

best
ranjib

On Fri, Oct 18, 2013 at 12:18 AM, Philippe Bérard < " target="_blank"> > wrote:

That’s really bad news. I still have « Test-driven infrastructure with Chef » but it’s a very small book covering only simple aspects of Chef.

 

I can’t understand how Stephen Nelson-Smith can attend so many events telling people what to do or not, and then canceling this so much awaited book.

 

We still don’t have a “pro puppet” like documentation, and I think it’s a real handicap for CHEF’s community.

 

Regards,

 

-- Philippe Bérard

 

De : Stephen Corbesero [mailto: " target="_blank"> ]
Envoyé : jeudi 17 octobre 2013 19:22
À : ' " target="_blank"> '
Objet : [chef] RE: Re: Chef : the definitive date ?

 

Unfortunately, the latest word I have seen from the O’Reilly web site is that “Chef: The Definitive Guide” has been cancelled with very little explanation.

 

This link is the discussion thread: http://support.oreilly.com/oreilly/topics/chef_the_definitive_guide_missing_from_search_results

 

 

 

From: Torben Knerr [ " target="_blank">mailto: ]
Sent: Thursday, October 17, 2013 12:49 PM
To: " target="_blank">
Subject: [chef] Re: Chef : the definitive date ?

 

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" < " target="_blank"> > 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