DevOps 101
•Als PPTX, PDF herunterladen•
5 gefällt mir•2,647 views
Donnie Berkholz will present an introduction to DevOps (updated for 2017!), then open it up to questions and discussion. Topics will include making microservices more easily adoptable, and that whole "serverless" thing. Wherever you are in your DevOps journey, there will be something for you in this meetup session.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (10)
Ähnlich wie DevOps 101
Ähnlich wie DevOps 101 (20)
Mehr von Donnie Berkholz
Mehr von Donnie Berkholz (17)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
DevOps 101
- 1. DevOps 101+ Donnie Berkholz, Ph.D. Research Director — Development, DevOps, & IT Ops DevOps MSP meetup, Jan 2017
- 2. Everyone’s becoming a software company… 2 But we don’t all realize it yet. 0 5 10 15 20 25 30 35 40 45 50 Early adopter Pragmatic Conservative Skeptical Percentage Technology adoption stance 4Q14 (n=706) 1Q15 (n=1050) 2Q15 (n=975) 3Q15 (n=935) 4Q15 (n=1057) 1Q16 (n=749) 3Q16 (n=806) 4Q16 (n=613) Source: 451 Research, Voice of the Enterprise: Cloud Transformation 4Q14: 9.5% 4Q16: 17.0%
- 3. 3 Source: 451 Research/Microsoft Cloud+Hosting commissioned research Minimizing risk, maximizing agility 31 30 22 25 25 21 20 19 22 21 23 23 11 14 17 18 12 15 17 16 2013 n=1540 2014 n=2041 2015 n=1736 2016 n=1734 Lower risk Speed time to market Improve product or service quality Lower costs Increase revenue
- 4. The new stack? 4 An infinite array of possible stacks.
- 5. DevOps: Putting IT into high gear 5
- 6. 6 What in the world is DevOps, anyhow?
- 7. 7 Agile, truly tip to tail Business to customer
- 8. 3 pillars of DevOps 8 Culture Automation Measurement Tied together by lean
- 9. 9 Culture: Tear down all the silos Flickr: kalandrakas
- 10. 10 Flickr: respresFlickr: hartvig, snapeverything, roymaloon Automation: Pets vs Cattle
- 11. Automation: Infrastructure as code 11 Wikipedia: Magnus Manske
- 12. Knight Capital and the $460 million bug 12 Wikipedia: Jericho
- 14. Where are we today? 14 10.0% 54.7% 27.9% 6.8% 0.7% Highly Manual Manual with Limited Automation Tools Automated with Manual Exception Handling Policy Based Automation and Orchestration Other n = 843 Source: 451 VotE Cloud, Q3 2015
- 16. 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% < 250 employees 250-999 employees 1,000-9,999 employees >10,000 employees Agile adoption: still not universal 16 451 Research, Voice of the Enterprise: Software-Defined Infrastructure, Q4 2015 (n=670)
- 17. 0% 10% 20% 30% 40% 50% 60% < 250 employees 250-999 employees 1,000-9,999 employees >10,000 employees DevOps adoption: resource-dependent? 17 451 Research, Voice of the Enterprise: Software-Defined Infrastructure, Q4 2015 (n=568)
- 18. DevOps tools in use still vary widely 18 33.83% 37.31% 39.30% 39.30% 40.80% 40.80% 44.28% 45.77% 51.24% 51.74% 63.18% Infrastructure as a Service Build and continuous integration… Application… Traditional middleware and… Release management Platform as a Service QA planning and automation tools Configuration management &… Performance Monitoring and… Project management tools Testing Source: 451 Research/Red Hat, Q1 2016, n=201
- 19. Release speed still lags demand 19 Source: 451 Research/Red Hat, Q1 2016, n=201 6% 28% 34% 23% 3% 1% 3% 0% 0% 5% 10% 15% 20% 25% 30% 35% 40%
- 20. Enter containers: The future of virtualization
- 21. 21 Aren’t they just like VMs? No. Source: 451 Research, “Now Shipping: The Docker and containers ecosystem rapidly takes shape”
- 22. Containers vs VMs: no clear approach 22 451 Research, Voice of the Enterprise: Software-Defined Infrastructure, Q4 2015 10.9% 14.6% 9.0% Containers Run Separately from VMs Containers Run On Top Of VMs Containers Are Replacing VMs n = 458
- 25. 56.1% 10.7% 3.9% 4.2% 2.1% 22.9% 31.5% 10.2% 8.4% 9.4% 4.7% 35.8% 19.1% 10.0% 6.7% 9.5% 4.6% 50.1% Discovery and Evaluation Running Trials/Pilot Projects In Test and Development Environment Initial Implementation of Production Applications Broad Implementation of Production Applications No Plans Q1 2015 Q3 2015 Q1 2016 Docker is not just a toy 25 14.1%} Source: 451 Voice of the Enterprise: Cloud; 1Q15 n=991; 3Q15 n=960; 1Q16 n=461 of cloud-using orgs Prod in 1Q16:
- 26. Fragmentation drives microservices — enabled by containers 26
- 27. 27 Loosely coupled services “ The only communication allowed [at Amazon] is via service interface calls over the network.” – Steve Yegge, Google, Oct 2011, paraphrasing Jeff Bezos memo https://plus.google.com/+RipRowan/posts/eVeouesvaVX
- 28. Loosely coupled teams “ One of the biggest changes is that we no longer have an official ‘architecture’ team. Instead, we have made ‘architecture’ an ‘ingredient’ on each of our teams.” 28 http://tech.gilt.com/post/102628539834/making-architecture-work-in-microservice – Lauri Apple, Gilt Groupe, 14 Nov 2014
- 29. Container management & orchestration: The foundation of microservices 29
- 30. Kubernetes seeing the most developer traction 30
- 32. Container orchestration is limited (∴ adoption immature) 32 451 Research, Voice of the Enterprise: Cloud, Q3 2015 9.4% 36.1% 39.9% 14.6% Currently use Considering using in the next two years Not familiar with these tools Have no plans to use in the next two years n = 534
- 33. Complexity is the new normal 33
- 34. REA microservices timeline 34 0 20 40 60 0 6 12 18 24 Microservices Months http://yowconference.com.au/slides/yow2014/SkurrieBottcherEvans-MonolithsToMicroservices.pdf “ Microservices is a long term strategy.” – Evan Bottcher, ThoughtWorks/REA, 9 Dec 2014
- 35. From primitive to framework 35
- 36. The cloud-native movement is just about to take off 36 32% 32% 13% 13% 9% Developing and running web-based applications Migrating legacy workloads and applications to the cloud Developing and running cloud native applications Managing legacy workloads, applications and assets on the cloud Testing new technologies and methods Source: 451 Research/Red Hat, Q1 2016, n=201
- 37. From primitive to framework to platforms 37 FaaS (Serverless) PaaS IaaS CaaS Config mgmt Container orch VMs Containers OpinionatedFlexible
- 38. 38 How can you DevOps … if there are no servers? “ Operations is the sum of all of the skills, knowledge and values that your company has built up around the practice of shipping and maintaining quality systems and software.” – Charity Majors, May 2016
- 39. How? DevOps (Culture, Automation, Measurement) What? Microservices Why? Survival 39
- 40. 40 Thank you! Donnie Berkholz Twitter: @dberkholz donnie.berkholz@451research.com
- 41. Some content from this presentation is Creative-Commons licensed. https://creativecommons.org/licenses/by-sa/ https://creativecommons.org/licenses/by/ 41
- 42. Minimizing risk, maximizing agility Architecture: Microservices, composable monitoring Code: Continuous integration, feature flags Servers: Continuous delivery, infrastructure as code Services: Rolling updates, resilience engineering Product: Continuous deployment, restricted audience 42
Hinweis der Redaktion
- Q: “Allocate 100 points among the following five goals as they relate to your company or organization?” Overall business goals Enabled by cloud, open source, self-service IT
- Languages, databases, frameworks … What’s driving the way we build technology?
- OODA loops
- Culture: Collaboration, Sharing Automation: Digital Measurement: KPIs As compared to ITIL: push down authority, plan iteratively, peer review, collaboration, automation
- Why? Empathy drives quality Internal customers Barriers slow delivery
- Why? Replicable – env parity Scalable Accelerated
- Configuration management CFEngine 1.0: 1993
- Developers vs DevOps Release management – quarters to weeks to days to hours Gary Gruver, HP Little’s Law – work in system proportional to arrival speed plus time in system. Reduce batch sizes. Lean.
- For cloud users: In general how would you describe your organization’s workload or service provisioning process?
- Why? Can’t improve what you can’t measure Cattle vs pets (scale, transience) Nagios (NetSaint): 1999 (MN co) Community, UX
- Overall 65.1%
- Overall 39.6%
- Data, not just code Note this is screened for DevOps-leaning audience Most orgs doing testing, but few automated pipelines
- Q: “Approximately how often do you deploy software applications to production?” Audience: People influential in cloud-services development
- The next step in DevOps How do we cope with these demands for agility, scalability, automation, transience?
- Q30. What is your organization’s strategy (if any) around the use of containers (e.g. Docker)? How does this change the infrastructure you’ve invested in for virtualization?
- VotE shows most orgs are largely moved to virtualization, a minority to automation, few to orchestration/private cloud Immutable infrastructure
- Make sure to clarify difference between Docker and K8s
- Of cloud-using orgs
- Business-defined separations. Bounded context based on cross-organizational empathy. Steve Yegge memo — Amazon must be SOA, or you’re fired.
- DevOps + microservices Bounded contexts, empathy defined DevOps is how you build and run microservices.
- Nomad out of HashiCorp, new competitor to Mesos/Kubernetes Azure Container Service, building on Docker & Mesos. Beta by EOY 2015 Also note PaaS providers moving to containers
- Make sure to clarify difference between Docker and K8s
- Windows catching up quickly with DevOps and containers No need to leave the Microsoft half of your environment behind
- Q16. What are your organization’s plans regarding a container orchestration tool?
- Also note PaaS providers moving to containers
- Q: “What are the top two uses of cloud-based platforms in your organization?” Audience: Those responsible for or influencing cloud-services decisions
- Most private PaaS options have bought into containers at this point
- Business-defined separations. Bounded context based on cross-organizational empathy. Steve Yegge memo — Amazon must be SOA, or you’re fired.
- The future of service delivery.
- DevOpsDays Minneapolis, July 20-21. $249, or $199 if you’re a startup, self-financed, etc