In the Chef-Server Web UI I can easily find the node’s state, but on
the node itself, where to query if this node lost the connection to
the Chef Server?
Any local cache?
Thanks.
chef dashboard, uses a report handler which lets you browser through
updated elements, etc.
since the chef client run is pull mechanism, you can used the expected last
run time and compare it with actual last successful run (available in
couch in epoch) to raise an alert.
On Mon, Jun 4, 2012 at 1:56 PM, howard chen howachen@gmail.com wrote:
In the Chef-Server Web UI I can easily find the node's state, but on
the node itself, where to query if this node lost the connection to
the Chef Server?Any local cache?
Thanks.
Hello,
On Mon, Jun 4, 2012 at 5:02 PM, Ranjib Dey ranjibd@thoughtworks.com wrote:
chef dashboard, uses a report handler which lets you browser through updated
elements, etc.
since the chef client run is pull mechanism, you can used the expected last
run time and compare it with actual last successful run (available in
couch in epoch) to raise an alert.
Maybe I am not clear enough, what I mean is if I lost my chef-server,
would it be possible to find out the node attribute from node itself?
Thanks.
you will be able to get the automatic attributes via ohai. rest im not
sure. you can take periodic backup of couch or enumerate all the nodes and
dump their attributes as json , knife node show <name> -Fj
On Mon, Jun 4, 2012 at 11:33 PM, howard chen howachen@gmail.com wrote:
Hello,
On Mon, Jun 4, 2012 at 5:02 PM, Ranjib Dey ranjibd@thoughtworks.com
wrote:chef dashboard, uses a report handler which lets you browser through
updated
elements, etc.
since the chef client run is pull mechanism, you can used the expected
last
run time and compare it with actual last successful run (available in
couch in epoch) to raise an alert.Maybe I am not clear enough, what I mean is if I lost my chef-server,
would it be possible to find out the node attribute from node itself?Thanks.