Dev, Ops, and The Modern Team

Presentation given at #MMWCON on 18 Sept 2014

Transcript

1. Dev, Ops, and the Modern Team Christopher Webber @cwebber
3. Who Am I?
4. Started as a student at CSU Fresno
5. Spent ~5 1/2 Years at UC Riverside in various positions
6. 1 1/2 Years at Demand Media in Operations role supporting large web sites
7. Community Software Engineer at
8. But, Who Are You? • SysAdmin • Developer • Designer • Manager • Other
9. Where Do You Come From? • Academic - Research • Academic - Administrative • Academic - Teaching • Corporate • Startup
10. What Even Is DevOps?
12. Breaking down of silos
13. Focus on the goal of the business
14. Here’s the secret. I’ll tell you EXACTLY what devops means. Devops means giving a shit about your job enough to not pass the buck. Devops means giving a shit about your job enough to want to learn all the parts and not just your little world. Developers need to understand infrastructure. Operations people need to understand code. People need to fucking work with each other and not just occupy space next to each other. -- John Vincent (@lusis)
15. CAMS
16. Culture https://flic.kr/p/eAJtpr
17. Automation
18. Measurement
20. CALMS
21. An Tool
22. So about that... I cant sell you 
 The DevOps
23. So What Does Your World Look Like?
24. Silos?
25. Think about the! reporting structure
26. Can you go straight across to your peers?
27. Does everything require approval from the highest levels?
28. How does "it" get into Production?
29. Can you just "Ship It”
30. Who does the actual deploy?
31. Do you have to beg and plead for a VM?
32. Did I hear someone mention change control?
33. Responsibility
34. Who owns it in prod?
35. Is it monitored?
36. What does a modern team look like?
37. Possibly, a lot like your current one does…
38. Communication
39. Dev and Ops 
 (and all the other disciplines) 
 talk to each other across 
 organizational boundaries
40. The focus is on fixing and improving the software and not blaming others
41. Other team are involved early on in discussions and given ample ability to provide feedback
42. Teams that get the chance to be involve early don't consistently become blockers
43. Different disciplines work to understand the language of others
44. Examples
45. The database is overloaded... Ops works with Dev to understand the busted query or queries
46. We discuss how an app gets to prod, when we start to write it, not after we have decided on the tech.
47. You don't get a say if all you can do is tell me why none of it is going to work.
48. Dev fixes ! vs ! Ops fixes
49. Dealing with Prod
50. "You build it,! you own it"
51. Big Releases ! vs! Small Releases
52. MTTD and MTTR! vs! MTBF
53. The Tools Matter
54. Collaboration…! LOL WUT
55. Is code shared?
56. Do they provide metrics?
57. Are they shared and the same?
58. Shipping
59. Homework • Web Operations: Keeping the Data On Time by John Allspaw and Jesse Robbins • The Phoenix Project: A Novel about IT, DevOps and Helping Your Business Win by Gene Kim, Kevin Behr, and George Spafford • Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation by Jez Humble and David Farley
60. Resources • Adam Jacob - Choose Your Own Adventure (DevOps) - Velocity 2010: https://www.youtube.com/watch? v=Fx8OBeNmaWw • Nathen Harvey - DevOps: No Horse Shit - ChefConf 2014: https://www.youtube.com/watch?v=0P0HD5pE-zU • John Willis - What Devops Means to Me: https:// www.getchef.com/blog/2010/07/16/what-devops-means- to-me/ • John Vincent - DevOps - the Title Match: http:// blog.lusis.org/blog/2013/06/04/devops-the-title-match/
61. Questions?