General discussion about Chef

[chef] Re: Re: how to manage nodes without chef-client?


Chronological Thread 
  • From: Kenneth Kalmer < >
  • To:
  • Subject: [chef] Re: Re: how to manage nodes without chef-client?
  • Date: Wed, 29 Dec 2010 12:29:36 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=FOsFDehzgAGFDc+HueFEYJySTOh2dqK2HFdtu4QZ7FbfkS/6EhCMa6rVfb61FuwTO4 +UX6kZS3ODgctpHAtZlGGyZ1QIymvM0JURo8w8VbC9SSI0AK8/pvKI8iA1aCsntoJ/K1 2ysdj4EfwpxLZWqYE2x0HFxJVQVIEKq5npSuo=
On Tue, Dec 28, 2010 at 8:15 AM, Bryan McLellan 
< >
 wrote:
>
> 2010/12/27 Grzegorz Marszałek 
> < >:
> > 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

http://opensourcery.co.za
@kennethkalmer

Archive powered by MHonArc 2.6.16.

§