Keynote Puppet Camp San Francisco 2010

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

The state of Puppet

Puppet is stable

Puppet Labs is Growing

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

Puppet is Pervasive Web Entertainment Technology Financial Defense

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

We’re Sysadmins

We Love Puppet

We’re a mixed and growing

We Update Quickly

We Use a lot of Operating

I promised some things last year

Puppet Camp 2009 Promises •1.0 •WebGUI •Modules

“Web GUI” Dashboard is growing and prospering

Let’s go Back

Why does Puppet exist?

Embarrassment

A simple dream: That sysadmins could reuse code

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

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

We needed a high-level language for

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

So: The ultimate goal was code reuse

We’ve built a platform that can enable reuse

Now we just need to start sharing

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

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

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

Collaborate on existing code rather than

Or, start again and publish

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 simpliﬁed interface for many conﬁguration actions Dashboard •Collaborate with other IT administrators on Puppet content Puppet Forge •Access Puppet Labs supported modules

The Future of Puppet

Messaging middleware is coming

Centralized data services

Much better CLI tools

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

One more thing

mCollective joins Puppet RI Pienaar joins Puppet Labs as advisor

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

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

mCollective Roadmap • Orchestrate Puppet runs using Dashboard classiﬁcations 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 • Simpliﬁed cross node dependency orchestration Q2 2011 • MCollective support for non-Ruby agents and clients

Any Question

Keynote Puppet Camp San Francisco 2010

by Puppet Labs on Oct 13, 2010

Accessibility

Upload Details

Usage Rights

1 Embed 55

Statistics

Keynote Puppet Camp San Francisco 2010 Presentation Transcript