Overview of DevOps

Overview of DevOps
Phil Huang
SDN Solution Engineer, Edgecore Networks Corporation
Dec 1, 2016

View Slide

Summary
© 2016 Edgecore Networks. All rights reserved. Subject to errors and misprints. |
www.edge-core.com
Overview of DevOps
01
04
02
Overview of NetDevOps
03
DevOps Case Studies

View Slide

Who am I?
3
© 2016 Edgecore Networks. All rights reserved | www.edge-core.com
§ Phil Huang
§ Edgecore SDN Solution Engineer
§ ONOS/CORD Ambassador
§ Familiar with
§ Open Source / DevOps / NetDevOps
§ SDN Open Source Committer
§ ONOS / Mininet / ONIE
§ Project
§ Global ONOS SDN-IP Deployment, Taiwan
§ GitHub
§ pichuang

View Slide

General Product Team
4
Ref: http://www.mindtheproduct.com/2016/02/what-the-hell-are-ci-cd-and-devops-a-cheatsheet-for-the-rest-of-us/
You QA/QC PM Operator

View Slide

Problem1: What’s wrong?
5
Ref: http://www.mindtheproduct.com/2016/02/what-the-hell-are-ci-cd-and-devops-a-cheatsheet-for-the-rest-of-us/

View Slide

Operator got…
6
Ref: VMWare ESX Host Purple Diagnostic Screen

View Slide

PM & QA think…
7

View Slide

You think…
8

View Slide

Problem 2: Lead time Too Long
9
§ Lead Time
§ Time between request to delivery
ØThis is what customer sees
§ Cycle Time (or Process Time)
§ Time between production start to completion
ØNot visible to customer
Ref: http://www.slideshare.net/Managewell/lean-and-kanbanbased-software-development
Time
Request Delivery
Production Start
Lead Time
Cycle Time

View Slide

No Value, No Revenue
10

View Slide

Problem 3: Schedule Visibility
11
Result
Visible Part
Mindset
Thinking
Invisible Part
Experience
You
Dirty work

View Slide

Problem 4: Human Error Race
• 80% of outages impacting mission-critical services will be caused by
people and process issue
• 20% of those outages will be caused by
change/configuration/release integration and hand-off issues
© 2016 Edgecore Networks. All rights reserved | www.edge-core.com 12
Ref: http://www.slideshare.net/giganati/is-orchestration-the-next-big-thing-in-devops

View Slide

Problem 5: What happened in your system?
13
Administrator control
via GUI and CLI
Crontab from system
Force majeure
…
Input Output

View Slide

Why DevOps?
14
§ Collaboration
§ Developer + Operator
§ Reduce challenges related to Ops and Dev collaboration
§ Deployment
§ Minimize deployment related downtime
§ Minimize roll-backs of deployed application
§ Defect resolution
§ Minimize MTTR
§ Increase the ability to reproduce and fix defects
MTTR = Mean Time To Resolution

View Slide

DevOps is about CALMS
15
§Culture
§ More communication with team member
§Automation
§ The idea that you should program everything
§Lean
§ Keeping everything to a minimum
§Measurement
§ Try to have visibility into everything
§Sharing
§ Regular exchanging of ideas across team

View Slide

Culture
16
More Feedback
Communication
Automation

View Slide

Culture
17
Waterfall
Plan Code Build Test Release Deploy Operate
Time
Plan
Code
Build
Test
Release Plan
Code
Build
Test
Release Plan
Code
Build
Test
Release
Agile

View Slide

Automation
18
§ DevOps Lifecycle
Plan Code Build Test Release Deploy Operate
Monitoring
Metrics
Analytics
Feedback

View Slide

Automation
19
Plan Commit Build Test Release Deploy Operate
Monitoring
Metrics
Analytics
Feedback
Continuous Integration
Continuous Delivery

View Slide

Lean
20
§MVP ( Minimal Viable Product )
§ Set a goal
§ Minimum cost
§ Time, Money…etc
§ Feedback from customer
§ Continual Improvement
Ref: http://justinmcgill.net/product-idea-validation-dont-build-mvp/

View Slide

Lean
21
Ref: https://blog.engineyard.com/2015/actually-mvp

View Slide

Measurement
22
§ Data collection
§ Syslog, performance data
§ Definition of measurement
§ Data visualization
§ A picture is worth a
thousand words
§ Data analysis
§ Find business value

