So, I have all the nodes export their Nagios stuff, and all my Nagios hosts then collect what they need (via tagging). The only tricks I used were to override the file locations so that everything actually gets put into a test directory, and then have an exec kicked by changes which runs a pre-flight and, if the results are good, rsyncs the files from the test directory into the real directory. To clean up nodes/services that have gone away, there is a nightly job that wipes the test directory.
On Sep 29, 2011, at 8:47 AM, Bernd Adamowicz wrote: > We were using Naginator resources like nagios_host, etc. along with stored > configurations and exported resources. Worked pretty well. However we have to > separate the Puppet master and the Icinga (Nagios) server. They will be on > different machines from now on. Are there any best practices for such a > scenario? I already thought about some kind of 'rsync' of the configuration > from Puppet master to the Icinga host. Any ideas? > > Thanks > Bernd > > -- > 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. > -- 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.
