ignite: a reset on devops: what it is, and isn't
DESCRIPTION
This is an Ignite Talk (20 slides advancing automatically, every 15 seconds) I gave at DevOpsDays Toronto 2014. Abstract: "We're in 2014 but ask a recruiter, a QA and a Dev what DevOps is and you'll get different answers, still. As someone who has consistently fallen between the pigeonholes of Developers and Operations Engineers, my biases are even and I'm ready to converge on the core, misinterpreted values of DevOps as a practice, not as a role. Tools, pipelines and Jedi mind tricks are equal players when it comes to a necessary DevOps dance. It's not about being a hero, it's not about fixing everything for everyone. Accept the world is bad, and make it better, not perfect. And if that doesn't work, let developers operate their own code in production."TRANSCRIPT
A Reset on DevOpsWhat it is, and isn’t
Max Griffiths@_maxamg
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
Why am I telling DevOps enthusiasts what DevOps
is?
…let’s eat sandwiches together
Align?Ruffle
feathers?
debate? self-assurance?
The Problem(and my frustration)
MOAR DEVOPS ROLES AVAILABLE
…That’s ok (for us!)but it’s not helping the situation
Elite Superstars
• DevOps heroes counteract shared ownership
• Project think they need these people
Other people’s frustration
…or confusion, e.g the article
“How ‘DevOps’ is Killing the Developer”
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
Stop.(Hammertime.)
What does the Internet say
“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
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
The mystical ???? role
What do we call ???? role
• I don't mind. Not DevOps
• NuOps?
• Jedi Master: behavioural technician?
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
Developers
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)
I Haz the Dockers
• Who supports the tools when they transition from bleeding edge to the blunter ‘cutting edge’
(the tool junkie)
A single DevOps person
The good
• Ops folk participating in showcases, retros, inception and planning session
• Developers rotating through Operations
What good looks like
• Simple effective communication
• Co-location
• and…
What good looks like
A Reset on DevOpsWhat it is, and isn’t
Max Griffithsmeetup.com/SF-LunchOps