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. Alice Continues to Smash Software Patents So Patent Lawyers, Monopolists' Lobbyists Etc. Now Attack the Supreme Court for Doing This

    Corporate lobbyists and patent lawyers are trying to put Alice in the grave, for its impact on software patents is very profound and thus far almost unstoppable



  2. How to Salvage the EPO's Reputation: Create More Boards of Appeal in Europe and Abolish the Misguided UPC Fantasy

    A critical evaluation of what goes on at the European Patent Office (EPO), which is quickly descending down (and overall degrading) to the level of Chinese systems, along with the corruption, the abuses, and the low quality of patents



  3. Court of Appeals for the Federal Circuit (CAFC) Has Just Sided With Patent Trolls

    The notorious CAFC, which manifested software patents in the United States, has just given a gift to patent trolls that typically use software patents for extortion down in Texas



  4. Analyses of the Latest Data From Lex Machina About Patent Litigation Show Some Litigation Declines

    Professor Mark Lemley's Lex Machina highlights litigation trends by collecting and analysing data related to patents and pertaining to intellectual monopolies in general; now it shows litigation droughts



  5. India is Having Another Taste of the Dangers of Western Patents, Must Learn to Reject Software Patents in the Face of Great Pressure

    The growing software giant which is India continues to face cruel and aggressive lobbying from the West, enabling the West to control India by patents that should not exist in the first place



  6. Links 29/4/2016: GNOME 3.21.1, Fairphone

    Links for the day



  7. Microsoft Says It Will Continue to Extort Companies That Distribute Linux, Using Software Patents As Usual

    Microsoft's war on Linux, a war which is waged using software patents (for revenue and/or for coercion in bundling deals), is still going on in spite of all the PR tactics from Microsoft and its paid partners



  8. Australia Might be Next to Block Software Patents If Commission's Advice is Followed

    Australian advice against software patents, which can hopefully influence Australian politicians and put an end, once and for all, to all software patents in Australia



  9. [ES] ''Si la Forma de Pensar de la EPO fuese Seguida, Guantánamo Sería Posible en Suelo Alemán.”

    La EPO está todavía bajo fuego, pero mucho de ello pasa detrás de las cortinas y envuelve abogados y/o burócratas



  10. The European Copy-Paste Office (EPO)

    This morning's example (not the first) of how the EPO uses 'social' media



  11. Links 28/4/2016: Fedora 24, EE Goes Open Source

    Links for the day



  12. Amid Referendum “the New European Unitary Patent System is Likely to Collapse Before It Started”

    The Unitary Patent Court (UPC) vision seems like it may be just one month away from its gradual death, depending on British voices amongst other key factors



  13. USTR is Trying to Shame and Bully India Into Introducing Software Patents in India

    Lobbying body of the US (corporations-led) is trying its usual dirty tactics against India's sound policy which excludes software/algorithms from patent scope



  14. No, Visual Studio is NOT Open Source and Xamarin Openwashing is NOT News

    The latest example of Microsoft openwashing, courtesy of confidants of Microsoft and those who got bamboozled by them



  15. Latest Black Duck Puff Pieces a Good Example of Bad Journalism and How Not to Report

    Why the latest "Future of Open Source Survey" -- much like its predecessors -- isn't really a survey but just another churnalism opportunity for the Microsoft-connected Black Duck, which is a proprietary parasite inside the FOSS community



  16. If EPO “Form of Thinking Were to be Followed, Guantanamo on German Soil Would be Possible.”

    The EPO is still under fire, but a lot of it happens behind the scenes and involves lawyers and/or bureaucrats



  17. Links 28/4/2016: Tomb Raider for GNU/Linux, Proxmox VE 4.2

    Links for the day



  18. [ES] La Departura de la Readidad de la EPO Y Su Entrada en la Esféra Industrial China de Propaganda

    La deceptiva trampa del maximálism de patentes, donde se asume que artficialmente aumentando el número de patentes otorgadas traerá el resultado esperado



  19. [ES] Una Fársa de Sistema: ¿Cómo la SIPO, USPTO, y cada vez más la EPO se Convierten en Llenado de Patentes (No Se Requiere Propia Examinación)

    Una crítica al decline en la calidad de patentes en algunas de las más grandes oficinas de patentes del mundo, donde aspiración parece ser neo-liberal en el sentido económico



  20. [ES] Microsoft ‘Asalto con Todo’ Contra Android, Java, y GNU/Linux, Usando la Clásica E.E.E. Táctica de Nuevo

    Otro recordatorio de la realidad que Microsoft está muy activo en el frente E.E.E., not no sólo contra GNU/Linux pero también Android y Java



  21. [ES] Más Rumores y Llamadas Acerca de Prospectos de Microsoft Vaya a Comprar Canonical (Ubuntu con todo y Zapatos)

    Teniendo en cuenta los últimos movimientos de Canonical, algunos expertos piensan que es posible que Shuttleworth elija el dinero a Microsoft sobre principios sino también inste para que esto ocurra



  22. Links 27/4/2016: A Lot About OpenStack, Vivaldi 1.1 Released

    Links for the day



  23. A Farce of a System: How SIPO, USPTO, and Increasingly the EPO Too Turn Into Filing Systems (No Proper Examination/Filtering Required)

    A critique of the declining quality of patents in some of the world's biggest patent offices, where the aspiration seems to be neo-liberal in the economic sense



  24. Microsoft's 'Full Assault' on Android, Java, and GNU/Linux, Using Classic E.E.E. Tactics Again

    Another reminder of the fact that Microsoft is very active on the E.E.E. front, not just against GNU/Linux but also Android and Java



  25. More Rumours and Calls Surrounding Prospects of Microsoft Buying Canonical (Ubuntu and More)

    Taking some of Canonical's recent moves into account, some pundits not only think it's possible for Shuttleworth to choose Microsoft money over principles but also urge for this to happen



  26. [ES] El Nuevo Impulso Finánciado por Microsoft Para Reforzar las Patentes de Software en los EE.UU., Apoyado por los Sospechosos Usuales (La Sagrada Familia) Mientras que Microsoft Cada Vez Más Lucha Como Compañíá Productiva

    Una mirada al esfuérzo de trae una resurgencia de las patentes de software en los Estados Unidos (con un clarísimo rol de Microsoft en él) y la fundación/conf ianza de Microsoften las patentes de software como arma contr Linux/Android porque las ganancias de Windows se están secando y el Windows Phone está al borde del colápso



  27. Links 26/4/2016: Firefox 46.0, Thunderbird's Stewardship

    Links for the day



  28. Links 25/4/2016: Kodi 16.1, OpenStack Summit

    Links for the day



  29. New Microsoft-Funded Push to Make Software Patents Stronger in the US, Backed by the Usual Suspects as Microsoft Increasingly Struggles as a Producing Company

    A look at the effort to bring about a software patents resurgence to the US (with clear Microsoft role in it) and Microsoft's reliance on software patents as a weapon against Linux/Android because Windows profits dry up and Windows Phone is on the verge of collapse



  30. Patents Roundup: Marijuana Patents, Patent Satellites, Patent Trolls, Wars, and Merchants (Notably Lawyers)

    Various strands of news about patents, focused on issues raised in the latter half of last week


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