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 EPO is Collapsing. Attacks on Journalists, Interns as Staff, Patents on Plants, and Bureaucratic Red Tape...

    A look at some of the latest issues surrounding the European Patent Office, whose insistence on denying the problems and instead attacking those who bring up legitimate concerns, will spell its doom



  2. Ignore the Bristows UPC Echo Chamber, the UPC is Not Happening

    Response to some of the latest UPC promotion, courtesy of some of the usual suspects, who stand to benefit financially if the UPC ever becomes a reality



  3. British Media Slams Battistelli for Attempting to Cover Up 2 Years of Juridical Abuses With Help From the Administrative Council of the EPO

    A growing voice of concern about the integrity of the European Patent Organisation, whose management appears to be in cahoots (overseers/regulators included) so as to cover up its own serious abuses



  4. Boards of Appeal Still Under Attack From Team Battistelli While the EPO Proceeds to Granting Patents on Carlsberg BEER!

    The lunacy of the EPO with its patent maximalism will likely go unchecked (and uncorrected) if Battistelli gets his way and turns the EPO into another SIPO (Croatian in the human rights sense and Chinese in the quality sense)



  5. Memo “Deliberately Leaked to Cover up the UPC” With Its Many Associated Issues Amid Brexit

    Some eye-opening updates about the awkward move from Lucy Neville-Rolfe, who made promises (expression of intent) she can neither fulfill nor justify to the British public



  6. Links 8/12/2016: Korora GNU/Linux 25, SparkyLinux 4.5.1

    Links for the day



  7. Links 7/12/2016: ROSA Desktop Fresh R8 Plasma 5, Ubuntu Touch OTA-14

    Links for the day



  8. The UPC Scam Part VII: A Fine Mess in the Making, as Nothing Can be Made of It Amid/After Brexit

    The final part in this multi-part series about UPC, which cannot be implemented in the UK as long as Brexit is on the agenda



  9. The UPC Scam Part VI: The Real Story Which People Missed Due to Puff Pieces Seeded by Battistelli-Bribed Media is That UPC Technically Cannot Come to the UK

    Another long installment in a multi-part series about UPC at times of post-truth Battistelli-led EPO, which pays the media to repeat the lies and pretend that the UPC is inevitable so as to compel politicians to welcome it regardless of desirability and practicability



  10. EPO Spiraling Down the Drain as Experienced Examiners and Judges Are Seemingly Being Replaced by Interns

    Implementing yet more of his terrible ideas and so-called 'reforms', Battistelli seems to be racing to the bottom of everything (patent quality, staff experience, labour rights, working conditions, access to justice etc.)



  11. A Lot of News From the Supreme Court (SCOTUS) Today, With Some Important Decisions on Patents Coming Soon

    A roundup of today's outcomes from the US Supreme Court, which intends to review and decide on important patent cases



  12. In Historic Blow to Design Patents, Apple Loses to Samsung at the Supreme Court

    A $399 million judgment against Android devices from Samsung, with potential implications for other Android OEMs, is rejected by SCOTUS



  13. Good Riddance. Ray Niro is Dead.

    The infamous father of patent trolling is dead, so we need to remember his real legacy rather than rewrite his history to appease his rich relatives (enriched by destroying real companies)



  14. EPO Suicides Greater in Number Than is Widely Reported, Unjust System a Contributor to These

    The horrible regime of Benoît Battistelli has an enormous human toll (fatalities), far greater than the Office is willing to publicly acknowledge



  15. Lobbying Disguised as 'Reporting' by the Patent Microcosm, Which Wants More Patents and More Lawsuits (Lawyers Needed)

    A rebuttal to some new articles about patents, especially those that strive to increase patent-related activities (usually for personal gain)



  16. USPTO Echo Chamber That Lacks Actual Software Professionals Deciding on Patentability of Software

    A look at yesterday's "Roundtable on Patent Subject Matter Eligibility," which lacked involvement from those actually affected by patents rather than those who sell, trade, and exploit these



  17. More Examples of Microsoft and Its Patent Trolls Taxing Linux, Even After Microsoft 'Joined' (Paid) the Linux Foundation

    A quick look at the past week's news and clues about Microsoft's (and its broad army of patent trolls) strategy for taxing Linux, or imposing bundling at zero cost (to Microsoft)



  18. Heiko Maas, the SPD “Cash for Access” Affair, and Suspicions of Unwarranted Censorship at IP Kat (Again)

    Unsayable views or just a glitch? Readers of IP Kat express concern about a culture of censorship at IP Kat



  19. Endgame for Battistelli at the European Patent Office (EPO)

    Battistelli turns bad into worse by spitting on the very notion of accepting justice (from the highest court in The Hague or even the UN in this case)



  20. Les Échos Chamber: Having Corrupted the Media (With EPO Money), Battistelli Now Uses It for More UPC Propaganda

    The lies about the Unitary Patent are now being broadcast (Battistelli given the platform) by the publication that Battistelli pays



  21. Rumour: EPO in Berlin the Next Casualty of Battistelli's 'Reform' (Organisational Suicide Plan)

    Months after we learned that a former staff representative in Berlin had been dismissed we come across an anonymous claim that Berlin's 'branch' of the EPO will be folded onto Munich's



  22. Caricature: the Maas App

    The failure of Maas to even bother with regulation of Battistelli (among others) earns him this cartoon



  23. Links 5/12/2016: Linux 4.9 RC 8, DeepMind as FOSS

    Links for the day



  24. Leaked: Battistelli Acknowledges Bunk 'Justice' in About 100 Cases at the Internal Appeals Committee of the EPO

    A look at Battistelli's response to the latest from the International Labour Organisation (ILO), exceptionally delivering two decisions at the very end of last month



  25. The UPC Scam Part V: Unitary Patent Regime a Fantasy of Patent Trolls

    "Good for trolls" is a good way to sum up the Unitary Patent, which would give litigators plenty of business (defendants and plaintiffs, plus commissions on high claims of damages) if it ever became a reality



  26. EPO at a Tipping Point: Battistelli Quarrelling With French Politicians, Administrative Council Urged to Act, Staff Unrest Peaking

    The latest messages about Battistelli's regime at the EPO, which faces growing opposition from more directions than ever before



  27. Quality of Patents at the EPO Dependent on the Appeal Boards When Battistelli Assesses Performance Using the Wrong 'Production' Yardstick

    A look at some recent articles regarding patent quality in the US and in Europe, in particular because of growing trouble at today's EPO, which marginalises the appeal boards



  28. Microsoft's Push for Software Patents Another Reminder That There is No 'New' Microsoft

    Microsoft's continued fascination with and participation in the effort to undermine Alice so as to make software patents, which the company uses to blackmail GNU/Linux vendors, widely acceptable and applicable again



  29. Links 5/12/2016: SparkyLinux 4.5 Released, Kondik Exits Cyanogen (Destroyed After Microsoft Deal)

    Links for the day



  30. Software Patents Continue Their Invalidation Process, But Patent Law Firms Try to Deny This in Order to Attract Misinformed (or Poorly-Informed) Clients

    A roundup of news about software patents and demonstration of the sheer bias in the media, which is mostly controlled or steered by the patent microcosm rather than actual inventors


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