+ All Categories
Home > Technology > Pragmatic Steps to DevOps: EMC Dojo One Year Later

Pragmatic Steps to DevOps: EMC Dojo One Year Later

Date post: 14-Apr-2017
Category:
Upload: pivotal
View: 168 times
Download: 2 times
Share this document with a friend
51
PRAGMATIC STEPS TO DEVOPS BRIAN ROCHE @brianroch ebos @emcdoj o dojoblog.em c.com
Transcript
Page 1: Pragmatic Steps to DevOps: EMC Dojo One Year Later

PRAGMATIC STEPS TO DEVOPSBRIAN ROCHE

@brianrochebos

@emcdojo

dojoblog.emc.com

Page 2: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 2BRIANROCHEBOS EMCDOJO

our world has changed

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 2BRIANROCHEBOS EMCDOJO

Page 3: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 3BRIANROCHEBOS EMCDOJO

The software disruption

Software is eating the world…– Marc Andreessen, 2011

Daily Steps

Oil & gas

Big data

d

cars

Self driving

agriculture

efficiency

Page 4: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 4BRIANROCHEBOS EMCDOJO

Your world has changedSome of you may not have

changedMany careers may face extinction

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 4BRIANROCHEBOS EMCDOJO

Page 5: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 5BRIANROCHEBOS EMCDOJO

S&P index

Page 6: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 6BRIANROCHEBOS EMCDOJO

Your world has changedSome of you may not have

changedMany careers may face extinctionThere is a better way

Learn by doing

Transform your team

Transform your company

Transform yourself

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 6BRIANROCHEBOS EMCDOJO

Page 7: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 7BRIANROCHEBOS EMCDOJO

The Global Solutions & emc dojo team is hereJoin us at our booth

Page 8: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 8BRIANROCHEBOS EMCDOJO

How do I get started? Dive right inAct your way to new thinking, Learn by ‘doing’

TAKE THE FIRS

T STEP

Learn by doin

g

Keep learning

Page 9: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 9BRIANROCHEBOS EMCDOJO

THE DOJO

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 9BRIANROCHEBOS EMCDOJO

Page 10: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 10BRIANROCHEBOS EMCDOJO

A Japanese term which literally means "place of the way”.A room in which martial arts are practiced

DOJO - noun \ˈdō-(ˌ)jō\

Contribute to Cloud Foundry Foundation sanctioned OS projects.Train new Cloud Foundry contributors to commit to OS Cloud Foundry.Innovate around the platform/infrastructure.

CLOUD FOUNDRY OS CONTRIBUTIONS & INNOVATION

Practice a modern software development methodology known as ‘the way’ (XP, Lean Startup).Evangelize new work patterns ‘the way’ to internal EMC product teams.

DIGITAL TRANSFORMATION

EMC - PIVOTALCLOUD FOUNDRY DOJO GOALS

Page 11: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 11BRIANROCHEBOS EMCDOJO

DIGITAL TRANSFORMATIO

NBRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 11BRIANROCHEBOS EMCDOJO

Page 12: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 12BRIANROCHEBOS EMCDOJO

steps to transformation

BALANCED TEAMS

BUILD, MEASURE,

LEARN

BMLTEST DRIVEN

DEVELOPMENT

tdd

MINIMUM VIABLE PRODUCT

MVPTIME,

INVENTORY

CONTINUOUS DELIVERY

CD

FEEDBACK

pairing

ELIMINATE WASTE

EXTREME PROGRAMMING

CONTINUOUS IMPROVEMENT

SUSTAINABLE PACE

Page 13: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 13BRIANROCHEBOS EMCDOJO

Edward hieattSvp – services at pivotal

labs

“The secret to our success is pair programming.

“BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 13BRIANROCHEBOS EMCDOJO

Page 14: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 14BRIANROCHEBOS EMCDOJO

PAIR PROGRAMMING

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 14BRIANROCHEBOS EMCDOJO

Page 15: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 15BRIANROCHEBOS EMCDOJO

Everything is a-okMeet Jackie

Works in a software companypromoted to director of engineeringManages an enterprise applicationToday is her first day with her new team

