DRAFT PROPOSAL FOR COMMENTS
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. |
...
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Frankfurt |
| Project Lifecycle State | Incubation |
| Participating Company | China Mobile, Huawei |
Scope
What is this release trying to address?
Describe the problem being solved by this release.
The Usecase-UI Frankfurt release is planning to support below new features and functionality :
...
of 5G Slicing and CCVPN. The details are as follow:
- Create CSMF Portal: Provide the CSMF Portal for managing the 5G Slicing (i.e., S3P items)
- Support use cases identified by ONAP and integration: vCPE, CCVPN
- Support Functional Requirements identified: Centralized Representation and Consistent Identification of Cloud Regions In ONAP
- Collaborate with DataLake project
- Enhance business order, business slicing and slicing monitoring)
- Add NSMF functions to the original Portal: Add extra pages and components to support the management of task flows created in CSMF
- Enhance Usecase-UI existing features:
Lifecycle Management improvement
FCAPS improvementimprove the functions of Lifecycle Management module and Monitor module - Support CCVPN-E-LINE Service over OTN NNI
- Support Multi-domain multi-layer Optical Service Orchestration
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
The existing use cases and new use cases in the Frankfurt release.
Minimum Viable Product
Usecase-UI will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
LCM GUI (instantiation/termination/scaling/healing/update) for VoLTE/vCPE/CCVPN use case
Monitor GUI for VNFs and VMs
...
CSMF Portal
Components and pages related to NSMF
CCVPN Service related to support CCVPN-E-LINE Service over OTN NNI and Multi-domain multi-layer Optical Service Orchestration
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.
Functionality Name | In or Out | Priority | Stretch |
CSMF Portal | In | H |
Support VoLTE/vCPE/CCVPN Use Case Instantiation, Termination, Scaling, Healing, Update
Create CSMF Portal and support related features | |
NSMF Pages and Components | In |
M
Support VNF Alarm and Performance display
H | Create NSMF Pages and components to support related features |
CCVPN-E-LINE Service | In |
M | Support |
CCVPN-E-LINE Service over OTN NNI |
| Multi- |
| domain multi-layer Optical Service Orchestration | In |
| M | Support Multi- |
Integration with other projects:
...
Functionality Name
...
In or Out
...
Priority
...
Stretch
...
Multi-Language
...
Out
...
H
...
Integration with Portal Platform
...
| domain multi-layer Optical Service Orchestration |
Epics
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Stories
Longer term roadmap
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
CSMF Portal | Providing GUI |
VNF Monitor Portal
Providing GUI for VNFs alarm and performance
VM Monitor Portal
Providing GUI for VMs alarm and performance
of CSMF Portal | |
NSMF Pages and Components | Providing GUI of NSMF Pages and Components |
CCVPN Service | Providing GUI for CCVPN Service's new features |
Sub-Components
List all sub-components part of this release.
...
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 1 | 1 |
| |
| Stability | 1 | 2 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 1 | 1+ |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1+ |
| |
| Usability | 1 | 1+ |
|
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 | |||
DMaaP API | API for VNFs/VMs fcaps data subscription | |||
A&AI API | API for gettring inventory and image management | |||
| 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 |
|---|
Known Defects and Issues
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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.
...
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the 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
- ...
...