James Turnbull (finally) joins Puppet Labs

Published on 12 April 2010 by

We're very excited to announce that after years of being a critical contributor to Puppet, including writing the Puppet Book, James Turnbull is joining Puppet Labs as Director of Operations, where he'll be responsible for infrastructure, support, and everything else we can get him to do.

He has been the merge master for Puppet for more than a year, and has built a lot of Puppet's service infrastructure, so it's great we're able to work with him to make Puppet his full time job.

Continue reading

Puppet Labs to Present at Under The Radar Conference

Published on 8 April 2010 by

Puppets’ Data Center Automation Platform Provides the Flexibility and Agility Needed to Effectively Manage Non-Standardized IT Environments

Puppet Labs, home of Puppet, the open source leader in data center automation, will present at this year’s Under The Radar: Commercializing The Cloud Conference. Puppet Labs’ presentation is part of the event’s Infrastructure sessions, and will take place Friday, April 16th, from 3:15-5:00pm, at the Microsoft Conference Center in Mountain View, California.

Continue reading

Concise writeup from administrator at Berkeley Lab Commons on why he chose Puppet over CFEngine

Published on 25 January 2010 by

I came across this link today describing a few reasons why James Welcher at Berkeley Lab Commons decided to use Puppet instead of CFEngine. He includes a link to an article from Luke Kanies as well as some good links for migrating from CFEngine to Puppet.

In his words, the reason he ultimately decided on Puppet hinged on its ability to handle more complex tasks:

Continue reading

Deploying Puppet in Client-Server, Standalone, and Massively Scaled Environments

Published on 12 January 2010 by

A common misconception about Puppet is that it can only be used in client/server mode. Although this is the most common use case, it is actually just one of three common deployment practices.

Client/Server model:

Client/server deployment is the most common and feature rich way to run Puppet. For any environments where multiple hosts are managed, client/server deployment is usually the way to go.

Continue reading

OSU's Lance Albertson details reasons for switching to Puppet

Published on 8 January 2010 by

Came across this link with an interview of Lance Albertson of Oregon State University's Open Source Lab talking about how they are managing their data center. Among the topics was a description of their reasons for switching from CFengine to Puppet. Here is what Lance had to say:

"OSUOSL uses Cfengine for systems management but hopes to migrate onto Puppet. What are the primary advantages of Puppet?

Continue reading

Reductive Labs Announces Puppet 0.25.2

Published on 5 January 2010 by

Reductive Labs is pleased to announce the availability of Puppet 0.25.2. The 0.25.2 release is a significant maintenance release in the 0.25.x branch and represents a significant amount of work from the Puppet community. Special thanks to everyone who contributed to the release and tested fixes – especially, but not limited to, Peter Meier (duritong), R.I.Pienaar (Volcane), Mark Plaskin, Dan Bode, Alan Harder, Ricky Zhou, Christian Hofstaedtler, Nigel Kersten, and especially Markus Roberts and Jesse Wolfe who worked around the clock to get the release out the door.

Continue reading