Page 16: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 16BRIANROCHEBOS EMCDOJO

MEET jackie’s TEAMTHE A-TEAM

ROCKSTARS

Everyone on Jackie’s team

is a super star. Heroes in their own

right.

EXPLORERS

THEY BLAZE THE TRAIL ON

NEW FUNCTIONALIT

Y always working alone.

ROCKET SCIENCE

WHAT THEY WORK ON IS LIKE ROCKET SCIENCE AND

YOU WOULDN’T

UNDERSTAND.

reckless

LIKE A ROCK CLIMBER WORKING

WITHOUT ANY SAFETY GEAR.

SUPER HERO

THEY ARE THE SINGLE POINT OF FAILURE.

IRREPLACEABLE – LIFE

WOULD END WITHOUT

THEM.

Page 17: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 17BRIANROCHEBOS EMCDOJO

PRODUCTION OUTAGEALL USERS LOCKED OUTCUSTOMERS ARE FURIOUS

“System wide outage brings critical business transactions to a halt.” SYSTEM ERROR

Page 18: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 18BRIANROCHEBOS EMCDOJO

SYSTEM ERROR

WHAT CAN WE DO?Pull the entire team together to brainstorm a solution

Outages happen all the timeDevelopers afraid to touch the codeEvery change leads to regressionContinuous restarts to avoid disaster

If only There was a better way

Page 19: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 19BRIANROCHEBOS EMCDOJO

welcome to the new worldFun, Open, collaborative

environments

WE VALUE APTITUDE OVER SPECIALIZATIONCONTINUOUSLY ADAPTING TO CHANGE

ROTATE OFTEN

WE WOULD NEVER GO BACK!

Rediscover software development

QUICKERON-RAMP

BETTERENGAGEME

NT

HIGHERCODE

QUALITY

SHARED ‘context’

ADAPTIVE TO

CHANGE

EMPATHY

Page 20: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 20BRIANROCHEBOS EMCDOJO

TDD BENEFITS

Safety net

DEPLOYMENT

Lean code

FAST FEEDBACK

QUALITY

Page 21: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 21BRIANROCHEBOS EMCDOJO

Continuous Delivery PipelineWhen the pipeline stops,

we stop

Step 3CONTINUO

USINTEGRATI

ON

Step 2

Run test automat

ion customer

feedbackStep 4

DEPLOYStep 1

Write the code

WE ARE GOOD AT SHIPPING CODE BECAUSE WE SHIP ALL THE TIME

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 21BRIANROCHEBOS EMCDOJO

Page 22: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 22BRIANROCHEBOS EMCDOJO

The worst thing that can happen when you release software is, no one cares.

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 22BRIANROCHEBOS EMCDOJO

Page 23: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 23BRIANROCHEBOS EMCDOJO

WATERSCRUMFALLSO WHAT’S WRONG WITH IT ANYWAY?

All requirements are well known

Product definition is stable

Technology is well understood

There’s nothing wrong if …

Little adaptation to customers is needed

Page 24: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 24BRIANROCHEBOS EMCDOJO

Sequential design process used in software

development

Waterfall

maintenance

verification

implement

Design

Requirements

Page 25: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 25BRIANROCHEBOS EMCDOJO

Potential waste

ACHIEVING FAILURECustomer feedback is

quarters away

Q1 Q2 Q3 Q4

Design

Build

Test

Release 1

InceptionRisk

= U

n-va

lidat

ed E

ffort

Page 26: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 26BRIANROCHEBOS EMCDOJO

Lean is a strategy for

building software in

times of extreme

uncertainty

Page 27: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 27BRIANROCHEBOS EMCDOJO

BUILD MEASURE LEARN CYCLEValidated Learning

Build

Measure

Learn

Risk

= U

n-va

lidat

ed E

ffort

Time

Build

Learn Learn Learn

Measure

Learn

Build

Measure

Learn

Build

Measure

Build

Measure

Build

MeasureBuild

Measure

Learn

Page 28: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 28BRIANROCHEBOS EMCDOJO

Should we build this product?

The dominant question is notCan we build this product?

