Well you can use the reporting system, dump to YAML and parse, but I would highly suggest waiting until 2.6.0 where the reporting is going from cludgy to elegant. If you need it now, look at: http://projects.puppetlabs.com/projects/puppet/wiki/Reports_And_Reporting
Right now supported things are email, syslog, and YAML (aka storage). A script could easily parse the YAML and do what you want, but since it is changing radically (for the better) in 2.6.0 I would avoid any heavy coding. - Tom On Jun 28, 9:38 am, dbs <[email protected]> wrote: > I have a 3 different puppetmasters running different groups of > machines (dev, testing, and production). I'd like to very simply say > "Give me a brief summary of the status of the nodes you manage." > > I've been having nightmare dependency problems trying to get things > like Dashboard running that seem to be able to do this (Ruby, which > may be an elegant language, is very crunchynew in regards to specific > versions and stable updates. Frustrating). > > What I'd like to see is something like: > > $ puppetstatus > Node etl01.foo.com : Ok (Last contact: 6/28/2010 12:40pm, last update: > 6/26/2010 11:05am (Module sudoers) > Node etl02.foo.com : Ok (Last contact: 6/28/2010 11:25am, last update: > 6/26/2010 11:03am (Module sudoers) > Node etl03.foo.com : Ok (Last contact: 6/28/2010 12:18pm, last update: > 6/26/2010 9:05am (Module sudoers) > Node db02.foo.com: Error (Last contact: 6/28/2010 12:18pm) : Depedency > not met : MySQL v5.1.20 > > Is this possible? I looked at the external nodes methodology, but > that seems to be a mechanism for just storing node definitions, not > getting status updates. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
