...
- 1 Overview
- 2Scope
- 3Release Deliverables
- 4Sub-Components
- 5Architecture
- 6Testing and Integration Plans
- 7Gaps
- 8Known Defects and Issues
- 9Risks
- 10Resources
- 11Release Milestone
- 12Team Internal Milestone
- 13Documentation, Training
- 14Other Information
Overview
Project Name | Enter the name of the project |
---|---|
Target Release Name | Jakarta |
Project Lifecycle State | Mature |
Participating Company | China Mobile, Huawei, China Telecom |
Scope
What is this release trying to address?
...
2. UUI enhancement and new features:
...
- PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR KOHN. USECASEUI-679 - 2 components in one Docker 处理中
- Modify UUI certificates USECASEUI-594 - UUI certificates are not correct
- Modify returning coverageAreaTAList for AN slice profile USECASEUI-618 - Fix issue in returning coverageAreaTAList for AN slice profile
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
- Maintenance and Enhancement of Intent-driven Closed-loop Autonomous Networks in R11. REQ-1214
- General intent model and general intent interface requirements in R11. REQ-1267
- Network Services without Perception for Users based on IBN REQ-1075.
- Display CCVPN Network Topology and Tunnel Installation in R10 REQ-1103.
Minimum Viable Product
Usecase-UI will include the necessary subcomponents supporting the primary objectives: supporting the use cases and meeting platform maturity goals.
- Add PyTorch framework to support more models (TenserFlow framework has been added since Honolulu Release).
- Improve the accuracy rate of intent translation with multiple models.
- Enhance the function of STT (speech to text).
- Add intent analysis micro service in UUI.
- A common user interface for CCVPN, E2E Slicing and other usecases by intent-based service;
- A common data set for NLP training;
- Enhancing the NLP algorithm and model for more accurate intent translation;
- Monitoring page: Ability to display underlay L1 network topology and resource utilization status; Ability to display installation and configuration for each OTN tunnel.
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.
...
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Jira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = USECASEUI AND issuetype = Bug AND fixVersion = "Jakarta Kohn Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
---|---|
Source Code | Source code for all UUI components |
Maven Artifacts | Maven Artifacts for all UUI components |
Docker Containers | Docker container associated with UUI components |
Documentation | UUI detailed documentation |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Please fill out the centralized wiki page: Jakarta Kohn Release Platform Maturity
API Incoming Dependencies
...
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 |
API Outgoing Dependencies
...
Testing and Integration Plans
Usecase UI Jakarta Kohn - 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 |
---|---|
To fill out | To fill out |
Known Defects and Issues
Please refer to the "Bugs" section above
...
Please update any risk on the centralized wiki page - Jakarta Kohn Risks
Resources
Fill out the Resources Committed to the Release centralized page.
...
The milestones are defined at the Release Planning: JakartaKohn and all the supporting project agreed to comply with these dates.
...
It is not expected to have a detailed project plan.
Date | Project | Deliverable |
---|---|---|
To fill out | To fill out | To fill out |
Documentation, Training
Please update the following centralized wiki: Jakarta Kohn Documentation
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...