Page 29: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 29BRIANROCHEBOS EMCDOJO

Minimum viable product

+ + =FIGURE OUT

THE PROBLEM THAT NEEDS TO BE SOLVED AND DEVELOPING A

(MVP) TO BEGIN THE PROCESS

OF LEARNING AS QUICKLY AS POSSIBLE.

01DID OUR

SOLUTION SOLVE THE

CUSTOMER’S NEEDS? IS

THE SOLUTION VALUABLE?

02DID WE

VALIDATE OUR HYPOTHESIS ABOUT THE PRODUCT STRATEGY

AND ENGINE OF GROWTH?

03OUR ULTIMATE

GOAL IS TO BUILD A

SUSTAINABLE BUSINESS

WITH MAXIMUM

ACCELERATION

04The problem valuable Pivot or persevere

Sustainable business

Page 30: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 30BRIANROCHEBOS EMCDOJO

Team focus?Does your focused team

look like this?

Endless meetingsConstant interruptionsCollaboration overJuggling 5 projects

email

Page 31: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 31BRIANROCHEBOS EMCDOJO

Devopsfocused work week

monday

Stand up

Business value

personal

lunch

Business value

9:00 am

1:30 – 6:00 afternoon

6:00 pm end

12:30 – 1:30 Lunch

9:15 – 12:30 morning

tuesday

Stand up

Business value

personal

lunch

Business value

wednesday

Stand up

Business value

personal

lunch

Business value

thursday

Stand up

Business value

personal

lunch

Business value

friday

Stand up

Business value

personal

lunch

Business value

Page 32: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 32BRIANROCHEBOS EMCDOJO

3 meetings to success

daily standup

15 minutes

iteration planning

30 minutes

retrospective

60 minutes

Page 33: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 33BRIANROCHEBOS EMCDOJO

Unresolved conflict – the silent team killerTeam performance

Time PressuresIneffective

Communication Feedback

PracticeThe Blame

Game

Assuming malicious

IntentBack stabbing and coalition

forming

HarborGrudges

Everyone

is the

enemy

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 33BRIANROCHEBOS EMCDOJO

Page 34: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 34BRIANROCHEBOS EMCDOJO

Research on Great teams

collaborationTime spent

collaborating has increased

to 50% or more

50%

startGoogle

commissioned research to

begin 5 years ago

5

teamsExamined 180 teams across

the entire company

180

patternsAfter

surveying 180 teams, google

found no patterns

0work

¾ of people’s day is spent collaborating

with team mates

¾

Page 35: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 35BRIANROCHEBOS EMCDOJO

What makes a great team

Teamnorms psychologi

calsafetyheard

mutualrespect

socialsensitivit

ydependab

ility

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 35BRIANROCHEBOS EMCDOJO

Page 36: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 36BRIANROCHEBOS EMCDOJO

Retros (retrospectives)Our ‘way’ of working changes

all the time

Whole-team

learningTeams learn to navigate conflict, by having uncom-

fortable, but necessary discussions.

Generateaction

More than an end of iteration wrap-up. Teams generate real

actions and change.

teamissuesTeam issues are as

challenging as technical issues – if not more so.

development

processTeams assess their ability to break down and solve problems and make

improvements.

Page 37: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 37BRIANROCHEBOS EMCDOJO

THE PROJECTS

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 37BRIANROCHEBOS EMCDOJO

Page 38: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 38BRIANROCHEBOS EMCDOJO

NHC From Cindy

WHAT IS IT• FULLY INTEGRATED AND OPTIMIZED

SOLUTION WITH PIVOTAL CLOUD FOUNDRY AT ITS CORE.

• FRICTIONLESS DEVELOPER EXPERIENCE ‘IT JUST WORKS’ ENABLING ENGINEERING TEAMS TO FOCUS ON WHAT MATTERS, BUILDING THEIR APPS.

WHAT DO YOU GET• TOOLCHAIN FOR BUILDING CI/CD

PIPELINES THROUGH PARTNER INTEGRATIONS WITH GITLAB, CLOUDBEES JENKINS PLATFORM, AND JFROG ARTIFACTORY

