I have a home-brewed script that seems to me to answer this part of the request. Not ruby, though...
> The issue was to detect the nodes that hadn't checked in but were >defined in the manifest. I don't try to parse the manifest in any way. Instead, I compare a list of the signed certificates known to my master with a list of machines which appear to have checked in during the past 24 hours. It may not be complete, but it is a good start. I am beginning to wonder if I need a derivative of this -- just highlighting the changes in the list of puppets that are absent without leave. I can post the script I have so far if it would help. Chris Ritson (Computing Officer and School Safety Officer) Room 707, Claremont Tower, EMAIL: c.r.rit...@ncl.ac.uk School of Computing Science, PHONE: +44 191 222 8175 Newcastle University, FAX : +44 191 222 8232 Newcastle upon Tyne, UK NE1 7RU. WEB : http://www.cs.ncl.ac.uk/ -- 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.
