Puppet Nodes

[Dominic]

Hello, New user to Puppet 

I am trying to see if Puppet can replace my Mac servers for managing 1200 clients. Testing has gone well and I am very impressed with the functions and potential this platform can offer me.

However I have hit upon a sticking point.

I need to manage lots of machines in groupings. Can I do this by defining the name in 

site.pp

import "nodes/*.pp"

then in nodes/

nodes/*.pp ==> lab1.pp

nodes/*.pp ==> lab2.pp

so 

nodes/lab1.pp

nodes/lab2.pp

so all 30 machines with the name lab1_1.domain (lab1_2.domain etc..) only get the lab1.pp and machines called lab2.*.domain get the lab2.pp or is there a better way to deal with this?

Or would it be 

nodes/labs.pp

node 'lab1* ' {

notify {"this is a lab1 machine"}

}

node 'lab2* ' {

notify {"this is a lab2 machine"}

}

Struggling to get my head around automatically defining groups.

Thank you  

 

[Dominic]

OK Think I found my own answer

https://docs.puppetlabs.com/puppet/latest/reference/lang_node_definitions.html

node /^lab1\d+$/ { include common }

node /^lab2\d+$/ { include somthingelse }

[Gavin Williams]

If you want something a bit smarter, you could look at The Foreman [1]. 

Cheers

Gavin

[1] http://theforeman.org/

[Dominic]

I did look at that..

But I could not see if the group structure was a more traditional layout. Might bring it up on a VM to have a look.

However the snippet of regex allowed me to pull all the modules together and deploy them in a manor that I want. Its a fantastically powerful tool.

I wish the grouping was nicer.

[Felix Frank]

On 11/11/2014 06:58 PM, Dominic wrote:
>
> I wish the grouping was nicer.

Hi,

would you care to elaborate on that? If we are missing features, we
should at least keep them around as tickets.

Thanks,
Felix