Intro to DevOps

An introduction to DevOps presented at the Crabby Admins (LOPSA-Baltimore) meetup.

Transcript

1. DevOps Transforming the way you think about IT Nathen Harvey @nathenharvey 1
2. Nathen Harvey ‣ Technical Community Manager at Opscode ‣ Co-host of the Food Fight Show Podcast ‣ Meetup Organizer ‣ Formerly: Web Operations ‣ @nathenharvey 2
3. Who are you? ‣ Developers? ‣ Systems Administrators? ‣ DevOps? ‣ “Business” People? ‣ Executives? 3
4. Are you sure? 4
5. DevOps 5 ‣ Cultural and Professional movement ‣ Development and Operations working together
6. Aligning Objectives 6 http://www.flickr.com/photos/amylovesyah/5042999235 http://www.flickr.com/photos/maryamandathompson/4810162947/
7. DevOps 7 ‣ Cultural and Professional movement ‣ Development and Operations working together ‣ Leveraging ideas & processes from other industries ‣ To enable the business
8. Technology – The Way Business Engages Customers
9. Globalization ‣ 40 years for container ships to move 70% of seaborne trade ‣ 22 years for internet access to reach 78% penetration in North America 9 WTO Trends in Globalization http://www.wto.org/english/res_e/booksp_e/anrep_e/wtr08-2b_e.pdf http://www.flickr.com/photos/duke_raoul/2261478794/sizes/l/in/photostream/
10. Globalization ‣ Online retail sales are 7% of all retail sales ‣ 75% of 2011 Thanksgiving shoppers did so online ‣ 42% of all retail purchases were influenced by online research – accounting for ~50% of total retail spending. 10 WTO Trends in Globalization http://www.wto.org/english/res_e/booksp_e/anrep_e/wtr08-2b_e.pdf http://www.flickr.com/photos/duke_raoul/2261478794/sizes/l/in/photostream/
11. 95% of the western world own cell phones ‣ 42% are smartphones ‣ 58% will be on next purchase ‣ 4.2 Billion phones globally for 7.09 Billion people (USCB) 11 http://ssiknowledgewatch.com/2012/05/09/cell-phones-approach-total-penetration-globally-with-smartphones-moving-toward-market-dominance-2/ http://www.brightsideofnews.com/news/2011/1/26/digital-divide-global-household-penetration-rates-for-technology.aspx?pageid=1
12. Software is the interface for consumption 12
19. The Result: The Coded Business How: Redefinition of how to use technology to create business value Why: To rapidly deliver experiences, goods and services to customers What: Consumer-facing businesses Drivers of IT Innovation
20. The Rise of the Coded Business ‣ Changes are outpacing skills development ‣ IT is moving from the back office to the front office ‣ Customers prefer digital consumption ‣ Technology directly supports customer interactions ‣ Accelerated pace of change ‣ Companies must move faster to compete
21. Patterns of the Coded Business Business Agility Development Velocity and Consistency Continuous Delivery IT Automation IT enables Business Agility and becomes a strategic advantage rather than a cost center.
22. Manufacturing Financial Services Retail Media and Entertainment High Technology Healthcare The Coded Business is Coming To Every Enterprise
23. Is the cultural and professional movement that grew directly from the collective experience of the pioneers of this transition It’s application to traditional IT is 1:1 The business adaptations encapsulated in Devops will eventually be ubiquitous ....At least, if you want to be great at the next couple decades of global economic growth DevOps
24. ‣ Culture ‣ Automation ‣ Measurement ‣ Sharing DevOps - CAMS 24
25. Open Communication ‣ Developers & Operations talk and listen to one another ‣ Production & build metrics are available to all ‣ Current infrastructure is documented 25 Walls, Mandi. O’Reilly Media. 2013
26. Incentive & Responsibility Alignment ‣ Create awesome customer experiences ‣ Focus on responsibility & accountability, not authority ‣ You are responsible for your own uptime 26 Walls, Mandi. O’Reilly Media. 2013
27. Respect ‣ You don’t have to like each other but you do need to recognize contributions and treat each other well 27 Walls, Mandi. O’Reilly Media. 2013
28. Trust ‣ Trust that everyone is competent and working toward the common goals ‣ Without trust, the tools don’t matter 28 Walls, Mandi. O’Reilly Media. 2013
29. Trust Others to Behave Responsibly 29
30. Stop Tolerating Assholes 30
31. You’re an Asshole if: 31 ‣ After encountering you, people feel oppressed, humiliated, or otherwise worse about themselves ‣ You target people less powerful than you Sutton, Robert. Business Plus. 2007
32. Assholes are incompetent - let’s shun them 32
33. Effective Communication 33 ‣ Lead with questions, not statements ‣ Understand the effort and time others have invested ‣ Avoid the passive- aggressive snark http://www.flickr.com/photos/aloha75/4753674243/sizes/l/in/photostream/
34. ‣ Culture ‣ Automation ‣ Measurement ‣ Sharing DevOps - CAMS 34
35. Scale x Complexity > Skills 35
36. Managing Complexity Then Web Servers Application Servers Database Add 1 server 20+ Changes To Add a New Server… • 2x Web Server Configurations • 2 Web Server Restarts • 4x Database Configurations • 8x Firewall Configurations • DNS Service • Network Configuration • Deployer • 8x Monitoring Changes The Bottom Line… 20+ Changes 12+ New Infrastructure Dependencies 4+ Hours
37. Managing Complexity Later We added: • Load Balancers • MemCache • Search Appliances • Lots of VM’s • More Scale Exponential Increase In: • Configuration Changes • Infrastructure Dependencies • Skills Needed • Greater Risk
38. How Do we Manage This at Cloud Scale? • Thousands of infrastructure dependencies and configurations needed for each change. • Huge Amounts of Time • Increased Cost of Correction of Manual Errors • Huge Need for Talent • Risk of Critical Skills Shortage Managing Complexity Today
39. Full Automation Common Automation Tasks: Scripts, OS Compliance, Updates & Patches Configuration Management Discovery and Visibility Application Management Continuous Deployment Automation is a People, Process, and Technology Journey The Path to the Coded Business
40. Continuous Delivery 40 ‣ Business needs to deliver a better customer experience as quickly and safely as possible. http://www.thoughtworks.com/imgs/continuous-delivery.jpg
41. Continuous Delivery ‣ Version Control System 41
42. Not Version Control ‣ cp foo{,.bak} ‣ cp foo{,.`date “+%Y%m%d%%H%M%S”`} 42
43. Continuous Delivery ‣ Distributed Version Control System ‣ Dependency management ‣ Software Configuration ‣ Environments ‣ Continuous Integration 43
44. Deployment Pipeline 44
45. Commit Code 45 Application Devs! Infrastructure Devs! Software Configuration Management! (SCM)!
46. Automated Build Infrastructure Devs! Software Configuration Management! (SCM)! Build! Pulling! Tag! Payload! N! Payload! 3! Payload! 2! Payload! 1! 46 Application Devs! Infrastructure Devs! Software Configuration Management! (SCM)!
47. Deployment Pipeline 47 1! 2! ….! Software Configuration Management! (SCM)! Build! Pulling! Tag! Payload! N! Payload! 3! Payload! 2! Payload! 1! Create Data (#)! Upload Cookbook! Autodeploy to Local Host! Update DEV! Request Portal! Chef Server! Bootstrap & Autodeploy! Infrastructure Devs! QA! DEV! …..! PROD! 1, 2, … N! …..! N! ! ! Promote! Promote!
48. ‣ Culture ‣ Automation ‣ Measurement ‣ Sharing DevOps - CAMS 48
49. What to measure? ‣ Measure everything! ‣ Performance metrics ‣ Process metrics ‣ People metrics 49
50. Availability ‣ A = MTTF/MTBF = MTTF / (MTTF + MTTD + MTTR) ‣ MTTD - Mean time to Diagnose ‣ MTTR - Mean time to Repair ‣ MTTF - Mean time to Failure ‣ MTBF - Mean time between Failures 50
51. Availability ‣ A = MTTF/MTBF = MTTF / (MTTF + MTTD + MTTR) ‣ MTTD - Mean time to Diagnose ‣ MTTR - Mean time to Repair 51
52. Failure ‣ It’s not “if” but “when” ‣ Focus on ‣ MTTD - Mean time to Diagnose ‣ MTTR - Mean time to Repair ‣ MTTR > MTBF! 52
53. Measure & Alert on the right things! ‣ Is CPU usage important enough to measure? ‣ Should you care about an individual host / server? ‣ Are the web servers responding quickly? ‣ How many deploys were completed today? ‣ Are customers able to checkout? 53
54. Measurement & Monitoring ‣ Service availability > Server availability ‣ Measure everything, alert on the important metrics ‣ Monitors and measurements are code, treat them as such 54
55. Drill
56. ‣ Culture ‣ Automation ‣ Measurement ‣ Sharing DevOps - CAMS 56
57. Internally ‣ Successes ‣ Failures ‣ Metrics ‣ Ideas ‣ Code 57
58. Externally ‣ Successes ‣ Failures ‣ Metrics ‣ Ideas ‣ Code 58
59. Sharing ‣ Conferences ‣ Blogs, papers, articles, etc. ‣ Podcasts 59
60. ‣ Culture ‣ Automation ‣ Measurement ‣ Sharing DevOps - CAMS 60
61. DevOps Practices ‣ Value Chain Mapping ‣ Virtualization ‣ Configuration Management ‣ Disposable Infrastructure 61
62. DevOps Practices ‣ Developers on call ‣ System Administrator Coders 62
63. When is it done? ‣ Committed to version control ‣ Tests are passing ‣ Deployed to production ‣ Monitored in production ‣ Customers getting value 63
64. Blameless Post Mortems ‣ Include all stakeholders ‣ Agree on timeline ‣ Identify the conditions that led to the failure ‣ Create tickets 64
65. IT - Extended Family ‣ Infrastructure as a Service ‣ Platform as a Service ‣ Software as a Service 65
66. Is the cultural and professional movement that grew directly from the collective experience of the pioneers of this transition It’s application to traditional IT is 1:1 The business adaptations encapsulated in Devops will eventually be ubiquitous ....At least, if you want to be great at the next couple decades of global economic growth DevOps
67. Businesses must deliver better customer experience as quickly and safely as possible. Safety matters! Failure to do so will have serious impacts on customer satisfaction and loyalty – just like it did when Sam Walton was the Ghengis Kahn of rural retail. http://www.flickr.com/photos/huffstutterrobertl/5088855119/lightbox/ Continuous Delivery
68. ‣ "In ten years, I'm certain every COO worth their salt will have come from IT. Any COO who doesn't intimately understand the IT systems that actually run the business is just an empty suit, relying on someone else to do their job." Essential Reading 68 Kim, Gene; Behr, Kevin ; Spafford, George (2013-01-10). The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win (Kindle Locations 5805-5807). IT Revolution Press. Kindle Edition.
69. ‣ “The Web is changing the way we live and touches every person alive. As more and more people depend on the Web, they depend on us. Web Operations is work that matters” Essential Reading 69 John Allspaw & Jesse Robbins Web Operations: Keeping the Data on Time O’Reilly. 2010.
70. Essential Reading 70
71. Want to learn Chef? ‣ 2-Day Chef Fundamentals next week in DC ‣ Focused on managing Windows servers with Chef ‣ Tuesday & Wednesday 71
72. Thank You! ‣ What questions do you have? ‣ Nathen Harvey ‣ nharvey@opscode.com ‣ @nathenharvey 72