10. .
LLeett''ss ttaakkee aa cclloosseerr llooookk
• Devs do sysadmin work
▶ Testing
▶ Database work
▶ Small deployments
• Ops do development work
▶ Bash, python scripting
▶ Infrastructure as Code
▶ Monitoring
11. .
IITT iiss eevvoollvviinngg
YYoouu nneeeedd ttoo ppllaayy tthhee ggaammee
• More velocity
• More changes
• Volatile environments
• Scalability
• No space for slow moves
• No space for old teams
12. .
WWhhaatt iiss DDeevvOOppss??
DevOps is getting Developers
and Ops working together!
13. .
DDeevvOOppss ddaayyss
• 200X-2009: World. Patrick Debois, Gildas Le Nadan,
Andrew Clay Shafer, Kris Buytaert, Jezz Humble, Lindsay
Holmwood, John Willis, Chris Read, Julian Simpson, Luke
Kanies, John Allspaw and lots of others…
• 2009: Ghent
• 2014: Ghent
• Dozens of others (Paris in 2013 and 2015)
14. .
DDeevvOOppss ddaayyss
• Talks in the morning
• Open-Space in the afternoon
• Some big companies have organized
internal DevOps days
15. .
DevOps is a cultural and
professional movement
Adam Jacob, OpsCode
22. .
.
Enable communication
CC-BY 3.0 http://commons.wikimedia.org/wiki/File:Fiap-paulista-coworking.jpg
23. .
CCoommmmuunniiccaattiioonn
• Sit together
• Mix open space and offices
• Standup (virtual, physical)
• Mails, mailing lists, chat
• Direct communication
• One language to rule them all
24. .
BBuuiilldd TTrruusstt
• Experiment
• Measure success
• Measure failure
• Automate the things
• Trust between people
25. .
.
Play together
CC-BY-SA 3.0 http://www.flickr.com/photos/kona99/3987853510/
26. .
PPllaayy ttooggeetthheerr
• More idea, creativity
• Different approaches
• More fun and comprehension
• Build trust
31. .
AAuuttoommaattee aallll tthhee tthhiinnggss
• Reproducable build
• Robust build
▶ Build on a prod-like environment
▶ No more "works on my machine"
• Test
• Deploy
32. .
You need to get more confident with
your code
36. .
CCoonnttiinnuuoouuss IInntteeggrraattiioonn
• Everyone works in one branch
• Run tests on the code
• Make a build each time
• Deploy each build to a development
environment
• Run tests on that environments
38. .
CCoonnttiinnuuoouuss DDeelliivveerryy
• A fresh build is always ready to be deployed
• The code is always in a good state
• Features flag
• Human action is needed to deploy
39. .
CCoonnttiinnuuoouuss DDeeppllooyymmeenntt
• Same as Continuous delivery… but
• Code is automatically deployed
• 0 downtime
• Silent upgrades
• No human intervention
• Requires mature testing infrastructure
44. .
IIAACC
• Infrastructure as Code
• Put infrastructure under version control
• History, amend, modelize your infra
• Deploy monitoring, backups, apps
• This is NOT bash scripting
• Deploy new platforms at will
• Think puppet, chef, …
45. .
YYoouurr iinnffrraa ccooddee iiss……ccooddee
• Puppet/Chef/…code must be deployed
• Use CI/CD for them also
• Run tests on them
• Use the same path
46. .
OOrrcchheessttrraattiioonn
• Restart all httpd
• Which servers have php 53 installed?
• Configure db, trigger commands..
• On multiple server at the same time
• Think mcollective, ansible, …
55. .
RReeaaddmmeettrriiccss
• Get business keys, values
• Share dashboards with dev ops mgmt
• Find metrics that matter
• Expose them
• Learn from them
56. .
UUsseemmeettrriiccss
• Analyze them
• Prevent expectable failure
• Correlate failures
• Root cause analysis