Hello,
I recently started deploying puppet on our server
farm. It works wonderfully with RHEL4, Gentoo and
Debian.
I''m looking for a way to determine the state of all
nodes.
Say for example that I change a file on the
puppetmaster which affects 200 nodes. Then I go to
lunch. When I get back, I''d like to know which nodes
have been updated and which have not.
I asked this in the IRC room, and one user responded,
"why wouldn''t it have updated them all"? It''s
really
not fair to make such an assumption. Nodes may be
down for repairs, some other sysadmin may have shut
down the puppet daemon, there are many possibilities.
My point is that in virtually all cases a "set it and
forget it" mentality isn''t acceptable.
I searched through the mailing list, some people
referenced the PuppetShow but that appears to be a
dead project.
How does everyone else determine the state of all
their nodes?
Thanks.
--
John Philips
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
I think what you want is reporting (and tagging) which is well documented: * http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting * http://reductivelabs.com/trac/puppet/wiki/ReportReference * http://mail.madstop.com/pipermail/puppet-users/2007-November/005001.html I found myself looking to do the same thing. I wrote a utility that will spin through my nodes to look at /var/lib/puppet/state/state.yaml to see when the last time that state file was updated. The result of that is output in the form of "N minutes ago" as anything over a period of time suggests a problem on my end. Cheers, Ryan On Dec 5, 2007, at 3:28 PM, John Philips wrote:> Hello, > > I recently started deploying puppet on our server > farm. It works wonderfully with RHEL4, Gentoo and > Debian. > > I''m looking for a way to determine the state of all > nodes. > > Say for example that I change a file on the > puppetmaster which affects 200 nodes. Then I go to > lunch. When I get back, I''d like to know which nodes > have been updated and which have not. > > I asked this in the IRC room, and one user responded, > "why wouldn''t it have updated them all"? It''s really > not fair to make such an assumption. Nodes may be > down for repairs, some other sysadmin may have shut > down the puppet daemon, there are many possibilities. > My point is that in virtually all cases a "set it and > forget it" mentality isn''t acceptable. > > I searched through the mailing list, some people > referenced the PuppetShow but that appears to be a > dead project. > > How does everyone else determine the state of all > their nodes? > > Thanks. > > -- > John Philips > > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Dooley wrote:> I think what you want is reporting (and tagging) which is well > documented: > > * http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting > * http://reductivelabs.com/trac/puppet/wiki/ReportReference > * http://mail.madstop.com/pipermail/puppet-users/2007-November/005001.html > > I found myself looking to do the same thing. I wrote a utility that > will spin through my nodes to look at /var/lib/puppet/state/state.yaml > to see when the last time that state file was updated. The result of > that is output in the form of "N minutes ago" as anything over a > period of time suggests a problem on my end. > > Cheers, > Ryan >Would be great if you added the utility to the Wiki somewhere. :) Regards James Turnbull - -- James Turnbull <james@lovedthanlost.net> - --- Author of Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) Hardening Linux (http://www.amazon.com/gp/product/1590594444/) - --- PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0C42DF40) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHV0rF9hTGvAxC30ARAn4kAJ4qqUC7H1vxbC2mqDTS79m/Xk8OJACdFcil PPDs2fdXowvyPr8uFy7gyhU=t8qB -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 06 December 2007, Ryan Dooley wrote:> I think what you want is reporting (and tagging) which is well > documented: > > * http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting > * http://reductivelabs.com/trac/puppet/wiki/ReportReference > * > http://mail.madstop.com/pipermail/puppet-users/2007-November/005001.html > > I found myself looking to do the same thing. I wrote a utility that > will spin through my nodes to look at /var/lib/puppet/state/state.yaml > to see when the last time that state file was updated. The result of > that is output in the form of "N minutes ago" as anything over a > period of time suggests a problem on my end.Wouldn''t it be better/easier to collect this timestamp with something like munin and/or nagios? Regards, DavidS - -- The primary freedom of open source is not the freedom from cost, but the free- dom to shape software to do what you want. This freedom is /never/ exercised without cost, but is available /at all/ only by accepting the very different costs associated with open source, costs not in money, but in time and effort. - -- http://www.schierer.org/~luke/log/20070710-1129/on-forks-and-forking -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHV6Aj/Pp1N6Uzh0URAsp3AJoCXCRsFbVZ7+GO/a/xjmUhDOfNNwCffe5g Oau9ytqNYEa9DNMsEcyLtlY=CAke -----END PGP SIGNATURE-----
On Dec 6, 2007, at 1:09 AM, David Schmitt wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thursday 06 December 2007, Ryan Dooley wrote: >> I think what you want is reporting (and tagging) which is well >> documented: >> >> * http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting >> * http://reductivelabs.com/trac/puppet/wiki/ReportReference >> * >> http://mail.madstop.com/pipermail/puppet-users/2007-November/ >> 005001.html >> >> I found myself looking to do the same thing. I wrote a utility that >> will spin through my nodes to look at /var/lib/puppet/state/ >> state.yaml >> to see when the last time that state file was updated. The result of >> that is output in the form of "N minutes ago" as anything over a >> period of time suggests a problem on my end. > > Wouldn''t it be better/easier to collect this timestamp with > something like > munin and/or nagios?Wouldn''t it make even more sense to just have your clients send a report and then use the timestamp from the latest report? -- He is indebted to his memory for his jests and to his imagination for his facts. --Richard Brinsley Sheridan --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
<Derek.Whayman@barclayscapital.com>
2007-Dec-06 16:36 UTC
Re: Reporting / determining state of nodes
This is exactly what we''re doing. A little bit of Perl-YAML processing on the reports. It would be nice if we didn''t do the parsing ourselves (I''m sure I''ve made a few mistakes in the referencing) but for the most part you can make good looking output from it. Derek -----Original Message----- From: puppet-users-bounces@madstop.com [mailto:puppet-users-bounces@madstop.com] On Behalf Of Luke Kanies Sent: 06 December 2007 16:31 To: Puppet User Discussion Subject: Re: [Puppet-users] Reporting / determining state of nodes Wouldn''t it make even more sense to just have your clients send a report and then use the timestamp from the latest report? ------------------------------------------------------------------------ For important statutory and regulatory disclosures and more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group. ------------------------------------------------------------------------