Puppet blog

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:

We are happy to make a new case study available from Los Alamos National Laboratory.

Calling the Puppet community.

CloudTweaks.com posted an article today that identified Puppet as one of the top 11 open source resources for cloud computing. The article originally appeared in GigaOM.

Puppet was specifically named because of Puppet's strength in managing large numbers of machines and virtual machines:

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.

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?

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.

Puppet is included in a list of open source software being employed by larger businesses.

Gigaom's list includes Puppet as a top resource.

The audio for the February Developer Call has been posted.  Thanks to Juri Rischel Jensen for cleaning up the audio once again.

You can also subscribe to the podcast.