So I like to think I know a bit about enterprise monitoring and configuration management. I’ve done a lot of it over the years across multiple platforms and using a bunch of tools - both proprietary and open source. I’ve even written two books about the open source tools, Nagios and Puppet. But all this time I’ve been doing it wrong. Really badly wrong. The typical enterprise monitoring and configuration management set-up is generally something like this: central server(s) manage and monitor a number of services on local and/or remote hosts.

This post is a little late… but. Puppet 0.25.1 - code name “zoot” - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available via tarball and gem. Please report issues and feedback via the Reductive Labs Redmine site: Please select an affected version of 0.25.1. RELEASE NOTES * We’ve clarified that the new ‘require’ function only works for 0.25.x clients. If the function is specified with 0.

I just thought I’d mention some of the places you can get help with Puppet and Facter. The first is the Puppet users mailing list (and for development related questions - the puppet-dev list too) Also available is the #puppet IRC channel on Freenode where a lot of helpful people lurk and can answer questions (needless to say a lot of really interesting sysadmin related rant^H^H^H discussion also takes places there too).

So I am at SFO waiting to board my plane back to Australia - it’s been a long, long, long eight days. I arrived in SFO on Saturday morning and spent a bunch of days sight seeing, working, a little writing and then actually putting together the slides and videos for my talk on Thursday. Over the course of the week I ate loads of Mexican food (and other good foods!

A small change in the way the Puppet reference documents are structured in the wiki. We’ve split out the Metaparmeter reference documentation from the Type Reference documentation and created a new page to hold them.