XebiaLabs Demonstration forEMC World 2015

May 2015

2 Copyright 2015. Confidential – Distribution prohibited without permission

Agenda

Do you sometimes feel like you’re

fighting against dark forces when

trying to implement DevOps

changes in your

organization? Feel like there’s

some evil entity keeping you from

achieving your DevOps goals?

This talk is designed to address the

fears, reactions and forces that one

faces when trying to implement

organizational change so that

you’re better armed for DevOps

success.

1. Looking at your application Portfolio

2. Tools that will help you achieve Continous Delivery

3. The Cost of NOT implementing Continuous Delivery

3 Copyright 2015. Confidential – Distribution prohibited without permission

Fear and Loathing in DevOps

1. Enterprises are getting crushed if they don’t get Agile

a) Ignoring DevOps (Agile, CI/CD, etc) or..

b) Trying to implement Agile as WaterScrumFall

2. Most large companies have a significant variety of applications to manage

4 Copyright 2015. Confidential – Distribution prohibited without permission

Embrace the Fear

Legacy (or as EMC says, “Mature”)

No plans for modernizing but will live for 1-7 years

Converting

Need to move application construction and deployment to a

more modern CI/CD approach

Modern

Created using CI/CD built in

There Are Three Types of Applications in the Enterprise

5 Copyright 2015. Confidential – Distribution prohibited without permission

All Your Applications Can Benefit From CD

Legacy (or as EMC says, “Mature”)

No plans for modernizing but will live for 1-7 years

Implement tooling that can:

• Create reliable, consistent delivery of entire application to

Production

• Whatever you can’t automate, at least make it:

• Repeatable

• Audited

• Reportable

• Consistent

Sounds nice, but how do I do this?

6 Copyright 2015. Confidential – Distribution prohibited without permission

It’s Time to Go Zombie Hunting!

Look for these zombies in your IT Organization:SysAdmin who says, “I just write and run scripts, that’s not code”

DBAs who say, “SQL is not code. You can’t version it.”

“I’m the only person that knows how to deploy this.”It’s time you implement a solution that forces you to

version everything!

7 Copyright 2015. Confidential – Distribution prohibited without permission

Ensure That Your Tooling Delivers

Orchestration is key to delivery

Converting

Need to move application construction and deployment to a

more modern CI/CD approach

8 Copyright 2015. Confidential – Distribution prohibited without permission

What Lies Beneath These Strange New Waters?

Modern

Created using CI/CD built in

Make sure you have a source of truth in this delivery pattern

9 Copyright 2015. Confidential – Distribution prohibited without permission

Don’t Believe the Hype

Thinking of using a CI tool or provisioning

tool for your application deployments?

Plenty of confusion / messaging in the DevOps

space trying to convince you that this is a good idea.

Where the heck are my audit reports?!?

10 Copyright 2015. Confidential – Distribution prohibited without permission

Continuous Delivery

Real Continuous Integration / Continuous Delivery

Continuous Integration

Test

Commit

Test

Build

Test

Provision

Test

Deploy DEV

QA

Test

Provision

Test

Deploy

Test

Provision

Test

Deploy

Test

Provision

Test

Deploy

STAGE

PROD

1..n

• Orchestrating delivery of complete application

versions across release pipeline, with varied

levels of automation

• Reporting / security / auditing / visibility into

delivery of application from DEV to PROD

CI and Provisioning is just part

of the deployment process

1..n

1..n

Microservices demand this model!

Orchestration for not just application

deployment, but entire delivery process

11 Copyright 2015. Confidential – Distribution prohibited without permission

The Fear Increases

This is what “Release Night” feels like for the Business.

12 Copyright 2015. Confidential – Distribution prohibited without permission

Let’s Think About a Typical Enterprise

Manual Configuration for Applications

Separate teams performing deployments (mixture of scripts, automation and manual tasks)

Cost of failed deployments increases significantly as apps travel towards PROD

Developer QA“PREPROD”

(incl. training, simulation, etc) PRODDEV

Different teams /

application / tools

impact the effciency

of deploying

applications

Outages / long

deployments

significantly impacting

teams, project

timelines, training

and other delivery

requirements

Outages / long

deployments significantly

impacting business

revenue and customer

experience

Outages / long

deployments impacting

other development

teams, as well as QA

efforts

It works on my

machine!

PAIN

13 Copyright 2015. Confidential – Distribution prohibited without permission

Want To Take A Swing At What This is Costing You?

The scariest part – I didn’t include costs for so

many of the other people / processes / tasks

involved with getting your application running in

Production!

Deployment of a typical Java applicationin an “enterprise” environment:

Current Costs: $3,223,400.00Automated Costs: $947,215Yearly Savings: $2,276,185

Dev team hourly rate: 70

Application releases: 15 (5 MAJOR releases, 10 MINOR releases per year)

Man-hours per MAJOR / MINOR release: 8hrs / 5hrs

Man-hours per Dev/Test release: 4hrs

Average error rate per deployment: 5

Number of environments for Dev/Test: 3

Deployments per test environment: 5

Time to fix errors: 2hrs

FTEs writing and maintaining scripts: 2

Cost per hour for unexpected PROD outage: 8000

Cost per hour for unexpected TEST outage: 5000

I just strated looking at numbers like

these….

14 Copyright 2015. Confidential – Distribution prohibited without permission

Want to Start Implementing True Cost Savings?

Error Prevention

Look to these three key areas

Reducing Script writing and

Maintenance

Automating Manual Work

15 Copyright 2015. Confidential – Distribution prohibited without permission

Ok – So How Do I Do It?

Three Easy Steps:

1. Pick an application(s) that will test every part of your delivery from DEV

to PROD

− Not just pushing binaries – I mean all the “business stuff” (Release reports, security audits, etc)

− Includes teams like Finance (ex/ “what needs to change in chargeback for this project?”)

2. Automate everything possible in every environment from DEV to PROD

− It’s no good if you automate in DEV, but manually deploy in QA

3. Repeat

− Once success is recognized in Production, getting more apps/teams on board will be easy

16 Copyright 2015. Confidential – Distribution prohibited without permission

Your Teams Will Love You For It!

Error Prevention

Reducing Script writing and Maintenance

Automating Manual Work

Let this guy go on

vacation

Stop making developers do monotonous

work

Stop merging late and

testing in PROD!

17 Copyright 2015. Confidential – Distribution prohibited without permission

Resources

▪ Learn More About CD:

− Get the eBook for Managers: go.xebialabs.com/IT-Managers-Guide-to-CD.html

− Visit XebiaLabs Resource Section: xebialabs.com/xl-resources/

▪ Get started today!

go.xebialabs.com/XL-Platform-Trial.html

▪ Stay informed:

blog.xebialabs.com

@XebiaLabs

vimeo.com/xebialabs

Thank You!