Speeding up enterprises, one deploy at a time - Devopsdays Toronto 2014
1 like885 views
This document summarizes a presentation about adopting DevOps practices in enterprises. It discusses that culture and technology influence each other and neither comes first. It provides examples of how configuration management tools improved operations and started conversations between development and operations. It emphasizes that getting others to see how the entire system works is important and that architecture matters for velocity. While DevOps can be adopted successfully sometimes, it requires buy-in from both development and operations as well as the right tools, processes, and architecture.
Speeding up enterprises, one deploy at a time - Devopsdays Toronto 2014
- 1. SPEEDING UP ENTERPRISES, ONE DEPLOY AT A TIME Stuart Charlton (@svrc) DevOpsDays Toronto 2014
- 2. HARRY TUTTLE, ENTERPRISE RELIABILITY ENGINEER
- 3. You’re asked to do something organizationally impossible
- 4. Your organization barely accomplishes the possible
- 5. You seriously consider a new line of work.
- 7. Devops P(aaS) Immutability Agile Lean Trust ! can be adopted, successfully, sometimes, maybe
- 8. …As with most things in the enterprise: ! (a) by accident or (b) if you’re a monomaniac on a mission
- 9. Three observations: ! 1. What comes first, culture or technology? 2. Getting others to see the system! 3. Architecture matters.
- 10. Culture or technology? Neither. These are reflexive (feedback loops). Emotional Impacts & Needs Culture Environmental Impacts New Knowledge and Needs Behaviour Technology
- 11. Can technology change an organization? It can change entire societies! Of course it can. Can you predict how technology will change an organization? “This is impossible to automate” “The tool won’t let us” “Are you certified?” “I can’t believe you use that programming language, ew”
- 12. Let’s assume DevOps is “new knowledge” to the enterprise… This means it’s a technology-led change, by definition. However, what technology are we speaking of? ….Configuration Management, Dev-Ops Collaboration, Clouds, Lean Value Streams, Chat Rooms, Wikis, Agile Methods, Immutable Containers, MicroServices, Big Data, Continuous Delivery …
- 13. ! The shape of the tools you choose, the environment you’re in, and the emotional state of the people you work with… drives the shape of behaviour you exhibit, drives the shape of the culture you live in.
- 14. EXAMPLES 1. Ops adopts config management (BladeLogic, Puppet, etc.) 2. Ops gets better 3. Dev doesn’t care, and still doesn’t test their code 1. Ops begins to transition to a self-service platform with new architecture constraints (Cloud Foundry, CLM, etc.) 2. Dev is forced to choose whether they change to fit the new hotness 3. A conversation begins
- 15. Getting Others to See The System Opera&ons* Management* Infrastructure* Engineering* Pla7orm* Engineering* Quality* Control* Services* Deployment* Services* Project* Execu&on* Release* Coordina&on* Release* Deployment* Schedule* Intake*Form* Intake*Analysis* Build*Guide* Collabora&on* Manual*Deploy* Heavy&PM)Coordina0on&&&Rework& Managed* Automated/ Manual*Tests* Manual*Provision* Middleware* Manual*Provision* Database* Manual*Provision* Compute* Manual*Provision* Storage* Manual*Provision* Network* Run*Produc&on*
- 16. Getting Others to See The System Opera&ons* Management* Infrastructure* Engineering* Pla7orm* Engineering* Quality* Control* Services* Deployment* Services* Project* Execu&on* Release* Coordina&on* SelfBService* Deployment*&** Test*Requests* Standard*Request* Standard*Deploy* (Automated)* Standard'Requests:' +"Straight*through"opera/onal"pla2orm" +"Monitoring"is"made"visible"" Standard* Automated*Tests* Standard*Manual* Tests* (Automated)* (Automated)* Monitoring*made* visible*to*Teams* Run*in*Produc&on* Case*Request* Manual*Deploy* Manual*Test* Manual*Provision* NetBNew* Pla7orm* Automa&on* Manual*Provision* NetBnew* Infrastructure* Automa&on*
- 17. Getting Others to See The System Opera&ons* Management* Infrastructure* Engineering* Pla7orm* Engineering* Quality* Control* Services* Deployment* Services* Project* Execu&on* Release* Coordina&on* SelfBService* Deployment*&** Test*Requests* Standard*Request* Standard*Deploy* (Automated)* Standard* Automated*Tests* Standard*Manual* Tests* (Automated)* (Automated)* Monitoring*made* visible*to*Teams* Run*in*Produc&on* Case*Request* Manual*Deploy* Manual*Test* Manual*Provision* NetBNew* Pla7orm* Automa&on* Manual*Provision* NetBnew* Infrastructure* Case%specific*Requests:* Automa&on* Tradi&onal*infrastructure/deploy*requests*+* tracked*in*release*management*system**+** *engineering*can*RFEs*to*pla<orm*
- 18. THE IMPOSSIBLE PROJECT OR, HOW ARCHITECTURE AND A GREAT TEAM SAVED OUR BUTTS You’re called into the CFO’s office… You need to build a system that will drive $2 billion annual revenue You have no staff and seven weeks. Solution: Guerilla Devops Warfare
- 19. Air Cover Second ! ! ! ! ! ! ! ! ! ! ! ! Line of Defence ! ! ! ! ! ! ! ! First Line of Defence ! ! ! Team Coach & PMs Product Owner Executives with Knives Simple Technology ! Tomcat Microservice JAX-RS only jQuery Puppet Bamboo EC2 Oracle XE MQ Simple Process ! Weekly Sprints Demos Every Week
- 20. Want velocity? Architecture matters! Devops is not just about Dev and Ops culture & tools Software Architecture (how is it structured for scale and change) Business (what are we doing and why) Team/organization (who does what, who protects you) Process (how do you coordinate work inside & expectations outside)
- 21. Results may be beautiful, but are fragile
- 22. Three observations: ! 1. What comes first, culture or technology? 2. Getting others to see the system! 3. Architecture matters.
- 23. Devops P(aaS) Immutability Agile Lean Trust ! can be adopted, successfully, sometimes, maybe
- 24. THANKS Stuart Charlton (@svrc)