Project Name:
- Proposed name for the project:
Integration
- Proposed name for the repository:
integration
Project description:
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:
Category | Description | Problem Being Solved | |
1 | Test |
|
•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 Management (ci-management repo) |
| •Required to support the executing of CI jobs (e.g. for Jenkins) |
3 | Autorelease |
|
|
4 | Distribution (This will use OAM ONAP Project) (descoping since comm serv1 has something like this, should keep these project be separated or merge?) |
| N/A |
Packaging (This will use OAM ONAP Project) (checking with Common serv 1) |
| N/A | |
6 | •Test cases for performance, scalability, resilience/stress testing, longevity •Benchmarking and performance whitepapers | •Define standard S3P testing metrics •Provide and publish benchmarking results | |
7 | 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 |
9 | End-to-end release use cases testing with VNFs with repeatability | •Create automatic test cases and script for VF testing •Perform VF compliant testing and verification using tools provided by ONAP •Delivery the testing reports and whitepaper | •Assist define the testing metrics •Reduce adoption risks for end-users |
10 | •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 | •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 | |
11 | Reference VNFs Project (now part of the Integration Project) | Two basic VNFs, namely a virtual firewall and a virtual load balancer (with virtual DNSs), have been provided. The objectives of the project are to improve, extend and maintain the vFirewall and vLoadBalancer VNFs:
|
|
12 | O-Parent | • ONAP Parent provides common default settings for all the projects participating in simultaneous release. | •Isolate all the common external dependencies, default version, dependency management, plugin management, etc. –Avoid duplicate/conflicting settings for each project •Each project sets its parent to inherit the defaults from ONAP Parent •Project level external dependencies and versions can be overridden if necessary |
Testing Principles (in progress)
- We expect test automation for all testing in scope for release 1.0.
- Regression, Unit and Feature/Function testing should be triggered by built process
- All testing must be able to execute on the selected ONAP environments
- Unit Testing for any project should have at least 30% code coverage
- Any new feature should be delivered with its associated unit tests/feature tests
Testing Roles and Responsibilities (in progress)
Types of Testing | Dev. Team | CSIT Team | E2E Team | S3P Team |
---|---|---|---|---|
Unit Testing | x | |||
Feature/Functional Testing | x | |||
Integration/Pair-Wise Testing | x | |||
End-to-End Testing | x | |||
Regression Testing | x | x | x | x |
Performance Testing | x | |||
Acceptance Testing | x | x | ||
Usability Testing | x | |||
Install/Uninstall Testing | x | |||
Recovering Testing | x | x | ||
Security Testing | x | |||
Stability Testing | x | |||
Scalability Testing | x | |||
Application Testing | x |
Testing Terminology
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
Name | Gerrit ID | Company Affiliation | Area of Interest | |
---|---|---|---|---|
Helen Chen | helenc878 | Huawei | Test, S3P, Open Lab, Reference VNFs | |
Chengli Wang | China Mobile | |||
Daniel Rose | AT&T | |||
Steven Smokowski | AT&T | |||
Marco Platania | AT&T | |||
Christophe Closset | AT&T | |||
Anael Closson | AT&T | |||
Hector Anapan-Lavalle | AT&T | |||
Xiaolong Kong | Orange | |||
François Despres | Orange | |||
Yi Yang | China Telecom | |||
Luman Wang | China Telecom | |||
Guangmin Liu | Huawei | |||
Gary Wu | Huawei | |||
Kang Xi | Huawei | |||
Yang Xu | Huawei | |||
Jianwen Ai | Huawei | |||
Murali p | Huawei | |||
Dmitriy Andrushko | Mirantis | |||
Elhay Efrat | Amdocs | |||
Marc Volovic | Amdocs | |||
Abhinav Singh | TechMahindra | |||
Sandeep Singh | TechMahindra | |||
Jinhua Fu | ZTE | |||
Yunlong Ying | ZTE | |||
Yuanxing Feng | ZTE |
- Names and affiliations of any other contributors
Name | Company Affiliation | Area of Interest | |
---|---|---|---|
Oliver Spatscheck | AT&T | ||
Catherine Lefevre | cl664y@intl.att.com | AT&T |
- Project Roles (include RACI chart, if applicable)
- Other Information:
- link to seed code (if applicable)
ECOMP existing repos:
- testsuite
- testsuite/heatbridge
- testsuite/properties
- testsuite/python-testing-utils
- demo
- ci-management
OPEN-O existing repos:
- integration
- ci-management
- oparent
- Vendor Neutral
This project is vendor neutral
- Meets Board policy (including IPR)
yes
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name: Integration
JIRA project name: integration
JIRA project prefix: integration
Repo name:
- integration
- demo
- testsuite
- testsuite/heatbridge
- testsuite/properties
- testsuite/python-testing-utils
- ci-management
- oparent
Lifecycle State: incubation
Primary Contact: Helen Chen
Project Lead:
mailing list tag [integration]
Committers:
*Link to TSC approval:
Link to approval of additional submitters: