On Dec 17, 9:08 pm, Alexandre <alexandre.fou...@gmail.com> wrote:
> 4). All implementations of 4) i saw in this discussion say i have for
> each node, specify exactly what i want to disable and enable, so that
> if i have 100 nodes, i have to create 100 different stripdown.
I think the result is rather that if you have 100 different *services*
you want to manage via Puppet, then you need a stripdown for each
one. And any way around that's true; it's merely a question of
whether you put all those services' stripdowns in the same class or in
separate classes. You probably have a lot fewer than 100 services.
Personally, if I am interested in the mysql service, then for each
node I would prefer to see one of:
node foo {
include mysql::server
...
}
or
node foo {
include mysql::server::disabled
...
}
or maybe
node foo {
include mysql::server::absent
...
}
You prefer to not be explicit about the latter two cases, and that's
fine, but it doesn't change the number of different combinations of
services your various nodes offer.
> While it is easy saying a node what it should include so that it
> provides the needed services, it is big task and unmaintanable to
> specify exhaustively what nodes should not include.
How maintainable it is depends in part on how many distinct
configurations you need to manage. Do be aware that nodes that are
configured identically do not need separate entries in the node list:
node node1,
node2 {
include mysql::server
}
If you have more than a handful of distinct configurations, though,
then you might be well served by an external node classifier. That's
a program you provide that Puppet uses to dynamically determine which
classes should be included for each node.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
