The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.
- 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 | Istanbul |
| Project Lifecycle State | Mature |
Participating Company | China Mobile, Huawei, China Telecom |
...
The Usecase-UI Istanbul release has following primary objectives:
- IBN module: Usecase UI will support kinds of service of intent management, such as creation, delete, deactivationvia adding a new
...
- “Intent-based Services” page
- IBN module: Usecase UI will support the monitoring of intent-instance via adding a new
...
- monitoring page
- E2E Slicing: Usecase UI will support the binding of intent-instance and slicing business ID
2. UUI enhancement and new features:
- Remove GPLv3 from the dockers built by the ONAP community
USECASEUI-494 - usecase UI dockers contain GPLv3 开放
- Upgrade postgresql
- PACKAGES UPGRADES IN DIRECT DEPENDENCIES
USECASEUI-574 - PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR ISTANBUL 开放
- Add test code for UUI
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
Smart Intent Guarantee based on IBN - R9 Intent Instance
Minimum Viable Product
Usecase-UI will include the necessary subcomponents supporting the primary objectives: supporting the use cases and meeting platform maturity goals.
- UUI BE Component for supporting Intent-instance Monitoring and Intent management enhancement, as well as supporting an api for binding the intend-instance and business id
- UUI FE Component for supporting Intent-instance Monitoring and Intent management enhancement
- 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.
...
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.
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 Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
...
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.
...
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
...
Known Defects and Issues
Please refer to Frankfurt Defect Status
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).
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
Please update the following centralized wiki: Frankfurt 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
- ...
...
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.