The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
- 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?
...
The Usecase-UI Jakarta release has following primary objectives:
- IBN module:
- IBN module:
- E2E Slicing: A common user interface for CCVPN, E2E Slicing and other usecases by intent-based service.
- IBN module: A common data set for NLP training.
- IBN module: Enhancing the NLP algorithm and model for more accurate intent translation. .
- “Network/ccvpn-network” module: Ability to display underlay L1 network topology and resource utilization status.
- “Network/ccvpn-network” module: Ability to display installation and configuration for each OTN tunnel.
2. UUI enhancement and new features:
- Upgrade postgresql
USECASEUI-405 - 2 components in one Docker 处理中
- Modify UUI certificates
- Modify returning coverageAreaTAList for AN slice profile
...
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.
...
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
...
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 Frankfurt Defect Status
...
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 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
- ...
...