Integration Dublin M1 Release Planning
- 1 Overview
- 2 Scope
- 2.1 What is this release trying to address?
- 2.2 Use Cases
- 2.2.1 vCPE Integration Test Case
- 2.2.2 vCPE with TOSCA VNF Test Case
- 2.2.3 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Status
- 2.2.4 5G - PNF PnP - Integration Test Status
- 2.2.5 5G - Bulk PM - Test Status
- 2.2.6 5G - OOF and PCI - Integration Test Cases
- 2.2.7 Scale Out - Integration Test Cases and Status
- 2.2.8 vFW/vDNS HPA Regression and Enhancement Testing
- 2.2.9 (HPA & Cloud Agnostic Intent - R3 Test Plan)
- 2.3 Minimum Viable Product
- 2.4 Functionalities
- 2.5 Longer term roadmap
- 3 Release Deliverables
- 4 Sub-Components
- 5 Architecture
- 6 Other Information
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Dublin |
Project Lifecycle State | Core |
Participating Company | AT&T, CMCC, China Telecom, ENEA, Ericsson, Huawei, Intel, Nokia, Orange |
Scope
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 | @Gary Wu | @Gary Wu |
| |
Use Case Testing | Highest | @Yang Xu | everyone in integration team, see use case owners below |
|
|
ONAP CI Enhancement | Highest | @Gary Wu | @Gary Wu @Yang Xu |
| |
Maintain ONAP Integration Testing Infrastructure | Highest | @Gary Wu | @Gary Wu @Yang Xu @Marco Platania |
| |
S3P Testing Enhancement | High | @Gary Wu | @Gary Wu @Yang Xu |
| |
vCPE Use Case Test Automation | High | @Yang Xu | @FREEMAN, BRIAN D @Yang Xu |
| |
Use Case Development for vFW and Scaling | High | @Marco Platania | @Marco Platania |
| |
CIA Project | High | @Adolfo Perez-Duran | @Adolfo Perez-Duran @Paul-Ionut Vaduva | https://lf-onap.atlassian.net/browse/INT-542 https://lf-onap.atlassian.net/browse/INT-543 |
|
Use Cases
| Use Case Test Cases | Lab | Responsible | EPIC |
|---|---|---|---|---|
1 | Intel / Windriver | @Brian Freeman / @Marco Platania |
| |
2 | vCPE Integration Test Case | Intel / Windriver | @Yang Xu / @Brian Freeman |
|
3 | vCPE with TOSCA VNF Test Case | CMCC | @Yan Yang
|
|
4 | 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Status | TLab | @Marcin Przybysz @marekPL |
|
5 | 5G - PNF PnP - Integration Test Status | TLab | @Marcin Przybysz @Krzysztof Kuzmicki |
|
6 | 5G - Bulk PM - Test Status | Intel / Windriver | @Former user (Deleted) @liam burke
|
|
7 | 5G - OOF and PCI - Integration Test Cases | Intel / Windriver | @N.K. Shankaranarayanan |
|
8 | Scale Out - Integration Test Cases and Status | Intel / Windriver | @Scott Blandford@Marco Platania |
|
9 | CMCC | @Yan Yang
|
| |
10 | vFW/vDNS HPA Regression and Enhancement Testing(HPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver | @Itohan Ukponmwan (Deactivated) @Eric Multanen (Deactivated) |
|
11 | Change Management - Flexible Designer & Orchestrator | Intel / Windriver | @Ajay Mahimkar @Elena Kuleshov @pagarwal Chris Rapposelli |
|
12 | Change Management - Traffic Management- | Intel / Windriver | @Lukasz Rajewski @Ajay Mahimkar |
|
13 | Intel / Windriver | @wangyaoguang @Ruchira Agarwal
|
| |
14 | Change Management - Schedule optimization | Intel / Windriver | @Ajay Mahimkar @Jerry Flood |
|
15 | BBS (Broadband Service) | Swisscom, CMCC, Huawei, Nokia | @David Perez Caparros @dbalsige |
|
16 | 5G Slicing (scope is not clear, need to wait for TSC requirement) | AT&T, Nokia, Ericsson | @Shekar Sundaramurthy |
|
17 | vFW on ARM (no integration commitment, vendor will cover all tests) | ARM, ENEA | @Paul-Ionut Vaduva |
|
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
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
Stories
Longer term roadmap
It provides all the cross-project infrastructure framework and DevOps toolchain (Continuous Integration, etc.), code and scripts, best practice guidance, benchmark and testing reports and white papers related to:
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
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
|---|---|
oParent | POM file with recommended Java library versions |
Robot | Executable for integration use case testing |
Demo | Executable for use case VNFs |
Integration | Scripts to deploy ONAP and test use cases |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
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.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
SDC BE API | SDC Backend API | M3 | M3 |
|
SO API | SO REST API | M3 | M3 |
|