System Integration and Testing

Project Name:

Proposed name for the project: System Integration and Testing
Proposed name for the repository: integration

Project description:

System Integration and Testing is responsible for ONAP cross-projects system integration and all related end-to-end release use cases testing with VNFs necessary for the successful delivery and industry adaption of the ONAP project as a whole.

Scope:

It provides all the cross-project infrastructure framework and DevOps toolchain (Continuous Integration, etc.), code and scripts, best practice guidance and benchmark, testing reports and white paper related to:

–Cross projects Continuous System Integration Testing (CSIT)

–End-to-end release use cases testing with VNFs with repeatability

–Service design for end-to-end release use cases

–Release delivering of the ONAP project

–Open Lab: building and maintenance community integration labs

–Continuous Distribution (CD) to ONAP community integration labs

	Category	Description	Problem Being Solved
1	Test	•Code and tools for automatic system testing and continuous integration test flows across ONAP projects •Common guidelines, templates, generic tools, infrastructure, and best practices to help project developers to write unit and system test code •Framework and tools for security testing	•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 ONAP project/product functions correctly in the case of continual change in subprojects •Ensure consistency in unit and system testing methodology across all the ONAP projects •Capture security issues
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	•Required to support the executing of CI jobs (e.g. for Jenkins)
3	Autorelease	•Scripts to build the artifacts/binaries (e.g. zip/targz files) that are used in the release candidates and final release from scratch	•Detect cyclical dependencies •Generate release candidates and final release •It generates dependency lists / graph automatically
4	Distribution (descoping since comm serv1 has something like this, should keep these project be separated or merge?)	•Scripts to be used by the end user for setup and execution of the ONAP project modules •Default/sample configuration files, README files	•Ease of industry adoption of ONAP by providing scripts and other information for setup/installation/configuration
5	Packaging (checking with Common serv 1)	•Scripts and package definitions for deb, RPM, etc. installer packages for various Linux or other OS distributions •Sample VM or docker images	•An industry standard installer could help anyone to try out ONAP easier •Industry adaption

6	S3P	•Test cases for performance, scalability, resilience/stress testing, longevity •Benchmarking and performance whitepapers	•Define standard S3P testing metrics •Provide and publish benchmarking results
6	Infrastructure Specification	•Develop the specifications for the “ONAP compliant” deployment and test environment	•Assist the planning and procurement of the necessary hardware and infrastructure for setting up ONAP environments
8	Bootstrap	•A framework to automatically install and test a set of base infrastructure components for new developer	•Reduce the barrier of entry to allow new ONAP 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

Architecture Alignment:

How does this project fit into the rest of the ONAP Architecture?
What other ONAP projects does this project depend on?
- All ONAP projects
How does this align with external standards/specifications?
Are there dependencies with other open source projects?
- Robot
- Jenkins
- OpenStack
- Docker

Resources:

Primary Contact Person
- Helen Chen, helen.chen@huawei.com
Names, gerrit IDs, and company affiliations of the committers
- Helen Chen, helen.chen@huawei.com, Huawei
- Chengli Wang wangchengli@chinamobile.com, China Mobile
- Daniel Rose dr695h@att.com, AT&T
- Steven Smokowski ss835w@att.com, AT&T
- Christophe Closset cc697w@intl.att.com, AT&T
- Sebastien Determe sd378r@intl.att.com, AT&T
- Anael Closson ac2550@intl.att.com, AT&T
- Xiaolong Kong xiaolong.kong@orange.com, Orange
- Yi Yang yangyi.bri@chinatelecom.cn, China Telecom
- Luman Wang wanglm.bri@chinatelecom.cn, China Telecom
- Guangmin Liu liuguangmin@huawei.com, Huawei
- Gary Wu gary.i.wu@huawei.com, Huawei
- Kang Xi kang.xi@huawei.com, Huawei
- Yang Xu yang.xu3@huawei.com, Huawei
- An Ho an.ho@huawei.com, Huawei
- Dmitriy Andrushko dandrushko@mirantis.com, Mirantis
- Murali p murali.p@huawei.com, Huawei
- François Despres francois.despres@orange.com, Orange
- Elhay Efrat elhay.efrat@amdocs.com, Amdocs