The content of this template is expected to be fill out for M1 Release Planning Milestone.
Info
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.
- 1Overview
- 21 Overview
- 2 Scope
- 2.11 What is this release trying to address?
- 2.22 Use Cases
- 2.33 Requirements
- 2.44 Minimum Viable Product
- 2.55 Functionalities
- 2.66 Longer term roadmap
- 33 Release Deliverables
- 44 Sub-Components
- 55 Architecture
- 66 Testing and Integration Plans
- 77 Gaps
- 88 Known Defects and Issues
- 99 Risks
- 1010 Resources
- 1111 Release Milestone
- 1212 Team Internal Milestone
- 1313 Documentation, Training
- 1414 Other Information
- 14.11 Vendor Neutral
- 14.22 Free and Open Source Software
Overview
Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Guilin |
| Project Lifecycle State | MatureIncubation |
| Participating Company | China Mobile, Huawei，China Telecom |
...
E2E Network Slicing: KPI Monitoring
CCVPN-Transport Slicing for Guilin Release
...
JDK upgrade evaluate and migrate (Depend on the commit resource) and Upgrade PostgreSQL:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Upgrade Vulnerable Direct Dependencies: Jira Legacy server System Jira serverId
Use Cases
...
4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-440
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
E2E Network Slicing Use Case in R7 Guilin
POC: Intent-Based Network#ScopeforGrelease
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
REQ-141 - CCVPN-E-LINE Service over OTN NNI 完成
REQ-141 - CCVPN-E-LINE Service over OTN NNI 完成
REQ-141 - CCVPN-E-LINE Service over OTN NNI 完成
E2E Network Slicing: KPI Monitoring:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Transport Slicing for Guilin Release:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Support for Intent-based Network: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-329
Minimum Viable Product
Usecase-UI will include the necessary subcomponents supporting the primary objectives: supporting the use cases and meeting platform maturity goals and supporting the use cases.
- CSMF UUI BE Component for 5G slicing
- CSMF FE Component for 5G slicing
- UUI BE Component (including NSMF for 5G slicing)
- UUI FE Component (including NSMF for 5G slicing)Component for supporting KPI Monitoring and Transporting Slicing
- 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 data
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 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
...
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.
...
Please fill out the centralized wiki page: Frankfurt Guilin 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 gettring 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 IBN data to get NLP processing result |
API Outgoing Dependencies
...
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.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.