EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS


Q&A With Puppet Labs’ James Turnbull Regarding Pro Puppet

Posted in Free/Libre Software, Interview at 12:39 am by Dr. Roy Schestowitz

[As ODF | As PDF]


As someone who deals with Puppet quite a lot at work, I had the great pleasure of speaking to longtime open source pundit James Turnbull, who recently co-authored his latest book “Pro Puppet” through Apress Media with colleague Jeffrey McCune of Puppet Labs. This is his fifth technical book about open source software. “Pro Puppet” is an in-depth book about how to install, use, and develop Puppet, the popular open source systems management platform used by organizations including Twitter, Rackspace, Digg, Genentech and more.

Q&A with James Turnbull

1. What in your estimation is the number of servers (including virtual instances) that run Puppet at any level of capacity?

A: This is a question that I ponder every few months. Our largest installation is around 50,000 nodes and we have several more at the 25,000 to 50,000 node range. Given the size of the community, I think we’ve quite easily reached the million plus node mark.

“Given the size of the community, I think we’ve quite easily reached the million plus node mark.”
      –James Turnbull
2. Throughout your work on the book, have you had a chance to
measure/survey the operating systems on which Puppet is deployed? Have you any insight regarding the distribution of usage?

A: Puppet Labs did a survey earlier in the year and gathered some data about usage. Based on that and interactions with the community I think we can pretty comfortably say that our core operating systems are Linux-based with Red Hat (and derivatives) and Ubuntu/Debian being the biggest platforms. The next largest block is Solaris with a smaller number of OSX, *BSD, HP UX and pSeries/AIX systems also being represented.

3. There is a common perception that Free/Open Source software suffers from deficient documentation and lack of support (despite this being the business model of many companies). How do you challenge these types of allegations?

A: This is a common perception that regularly makes me laugh. I usually respond that all software has deficient documentation and lacks support! It’s true some open source tools lack documentation but others, for example MySQL, have exemplary documentation. Some open source software communities are hard to get help from and others fall over themselves to help people out. I’m always immensely proud of how the Puppet community, which is largely made up of some of the busiest people in IT – sysadmins, goes out of its way to help newcomers and share knowledge.

Of course this same problem is present across enterprise and commercial software. Otherwise authors wouldn’t be able to sell books offering insights into using commercial software. :) It’s even perhaps somewhat worse for enterprise software where submitting a bug request can lack transparency and where examples of how others have solved issues can be hard to find or perceived as proprietary information.

4. How can your book address or assist a crowd of people with no prior knowledge of UNIX/Linux and how can it assist those who are familiar with everything but Puppet?

A: Pro Puppet is aimed at users with some Linux/Unix knowledge, albeit at a fairly basic level — a few friends and I created an earlier book called Pro Linux System Administration designed to teach someone with zero Linux knowledge how to be a Linux sysadmin. Pro Puppet is aimed at junior and mid-level sysadmins looking to get started with Puppet and take them through to advanced topics like scaling and extending Puppet.

5. What impact do you foresee the licensing changes from the GPL to the Apache licence as having?

A: Both the GPL and Apache licenses are free and open source licenses and we’re very much staying true to our open source roots. However where we are with Puppet now we need a license that people, for whatever reasons, consider easier to integrate with. In the open source world that license is Apache and we’re already starting to see Puppet being used heavily as an integrated tools in Cloud and Infrastructure/Platform as a service (IAAS, PAAS) offerings as a result.

6. Manual operators of Puppet seem to rely mostly on the initial setup. What proportion of the work would you say a Puppet expert needs to invest in setting up the software compared to the overall lifetime of a box and its operation?

A: With Puppet, the large proportion of the work you need to do to get started is up front. Once you’ve done that work setting up new boxes becomes a routine and easy task. Maintaining and managing them is also fast and simple. Indeed, one of the benefits of Puppet is that not only do you get fast and automated setup, but you can make sure they stay the way you configured them for as long as you need. That ability to stem the tide of configuration drift and limit the potential for human error and entropy causing issues is an enormous timesaver.

7. What is the most eccentric/fascinating/uncommon use of Puppet that you have come across?

A: One that fascinated me recently is the Deutsche Flugsicherung, the German air traffic control network, who use Puppet to ensure all the operator workstations and tower servers are up to date. They have a very strict and structured work flow and an interesting deployment model where any configuration drift is anathema. I also find Air Traffic Control really interesting (I’m a geek it’s true) so it was pretty exciting to see Puppet being used in such an interesting arena.

8. Puppet functionality lags behind in platforms such as Windows. What would you advise organisations that choose to run it on this platform?

A: We’re actively working on Microsoft Windows support but we’re not there yet. What we’d love to see is people telling us what they need. I’m not primarily a Windows guy so I actually don’t know what the pain points are for Windows sysadmins. If a few of them could tell us “If you automated these 4, 5, 10 things that would make my job easier!” then that would help us structure that future support.

