Devs are from Mars, Ops are from Venus, Maish Saidel-Keesing, Cisco
Download as PPTX, PDF2 likes477 views
The document discusses differences between developers (Devs) and operations (Ops) teams. It notes that while DevOps aims to bring these teams together, Devs and Ops have different priorities and ways of working. The document presents examples of tools, terminology, definitions of done, and challenges each team faces to illustrate how Devs are focused on writing code while Ops ensures systems are running stably. It suggests finding ways to better align these two "different species" through approaches like defining requirements and project handovers.
Devs are from Mars, Ops are from Venus, Maish Saidel-Keesing, Cisco
- 1. Devs are from Mars, Ops are from Venus #DevOpsDays Platform Architect Cisco November 23rd, 2014
- 2. A Little Bit About Me • Maish Saidel-Keesing - @maishsk • Blogger – Technodrone (http://technodrone.blogspot.com) • Platform Architect – Cisco, Israel • OpenStack Architecture Design Guide Co-Author of VMware vSphere Design • vExpert, VCAP5-DCD/DCA blah blah blah ….. © 2013-2014 Cisco and/or its affiliates. All rights reserved. 2
- 4. “we are unique individuals with unique experiences” ― John Gray © 2013-2014 Cisco and/or its affiliates. All rights reserved. 4
- 5. • DevOps.. DevOps everyone is talking about DevOps!! • Just stuffing people in a scrum together doesn’t make it work. • We are two different species © 2013-2014 Cisco and/or its affiliates. All rights reserved. 5
- 6. Hacking a workaround that surprisingly works well © 2013-2014 Cisco and/or its affiliates. All rights reserved. 6
- 7. Devs care about Code Writing Software Getting Thing 1 to work with Thing 2 © 2013-2014 Cisco and/or its affiliates. All rights reserved. 7
- 8. Keeping the systems running © 2013-2014 Cisco and/or its affiliates. All rights reserved. 8
- 9. Ops care about Not getting too many alerts at 02:56 Things are stable Standards Everything is Green © 2013-2014 Cisco and/or its affiliates. All rights reserved. 9
- 10. Tools - Devs IDE Simulators Jenkins SCM – git, svn DB tools - SQLDeveloper, MongoVUE Maven © 2013-2014 Cisco and/or its affiliates. All rights reserved. 10
- 11. Not sure how, but it’s working © 2013-2014 Cisco and/or its affiliates. All rights reserved. 11
- 12. Tools - Ops Scripts Infrastructure Hardware Servers Storage Switches © 2013-2014 Cisco and/or its affiliates. All rights reserved. 12
- 13. New high end server arrived © 2013-2014 Cisco and/or its affiliates. All rights reserved. 13
- 14. Terminology - Devs Sprints Scrum Release Continuous Integration / Delivery Kanban Libraries © 2013-2014 Cisco and/or its affiliates. All rights reserved. 14
- 15. Sysadmins being introduced to Kanban © 2013-2014 Cisco and/or its affiliates. All rights reserved. 1155
- 16. Terminology - Ops Requirements (not what the software should do!) Change Management Availability Support / Helpdesk © 2013-2014 Cisco and/or its affiliates. All rights reserved. 16
- 17. Redundancy © 2013-2014 Cisco and/or its affiliates. All rights reserved. 17
- 18. Definition of Done - Devs Whatever the Sprint says it should be It works!! in Vagrant in Devstack on my laptop © 2013-2014 Cisco and/or its affiliates. All rights reserved. 18
- 19. Definition of Done - Ops Software is stable Backup/restore works Highly available Monitoring with defined thresholds © 2013-2014 Cisco and/or its affiliates. All rights reserved. 19
- 20. Project handover © 2013-2014 Cisco and/or its affiliates. All rights reserved. 20
- 21. Tétine (flickr) © 2013-2014 Cisco and/or its affiliates. All rights reserved. 21
- 22. The two sides of XaaS: Development vs. What the world sees © 2013-2014 Cisco and/or its affiliates. All rights reserved. 22
- 23. Links @maishsk My Blog – Technodrone DevOps Reactions © 2013-2014 Cisco and/or its affiliates. All rights reserved. 23
- 25. Thank you.
Editor's Notes
- #4: Which one is Venus? Mars? I only looked that up – we don’t really know other people until we need to
- #5: Which one are you? How Many developers here? How many Sysadmins? There is no such a thing as an Op. Infra Admin, sysadmin
- #6: I am an Ops guy – have always been – I dabble in Code but mainly the infrastructure part is my passion. Developers and Operations don’t have the same outlook on life Werewolves, Vampires – I don’t like that analogy – we are both people, good people. But different. Extreme stereotyping here – on purpose – but still please forgive me.
- #7: Does this work – yes. Will the solution work in the long run?
- #8: Code is a work of art, immortal. We make things – from nothing. From a drawing on a whiteboard. Getting thing 1 and thing 2 to work together does not mean that it will work in an enterprise environment
- #10: Who do you think get’s an alert when it hits the fan? Applications do not behave sporadically, I know what it does – all day, every day. Don’t go introducing some new kind of fangled database every new version We actually don’t really like dashboards…. ;) that is for managers.
- #11: Ops might answer to these IDE – that is a disk interface isn’t it Simulator – I played flight simulator once Jenkins – isn’t he that butler guy? SCM – a place people keep code?? Branch – I climbed a branch once as a kid.. DB tools – I can install the DB for you Maven – I understand.
- #13: Scripts – we are really good – I even wrote a 500 line script to automatically install Oracle RAC once – but I do not write software. We have virtualized infrastructure – which usually works very well. That paper clip is a real tool – to power servers on and off. Big button does not exist on a server
- #15: Sprints – 100 / 400 meters? Scrum – I do not do rugby Library – the place with books isn’t it?
- #17: Requirements – how much CPU/RAM/network/Disk/IO are you going to need. But really need! Availability – what happens to the applications when I loose a server, rack, datacenter. Support – is not only the guy you call when your thing is not working.
- #19: There are other things besides the small world you live in. What about VLAN’s? What about firewalls?
- #21: Handoffs should not be like this. Actually there should not be any handoffs – because a true Devops team does not pass the app to someone else. They support it – from development -> deployment -> retirement.
- #22: Oil and Water – they do not mix, they are fundamentally different They are each special – each has their upsides – and downsides. Learn from each other. Do not care about your own world, make the effort to learn about the other’s as well.
- #25: Give each other a hug. Have coffee/beer/Shawarma together. Most importantly talk. Listen, and work together.