Hello!
I’m new to chef, but I’ve noticed, that there is possibility (and it’s mentioned on wiki) to give chef client diffirent node name.
What I’m trying to accomplish is to add to system nodes that are unable to run chef-client - list switches, or access points. I’d like to monitor them, and I’d like to configure my nagios from chef. On debian/windows nodes, where I have chef-client I can add proper attritubes and then, on nagios server I can search for them and build nagios config. I’d like to do the same with “unmanaged” nodes - to add attributes with proper data. I thought about using chef-client -N SWITCH_FQDN - but is this good idea? Any recommendations for begginer? 
Cheers
Grzegorz Marszałek
graf0@post.pl
2010/12/27 Grzegorz Marszałek graf0@post.pl:
I'm new to chef, but I've noticed, that there is possibility (and it's mentioned on wiki) to give chef client diffirent node name.
You can. It is theoretically possible to use a chef node to represent
another node. I don't of anyone doing it though.
What I'm trying to accomplish is to add to system nodes that are unable to run chef-client - list switches, or access points.
That's awesome.
The easiest way would be to use "knife node create" which will give
you the basic JSON structure for a node and commit it. If you've got
more than a few nodes, I think writing a snmp discovery tool that
collects data and then talks to the API directly would be great.
Bryan
On Tue, Dec 28, 2010 at 8:15 AM, Bryan McLellan btm@loftninjas.org wrote:
2010/12/27 Grzegorz Marszałek graf0@post.pl:
What I'm trying to accomplish is to add to system nodes that are unable to run chef-client - list switches, or access points.
That's awesome.
The easiest way would be to use "knife node create" which will give
you the basic JSON structure for a node and commit it. If you've got
more than a few nodes, I think writing a snmp discovery tool that
collects data and then talks to the API directly would be great.
I use data bags for the non-chef hosts, and nagios builds the host
checks from that. Works very well, not as flexible and powerful as
directly interrogating the node's attributes, however it still works
very well.
Best
--
Kenneth Kalmer
kenneth.kalmer@gmail.com
http://opensourcery.co.za
@kennethkalmer