1st conference 2015 devops
TRANSCRIPT
what if...what your devops practices say about
organisational maturity
lies of omission!
“Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.”to production
HOW?!?“Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.”
missing pieces of the puzzle
agilehow do
we build
“it”?
lean*what “it”
should we
build?
devopswe’ve built
“it”...
now what?
devops -?
2014 State of DevOps report
30xmore frequent
deployments8000x
faster lead times
than peers
high functioning devops in the wild
low hanging fruit
deployment focus
@ scale
low hanging fruitwhat your practices (can) say about you
you build it, you fix it
“we found that when you woke up developers
at 2am, defects got fixed faster than ever”
???
you build it, you fix it
“we found that when you woke up developers
at 2am, defects got fixed faster than ever”
share ownership
“Backend services typically have two so-called
System Owners - one from Dev and one from
Ops.”
???
share ownership
Backend services typically have two so-called
System Owners - one from Dev and one from
Ops.
???
celebrate deployments
???
celebrate deployments
no more snowflakes
“remove (login) access to all deployed systems”
???
no more snowflakes
“remove (login) access to all deployed systems”
deployment focus
what your practices (can) say about you
use short release cycles
“... we have one hard and fast rule for new
Engineers on their first day: deploy to
production”
???
use short release cycles
“... we have one hard and fast rule for new
Engineers on their first day: deploy to
production”
separate deployment from release
“right now ... there is already the code [in
production] for every major thing [we’re] going
to launch in the next six months and beyond!”
???
separate deployment from release
“right now ... there is already the code for every
major thing [we’re] going to launch in the next
six months and beyond!”
separate deployment from release
“Feature toggles should be a first-class part of
your stories. One team … builds feature bits
into their stories such that the first task they
perform when they play a story is to add the
feature bit for that story.”
???
separate deployment from release
“Feature toggles should be a first-class part of
your stories. One team … builds feature bits
into their stories such that the first task they
perform when they play a story is to add the
feature bit for that story.”
@ scale
what your practices (can) say about you
embrace continuous deployment
“In 2011, [we] were doing a maximum of 1,079
deployments”
???
embrace continuous deployment
“In 2011, [we] were doing a maximum of 1,079
deployments
PER HOUR.”
???
embrace continuous deployment
“In 2011, [we] were doing a maximum of 1,079
deployments
PER HOUR.”
integrate continuously...
“... engineers have built a powerful continuous
integration system running 60 million tests per
day”
???
integrate continuously...
“... engineers have built a powerful continuous
integration system running 60 million tests per
day”
“Over the last year Chaos Monkey has
terminated over 65,000 instances running in
our production and testing environments. Most
of the time nobody notices”
architect for network failure
???
“Over the last year Chaos Monkey has
terminated over 65,000 instances running in
our production and testing environments. Most
of the time nobody notices”
architect for network failure
Conclusion
Conclusion
REFERENCE
S
http://bit.ly/1C3S0DZ
http://etsy.me/1FEyyex
http://bit.ly/1v70LcY
http://bit.ly/198ccb4
http://bit.ly/1hqFE9d
2014 State of DevOps report
http://bit.ly/1Hte2id
http://tcrn.ch/1AZIaMe
http://nflx.it/1ia88X4
http://bit.ly/1AcOLUB
http://bit.ly/1E2vztN
Andy Marks
@andee_marks
“we should optimise for the time it takes us to deliver valuable software to
users”
