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. Team UPC is Interjecting Itself Into the Media Ahead of Tomorrow's Lobbying Push Against the European Council and Against European Interests

    A quick look at the growing bulk of UPC lobbying (by the legal firms which stand to benefit from it) ahead of tomorrow's European Council meeting which is expected to discuss a unitary patent system



  2. IP Kat is Lobbying Heavily for the UPC, Courtesy of Team UPC

    When does an IP (or patent) blog become little more than an aggregation of interest groups and self-serving patent law firms, whose agenda overlaps that of Team Battistelli?



  3. Leaked: Conclusions of the Secretive EPO Board 28 Meeting (8th of September 2016)

    The agenda and outcome of the secretive meeting of the Board of the Administrative Council of the EPO



  4. Letter From the Dutch Institute of Patent Attorneys (Nederlandse Orde van Octrooigemachtigden) to the Administrative Council of the EPO

    The Netherlands Institute of Patent Attorneys, a group representing a large number of Dutch patent practitioners, is against Benoît Battistelli and his horrible behaviour at the European Patent Office (EPO)



  5. EPO's Board 28 Notes Battistelli's “Three Current Investigations/Disciplinary Proceedings Involving SUEPO Members in The Hague."

    The attack on SUEPO (EPO staff representatives) at The Hague appears to have been silently expanded to a third person, showing an obvious increase in Battistelli's attacks on truth-tellers



  6. Links 28/9/2016: Alpine Linux 3.4.4, Endless OS 3.0

    Links for the day



  7. Cementing Autocracy: The European Patent Office Against Democracy, Against Media, and Against the Rule of Law

    The European Patent Office (EPO) actively undermines democracy in Europe, it undermines the freedom of the press (by paying it for puff pieces), and it undermines the rule of law by giving one single tyrant total power in Eponia and immunity from outside Eponia (even when he breaks his own rules)



  8. Links 28/9/2016: New Red Hat Offices, Fedora 25 'Frozen'

    Links for the day



  9. Team Battistelli Intensifies the Attack on the Boards of Appeal Again

    The lawless state of the EPO, where the rule of law is basically reducible to Battistelli's ego and insecurities, is again demonstrated with an escalation and perhaps another fake 'trial' in the making (after guilt repeatedly fails to be established)



  10. After the EPO Paid the Financial Times to Produce Propaganda the Newspaper Continues to Produce UPC Puff Pieces, Just Ahead of EU Council Meeting

    How the media, including the Financial Times, has been used (and even paid!) by the EPO in exchange for self-serving (to the EPO) messages and articles



  11. Beware the Patent Law Firms Insinuating That Software Patents Are Back Because of McRO

    By repeatedly claiming (and then generalising) that CAFC accepted a software patent the patent microcosm (meta-industry) hopes to convince us that we should continue to pursue software patents in the US, i.e. pay them a lot more money for something of little/no value



  12. The US Supreme Court Might Soon Tighten Patent Scope in the United States Even Further, the USPTO Produces Patent Maximalism Propaganda

    A struggle brewing between the patent 'industry' (profiting from irrational saturation) and the highest US court, as well as the Government Accountability Office (GAO)



  13. Patent Trolling a Growing Problem in East Asia (Software Patents Also), Whereas in the US the Problem Goes Away Along With Software Patents

    A look at two contrasting stories, one in Asia where patent litigation and hype are on the rise (same in Europe due to the EPO) and another in the US where a lot of patents face growing uncertainty and a high invalidation rate



  14. The EPO's Continued Push for Software Patents, Marginalisation of Appeals (Reassessment), and Deviation From the EPC

    A roundup of new developments at the EPO, where things further exacerbate and patent quality continues its downward spiral



  15. The Battistelli Effect: “We Will be Gradually Forced to File Our Patent Applications Outside the EPO in the Interests of Our Clients”

    While the EPO dusts off old files and grants in haste without quality control (won't be sustainable for more than a couple more years) the applicants are moving away as trust in the EPO erodes rapidly and profoundly



  16. Links 27/9/2016: Lenovo Layoffs, OPNFV Third Software Release

    Links for the day



  17. The Moral Depravity of the European Patent Office Under Battistelli

    The European Patent Office (EPO) comes under heavy criticism from its very own employees, who also seem to recognise that lobbying for the UPC is a very bad idea which discredits the European Patent Organisation



  18. Links 26/9/2016: Linux 4.8 RC8, SuperTux 0.5

    Links for the day



  19. What Insiders Are Saying About the Sad State of the European Patent Office (EPO)

    Anonymous claims made by people who are intimately familiar with the European Patent Office (from the inside) shed light on how bad things have become



  20. The EPO Does Not Want Skilled (and 'Expensive') Staff, Layoffs a Growing Concern

    A somewhat pessimistic look (albeit increasingly realistic look) at the European Patent Office, where unions are under fire for raising legitimate concerns about the direction taken by the management since a largely French team was put in charge



  21. Patents Roundup: Accenture Software Patents, Patent Troll Against Apple, Willful Infringements, and Apple Against a Software Patent

    A quick look at various new articles of interest (about software patents) and what can be deduced from them, especially now that software patents are the primary barrier to Free/Libre Open Source software adoption



  22. Software Patents Propped Up by Patent Law Firms That Are Lying, Further Assisted by Rogue Elements Like David Kappos and Randall Rader (Revolving Doors)

    The sheer dishonesty of the patent microcosm (seeking to bring back software patents by misleading the public) and those who are helping this microcosm change the system from the inside, owing to intimate connections from their dubious days inside government



  23. Links 25/9/2016: Linux 4.7.5, 4.4.22; LXQt 0.11

    Links for the day



  24. Patent Quality and Patent Scope the Unspeakable Taboo at the EPO, as Both Are Guillotined by Benoît Battistelli for the Sake of Money

    The gradual destruction of the European Patent Office (EPO), which was once unanimously regarded as the world's best, by a neo-liberal autocrat from France, Benoît Battistelli



  25. Bristows LLP's Hatred/Disdain of UK/EU Democracy Demonstrated; Says “Not Only Will the Pressure for UK Ratification of the UPC Agreement Continue, But a Decision is Wanted Within Weeks.”

    Without even consulting the British public or the European public (both of whom would be severely harmed by the UPC), the flag bearers of the UPC continue to bamboozle and then pressure politicians, public servants and nontechnical representatives



  26. Released Late on a Friday, EPO Social 'Study' (Battistelli-Commissioned Propaganda) Attempts to Blame Staff for Everything

    The longstanding propaganda campaign (framing staff as happy or framing unhappy staff as a disgruntled minority) is out and the timing of the release is suspicious to say the least



  27. Links 23/9/2016: Latest Microsoft and Lenovo Spin (Now in ‘Damage Control’ Mode)

    Links for the day



  28. White Male-Dominated EPO Management Sinks to New Lows, Again

    Benoît Battistelli continues to make the EPO look like Europe's biggest laughing stock by attempting to tackle issues with corny photo ops rather than real change (like SUEPO recognition, diverse hiring, improved patent quality, and cessation of sheer abuses)



  29. Journalism 102: Do Not Become Like 'Managing IP' or IAM 'Magazine' (the Megaphones of the EPO’s Management)

    Another look at convergence between media and the EPO, which is spending virtually millions of Euros literally buying the media and ensuring that the EPO's abuses are scarcely covered (if ever mentioned at all)



  30. Journalism 101: Do Not Believe Anything That Benoît Battistelli and the EPO's Management Say (Also Don't Fall for the UPC Hype)

    A survey/review (or an overview) of recent articles about the EPO and why they're wrong (mostly because they parrot the official lies from Battistelli's department)


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