Open-O Integration

Project Proposal
Overview

• Project Name: Integration

• Repository Name: integration
• Description: Responsible for the integration
framework / automated tools, code and scripts,
best practice guidance related to cross-project
Continuous System Integration Testing (CSIT),
and delivery of the Open-O project.
• Participants: Huawei, ZTE, China Mobile, others?
Project Scope

• Provides all the cross-project infrastructure code,

scripts, system test cases, continuous system
integration tool chain, and POC necessary for the
successful delivery and industry adoption of the
Open-O project as a whole
Project Description
Category Description
1 Test • Code and tools for automatic system testing and
continuous integration test flows across Open-O
projects
• Common guidelines, templates, and best
practices to help project developers to write unit
and system test code
• Framework and tools for security testing
2 CI Builder • Scripts and definitions for build pipelines and CI
jobs in Jenkins, as well as for VM and docker
images required for CI tests
3 Autoreleas • Scripts to build the artifacts/binaries (e.g.
e zip/targz files) that are used in the release
candidates and final release from scratch
4 Distribution • Scripts to be used by the end user for setup and
execution of the Open-O project modules
• Default/sample configuration files, README files
5 Packaging • Scripts and package definitions for deb, RPM,
etc. installer packages for various Linux or other
OS distributions
• Sample VM or docker images
Problem Being Solved
• Automate the building artifacts/binaries to minimize human
errors and reduce engineering costs
• Ensure that changes in one project will not break the
functionality of other projects
• Assure that the entire Open-O project/product functions
correctly in the case of continual change in subprojects
• Ensure consistency in unit and system testing
methodology across all the Open-O projects
• Capture security issues
• Required to support the executing of CI jobs (e.g. for
Jenkins)
• Detect cyclical dependencies
• Generate release candidates and final release
• It generates dependency lists / graph automatically
• Ease of industry adoption of Open-O by providing scripts
and other information for setup/installation/configuration
• An industry standard installer could help anyone to try out
Open-O easier
• Industry adaption
Project Description (cont.)
Category Description
6 POC • Scripts and definitions for setting up a POC sample
deployment of use cases in lab settings
• Provisioning, installation, and setup of all the telco
equipment such as switches, routers, and gateways
to enable end to end testing
• Allow remote access to the lab environment for
interoperability testing
• Automatic updates of code in lab environment from
future releases
7 Performance • Test cases for performance, scalability,
resilience/stress testing, longevity
• Benchmarking and performance whitepapers
8 Infrastructure • Develop the specifications for the “Open-O
Specification compliant” deployment and test environment
9 Bootstrap • A framework to automatically install and test a set of
base infrastructure components for new developer
Problem Being Solved
• Support the needs of consistent, reproducible lab
setup for demo and POC purposes
• Promote easy interoperability testing with different
hardware devices, SDN controllers, etc.
• Automate the process of keeping the lab code up to
date with the latest changes
• Define standard performance metrics
• Provide and publish benchmarking results
• Assist the planning and procurement of the necessary
hardware and infrastructure for setting up Open-O
environments
• Reduce the barrier of entry to allow new Open-O
developers to ramp up onto active development
quickly
• Reduce the cost to the community in responding to
simple environment setup questions faced by new
developers
Architectural Alignment

Portal

Orchestrator Service

Integration
Orchestrator
Common Global Service-O
Test &
Lab
Common SDN-O NFV-O
Service

Driver
Release Plan
• Release 1
– Infrastructure for system tests and continuous integration tests
– Distribution (user-facing setup/config) scripts
– Basic Autorelease scripts
– Builder scripts
– POC supports two board approved use cases: residential and enterprise
• Future Releases
– System test best practices and guidelines
– Packaging scripts (deb, RPM, pre-built VMs/containers)
– Performance, scalability test cases, analytics
– Infrastructure Specifications
– Bootstrap
Tooling (in progress)

• System Test and • Distribution

Continuous Integration – Shell scripts
Infrastructure – README documentation
– Git/Gerrit • Autorelease
– Jenkins CI – Maven
– Robot Framework – Shell scripts
– JMeter
• Builder, POC
– Python Requests
– Shell scripts
Resources
Initial Committers
1. Helen Chen helen.chen@huawei.com
2. Chengli Wang wangchengli@chinamobile.com
3. Guangmin Liu liuguangmin@huawei.com
4. Guangzhi Li Guangzhi.Li1@huawei.com
5. Gary Wu gary.wu2@huawei.com
6. Murali P murali.p@huawei.com
7. Hailin Ye yehailin@huawei.com
8. Yingjie Ren jeffery.ren@huawei.com
9. Leibo Huang huang.leibo20@zte.com.cn
10. Zhaoxing Meng meng.zhaoxing1@zte.com.cn
11. Leibo Huang huang.leibo20@zte.com.cn
12. Jie Feng feng.jie2@zte.com.cn
13. Jinhua Fu fu.jinhua@zte.com.cn
14. Huabing Zhao.huabing@zte.com.cn
 Project Artifact Log CSIT Suite
Repository Repository Repository Repository
(git/gerrit) (nexus) (nexus) (git/gerrit)

Project Distribution Test

Build Build Build
(robot
(jenkins) (jenkins) framework)

Project Reporting
Dashboard Dashboard
(spectrometer) (sonar)
 Patch Patch Release
Review Merged Build

for all

Validate Validate Verify Merge

Autorelease Distribution Build Build

Test Test
feature-only feature-all

Test Test
feature-only feature-all
Integration Distribution
Build Build

Test Test
feature-only feature-all for all
ds

Test Test
feature-only feature-all