1. OPEN-O DevOps Practice with Automation Toolchain
Helen Chen
Principal Architect,
PTL of OPEN-O Integration
Weidong Shao
Principal Engineer

2. Agenda
OPEN-O Introduction
DevOps Practice: Toolchain
Compass

3. Agenda
OPEN-O Introduction
DevOps Practice: Toolchain
Compass

4. Service Agility Calls for Open Source Orchestration
Developers
Weak development capability
How to orchestrate SDN /NFV and legacy networks?
Orchestrator
Open - Orchestrator
Complex
legacy OSS for new services
SDN / NFV
Service agility is the main driven force for telco transformation. SDN and network virtualization made telco’s network more agile. Unfortunately, they also introduce new complexities and new challenges.
Normally, the telco doesn’t have very strong software development capabilities
how to manage and operate a hybrid networks with the new SDN / NFV network, together with Legacy networks?
And the connectivity service delivery is much more complex in telco networks, and their VNFs needs much higher reliability, % such 5 9s. It is very difficult for traditional OSS to orchestrate them while preventing vendor lock-in
Because of those issues, in earlier this year, Huawei, China Mobile and Linux foundation with anther 12 partners proposed an open sourced orchestrator: OPEN-O.

5. OPEN-O: Any Service Over Any Network
Multi- SDN Controller
Multi-VNFM /VIM
Multi-EMS
APP / BSS / OSS
OPEN-O
It’s about the services
* End-to-end
* Model-driven
Redevelop brownfields
* Connectivity services
* SDN and EMS system
Tailored to the operator
* Guided by real use cases
* Modular framework
The primary goal of OPEN-O is to create a carrier-grade open-source end-to-end service orchestration platform, bridging the gap between NFV, SDN, and Legacy Network Services to enable Any Service over Any Network.
There’re three main values for service providers:
OPEN-O is about the services, with OPEN-O, the service providers could focus on how to bring in new services and value to their customers without worrying about the basic network infrastructure. OPEN-O’s model-driven capability and end to end service and resource orchestration, could accelerate the telco operators on boarding new services. For those who have strong software development capability, they could leverage OPEN-O to build their Open platform. For those who don’t want to build their own, OPEN-O brings them options of choosing a commercial solution based open source to prevent vendor lock-in.
OPEN-O provides a unified connectivity services over legacy networks and SDN / NFV networks. It also provides orchestration capabilities on top of traditional EMS and SDN system.
Since OPEN-O is guided by service providers’ real use cases, it serves the service providers the best. OPEN-O’s modular framework with standard open API allows service providers easily extend and customize according to their network. To the south, it helps to integrate with multiple vendors; to the north, it could easily connect with its own OSS to solve the services and resource orchestration over the hybrid networks.

6. OPEN-O Latest Update Launched June 7, 2016
Released Sun Release at Nov 3, 2016
Working toward Mercury release at April 27, 2017

7. Agenda
OPEN-O Introduction
DevOps Practice: Toolchain
Compass

8. The Challenges for OPEN-O Integration
5 months release cycle
Codebase
13 projects
56 Repos,
1,553,618 LOC (as of 4/1/2017)
Developers
125+
Span 16 hours of time zones: Asia, Europe, US
End-to-end multi-vendors’ real equipment, PNF and VNF, deployment in Integration community labs

9. OPEN-O DevOps Practice
Software Architecture: Microservices
Continuous Integration is important; testing is key
Unit tests: 50% coverage
System integration tests
A full DevOps toolchain
When people talk about DevOps, there’s cultural change, but open source seems fine.

10. OPEN-O Highly Modular Architecture Helps DevOps
Common Service HA
Log
Driver Mgr.
Micro-Service Bus
Protocol Stack
Auth.
Client
GS-O
Service Decomposer
Service Lifecycle Mgr.
Service
Formation
Abstract NBI
13 Projects
~60 Microservices
GUI Portal
CLI
Common
TOSCA
Workflow
Parser
Catalog
Model
Designer
SDN-O
NFV-O
Abstract NBI
Abstract NBI
SDN
Monitor
SDN Lifecycle Mgr.
NFV Monitor
NS Lifecycle Mgr.
VPN
Holmes
SDN Res.
Mgr.
Traffic Optimize
NFV Res. Mgr.
Policy
Abstract SBI
Modeling
Abstract SBI
SDN Hub
Driver
ACCESS/WAN SDN Controller Drivers
Cloud Drivers
NFV
Driver
VNF SDK
NFV SDN
Controller Drivers
VNFM Drivers
VIM Drivers
OPEN-O Mercury release has 13 projects. It consists of a hierarchy of 3 orchestration modules:
Three high light of OPEN-O Architecture:
First of all, It is modle-driven. OPEN-O has adopted standard service modeling languages YANG and TOSCA to ensure extensibility, implementation efficiency, and interoperability. Operators could use OPEN-O graphics model designer to create the business flow by drag and drop
OPEN-O’s Modular framework with standard OPEN API allow telco to easy extend its functionality
Micro-service architecture allows telco to deploy any combination of services.
GVNFM
Integration

11. OPEN-O Toolchain OPEN-O Toolchain covers key aspects of DevOps:
code, build, test, package, release, deployment, configuration, and monitoring
git: version control
gerrit: code review
Jira: ticket system:
confluence: wiki
Bitergia: activity report
sagger: API
zoom: meeting
Nexus: release server
Jenkins is an open source automation server written in Java
slack: chat
sonarqube: unit test coverage report
Maven can manage a project's build, reporting and documentation from a central piece of information based on POM

