[chef] Re: Re: Single Chef client for configuring multiple nodes


Chronological Thread 
  • From: Jesse Nelson < >
  • To: chef < >
  • Subject: [chef] Re: Re: Single Chef client for configuring multiple nodes
  • Date: Wed, 27 Feb 2013 23:38:41 -0800

I did do some work on a proxy like this a while back, but I no longer work where it was intended  It used the same client to represent many nodes. Brokered data into faux nodes from snmp endpoints. Still think it would be a worthwhile tool for the community to have. 


On Wed, Feb 27, 2013 at 10:43 PM, AJ Christensen < " target="_blank"> > wrote:
Just use --node-name or an alternate configuration file (pointing to
the same client pem, with a different node_name).

Works great! I've never found a use for it; we always thought people
might create a client that was responsible for multiple virtual nodes,
e.g. switches that weren't running Chef or something along those
lines.

--AJ

On 28 February 2013 19:31,  < "> > wrote:
> Hi,
>
> Found this statement in the Chef client documentation... "A single Chef Client
> can run recipes for multiple Nodes". But I could not find any further
> documentation or supporting description which talks about how this is possible.
>
> Any one has tried this? Is there any in-built support for enabling a single
> client to configure multiple nodes ?
>
> Any info on this regard will be very helpful.
>
> Thanks,
> Saritha




Archive powered by MHonArc 2.6.16.

§