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.
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
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
31.
32. Well Defined • Canary tests
Rollout • Red/Black
Mechanism Deployment
• Dark launches
39. • Infrastructure as
The Common product, app devs
to All the as customers
– Netflix calls it NoOps,
Above but it pisses of Allspaw
40.
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
48. What’s Next?
– Not everyone is
Amazon & Netflix
– The next challenge is
to make this
accessible to all
Notes de l'éditeur
Motivation, what you won’t find in this talk
Devops as teamsShared metrics Incident mgmtService owners on call CI / CD Game day Infra as code: Full stack automation Commodity HW Reliability in SW stack Data center APIs Core infra services: infra as product, app as customer Application as services: Service orientation Versioned APIs SW resiliency (design for failures) DB storage abstraction Complexity pushed up the stack Deep instrumentation
In amazon every dev runs her own code
Push karma
Ben talked about it, it’s everyone’s responsibility, including devs
Ben mentioned Mark Ibericogithub – undeployed code is lost value
Change is a cause for instability
Which will allow you to test and rollback changes if needed
Roll your own tools - Etsy
Talk a bit about the netflix stack – bakery, simian army, asgard
Imuutable servers
infra as product, app as customer (netflix calls it noops, which pisses of allspaw)
Devs thinking about ops
Facebook – gatekeeper, wix, etsyCaveat: code can get messy, need to clean up dead code paths methodically