5 (or maybe 6) things you should touch before going ZeroTouch Jos - - PowerPoint PPT Presentation

5 (or maybe 6) things you should touch before going ZeroTouch

José Bonnet, AlticeLabs, 22nd March, 2018, Madrid

‘Sponsored by’

. 2

http://sonata-nfv.eu

https://github.com/sonata-nfv

http://5gtango.eu

3

4

Technologies, processes & tools

http://cdn.wonderfulengineering.com/wp-content/uploads/2014/06/gear-wallpaper-6.jpg

Complex!

• Source Code

Management/Version Control Systems

• Continuous Integration
• Deployment
• Cloud/IaaS/PasS
• BI/Monitoring
• Database Management
• Repository Management

Processes…

• Configuration/Provisioning
• Release Management
• Logging
• Build
• Testing
• Containerization
• Collaboration
• Security

. 6

Frightening, isn’t it?

. 7

5GTANGO adopted tools

. 8

• Source Code Management/Version

Control Systems: Git/GitHub

• Continuous Integration: Jenkins
• Deployment: Jenkins
• Cloud/IaaS/PasS: OpenStack
• BI/Monitoring: internal tool
• Database Management: -
• Repository Management:

DockerHub

• Configuration/Provisioning: Ansible
• Release Management:

GitHub/Manual

• Logging: Graylog
• Build: Jenkins/Docker
• Testing: depends on PL/shell
• Containerization: Docker/Kubernetes
• Collaboration: Gitter/GitLab’s issues
• Security: Snort

5GTANGO DevOps flow

. 9

Scrum

. 10

http://highlanderrugby.com/wp-content/uploads/2016/10/womenclevelandscrum.jpg?x65310

Kanban/Lean

. 11

https://static01.nyt.com/images/2013/09/18/business/TOYODA-obit-web/TOYODA-obit-web-master1050.jpg

• …it should work for you, and not the other way around!
• ...there is always a cost in adopting it:
• Developer’s training;
• Tools integration/adaptation;
• Habits/culture changing

Whatever the methodology…

. 12

• Defining your objectives…
• ...per sprint, version, month, customer...
• ...but not too many: don’t build a ‘team to measure the objectives’
• ...and measuring them often:
• Caveat: a team can quickly adapt its dynamics and start working ‘for the objective(s)’ only!
• Adapting ‘methodologies’ to your own reality
• Focusing on:
• speed of delivery: gives you many competitive advantages;
• continuous delivery: breaks your problem into valuable/working

pieces – more on this later

• Embracing diversity:
• costs are higher at the beginning, but will make your

environment(s) more plastic

• Offering everyone in your team a copy of Betsy Beyer’s et al

(editors) ‘Site Reliability Engineering’

Start by:

13

14

15

Product Management

• I know, most of us aren’t…
• ... But going after ‘zero-touch’ will make your:
• …teams more efficient
• …processes leaner and more flexible
• And… maybe we all should be a product-oriented shop:
• Deciding on a ‘per customer’ base looks easier, isn’t it?

…but I’m not a product oriented shop!

16

• The Product Manager is not…
• ... the Product ‘Marketeer’
• ... the Project Manager
• ... the Product Designer
• ... the Product Engineer
• The Product Manager is the one who...
• … best knows his/her potential customers/market
• …assesses product opportunities
• …defines the product to be built
• But the key characteristic of a Product Manager is…

What is the Product Manager?

17

…to know how to cut the product into meaningful slices

. 18

https://d1cvtajkxcatn5.cloudfront.net/cache-buster- 1407145440/com/key_visuals/600x400px/construction_timber__new_ 600x400.png

• Letting you Product Managers master their product’s market and

customers

• Offering Product Manager of your team a copy of Martin Cagan’s

‘Inspired’ book…

• ...and making sure they read it!
• Empowering your Product Managers, make them

accountable

• Encouraging failure… if numbers are not bright
• Remembering that you are not your customer!

Start by:

19

20

21

Infrastructure (as code)

22

Stop treating your infrastructure as pets…

http://animalercare.com/clients/19508/images/Group_cats_and_dogs.jpg

…treat them as as cattle!

. 23

http://michaelseebeck.com/wp-content/uploads/2013/11/tablelands-cattle-haqt0086.jpg

• …not humans:
• Save humans for non-repetitive tasks, they will thank you (more on this later)
• Version controll every script
• Mind that:
• not all customers will allow you access to their infrastructure
• Installed machines start diverging from the moment they’re installed!

Have scripts installing machines…

24

• Having a centralized inventory of your computing and network

resources

• Allowing teams to request resources, but make them accountable for

those that are granted:

• Every requested resources have costs, even though they are a small fraction
• f ones we used to have (with bare metal)
• Offering everyone in your team a copy of Kief Morris’

‘Infrastructure as Code’ book!

Start by:

. 25

26

27

Software development

28

Software is eating the world

‘Why Software Is Eating The World’, Marc Andreessen, Aug, 20th, 2011

