DevOps Transformations: Structuring Approaches to Change
-
Upload
ranger4-limited -
Category
Technology
-
view
288 -
download
0
Transcript of DevOps Transformations: Structuring Approaches to Change
www.ranger4.com
DevOpstastic
DevOps Transformations: Structuring approaches to
change
9th June 2015
Helen BealRanger4
@helenranger4
www.ranger4.com
DevOpstastic
1. Release on demand5 DevOps Goals
2. Eliminate technical debt
3. Fail smart
4. Look outside-in
5. Measure feature value
www.ranger4.com
DevOpstastic
Release and Deployment Management Maturity
Level 1 Level 2 Level 3 Level 4 Level 5Manual Packaged Scripted Complex On DemandBespoke, unpractised process. Authorization and sign off incidental. Roll back via back up copy or scripts.
Some packages (e.g. MSIs) and scripts. Release authorization considered.
Multiple scripts allowing automation. Can deploy to multiple parts of route to live. Possible roll back through redeployment. Some version control.
Can deploy composite applications. Role based security available. Multiple platforms services through single interface.
Push button deployments when code is ready – continuous delivery and deployment achieved. Full auditability and compliance.
www.ranger4.com
DevOpstastic
CONSISTENCY & VISIBILITY• Create a consistent process across all environments• Validate through development and QA• Obtain ‘license’ to deploy to production
CONTROL & GOVERNANCE• Implement an audited process for deployment• Make all environments visible, but control who can do what
INTEGRATION ACROSS THE LIFECYCLE• Linked data – no more spreadsheets of links and references• Track changes and deploy what is needed at the right time• Create an executable plan and track delivery progress
www.ranger4.com
DevOpstastic
SHIFT LEFT• Earlier testing• More risk mitigated • Defects cost significantly less to find and fix
REDUCED TEST ENVIRONMENT COSTS• Reduced overhead on physical resources and support• Reduced overhead building test environments
INCREASED QUALITY• More defects fixed; fewer production defects• Integration defects carry the most risk in modern software
solutions. Validate the integration well before end to end testing is possible.
www.ranger4.com
DevOpstastic
Case Study: Banking Industry ~120 interfaces
10
160k
96K110
160
205
60K
34 4
5
322
10.3
www.ranger4.com
DevOpstastic
CA
QuestHP
OpTier
Opnet
IBM
Compuware
Oracle
MicrosoftSL
Inetco
NetScout
eG InnovationsProgress
ASG
IderaVisual networks
Info vista
Network Instruments
Knoa
Aternity
Coradient
CorrelsenseNastel
dynaTracePrecise
Arctures Technologies
BMC
Managed Engine
New RelicAppDynamics
2011Riverbed
OpTier
2012
AppNeta
Dell
2013
Gartner APM Magic Quadrant
www.ranger4.com
DevOpstastic
Dev
route to live
Test QA Prod
Deploy your application at any time, at high speed
www.ranger4.com
DevOpstastic
Dev
route to live
Test QA Prod
Deploy your application at any time, at high speed
!
Be pre-emptively alerted to performance issues/outages
www.ranger4.com
DevOpstastic
Dev
route to live
Test QA Prod
Deploy your application at any time, at high speed
Be pre-emptively alerted to performance issues/outages
Redeploy last known working version instantly, fix, test, redeploy
www.ranger4.com
DevOpstastic
Requirements Management Maturity
Level 1 Level 2 Level 3 Level 4 Level 5Written Requirements
Organized Structured Traced Integrated
Documented and shared, regular collaboration between teams, backup and restore enabled
Formatted consistently, stored and secured. Version tracked and easily accessible to those with rights
Types (e.g. functional/non-functional) are specified. Attributes and prioritization is applied. Querying and filtering is possible.
Determine and track requirements relationships, has a hierachy of requirements: user needs, features and use cases. Coverage analysis reports implemented.
Requirements management fully integrated with software development environment: used directly in design, development, change tracking, testing and PM.
www.ranger4.com
DevOpstastic
2014 State of DevOps Report
Top Practices Correlated with Deployment Frequency
Continuous DeliveryContinuous delivery ensures that your software is always in a releasable state, turning deployment into a non-event that can be performed on demand.
Use of version control for all production artifactsWhen it’s easy to recreate environments for testing and troubleshooting, throughput goes up.
www.ranger4.com
DevOpstastic
2014 State of DevOps Report
Top Practices Correlated with Lead Time for Changes
Use of version control for all production artifactsThe ability to get changes into production repeatedly in a reliable, low-risk way depends on the comprehensive use of version control.
Automated testingWith a reliable and comprehensive set of automated tests, you can quickly gain confidence that your code is releasable without lengthy integrations and manual regression testing cycles.
www.ranger4.com
DevOpstastic
2014 State of DevOps Report
Top Practices Correlated with Mean Time to Recover (MTTR)
Use of version control for all production artifactsWhen an error is identified in production, you can quickly either redeploy the last good state or fix the problem and roll forward, reducing the time to recover.
Monitoring system and application healthLogging and monitoring systems make it easy to detect failures and identify the events that contributed to them. Proactive monitoring of system health based on threshold and rate-of-change warnings enables us to preemptively detect and mitigate problems.
www.ranger4.com
DevOpstastic
Continuous Delivery
Design & Plan Code Integrat
e Test Release Deploy Operate
Requirements Management
Configuration & Build Management
Project and Portfolio Management
Application Release Automation
Application Performance Management
Artifact Repository
Integration Testing
Performance Testing
Automated Functional Testing
DevOps Toolchains