If you are looking to implement it via the puppetdbquery module that Ken was referring to earlier, here is some code to do so with. I recently implemented this approach with my own setup and it worked out great. About 2500 nagios_service resources went from taking 20-30 minutes to about 2. Only issue i ran into was with puppet dashboard when the size of the report log became too big to save for one run. I had to alter the mysql DB columns from text to mediumtext and now its all good.
https://gist.github.com/richardc/4714701 On Wednesday, June 5, 2013 3:57:22 PM UTC-4, David Schmitt wrote: > > On 2013-06-05 15:53, Jonathan Gazeley wrote: > > On 25/05/13 17:24, David Schmitt wrote: > >> On 2013-05-25 10:11, Alexander Bien wrote: > >>> On 24.05.2013 16:58, Ken Barber wrote: > >>>> Its probably the nagios resource, its well known for not scaling when > >>>> the files contain a lot of entries. That would explain why your > >>>> PuppetDB is showing low load - as its probably not the bottleneck. > >>> > >>> I second that. We have mysql storeconfigs, about 5000 Services, 2,5 MB > >>> nagios_* files and >50k lines of config. The puppet run takes aprox 45 > >>> minutes. I have heard people on irc say that its not uncommon. > >> > >> You can cut quite a bit off that time by using templates and files > >> (one per service/host) and purging on the base directory. > >> > > > > Hi David, > > > > Sorry to reply to a stale thread. Please could you explain a bit more on > > your solution? Presumably I need to pas some extra arguments to my > > spaceship operator that collects the Nagios resources, but how is the > > directory-level purging done? > > I'm doing it this way: > > file { > "/etc/nagios/conf.d": > ensure => directory, > source => "puppet:///modules/nagios/empty", > ignore => [ '.gitkeep' ], > recurse => true, > force => true, > purge => true; > } > > File<<| tag == 'nagios::service' |>> > > define nagios::service(...) { > @@file { > "/etc/nagios/conf.d/${host}_service_${name}": > content => template("nagios/service.erb"), > tag => 'nagios::service', > ...; > } > > This way you collect a minimal number of simple resources. This still is > dog slow when you have a couple of thousand services, but it sure beats > the heck out of parsing the complete nagios config for each nagios_* > resource. > > > > Regards, David > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2858c151-1647-4bcd-bd3d-6071451aedf1%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
