Dev ops overview (brief)

What’s the commotion about
Overview of what is happening in the industry
around CI/CD and DevOps
10/8/12 © Copyright 2012 Constant Contact Inc.

Are you aware of what is happening out there?
© Copyright 2013 Constant Contact Inc. 2

On the Care and Feeding of Feedback Cycles by Elisabeth Hendrickson @ FLOWCON 2013

Operations sees …
 Fragile applications are prone to
failure
 Long time required to figure out
“which bit got flipped”
 Detective control is a salesperson
 Too much time required to restore
service
 Too much firefighting and unplanned
work
 Planned project work cannot
complete
 Frustrated customers leave
 Market share goes down
 Business misses Wall Street
commitments
 Business makes even larger
promises to Wall Street
 More urgent, date-driven projects put into
the queue
 Even more fragile code put into production
 More releases have increasingly “turbulent
installs”
 Release cycles lengthen to amortize “cost
of deployments”
 Failing bigger deployments more difficult to
diagnose
 Most senior and constrained IT ops
resources have less time to fix underlying
process problems
 Ever increasing backlog of infrastructure
projects that could fix root cause and
reduce costs
 Ever increasing amount of tension
between IT Ops and Development
Dev sees …
The Downward Spiral (from Gene Kim)

These are business problems!
 Pressure on dev teams forces them to take shortcuts and
accumulate technical debt
 Attention to Automated testing is reduced and the coding is
slashed
 Assumption that QA will catch the problem - beginning of throw
over the wall
 QA is starting to run behind the schedule because the amount of
work increasing
 Dev cycle is increasing by taking time from QA
 QA is starting to fortify the wall and put processes in place
requiring strict documentation of what has changed
 Code gets into a fragile steaming hot pile that no one wants to get
close to and even touch
 Lead developer gets bored, frustrated and burned out and leaves
 Hot pile stays there forever

Devops Modelling by Patrick Debois @ YOW! 2013

What is DevOps?
http://www.devopsdays.org/blog/2010/05/16/the-panel-experiment-and-ignite-devops/

DevOps = CAMS / CLAMS / CALMS
 Culture
 Automation
 (Lean)
 Measurement
 Sharing
 Culture
 Fast feedback
 Direct connections
 Data-based communication
 Enablement, not self-protection
John Willis (the Demming of DevOps)
Inverse incentives:
• measure Ops on # of released features
• Devs on stability of their apps in production

 Measurement
 Measure everything
 Sharing
 Share information
 Share power
 Share knowledge
 Automation
 Lightweight tools,
readiness to discard or
change tools
 Open-source bias
 Automate for leverage
to change
 Embrace & adopt
“developer” tools
 SCM
 Configuration
Management

What is Continuous Delivery?
 reduce the cost, time, and risk
of delivering incremental changes to users

Lean thinking …
 Deliver fast
 Build quality in
 Optimize the whole
 Eliminate waste
 Amplify learning
 Decide late at last responsible moment
 You have the best information possible to make your
decision
 Empower team

Micro-services!

v1
v2
Ruby
Java

Canary Releasing

Data Migration
Jez Humble on Continuous Delivery @ Devops days 2010

Either you break it or our users will
Add some Chaos to the system
You Don’t Choose Chaos Monkey …
Chaos Monkey Chooses You

Histrix Circuit Breaker

Turbine Dashboard

http://www.slideshare.net/beamrider9/continuous-deployment-at-etsy-a-tale-of-two-approaches

Etsy

ChatOps @ GitHub

Books

Dev ops overview (brief)

More Related Content

What's hot

Similar to Dev ops overview (brief)

More from Igor Moochnick

Recently uploaded

Dev ops overview (brief)

Editor's Notes