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. The EFF Back to Tackling Software Patents, Not Just Patent Trolls

    Electronic Frontier Foundation lawyers start targeting large companies that exploit patents for intimidation and extortion, not just patent trolling



  2. Microsoft Wants to Devour the Competition (Linux), Devour People's Data

    Refuting the "new Microsoft" propaganda and some ludicrous concept that Microsoft is now "playing nice"



  3. Benoît Battistelli Thinks 'President' is Above the Law, Decides to Ignore the Court's Ruling

    Staff of the EPO is given yet more reasons to protest tomorrow at the British Consulate, for the so-called 'President' of the EPO reminds everyone of the very raison d'être for the protest -- a vain disregard for the rule of law



  4. Links 24/2/2015: Xfce 4.12 a Week Away, GNOME 3.16 Previewed

    Links for the day



  5. Links 23/2/2015: Ubuntu Kylin 14.04.2 LTS, Cinnamon 2.6 Previews

    Links for the day



  6. IRC Proceedings: February 8th - February 21st, 2015





  7. The EPO's Sham 'Internal Investigation' of EPO Vice-President Željko Topić's Affairs

    The EPO never investigated the Željko Topić affair, it only pretends to have investigated (one small aspect, i.e. cherry-picking) using a Benoît Battistelli-controlled group



  8. Links 21/2/2015: GNOME 3.15.90, Google Wins Android Lawsuit

    Links for the day



  9. Microsoft AstroTurfing War on GNU/Linux is Still Going On, But Hidden Better, Uses API as Instrument of Lock-in

    The corruptible press continues to describe blatant attacks (Embrace, Extend, Extinguish) against GNU/Linux and Free software as Microsoft 'embracing' Open Source



  10. Lenovo's Superfish Scandal is Spyware on Top of Spyware (Microsoft Windows), the Problem is Inherently Proprietary Software

    Shifting focus to the root problem, which is neither Lenovo nor its laptops but the non-free programs installed on hardware



  11. Benoît Battistelli Once Again Threatens EPO Staff That 'Dares' to Protest, Battistelli Exploits Terror Attacks to Pretend to Respect Free Speech

    The European Patent Office (EPO) President, Benoît Battistelli, reportedly started threatening -- as before -- staff that decides to exercise the right to assemble and protest against abuses, including the abuses of President Battistelli himself



  12. Links 20/2/2015: Android Studio v1.1, GDB 7.9

    Links for the day



  13. Links 20/2/2015: Bloomberg Joins Linux Foundation, ClearOS Community 6.6.0

    Links for the day



  14. The Chartered Institute of Patent Attorneys Slams the European Patent Office for Structural Failings

    An important letter which we overlooked while writing yesterday's 4 articles about the European Patent Office (EPO); yet another key stakeholder complains



  15. Links 19/2/2015: Hewlett-Packard on Cumulus Linux, Previews of GNOME 3.16 Beta

    Links for the day



  16. Techrights Under Attack Again, Shortly After Important EPO Articles

    Techrights highlights a pattern that is months old; Site faces availability issues shortly after reports about the European Patent Office and its abuses



  17. EPO Staff Protests Against Benoît Battistelli’s Lowering of Patents Quality (Scope Expansion and Software Patents for Profit)

    A protest in Munich in less than 6 days will target Mr. Sean Dennehey, who has helped Battistelli cover up his abuses and crush legitimate critics, whom he deemed illegal opposition as if the EPO is an authoritarian regime as opposed to a public service which taxpayers are reluctantly (but forcibly) funding



  18. Breaking: European Patent Office Sued by Its Own Staff in The Hague, Must Unblock Staff's Voices

    The crooked management of the European Patent Office (EPO) gets in legal trouble after repeated attempts to cover up abuses and suppress criticism



  19. Željko Topić's History in SIPO Leaves a Legacy of Alleged DZIV Vehicles (Bribes), Authorship Abuses, and Intimidation Against Reporters

    Another deep look at Željko Topić's background in Croatia, preceding his very notorious appointment to the EPO where he now serves as Benoît Battistelli's most controversial attack dog



  20. The Old Obsession With Patent Trolls Continues to Distract From Debate About Software Patenting

    A roundup of recent coverage about monopolies on algorithms in the United States



  21. Links 19/2/2015: 64-bit ARM Linux, Chinese New Year

    Links for the day



  22. Links 18/2/2015: Linux Report, FlightGear 3.4

    Links for the day



  23. EPO Scandals: The Story So Far

    An overview of articles about mischief, misconduct and breach of laws at the EPO



  24. Links 17/2/2015: TripleO, Pivotal

    Links for the day



  25. Links 17/2/2015: SystemD 219, Frugalware 2.0 (Rigel) Released

    Links for the day



  26. Željko Peratović Slammed for Whitewashing Željko Topić After Publishing Important Piece on Behalf of Key Sources

    Response from Ivan Kabalin to Zeljko Peratovic's so-called "apology" which is both mysterious and seemingly inadequate as it does nothing to actually explain what was wrong (if anything)



  27. Benoît Battistelli Has Made Oversight of European Patent Office Absolutely Impossible





  28. Microsoft Already Killed Nokia, Don't Let It Kill Android Players Too

    Microsoft's strategy against Android mirrors the company's evil strategy that derailed MeeGo and Nokia



  29. Intel Continues to Attack Software Freedom Through UEFI

    The Trojan horse that Microsoft uses to cement its monopoly on desktops and laptops (making it hard or impossible to install and run GNU/Linux) is also being misused to block Coreboot



  30. Links 16/2/2015: Netrunner 15, Bridge Linux

    Links for the day


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