...
Project Name | Enter the name of the project |
---|---|
Target Release Name | CasablancaDublin |
Project Lifecycle State | Incubation |
Participating Company | China Mobile, ZTE, Huawei, Raisecom |
...
Describe the problem being solved by this release.
The Usecase-UI Casablanca Dublin release is planning to support below features and functionality:
...
- Improve platform maturity:enhance scalability, manageability,security (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 Usecase-UI existing features:
Lifecycle Management improvement
FCAPS improvement
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
CCVPN Use Case : Residential Broadband vCPE (Approved)
Centralized Representation and Consistent Identification of Cloud Regions In ONAPDublin)
Minimum Viable Product
Describe the MVP for this releaseUsecase-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/upgradeupdate) for VoLTE service/vCPE/CCVPN use case
Monitor GUI for VNFs and VMs
...
Functionality Name | In or Out | Priority | Stretch |
LCM | In | H | Support VoLTE/vCPE/CCVPN Use Case Instantiation, Termination, Scaling, Healing, Update |
VNF Monitor | In | HM | Support VNF Alarm and Performance display |
VM Monitor | In | H | Support VM Alarm and Performance display |
Multi-Language | In | H | Support Multi-language display for Usecase-UI pages |
...
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
...
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
---|---|---|---|---|
Performance | 1 | 1 |
| |
Stability | 1 | 2 |
| |
Resiliency | 2 | 2 |
| |
Security | 1 | 1+ |
| |
Scalability | 01 | 1 |
| |
Manageability | 1 | 1+ |
| |
Usability | 1 | 1+ |
|
...
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 | |||
Micro-services bus 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) |
API Outgoing Dependencies
None
...
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...