I'm not sure this is relevant, too late or simply already implemented,
but I'd like to have array of facts.
A very good example is the "ssh_keys" resource: i'd like to access
$ssh_keys['root'] and distributed that as an authorized_keys to other
nodes. I need this for my backups. :)
I'm sure it
I have done this:
class nrpe inherits puppet::master {
include nagios2::nrpe
user { "nagios":
groups => 'puppet',
}
file { "/usr/lib/nagios/plugins/check_puppet":
ensure => "present",
On Tue, Dec 09, 2008 at 06:46:58PM -0500, Micah Anderson wrote:
> I've created documentation in the ticket[0] on this issue about how to
> get a release signing key setup and how to get it deployed into the
> release process for puppet. I am very interested in any comments for how
> to improve this
On Tue, Dec 09, 2008 at 04:30:36PM -0500, Micah Anderson wrote:
> James Turnbull <[EMAIL PROTECTED]> writes:
>
> > The MD5 hash for the file is here:
> >
> > http://reductivelabs.com/downloads/puppet/puppet-0.24.7rc2.tgz.md5
>
> As the one who requested this[0], I'm happy that this is being
> pro
We had nodes on which puppetd keeps on dying and we like to know about
it. So I wrote a small Nagios plugin (that we run through NRPE,
naturally), to process the output of 'puppetlast' regularly and monitor
for boundary conditions.
The source is maintaned here:
http://hg.koumbit.net/module-puppe
So it seems a few people have developped a good few modules on their
own, something I clumsily complained about earlier...
Now I always have a hard time finding those repositories before starting
to write my own module. So I took the liberty of going back into my mail
archive and add the ones I kn
