Demystifying DevOps - it's not Agile, but they're friends
•Download as PPTX, PDF•
2 likes•805 views
A slightly longer version of my Ignite talk that I gave to the DFW Agile-DevOps meetup
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Demystifying DevOps - it's not Agile, but they're friends
Similar to Demystifying DevOps - it's not Agile, but they're friends (20)
Recently uploaded
Recently uploaded (20)
Demystifying DevOps - it's not Agile, but they're friends
- 1. Demystifying DevOps What it is, and isn’t Max Griffiths @_maxamg
- 2. I’m Max (hi) • DevOps things for 12+yrs • Used to be a dev.. probably more ops now • Work for ThoughtWorks in SF • Eating my way round the world, solving problems for clients in various industries • Worked for startups and large enterprises • People problems + tech problems = FUN
- 3. Dev……….Ops
- 4. Difference in work style Developers - Features - Functionality = Change-happy Operations - Uptime - Stability = Change-averse
- 5. “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 2012
- 6. The Problem (and my frustration) • Been around for a long time • We STILL have confusion and ambiguities
- 7. The Problem …continued …That’s ok (for us!) but it’s not helping the situation
- 8. Elite Superstars • DevOps heroes counteract shared ownership • Project think they need these people
- 9. Other people’s frustration …or confusion, e.g the article “How ‘DevOps’ is Killing the Developer”
- 10. 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
- 12. Agile vs. DevOps? Agile == DevOps?
- 13. Agile vs. DevOps? Agile == DevOps? Agile ⊨ DevOps?
- 14. They’re pals!
- 15. …with common interests: • Fast Feedback (including visual) • Consumer-centric and Value driven • Optimising on speed and quality
- 16. A philosophy, a culture NOT a role • Think about QA: quality is everyones concern • However: a certain set of skills really help in times of DevOps anti patterns
- 17. The mystical ???? role
- 18. What do we call ???? role • I don't mind. Not DevOps • NuOps? • Jedi Master, …behavioural technician?
- 19. Antipatterns
- 20. 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
- 21. Developers
- 22. A DevOps Team • Not necessarily a bad thing! • But in most cases a sign that something isn’t quite right
- 23. A DevOps Team • ref 1: DevOpsDays London 2013 (Mark Rendell) • ref 2: “Forming new DevOps teams and giving people DevOps titles is successful in practice” Findings From Puppet Labs State Of DevOps 2014 - Nigel Kersten
- 24. I Haz the Dockers • Who supports the tools when they transition from bleeding edge to the blunter ‘cutting edge’ (the tool junkie)
- 25. A single DevOps person
- 26. The Good
- 27. The good • Ops folk participating in showcases, retros, inception and planning session • Developers rotating through Operations
- 28. What good looks like • Simple effective communication • Co-location, or equally dispersed • and…
- 29. What good looks like
- 30. Demystifying DevOps What it is, and isn’t Max Griffiths meetup.com/SF-LunchOps
- 32. Turns out, configuring servers is really easy 3 basic ‘resources’: - Packages - Files - Services
- 33. Players in the market:
Editor's Notes
- DevOps things for 10yrs Work for ThoughtWorks in SF Eating my way round the world, solving problems for clients in various industries
- using “rapidly” and forgetting “quality” is dangerous, but I like “response”.. means it’s answering a problem that existed, but wont necessarily always exist.
- DevOps has been around for years as a discipline, and coined “DevOps” for 5years ref: Patrick Debois - of DevOpsDays fame. - 2009 Poll: who feels they have a grasp of what devops is and isnt?
- Every employer is calling for DevOps (even ThoughtWorks). But what do they mean? LinkedIn is headhunting us by word searching! …which is great (for us!) but it’s not helping the situation
- Gives rise to: DevOps experts exist as heroes exist and counteract shared ownership Also, needing a pipeline doesn't mean you need a DevOps specialist
- Other people are frustrated…or at least confused, people saw the blog post right? “How ‘DevOps’ is Killing the Developer” so it’s not just me.
- Specialism is good but Devs being more Ops-minded - GOOD! Ops folk being more Devvy - SURE! Coding Puppet isn’t DevOps - thats infra coding - but it’s a good bridge of skills!
- Agile against DevOps?
- Agile is the same as DevOps?
- Agile entails DevOps?
- My view: they’re pals! - mutually exclusive philosophies …with some overlap or, common interests:
- Visual feedback - agile boards vs Monitoring dashboards Value is about success with the product customer, or consumer of the service - a dev team could be the customer of a DevOps initiative
- DevOps is a philosophy NOT a ROLE Every project doesn't need a DevOps person. like QA’s - quality is everyones concern But a certain set of skills really helps fight the DevOps cause, so there’s this role that is neither solid Dev, nor Ops
- Someone who has experience on both sides? Feels pain when others feel pain? maybe they contribute solutions to dev and ops land?
- so what do we call it? i don't really mind.. but not DevOps Call it OpsDev (if you really want to screw with people) Perhaps you’re just the new wave of Ops Jedi Master, behavioural technician
- I’ll leave you with how to spot bad and good devops
- Bad Ops Team that only care about stability and uptime probably surly, know Linus Torvalds and unlikely to deploy your code without a huge document
- Old school Developers… only caring about new features compiling hot fixes at home and asking Ops to deploy it in the morning. Naughty.
- A Devops Team..is actually ok! under certain conditions. But in most cases a sign that something isn’t quite right. A friend of mine did a talk defending this. Ask me for details Mark Rendell DevOpsDays London 2013 http://devopsdays.org/events/2013-london/proposals/When%20you%20need%20a%20DevOps%20team
- A Devops Team..is actually ok! under certain conditions. But in most cases a sign that something isn’t quite right. A friend of mine did a talk defending this. Ask me for details Mark Rendell DevOpsDays London 2013 http://devopsdays.org/events/2013-london/proposals/When%20you%20need%20a%20DevOps%20team
- The Tool Junkie - a proliferation of the latest gadgets will become hard for the project to support
- A DevOps person! What does this person do exactly? (apart from swan around citing Martin Fowler) Seriously though - If the problem isn’t strictly dev, or ops, this role becomes a catch-all and a bottleneck
- the good! Ops participating in showcases, retros, inceptions and planning sessions Devs rotating through Ops - Show them how bad their logging is (and don’t let them attach a debugger)
- A culture of valuable, respectful, concise communication Co-location: same room if possible. you just can’t beat it. And finally…
- Again, it’s about breaking down barriers and empathising. This is done more effortlessly when emotions are engaged. “HugOps”
- Lunch Ops