devoxxuk 2014 "moving to a devops mode: easy, hard, or just plain terrifying?"

@spoole167 @danielbryantuk #DevOps

MOVING TO A DEVOPS MODE: EASY, HARD OR JUST PLAIN TERRIFYING?

Daniel Bryant Steve Poole @danielbryantuk @spoole167


Your Guides for Today’s Journey into DevOps…

Daniel Bryant Principal Consultant, OpenCredo

ü Full-Stack Developer ü Open Source Advocate ü Agile, Continuous Delivery and DevOps ü Aspiring Software Craftsman

Steve Poole IBM Developer

ü Making Java Real Since Version 0.9 ü Open Source Advocate ü DevOps Practitioner (whatever that means!) ü Driving Change


Our Goals…

•  DevOps is about extending ‘agility’ across your IT organisation •  Implementing this is not going to be easy…

•  … some things will be hard, some things terrifying

•  However, there are real benefits

@YourTwitterHandle #DVXFR14{session hashtag} @spoole167 @danielbryantuk #DevOps


Once upon a time the universe was static

Design, Code

Unit test

Functional Test System test

Stage Configure

Fix bugs

Fix bugs Helpline

Monitor, backup upgrade, support, repair

security, compliance

Uses

reality chasm


This was called “Waterfall”

Reinforced team separation Long feedback cycles Long time-to-market

Tended to increase ‘Release Panic’

BIG Reality Chasm DEV OPS


Waterfall - more a roller-coaster ride…

Time

# o

f bug

s Start to panic

here

DEV OPS

QA Client

£ Value here

Really panic here

Reality Chasm


If you fell into the reality chasm…

Time

# o

f bug

s Start to panic

here

Really panic here

DEV OPS

QA Client

No Value here


Agile helps reduce the chasm

Time

# o

f bug

s Feedback here

OPS

Client

DEV

Feedback here Feedback here

QA £

Value here


But now clients say…

Time

# o

f bug

s

OPS

Client

DEV

QA

£

I want value here

And here


The new challenge – we can’t afford the gap

Time

# o

f bug

s

OPS

Client

DEV

QA

Move Left


How to bring Dev, QA & Ops together?

ü Culture

ü Common goals

ü Shared responsibility

ü Education

ü Standard technology


Netflix are not Unicorns!

Neither are Amazon, etsy, Spotify…

and besides…


Change your mindset…


Culture is Vital

•  Culture drives behaviour, drives culture… •  “Communication, simplicity, feedback, courage”

•  Everyone is responsible for delivery

•  Continuous experimentation and learning

•  Not easy to change culture •  The hardest part of DevOps…

•  …but you will learn new things


Changing Culture

•  Greenfield •  Flickr’s story (slidesha.re/sHpYV)

•  “Why other people don’t get it”

•  Sandro Mancuso (slidesha.re/1bcStpe)

•  Enterprise •  “The Phoenix Project” (Gene Kim et al)


Changing Culture

•  Create an effective team…

•  “Habits of highly effective technical teams” •  Martijn Verburg (bit.ly/1aF9SnK)

•  “Patterns of Effective Teams” •  Dan North (vimeo.com/68226771)

•  Buy some doughnuts… •  Andrzej Grzesik (http://www.youtube.com/watch?v=OFr0PoIIdvk)


We’ve all got issues…

Great, so how does this work for individual teams?


Continuous Delivery and DevOps go hand-in-hand…

•  Create a build and deployment pipeline

•  Adopting Continuous Delivery •  Jez Humble (http://bit.ly/1oEReUM)

•  Implementing Continuous Delivery •  Rachel Laycock (http://bit.ly/1l1qMPf)


Start with automated build & unit test

Continuous Integration

JUnit

SCM Build

Build Orchestration

Unit Test


Add staging for automated QA


JUnit

Continuous Delivery

Repository

Performance & QA

Deployment tools


Add “automatic(ish) deployment to production™”


JUnit

Continuous Delivery

Continuous Deployment

Hosting

Deployment tools


Base it on virtualization technologies

Continuous Deployment Pipeline

External Cloud

On premises cloud

Clo

ud

Dep

loym

ent

Orc

hest

rato

r JUnit


The imperative of DevOps

Startups through to big businesses are demanding the value that DevOps & Cloud Technologies can offer

1. Production deployment pipeline up and running in days

2. Updates published in hours

DevOps helps transition an organization into this new world… Helps to remove the ‘reality chasm’


The imperative of DevOps

The cost?

1. Standardized pipelines

2. Dev and Ops teams working together

3. Greatly expanding your horizons and your technical skills

4. Leaving your comfort zone


Developers…


Contribute to the pipeline

•  Continuous Integration

•  Unit / Integration Tests

•  Automate all the things

•  Stop throwing stuff over the wall…

•  …or we’ll throw you over it too!


Moving closer to Ops

•  Design patterns •  Asynchronous communication

•  Timeouts / retries

•  Bulkheads / circuit-breakers

•  Metrics are your friend •  Technical and business data

•  Logging (centralised)


Thinking/Acting like a sysadmin

•  Learn Linux fundamentals

•  Diagnostic skills •  top, iotop, iostat, netstat, vmstat

•  Java utils: jps, jstat, jmap, jhat •  “DevOps Troubleshooting” by K. Rankin

•  Maybe grow a beard…


QA…


Automating QA

•  Automate all the things…

•  Tests can be specifications •  Specifications can be tests…

•  Make it easy for everyone to execute •  Make it fast (and conditional)

•  Contribute to the build pipeline •  If you want people to care, then fail the build!


Automating QA

•  Unit and Intra-component integration testing •  Spock is awesome •  Utilise embedded datastore/middleware

•  Performance •  JMeter + plugins •  Gatling

•  Website •  Geb (Groovy + Selenium)


Operations…


Ops should be operational…

•  Learn about coding (pair program!) •  Python, Ruby, Groovy

•  Get closer to Dev & QA •  Provide constant feedback

•  Embrace chaos for testing •  Simian army…


Monitoring is mandatory

•  Infrastructure monitoring •  Nagios

•  Zabbix

•  Splunk •  AppDynamics

•  Several trail-blazers •  Etsy (www.codeascraft.com)

•  Netflix (techblog.netflix.com)


Graphing…


Say No To Snowflakes!

•  “Infrastructure as Code” •  Version control everything

•  Automate all provisioning •  Chef, Puppet, SaltStack, Python, AWS CLI

•  Play with Vagrant (www.vagrantup.com)

•  Docker and Packer are also interesting


Who here ‘does’ Agile?


Are you personally ready?

•  Do you use Agile techniques?

•  Can you spell “Continuous Integration”?

•  Are the advantages of DevOps clear? •  Could you communicate them to your Dev & Ops teams?


Summary

Businesses need to be able to react faster… …DevOps and the Cloud are key enablers

DevOps is as much a game changer as Agile was…

…this is a Developer, QA and Ops “renaissance” Don’t be afraid to learn and experiment…

…you’ll benefit even if the tech doesn’t survive

Agile moved you closer to the customer… …DevOps moves you closer to the IT team


Moving to a DevOps Mode…

You should be terrified

The transition will be hard

But it’s easy to get started

devoxxuk 2014 "moving to a devops mode: easy, hard, or just plain terrifying?"

Technology

dev amp

devops mode

devops

build

agile

learn

closer

www