You Build It, But How Are You Going to Run It?
•
1 like•409 views
Damon Edwards, co-founder of Rundeck, presents at DevOps Con Munch on December 3, 2019. The DevOps movement is undeniably pulling Developers closer to Operations. "Shift left" and "You build it, you run it" have become common slogans. However, for years, we were told that developer involvement in production was verboten — a bad idea that would surely lead to chaos, poor productivity, and higher costs. Our legacy processes, policies, and technologies were all built to live within and reinforce the Dev and Ops divide. This talk will examine: 1) what changed 2) how to make it work at scale. See a Demo of Rundeck Enterprise : https://www.rundeck.com/see-demo --or-- Download Rundeck Open Source here: https://rundeck.com/open-source Connect: Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck Github: https://github.com/rundeck/rundeck/issues Twitter: https://twitter.com/Rundeck Facebook: https://www.facebook.com/RundeckInc/ LinkedIn: www.linkedin.com › company › rundeck-inc
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to You Build It, But How Are You Going to Run It?
Similar to You Build It, But How Are You Going to Run It? (20)
More from Rundeck
More from Rundeck (20)
Recently uploaded
Recently uploaded (20)
You Build It, But How Are You Going to Run It?
- 1. Damon Edwards You Build It. You Run It. (But How?)
- 2. Damon Edwards You Build It. You Run It. (But How?) @damonedwards rundeck.com/dc-munich-19
- 3. Recap from this morning’s keynote… + “Value-Aligned” and Self-Regulating Shared Responsibility Model
- 4. Recap from this morning’s keynote… + “Value-Aligned” and Self-Regulating Shared Responsibility Model The Three Ways
- 5. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change!
- 6. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change! You build it.
- 7. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change! You build it. They run it.
- 8. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change! Broken Flow! You build it. They run it.
- 9. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change! Broken Flow! Slow Feedback! You build it. They run it.
- 10. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change! Broken Flow! Slow Feedback! Difficult to Learn! You build it. They run it.
- 11. Old operating models can’t keep up… The Three Ways Development Team Operations Team Running Service WallofConfusion I want stability! I want change! Broken Flow! Slow Feedback! Difficult to Learn! You build it. They run it.
- 12. …”but, we have to keep Operations work away from our expensive devs!”
- 13. It’s 2am …
- 14. It’s 2am … It’s the NOC… Talk them through: health checks, reviewing log files, and process of diagnosing and recovering the system. Same as you did for dev teams 2 months ago, QA teams last month, Ops during deploy last week, etc.
- 15. It’s 2am …
- 16. It’s 10am …
- 17. It’s 10am … Will this new component work with the current production environment? Why isn’t this test environment working the way I expect? I need the latest test data. Is this the correct version of the API? Why is this environment broken?
- 18. It’s 2pm …
- 19. It’s 2pm … It’s Ops… “Will your applications be affected if we take down EU-West?” “Is it ok if we change these firewall rules?” “We are getting customer complaints about performance. Are you sure you didn’t change something?”.
- 20. It’s 5pm …
- 21. It’s 5pm … It’s Ops… “Outage!” “What do these error messages mean?” “Incident bridge has started”
- 25. Dev Ops Running Service You build it. You run it.
- 26. Dev Ops Running Service You build it. You run it. Same backlog, same priorities, same management
- 27. Dev Ops Running Service You build it. You run it. Does not mean everyone do everything! Same backlog, same priorities, same management
- 28. You build it. You run it. …but how?
- 29. 1. Understand how the money and politics flow 2. Deployability, configurability, observability are product features 3. Integration tests over unit tests 4. Make any handoff between teams “verification-driven” 5. Limit the surface area with platforms (and platform teams) 6. Protect capacity and limit interruptions 7. Demand “prod-like” environments everywhere 8. Test in production 9. Automate the runbooks 10. Enable self-service operations
- 30. 1. Understand how the money and politics flow
- 31. 1. Understand how the money and politics flow
- 32. 2. Deployability, configurability, observability are product features
- 33. 3. Integration tests over unit tests
- 34. 4. Make any handoff between teams “verification-driven”
- 35. 5. Limit the surface area with platforms (and platform teams)
- 36. 6. Protect capacity and limit interruptions
- 37. 7. Demand “prod-like” environments everywhere
- 38. 8. Test in production
- 39. 9. Automate your runbooks
- 40. 9. Automate your runbooks
- 41. 9. Automate your runbooks Before
- 42. 9. Automate your runbooks Before After
- 43. 9. Automate your runbooks Before
- 44. 9. Automate your runbooks Before After
- 45. 9. Automate your runbooks Before
- 46. 9. Automate your runbooks Before After
- 47. 10. Enable self-service operations
- 48. 10. Enable self-service operations
- 49. 10. Enable self-service operations
- 50. 10. Enable self-service operations
- 51. Advanced: “You build it, You run it” in a divided org
- 52. Advanced: “You build it, You run it” in a divided org Dev Ops Cross-Functional Team Cross-Functional Team Shared Responsibility Model “Value-Aligned” and Self-Regulating
- 53. Advanced: “You build it, You run it” in a divided org Dev Ops Cross-Functional Team Cross-Functional Team Shared Responsibility Model “Value-Aligned” and Self-Regulating
- 54. Recap Build consensus on the “why” Build your own principles Iterate 1. Understand how the money and politics flow 2. Deployability, configurability, observability are product features 3. Integration tests over unit tests 4. Make any handoff between teams “verification-driven” 5. Limit the surface area with platforms (and platform teams) 6. Protect capacity and limit interruptions 7. Demand “prod-like” environments everywhere 8. Test in production 9. Automate the runbooks 10. Enable self-service operations