On Nov 17 2011, 5:51 am, Martijn Grendelman <mart...@iphion.nl> wrote:
> Hi,
>
> Is there a way to 'unique-ify' a collection of resources?
>
> Suppose that nodes export '@@nagios_hostgroup' resources for hostgroups
> that they want to be a member of. The Nagios server node collect those:
>
> Nagios_hostgroup <<||>>
>
> But many nodes export the same hostgroups, because the whole point of
> having hostgroups is, that multiple hosts can be a member :-) So, the
> collection would lead to duplicate definitions. Is there a way to avoid that?
The trick here is to realize that only the nagios server (the resource
collector) needs access to these resources. This means your clients
really do not need to export the resource at all. Instead, the
resources should be included in the manifest that ends up being
compiled by your nagios server(s). You're probably saying "Yes, but
how do I then control what hostgroup each client is a member of?". I
solve this problem with a combination of a node scoped variable and
the hostgroups parameter of the Nagios_host exported resource like so:
@@nagios_host {
hostgroups => inline_template("<%= has_variable?
('my_nagios_hostgroups') ? my_nagios_hostgroups : 'Other' %>"),
...
and of course, my nagios server's manifest then includes the hostgroup
resources
nagios_hostgroup { ['Awesome', 'Not Awesome', 'Other']:
ensure => present,
...
}
Best,
Adam
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
