what is devops, really?

What Is DevOps, Really?Josh Olson

Senior Consultant

josholson490

joshua.olson@ilmservice.com

jolson490

www.ilmservice.com

Sean EppingPrincipal Consultantsean.epping@ilmservice.com

seanepping

@seanepping

Goals

1. Discover DevOps’ business value2. Understand what DevOps is3. How to get started with DevOps

(Figure 1)

The Continuous Improvement Feedback Loop

• DevOps = short, efficient, & fast loop

(Amazon, 2015)

DevOps’ Business Value: Backed With Hard Data

(Puppet Labs, 2016)

• Performance difference: Traditional vs DevOps• 4,600 technical professionals surveyed worldwide

• Wide variety of roles, departments, industries, company & infrastructure sizes

• Outliers (unicorn companies) excluded

Lead Time

• Lead Time: 3.5 months vs 1 hour• Deliver more value sooner

Deployment Frequency

• Deployment Frequency: 1.7 months vs 4x day• Less risk• Feedback sooner

Failure Rate

• Changes that cause an outage: 23% vs 7.5%• Get more done – and with less errors

Failure Recovery

• Recovery time: 1 day vs 1 hour

The DevOps Difference

• Ops: less pager calls at 3am• Devs: write more code• More fun – and deliver more value

(Figure 2)

“Show Me the Money!”

• Silverpop/IBM: Automating Deployments yields Savings

• Etsy: DevOps Increased RevenueYear Initiative Sales Increase Visitors Increase

2009 Automated deployments $90M (by 103% to $177M) 96% (to 320M)

2010 Standardized infrastructure & configurations $130M (by 73% to $307M) 66% (to 534M)

2011 Eliminating non-standard technologies $219M (by 71% to $526M) 67% (to 895M)

Before DevOps• 12-18 people for 8+ hours• 400 manual steps• Inconsistent error-prone

process

With DevOps• 5 minute deployments• Zero downtime• $1M annual savings

(IBM, 2015)

(IT Revolution, 2012)

Increasing Value of DevOps

• Compounding (e.g. 7.3x more deployments in year)• Get started this year

So What is DevOps?

(Figure 3)

What DevOps is

• “software DEVelopment” + “information technology OPerationS”• Devs: software• Ops: infrastructure

• Better tools – but beware...

(Figure 4)

Don't Get Duped

(Figure 5)

DevOps: Not on a Shelf

Using Agile to Dispel DevOps Myths

Myths• DevOps engineer• “Jack of all trades, master of none”• More interruptions

Truths• DevOps evangelist & team

• Still specialists

• Reclaim time

(Figure 6)

Agile & DevOps

(Figure 7)

• Concepts for how to create technology

Agile

(Figure 8)

DevOps = Agile into Ops

• Both have similar principles• Speed, collaboration, transparency

• DevOps extends “done”• Everyone gets to party at the end!

CAMS (DevOps Core Values)

• Culture• Automation• Measurement• Sharing

(John Willis, Chef 2010)

Culture traditionally between Devs and Ops…

Without DevOps: Divided Culture

• But what you want is…

(Figure 9)

DevOps Culture: Teamwork

• How do you get there…

(Figure 10)

Traditionally: Features vs Stability

• Why change is needed: moving faster and scaling up

(Figure 11)

DevOps: Features AND Stability

• How to tear down the wall…

(John Willis, IT Revolution 2012)

DevOps Culture: Increased Collaboration

• “Report It” “Fix It” (collaboration & shared responsibility)• Ops help Devs design environment from beginning• Devs help Ops support Prod

• Eliminate “Us vs. Them” mentality

(Figure 12)

Automation: Pets vs Cattle (Owning vs Renting)

• Indispensable• Manually uniquely crafted• Personal attachment• Named

(Traditional) (DevOps)

• Expendable• Automated & consistently built• No nurturing• Numbered

(Figure 13)

Automation: The 3 C's (CI/CD)

• Need automated testing• Which CD is best?

• “It depends” - do what’s best for your organization• Both minimize time spent not delivering value

