- 1 Overview
- 2 Scope
- 3 Release Deliverables
- 4 Sub-Components
- 5 Architecture
- 6 Testing and Integration Plans
- 7 Gaps
- 8 Known Defects and Issues
- 9 Risks
- 10 Resources
- 11 Release Milestone
- 12 Team Internal Milestone
- 13 Documentation, Training
- 14 Other Information
Overview
Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Honolulu |
| Project Lifecycle State | Mature |
| Participating Company | China Mobile, Huawei，China Telecom |
...
What is this release trying to address?
The Usecase-UI Guilin Honolulu release has following primary objectives:
...
E2E Network Slicing: KPI Monitoring
Transport Slicing for Guilin Release
POC: Support for Intent-based Networkand enhancement of endpoint design
Smart Operator Intent Translation: multiply methods of creating 5G service slicing based on IBN
2. UUI enhancement and new features:
JDK upgrade evaluate and migrate (Depend on the commit resource) and Upgrade PostgreSQL:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Upgrade Vulnerable Direct DependenciesRemoved GPLv3 from the dockers built by the ONAP community: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-494
Organize the existed API, clarify the data format and parameter of them and delete the useless ones: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-440506
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
...
- UUI BE Component for supporting KPI Monitoring and Transporting Slicing, 5G Slicing enhancement and IBN input
- UUI FE Component for supporting KPI Monitoring and Transporting Slicing
POC:
- UUI FE Component for providing the entry for IBN system
- UUI BE Component for receiving the IBN datasupporting KPI Monitoring, 5G Slicing enhancement and IBN input
- UUI NLP Component for supporting the smart operator intent translation based on IBN
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
| Jira Legacy | |||||||
|---|---|---|---|---|---|---|---|
|
...
POC:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
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
Please fill out the centralized wiki page: Guilin Honolulu Release Platform Maturity
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) | |||
| Portal Platform API | API for integration of portal applications | ||||||
Catalog API (SDC) | API to read the NS and VNF Catalog | ||||||
SO API(Modeling) | API for NS instantiation and termination | ||||||
MSB API | API for registration and use of micro-services bus | Microservice Bus API Documentation | |||||
A&AI API | API for getting inventory and image management | AAI REST API Documentation | |||||
| VF-C API | API for NS instantiation and termination | ||||||
| DataLake API | API for FCAPS (VNF/VM monitoring) | ||||||
| External API | API for external data | IBN API | API for IBNdata | to get NLP processing result
API Outgoing Dependencies
...
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
Usecase UI Honolulu- Functional Test Cases
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.
Gaps identified | Impact |
|---|---|
Known Defects and Issues
Provide a link toward the list of all known project bugs.N/A
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:usecase-ui
Release Milestone
The milestones are defined at the Release Level and Planning: Honolulu and all the supporting project agreed to comply with these dates.
...
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
Please refer to Honolulu Documentation
Other Information
Vendor Neutral
...
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.