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 19/2/2018: Linux 4.16 RC2, Nintendo Switch Now Full-fledged GNU/Linux

    Links for the day



  2. PTAB Continues to Invalidate a Lot of Software Patents and to Stop Patent Examiners From Issuing Them

    Erasure of software patents by the Patent Trial and Appeal Board (PTAB) carries on unabated in spite of attempts to cause controversy and disdain towards PTAB



  3. The Patent 'Industry' Likes to Mention Berkheimer and Aatrix to Give the Mere Impression of Section 101/Alice Weakness

    Contrary to what patent maximalists keep saying about Berkheimer and Aatrix (two decisions of the Federal Circuit from earlier this month, both dealing with Alice-type challenges), neither actually changed anything in any substantial way



  4. Makan Delrahim is Wrong; Patents Are a Major Antitrust Problem, Sometimes Disguised Using Trolls Somewhere Like the Eastern District of Texas

    Debates and open disagreements over the stance of the lobbyist who is the current United States Assistant Attorney General for the Antitrust Division



  5. Patent Trolls Watch: Microsoft-Connected Intellectual Ventures, Finjan, and Rumour of Technicolor-InterDigital Buyout

    Connections between various patent trolls and some patent troll statistics which have been circulated lately



  6. Software Patents Trickle in After § 101/Alice, But Courts Would Not Honour Them Anyway

    The dawn of § 101/Alice, which in principle eliminates almost every software patent, means that applicants find themselves having to utilise loopholes to fool examiners, but that's unlikely to impress judges (if they ever come to assessing these patents)



  7. In Aatrix v Green Shades the Court is Not Tolerating Software Patents But Merely Inquires/Wonders Whether the Patents at Hand Are Abstract

    Aatrix alleges patent infringement by Green Shades, but whether the patents at hand are abstract or not remains to be seen; this is not what patent maximalists claim it to be ("A Valentine for Software Patent Owners" or "valentine for patentee")



  8. An Indoctrinated Minority is Maintaining the Illusion That Patent Policy is to Blame for All or Most Problems of the United States

    The zealots who want to patent everything under the Sun and sue everyone under the Sun blame nations in the east (where the Sun rises) for all their misfortunes; this has reached somewhat ludicrous levels



  9. Berkheimer Decision is Still Being Spun by the Anti-Section 101/Alice Lobby

    12 days after Berkheimer v HP Inc. the patent maximalists continue to paint this decision as a game changer with regards to patent scope; the reality, however, is that this decision will soon be forgotten about and will have no substantial effect on either PTAB or Alice (because it's about neither of these)



  10. Academic Patent Immunity is Laughable and Academics Are Influenced by Corporate Money (for Steering Patent Agenda)

    Universities appear to have become battlegrounds in the war between practicing entities and a bunch of parasites who make a living out of litigation and patent bubbles



  11. UPC Optimism Languishes Even Among Paid UPC Propagandists Such as IAM

    Even voices which are attempting to give UPC momentum that it clearly lacks admit that things aren't looking well; the UK is not ratifying and Germany make take years to look into constitutional barriers



  12. Bejin Bieneman Props Up the Disgraced Randall Rader for Litigation Agenda

    Randall Rader keeps hanging out with the litigation 'industry' -- the very same 'industry' which he served in a closeted fashion when he was Chief Judge of the Federal Circuit (and vocal proponent of software patents, patent trolls and so on)



  13. With Stambler v Mastercard, Patent Maximalists Are Hoping to Prop Up Software Patents and Damage PTAB

    The patent 'industry' is hoping to persuade the highest US court to weaken the Patent Trial and Appeal Board (PTAB), for PTAB is making patent lawsuits a lot harder and raises the threshold for patent eligibility



  14. Apple Discovers That Its Patent Disputes Are a Losing Battle Which Only Lawyers Win (Profit From)

    By pouring a lot of money and energy into the 'litigation card' Apple lost focus and it's also losing some key cases, as its patents are simply not strong enough



  15. The Patent Microcosm Takes Berkheimer v HP Out of Context to Pretend PTAB Disregards Fact-Finding Process

    In view or in light of a recent decision (excerpt above), patent maximalists who are afraid of the Patent Trial and Appeal Board (PTAB) try to paint it as inherently unjust and uncaring for facts



  16. Microsoft Has Left RPX, But RPX Now Pays a Microsoft Patent Troll, Intellectual Ventures

    The patent/litigation arms race keeps getting a little more complicated, as the 'arms' are being passed around to new and old entities that do nothing but shake-downs



  17. UPC Has Done Nothing for Europe Except Destruction of the EPO and Imminent Layoffs Due to Lack of Applications and Lowered Value of European Patents

    The Unified Patent Court (UPC) is merely a distant dream or a fantasy for litigators; to everyone else the UPC lobby has done nothing but damage, including potentially irreparable damage to the European Patent Office, which is declining very sharply



  18. Links 17/2/2018: Mesa 17.3.4, Wine 3.2, Go 1.10

    Links for the day



  19. Patent Trolls Are Thwarted by Judges, But Patent Lawyers View Them as a 'Business' Opportunity

    Patent lawyers are salivating over the idea that trolls may be coming to their state/s; owing to courts and the Patent Trial and Appeal Board (PTAB) other trolls' software patents get invalidated



  20. Microsoft's Patent Moves: Dominion Harbor, Intellectual Ventures, Intellectual Discovery, NEC and Uber

    A look at some of the latest moves and twists, as patents change hands and there are still signs of Microsoft's 'hidden hand'



  21. Links 15/2/2018: GNOME 3.28 Beta, Rust 1.24

    Links for the day



  22. Bavarian State Parliament Has Upcoming Debate About Issues Which Can Thwart UPC for Good

    An upcoming debate about Battistelli's attacks on the EPO Boards of Appeal will open an old can of worms, which serves to show why UPC is a non-starter



  23. The EPO is Being Destroyed and There's Nothing Left to Replace It Except National Patent Offices

    It looks like Battistelli is setting up the European Patent Office (EPO) for mass layoffs; in fact, it looks as though he is so certain that the UPC will materialise that he obsesses over "validation" for mass litigation worldwide, departing from a "model office" that used to lead the world in terms of patent quality and workers' welfare/conditions



  24. IBM is Getting Desperate and Now Suing Microsoft Over Lost Staff, Not Just Suing Everyone Using Patents

    IBM's policy when it comes to patents, not to mention its alignment with patent extremists, gives room for thought if not deep concern; the company rapidly becomes more and more like a troll



  25. In Microsoft's Lawsuit Against Corel the Only Winner is the Lawyers

    The outcome of the old Microsoft v Corel lawsuit reaffirms a trend; companies with deep pockets harass their competitors, knowing that the legal bills are more cumbersome to the defendants; there's a similar example today in Cisco v Arista Networks



  26. The Latest Lies About Unitary Patent (UPC) and the EPO

    Lobbying defies facts; we are once again seeing some easily-debunked talking points from those who stand to benefit from the UPC and mass litigation



  27. Speech Deficit and No Freedom of Association at the EPO

    True information cannot be disseminated at the EPO and justice too is beyond elusive; this poses a threat to the EPO's future, not only to its already-damaged reputation



  28. No, Britain is Not Ratifying 'Unitary' Anything, But Team UPC Insinuates It Will (Desperate Effort to Affect Tomorrow's Outcome)

    Contrary to several misleading headlines from Bristows (in its blog and others'), the UPC isn't happening and isn't coming to the UK; it all amounts to lobbying (by setting false expectations)



  29. The EPO's Paid Promotion of Software Patents Gets Patent Maximalists All Excited and Emboldened

    The software patents advocacy from Battistelli (and his cohorts) isn't just a spit in the face of European Parliament but also the EPC; but patent scope seems to no longer exist or matter under his watch, as all he cares about is granting as many patents as possible, irrespective of real quality/legitimacy/merit



  30. Andrei Iancu Begins His USPTO Career While Former USPTO Director (and Now Paid Lobbyist) Keeps Meddling in Office Affairs

    The USPTO, which is supposed to be a government branch (loosely speaking) is being lobbied by former officials, who are now being paid by private corporations to help influence and shape policies; this damages the image of the Office and harms its independence from corporate influence


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