(Figure 14)

Automation: Infrastructure as Code

• Versioning environments

• Consistent & repeatable• DevSecOps: security as code

(Figure 15)

Better Together

• Fantastic Four• DevOps• The Cloud• Microservices (modularity)• Containers (virtualization)

• 1 OS to rule them all – unlike VMs• Infrastructure as code – e.g. Dockerfile• Eliminate WOMM (Works on My Machine)

• No wrong recipe• Any number of them• No pre-requisites• Implement each incrementally

(Figure 16)

Getting Started With DevOps

• Organizational definition of DevOps• ROI Analysis

• Value: more specific than time & $• Cost: training, staff augmentation, tools• Time (“it depends”):

• Automate deployments: e.g. 3 weeks (Pearson VUE, 2014)• DevOps/Containers: ~1 year• Each iteration gets easier: 1, 2, 10, 100, 1K

• Get top-down buy-in(Figure 17)

DevOps ROI: Data From LPS (client of ILM)

• Decrease in daily costs after implementing DevOps in January 2017 to March 12

Summary

1. DevOps brings business value2. What DevOps is

• Collaborative culture• Cross-disciplinary engineering practices• Efficient & integrated tools

3. Get started with DevOps!

(Figure 18)

www.ilmservice.com

Sean EppingPrincipal Consultant

Josh OlsonSenior Consultant

• Thank you!• Q&A

(Figure 19)

josholson490

joshua.olson@ilmservice.com

jolson490

sean.epping@ilmservice.com

seanepping

@seanepping

Resources

• Feedback Loop: (Amazon, 2015): DevOps: A Look at Our Tools and Processes• (Puppet Labs, 2016): 2016 State of DevOps Report

• And other great DevOps resources from Puppet Labs:• Six DevOps myths, busted• Get Started with DevOps: A Guide for IT Managers• How to Build a High-Performing IT Team: Five essential steps to mapping your DevOps journey

• DevOps Business Value: Case Studies• (IBM, 2015) Silverpop/IBM: Automating Deployments yields Savings• (IT Revolution, 2012) Etsy: DevOps Increased Revenue

• CAMS acronym description: (John Willis, Chef 2010), What Devops Means to Me• CAMS image: DEVOPS: HOW A CULTURE OF EMPATHY CREATES MASSIVE PRODUCTIVITY, Telehouse

• Wall of Confusion: (John Willis, IT Revolution 2012): DevOps Culture, IT Revolution

Figures/Images

• Figure 1: goal bridge.jpg• Figure 2: I-Love-My-Job.jpg• Figure 3 (Princess Bride - what DevOps means): Microsoft Virtual Academy: DevOps• Figure 4 (Venn diagram DevOps): DevOps Journey Part II - Version Control• Figure 5 (sold them tools… - Dr. Evil's allies): Agile Memes, Part 1• Figure 6: myth-busted.jpg• Figure 7: logos: Agile (loops.png) & DevOps (cog wheels gears.png)• Figure 8 (roles included in Agile & DevOps): What Is Continuous Delivery: The Last Mile• Figure 9 (worked in Dev…): DevOps: Tear Down that Wall!• Figure 10: Avengers - Together.jpg• Figure 11 (wall between Devs & Ops): VMware DevOps Blogs: What Is DevOps, and Why Should I Care? — The IT Leadership Perspective• Figure 12: removing walls & silos• Figure 13: Pets (puss-in-boots.png) vs Cattle (Pets vs. Cattle: The Elastic Cloud Story - slide 8)• Figure 14 (CI/CD): Continuous Integration, Delivery and Deployment Explained• Figure 15 (versioning code & infrastructure): DevSecOps (slide 11)• Figure 16 (better together - fantastic four): cookies & milk and donut & coffee• Figure 17: Logic – Spok.gif• Figure 18: questions - raised_hands.jpeg

PERIODIC TABLE OF DEVOPS TOOLS (V2)

• Just as an e.g., I circled the tools used in an app I (Josh) created.

VMs vs Containers

• (Virtual machines vs. Docker containers)