the reality of cloud services and the new...
TRANSCRIPT
The Reality of Cloud Services and the New Cool
John M. Clark
US IT Service Mgmt Architect
@CyberJMC66, @MicrosoftITSM
Kathleen Wilson
WW Datacenter & Cloud Architect
@mkathleenwilson
Why DevOps … “DevOps is the result of the continuing POOR relationship between Operations, Applications, Infrastructure and Customer
“DevOps is at the very top of the Gartner Hype Cycle – July 2015 Source: Gartner Group, Doc G00278003 (July 2015)
“DevOps is a philosophy vs. a framework. Easier concepts “DevOps has helped
organizations like Microsoft change how applications and services are created, updated, and operated
Why DevOps …
How much high performance DevOps organizations are outperforming the traditional enterprise counter parts. *Note - from The Phoenix Project
DevOps Is… “DevOps is development and operations collaboration”
“DevOps treats your infrastructure
as code”
“DevOps is using automation”
“Kanban for Ops?”
“DevOps is feature
switches”
“DevOps is small deployments”
Traditional Dev and Ops
1. Hardware fails
3. Software has bugs
2. Humans make mistakes
...how you deal with these laws for the cloud vs legacy IT
Is vastly different...
Three “Laws” of a Service Provider (and every IT organization on the planet)
Changing the ITSM Conversation
World Class
Support
Slow, Controlled Change:
Dev, Test, Staging, Production
Failure Mode
Monitoring
IT Team Escalations
Extreme Focus on SLAs and OLAs
Operational Best Practices
Changing the ITSM Conversation
Online Initiated World-class
Support
Constantly Deploying: Deployment
Rings and VIPSwaps
Service Capability
Monitoring
Federated Operations Escalations (Internal and External)
Realization that financial penalties will not make your business whole
Operations Automation And DevOps
Airplanes, Airlines, and Pilots
IT = build, own, maintain, fly your own airplane
Cloud = sit back, relax, and enjoy the flight ...even if you are a pilot...
Two Different Worlds
Two Different Worlds
Two Different Worlds
Two Different Worlds
https://www.microsoft.com/en-
us/download/details.aspx?id=46920
DEVOPS Evolution in Office
Manual = Bug
App Eng owns more of the stack (e.g.
Storage design)
App/Service anticipates
downstream failures (smap)
Monitoring IP owned by
engineering Major Incidents an opportunity
to drive improvements
Change is a Reality...enable
it (constant deployments)
Rollback vs Roll Forward
Every call to support =
Bug
Monitoring Considerations
Major Incident Considerations
Change and Release Considerations
Service Quality Considerations
Summing it all up in two points
ROLE PLAY SAFE WORD IS “SPARKLE” WE WILL NEED SOME VOLUNTEERS???
What changes
Happy DevOps
DEV OPS Production
Resources
• Modern Service Management LinkedIn Group
• @MicrosoftITSM
• Channel 9 and Microsoft Virtual Academy Modern DevOps to ITIL, Creating a Lifecycle for Service Management
• PuppetLabs State of DevOps Report 2014
• The Phoenix Project
Thank you for attending this session.
Please don’t forget to complete a session evaluation on the conference app.