Unfortunately the answer right now is “not really.” The node status
page has a little information, but it’s probably not enough detail.
Improving chef’s reporting capabilities is definitely something we’re
interested in doing, as it’s a often-requested feature. I don’t know
where exactly it fits with our roadmap, however.
In the meantime, you can put a recipe very last in the run list that
sends email or otherwise reports a completed run to an external
system. If you’d like to be notified of failures, there’s a hack you
can use involving ruby’s at_exit hooks. I described a bit how it works
On Wed, Jan 13, 2010 at 10:05 PM, Dikang Gu email@example.com wrote:
That is: I run the chef-client as a daemon in the chef client node, and how
could I know when it is finished (for example, a software is installed on
the node)? Can I get this information by querying the chef server?
Hope my question is clear.