12. CI Toolchain: Gerrit Widely used in open source projects:
OPEN-O, OpenStack, OpenDaylight, OPNFV, etc.
Facilitates collaboration between developers.

13. CI Toolchain: Jenkins
Continuous integration server widely used in open source projects
Extensive support of plugins

14. OPEN-O CSIT Infrastructure
OPEN-O Mercury has 79 CSIT test suites, 519 test cases
Test Suites written using Robot Framework
OPEN-O Microservices run via docker
Mock southbound services run via docker using Moco Simulator
e.g. mock VIMs or SDN controllers
Robot test suites executed via Jenkins
Jenkins Master
Jenkins Slave VM
Robot process
OPEN-O Microservice 1
OPEN-O Microservice 2
Docker Containers
OPEN-O Microservice 3
Mock Services / Components
Continuously run System and Integration Tests against any code changes
Maintain quality and detect regressions
Detect and prevent breaking code changes
Each test suite runs on a fresh Jenkins slave VM
Docker containers run within single VM
Robot process runs on VM directly
Supports parallel test runs

15. OPEN-O Jenkins Job Flow
SonarQube
(Static Analysis)
Code
Per Project
Code Change Proposed
Code
Verify Job
/ Unit Test
Pass?
Code Change Merged
Code
Merge Job
/ Unit Test
Yes
Nexus
(Java SNAPSHOT Artifacts) No
Docker
Definition
Per Microservice
Docker Change Proposed
Docker
Verify Job
Pass?
Docker Change Merged
Docker
Merge Job
Docker Hub
(Docker SNAPSHOT Images)
Yes No
Test Suite
Per Functionality
Test Suite Change Proposed
CSIT
Verify Job
Pass?
Test Suite Change Merged
CSIT
Test Job
CSIT Test Job 2,
etc.
Yes No
Build and unit test

16. OPEN-O Jenkins Autorelease/RC Job Flow
Code
Cross-Project
Daily Cron Trigger
Autorelease
Build Job
(Builds All Projects Together From Source)
Nexus
(Java RC/Release Artifacts)
Docker
Definition
Per Microservice
Docker
Merge Job
Docker Hub
(Docker RC/Release Images)
CSIT
Test Job
CSIT Test Job 2,
etc.
Test Suite
Per Functionality
Build and unit test

17. OPEN-O Release Distribution (~60 docker images)
End User
Jira N
Source Code
Repository
from base:ubuntu
RUN apt-get install apache
RUN apt-get install php
RUN tar –xvf huawei.tar –C /opt/huawei
dockerfile
download 6 5 6
Nexus
Nexus or Public Cloud
Integration Lab
Image
Artifacts
Image
MSs
Image
VM Image
Tar ball
download
build 1
Those images will be used for CSIT with Robot framework 4
End to End
Testing
Image
push
Basic
Health &
Phase 3
Testing
Docker Engine
VM3
VM2
VM1
CentOS
Docker Engine
Microservice
Container 2
CentOS
push
Public
Image Registry
(Central)
Located at: 3
pull
Status Report
Image

18. Mercury VoLTE Deployment: : End to end MVs Real Devices
OPEN O
GSO
OPEN-O Mercury
SDNO
NFVO
S-VNFM/EMS
S-VNFM/EMS
S-VNFM2
S-VNFM
/EMS
SDN Controllers /
VIM / G-VNFM / S-VNFM
SPTN SDN
Controller
VIM1
VIM2
WAN SDN
Controller
VIM3 OS
vSBC OS
vPCSCF
DC SDN
Controller OS
vSPGW-U
DC SDN
Controller OS
vPCRF OS
vI/SCSCF OS
vTAS GW
SPTN OS
vPCRF OS
vHSS OS
vMME
DC SDN
Controller
Equipment / VFs OS
vSBC OS
vPCSCF
VXLAN GW
MPLS-TP / MPLS BGP L3VPN
WAN
TIC-Core OS
vSPGW-U
VXLAN GW
OSPF
TIC-Edge
EBGP-EVPN
Control Plane
VXLAN
OpenFlow
Overlay
OSPF
Legend:
SDN-O
Underlay
NFV-O

19. Agenda
OPEN-O Introduction
DevOps Practice: Toolchain
Compass

20. Compass
Provides deployment automation of cloud infrastructure and cloud applications, including NVFs in NFV architecture
Uses a unified data modeling and management of resources from bare metal servers to VMs or containers.
Open source project (in OpenStack, and OPNFV)

21. Support various Openstack version/flavor installation
Compass – Key Features
Deploy to baremetal
Support various OS installation
Support various Openstack version/flavor installation
Support various SDN installation
Remote deploy: remotely configure and deploy cluster to your DC

22. Compass From baremetal to Application
Deploy any software on any hardware with simple plugin!

23. Compass Extensible architecture Plugin mechanism
Easily integrated with third-party
How to use compass
Web UI
REST APIs
Python Client library

24. Compass as a Openstack VIM installer

25. Compass as a Infrastructure Automation Platform(TBD)

26. OPEN-O DevOps Practice
Benefits
Significantly shorter time to market
Better product quality
More reliable release
Key success factors
Modular architecture: micro-services
Good tool chains, ideally all automated.

27. 谢谢 Visit OPEN-O at booth for more details
OPEN-O Sun release demo: 谢谢