optimising devops: introduction
DESCRIPTION
An overview of our trio of DevOps trio of tools for change as well as an into to DevOps.TRANSCRIPT
www.ranger4.com
DevOpstastic
Optimising DevOps
www.ranger4.com
DevOpstastic
people process tools
cultureinteraction
sautomatio
n
1 2 3
www.ranger4.com
DevOpstastic
A DevOps Maturity Model
1
5
4
3
2
DevOpsDONE
Optimising DevOps
Starting DevOps
Fundamental DevOps
Not started DevOps
Fine tuning, tied tightly to business goals, innovation delivered to market
on demand
Automated build, cross-functional teams, product-focused, cultural
change happening
Thinking about cultural change, starting to write scripts, looking at test
automation
Outages, war-rooms, blame, unplanned work, delays and defects
Happy people with integrated toolchain to pre-empt failure, automate test and
deployment – Continuous Delivery
www.ranger4.com
DevOpstastic
Deplo
y
Arc
hit
ect
ure
and
Pro
cess
Modelin
g
Develo
pm
ent
Build
Requir
em
ents
G
ath
eri
ng a
nd
Managem
ent
Test
ing
Rele
ase
Configura
tion
APM
Software Development LifeCycle
DevOps Toolchain for Continuous Delivery
Plan Design Implement Maintain
Development Operations
www.ranger4.com
DevOpstastic
“IT performance is measured in terms of throughput and stability, two attributes
that seem to be opposed, yet are both essential to achieving IT that’s a real strategic asset.
The individual measures that make up IT performance are…”
2014 State of DevOps Report
www.ranger4.com
DevOpstastic
1. Deployment frequency
2. Lead time for changes
3. MTTR2014 State of DevOps Report
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
Deplo
y
Test
ing
Rele
ase
APM
The core components of optimized DevOps
www.ranger4.com
DevOpstastic
WHY?
www.ranger4.com
DevOpstastic
Dev
route to live
Test QA Prod
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
BeDevOpstastic