The future of (Windows) operations #WinOps #DevOps
Download as PPTX, PDF1 like470 views
DevOpsGuys co-founder Steve Thair talks about the impact DevOps automation and Cloud Technologies will have on IT operations, and how you can change your skills to remain relevant
Ad
More Related Content
What's hot (20)
Similar to The future of (Windows) operations #WinOps #DevOps (20)
Ad
More from DevOpsGroup (20)
Ad
Recently uploaded (20)
The future of (Windows) operations #WinOps #DevOps
- 1. www.devopsguys.com | Phone: 0800 368 7378 | e-mail: [email protected] | 2017 The Future of (Windows) Operations How will the Ops role change in a Cloud & DevOps world?
- 4. 4#WinOps @DevOpsGuys#WinOps @DevOpsGuys http://www.bbc.co.uk/news/technology-34066941
- 5. 5#WinOps @DevOpsGuys#WinOps @DevOpsGuys Manages Ops Servers Manages Ops Manages Servers / PaaS / Containers Trains the AI Ops Manages “Orchestrator” Servers / PaaS / Containers Manages AI “Orchestrator” Traditiona l Cloud Native Future State
- 6. 6#WinOps @DevOpsGuys 40 400 2500 0 500 1000 1500 2000 2500 3000 Traditional IT DevOps IaaS (legacy app) DevOps Cloud Native Admin/Server Ratio Admin/Server Ratio The Admin / “Server” ratio FutureState 10x ? AI Ops
- 7. 7#WinOps @DevOpsGuys#WinOps @DevOpsGuys “Historically, wholesale job retraining has been challenging to scale, but the inexorable nature of this transition demands that we try to help them be productive in an even more digitized world economy.” – Cathy Engelbert, CEO, Deloitte
- 9. 9#WinOps @DevOpsGuys Hosting Platform Team Security & Compliance Platform Team Monitoring & Alerting Platform Team DevOps & CI Platform Team DevOps Platform Teams provide self-service capabilities for Delivery Teams Triage/SRE Team Customer Service Desk Platform-as-a-Service / “Self-Service” model Shared Git Repo Maintainers Sharedtemplates andbestpractice Product Delivery Team 1 Test Automation Platform Team “xyz” Platform Team Product Delivery Team 2 Product Delivery Team ‘n’ EnablementServices EnablementServiceshelptransform DeliveryteamstoAgileand DevOpsModelssotheycanusethe platformserviceseffectively Enterprise Shared Source Model
- 10. What does the Future look like Part 1 – A different Mindset
- 12. 14#WinOps @DevOpsGuys#WinOps @DevOpsGuys “"The concept from the engineering standpoint is the evolution of the engineering scientist, i.e., the scientific generalist who maintains a broad outlook. The method is that of the team approach. On large-scale-system problems, teams of scientists and engineers, generalists as well as specialists, exert their joint efforts to find a solution and physically realize it...The technique has been variously called the systems approach or the team development method” - Harry H. Goode & Robert E. Machol, 1957.”
- 14. 16#WinOps @DevOpsGuys Think Vertical Not Horizontal
- 15. 17#WinOps @DevOpsGuys#WinOps @DevOpsGuys Vertical vs Horizontal Slicing horizontally Slicing Vertically Traditional “silos of experts” model DevOps-enabled Product Team Middle-Tier Front-end Back-end TESTS Middle-Tier Front-end Back-end TESTS
- 16. 18#WinOps @DevOpsGuys Think T Not I* http://www.scrumexpert.com/knowledge/t-shaped-skills-and-swarming-make-for-flexible-scrum-and-a
- 20. What does the Future look like Part 2 – Changing the WAY we work
- 23. 25#WinOps @DevOpsGuys Cloud Adoption Frameworks (CAF’s)
- 26. 28#WinOps @DevOpsGuys#WinOps @DevOpsGuys To Do Some Stuff to Do Ready Stuff Ready to Action In- Progress This is what I’m doing right now! Done Done and signed off by everyone. “Done Done.” Sticky Label Design "© Copyright Showeet.com" And it’ll be done when it’s done… So stop bugging me for status updates and go check the board…
- 29. 31#WinOps @DevOpsGuys This isn’t an easy Transformation… From… Key Success Factor To… Command & Control Management Style Autonomous Conservative Attitude to Change Experimental Silo Organisation Structure Collaborative Project-focussed Delivery Focus Product-centric Waterfall Delivery Model Iterative (Agile) Large (Huge) Batch size Smallest possible Monolithic Systems Architecture Loosely coupled Proprietary Technology Open (Source) Manual Processes Automated
- 31. What does the Future look like Part 3 – A focus on Outcomes and metrics
- 32. 34 Driving Experimentation We believe: Will result in: Increased test automation Improved IT Performance We will have the confidence to proceed when: We see a measurable improvement in Change Fail Rate and MTTR We believe: Will result in: <this capability> <this outcome> We will have the confidence to proceed when: <we see a measurable signal> Hypothesis-driven development: Barry O’Reilly: http://barryoreilly.com/2013/10/21/how-to-implement-hypothesis-driven- development/
- 33. 35 Outcome focus Test Automation Version Control Deployment Automation IT Performance (Speed & Stability) Deployment Frequency Lead time for change MTTR Change fail rate % Total test coverage Unit test coverage % Application code in VC % App config code in VC % Infrastructure code in VC % Deployments Automated
- 34. 36 3 Levels of Measurement • Customer Satisfaction – measure what matters to them (and not what you THINK matters to them) • Capability – internal capability measures aligned to customer demands • Process – measuring the value stream of processes that create that capability “The Vanguard Guide to Using Measures for Performance Improvement” (2001)
- 35. 37 Example of metrics Customer Need Customer Measure Capability Metric Process Metrics • Features delivered quickly • % Feature delivered as agreed • Average Lead Time • % availability of Test environments • % of re-work required • Monthly cloud hosting spend
- 36. 38#WinOps @DevOpsGuys 4 Most Commonly Cited DevOps Metrics • Deployment Frequency • MTTR – Mean Time to Recover • Change Failure Rate • Lead Time & Process Time 2016 State of DevOps Report | presented by Puppet + DORA Wait Time Process Time Lead Time (Start to Finish)
- 37. 39#WinOps @DevOpsGuys Goodhart’s Law “When a measure becomes a target, it ceases to be a good measure.” “If a measurement can’t be used to improve the system (via feedback) then it’s useless” – Steve’s Corollary https://en.wikipedia.org/wiki/Goodhart%27s_law
- 38. What does the Future look like Part 4 – What does this all mean for Windows Ops?
- 40. 42#WinOps @DevOpsGuys Server Core + Powershell = ? Windows Server Core “GUI” Powershell ( & DSC)
- 41. 43#WinOps @DevOpsGuys#WinOps @DevOpsGuys “DSC represents a massive change in how Windows administrators think about their entire environment. Provided every configuration setting can be boiled down to a DSC setting – which will be true over time – then “administration” will essentially become “intelligent editing of text files.”“ 23 April 2018 Why DSC is the future? 43 “DSC represents a massive change in how Windows administrators think about their entire environment. Provided every configuration setting can be boiled down to a DSC setting – which will be true over time – then “administration” will essentially become “intelligent editing of text files.”“ Jones & Murawski “The DSC Book” https://onedrive.live.com/?cid=7F868AA697B937FE&id=7F868AA697B937FE%21110 AKA Unix Admin
- 42. 44#WinOps @DevOpsGuys Package Management is key
- 44. 46#WinOps @DevOpsGuys Cloud & Hybrid
- 45. What does the Future look like Summary
- 46. 48#WinOps @DevOpsGuys To Summarise • Automation & Cloud will severely impact IT Operations • We will have to change how we think • We will have to change how we work • We will have to change how we measure success • We will have to change the tools we use • So get started on re-training now!
- 48. 50#WinOps @DevOpsGuys About DevOpsGuys • Founded 2013 • 84 Staff • 30+ Clients • Headquartered in Cardiff, Wales • Established as thought leaders in DevOps • Quoted by Gartner and Forrester in research • Microsoft customer advisory board for DevOps “DevOpsGuys are luminaries in the UK DevOps space.” Gene Kim, Author – “The Phoenix Project”
Editor's Notes
- #3: Last month the CEO of Deloitte Cathy Engelbert posted this article onto LinkedIn. It pretty much sums up the “mainstream” argument that the coming disrumption to “white & blue collar jobs” from automation will be “OK”
- #4: The industrial and mining heartlands of the UK are still the areas with the highest unemployment nearly 40 years after the decline of coal mining and major industrial centres.,
- #5: Frey & Osborne study
- #6: Orchestrators = Kubernetes / Mesos DC/OS / Service Fabric
- #7: DEVOPS encourages Operations to take a different attitude towards server infrastructure – moving away from uniquely-configured “snowflake” servers towards automated, mass-produced, nameless servers. This is often referred to as treating your servers as “Cattle, not pets” – if a server is sick, just get rid of it and provision another, don’t waste time nursing it back to health. This approach, powered by new DevOps automation tools, means that a given server administrator can now manage far more servers than before – from a rule of thumb of 40:1 ratio for physical servers to up to 400:1 to 2500:1 for large-scale cloud environments. Similarly, adopting a “microservices” software architecture pattern can increase the number of services (and servers) an administrator is expected to manage. All of this drives cloud adoption , particularly when the relative economics (£0.012/hr for the smallest Azure A0 instance compared to ~£40/hr for a mid-level engineer on £50K/yr, a 3300x ratio) emphasise the human cost, not the server costs. Smashing the server/admin ratio is a key step is driving the cloud adoption return-on-investment. G5 32 Core 448.00 GB RAM 6,144 GB Storage £7.4456/hr
- #8: Yes it’s difficult… in fact it’s nearly impossible…
- #10: DevOps Topologies Security can be embedded in the “Delivery Team” (what the DevOps Handbook calls a “Feature Team Model”) Security can be part of the “Platform Team” (what the DevOps Handbook calls a “Functional Team Model”) Remember – Platform teams do NOT do Delivery work, they provide “as-a-service” capability to ENABLE Delivery teams to deliver better software, faster.
- #11: DEVOPS encourages Operations to take a different attitude towards server infrastructure – moving away from uniquely-configured “snowflake” servers towards automated, mass-produced, nameless servers. This is often referred to as treating your servers as “Cattle, not pets” – if a server is sick, just get rid of it and provision another, don’t waste time nursing it back to health. This approach, powered by new DevOps automation tools, means that a given server administrator can now manage far more servers than before – from a rule of thumb of 40:1 ratio for physical servers to up to 400:1 to 2500:1 for large-scale cloud environments. Similarly, adopting a “microservices” software architecture pattern can increase the number of services (and servers) an administrator is expected to manage. All of this drives cloud adoption , particularly when the relative economics (£0.012/hr for the smallest Azure A0 instance compared to ~£40/hr for a mid-level engineer on £50K/yr, a 3300x ratio) emphasise the human cost, not the server costs. Smashing the server/admin ratio is a key step is driving the cloud adoption return-on-investment. G5 32 Core 448.00 GB RAM 6,144 GB Storage £7.4456/hr
- #15: We need to become systems engineers who look at the whole end to end flow.
- #22: Even Azure Stack – hybrid – you don’t get to touch the hardware – the vendor does that for you?
- #24: Incident versus Problem – just killing and re-spawning Roles not job descriptions etc. They way we do things all around the circle is going to change -
- #25: If you want to learn more attend Kathleen’s talk at 1615 in the Microsoft track.
- #44: Not just a huge number of ini files in /etc directory but it’s all moving to CODE. DSL’s like DSC.
- #45: Package management is nothing new to Linux Chocolatery or OneGet
- #46: Pizza hut example – dynamics scalability
- #51: We were co-founded by 2 experienced technologists, with a track record of delivering results at enterprise scale.