On 4 December 2012 17:05, fatmcgav <fatmc...@gmail.com> wrote: > Pete > > Sounds good to me... N be easier than me re-inventing the wheel... > > Would be happy to guinea pig... :) >
Awesome. I have an account on gitorious which I am going to use to put my code on. Gimme a bit to get my module cleaned up and make sure it works by itself. Will let you know when it's up there. Pete. > > Cheers > Gav > > > > On 3 December 2012 23:56, Peter Brown <rendhal...@gmail.com> wrote: > >> Hi Gavin, >> >> I have a module i wrote that seems like it will do what you need. >> I also have a nagios module that uses it to setup nrpe services on each >> node and exports nagios checks to be imported into a nagios instance. >> >> I basically setup nrpe on each node to use a config directory and have a >> define that uses templates to generate each nrpe service that need to be >> setup. >> My nagios module needs some rewriting before I will be happy releasing it. >> The nrpe module is pretty much good to go though. >> It can also use sudo, also managed by another module I have (Yeah I have >> a lot olf modules and most of them talk to other modules I wrote) >> >> I am going start putting my stuff on github and puppet forge as soon as I >> have them ready. >> >> Are you interested in being a guinea pig? >> >> :) >> >> Pete. >> >> >> On 3 December 2012 21:47, Gavin Williams <fatmc...@gmail.com> wrote: >> >>> Morning all >>> >>> I've had a quick google, but couldn't find anything useful for our >>> scenario... >>> >>> Basically, we use Nagios & NRPE in our environment, along with a >>> hand-full of in-house written plugins specific to our applications etc... >>> These scripts change on a fairly regular basis, so hand rolling a RPM >>> each time is too much work as far as i'm concerned... >>> >>> So I can easily get NRPE installed on a node using Puppet... However >>> what I'm struggling with is getting all the plugins synced over aswell... >>> >>> One suggestion I read was to use a file resource, however I've also read >>> about severe performance issues when working with tens of files... >>> I dont really want to have to create some kind of NFS file share to >>> distribute the files... >>> >>> So, any other ideas? >>> >>> Cheers >>> Gavin >>> >>> P.S. Env consists of a single 3.0 Puppet Master, currently with about a >>> dozen nodes connected, but this will rapidly increase once we start full >>> roll-out... >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msg/puppet-users/-/NgMZ8MKfN1oJ. >>> >>> 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. >> > > -- > 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.