Introduction to devops 2016

48
introduction to devops 2016-08-17 Gérard de Vos @gr4rd [email protected]

Transcript of Introduction to devops 2016

introduction to devops2016-08-17

Gérard de Vos @[email protected]

Agenda● /me● One definition of devops● Old or new? A bit of history● Another definition of devops● Where?● CALMS● Takeaways

/meNow:

Previously:

Also:

One definition of devops

“Devops is a cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.”

- Adam Jacob, CTO & founder of Chef

http://readwrite.com/2015/07/29/devops-people-not-technology/

It is newIn 2009 things came together:

● Agile infrastructure thread by Patrick Debois et al.● "10+ Deploys Per Day: Dev and Ops Cooperation at Flickr" by John Allspaw

and Paul Hammond https://www.youtube.com/watch?v=LdOe18KhtT4

● Lessons Learned blog, and later “Lean Startup” book, by Eric Ries● “Continuous Delivery” by Jez Humble and David Farley

And something called "cloud".

http://itrevolution.com/the-convergence-of-devops/

A bit on evolution

Credit: shutterstock.com

http

://bl

og.g

arde

vian

ce.o

rg/2

014/

05/it

-all-

gone

-bit-

war

dley

-her

e.ht

ml

Another definition of devops

“Devops is co-evolution of practice with the evolution of an underlying activity.”

- Simon WardleyResearcher @ Leading Edge Forum

Previously: VP Cloud at Canonical, CEO at Fotango

http://blog.gardeviance.org/2015/04/devops-weve-been-here-before-we-will-be.html

http

://bl

og.g

arde

vian

ce.o

rg/2

015/

10/a

gile

-vs-

lean

-vs-

six-

sigm

a.ht

ml

http

://w

ww

.jedi

.be/

blog

/201

2/05

/12/

codi

fyin

g-de

vops

-are

a-pr

actic

es/

http

://w

ww

.jedi

.be/

blog

/201

2/05

/12/

codi

fyin

g-de

vops

-are

a-pr

actic

es/

CALMS ● Culture● Automation● Lean● Measurement● Sharing

http://itrevolution.com/devops-culture-part-1/(https://www.chef.io/blog/2010/07/16/what-devops-means-to-me/)

Culture

Design for failure

“The best way to avoid failure is to fail constantly.”

http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html

“Waking up developers at 3am is a great feedback loop: defects get fixed very quickly”

MobBrowser case study

http://www.slideshare.net/realgenekim/devops-kanban-meet-up-32212

“You built it, you run it”

- Werner VogelsCTO Amazon

https://queue.acm.org/detail.cfm?id=1142065

Blameless (or blame-aware) post-mortems“Take a hard look at how the accident actually happened, treat the engineers involved with respect, and learn from the event.”

https://codeascraft.com/2012/05/22/blameless-postmortems/

AutomationContinuous integration

Continuous delivery

Infrastructure as code

-------------------------------+

Reduce risk Increase speed Usually in that order

AutomationGit / VCS

Automated testing. Test driven development etc.

Deployment tooling

ChatOps

These document and share the decision making process and development progress.

LeanW. Edwards Deming, Henry Ford, Taiichi Ohno et al.

Toyota Production System

Kaizen. Continuous Improvement

Muda. Remove ‘waste’

http

s://e

n.w

ikip

edia

.org

/wik

i/Val

ue_s

tream

_map

ping

http

s://g

oatc

an.d

o/20

14/0

4/04

/get

-you

r-he

ad-o

ut-o

f-you

r-aa

s/

MeasurementThe feedback loop

How you know what you are doing

“only about 1/3 of ideas improve the metrics they were designed to improve.”

Online Experimentation at Microsoft: http://ai.stanford.edu/~ronnyk/ExPThinkWeek2009Public.pdf

“The ability to learn faster than your competitors may be the only sustainable competitive advantage.”

- Arie de GeusFormer head of Shell's Strategic Planning Group

SharingShare discoveries and lessons.

Work in the open: repositories, wikis, trackers, monitors.

USDS

More

MoreDevops Meetup Amsterdam (duh)http://www.meetup.com/DevOpsAmsterdam/

Devopsdayshttp://www.devopsdays.org/Devopsdays Amsterdam will be back June 28-30 2017 :-)

Devopsweekly.org newletterhttp://www.devopsweekly.com/

In short● Devops is about people.● Devops is, also, just part of evolution.● It is not for everywhere. Most powerful in the middle.● It is not just for those with job labels of “dev” or “ops”. ● It is still young and evolving. (you have to) Adapt it to your organization,

department, team.● Keep learning and improving.● Share and enjoy!

Questions?

Thank you!