DevOps is much more than tooling and technical details, it’s first and foremost a cultural and operational shift. This deck was given at www.devopscon.com, and covers some of the principles and best practices preached for by devops thought leaders such as John Allspaw, Jesse Robbins, Adrian Cockroft, Jez Humble and others.

2. Some
Background

3. A Few
Definition
Attempts

4. “stresses
communication &
collaboration ...
aims to help an
organization rapidly
produce software
products and
services”

5. “The DevOps
movement was
born of the need to
improve IT service
delivery agility... “

6. “Some of that is
tools ... A big part of
that is culture”
Jesse Robbins,
OpsCode

7. “Help me define it…”
Adrian
Cockroft, Netflix

9. It’s about shipping
better software,
So… What Is faster & more
It about? consistently
• Where traditional dev
and ops roles fail to
deliver

10. Learn by example, not invent
(yet) another definition…

11. Jesse’s Dev & Ops as Teams
Taxonomy (Culture & Processes)
(I know, this can also
start a flame war…)
Infrastructure as Code
Application as Services

13. Accountability • sdf
http://www.slideshare.net/jezhumble/scaling-devops

14. Devs own their
code, so they
expect 24x7
contact with it
Trust &
Responsibility
Allspaw’s Take

15. When things
break, dev and
ops both
participate
Trust &
Responsibility
Allspaw’s Take

16. Post mortems
have dev and ops
remediations
Trust &
Responsibility
Allspaw’s Take

17. “Everyone who has
changes going out
is accounted for and
is actively testing
and supporting
their changes”
Chuck Rossi,
Facebook

19. Definition of Done
http://www.slideshare.net/jesserobbins/hacking-culture-at-velocityconf

20. “Done means
released”
Jez Humble

21. Measure
“If it moves, graph
Everything it. If it matters, alert
on it”
Allspaw

22. Not Just
Infrastructure
• Measure infra, app
and business KPIs
• Don’t just measure,
correlate

23. http://www.slideshare.net/jallspaw/dev-and-ops-collaboration-and-awareness-at-etsy-and-flickr

24. Paint the Walls
http://www.slideshare.net/realgenekim/2012-velocity-london-devops-patterns-distilled

25. “Ship early,
ship often”
• Small increments
• Undeployed code is
lost value
Chuck Rossi,
Facebook

26. http://www.slideshare.net/jallspaw/ops-metametrics-the-currency-you-pay-for-change

27. http://www.slideshare.net/jallspaw/ops-metametrics-the-currency-you-pay-for-change

28. http://www.slideshare.net/jallspaw/ops-metametrics-the-currency-you-pay-for-change

29. http://www.slideshare.net/jallspaw/ops-metametrics-the-currency-you-pay-for-change

30. 11.6 seconds
Mean time between deployments
1079
Max number of deployments / hour
10,000
Mean number of hosts simultaneously
receiving a deployment
Source: John Jenkins

32. Well Defined • Canary tests
Rollout • Red/Black
Mechanism Deployment
• Dark launches

33. http://www.slideshare.net/bitfield/agile-sysadmin-and-the-art-of-infrastructure-automation-2493286

38. A Self-
Service Data
Center Really
Helps
(Even more so if
it has an API..)

39. • Infrastructure as
The Common product, app devs
to All the as customers
– Netflix calls it NoOps,
Above but it pisses of Allspaw

41. • Small services
with APIs
– Easier to ship, easier to
debug, easier to
manage at large scale
– Caveat: forward and
backward compatibility
– @adrianco’s “anti-
fragility”

42. • We assume
commodity HW,
Resiliency in
Cloud
the Software
• So we have to
Stack
build reliability
into our code

43. Feature Flips
http://www.flickr.com/photos/maxabxarata/535048895/

45. “Everything is
Built for 3”
Jeremy Edberg,
Netflix

46. Circuit Breakers (Netflix)

47. Fire Drills &
Monkeys…

48. What’s Next?
– Not everyone is
Amazon & Netflix
– The next challenge is
to make this
accessible to all