• ANALYTICS AND MONITORING OF APP PERFORMANCE THROUGH PARTNER INTEGRATIONS WITH NEW RELIC AND APPDYNAMICS

WHEN IS IT AVAILABLE• CURRENTLY IN BETA; WITH A GA

SEPTEMBER 2016.• BUSINESS DATA AND ANALYTICS ADD-ON

COMING 2H, 2016 THAT PRODUCES A COMPREHENSIVE TOOLKIT FOR DATA SCIENTISTS AND ENGINEERS TO PERFORM BIG DATA ANALYTICS.

NATIVE HYBRID CLOUDCloud-Native Apps a t t h e S P E E D O F B U S I N E S SFully Engineered Turn-key Solution For Cloud Native Applications

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 38BRIANROCHEBOS EMCDOJO

Page 39: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 39BRIANROCHEBOS EMCDOJO

PERSISTENCE comes to

Cloud Foundry is WAY cool & 12 Factor Apps are WAY cool tooBUT we have legacy apps that still need attentionManagement of different applications is costly and inefficientThere should be a place for all of your apps in Cloud FoundrySo we implemented persistence leveraging ScaleIO and IsilonNow all of your apps can enjoy the benefits of Cloud Foundry

OS

CEPH FS

EMC

SCALEIO

EMC

ISILONMORE TO COME …

Page 40: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 40BRIANROCHEBOS EMCDOJO

Lorem ipsum dolor sit amet, sit sed dignissim volutpat, donec sed sodales ridiculus consectetuer orci. Nam vestibulum vitae ac, amet sed mollis vel sed eleifend, eum mi,

Insert your catchy tagline here

ORCHESTRATION• RACKHD PROVIDES PLATFORM

AGNOSTIC MANAGEMENT AND ORCHESTRATION OF PHYSICAL HARDWARE.

• WITH THE ABILITY TO DISCOVER EXISTING HARDWARE RESOURCES THIS INFO CAN BE USED TO PERFORM LOW LEVEL HARDWARE MGMT TASKS.

CLOUD FOUNDRY• THE RACKHD CPI DEVELOPED IN THE

CLOUD FOUNDRY @EMCDOJO• BOSH IS NOW EMPOWERED TO

PROVISION BARE-METAL MACHINES, DEPLOY SOFTWARE ON THEM, AND MONITOR THE HEALTH OF DEPLOYMENTS

THE CPI IS AVAILABLE NOW • RELEASED UNDER THE APACHE 2.0 LICENSE,

IT CAN BE FOUND IN THE CF INCUBATOR:• HTTPS://GITHUB.COM/CLOUDFOUNDRY-

INCUBATOR/BOSH-RACKHD-CPI-RELEASE/BLOB/MASTER/DOCS/HOW_TO_DEPLOY_CLOUD_FOUNDRY_ON_BARE-METAL_MACHINE(S).MD

RACKHD & CLOUD FOUNDRY

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 40BRIANROCHEBOS EMCDOJO

Page 41: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 41BRIANROCHEBOS EMCDOJO

EMC DOJO

GINGKO4J

ADVANCED DEVELOPMENT

SPRING CONTENTGOLANG has a testing framework called Ginkgo.  Similar to frameworks like RSpec in Ruby.  These frameworks provide a simple DSL that allows developers to write structured, context rich tests.   We have built an equivalent DSL for Java called Ginkgo4j offering native support for Spring.  Now Java developers can write the same descriptive tests for their code.

Spring Framework enables developers to focus on what matters, building their apps, taking care of the plumbing on their behalf.  Spring Content abstracts file IO with support for multiple underlying storage infrastructures (S3, FS, nosql and SQL databases).  Developers now have the same familiar easy access to their unstructured data.

Page 42: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 42BRIANROCHEBOS EMCDOJO

PROJECT UNIK

Lorem ipsum dolor sit amet, sit sed dignissim volutpat, donec sed sodales ridiculus consectetuer orci. Nam vestibulum vitae ac, amet sed mollis vel sed eleifend, eum mi,

Insert your catchy tagline here