Different activities in software development

. 29 Breakdown of Effort Cost - Software Cost Estimation by Capers Jones

Open-source

. 30

12 factors App

. 31

https://12factor.net/

• Describe your software (‘network services’ composed of inter-

connected ‘network functions’)

Descriptors

. 32

• Virtual Network Functions are implemented by one or more Virtual

Deployment Units (VDUs – VMs or Containers)

Descriptors

. 33

• Basic/initial:
• https://github.com/sonata-nfv/son-examples/blob/master/service-projects/sonata-

fw-vtc-service-update-sp/sources/nsd/sonata-demo.yml

• https://github.com/sonata-nfv/son-examples/blob/master/service-projects/sonata-

fw-vtc-service-update-sp/sources/vnf/fw-vnf/fw-vnf-vnfd.yml

• https://github.com/sonata-nfv/son-examples/blob/master/service-projects/sonata-

fw-vtc-service-update-sp/sources/vnf/vtc-vnf/vtc-vnf-vnfd.yml

• More complete/recent (vCDN pilot):
• https://github.com/sonata-nfv/son-vcdn-pilot/blob/master/NSD/sonata-vcdn.yaml
• https://github.com/sonata-nfv/son-vcdn-

pilot/blob/master/VNFs/vCC/Descriptor/vCC-vnfd.yml

• https://github.com/sonata-nfv/son-vcdn-

pilot/blob/master/VNFs/vTC/Descriptor/vtc-nfd.yml

• https://github.com/sonata-nfv/son-vcdn-

pilot/blob/master/VNFs/vTU/Descriptor/vtu-nfd.yml

SONATA’s examples

. 34

The way you deploy your software is changing!

That is…

. 35

Serverless: are you ready?

. 36

• Knowing that software development is not just writing code:
• Project management
• Tests (several kinds of)
• Documentation (several kinds of)
• Reviews
• …
• Using more and more open-source, and giving back!
• Offering each one of your developers a copy of

Robert Martin’s ‘Clean Code’ book!

Start by:

37

38

39

Automate everything

. 40

https://builttoadapt.io/why-tdd-489fdcdda05e

Automation vs. speed (of delivery)

Continuous delivery: still a lot to gain!

. 41 http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-continuous-deployment

Automated tests: most of them

. 42

Faster, ran often Slower, ran less often

Even chaos can be automated!

43

https://medium.com/netflix-techblog/the-netflix-simian-army-16e57fbab116 https://github.com/netflix/chaosmonkey Netflix’s Chaos Monkeys

• Looking for repetitive tasks being executed manually:
• Assess them thoroughly: how often have they been executed today/last

week/last month?

• How many people do you need to execute them? How much does it costs?
• Investing the equivalent of the recent cost of executing them

manually in automating them:

• Legacy products: cost/benefit depends on life expectancy
• Offering everyone in your team a copy of Humble &

Farley’s ‘Continuous Delivery’ book

Start by:

. 44

45

Find the best!

. 46

http://www.todayifoundout.com/wp- content/uploads/2014/11/crowd.jpg

People!

…and let them be software engineers!

. 47

AI for software development?

. 48

http://setuix.com/is-artificial-intelligence-dangerous/

. 49

https://cdn-mf0.heartyhosting.com/sites/mensfitness.com/files/styles/gallery_details_image/public/cristiano-ronaldo-real- madrid-gallery-3_1.jpg?itok=BCBYasj9

Heroes…

…piano carriers are also needed!

50

http://pianomoversguide.com/wp-content/uploads/2014/07/speciality-piano-mover.jpg

. 51

https://pcdn.disabilityscoop.com/wp-content/uploads/2017/08/ds170829_puzzle.jpg

People are very seldom inter-changeable!

Differences have costs

52

http://smallville.com.au/wp-content/uploads/2016/11/rsz_ac60848379920435bf42afa1daa68575-1.jpg

. 53

hefabweb.com/wp-content/uploads/2012/09/20Tc2.jpg

If you pay in peanuts…

Start by:

• Attracting the promising…
• ...and retaining the best…
• Accepting that the best ones may not be with you forever:
• They can’t be at 100% performance 100% of the time;
• Someone better than you will attract them;
• Avoiding pre-conceptions: the best can be anywhere, working from

anywhere;

• Not paying in peanuts, or you will only attract those that you

competitors have found to be… unattractive!

55

Key takeaways

• People:
• hiring and retaining the best pays back in competitive advantages; the team is the

hero, not any of the individuals

• Automate everything:
• Helps a lot retaining your people, increases reliability and predictability
• Software Development:
• Apply basic principles and start ‘describing’ your software
• Infrastructure as code:
• Treat your infrastructure as cattle, instead of as pets
• Product Management:
• Learn to slice the product into features and prioritize them
• Technologies, processes and tools:
• Embrace diversity, do not ‘fall in love’ with just one

Key takeaways

56

57

Thank you!

• jbonnet@alticelabs.com