Hi,
maybe it''s in front of me but I can''t see it, maybe
I''m looking for
something in existent, but sounds strange to me.
Is there ant way for grouping node in nodes.pp?
I mean, now I have:
# cat nodes.pp
node "td234.pic.es" , "td065.pic.es",
"td006.pic.es" [...]{
include worker_node
}
May I do a group of, i.e,
WN_A {
td234.pic.es
}
WN_B {
td065.pic.es
td006.pic.es
}
group WN_A WN_B{
include C
}
group WN_A {
include A
}
group WN_B {
include B
}
Anyone could help me?
Cheers,
Arnau
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Has anyone put together a puppet proposal for deploying puppet in your environment? Zach On 1/22/09 8:10 AM, "Arnau Bria" <arnaubria@pic.es> wrote:> > Hi, > > maybe it''s in front of me but I can''t see it, maybe I''m looking for > something in existent, but sounds strange to me. > > Is there ant way for grouping node in nodes.pp? > > I mean, now I have: > > # cat nodes.pp > node "td234.pic.es" , "td065.pic.es", "td006.pic.es" [...]{ > include worker_node > } > > > May I do a group of, i.e, > > WN_A { > td234.pic.es > } > > WN_B { > td065.pic.es > td006.pic.es > } > > group WN_A WN_B{ > include C > } > > > group WN_A { > include A > } > > group WN_B { > include B > } > > > > Anyone could help me? > > Cheers, > Arnau > > >-- Zachary Buckholz, Senior Unix Systems Administrator University of Phoenix | IT Operations 4025 S. Riverpoint Parkway │ Phoenix, Arizona 85040 phone: 602.557.6809 | cell: 602.377.8023 | email: zach.buckholz@apollogrp.edu P Please consider the environment before printing this email. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/22/2009 9:10 AM, Arnau Bria wrote:> Is there ant way for grouping node in nodes.pp?The following should work for what you described. I use a similar model to have a parent class for all compute cluster nodes, and then child classes for each group of nodes that needs a slightly different policy (a reboot schedule for nodes that operate as Windows PCs during the day, another group that should have a particular piece of software loaded on them, etc.) class worker-node { include C } class worker-node-a inherits worker-node { include A } class worker-node-b inherits worker-node { include B } node "td234.pic.es" { include worker-node-a } node "td065.pic.es", "td006.pic.es" { include worker-node-b } -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, 22 Jan 2009 09:34:11 -0600 Mike Renfro wrote:> > On 1/22/2009 9:10 AM, Arnau Bria wrote: > > > Is there ant way for grouping node in nodes.pp? > > The following should work for what you described. I use a similar > model to have a parent class for all compute cluster nodes, and then > child classes for each group of nodes that needs a slightly different > policy (a reboot schedule for nodes that operate as Windows PCs > during the day, another group that should have a particular piece of > software loaded on them, etc.) > > class worker-node { > include C > } > > class worker-node-a inherits worker-node { > include A > } > > class worker-node-b inherits worker-node { > include B > } > > node "td234.pic.es" { > include worker-node-a > } > > node "td065.pic.es", "td006.pic.es" { > include worker-node-b > }Yep, I was thinking of inherits, but I''ll have to control host group like: node "nodeA" "nodeB" { } which is what I''m trying to not use. Thanks for your reply, Arnau --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, 22 Jan 2009 08:16:48 -0700 Zach Buckholz wrote:> > > Has anyone put together a puppet proposal for deploying puppet in your > environment?I don''t understand you, sorry.> ZachArnau --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/22/2009 10:11 AM, Arnau Bria wrote:> Yep, I was thinking of inherits, but I''ll have to control host group > like: > node "nodeA" "nodeB" { > } > > which is what I''m trying to not use.Your original concept used something like WN_A { td234.pic.es } WN_B { td065.pic.es td006.pic.es } which isn''t too different. What specifically are you trying to avoid? -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, 22 Jan 2009 10:32:14 -0600 Mike Renfro wrote:> > On 1/22/2009 10:11 AM, Arnau Bria wrote: > > > Yep, I was thinking of inherits, but I''ll have to control host group > > like: > > node "nodeA" "nodeB" { > > } > > > > which is what I''m trying to not use. > > Your original concept used something like > > WN_A { > td234.pic.es > } > > WN_B { > td065.pic.es > td006.pic.es > } > > which isn''t too different. What specifically are you trying to avoid?Maybe it''s just syntax issue.... maybe with files example I can explain myself better: WN_A.pp { td234.pic.es } WN_B.pp { td065.pic.es td006.pic.es} nodes.pp> group WN_A WN_B{ > include C > } > > > group WN_A { > include A > } > > group WN_B { > include B > }Then adding a noe is just adding a new line to a file... I''ll manage about 100-120 hosts...1 Thanks for your reply, Cheers, Aranu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 1/22/2009 10:42 AM, Arnau Bria wrote:> Then adding a noe is just adding a new line to a file... > I''ll manage about 100-120 hosts...1I manage about 90 with the ''node "node1", "node2", "node3" {}'' method, but my groupings are pretty static. Entered them once, and haven''t thought about it much since then. Two options come to mind for decoupling your node lists from the manifests: 1. Use or adapt http://reductivelabs.com/trac/puppet/wiki/Recipes/HostgroupFact -- I mostly wrote this so I could have a single fact that would let me select a particular hosts.equiv for a similar group of systems. Using it as-is would require that you can write Ruby lists to describe the hostnames in each group, distribute the fact to each client, etc. 2. External node classification tools. Never used these, but they''ll probably do everything you''d want and more. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Mike Renfro wrote:> On 1/22/2009 10:42 AM, Arnau Bria wrote: > >> Then adding a noe is just adding a new line to a file... >> I''ll manage about 100-120 hosts...1 > > I manage about 90 with the ''node "node1", "node2", "node3" {}'' method, > but my groupings are pretty static. Entered them once, and haven''t > thought about it much since then. Two options come to mind for > decoupling your node lists from the manifests: > > 1. Use or adapt > http://reductivelabs.com/trac/puppet/wiki/Recipes/HostgroupFact -- I > mostly wrote this so I could have a single fact that would let me select > a particular hosts.equiv for a similar group of systems. Using it as-is > would require that you can write Ruby lists to describe the hostnames in > each group, distribute the fact to each client, etc. > > 2. External node classification tools. Never used these, but they''ll > probably do everything you''d want and more. >External node is clearly made for this kind of things. Way to go. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks to both for your replies. I''ll take a look and come back with my decision. Cheers, Arnau --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---