View Slide

Sharing
23
§ Focus on communication
§ Any experiences for team
ØFocus on people

View Slide

2016 State of DevOps Report
24
Ref: https://puppet.com/resources/white-paper/2016-state-devops-report/

View Slide

Periodic Table of DevOps Tools
25

View Slide

Develop workflow
26
You
Workflow
1. Launch VM
2. Setting environment
3. Install applications
4. Quick start
5. Develop
6. Compile
7. Re-install application
Choose Hypervisor, CPU, RAM, Disk size, location
Bash, vim, dependency package
View INSTALL file
View README files
View Developer’s Guide

View Slide

Develop workflow
27
You
Workflow
1. Launch VM
4. Quick start
5. Develop
6. Compile
View INSTALL file
View README files

View Slide

Baby Step 1 – Reduce Routine Manual Job
$ cd $PROJECT_ROOT
$ python setup.py build
$ python setup.py install
$ cd $WORK_ROOT
$ ./service start
• $ /usr/bin/rebuild.sh
Manually One-Click
#!/bin/bash
set -x
cd $PROJECT_ROOT
python setup.py build
python setup.py install
cd $WORK_ROOT/service start

View Slide

Baby Step 2 – Version Control Everything
• $ /usr/bin/rebuild.sh
#!/bin/bash
set -x
cd $PROJECT_ROOT
echo “Start build”
python setup.py build
echo “Start install”
python setup.py install
cd $WORK_ROOT/service start

View Slide

Develop workflow
30
You
Workflow
1. Launch VM
4. Quick start
5. Develop
6. Compile
View INSTALL file
View README files

View Slide

Baby Step 3 – Packer + Vagrant
31
Provisioning
Runtime VM

View Slide

Case Study - OpenSource Contribution Workflow
32
Ref: http://docs.openstack.org/infra/manual/developers.html
You

View Slide

Gerrit Code Review
33

View Slide

Jenkins
34

View Slide

Case Study - CISCO
35
Ref: http://www.slideshare.net/CiscoDevNet/enabing-devops-in-an-sdn-world

View Slide

Case Study - Spirent
36
Ref: http://dw.connect.sys-con.com/session/2779/Marc_Hornbeek.pdf

View Slide

Case Study – BigSwitch Chaos Monkey
37

View Slide

What is NetDevOps?
38
§ Infrastructure as Code (IaC)
§ Bare Metal network
§ VM network
§ Container network
Ø Configuration Management
§ Network automation
ØRapid provisioning

View Slide

Traditional Networking Methodology
39
§ Logging in manually with a password
§ Typing commands
§ Copy and paste over console or terminal
§ Check, check and check..

View Slide

Step 1: Using Git & GitHub
40
§ Configuration file repository
§ File change and revision management
§ Build for teams to work the same files

View Slide

Step 2: Commit Your Configuration
41
$ git add .
$ git commit -a -m "Add new switch configuration" –s
[master 8cf8a38] Add new switch configuration 1 file
changed, 1 insertion(+) create mode 100644
ofswitch.conf
$ git push -u origin master

View Slide

Show Changes In Action
42

View Slide

Blame someone
43
$ git blame ofswitch.conf
69f5f511 (Phil Huang 2016-11-01 13:59:23 +0800 1) Phil Huang
69f5f511 (Phil Huang 2016-11-01 13:59:23 +0800 2) is a
60643262 (Phil Huang 2016-12-01 15:00:51 +0800 3) good
69f5f511 (Phil Huang 2016-11-01 13:59:23 +0800 4) man

View Slide

Step 3: Choose CM
44

View Slide

Ansible Network Modules
45

View Slide

Step 4: Templatize Configuration Files
46
§ Let you reuse code snippets
§ Avoid human error and typos
Ref: https://github.com/CumulusNetworks/cldemo-netq-l3

View Slide

Step 5: Virtualize Copy of Network
47

View Slide

Step 6: Continuous Integrations System
48
§ Catch error or typos early
§ Make sure all of the setting is same
as production

View Slide

Summary
49
§ More communication
§ Get early feedback
§ Automate everything
§ Version control
§ Visibility

View Slide

Recommend Books
50

View Slide

51
Open Networking
from
Freedom
Control
Innovation

View Slide

Overview of DevOps

Overview of DevOps

Phil Huang

More Decks by Phil Huang

Other Decks in Technology

Featured

Transcript