I notice on this page (http://wiki.opscode.com/display/chef/Chef+Client#ChefClient-ClientsdoworkforoneormanyNodes) it mentions one client can manage multiple nodes. So far I’ve always seen a one-to-one relation between clients and nodes. Can anyone shed some light on how one-to-many is used and why?
Yo,
On 22 July 2010 09:16, Alex Soto apsoto@gmail.com wrote:
I notice on this page (
http://wiki.opscode.com/display/chef/Chef+Client#ChefClient-ClientsdoworkforoneormanyNodes)
it mentions one client can manage multiple nodes. So far I've always seen a
one-to-one relation between clients and nodes. Can anyone shed some light
on how one-to-many is used and why?
I haven't seen anyone use this - or use it myself. Very possible. It's used
by supplementing the client configuration with -N/--node-name/node_name
(client.rb).
Regards,
AJ
On Jul 21, 2010, at 2:31 PM, AJ Christensen wrote:
Yo,
On 22 July 2010 09:16, Alex Soto apsoto@gmail.com wrote:
I notice on this page (http://wiki.opscode.com/display/chef/Chef+Client#ChefClient-ClientsdoworkforoneormanyNodes) it mentions one client can manage multiple nodes. So far I've always seen a one-to-one relation between clients and nodes. Can anyone shed some light on how one-to-many is used and why?I haven't seen anyone use this - or use it myself. Very possible. It's used by supplementing the client configuration with -N/--node-name/node_name (client.rb).
Ok, next time I have a test machine up I'll give it a run through, but I'd love to hear if any one else has tried this, what happens, what's it useful for, etc.
Regards,
AJ
On 21 July 2010 22:52, Alex Soto apsoto@gmail.com wrote:
I haven't seen anyone use this - or use it myself. Very possible. It's used
by supplementing the client configuration with -N/--node-name/node_name
(client.rb).Ok, next time I have a test machine up I'll give it a run through, but I'd
love to hear if any one else has tried this, what happens, what's it useful
for, etc.
This sounds to me like a feature that was almost accidently
implemented, as a side effect of being able to specify the
configuration file. I can't think of any situation in which I'd want
multiple nodes on one machine, if only because of the risk of them
getting stuck in a loop of overriding each other's decisions.
On 23 Jul 2010, at 11:23, Jon Wood wrote:
This sounds to me like a feature that was almost accidently
implemented, as a side effect of being able to specify the
configuration file. I can't think of any situation in which I'd want
multiple nodes on one machine, if only because of the risk of them
getting stuck in a loop of overriding each other's decisions.
The example I saw for multiple nodes per client was for configuring nodes that can't run chef directly (e.g. firewalls and routers), so another node acts as a kind of proxy.
Marcus
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK resellers of info@hand CRM solutions
marcus@synchromedia.co.uk | http://www.synchromedia.co.uk/