[chef] Re: Re: How could I know from the chef server side that whether the running of a chef-client is done?

[Daniel DeLeo < >]

On Wednesday, March 7, 2012 at 8:53 AM, Peter Norton wrote:

> The first link you provide has a pull request that implements reporting to 
> the server. If you combine that with chef-gelf you'd have on the one hand a 
> quick look at the results of the latest run (from the ticket) and a 
> searchable history on a graylog2 server (via chef-gelf).
> 
> There's probably a better way to do this, but these seem like a pretty good 
> start.
> 
> -Peter
> 
> On Wed, Mar 7, 2012 at 7:43 AM, tetsu soh 
> <
 
>  
> (mailto:
 )>
>  wrote:
> > Hi,
> > 
> > How can I check the status of a recipe on Chef server side? Whether it
> > is executed, failed or succeed?
> > 
> > I find a ticket to propose a new feature. How is it going on?
> > http://tickets.opscode.com/browse/CHEF-385
> > 
> > As this mail mentioned, chef's reporting capabilities is something
> > need to improve.
> > http://lists.opscode.com/sympa/arc/chef/2010-01/msg00030.html
> > 
> > 2 years have passed, any progress? or new solution for this?
> > 
> > 
> > Thank you,
> > Tetsu
> 

This feature will be built in to Chef 11. We've resisted adopting the easy 
solution of shoving data in the node because 1) we don't want to take a 
chance on putting bogus node data on the server and screwing up search 
results (could happen during a failed run); 2) This doesn't scale to keeping 
more than one run's data, so we knew we'd need to replace it eventually 
anyway; and 3) knowing we'd replace it, we didn't want to offer an API around 
which people would build tools only to completely change it later (we've 
changed APIs before, but it's not something we take lightly).

What we're implementing for Chef 11 will track client runs over time, 
including information about which resources are updated and how.

Hope that explains things a bit.

-- 
Dan DeLeo