Your SlideShare is downloading. ×
  • Like
Agile 2013 Talk: How DevOps Changes Everything
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Agile 2013 Talk: How DevOps Changes Everything

  • 4,122 views
Published

The most important DevOps things I’ve learned over the last 4 years. I presented this at Agile 2013 in Nashville, TN. #agile #devops #automation #culture #distributedTeams #measurement #sharing …

The most important DevOps things I’ve learned over the last 4 years. I presented this at Agile 2013 in Nashville, TN. #agile #devops #automation #culture #distributedTeams #measurement #sharing #bestPractices

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
4,122
On SlideShare
0
From Embeds
0
Number of Embeds
8

Actions

Shares
Downloads
55
Comments
2
Likes
6

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. How DevOps changed everything Karthik Gaekwad @iteration1 #AgileDevOps Wednesday, August 7, 13
  • 2. Howdy! • I’m Karthik Gaekwad • Senior Web Engineer • Mentor Graphics Embedded • From Austin,TX • We have great BBQ, chill people and brutal summers! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 3. My Background • National Instruments (NI) • Ecommerce Team (Agile) • R&D Cloud Team (DevOps) • Mentor Graphics Embedded • Cloud Team (DevOps) • Organizer: CloudAustin, DevOpsDays Austin, TheAgileAdmin #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 4. Audience Survey #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 5. The most important DevOps things I’ve learned over the last 4 years Let’s not waste time! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 6. First, we have to talk about agile... #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 7. #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 8. There was a waterfall Requirements Design Implement, Test Maintain Deploy #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 9. Roles Requirements Design Implement Maintain Deploy Product Manager, Business Analyst Business Analyst,Web Designer,Architect Programmer Analyst,Web Developer Programmer Analyst, System Administrator System Administrator #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 10. S #AgileDevOps@iteration1 Agile 2013 Waterfall.. Wednesday, August 7, 13
  • 11. #AgileDevOps@iteration1 Agile 2013 “But I told you this already” Communication Wednesday, August 7, 13
  • 12. #AgileDevOps@iteration1 Agile 2013 “That is not my job!” Accountability Wednesday, August 7, 13
  • 13. #AgileDevOps@iteration1 Agile 2013 “That is not a priority” Time to deliver Wednesday, August 7, 13
  • 14. #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 15. **About the time I started... #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 16. New Product: Partslist Collaborate and tag parts to build large systems #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 17. Transitioned to SCRUM 2 Week Iterations Targeted Feature sets Demo at end of iteration #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 18. The Product Team > Traditional Organization #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 19. Results Working together, building things that were wanted #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 20. Results Between Business and IT #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 21. Results Better products being delivered, at a faster pace. Methodology expanded to all other web teams... #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 22. Results I love my job! #ForReal #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 23. Agile: Retrospective • Scrum brought team together. • Building products on time, which were actually needed. • Superior collaboration between business and IT. • Organization shift -> Scrum #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 24. Ops conversations “Agile is cool! but it’s hard for ops to be agile because it takes months to buy and provision servers.” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 25. #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 26. Ops conversations Deployer Dude “All day everyday” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 27. But in the community... #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 28. But in the community... #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 29. “We’re making cloud products now” “Go build us cloud products now” Sincerely, Management #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 30. “We’re making cloud products now” “Cloud is AWESOME!” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 31. “We’re making cloud products now” “Cloud is OSSM” -Dave Nielson -NIST #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 32. “We’re making cloud products now” “Cloud is AWESOME OSSM” On-demand Self-service Scalable Measurable #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 33. “Give me API or give me death” @littleidea #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 34. “We’re making cloud products now” “Agile DevOps Cloud Team” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 35. DevOps “A cultural and professional movement” Adam Jacobs #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 36. DevOps “System administrators participating in an agile development process alongside developers and using many of the same agile techniques for their systems work.” The Agile Admin Blog #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 37. Alison Chaiken Embedded Linux,Thought Leader “Get rid of the devs; get rid of the ops; let’s just find people who can solve problems” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 38. CULTURE MEASUREMENT AUTOMATION SHARING Pillars of DevOps John Willis Damon Edwards #AgileDevOps@iteration1 Agile 2013 By: Wednesday, August 7, 13
  • 39. DevOps 101 Ideas and Stories Free!! No charge!! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 40. “We’re making cloud products now” “Agile DevOps Cloud Team” #AgileDevOps@iteration1 Agile 2013 Buzzword friendly! Wednesday, August 7, 13
  • 41. We had a goal: “Build a cloud authentication prototype” Wednesday, August 7, 13
  • 42. C U LT U R E Our 1st sprint(s) sucked! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 43. C U LT U R E But we suffered from “Wall of confusionitis” Devs: “REST Services!” Ops: “System Stability!” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 44. C U LT U R E Not seeing eye to eye #Frustrating #Angry #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 45. C U LT U R E #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 46. C U LT U R E Really, this is “Platform Architecture”, but I’m too lazy to redo the image #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 47. C U LT U R E Devs and ops understand good architecture. #GoodPlaceToStart #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 48. C U LT U R E Think platform first, then app later. #PaaS #REST #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 49. • Everyone understood architecture • Helped everyone speak same language • Reduced friction • Called it “The System Model” A U T O M A T IO N #AgileDevOps@iteration1 Agile 2013 1st win:Architecture Wednesday, August 7, 13
  • 50. 1st win:Architecture • “Model Driven Automation” • Championed by ops • Everyone needs to understand the model • Figure out how to deploy the model A U T O M A T IO N #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 51. 1st win:Architecture • Programmable Infrastructure Environment (PIE) • Based on version controlled architecture diagram • Provisioned cloud boxes • Ran deploys • Set standard naming for boxes • On demand deploy for apps A U T O M A T IO N #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 52. Outcomes • Ops learns Java! • Ops learns version control! • Developers get comfortable with production environments! • ...Now we’re speaking many common languages! A U T O M A T IO N #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 53. No Chef? No Puppet? A U T O M A T IO N Are y’all crazy??? #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 54. A U T O M A T IO N Everybody be cool • We believe the cleanest abstraction layer is starting with the entire system you’re trying to model • In 2009, chef and puppet were younger • We were scared of Ruby • We needed windows cloud support • Plus dawg, cloud was a wild wild world then! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 55. A U T O M A T IO N Please automate!! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 56. A U T O M A T IO N Do I pick Chef or Puppet?? “whatever makes you happy” #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 57. SH A R IN G For chef/puppet, you’ll need to code. #NotJust4Devs #NotScary #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 58. SH A R IN G Stuck? Just ask your DevOps dev guy! #NotJust4Devs #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 59. SH A R IN G Don’t hide. Share the knowledge #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 60. SH A R IN G App configs Wednesday, August 7, 13
  • 61. SH A R IN G App configs Easy Change Management Let your automation control these kind of files Wednesday, August 7, 13
  • 62. Tools Philosophy D EV O PS • Needed to work for cloud • Facilitate collaboration • Charts and graphs • Everyone wants to use it #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 63. Tools Philosophy M EA SU R E • Monitoring = Cloudkick • Monitor servers • Monitor code (custom synthetic checks) We use #datadog now #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 64. Tools Philosophy M EA SU R E Teach your devs how to monitor their code, and they will love the tool Example: #NewRelic #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 65. Tools Philosophy M EA SU R E If it measures business metrics, management will love you too! #statsd #dogstatsd HINT: Management pays you. Make them happy #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 66. Tools Philosophy M EA SU R E WASTE OF TIME: SSH’ing into a box to read log files #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 67. Tools Philosophy M EA SU R E Get a logging solution. Plethora of choices! #Logstash #Graylog #Splunk #Sumologic Which one? CloudAustin July Meetup #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 68. SH A R IN G You’ll need more tools Find them or write them! You’re devops now! Tools Philosophy #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 69. Tools Philosophy M EA SU R E DevOps victory: “People” use tools that solve their core problems #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 70. DevOps 201 MOAR Ideas and Stories For ops who can code and dev not scared of linux #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 71. C U LT U R E Is different for every team. What works for your team, works for your team #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 72. C U LT U R E This worked for us... #AlwaysBeInclusive #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 73. C U LT U R E Stuff Breaks Like...all the time #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 74. C U LT U R E #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 75. C U LT U R E #DontDoThis #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 76. C U LT U R E Be Cool. Fix the issue at hand If you panic, everyone else does too. #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 77. C U LT U R E Post Mortem Do a Post mortem #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 78. C U LT U R E Post Mortem It’s okay to admit mistakes You’re not Batman... #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 79. C U LT U R E Post Mortem Why x5 Add more tests Make sure it doesn’t happen again #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 80. C U LT U R E RELEASE OFTEN Release with 4 changes is less risky than Release with 40,000 changes #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 81. D EV O PS Testing Wednesday, August 7, 13
  • 82. D EV O PS Test Everything Test the code Test the infrastructure It’s all the same now #infrastructureAsCode #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 83. D EV O PS Free Time? Write more tests! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 84. D EV O PS CONTINUOUSLY #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 85. D EV O PS CONTINUOUSLY #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 86. D EV O PS Manual Changes To Production #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 87. D EV O PS Manual Changes Don’t do this. Do this: 1. Make manual changes in dev 2.Add to your chef/puppet script 3. Release to test/prod #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 88. DevOps 301 MOAR MOAR Tips For when your team grows #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 89. Security in the loop Add security audits as a part of your sprint. We do an audit periodically #AgileDevOps@iteration1 Agile 2013 @Gauntlt @RuggedDevOps Wednesday, August 7, 13
  • 90. Security in the loop Hire an infosec pro to your devops team #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 91. Security in the loop No budget? Try a cross functional working group #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 92. Expanding Teams? • Rotate times for meetings (status/planning) • Scrum standups were recorded and dropbox(ed) • “OK to call” philosophy • Campfire chat (saves history) • Ownership of new features #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 93. Expanding Teams? • No secret: Face to face is always better • Prioritize travels for visits to teammates #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 94. Everyone asking for DevOps? The embedded DevOps model works* #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 95. Everyone asking for DevOps? Make sure your team culture is strong enough so you don’t lose person permanently :) #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 96. Start Small... Don’t say “WE’RE 100% DEVOPS TODAY” Wednesday, August 7, 13
  • 97. DevOps 401 MOAR MOAR MOAR Ideas For next time. I don’t have any. Tweet #agiledevops for your best ideas! #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 98. STILL STUCK? Just ask! We’re devops, and this is real (even though we can’t define it) Twitter: #devopsama http://devopsweekly.com/ Go to a devopsdays https://groups.google.com/forum/#!forum/devops #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 99. DevOps: Retrospective • DevOps and CAMS bring team together. • Building stable products on time, which were actually needed. • Superior collaboration between devs and ops • Organization shift -> DevOps #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13
  • 100. DevOps: Retrospective • DevOps and CAMS bring team together. • Building stable products on time, which were actually needed. • Superior collaboration between devs and ops • Organization shift -> DevOps #AgileDevOps@iteration1 Agile 2013 • Scrum brought team together. • Building products on time, which were actually needed. • Superior collaboration between business and IT. • Organization shift -> Scrum Wednesday, August 7, 13
  • 101. Thank you! Let’s work together, and solve the problems that our business wants us to! #DevOps #AgileDevOps@iteration1 Agile 2013 Wednesday, August 7, 13