Transcript
Page 1: Ignite: A Reset on DevOps: What it is, and isn't

A Reset on DevOpsWhat it is, and isn’t

Max Griffiths@_maxamg

Page 2: Ignite: A Reset on DevOps: What it is, and isn't

I’m Max (hi)

• DevOps things for 10yrs

• Work for ThoughtWorks in SF

• Eating my way round the world, solving problems for clients in various industries

Page 3: Ignite: A Reset on DevOps: What it is, and isn't

Why am I telling DevOps enthusiasts what DevOps

is?

…let’s eat sandwiches together

Align?Ruffle

feathers?

debate? self-assurance?

Page 4: Ignite: A Reset on DevOps: What it is, and isn't

The Problem(and my frustration)

MOAR DEVOPS ROLES AVAILABLE

…That’s ok (for us!)but it’s not helping the situation

Page 5: Ignite: A Reset on DevOps: What it is, and isn't

Elite Superstars

• DevOps heroes counteract shared ownership

• Project think they need these people

Page 6: Ignite: A Reset on DevOps: What it is, and isn't

Other people’s frustration

…or confusion, e.g the article

“How ‘DevOps’ is Killing the Developer”

Page 7: Ignite: A Reset on DevOps: What it is, and isn't

Specialism is good.Pride yourself on special

things

• Devs being more Ops-minded - GOOD!

• Ops folk being more Devvy - SURE!

• Coding Puppet isn’t DevOps - thats infra coding

Page 8: Ignite: A Reset on DevOps: What it is, and isn't

Stop.(Hammertime.)

What does the Internet say

Page 9: Ignite: A Reset on DevOps: What it is, and isn't

“DevOps is a response to the interdependence of software development

and IT operations. It aims to help an organisation rapidly produce software

products and services”

“DevOps” - Wikipedia

Page 10: Ignite: A Reset on DevOps: What it is, and isn't

A philosophy, a cultureNOT a role

• Think about QA: quality is everyones concern

• But a certain set of skills really help in times of DevOps anti patterns

Page 11: Ignite: A Reset on DevOps: What it is, and isn't

The mystical ???? role

Page 12: Ignite: A Reset on DevOps: What it is, and isn't

What do we call ???? role

• I don't mind. Not DevOps

• NuOps?

• Jedi Master: behavioural technician?

Page 13: Ignite: A Reset on DevOps: What it is, and isn't

What does bad DevOps look like?

• Operations Old Skool

• cares only about: stability, uptime

• probably surly, still codes Perl, and unlikely to deploy your code without a huge document

Page 14: Ignite: A Reset on DevOps: What it is, and isn't

Developers

Page 15: Ignite: A Reset on DevOps: What it is, and isn't

A DevOps Team

• Not necessarily a bad thing!

• But in most cases a sign that something isn’t quite right

• ref: DevOpsDays London 2013 (Mark Rendell)

Page 16: Ignite: A Reset on DevOps: What it is, and isn't

I Haz the Dockers

• Who supports the tools when they transition from bleeding edge to the blunter ‘cutting edge’

(the tool junkie)

Page 17: Ignite: A Reset on DevOps: What it is, and isn't

A single DevOps person

Page 18: Ignite: A Reset on DevOps: What it is, and isn't

The good

• Ops folk participating in showcases, retros, inception and planning session

• Developers rotating through Operations

Page 19: Ignite: A Reset on DevOps: What it is, and isn't

What good looks like

• Simple effective communication

• Co-location

• and…

Page 20: Ignite: A Reset on DevOps: What it is, and isn't

What good looks like

Page 21: Ignite: A Reset on DevOps: What it is, and isn't

A Reset on DevOpsWhat it is, and isn’t

Max Griffithsmeetup.com/SF-LunchOps


Top Related