SMALL FOOTPRINT, BIG IMPACT• UNIKERNELS ARE APPLICATION IMAGES

THAT CONTAIN THE MINIMUM CODE NECESSARY TO MAKE AN APPLICATION RUN.

• OFFERING MORE SECURITY (REDUCED ATTACK SURFACE) AND FASTER BOOT TIMES THAN A TRADITIONAL OS DUE TO THEIR SMALL FOOTPRINT.

LIGHTWEIGHT KERNELS• SPECIALIZED, LIGHTWEIGHT KERNELS

MAKE IT EASIER FOR DEVELOPERS TO DELIVER SOLUTIONS IN THE CLOUD COMPUTING AND (IOT) MARKET.

• COMPILE AN OPERATING SYSTEM AND RUN IT ON VIRTUALLY ANY CLOUD PLATFORM.

UNIK IS AVAILABLE NOW • RELEASED UNDER THE APACHE 2.0 LICENSE,

PROVIDES A SIMPLE DOCKER-LIKE COMMAND LINE INTERFACE, TO MAKE BUILDING UNIKERNELS AS EASY AS BUILDING CONTAINERS.

• HTTPS://GITHUB.COM/EMC-ADVANCED-DEV/UNIK

(pronounced you-neek)

UNIK ENABLES SOFTWARE DEVELOPERS TO COMPILE APPLICATIONS INTO DIFFERENT UNIKERNELS CREATING EXTREMELY LIGHTWEIGHT, EFFICIENT APPLICATION INSTANCES.UNIK IS POISED TO PLAY A SIGNIFICANT ROLE IN THE CLOUD IOT WORLD.

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 42BRIANROCHEBOS EMCDOJO

Page 43: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 43BRIANROCHEBOS EMCDOJO

A little helpFrom your friends

TRANSFORMING HOW THE WORLD BUILDS SOFTWARE. Kick-start your DevOps process and transform how you build software. Solving real problems working alongside customers to launch market-tested, innovative solutions that have the power to transform the world. The knowledge and adoption of ‘the way’ will be just as important as the product you produce.

A BROAD SET OF TOOLS AND KNOW-HOW TO HELP CUSTOMERS BREAK DOWN MONOLITHIC APPS. Pairing with customers either on-site or at our custom built facilities, EMC Services will help you transform your legacy apps and achieve the promise of a DevOps culture. While rapidly building and delivering solutions that meet the business needs of customers.

Page 44: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 44BRIANROCHEBOS EMCDOJO

THE RESULTs OF incorporating feedback

PAIRINGtdd

CI/CD

BML

MVPeliminat

ewaste

Feedback

BALANCED

TEAMS

Page 45: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 45BRIANROCHEBOS EMCDOJO

OPSRELEASEENG

RELEASEENGDEVELOPMENT

devopsQA OPS

Page 46: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 46BRIANROCHEBOS EMCDOJO

devopsdevopsdevo

ps

Shared ownershipempathy

predictability Higher qualityContinuous delivery

Seamless upgradesLess waste

focus

tddpairing

Automate everything Better-closer-togethertrust

devopsbetter

together

Page 47: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 47BRIANROCHEBOS EMCDOJO

Inside outtheHappens from Evolution

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 47BRIANROCHEBOS EMCDOJO

Page 48: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 48BRIANROCHEBOS EMCDOJO

Don’t swim half way and turn backTransform yourself

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 48BRIANROCHEBOS EMCDOJO

Page 49: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 49BRIANROCHEBOS EMCDOJO

conclusionWhat have we learned?

There is a Better way

The worldHas

changedLearn by

doingTransform yourself

Change the

world

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 49BRIANROCHEBOS EMCDOJO

Page 50: Pragmatic Steps to DevOps: EMC Dojo One Year Later

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 50BRIANROCHEBOS EMCDOJO

Thank youdojoblog.emc.com@brianrochebos @emcdojo

BRIAN ROCHE: PRAGMATIC STEPS TO DEVOPS 50BRIANROCHEBOS EMCDOJO

Page 51: Pragmatic Steps to DevOps: EMC Dojo One Year Later

Recommended