Chef : the definitive date?


#1

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
http://www.jalios.com/ www.jalios.com

JALIOS

<https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDeman
deDinformation%2FeditFormDemandeDinformation.jsp&cids=> webinars

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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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


#2

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” philippe.berard@jalios.com
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****

[image: JALIOS]****

[image: webinars]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=


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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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****




#3

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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” <philippe.berard@jalios.commailto:philippe.berard@jalios.com> 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 17tel:%2B33%20(0)1%2039%2023%2031%2017
Mob : +33 (0)6 01 27 87 86tel:%2B33%20(0)6%2001%2027%2087%2086
Fax : +33 (0)1 39 55 47 56tel:%2B33%20(0)1%2039%2055%2047%2056

58, Rue Pottier
78150 Le Chesnay
www.jalios.comhttp://www.jalios.com/

[cid:image001.gif@01CECB3B.CB64E860]

[cid:image002.jpg@01CECB3B.CB64E860]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=
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:michael.hart@arcticwolf.commailto:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : <chef@lists.opscode.commailto:chef@lists.opscode.com>
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.4773tel:226.388.4773

On 2013-08-21, at 12:43 PM, Daniel DeLeo <dan@kallistec.commailto:dan@kallistec.com> 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.4773tel:226.388.4773


Daniel DeLeo


#4

The best I’ve seen is this one: http://www.packtpub.com/chef-starter/book

Unfortunately it still can be really confusing. When people ask “How do I start chef?” I say this: First, try to do something with chef-solo. Second ask questions, mailing list/#chef free node. Third, read the above book. Forth try to set up open source chef server, and start learning knife plug ins. Fifth, start over because trust me you’ll want to re-visit it because you’ll want to refactor everything.

That’s the cycle I’ve been seeing/doing and I think it’s going great.

Best Regards,
JJ Asghar
e: jj.asghar@peopleadmin.com | c: 512.619.0722 | o: 512.977.5876

From: Philippe Bérard <philippe.berard@jalios.commailto:philippe.berard@jalios.com>
Reply-To: "chef@lists.opscode.commailto:chef@lists.opscode.com" <chef@lists.opscode.commailto:chef@lists.opscode.com>
Date: Thursday, October 17, 2013 11:38 AM
To: "chef@lists.opscode.commailto:chef@lists.opscode.com" <chef@lists.opscode.commailto:chef@lists.opscode.com>
Subject: [chef] Chef : the definitive date ?

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.comhttp://www.jalios.com/

[JALIOS]

[webinars]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=
PAfin de contribuer au respect de l’environnement, merci de n’imprimer ce message qu’en cas de nécessité.

