The Devops Journey: Disrupt or Be Disrupted
The Devops Journey: Disrupt or Be Disrupted
The Devops Journey: Disrupt or Be Disrupted
Disrupt or be Disrupted
Cosmo Schillaci, IBM
[email protected]
Delay
Delay
Delay
Delay
Lack of
Trust
Successful transformations span all layers
Changing the
People culture is a
differentiator
Manage Deliver
Automate monitoring Deliver continuously using a
Enable fast recovery automated pipeline
Be resilient Automate deployments
Run
Automate operations
Build high availability
infrastructure
Dark launches and feature
toggles
Auto-scale
15
Automate & SHIFT LEFT!
Accelerate Delivery
Minimal Viable Product
17
Continuous Delivery
18
Continuous Delivery
Automate Deployment
1. Integrate build automation with deployment automation
Successful build starts deployment process
2. Use a consistent deployment process
Use the same process across all environments - test to production
3. Leverage canary deployments
Limit risk exposure to the business
19
Continuous Delivery
Test Continuously
1. Include test automation as part of deployment process
Deploy process kickoff automated tests for immediate feedback
2. Shift left with service virtualization to test earlier
Simulate dependencies; Test what you want, when you want, how you want.
3. Test across all channels
API, functional, performance, security test automation
20
Continuous Delivery
21
Continuous Delivery
Release Management
1. Manage the deployment of change across environments
Execute manual and automated deployment steps without delay
2. Release together what has been tested together
Ensure quality criteria has been met in each test environment
3. Log release actions for audibility and compliance
Automatically capture the who, what, when, where, result outcomes
22
Wrapping up!
23
High Performers are realizing
2016 State of DevOps report
24x faster recovery
from failures
95% $2.3M
implementation
time by
avoidance of
over
on a single
application
items of mobile
8x 4 hours
integration testing
time from 3 weeks to