9. How does Puppet compare to its proprietary counterparts?

A: I think the key difference is time to value or as I prefer “how long before I’m doing something useful”. Often when you install one of the larger proprietary tools it can take significant time and people to deliver value or to get things done. We find people can download Puppet, install it and be doing something useful in a matter of minutes or an hour rather than months.

“One of the new features in Puppet 2.6.0 though was a Ruby DSL for Puppet. This allows any developer (and sysadmins too) to write their Puppet manifests in Ruby.”
      –James Turnbull
10. If one receives proper training or learns from your book, how would the difficulty of using Puppet compare to the difficulty of using other products that are out in the market?

A: I think Puppet is pretty easy to use (but I’m also biased!). It does have rough edges and things that are hard to get your head around though. One thing I think we do really well in the book is build on knowledge. You can start simple and grow into the more complex topics. I think having that sort of resource makes it really easy for people to learn how to use Puppet. The other resource I’m really excited about is a new section in the documentation called Learning Puppet (http://docs.puppetlabs.com/learning/) that offers a similar “grow into using it” experience.

I think as a result of having the book plus documentation and training available that makes Puppet a lot less difficult to understand than some of the alternatives out there.

11. How would you say the Puppet learning curve compares if a programmer and non-programmer were both faced with the task of learning it?

A: I recently came to the conclusion that I now spend more time cutting code than I do being a sysadmin which is a big change in my life. As a result I’ve been thinking about how both groups approach learning and problems. I think for a lot of sysadmins Puppet is very easy to engage with. Puppet’s language is a logical extension for people use to dealing with configuration files and scripts.

For developers that’s perhaps not as natural a progression and some have struggled in the past with learning Puppet. One of the new features in Puppet 2.6.0 though was a Ruby DSL for Puppet. This allows any developer (and sysadmins too) to write their Puppet manifests in Ruby. This approach is something that may make more sense and make it easier for developers to learn Puppet.

As a result of this Ruby interface (which we cover in the book too) I think the learning curve for both non-developers and developers is rapidly approaching parity.


We would like to thank James for being available for this interchange of insights and we hope his literature will spread Puppet to more and more companies, aiding the spread of Free/open source in systems management. Puppet sure helps the company that I work for.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New

  1. How the EPO Twisted Defamation Law in a Failed Bid to Silence Techrights

    Using external legal firms (not the EPO's own lawyers), the EPO has been trying -- and failing -- to silence prominent critics

  2. East Texas and Its Cautionary Tale: Software Patents Lead to Patent Trolls

    Lessons from US media, which focuses on the dire situation in Texas courts, and how these relate to the practice of granting patents on software (the patent trolls' favourite weapon)

  3. The Latest EPO Spin: Staff Protesters Compared to 'Anti-Patent Campaigners' or 'Against UPC'

    Attempts to characterise legitimate complaints about the EPO's management as just an effort to derail the patent office itself, or even the patent system (spin courtesy of EPO and its media friends at IAM)

  4. The Serious Implication of Controversial FTI Consulting Contract: Every Press Article About EPO Could Have Been Paid for by EPO

    With nearly one million dollars dedicated in just one single year to reputation laundering, one can imagine that a lot of media coverage won't be objective, or just be synthetic EPO promotion, seeded by the EPO or its peripheral PR agents

  5. EPO: We Have Always Been at War With Europe (or Europeans)

    The European Patent Office (EPO) with its dubious attacks on free speech inside Europe further unveiled for the European public to see (as well as the international community, which oughtn't show any respect to the EPO, a de facto tyranny at the heart of Europe)

  6. What Everyone Needs to Know About the EPO's New War on Journalism

    A detailed list of facts or observations regarding the EPO's newfound love for censorship, even imposed on outside entities, including bloggers (part one of several to come)

  7. EPO Did Not Want to Take Down One Techrights Article, It Wanted to Take Down Many Articles Using Intimidation, SLAPPing, and Psychological Manipulation Late on a Friday Night

    Recalling the dirty tactics by which the European Patent Office sought to remove criticism of its dirty secret deals with large corporations, for whom it made available and was increasingly offering preferential treatment

  8. The European Private Office: What Was Once a Public Service is Now Crony Capitalism With Private Contractors

    The increasing privatisation of the European Patent Office (EPO), resembling what happens in the UK to the NHS, shows that the real goal is to crush the quality of the service and instead serve a bunch of rich and powerful interests, in defiance of the original goals of this well-funded (by taxpayers) organisation

  9. Microsoft Once Again Disregards People's Settings and Abuses Them, Again Pretends It's Just an Accident

    A conceited corporation, Microsoft, shows not only that it exploits its botnet to forcibly download massive binaries without consent but also that it vainly overrides people's privacy settings to spy on these people, sometimes with help from malicious hardware vendors such as Dell or Lenovo

  10. When the EPO Liaised With Capone (Literally) to Silence Bloggers, Delete Articles

    A dissection of the EPO's current media strategy, which involves not only funneling money into the media but also actively silencing opposing views

  11. Blogger Who Wrote About the EPO's Abuses Retires

    Bloggers' independent rebuttal capability against a media apparatus that is deep in the EPO's pocket is greatly diminished as Jeremy Phillips suddenly retires

  12. Leaked: EPO Award of €880,000 “in Order to Address the Media Presence of the EPO” (Reputation Laundering)

    The European Patent Office, a public body, wastes extravagant amounts of money on public relations (for 'damage control', like FIFA's) in an effort to undermine critics, not only among staff (internally) but also among the media (externally)

  13. Links 27/11/2015: KDE Plasma 5.5 Plans, Oracle Linux 7.2

    Links for the day

  14. Documents Needed: Contract or Information About EPO PR/Media Campaign to Mislead the World

    Rumour that the EPO spends almost as much as a million US dollars “with some selected press agencies to refurbish the image of the EPO”

  15. Guest Post: The EPO, EPC, Unitary Patent and the Money Issue

    Remarks on the Unitary Patent (UP) and the lesser-known aspects of the EPO and EPC, where the “real issue is money, about which very little is discussed in public...”

  16. Saving the Integrity of the European Patent Office (EPO)

    Some timely perspective on what's needed at the European Patent Office, which was detabilised by 'virtue' of making tyrants its official figureheads

  17. A Call for Bloggers and Journalists: Did EPO Intimidate and Threaten You Too? Please Speak Out.

    An effort to discover just how many people out there have been subjected to censorship and/or self-censorship by EPO aggression against the media

  18. European Patent Office (EPO) a “Kingdom Above the EU Countries, a Tyranny With ZERO Accountability”

    Criticism of the EPO's thuggish behaviour and endless efforts to crush dissenting voices by all means available, even when these means are in clear violation of international or European laws

  19. Links 26/11/2015: The $5 Raspberry Pi Zero, Running Sans Systemd Gets Hard

    Links for the day

  20. EPO Management Needs to Finally Recognise That It Itself is the Issue, Not the Staff or the Unions

    A showing of dissent even from the representatives whom the EPO tightly controls and why the latest union-busting goes a lot further than most people realise

  21. Even the EPO Central Staff Committee is Unhappy With EPO Management

    The questions asked by the Central Staff Committee shared for the public to see that not only a single union is concerned about the management's behaviour

  22. The Broken Window Economics of Patent Trolls Are Already Coming to Europe

    The plague which is widely known as patent trolls (non-practicing entities that prey on practicing companies) is being spread to Europe, owing in part to misguided policies and patent maximalists

  23. Debunking the EPO's Latest Marketing Nonsense From Les Échos and More on Benoît Battistelli's Nastygram to French Politician

    Our detailed remarks about French brainwash from the EPO's media partner (with Benoît Battistelli extensively quoted) and the concerns increasingly raised by French politicians, who urge for national or even continental intervention

  24. The Sun King Delusion: The Views of Techrights Are Just a Mirror of EPO Staff Unions

    Tackling some emerging spin we have seen coming from Battistelli's private letters -- spin which strives to project the views of Techrights onto staff unions and why it's very hypocritical a form of spin

  25. Links 25/11/2015: Webconverger 33.1, Netrunner 17 Released

    Links for the day

  26. United They Stand: FFPE-EPO Supports Suspended Staff Representatives From SUEPO

    An obscure union from the Dutch side of things at the EPO is expressing support for the suspended colleagues from SUEPO (more German than Dutch)

  27. Censoring WIPR Article About Censorship by EPO

    A testament to how terrified journalists have become when it comes to EPO coverage, to the point of deleting entire paragraphs

  28. Censorship at the EPO Escalates: Now We Have Threats to Sue Publishers

    Having already blocked Techrights, the EPO's management proceeds to further suppressions of speech, impeding its staff's access to independently-distributed information (neither ordinary staff nor management)

  29. Response to Bogus Accusations That EPO Staff Protests Are Really an Attempt to Derail UPC

    Common myths about staff protests in the European Patent Office (EPO) debunked, with some additional background and general perspective on recent events, the unitary patent (UPC) and so on

  30. New Heise Article Makes It Clear That 'Nazi'-Themed Accusations Against the Suspended Board Judge Were Insufficiently Substantiated

    The personal attacks on a judge who was illegally suspended (a so-called 'house ban') increasingly look like the management's own campaign of defamation, mostly intended to marginalise and punish a judge who spoke about serious charges against VP4 (Željko Topić)


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time


Recent Posts