This document discusses the history of devops from 2009 to the present. It began as a movement in 2009 in Ghent to improve software delivery using open source tools and has since grown globally with over 250 events held. While tools have evolved from things like Puppet and Jenkins to Docker and Kubernetes, the core challenges of culture change, continuous delivery, monitoring, and cloud infrastructure remain. The document cautions that tools alone will not solve problems and that the industry focuses too much on hype and certification over meaningful change. The key takeaway is that after over 10 years, many organizations still struggle with devops principles due to cultural barriers, and the work of bridging development and operations is ongoing.

1. From devoops to devops,
103 years of (not) learning
Devops.barcelona November 2022
Kris Buytaert

3. 13 years of
World Domination
●
2009 Ghent
●
2010 Sydney , MountainView, Hamburg, Sao Paulo
●
2011 Boston, MountainView, Goteborg,
●
2012 Austin, Tokyo , MountainView, Rome
●
2013 London (2x) Paris, Amsterdam
●
……
●
2019 Ghent

5. A global movement to improve the
quality of software delivery leveraging
Open Source experience, started in Gent
in 2009

6. Future #devopsdays
●
250 events and counting
●
900+ organisers
●
70+ events in 2019
●
10th year aniversay
●
Other events
with #devops
track

7. Kris Buytaert
●
@krisbuytaert
●
I used to be a Dev,
●
Then Became an Op
●
CTO and Open Source Consultant @inuits.eu
●
Chief Yak Shaver @o11y.eu
●
Organiser of #devopsdays, #cfgmgmtcamp, #loadays, ….
●
CoFounder of the above
●
Everything is a freaking DNS Problem
●
Evangelizing devops
●

8. Why we study history ?
●
Because I`m a grumpy old frustrated
developer sysadmin
●
Because I`m an old opiniated guy
●
Because history repeats
●
We need to learn from our mistakes

9. The “Old” Days
●
“Put this Code Live, here's a tarball” NOW!
●
What dependencies ?
●
No machines available ?
●
What database ?
●
Security ?
●
High Availability ?
●
Scalability ?
●
My computer can't install this ?

10. Culture
Then
●
Agile, Kanban, Lean
●
Startups as examples
●
Success Stories
●
Unicorns
●
Poster Childs
Now
●
Agile, Fake Agile, Less, Safe,
●
Enterprises as examples => No
examples
●
Popular Antipatterns
●
How to include management
●
Failure
●
Burnout

11. * as code
Then
●
Cfengine, Puppet, Chef
●
Mcollective, Noah,
Rundeck
●
Hudson, Jenkins
Now
●
Bash in Yaml
●
Ansible, Rundeck, Choria,Bolt
●
Jenkins, JenkinsX GitlabCI,
CircleCI, TravisCI
– Pipeline As Code
●
kubectl apply -f …….
●
helm install …….

12. Continuous Something
Then
●
Deploying Software
●
Svn, Git
●
Git flow
●
Release Management
Now
●
Git
●
Stop Branching
●
Trunk Based
Development

13. Monitordrama
Then
●
Bloated commercial
●
Nagios
●
Cacti, Munin , RRD
●
Ganglia
●
Zenoss
●
Scaling Zabbix
●
#monitoringsucks
Now
●
Icinga
●
ELK
●
Graphite + Grafana
●
Prometheus
●
#monitoringlove
●
#observability
●
#opentracing

14. Cloudy
Then
●
Xen, KVM, openVZ, lxc
●
Vagrant
●
Linux-HA, CoroSync
●
Ceph, Gluster, DRBD,
●
EC2, OpenStack, Cloudstack,
Eucalyptus,OpenNebula,
openQRM
Now
●
Docker , Docker, Docker,
Moby, Rkt, lxc, cri-o,podman
●
Docker , Docker, Docker,
●
Mesos, Kubernetes, K8s, K3s,
Nomad
●
NFS
●
EC2, GCE, Azure, OpenStack,

15. Docker
Docker
Docker
Docker
Docker
Docker

16. Tools will not fix your
broken culture
Tooling hype is not helping

17. Kubernetes
Docker
Kubernet
es
Kubernete
s
Kube
Kubernete
s

18. Tools vs Culture

19. ●
While true ;
– We’re going to go for fancy new $tool
– We’re not going to change how we use it
– We’re going to fail
●
done

20. O11y will fix it !
●
Observability will NOT fix your broken
monitoring.
●
Prometheus will NOT fix your AlertFatigue
●
Automating it from a SSOT will !

21. This industry is
great at killing awesome
things

22. Is ITIL dead ?
●
The last mile
●
The men who say no
●
Guardians of Production
●
Friday at 10 am
●
Reducing risk upfront
●
Machines make decisions
●
Lower downtime
●
Constantly
●
Learn the Language
●
Automate the steps
●
Speed up 1000x

23. Agile is dead ?
●
Waterfall
●
Watermill
●
Jira & Standups
●
SaFe

24. Who killed #devops ?

25. We Did
●
7 tools for your devops stack
●
Puppet vs Chef vs Ansible
●
Docker , the Ultimate “Devops” Tool
●
Implement all the tools ..

26. Recruiters Killed #devops
●
It's not a job title.
●
Is it a developer ?
●
Is it an ops engineer ?
●
a system engineer writing code ?
●
a developer running operations ?

27. #devopsteam
●
It's not the team running tooling
●
It's not the team in charge of delivery
●
It's not yet another silo between devs and ops

28. There is no such thing
●
Who is certified ?
●
By who ?

29. Certification kills everything
●
ITIL => misses the goal
●
Scrum => makes it a procedure
●
Devops => the biggest scam of them all
●
For the cause of education ?
●
Devops “insert your tool here” Certifcation ?
●
Certification = Vendors milking users

32. #enterprise devops
●
“You can only change small
organisations”
●
“You can't change a large
organisation”
●
“You need to do things different“
●
There is much more to change
●
It takes longer
●
The resistance is bigger
●
“The antibodies kick in”

33. Most Large Enterprises are not even close to
#devops, #agile
Their culture is so broken they keep lying to
themselves they are
While pushing people closer to BurnOut :(

34. Pro Tip
Do not call it a
devops
transformation

35. 103 years later

36. Dev Ooops #container edition
●
“Put this Code Live, here's a Docker Image ”
●
No machines available ?
●
What database ? Where to store the data ?
●
Security ? What distro is this even ?
Bad Cows ?
●
How do we monitor his ?
●
Backups ?
●
How did you build this ?

37. What have we really learned ?

38. The rise of
●
Cargo Culting
●
YoloOps
●
Resume Driven development
●
Hype Driven development

39. “Success” Stories
●
Not always real success stories :(
●
Change Happens
●
But not company wide

40. A long Journey
●
We are nowhere close to being finished..
●
Young organisations become old
●
New people onboard
●
New technologies need to be embrace

41. Teaching people

42. Our role tomorrow today
●
Teacher
●
Student
●
Bridge Builder
●
Developer
●
Troubleshooter
●
Evangelist
●
Shrink

43. It's not about the tools
It's about change
It's about the people

44. o11y
CONTACT
Essensteenweg 31
2930 Brasschaat
info@o11y.eu
kris@o11y.eu