On 26 June 2010 23:15, Douglas Garstang <[email protected]> wrote: > Am I the only dinosaur on the mailing list?
Not really. > Admittedly I haven't had an in depth look at the puppet dashboard yet, > but I'm not sure I get the point of it. If it's solely for reporting > purposes, then great, but is it also a tool for making changes to > nodes? That's the bit I don't understand. As an admin, revision > control is _everything_, and I need to be able to account for every > single configuration change that is made to a system. I need to know > who did what, when, and exactly what they did. Does the dash board > allow you to do that? Such auditing could fairly trivially be implemented into a Ruby on Rails web application, and is probably beyond the scope of what they're trying to achieve with the initial releases. I agree it is definitely a worthwhile goal to implement auditing if the long-term future for Puppet Dashboard is to action changes to infrastructure, and not just present a pretty interface to data. Cheerio, - Alex -- 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.
