homebloga tour of dashboard version 1 1

A Tour of Dashboard Version 1.1

Version 1.1 of Puppet Dashboard was recently released, fixing a number of bugs and broadening the feature set. If you’re already a Dashboard user, you’ll certainly find this a worthwhile upgrade. If you’re not, then now is a great time to check it out. Here’s why: Inventory service integration. Working in beautiful harmony with the recently-released inventory service feature of Puppet, Dashboard can now query and report facts across all your nodes. When viewing an individual node, its current fact information will be retrieved via the inventory service for your perusal. Also of note is the “Custom query” function, found in the left-hand node navigation. This page allows you to specify conditions on particular facts and search for all nodes matching those conditions. For instance, this can be used to easily find all your Debian nodes that haven’t yet been upgraded to Puppet 2.6. Filebucket integration. Continuing in the vein of interconnectivity with Puppet, Dashboard is now filebucket-aware. When the checksum of a file is mentioned in a report, Dashboard will offer to display the bucketed contents. Similarly, when a file’s content changes, you will have the option to view a diff. Improved report support. Reports in the Puppet 2.6 format are now fully supported, in addition to inspect reports created by the new “puppet inspect” application. The page for a Puppet 2.6 report provides resource-level summaries, including information about the previous and current values of any changed properties. Viewing an inspect report is quite similar, except the information shown represents a snapshot of the current state of the system at the time of the report. File search. Using the new file search page, you can easily find which of your nodes have a particular version of an important file. Simply provide the file name and desired checksum, and receive a list of which nodes have the content you want, and which don’t. This feature searches the latest inspect report for your nodes, so you will need to periodically run “puppet inspect” for this functionality to work. This release is available for download, and documentation is coming—preliminary documentation is available here.