DevOps vs Traditional IT Ops (DevOps Days ignite talk by Oliver White)

  • 2,134 views
Uploaded on

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 …

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).

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,134
On Slideshare
0
From Embeds
0
Number of Embeds
7

Actions

Shares
Downloads
100
Comments
0
Likes
12

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. DEVOPS VS. TRADITIONAL IT OPS STATS, 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.
  • 2. 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?
  • 3. 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) INFRASTRUCTURE IMPROVEMENTS (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
  • 4. 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.8 3.6 INFRASTRUCTURE IMPROVEMENTS (TEST PROCESSES AND RECOVERY PLANS)
  • 5. 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.4 3.8 SUPPORT (HANDLING SUPPORT FOR OPS INFRASTRUCTURE)
  • 6. DevOps vs. Traditional IT Ops: Firefighting 2.4 3.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.
  • 7. 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).
  • 8. What about failures and recoveries? Average team has 2 app failures per month Recovery time is >30min for over 50% of all respondents.
  • 9. TRADITIONAL IT OPS DEVOPS ORIENTED OVERALL NOT APPLICABLE 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
  • 10. 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
  • 11. But what about releasing software? Surely DevOps can't be THAT much better? Wrong. Ok ok, so DevOps recover faster...
  • 12. 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
  • 13. 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?
  • 14. 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
  • 15. WHAT KINDS OF INFRASTRUCTURE DO YOU USE? GOOD OLD PHYSICAL SERVERS INTERNAL VIRTUALIZATION CLOUD (laaS,PaaS) SaaS ALL THE WAY 65% 63% 8% 35% Let's ask the audience
  • 16. Popular infrastructure config tools POPULAR INFRASTRUCTURE CONFIGURATION TOOLS PUPPET 40% CHEF 31% CFENGINE 4% ANSIBLE 3% FABRIC 3% BASH 6%
  • 17. Popular Test Automation tools POPULAR TEST AUTOMATION TOOLSSELENIUM71% JUNIT22% JMETER11% JENKINS7% SOAPUI RSPEC TESTNG CUCUMBER 6% 5% 5% CUSTOM14% 7%
  • 18. 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!)
  • 19. THANKS FOR YOUR 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 labs@zeroturnaround.com w RebelLabs http://zeroturnaround.com/rebellabs