SC18 DevOps Short Introduction
Download as PPTX, PDF0 likes98 views
This document contains a summary of a presentation on DevOps. It discusses how DevOps aims to improve collaboration between development and operations teams by integrating them, adopting more frequent releases, and organizing teams around products rather than functions. It also notes that DevOps seeks to reduce stress and improve work-life balance by changing workflows and responsibilities. The document provides some statistics on DevOps adoption and outlines the key aspects or "CLAMS" of a DevOps culture and approach.
SC18 DevOps Short Introduction
- 1. ©2018 Micron Technology, Inc. All rights reserved. Information, products, and/or specifications are subject to change without notice. All information is provided on an “AS IS” basis without warranties of any kind. Statements regarding products, including regarding their features, availability, functionality, or compatibility, are provided for informational purposes only and do not modify the warranty, if any, applicable to any product. Drawings may not be to scale. Micron, the Micron logo, and all other Micron trademarks are the property of Micron Technology, Inc. All other trademarks are the property of their respective owners. DevOps Intro …and memes…lots of memes. Jason Echols Assume many images were found on the internet and shamelessly utilized for our mutual education.
- 2. © 2018 Micron Technology, Inc. | Why is DevOps Important? 2 People & Business
- 3. © 2018 Micron Technology, Inc. | Why is DevOps Important? 3 James Wickett (@wickett) DevOps Days Organizer Rugged Dev Podcast Gauntlt Core Team (Open DevOps Security Tool) LASCON Founder “Look across the industry ten years ago…you saw burnout, overwork, stress, depression and other job- related problems. Operations teams had very difficult on- call schedules and lots of the emotional baggage that went with it. Operations teams were seen as inhibitors of change and they slowed down the business. Often at the end of a waterfall cycle there was a tense period where the development teams sent months of work over to operations to deploy in a weekend – and when that didn’t work the teams and the business suffered, again. DevOps sought to change this with more frequent releases and smaller batch sizes. Developers went on call and instead of organizing teams around discipline (dev, ops, security, ...), businesses started organizing teams around products and value provided to the customers. The mantra of if you wrote it, you own it started to take shape and things have never been better!”
- 4. © 2018 Micron Technology, Inc. | Why is DevOps Important? 4 Rackspace Survey (2015) - Source: http://ddf912383141a8d7bbe4-e053e711fc85de3290f121ef0f0e3a1f.r87.cf1.rackcdn.com/DevOps-Survey-Infographic.png
- 6. © 2018 Micron Technology, Inc. | Dev? Op? Huh? 6 Developer (DEV) Operations (OPS)
- 7. © 2018 Micron Technology, Inc. |7 Why Else is DevOps Taking Off?
- 8. © 2018 Micron Technology, Inc. | DevOps Interest #2 Search Phrase containing “DevOps” “What is DevOps”
- 9. © 2018 Micron Technology, Inc. | DevOps Summary DevOps “CLAMS” Culture Lean (Optional) Automation Measurement Sharing CULTURE OVER CODE (or Tools) Oh, and Security Too!
- 10. © 2018 Micron Technology, Inc. | Old-School vs. DevOps Unicorn 10 Requirements Developer(s) Testing (QA) Deployment Operations Infrastructure 9 Months 9 Hours Automated Automated Automated
- 11. © 2018 Micron Technology, Inc. | DevOps Workflow (tool focus) ONE VIEW… HERE ARE 50 MORE. ProductionDeploy/ReleaseDevelopment (CI)Developer Test Repo
- 12. A Quick Word on Culture and DevOps Adopters
- 13. © 2018 Micron Technology, Inc. | What if you don’t change organizations and culture? 13
- 14. © 2018 Micron Technology, Inc. | What does DevOps Org look like at Microsoft Cloud + Enterprise?
- 15. © 2018 Micron Technology, Inc. | Companies Adopting DevOps… 15 What (else) do they have in common? Your call…I think they all see software as a competitive differentiator.
- 16. Resources
- 17. © 2018 Micron Technology, Inc. | Learn More 17 Top DevOps Resources DevOps Thought Leaders and Practitioners to Follow DevOps Fundamentals on Lynda
- 18. © 2018 Micron Technology, Inc. |18
Editor's Notes
- #2: DevOps and memes go together like peanut butter and Jelly. Hopefully this doesn’t cause any graphics designers to give up on humanity, or make Nancy Duarte turn into a recluse. I plan to break most of the presentation rules here! We’ll cover the basics of DevOps, why it’s important, what things come together to build a DevOps environment, and how that impacts infrastructure.
- #4: This quote from a prominent DevOps practitioner James Wickett sums it up well.
- #5: So, that’s the people impact, here’s the IT and business impact from a Rackspace survey.
- #8: The traditional waterfall development (dev) team would spend months building complex new software. Some QA might happen, then the Operations (ops) team would be pushed to quickly put it into production to get the value to the business ASAP. This usually failed – sometimes spectacularly. Both teams would go into fast fix mode, or worse finger-pointing modes. Meanwhile people and the business suffered. Oh, and the customers too…
- #9: In 2009, Patrick Debois from Belgium and Andrew “Clay” Shafer from the US met and started talking up (and coined the term) DevOps, and then Patrick held the first DevOpsDays event in Ghent that lit the fuse. https://theagileadmin.com/what-is-devops/ In 2018 the #1 search phrase containing “DevOps” became “DevOps Engineer” vs “what is devops”
- #10: If you only take one thing away from this presentation, this is it. CLAMS. CLAMS is the generally agreed to set of things you need to address to successfully transition to a DevOps environment.
- #11: The traditional software development model would take months to develop software for a major release, with lots of new things. Then that would be thrown over the wall to testing, then Operations. Each step was manual and labor intensive, often in different software environments. DevOps takes Agile concepts along with automation and other ideas to build a streamlined, automated workflow that creates results faster and with less stress on the employees to meet gargantuan delivery dates. By the way, you still need people for all of this, but they are doing more interesting and challenging things in general, rather than QA’ing someone else's code for the 5th time, or trying to determine why it won’t come up in the production environments at 3AM before a deadline. DevOps isn’t perfect, problems still pop up, and radical change in culture, organizations, and tools are needed…but it’s becoming more common because of the people and business benefits.
- #12: Inside testing: Automated: Gauntlt, Ixia, etc Outside testing: Penetration, 3rd party Audit, etc. Test times: Commit: 2-5 Min Nightlys: 15 Min – 30 Min Major Release: Hours
- #15: The previous slide talked about people and culture. Here is how Microsoft explains the DevOps shift within their organization.
- #16: As you can see, many very agile, web-centric companies have been early adopters of DevOps, but many traditional companies are joining too. Traditional companies that are highly competitive or see constant change in their industry tend to be early adopters across the board. Highly regulated companies tend to lag as regulations do not account for many of the DevOps methodologies…but there are breakouts starting in all industries.