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?
...
The Usecase-
...
UI Frankfurt release has following primary objectives:
1. Supporting use cases identified by ONAP and integration:
Multi-domain Optical Network Services
E2E Network Slicing Use Case
2. UUI enhancement and new features:
...
JDK upgrade evaluate and migrate (Depend on the commit resource)
3. Document current upgrade component strategy(TSC must have) Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-353
4. SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - plan to solve the most of the security issues, but also depends on the commit resource Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-354
5. SECCOM Password removal from OOM HELM charts(TSC must have) Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-355
6. SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key USECASEUI-356
Use Cases
Requirements
Describe the use case this release is targeted for (better if reference to customer use case).
...
Use Case: Residential Broadband vCPE (Approved)
...
requirements).
Multi-domain Optical Network Services
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
E2E Network Slicing Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-146 Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-158
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 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)
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
...
LCM
...
In
...
H
...
Support VoLTE/vCPE/CCVPN Use Case Instantiation, Termination, Scaling, Healing, Update
...
VNF Monitor
...
In
...
M
...
Support VNF Alarm and Performance display
...
VM Monitor
...
In
...
H
...
Support VM Alarm and Performance display
...
Integration with other projects:
...
Functionality Name
...
In or Out
...
Priority
...
Stretch
...
Multi-Language
...
Out
...
H
...
Integration with Portal Platform
Epics
...
Epics
| 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.
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note..., etc) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
Service LCM Portal | Providing GUI of service life cycle management |
VNF Monitor Portal | Providing GUI for VNFs alarm and performance |
VM Monitor Portal | Providing GUI for VMs alarm and performance | Multi-Language | Providing Multi-Language GUI for portal users
| 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.
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
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.
...
- 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
...
- 0 – none
- 1 – 72 hours component level soak w/random transactions
- 2 – 72 hours platform level soak w/random transactions
- 3 – 6 months track record of reduced defect rate
...
- 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
...
- 0 – none
- 1 – CII Passing badge + 50% Test Coverage
- 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
- 3 – CII Gold
...
- 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
...
- 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
...
- 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
...
Please fill out the centralized wiki page: Frankfurt 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 |
DMaaP API
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
None
...
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.
Release Milestone
...
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
- ...
...