When you can’t move fast and break things

Feb 2014

Moses Mendoza / Engineering ManagerPuppet Labs Inc.

Finance

Military

Research

Life

Too Big To Fail.

Except the servers. The servers can fail.

Continuous deployment

!=continuously deploying puppet?

Move Fast and Break Things- former Facebook motto

Move Fast and Break Things with stable infrastructure- current Facebook motto

But… we’re agile, too.

How do we enable adoption?

● Don’t care

● Don’t ship

● Communicate

options?

PUPPET 3.0

codename “Telly”

Enter: Semver

x .y .z

28-09-12

07:48 request initiated

07:50 denied

we don’t ship on Fridays

09:50 a proposition:

Release Candidate Repos

09:51 agreement

The rubygems situation,

or, try to be consistent.

30 days of rage.

The dangerous and alluring

ensure => latest

"my biggest concern with this problem in its current state, is the potential fallout of users (and the people they influence) who now find puppet to be "too volatile" or "too unstable", and decide to look for alternatives"- Aaron Russo

https://groups.google.com/forum/#!msg/puppet-users/Q14kTSE0pvY/o33U4atSmJwJ

“people seem to be expecting the rest of the world to maintain a controlled environment simply because they don't?”- R.I. Pienaar

https://groups.google.com/forum/#!msg/puppet-users/Q14kTSE0pvY/o33U4atSmJwJ

Document expectations.

Define the terms.But don’t forget to agree on the definitions.

Extend Ownership.

Own a failure, so users don’t have to.

Recalled:puppet 3.5.0

share a version contractempathizedocument expectationsown it all the way through

test early and oftencontrol your environment

Looking forward

Questions?

Moses MendozaEngineering Manager | Puppet Labsmoses@puppetlabs.com