1. Puppet
Camp San
Francisco
2010
Luke Kanies
Founder of Puppet project
Founder and CEO of Puppet Labs

2. The state of
Puppet

3. Puppet is stable

4. Puppet
Labs is
Growing

5. Puppet is
changing quickly
• Still plenty of features to add
• Every day we learn, and every lesson brings a
refactoring
• Maturity brings its own design requirements
• Connectiveness is a larger priority

6. Puppet is
Pervasive
Web Entertainment Technology
Financial
Defense

7. The Survey
Please take a few
minutes to fill out our
http://bit.ly/ayJ0hN

8. We’re Sysadmins

9. We Love Puppet

10. We’re a mixed
and growing

11. We Update Quickly

12. We Use a lot of
Operating

13. I promised some
things last year

14. Puppet Camp
2009 Promises
•1.0
•WebGUI
•Modules

15. 2.6

16. “Web GUI”
Dashboard is
growing and
prospering

17. Let’s go Back

18. Why does Puppet
exist?

19. Embarrassment

20. Fear

21. A simple dream:
That sysadmins
could reuse code

22. Focus on the
things you care
Usually
Ideally
0 25.0 50.0 75.0 100.0
Things you have to do
Things you want to do

23. The Problem
}
• No standardization
Every • 75% of IT budgets spent
infrastructure to maintain existing
systems
starts from
• Code changes with the
scratch sysadmin

24. We needed a
high-level
language for

25. Shell scripts are
assembly code
Programmin
SysAdmin
g
Low-level,
non- Assembly perl/shell/etc
portable,
single-use
Abstract,
portable, C* Puppet
reusable
* For small values of
abstract

26. So: The ultimate
goal was code
reuse

27. We’ve built a
platform that can
enable reuse

28. Now we just need
to start sharing

29. Puppet Forge
http://forge.puppetlabs.com
http://projects.puppetlabs.com/projects/
module-site

30. Westheimer's Discovery:
A couple of months
in the laboratory can
frequently save

31. Luke’s Corollary:
A couple of months
of development can
frequently save a couple of
hours on the internet.

32. Collaborate on
existing code
rather than

33. Or, start again and
publish

34. Fills out the
product portfolio
•The industry-leading open source automation platform
Puppet •Supported with subscription
Puppet •A graphical view into your Puppet infrastructure
•A simplified interface for many configuration actions
Dashboard
•Collaborate with other IT administrators on Puppet content
Puppet Forge •Access Puppet Labs supported modules

35. The Future of
Puppet

36. Messaging
middleware is
coming

37. Centralized data
services

38. Much better CLI
tools

39. Enterprise
• Thewhole Puppet stack -
packaged and QA’d
• Less
frequent releases with
upgrade guarantees
• No extra code

40. One more
thing

41. mCollective
joins Puppet
RI Pienaar joins Puppet Labs as advisor

42. mCollective makes
Puppet better
Datacenter
Puppet
Datacenter
Puppet
Servers Servers
1 2 3 1 2 3
Message Queue Message Queue
(ActiveMQ, (ActiveMQ,
RabbitMQ) RabbitMQ)
NOC
MCollective
Puppet
Dashboard

43. mCollective adds
orchestration
Command MCollective sequences
Line Web Puppet actions based on data
Interface interface Dashboard in Puppet
(CLI)
Scenario 1 (Complete Process)
Step 1: Remove server group 3 from load balancers
Step 2: Upgrade server on group 3
Step 3.Verify monitoring status of group 3
Puppet MCollective Step 4: Put group 3 back in load balancers
Scenario 2 (Across Server Groups)
1 2 3 1 2 3 1 2 3 Step 1: Prevent Puppet runs for machines of type 5
Step 2: Restart Apache on all machines of type 2
Step 3: Update machines of type 4 in batches of 50
Datacenter Datacenter Datacenter every 2 hours
Step 4: Schedule mail delivery of type 4 in batches of
50 every 2 hours
4 5 6 4 5 6 4 5 6

44. mCollective
Roadmap
• Orchestrate Puppet runs using Dashboard classifications
Q4 2010 • View run status of Puppet clients via MCollective
• Generic interface to MCollective Agents in Puppet Dashboard
Q1 2011 •
•
Puppet REST interface integration with MCollective
Scheduled and background MCollective action invocation
• Simplified cross node dependency orchestration
Q2 2011 • MCollective support for non-Ruby agents and clients

45. Any
Question