A session in the DevNet Zone at Cisco Live, Berlin. At the moment, this is the DoE: DevOps of Everything. DevOps is about culture first but many people take shortcuts to tools and workflow. They forgot the essence of DevOps which is about people and not only from Dev to Ops. In this session, we will show you how we are currently building a DevOps culture with a focus on continuous improvement.

2. How Cisco is building a
DevOps Culture
Jérémie Garnier – Expert Development

3. • What is DevOps?
• DevOps journey
• Continuous improvements
• Conclusion
Agenda

4. jegarnie@cisco.com:~$ whoami
• Development Expert
• Currently working on a Big Data Platform called PaNDA
http://panda.cisco.com & https://developer.cisco.com/site/panda/
• Like new technologies
• Collaboration & sharing
• DevOps evangelist

5. “In theory there is no difference between
theory and practice; in practice there is.”
Walter Savitch

6. 6
Source: http://cdn.oreilly.com/radar/images/posts/0612-what-is-devops-cover.jpg

7. DevOps of Everything

9. 9
Source: http://www.colonlibrary.org/wp-content/uploads/2015/03/magic-trick.jpg

10. 10
Source: http://sd.keepcalm-o-matic.co.uk/i/keep-calm-and-step-back.png

11. 11
DevOps is about breaking down the Development & Operations Silo and getting
both focused on the business goals of software
What is DevOps?

12. 12
Patrick Debois
DevOps: optimize the whole
CustomerBusiness
Theory of Constraints
HR MGMT FIN
SALES DEV OPS
Source: http://www.jedi.be/blog

13. 13
John Willis - What DevOps means to me
Culture
DEV OPS
Automate
Measure
Share

14. 14
Source: https://www.sweetprocess.com/wp-content/uploads/2013/07/first-procedure-to-document.jpg
• Higher performance
• Higher quality
• Remove bottlenecks
• Remove Silos
• Less manual work
• Delivery: more frequent & lighter
• Minimize risk (shorter product backlog - iterate)
• Tightly coupled with business objectives
Why DevOps?

15. 15

16. Development has changed
16
Source: http://image.slidesharecdn.com/devopsguys-devops101forrecruiters-140117090454-phpapp02/95/devopsguys-devops-101-for-recruiters-8-638.jpg?cb=1390435671

17. How?
17

18. How?
18
Agile frameworks:
Scrum / Kanban
Continuous integration Continuous testing Continuous delivery
Continuous load testing Continuous deployment Continuous monitoring
Continuous feedbacks
Continuous penetration
testing
Continuous
improvements
Dashboards
Automation
Sourcecontrol

19. 19
DevOps Journey: road to success
Source: http://devops.com/2014/03/16/the-devops-journey/

20. 20
Starting as Developer
(Before 2010)

21. 21
Source: http://www.techspot.com/images2/news/bigimage/2015/08/2015-08-20-image-27.jpg

22. 22
Source: http://33.media.tumblr.com/df06ab544c2cfddc6fad7242ca1a0fb0/tumblr_inline_nng15xQt631raprkq_500.gif

23. 23
Moving to Agile
(2010)

24. 24

25. 25

26. 26

27. 27
Workflow

28. 28
Oct
April
May
v1.0 v1.0.1
v1.0.2
1st SDP
deployment
v1.0.3
v1.0.4
v1.0.5 v1.0.6
June
v1.0.7
v1.0.8
v1.0.9
v1.0 v1.0.1 v1.0.2 v1.0.3 v1.0.4
v1.0.5
v1.0.6
July Aug. Sept
v1.0.10
v1.0.11
v1.0.12
v1.0.13
v1.0.14
v1.0.15
v1.0.16
v1.0.17
v1.0.18
v1.0.19
v1.0.20
v1.0.21
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.1.4
v1.0.7
v1.0.8
v1.0.9
v1.0.10
v1.0.11 v1.0.12
v1.0.13
v1.0.14
v1.0.15
APISoftbox

29. 29
• Ops working with Dev (shared
tools / scrums / backlog)
• Each iteration:
• Adding more tests, automation, scripts, documentation…
• Code review
• Everyone was coding !
Source: http://blog.psoda.com/wp-content/uploads/2014/07/lessons-learned.png
Step back

30. Something missing?
30
• Not everything under source
control
• No continuous integration /
delivery / deployment (manual
steps)
Source: http://www.rebellesociety.com/wp-content/uploads/2013/11/missingpiece.jpg

31. 31
Moving to DevOps
New Tools & Technologies
2012 - 2013

32. Cloud TV system born in the cloud
32

33. Feature and chapter teams
33

34. Workflow
34

35. Step back
35
• DevOps need to be considered at Day 0
• You need Ops team
• 6 deployments per day
• Dashboard with commit/tasks deployed in
staging/production
• Dedicated infra team is not working

36. 36
Moving to DevOps
SaaS, Docker & DevOps
2013 - 2015

37. New approach / tool / technologies
37

38. 38

39. Workflow
39

40. Step back
40
• Flexible solution & team
• Continuous improvements !
• More details:
https://www.youtube.com/watch?v=2GaDYdja2P8
2015 #vBrownBag at Cisco Live! Jeremie Garnier CI:CD:CT on
a Microservices Applications

41. 41
2015
Moving forward

42. Canary release
42
• Canary Release definition is a
technique to reduce the risk of
introducing a new software version
in production by slowly rolling out
the change to a small subset of
users before rolling it out to the
entire infrastructure and making it
available to everybody.

43. Open Source and technologies
43

44. Workflow
44

45. 45
Source: https://mystery756.files.wordpress.com/2012/07/yoda-do-or-do-not-1.jpg

46. Continuous improvements

47. 47
Source: http://thisisindexed.com/wp-content/uploads/2010/11/card27451.jpg

48. DevOps Unconferences
48
• Open Spaces
• Lightning talks
• https://developer.cisco.com/devops

49. Books
49

50. DevNet
50

51. 51
Source: https://s-media-cache-ak0.pinimg.com/736x/d4/55/9b/d4559b9cf76fe91919ee94e875b21e75.jpg

52. 52

53. 53
Source: https://c2.staticflickr.com/8/7053/6824930292_a9b4287135_b.jpg
jgarnier19
jgarnier

54. Thank you