| Table of Contents | ||
|---|---|---|
|
Overview
...
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 |
...
- 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.
...
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 |
|
...
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.
...
| 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
...