De : Michael Hart [mailto:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : <chef@lists.opscode.commailto:chef@lists.opscode.com>
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 <dan@kallistec.commailto:dan@kallistec.com> 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


#5

On 10/17/2013 3:46 PM, JJ Asghar wrote:

The best I’ve seen is this one: http://www.packtpub.com/chef-starter/book

There is also the following, released ~1.5 months ago:

Chef Infrastructure Automation Cookbook
http://www.packtpub.com/chef-infrastructure-automation-cookbook/
Pages: 276
Author: Matthias Marschall of http://www.agileweboperations.com/

I own it, but have only read enough of it so far to say that it is
at least written and edited well. I purchased it mainly to see if it
was The Chef Book to hand to colleagues that need to get up to
speed… but also to see if there was anything to learn from it
(I’m deep into Chef already, not starting out).

Someday…

Unfortunately it still can be really confusing. When people ask “How do
I start chef?” I say this: First, try to do something with chef-solo.
Second ask questions, mailing list/#chef free node. Third, read the
above book. Forth try to set up open source chef server, and start
learning knife plug ins. Fifth, start over because trust me you’ll want
to re-visit it because you’ll want to refactor everything.

That’s the cycle I’ve been seeing/doing and I think it’s going great.

Best Regards,
JJ Asghar
e: jj.asghar@peopleadmin.com | c: 512.619.0722 | o: 512.977.5876

From: Philippe Bérard <philippe.berard@jalios.com
mailto:philippe.berard@jalios.com>
Reply-To: "chef@lists.opscode.com mailto:chef@lists.opscode.com"
<chef@lists.opscode.com mailto:chef@lists.opscode.com>
Date: Thursday, October 17, 2013 11:38 AM
To: "chef@lists.opscode.com mailto:chef@lists.opscode.com"
<chef@lists.opscode.com mailto:chef@lists.opscode.com>
Subject: [chef] Chef : the definitive date ?

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 http://www.jalios.com/

JALIOS

webinars
https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=

PAfin de contribuer au respect de l’environnement, merci de n’imprimer
ce message qu’en cas de nécessité.

*De :*Michael Hart [mailto:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : <chef@lists.opscode.com mailto:chef@lists.opscode.com>
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 <dan@kallistec.com
mailto:dan@kallistec.com> 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


#6

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:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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 tel:%2B33%20(0)1%2039%2023%2031%2017
Mob : +33 (0)6 01 27 87 86 tel:%2B33%20(0)6%2001%2027%2087%2086
Fax : +33 (0)1 39 55 47 56 tel:%2B33%20(0)1%2039%2055%2047%2056

58, Rue Pottier
78150 Le Chesnay
http://www.jalios.com/ www.jalios.com

JALIOS

<https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDeman
deDinformation%2FeditFormDemandeDinformation.jsp&cids=> webinars

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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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


#7

No, I don’t think it’s going that great.

Some questions are never answered here, and asking questions each time you have a problem is, very often, a waste of time.

Thanks for your answer, though

Regards,

– Philippe Bérard

De : JJ Asghar [mailto:jj.asghar@peopleadmin.com]
Envoyé : jeudi 17 octobre 2013 21:47
À : chef@lists.opscode.com
Objet : [chef] Re: Chef : the definitive date ?

The best I’ve seen is this one: http://www.packtpub.com/chef-starter/book

Unfortunately it still can be really confusing. When people ask “How do I start chef?” I say this: First, try to do something with chef-solo. Second ask questions, mailing list/#chef free node. Third, read the above book. Forth try to set up open source chef server, and start learning knife plug ins. Fifth, start over because trust me you’ll want to re-visit it because you’ll want to refactor everything.

That’s the cycle I’ve been seeing/doing and I think it’s going great.

Best Regards,

JJ Asghar

e: jj.asghar@peopleadmin.com | c: 512.619.0722 | o: 512.977.5876

From: Philippe Bérard philippe.berard@jalios.com
Reply-To: "chef@lists.opscode.com" chef@lists.opscode.com
Date: Thursday, October 17, 2013 11:38 AM
To: "chef@lists.opscode.com" chef@lists.opscode.com
Subject: [chef] Chef : the definitive date ?

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
http://www.jalios.com/ www.jalios.com

JALIOS

https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids= webinars

PAfin de contribuer au respect de l’environnement, merci de n’imprimer ce message qu’en cas de nécessité.

De : Michael Hart [mailto:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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


#8

fwiw

Patrick

On 18/10/13 09:18, 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

*De :*Stephen Corbesero [mailto:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com mailto:chef@lists.opscode.com
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” <philippe.berard@jalios.com
mailto:philippe.berard@jalios.com> 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.


#9

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 :slight_smile:
best
ranjib

On Fri, Oct 18, 2013 at 12:18 AM, Philippe Bérard <
philippe.berard@jalios.com> 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:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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****

[image: JALIOS]****

[image: webinars]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=


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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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****




#10

Hi Patrick,

Thanks for the other book you mentionned, looks like I’ve been missing it.

Still much disappointed with this book’s cancelation, as it’s been heavily
promoted by Opscode people themselves.

Regards,

– Philippe Bérard

De : Patrick Debois [mailto:Patrick.Debois@jedi.be]
Envoyé : vendredi 18 octobre 2013 09:23
À : chef@lists.opscode.com
Objet : [chef] Re: RE: RE: Re: Chef : the definitive date ?

fwiw

Patrick

On 18/10/13 09:18, 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

De : Stephen Corbesero [mailto:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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.


#11

On Oct 18, 2013 9:18 AM, “Philippe Bérard” philippe.berard@jalios.com
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.

Not sure which edition you have, but the 2nd edition is a complete rewrite
and covers much more than the 1st edition.

It’s surely not an in-depth definitive Chef guide, instead it covers a
broad range of the whole Chef / Ruby / Vagrant / Berkshelf / Testing
frameworks ecosystem which is great in its own (but maybe not what you are
specifically asking for ;-))

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:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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


#12

Hi,

Have you seen our effort at:

http://gettingstartedwithchef.com/

If it’s not suitable or not what you’re looking for then I’d be very
interested to hear what we’re doing wrong.

Cheers,

Andy

On Thu, Oct 17, 2013 at 6:21 PM, Stephen Corbesero <
Stephen.Corbesero@synchronoss.com> wrote:

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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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****

[image: JALIOS]****

[image: webinars]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=


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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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****




Andy Gale
http://andy-gale.com
http://twitter.com/andygal http://twitter.com/andygale


#13

That’s a really nice resource, I’ll be sharing it with people who want to
learn Chef.

On Fri, Oct 18, 2013 at 6:51 AM, Andy Gale andy@salgo.net wrote:

Hi,

Have you seen our effort at:

http://gettingstartedwithchef.com/

If it’s not suitable or not what you’re looking for then I’d be very
interested to hear what we’re doing wrong.

Cheers,

Andy

On Thu, Oct 17, 2013 at 6:21 PM, Stephen Corbesero <
Stephen.Corbesero@synchronoss.com> wrote:

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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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****

[image: JALIOS]****

[image: webinars]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=


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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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****




Andy Gale
http://andy-gale.com
http://twitter.com/andygal http://twitter.com/andygale


Best regards, Dmitriy V.


#14

The closest equivalent to Pro Puppet is this book:

http://www.amazon.com/Chef-Infrastructure-Automation-Cookbook-ebook/dp/B00ESX18KQ/ref=sr_1_6?ie=UTF8&qid=1382151797&sr=8-6&keywords=chef+opscode

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 philippe.berard@jalios.com 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:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com 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
<image001.gif>
<image002.jpg>
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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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


#15

Hello all,

On 18 October 2013 08:18, Philippe Bérard philippe.berard@jalios.comwrote:

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.

The 2nd edition of this has just been released, it’s 300+ pages long and is
a complete rewrite. Owners of the 1st edition can download the 2nd edition
free of charge.


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.

I have mentioned this several times on Twitter, but I guess I should have
written on the list too. The book has been cancelled for the following
reasons:

  1. Chef is large and fast moving. Attempting to maintain a “definitive
    guide”, especially one for which there is an expectation that it will be
    printed, and sold at a high price, is just unrealistic. Especially for one
    person, who does more that write books for a living. Chef isn’t in a place
    where we could write a definitive introduction and not have it date.

  2. The docs.opscode.com site is a valuable resource. Opscode employs a
    professional technical writer, and is responsive to suggestions and help.
    It is improving all the time, and by explicitly not backing a definitive
    guide, or expecting one, it encourages the community to cooperate on a
    "currently" definitive guide for the community to use and share.

  3. The rewrite of Test-driven Infrastructure was a massive undertaking.
    The decision was made to finish that rather than divert attention to the
    TDG book. Initial feedback I have had is that TDI2 is a good book, and I
    will continue to work on and expand this.

  4. For beginners, the learnchef website is great, and Seth Vargo is working
    on an introductory volume, also for O’Reilly.

  5. The strategy we feel is right (that is O’Reilly, me and Nathen at
    Opscode) is to create subject-specific deeper dive books of a more
    manageable length. I have a few ideas for this, and would welcome input
    from the community as to what the most important topics are.

To sum up - I remain committed to continuing to write on Chef, and will try
to be responsive to suggestions and feedback. I think it was a mistake to
begin the TDG project, in retrospect, and while I do accept that the
communication around the cancellation could have been handled much better,
I do think it’s the right decision.

S.



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:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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****

[image: JALIOS]****

[image: webinars]https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDemandeDinformation%2FeditFormDemandeDinformation.jsp&cids=


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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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****




Stephen Nelson-Smith,
Founder, Principal Consultant,
Atalanta Systems Ltd,
Web: http://agilesysadmin.net
Twitter: @lordcope
Skype: atalanta.systems
Direct: +44 (0) 1329 550203
Mobile: +44 (0) 7917 101919

Atalanta Systems: The Agile Infrastructure Enablers
http://atalanta-systems.com


#16

Hi,

On 19 October 2013 04:06, Rilindo Foster rilindo@mac.com wrote:

The closest equivalent to Pro Puppet is this book:

http://www.amazon.com/Chef-Infrastructure-Automation-Cookbook-ebook/dp/B00ESX18KQ/ref=sr_1_6?ie=UTF8&qid=1382151797&sr=8-6&keywords=chef+opscode

Matthias is a great guy and a lucid writer. He knows Chef well, and this
is a good book.

S.


#17

Hi Stephen, and thanks for this explanation.

Maybe someone should have changed the book title, then, and call it “Pro
Chef” or something close.

I can understand that there are plenty of docs on the Net, but something to
read on paper is, very often, far more convenient for learning. I’m new at
Ruby, new at Chef and have done many cookbooks that worked well, installing
complete Apache+Mod-JK+PostgreSQL+JAVA+Tomcat+Webapp environments, and had a
to rewrite almost everything when Chef 11 went out.

I’ll buy the book on Packt, hoping that you will find new ideas for a book
on Chef aimed at intermediate and expert users.

Regards,

– Philippe Bérard

De : Stephen Nelson-Smith [mailto:stephen@atalanta-systems.com]
Envoyé : samedi 19 octobre 2013 07:12
À : chef@lists.opscode.com
Objet : [chef] Re: RE: RE: Re: Chef : the definitive date ?

Hello all,

On 18 October 2013 08:18, Philippe Bérard philippe.berard@jalios.com
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.

The 2nd edition of this has just been released, it’s 300+ pages long and is
a complete rewrite. Owners of the 1st edition can download the 2nd edition
free of charge.

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.

I have mentioned this several times on Twitter, but I guess I should have
written on the list too. The book has been cancelled for the following
reasons:

  1. Chef is large and fast moving. Attempting to maintain a “definitive
    guide”, especially one for which there is an expectation that it will be
    printed, and sold at a high price, is just unrealistic. Especially for one
    person, who does more that write books for a living. Chef isn’t in a place
    where we could write a definitive introduction and not have it date.

  2. The docs.opscode.com site is a valuable resource. Opscode employs a
    professional technical writer, and is responsive to suggestions and help.
    It is improving all the time, and by explicitly not backing a definitive
    guide, or expecting one, it encourages the community to cooperate on a
    "currently" definitive guide for the community to use and share.

  3. The rewrite of Test-driven Infrastructure was a massive undertaking. The
    decision was made to finish that rather than divert attention to the TDG
    book. Initial feedback I have had is that TDI2 is a good book, and I will
    continue to work on and expand this.

  4. For beginners, the learnchef website is great, and Seth Vargo is working
    on an introductory volume, also for O’Reilly.

  5. The strategy we feel is right (that is O’Reilly, me and Nathen at
    Opscode) is to create subject-specific deeper dive books of a more
    manageable length. I have a few ideas for this, and would welcome input
    from the community as to what the most important topics are.

To sum up - I remain committed to continuing to write on Chef, and will try
to be responsive to suggestions and feedback. I think it was a mistake to
begin the TDG project, in retrospect, and while I do accept that the
communication around the cancellation could have been handled much better, I
do think it’s the right decision.

S.

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:Stephen.Corbesero@synchronoss.com]
Envoyé : jeudi 17 octobre 2013 19:22
À : 'chef@lists.opscode.com’
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 [mailto:ukio@gmx.de]
Sent: Thursday, October 17, 2013 12:49 PM
To: chef@lists.opscode.com
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” philippe.berard@jalios.com
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 tel:%2B33%20(0)1%2039%2023%2031%2017
Mob : +33 (0)6 01 27 87 86 tel:%2B33%20(0)6%2001%2027%2087%2086
Fax : +33 (0)1 39 55 47 56 tel:%2B33%20(0)1%2039%2055%2047%2056

58, Rue Pottier
78150 Le Chesnay
http://www.jalios.com/ www.jalios.com

JALIOS

<https://www.jalios.com/jcms/?portal=xtl_14865&cid=r_19240&jsp=types%2FDeman
deDinformation%2FeditFormDemandeDinformation.jsp&cids=> webinars

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:michael.hart@arcticwolf.com]
Envoyé : jeudi 22 août 2013 02:45
À : chef@lists.opscode.com
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 dan@kallistec.com 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


Stephen Nelson-Smith,
Founder, Principal Consultant,
Atalanta Systems Ltd,
Web: http://agilesysadmin.net
Twitter: @lordcope
Skype: atalanta.systems
Direct: +44 (0) 1329 550203
Mobile: +44 (0) 7917 101919

Atalanta Systems: The Agile Infrastructure Enablers
http://atalanta-systems.com