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

06.10.11

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]

Introduction:

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.

Conclusion:

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. Links 27/2/2017: GNU Linux-libre 4.10, Weston 2.0.0, Git 2.12.0, Linux From Scratch 8.0

    Links for the day



  2. Top Officials in French Government Are Growing Tired of Battistelli's Abuses at the European Patent Office (EPO)

    An automated translation of a recent debate about the EPO in the French government, culminating in intervention by Richard Yung



  3. A US Supreme Court (SCOTUS) Which is Hostile Towards Patent Maximalists May Closely Examine More Patents That Apple Uses Against Android

    A company which often takes pride in designers rather than developers (art, not technical merit) may lose that leverage over the competition if its questionable patents are taken away by the Supremes



  4. As Long as Software Patents Are Granted and Microsoft Equips Trolls With Them, “Azure IP Advantage” is an Attack on Free/Libre Software

    Microsoft is feeding enemies of GNU/Linux and Free/libre Open Source software (FLOSS) in order to sell its 'protection', which it names "IP Advantage" in a rather Orwellian fashion (same naming as back in the Novell days)



  5. Patent Trolls on Their Way Out in the United States and Their Way Into China, No Thanks to the Open Invention Network (OIN)

    An update on patent trolls and the role played by supposed allies of Free/libre software, who in practice do everything to exacerbate the problem rather than resolve it



  6. Insensitivity at the EPO’s Management – Part VIII: When Governed by Criminals, Truth-Tellers Are Cast as Criminals and Criminals as Justice Deliverers

    The bizarre state of affairs at the European Patent Office, where being an honest and transparent person makes one incredibly vulnerable and subjected to constant harassment from the management



  7. The Sickness of the EPO – Part V: Shedding Light on Institutional Abuse Against Ill and/or Disabled Individuals

    The seriousness of the situation at the EPO and a call for action, which requires greater transparency, even if imposed transparency



  8. The EPO's Race to the Bottom in Recruitment and Early Retirements Explained by an Insider

    The European Patent Office under Battistelli is failing to attract -- and certainly failing to retain -- talented examiners



  9. Wouter Pors and Other UPC Boosters Believe That Repeating the Lies Will Potentially Make Them Truths

    The lobbying campaign for UPC, or hopeful lies (sometimes mere rumours) disguised as "news", continues to rely on false perceptions that the UPC is just a matter of time and may actually materialise this year



  10. The Patent Trial and Appeal Board (PTAB) is Utilised in Fixing the US Patent System and the Patent Microcosm Loses Its Mind

    A roundup of PTAB news, ranging from attacks on the legitimacy of PTAB to progress which is made by PTAB, undoing decades of overpatenting



  11. The Patent Trial and Appeal Board (PTAB) and the Federal Circuit (CAFC) Take on Patents Pertaining to Business Methods

    Patents on tasks that can be performed using pen and paper (so-called 'business methods', just like algorithms) and oughtn't be patent-eligible may be the next casualty of the America Invents Act (AIA)



  12. Google's Stewardship of GNU/Linux (Android, Chromebooks and More) in Doubt After Company Resorts to Patent 'First Strikes'

    Google has just turned a little more evil, by essentially using patents as a weapon against the competition (by no means a defensive move)



  13. Links 24/2/2017: Ubuntu 17.04 Beta, OpenBSD Foundation Nets $573,000 in Donations

    Links for the day



  14. IAM, Greased up by the EPO, Continues Lobbying by Shaming Tactics for the UPC, Under the Guise of 'News'

    The shrill and well-paid writers of IAM are still at it, promoting the Unitary Patent (UPC) at every opportunity and every turn



  15. Patent Scope Gone Awry: European Vegetable Patents Office?

    In its misguided race to raise so-called 'production', the EPO lost sight of its original goals and now facilitates patent royalty payments/taxation for naturally-recurring items of nature



  16. Yes, There is Definitely Brain Drain (Experience Deficit) at the European Patent Office and Stakeholders Feel It

    The direction that the European Patent Office has taken under Battistelli undoes many decades (almost half a century) of reputation-building and progress and naturally this repels existing staff, not to mention hampers recruitment efforts



  17. The Sickness of the EPO – Part IV: Cruel Management That Deliberately Attacks the Sick and the Weak

    The dysphoric reality at the European Patent Office, which is becoming like a large cell (with bolted-down windows) where people are controlled by fear and scapegoats are selected to perpetuate this atmosphere of terror and maintain demand (or workload) for the Investigative Stasi



  18. Links 23/2/2017: Qt 5.9 Alpha, First SHA1 Collision

    Links for the day



  19. UPC Roundup: War on the Appeal Boards, British Motion Against the UPC, Fröhlinger Recalled, and Fake News About Spain

    Taking stock of some of the latest attempts to shove the Unitary Patent (UPC) down Europe's throat, courtesy of Team Battistelli and Team UPC



  20. The Sickness of the EPO – Part III: Invalidity and Suicides

    An explanation of what drives a lot of EPO veterans to depression and sometimes even suicide



  21. The Appeal Board (PTAB) and Federal Circuit (CAFC) Maintain Good Pace of Patent Elimination Where Scope Was Exceeded

    The Court of Appeals for the Federal Circuit (CAFC) continues to accept about 4 out of 5 decisions of the Patent Trial and Appeal Board (PTAB) and the US Supreme Court (SCOTUS) refuses to intervene



  22. Software Patents Are Ebbing Away, But the “Swamp” Fights Back and Hijacks the Word “Fix”

    The club of patent maximalists, or those who profit from excess prosecution and legal chaos, isn't liking what has happened in the United States and it wants everything reversed



  23. Report From Yesterday's Debate About the European Patent Office (EPO) at the Bavarian Landtag

    A report of the EPO debate which took place at the Bavarian Landtag yesterday (21/2/2017)



  24. Links 22/2/2017: Wine-Staging 2.2, Nautilus 3.24

    Links for the day



  25. French Politician Richard Yung Tells the Government About Abuses at the European Patent Office (EPO)

    The subject of EPO scandals has once again landed in French politics, just a couple of months since it last happened



  26. The Sickness of the EPO – Part II: Background Information and Insights

    With a privatised, in-house (sometimes outsourced and for-profit) force for surveillance, policing, justice, public relations and now medical assessment (mere vassals or marionettes of the management) the EPO serves to show that it has become indistinguishable from North Korea, where the Supreme Leader gets to control every single aspect (absolutely no separation of powers)



  27. EPO Cartoon/Caricature by KrewinkelKrijst

    A new rendition by Dutch cartoonist and illustrator KrewinkelKrijst



  28. Inverting Narratives: IAM 'Magazine' Paints Massive Patent Bully Microsoft (Preying on the Weak) as a Defender of the Powerless

    Selective coverage and deliberate misinterpretation of Microsoft's tactics (patent settlement under threat, disguised as "pre-installation of some of the US company’s software products") as seen in IAM almost every week these days



  29. The Sickness of the EPO – Part I: Motivation for New Series of Articles

    An introduction or prelude to a long series of upcoming posts, whose purpose is to show governance by coercion, pressure, retribution and tribalism rather than professional relationship between human beings at the European Patent Office (EPO)



  30. Insensitivity at the EPO’s Management – Part VII: EPO Hypocrisy on Cancer and Lack of Feedback to and From ECPC

    The European Cancer Patient Coalition (ECPC), which calls itself "the largest European cancer patients' umbrella organisation," fails to fulfill its duties, says a source of ours, and the EPO makes things even worse


CoPilotCo

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

CoPilotCo

Recent Posts