Be Careful what you wish for ....

DevOps

Keynote theme c/o - furnace - http://graphicriver.net/item/ignite-keynote-presentation-template/2639047

who is envato?Envato Marketplaces Tuts+ Microlancer

our marketplaces

So Are We “Doing” Devops?The DevOps Checklist

Infrastructure as Code

Multiple Deploys a Day

Push button Deploys by Developers

Ops and Dev share first-line support

No Ops or Dev Silos

so pretty hip right?

our devops guys

and at scale?Or are we just another “Ramen Noodles” eating Startup deploying 20 times a day but with no customers? ...

•1 product sold every 10 seconds (> 8000 a day)

•100m page views a month

•10m+ app server requests a day

•50+ virtual Machines

•Themeforest - 4th largest Rails site in the World (GitHub is the 5th)

off the charts hip now!

DR Planning and Practice

Infrastructure Capacity Planning

Reviewing Health of the Environment

Incident and Planned Outage Processes

Incident Root Cause Analysis and Long Term fixes

Decidedly less cool

what if there was more to the DevOps checklist?We are historically Not Awesome at ...

so, What is it to “Be” DevOps?

It’s about Culture and Mindset and not only tools and activities

Its about 2 cultures coming together Working side-by-side Respecting and complementing each others skills and mind sets and Trusting each other

the merging of 3 brain hemispheresOPS

Risk and Growth Manager

•Long Term Thinking

•Reducing Risk and Cost

•Planning for Growth

Change Controller

•Motivated by Stability

•Less change is better

•Controlling immediate change

Dev

•Motivated by Creating

•More change is better

•Focus on short term

Creator of Change

to become only one!

Change Controller

•Motivated by Stability

•Less change is better

•Control change

The BathwaterThe Baby

•Motivated by Creating

•More change is better

•Focus on short term

Dev OPS

•Long Term Thinking

•Reducing Risk and Cost

•Planning for Growth

Risk and Growth ManagerCreator of Change

what should we have done differently?•Grew Dev Capacity and not Ops Specialist Capacity

•Too Dev-biased when prioritising tech work

•No Ops voice in strategic planning

•Ops stuff we did tackle was “dev-friendly” e.g. Puppet

•Too focussed on the Now rather than 3-5 years

•Brain atrophy of the Ops right side brain

•Now playing catchup on Infrastructure and Ops work

our learningsIn Embracing “Being” DevOps

But DON’T neglect that part of the Ops mindset and culture that allows you to plan for and manage risk and growth as your business scales

DO use tooling and automation to de-risk and enable rapid change

prefer

the end

Keynote theme c/o - furnace - http://graphicriver.net/item/ignite-keynote-presentation-template/2639047

Questions ...