From devoops to devops, 103 years of (not) learning
•
0 likes•11 views
13 years ago we had the idea to organise a conference in Gent to bridge the gap between developers and the people running their code. It was the start of a new global movement. We never predicted that #devops would be where #devops is today. The word devops has evolved, the community has evolved. Over the years the word devops lost it’s meaning, at least it’s original meaning. The real challenge for the next decade will be to see how we can revive those original values and ideas, if at all… Can we fix Devops? This talk will give you some Ideas about that.
Recommended
Recommended
More Related Content
Similar to From devoops to devops, 103 years of (not) learning
Similar to From devoops to devops, 103 years of (not) learning (20)
Recently uploaded
Recently uploaded (20)
From devoops to devops, 103 years of (not) learning
- 1. From devoops to devops, 103 years of (not) learning Kris Buytaert @krisbuytaert
- 3. @krisbuytaert 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. @krisbuytaert 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. @krisbuytaert Kris Buytaert ● I used to be a Dev, ● Then Became an Op ● CTO and Open Source Consultant @inuits.eu ● Chief Yak Shaver @o11y.eu ● Everything is a freaking DNS Problem ● Evangelizing devops ● Organiser of #devopsdays, #cfgmgmtcamp, #loadays, #deliveryconf ? ….
- 8. @krisbuytaert 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. @krisbuytaert 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. @krisbuytaert 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. @krisbuytaert * 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. @krisbuytaert Continuous Something Then ● Deploying Software ● Svn, Git ● Git flow ● Release Management Now ● Git ● Stop Branching ● Trunk Based Development
- 13. @krisbuytaert Monitordrama Then ● Bloated commercial ● Nagios ● Cacti, Munin , RRD ● Ganglia ● Zenoss ● Scaling Zabbix ● #monitoringsucks Now ● Icinga ● ELK ● Graphite + Grafana ● Prometheus ● #monitoringlove ● #observability ● #opentracing
- 14. @krisbuytaert 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,
- 16. @krisbuytaert Tools will not fix your broken culture Tooling hype is not helping
- 19. @krisbuytaert This industry is great at killing awesome things
- 20. @krisbuytaert 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
- 21. @krisbuytaert Agile is dead ? ● Waterfall ● Watermill ● Jira & Standups ● SaFe
- 23. @krisbuytaert We Did ● 7 tools for your devops stack ● Puppet vs Chef vs Ansible ● Docker , the Ultimate “Devops” Tool ● Implement all the tools ..
- 24. @krisbuytaert 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 ?
- 25. @krisbuytaert #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
- 26. @krisbuytaert There is no such thing ● Who is certified ? ● By who ?
- 27. @krisbuytaert 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 ● You can’t standardise it either !!
- 28. @krisbuytaert
- 29. @krisbuytaert 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 :(
- 31. @krisbuytaert 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 ?
- 32. @krisbuytaert What have we really learned ?
- 33. @krisbuytaert The rise of ● Cargo Culting ● YoloOps ● Resume Driven development ● Hype Driven development
- 34. “Success” Stories ● Not always real success stories :( ● Change Happens ● But not company wide
- 35. @krisbuytaert A long Journey ● We are nowhere close to being finished.. ● Young organisations become old ● New people onboard ● New technologies need to be embrace
- 37. @krisbuytaert Our role tomorrow today ● Teacher ● Student ● Bridge Builder ● Developer ● Troubleshooter ● Evangelist ● Shrink
- 38. @krisbuytaert It's not about the tools It's about change It's about the people
- 39. @krisbuytaert Contact Inuits Inuits Essensteenweg 31 Essensteenweg 31 Brasschaat Brasschaat Belgium Belgium 891.514.231 891.514.231 +32 475 961221 +32 475 961221 Kris Buytaert Kris.Buytaert@inuits.eu Kris Buytaert Kris.Buytaert@inuits.eu Further Reading Further Reading @krisbuytaert @krisbuytaert http://www.krisbuytaert.be/blog/ http://www.krisbuytaert.be/blog/ https://inuits.eu/ https://inuits.eu/