Intro to DevOps

Talk presented at RUG::B Berlin

Transcript

1. Intro to DevOps: Why? What?
2. Greg Karékinian @gkarekinian Software developer Infrastructure developer Cofounder
3. TL;DR It’s not about dev It’s not about ops It’s about the customer & the product running in production
4. Why?
5. Agile, Lean, Kanban, etc.
6. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
7. Cross-functional teams: Devs, testers, UI/UX Designers, business experts...
8. Deliver value to your customers by iterating and incrementing.
11. 2/4 weeks 1 day Working product Iteration Increment
12. What about production?
15. Devs Testers Designers Business Experts Ops Production servers
16. Devs Testers Designers Business Experts Ops Production servers Sends message on pager when stuff breaks Delivers changes that work on their machine
19. If it hurts, do it often.
20. “Us VS Them” mentality
21. https://twitter.com/oising/status/298464920717099009
26. Devs Change & deliver often Ops Keep the production servers available, stable & cost-efficent “Us VS Them” mentality
27. Devs “The ops built a shitty platform.” Ops “The devs wrote shitty code.” “Us VS Them” mentality
28. We say we want to respond to change, but change is still scary.
29. Cross-functional teams: Devs, testers, UI/UX Designers, business experts...
30. Cross-functional teams: Devs, testers, UI/UX Designers, business experts... We forgot the ops.
31. Optimize the whole value chain, not just silos.
32. A bit of history
33. Flickr, 2009 John Allspaw @ Velocity Conference: 10 deploys a day Collaboration betweens Devs & Ops.
34. First DevOps Days Ghent, 2009
35. Amazon, May 2012 11.6 seconds mean time between deployments 1,079 max number of deployments in a single hour 10,000 average number of hosts simultaneously receiving a deployment ~0.001% deployments actually causing an outage
36. How often do you deploy to production?
37. How often do you deploy to production? Remember, it’s not a contest.
38. What?
39. DevOps: A culture
41. Rap is something you do Hip Hop is something you live — KRS-One
43. Cross-functional teams: Devs, testers, UI/UX Designers, business experts, Ops...
44. Remove silos Build bridges
45. Share knowledge, experience & responsability
46. Ship working software that delivers business value, with confidence.
47. Ship working software that makes users happy, with confidence.
48. Find your constraints & bottlenecks and come up with solutions.
49. DevOps is NOT just a buzzword
50. “DevOp” is NOT a job title
51. DevOps is NOT just about cool new tools
52. “There will be many charlatans in the next few years proclaiming their Devops product or Devops features. However, you know the true followers when they start talking about the Devops culture first and then their tool as a second-class citizen behind people and process.” — John Willis in 2010 http://www.opscode.com/blog/2010/07/16/what-devops-means-to-me/
53. DevOps is NOT renaming your Ops Team to DevOps team
54. DevOps is NOT giving root access to everyone
55. DevOps is NOT forcing your sysadmins to write application code
56. DevOps is NOT forcing your developers to rack servers
57. DevOps is NOT a process to follow
58. DevOps is NOT a manifesto
59. DevOps is NOT a certification
60. https://twitter.com/kbsingh/status/309666143369564160
61. DevOps is NOT something you can buy as a product
62. DevOps is NOT something you become after 2 days of training
63. DevOps is NOT pushing to production on Thursday instead of Friday but still pray
64. DevOps is NOT pushing to production hundreds of times a day just because you heard Amazon does it
65. “He's our DevOps guy.”
66. “The rest of us don’t care about production.”
67. “He's our guy who writes tests.”
68. “We just write code and pray.”
69. “He's our guy who uses version control.”
70. “The rest of us just share TAR archives and files by email.”
72. DevOps can be sysadmins & devs pairing
73. DevOps can be sysadmins & devs communicating
74. DevOps can be developers on call / with pagers
75. DevOps is everyone on the same boat, going in the same direction
76. Bring Your Own Process Sorry, your job is solving problems.
78. “Collaborate not only when things go wrong.” — Patrick Debois
79. TL;DR It’s not about dev It’s not about ops It’s about the customer & the product running in production
80. Questions?
81. NoOps?
82. Thank you.
83. Slides available at: https://speakerdeck.com/ gkarekinian/intro-to-devops
84. People Patrick Debois @patrickdebois http://www.jedi.be/blog/ John Willis @botchagalupe John Allspaw @allspaw http://www.kitchensoap.com Mark Imbriaco @markimbriaco More: http://www.jedi.be/blog/2010/02/12/what- is-this-devops-thing-anyway/
85. Sources http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/ DevOps is not a technology problem: http://dev2ops.dtosolutions.com/2010/11/ devops-is-not-a-technology-problem-devops-is-a-business-problem/ What DevOps is not: http://www.agileweboperations.com/what-devops-is-not DevOps Ractions: http://devopsreactions.tumblr.com Images Sunn O))): http://www.ideologic.org/news/view/ sunn_o_west_coast_december_2012 KRS-One: http://pixmaster-eu.dontstayin.com/a41f9210- c626-420f-837e-2e5dc49e1f89.jpg Hip Hop 4 Elements: http://add-massu.blogspot.com Big-Bang integration picture: http://emmanuelchenu.blogspot.com