One Does Not Simply Walk Into Devops
5 likes4,160 views
The document discusses the DevOps movement, emphasizing the importance of communication, collaboration, and cultural aspects in improving software delivery and organizational agility. It highlights various practices, such as infrastructure as code, accountability in deployment, and the need for continuous monitoring and testing to enhance software reliability. Additionally, it outlines strategies for effective deployments and the challenges in implementing DevOps across different organizations.
One Does Not Simply Walk Into Devops
- 4. âstresses communication & collaboration ... aims to help an organization rapidly produce software products and servicesâ
- 5. âThe DevOps movement was born of the need to improve IT service delivery agility... â
- 6. âSome of that is tools ... A big part of that is cultureâ Jesse Robbins, OpsCode
- 7. âHelp me define itâŠâ Adrian Cockroft, Netflix
- 9. Itâs about shipping better software, So⊠What Is faster & more It about? consistently âą Where traditional dev and ops roles fail to deliver
- 10. Learn by example, not invent (yet) another definitionâŠ
- 11. Jesseâs Dev & Ops as Teams Taxonomy (Culture & Processes) (I know, this can also start a flame warâŠ) Infrastructure as Code Application as Services
- 13. Accountability âą sdf http://www.slideshare.net/jezhumble/scaling-devops
- 14. Devs own their code, so they expect 24x7 contact with it Trust & Responsibility Allspawâs Take
- 15. When things break, dev and ops both participate Trust & Responsibility Allspawâs Take
- 16. Post mortems have dev and ops remediations Trust & Responsibility Allspawâs Take
- 17. âEveryone who has changes going out is accounted for and is actively testing and supporting their changesâ Chuck Rossi, Facebook
- 20. âDone means releasedâ Jez Humble
- 21. Measure âIf it moves, graph Everything it. If it matters, alert on itâ Allspaw
- 22. Not Just Infrastructure âą Measure infra, app and business KPIs âą Donât just measure, correlate
- 25. âShip early, ship oftenâ âą Small increments âą Undeployed code is lost value Chuck Rossi, Facebook
- 30. 11.6 seconds Mean time between deployments 1079 Max number of deployments / hour 10,000 Mean number of hosts simultaneously receiving a deployment Source: John Jenkins
- 32. Well Defined âą Canary tests Rollout âą Red/Black Mechanism Deployment âą Dark launches
- 38. A Self- Service Data Center Really Helps (Even more so if it has an API..)
- 39. âą Infrastructure as The Common product, app devs to All the as customers â Netflix calls it NoOps, Above but it pisses of Allspaw
- 41. âą Small services with APIs â Easier to ship, easier to debug, easier to manage at large scale â Caveat: forward and backward compatibility â @adriancoâs âanti- fragilityâ
- 42. âą We assume commodity HW, Resiliency in Cloud the Software âą So we have to Stack build reliability into our code
- 45. âEverything is Built for 3â Jeremy Edberg, Netflix
- 48. Whatâs Next? â Not everyone is Amazon & Netflix â The next challenge is to make this accessible to all
Editor's Notes
- #2: Motivation, what you wonât find in this talk
- #12: Devops as teamsShared metrics Incident mgmtService owners on call CI / CD Game day Infra as code: Full stack automation Commodity HW Reliability in SW stack Data center APIs Core infra services: infra as product, app as customer  Application as services: Service orientation Versioned APIs SW resiliency (design for failures) DB storage abstraction Complexity pushed up the stack Deep instrumentation Â
- #14: In amazon every dev runs her own code
- #18: Push karma
- #21: Ben talked about it, itâs everyoneâs responsibility, including devs
- #26: Ben mentioned Mark Ibericogithub â undeployed code is lost value
- #28: Change is a cause for instability
- #33: Which will allow you to test and rollback changes if needed
- #37: Roll your own tools - Etsy
- #38: Talk a bit about the netflix stack â bakery, simian army, asgard
- #39: Imuutable servers
- #40: infra as product, app as customer (netflix calls it noops, which pisses of allspaw)
- #43: Devs thinking about ops
- #44: Facebook â gatekeeper, wix, etsyCaveat: code can get messy, need to clean up dead code paths methodically
- #46: Database questions, mention