I gave up and stopped trying to obfuscate the nagios configuration in
puppet. I simply have puppet pushing out anything I drop into
/etc/nagios/conf.d, and then doing a nagios restart. This makes it very easy
to add hosts and services because a script can read the node manifest and
drop the necessary files into modules/nagios/etc/nagios/conf.d.

Doug.

On Fri, Mar 11, 2011 at 7:22 AM, Brian Gallew <g...@gallew.org> wrote:

> My setup also has a worst-case propagation delay of 90 minutes.  I have a
> custom fact that collects all of the information in classes.txt on the
> client.  That, in turn, is used (for Nagios) by a custom parser function
> that produces the hostgroup list for when the nagios_host resource is
> exported.  It's not optimal, but it's fully automatic.  In the rare case
> where I want/need the info to propagate immediately, I can run "puppet agent
> --test" twice on the client and then once more on the Nagios server.
>
> All of the services, as in your case, are generated as members of
> hostgroups.
>
>
> On Fri, Mar 11, 2011 at 6:14 AM, Martijn Grendelman <mart...@iphion.nl>wrote:
>
>> On 11-03-11 12:46, Martijn Grendelman wrote:
>> [snip]
>>
>> > I did exactly what you did: use exported concat-fragments to collect the
>> > hostgroups on the puppetmaster and then use generate() to provision the
>> > hostgroups parameter of the nagios_host.
>>
>> [snip]
>>
>> > The biggest downside of my system so far, is the fact that, in a
>> > worst-case scenario, it takes 90 minutes for a configuration change to
>> > propagate to Nagios.
>>
>> I now replaced the exported concat fragments with local concat fragments
>> and a custom fact, which reads the result of the concat and joins it into
>> a comma-separated string.
>>
>> Dependencies make sure that the concats are done before the nagios_hosts
>> are exported.
>>
>> This removes the need to collect anything on the puppetmaster and reduces
>> the time needed to propagate a configuration change to Nagios in the worst
>> case to 30 minutes.
>>
>> Best regards,
>> Martijn.
>>
>> --
>> 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.
>



-- 
Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627

-- 
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.

Reply via email to