I’ve been at PuppetConf for the last couple of days. As usual, it has been an amazing experience and worth the price of admission.
After seeing the presentations, I have a few things I’d like to explore when I get back to the office next week:
- Puppet 3.0 has been released (to the dev repos- hits prod repos on Monday apparently).
- I want to get reinvigorated about the cloud
- Random tools
I’m most excited for the native Hiera support. I’m also excited to see that you can do fully-qualified variables in hiera.
I’ve always been a fan of centralized logging, however my current methodology is to use rsyslog + LogAnalyzer as the solution. We never use LogAnalyzer, the MySQL DB is a pain to maintain, etc. I’m going to look initially at pointing rsyslog at logstash instead, then using logstash to ship apache logs. Logstash’s graphite capabilities looks like something I want to reverse engineer so I can exploit it for logs other than just apache logs.
I think there’s value in using TDD for puppet code, but before diving in head first I want to play around a bit and make sure that it’s something worth investing my time into.
Since my departure from Walt Disney Studios in April, I haven’t done much of anything with regard to the cloud or CloudStack. I want to change that. I can’t afford to have a home lab right now to stand up a test cloud, so I’m going to attempt to leverage public cloud providers built on top of CloudStack to continue my work with automated cloud provisioning with CloudStack. Things have changed quite a bit since I originally gave my talk at PuppetCamp LA and I want to make sure it all works. I’m also considering submitting a talk for the Cloudstack Collaboration Conference later this year in Las Vegas.
I need to finally pull the trigger and start learning to use some new tools. At the top of my list are Vagrant, BoxGrindr, and Varnish.
If you didn’t attend this year, you really missed out. Catch the slides once they have been posted and register early for next year.