introduction to devops - update 2017

49
introduction to devops 2017-01-18 Gérard de Vos @gr4rd [email protected] Meetup Amsterdam Updated for 2017! ;)

Upload: gjdevos

Post on 24-Jan-2017

48 views

Category:

Internet


3 download

TRANSCRIPT

Page 1: Introduction to devops - update 2017

introduction to devops2017-01-18

Gérard de Vos @[email protected] Meetup

Amsterdam

Updated

for 2017!

;)

Page 2: Introduction to devops - update 2017

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

Page 3: Introduction to devops - update 2017

/meNow:

Previously:

Also:

Page 4: Introduction to devops - update 2017

Warning: devops is fluffy

Page 5: Introduction to devops - update 2017

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/

Page 7: Introduction to devops - update 2017
Page 8: Introduction to devops - update 2017

In 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/

It is new

Page 10: Introduction to devops - update 2017

A bit on evolution

Credit: shutterstock.com

Page 11: Introduction to devops - update 2017

http

://bl

og.g

arde

vian

ce.o

rg/2

014/

05/it

-all-

gone

-bit-

war

dley

-her

e.ht

ml

Page 12: Introduction to devops - update 2017

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

Page 14: Introduction to devops - update 2017

http

://bl

og.g

arde

vian

ce.o

rg/2

015/

10/a

gile

-vs-

lean

-vs-

six-

sigm

a.ht

ml

Page 15: Introduction to devops - update 2017

http

://w

ww

.jedi

.be/

blog

/201

2/05

/12/

codi

fyin

g-de

vops

-are

a-pr

actic

es/

Page 16: Introduction to devops - update 2017

http

://w

ww

.jedi

.be/

blog

/201

2/05

/12/

codi

fyin

g-de

vops

-are

a-pr

actic

es/

Page 17: Introduction to devops - update 2017
Page 18: Introduction to devops - update 2017

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/)

Page 19: Introduction to devops - update 2017

Culture

Page 20: Introduction to devops - update 2017
Page 23: Introduction to devops - update 2017

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

Page 24: Introduction to devops - update 2017

“Being woken up at 3am every night by your pager is certainly a powerful incentive to focus on quality when writing your code.”

Martin Fowler - Microservices

https://martinfowler.com/articles/microservices.html

Page 25: Introduction to devops - update 2017

“You built it, you run it”

- Werner VogelsCTO Amazon

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

Page 26: Introduction to devops - update 2017
Page 29: Introduction to devops - update 2017

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/

Page 30: Introduction to devops - update 2017

AutomationContinuous integration

Continuous delivery

Infrastructure as code

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

Reduce risk Increase speed Usually in that order

Page 31: Introduction to devops - update 2017
Page 32: Introduction to devops - update 2017
Page 33: Introduction to devops - update 2017

AutomationGit / VCS

Automated testing. Test driven development etc.

Deployment tooling

ChatOps

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

Page 34: Introduction to devops - update 2017

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

Toyota Production System

Kaizen. Continuous Improvement

Muda. Remove ‘waste’

Page 35: Introduction to devops - update 2017

http

s://e

n.w

ikip

edia

.org

/wik

i/Val

ue_s

tream

_map

ping

Page 36: Introduction to devops - update 2017

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/

Page 37: Introduction to devops - update 2017

MeasurementThe feedback loop

How you know what you are doing.

Page 38: Introduction to devops - update 2017

“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

Page 39: Introduction to devops - update 2017

StatsD

Page 40: Introduction to devops - update 2017

“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

Page 41: Introduction to devops - update 2017

SharingShare discoveries and lessons.

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

Page 44: Introduction to devops - update 2017

USDS

Page 45: Introduction to devops - update 2017

More

Page 46: Introduction to devops - update 2017

MoreDevops Meetup Amsterdamhttp://www.meetup.com/DevOpsAmsterdam/

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

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

Page 47: Introduction to devops - update 2017

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. No "best" practices yet you can blindly copy

(you have to) Adapt it to your organization, department, team● Be CALMS● Keep learning and improving● Share and enjoy!

Page 48: Introduction to devops - update 2017

Questions?

Page 49: Introduction to devops - update 2017

Thank you!