The closest equivalent to Pro Puppet is this book:
It is a probably best book for Chef at this point in time.
- Rilindo
On Oct 18, 2013, at 2:18 AM, Philippe Bérard <
">
> 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 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. 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 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 | | | <image001.gif> |
P Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité. Thanks Daniel, the feature in Enterprise Chef sounds interesting. Do you know the timeline for this feature's release in Enterprise Chef? 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.
|