Devops is a cultural and professional movement focused on building and operating high-velocity organizations. It brings together development and operations teams and processes in order to break down silos and allow for continuous delivery of updates and improvements. While the concept and practices of devops have evolved in recent years, elements of the approach have existed for some time, such as automating infrastructure and deployments. Successful devops implementation focuses on establishing a collaborative culture, automating processes, taking a lean approach, implementing measurements, and promoting sharing of knowledge.

1. introduction to devops
2017-01-18
Gérard de Vos
@gr4rd
gjdevos@gmail.com Meetup
Amsterdam
Updated
for 2017!
;)

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

3. /me
Now:
Previously:
Also:

4. Warning: devops is fluffy

5. 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/

6. It is not new

8. 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

9. http://www.devopsdays.org/events/2009-ghent/

10. A bit on evolution
Credit: shutterstock.com

11. http://blog.gardeviance.org/2014/05/it-all-gone-bit-wardley-here.html

12. Another definition of devops
“Devops is co-evolution of practice
with the evolution of an underlying activity.”
- Simon Wardley
Researcher @ 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

13. https://twitter.com/swardley/status/717167176386482176
http://blog.gardeviance.org/2015/04/devops-weve-been-here-before
-we-will-be.html

14. http://blog.gardeviance.org/2015/10/agile-vs-lean-vs-six-sigma.html

15. http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/

16. http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/

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

19. Culture

21. https://twitter.com/sethwalker/status/523161292920872960

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

23. 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

24. “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

25. “You built it, you run it”
- Werner Vogels
CTO Amazon
https://queue.acm.org/detail.cfm?id=1142065

27. http://www.slideshare.net/adriancockcroft/when-developers-operate-and-operators-develop

28. https://dl.dropboxusercontent.com/u/1018963/Articles/SpotifyScaling.pdf
http://nomad8.com/wp-content/uploads/2014/02/Squads-Chapters-Guilds-in-one-page.graffle.pdf

29. 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/

30. Automation
Continuous integration
Continuous delivery
Infrastructure as code
-------------------------------+
Reduce risk
Increase speed
Usually in that order

33. Automation
Git / VCS
Automated testing. Test driven development etc.
Deployment tooling
ChatOps
These document and share the decision making process and development
progress.

34. Lean
W. Edwards Deming, Henry Ford, Taiichi Ohno et al.
Toyota Production System
Kaizen. Continuous Improvement
Muda. Remove ‘waste’

35. https://en.wikipedia.org/wiki/Value_stream_mapping

36. https://goatcan.do/2014/04/04/get-your-head-out-of-your-aas/

37. Measurement
The feedback loop
How you know what you are doing.

38. “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

39. StatsD

40. “The ability to learn faster than your competitors may be the only sustainable
competitive advantage.”
- Arie de Geus
Former head of Shell's Strategic Planning Group

41. Sharing
Share discoveries and lessons.
Work in the open:
repositories, wikis,
trackers, chatrooms,
dashboards, monitors.

42. http://www.slideshare.net/KrisBuytaert/velocity2013-mh

43. GDS
https://www.gov.uk/government/organisations/government-digital-service/about
https://github.com/alphagov

44. USDS

45. More

46. More
Devops Meetup Amsterdam
http://www.meetup.com/DevOpsAmsterdam/
Devopsdays
http://www.devopsdays.org/
Devopsdays Amsterdam will be back June 28-30 2017 :-)
Devopsweekly.org newletter
http://www.devopsweekly.com/

47. 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!

48. Questions?

49. Thank you!