Click here to load reader
Upload
zeroturnaround
View
3.014
Download
1
Embed Size (px)
DESCRIPTION
This is a 5-min version of RebelLabs IT Ops / DevOps Productivity Report" (http://zeroturnaround.com/rebellabs/rebel-labs-release-it-ops-devops-productivity-report-2013/) presented at DevOps Days in Paris, Austin, Berlin and Silicon Valley by Oliver White (@TheOTown).
Citation preview
DEVOPS VS. TRADITIONAL IT OPSSTATS, NUMBERS AND CONCLUSIONS
BY ZEROTURNAROUND
Oliver White (@theotown)Head of RebelLabs, ZeroTurnaround
A 5-MIN IGNITE TALK ABOUT HOW DEVOPS BEATS TRADITIONAL IT OPS, EVERY TIME.
Traditionally siloed team structures don't scale
Oppositng philosophies (Dev <3 change, Ops <3 stability)
Continuously evolving technologies & needs require more flexibility
Reminder: why we want DevOps
How do DevOps teams spend their time each week, compared to Traditional IT Ops teams?
DEVOPS ORIENTED TRADITIONAL IT OPS
2.8
3.1
3.8
5.1
2.4
4.8
3.5
5.3
4.0
2.4
2.7
4.8
7.2
3.8
3.6
3.8
4.6
4.5
TRADITIONAL IT OPS VS. DEVOPS COMPARED
OVERHEAD(SOCIALIZING, BRAINSTORMING,
DAYDREAMING, PROCRASTINATING)
SELF-IMPROVEMENT(TRAINING, READING, EDUCATION)
FIREFIGHTING(E.G. MISSION CRITICAL
FAILURE RECOVERY)
COMMUNICATION(MEETINGS, EMAILS, PLANNING, ETC.)
SUPPORT(HANDLING SUPPORT FOR OPS
INFRASTRUCTURE)
INFRASTRUCTUREIMPROVEMENTS
(TEST PROCESSES AND RECOVERY PLANS)
INFRASTRUCTURE MANAGEMENT(REVIEWING EVOLVING
INFRASTRUCTURE NEEDS)
AUTOMATING REPETITIVE TASKS(WRITING SCRIPTS/USING
AUTOMATION TOOLS)
DEPLOYING CHANGES(APP, DB, CONFIG & INFRA UPDATES)
DevOps vs. Traditional IT Ops: Overall work week
DevOps vs. Traditional IT Ops: Infrastructure improvements
What they're doing: testing processes and recovery plans and making sure these things work
DEVOPS SPENDS 33% MORE TIME IMPROVING INFRASTRUCTURE AGAINST FAILURES
4.83.6
INFRASTRUCTUREIMPROVEMENTS
(TEST PROCESSES AND RECOVERY PLANS)
DevOps vs. Traditional IT Ops: Handling Support
What they're doing: Handling support cases for operations infrastructure - i.e. when things go wrong
TRADITIONAL IT OPS REQUIRE NEARLY 60% MORE TIME PER WEEK TO HANDLE SPPORT CASES.
2.43.8
SUPPORT(HANDLING SUPPORT FOR OPS
INFRASTRUCTURE)
DevOps vs. Traditional IT Ops: Firefighting
2.43.8
SUPPORT(HANDLING SUPPORT FOR OPS
INFRASTRUCTURE)
What they're doing: dropping everything to recover from failures or fix something urgently
DEVOPS SPENDS ABOUT 21% LESS TIME PUTTING OUT FIRES ON A WEEKLY BASIS.
DevOps wins!
21% less time putting out fires 37% less time handling support cases
With that extra time, DevOps spends 33% more time improving infrastructure, and they even spend 15% more time on self-improvement (education, training).
What about failures and recoveries?
Average team has 2 app failures per month
Recovery time is >30min for over 50% of all respondents.
TRADITIONALIT OPS
DEVOPSORIENTED
OVERALL
NOTAPPLICABLE
60+ MIN
30-60 MIN
10-30 MIN
0-10 MIN
8%7%
9%
40%22%
28%
22%30%
27%
24%30%
24%
6%11%11%
HOW LONG DO RECOVERIES TAKE?
DevOps vs. Traditional IT Ops: Firefighting
71% of DevOps teams can recover
from failures in < 60min
40% of traditional IT Ops teams need >1 hr to recover
DevOps vs. Traditional IT Ops: Firefighting
Traditional IT Ops teams are almost 2x more likely to require 60+ minutes to recover
Recoveries in <30 minutes are 33% more likely for DevOps teams than traditional IT Ops
But what about releasing software?
Surely DevOps can't be THAT much better?
Wrong.
Ok ok, so DevOps recover faster...
Boom!
DevOps teams need less than HALF THE TIME to release an application version (36.6 min vs. 85.1 min).
Average
Median
Standard Deviation
85.1
30
113.6
36.6
15
48.5
TIME IN MINUTES
TRADITIONAL IT OPS
DEVOPS ORIENTED
DevOps spends more time on improving things and less time fixing things DevOps recovers from failures faster DevOps releases apps more than twice as fast
Quick summary so far...
Hmmm, maybe it's in the tools they are using?
Top tools and technologies used by DevOps and IT Ops teams
Top Ranked Productivity Tools & Technologies 2013
77%SHELL SCRIPTS
71%SELENIUM
63%VI/VIM
51%NAGIOS
40%PUPPET
34%PYTHON
31%CHEF
WHAT KINDS OF INFRASTRUCTURE DO YOU USE?
GOOD OLD PHYSICAL SERVERS
INTERNALVIRTUALIZATION
CLOUD(laaS,PaaS)
SaaS ALL THE WAY
65%
63%
8%
35%
Let's ask the audience
Popular infrastructure config tools
POPULAR INFRASTRUCTURE CONFIGURATION TOOLS
PUPPET 40%
CHEF 31%
CFENGINE 4%
ANSIBLE 3%
FABRIC 3%
BASH 6%
Popular Test Automation tools
POPULAR TEST AUTOMATION TOOLSSE
LEN
IUM
71%
JUN
IT22
%
JMET
ER11
%
JEN
KIN
S7%
SOA
PUI
RSPE
C
TEST
NG
CUCU
MBE
R
6% 5% 5%
CUST
OM
14% 7%
Most app failures still occur due to software quality or lack of automation Most teams have <10% of their infrastructure configured with code (i.e. using Puppet, Chef)
Most teams have <10% of their smoke tests automated
Most teams don't test their recovery processes.
DevOps clearly wins, but still isn't perfect (hey!)
THANKS FORYOUR ATTENTION!Psst: For the full report in pdf, give us a business card or your details and we'll send it to you
BY ZEROTURNAROUND
RebelLabs
http://zeroturnaround.com/rebellabs