Well, we survived a faux apocalypse and 2013 is upon us. This is that special time of year when we reflect on what really happened over the last 12 months and what we hope to accomplish in the next 12.
Internally we’ve refocused some teams, shifted people around, and grown staff levels. Heck, the (delivery) team I run didn’t exist 12 months ago. So, in the past year, what has happened that you, the user, care about?
Puppet Labs shipped 143 separate releases of product in 2012. This excludes modules on the Puppet Forge, and Puppet Forge releases themselves. I was astonished when we started tracking this metric where we were at. It doesn’t seem like we ship that much, but when you have an array of projects, including Puppet, Facter, MCollective, Puppet Dashboard, Hiera, hiera-puppet, puppetlabs_spec_helper, PuppetDB and Puppet Enterprise, it starts to add up.
Between those projects and cutting release candidates for them, you’ve got something like 2.77 releases per week from Puppet Labs. Wow. Early in 2012, we didn’t package up every release candidate; we just made tarballs and put them up on the website. In the middle of May, however, we began automating more of our packaging and uploading processes to launch the release candidate repositories. This now means packaging (Mac, Windows, RPM, Deb, Rubygems) of preview release software, as well as final releases. Our goal wit that was to get more people trying the next thing coming out of Puppet Labs. It worked.
Puppet Labs’ first major release for 2012 was Puppet Enterprise 2.5, which launched in March. It introduced Windows support, added in the Puppet Module Tool to Puppet, and included role-based access control to the Puppet Enterprise console.
April saw the launch of MCollective 2.0, which added speed enhancements, better security features around STOMP, command chaining, JSON output, and a batch mode to run commands in smaller groups and eliminate all thundering-herd problems.
PuppetDB was released in the middle of May. This was a really exciting and interesting piece of technology for anybody in the Puppet ecosystem. First off, it was designed with APIs in mind from the ground up. It was backward compatible with the storedconfig interface. PuppetDB was also our first real project not to be primarily in Ruby. The end result, though, was fantastic. Speed was the primary feature, but you’re just beginning to see the feature-rich solutions that can be built using PuppetDB as a backend.
Shortly after Puppet Enterprise 2.6.0 was released — which added authentication options to the Puppet Enterprise console via LDAP, Active Directory and Google Apps — came my favorite time of year: PuppetConf 2012. PuppetConf was bigger and better than ever this year. We had several awesome write-ups of Conf from this year. I can promise you one thing, if you weren’t there, you’re going to want to be in 2013.
PuppetConf was a success basically any way you measure it. Besides launching the Puppet Certification Program, PuppetConf also saw us push on the platform-side of development quite a bit. PuppetDB launched 1.0 just before the conference kicked-off. And if you weren’t completely blown away by the awesome talks from Gene Kim, CERN, VMware , GitHub and SpaceX, there was more…
Puppet 3.0.0 finally made it to the hands of our users the Friday of PuppetConf. Puppet 3.0.0 was great. It was faster, so much faster. It also supports Ruby 1.9.3. Data-binding through Hiera were rolled into the core of Puppet 3.0. Tack on lots of bug fixes, better support for Solaris and Windows and you’ve got an all-around great release.
The rest of 2012 saw us ship many bug-fix and feature releases of every product in our library.
We also stepped up our game on the Puppet Forge. In June, we crossed the 400-module mark on the Forge. Today, we have 726 (as of *right* now). We created a product team for the Puppet Forge and I hope you’ve noticed some awesome changes. Module pages show if they have any issues at GitHub, module download counts, and the front page has been reworked to show you what’s new and who’s frequently putting fresh content on the Puppet Forge.
The number of Puppet Camps we hosted also grew exponentially this year, from one in 2011, to 14 in 2012. We had camps all over the world — Atlanta, Edinburgh, Stockholm, Amsterdam, New York, Los Angeles, Dublin, Geneva, Chicago, Nuremberg, Sydney, Kuala Lumpur, Boston and Singapore — and the demand for them continues to grow. Check out some of the cities we already have lined up in 2013.
I hope 2012 was awesome for you as a Puppet user. With new releases and better content, there hasn’t been a more exciting time to automate your infrastructure. We had high expectations for ourselves in 2012. We have a much higher bar for ourselves in 2013, which should mean good things for you.