| Table of Contents | ||
|---|---|---|
|
Overview
...
What is this release trying to address?
| Scope | Priority | Committer Lead | Resources Committed | Epic | Dependencies | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Do Not Break the Build | Highest | Yang Xu | Yang Xu Marco Platania |
| |||||||||||||||||||||||||||||||||
| oParent Update for Security Vulnerability | Highest |
| |||||||||||||||||||||||||||||||||||
| Use Case Testing | Highest | everyone in integration team, see use case owners below | |||||||||||||||||||||||||||||||||||
| ONAP CI Enhancement | Highest |
| |||||||||||||||||||||||||||||||||||
| Maintain ONAP Integration Testing Infrastructure | Highest |
| |||||||||||||||||||||||||||||||||||
| S3P Testing Enhancement | High |
| |||||||||||||||||||||||||||||||||||
| vCPE Use Case Test Automation | High |
| |||||||||||||||||||||||||||||||||||
| Use Case Development for vFW and Scaling | High |
| |||||||||||||||||||||||||||||||||||
| CIA Project | High |
|
Use Cases
Use Case Test Cases | Lab | Responsible | EPIC | |
|---|---|---|---|---|
| 1 | vFW / vDNS | Intel / Windriver | ||
| 2 | vCPE Integration Test Case | Intel / Windriver | ||
| 3 | vCPE with TOSCA VNF Test Case | CMCC | ||
| 4 | 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Status | TLab | ||
| 5 | 5G - PNF PnP - Integration Test Status | TLab | ||
| 6 | 5G - Bulk PM - Test Status | Intel / Windriver | ||
| 7 | 5G - OOF and PCI - Integration Test Cases | Intel / Windriver | ||
| 8 | Scale Out - Integration Test Cases and Status | Intel / Windriver | ||
| 9 | CCVPN Integration Test Cases | CMCC | ||
| 10 | vFW/vDNS HPA Regression and Enhancement Testing( |
HPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver | |||
| 11 | Change Management - Flexible Designer & Orchestrator | Intel / Windriver | ||
| 12 | Change Management - Traffic Management- | Intel / Windriver | ||
| 13 | Intel / Windriver | |||
| 14 | Change Management - Schedule optimization | Intel / Windriver | ||
| 15 | BBS (Broadband Service) | Swisscom, CMCC, Huawei, Nokia | ||
| 16 | 5G Slicing (scope is not clear, need to wait for TSC requirement) | AT&T, Nokia, Ericsson | ||
| 17 | vFW on ARM ( |
| no integration commitment, vendor will cover all tests) | ARM, ENEA | |||
| 18 | Model driven control loop design | AT&T, Nokia | Testing confirmed by AT&T | |
| 19 | K8S based cloud region support | Intel, VMWare | Testing confirmed by Intel | |
| 20 | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | VMWare, Intel | Testing confirmed by Intel | |
| 21 | Consistent ID of a Cloud Region | Windriver, AT&T, CMCC | Need to talk to Bin Yang about testing resource |
Minimum Viable Product
- CI/CD running on onapci.org
- Automatic unit testing, CSIT testing, and end-to-end testing
- Guidelines, frameworks, or best practice recommendations on S3P testing for ONAP project teams
...
- Cross-project Continuous System Integration Testing (CSIT)
- End-to-End (ETE) release use cases testing with VNFs with repeatability
- CI/CD to ONAP community integration labs
- Reference VNFs that can be used to show how the ONAP platform handles
- VNF installation and
- VNF life cycle management
- VNF Requirement compliance
Release Deliverables
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Manageability | Not Measured | 1, partial of 2 |
| |
| Performance | Not Measured | Not Measured |
| |
| Resiliency | 2 | 3 | Will cover geo-redundancy if lab env supports it. All Integration team will perform platform-level testing similar to: |
|
| Scalability | Not Measured | Note Measured |
| |
| Security | Not Measured | Not Measured |
| |
| Stability | 2 | 2 | Integration team will perform platform-level testing similar to: |
|
| Usability | Not Measured | Not Measured |
|
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
Name | Description | Version |
|---|---|---|
| Chaos Monkey | Resilience Testing tool | |
Docker | Container platform | |
| Jenkins | CI/CD tool | |
| JMeter | Performance Testing tool | |
| Openstack | Cloud OS | |
| Robot | Testing framework |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
The goal is to automate all the unit testing, CSIT testing, and end-to-end testing in release Casablanca. The detailed test roles and responsibilities are listed below.
Types of Testing | Dev. (Project Team) | CSIT (Project Team) | E2E (Integration Team) | S3P (Project + Integration) |
|---|---|---|---|---|
| Usability Testing | x | |||
| Unit Testing | x | |||
| Stability Testing | x | |||
| Security Testing | x | |||
| Scalability Testing | x | |||
| Regression Testing | x | x | x | x |
| Performance Testing | x | |||
| Integration/Pair-Wise Testing | x | |||
| Install/Uninstall Testing | x | |||
| Feature/Functional Testing | x | |||
| End-to-End Testing | x | |||
| ONAP Upgrade Testing | x | x |
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| Need additional lab resources (RAM, disk, network bandwidth, etc.) | None | None |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...