Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

...

Project NameEnter the name of the project
Target Release NameFrankfurt
Project Lifecycle StateIncubation
Participating Company China Mobile, Huawei

Scope

What is this release trying to address?

The Usecase-

...

  1. Create CSMF Portal: Provide the CSMF Portal for managing the 5G Slicing (i.e., business order, business slicing  and slicing monitoring)
  2. Add NSMF functions to the original Portal: Add extra pages and components to support the management of task flows created in CSMF
  3. Enhance  Usecase-UI existing features: improve the functions of Lifecycle Management module and Monitor module
  4. Support CCVPN-E-LINE Service over OTN NNI
  5. Support Multi-domain multi-layer Optical Service Orchestration

Use Cases

  • Vertical Industry Oriented On-demand 5G Service
  • Multi-domain Optical Network Services

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
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-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
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-354

5. SECCOM Password removal from OOM HELM charts(TSC must have) 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-355

6. SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-356

Use Cases

Requirements

Describe the use case this release is targeted for (better if reference to customer requirements).

Multi-domain Optical Network Services

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-141
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-37

E2E Network Slicing 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-146
  
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-158

Minimum Viable Product

Usecase-UI will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

  1. CSMF BE Component for 5G slicing
  2. CSMF Portal FE Component for 5G slicing
  3. UUI BE Component (including NSMF for 5G slicing)
  4. UUI FE Component (including NSMF for 5G slicing)

...

Functionality Name

...

In or Out

...

Priority

...

Stretch

...

CSMF

...

In

...

H

...

Support 5G slicing service management for customers

...

NSMF

...

In

...

H

...

Support 5G slicing service management for ONAP users

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note..., etc) of this release.

Deliverable NameDeliverable Description

CSMF BE Component

Providing CSMF BE Component

CSMF FE ComponentProviding CSMF FE Component

UUI BE Component

Providing UUI BE Component

UUI FE Component

Providing UUI FE Component
Source CodeSource code for all UUI components
Maven ArtifactsMaven Artifacts for all UUI components
Docker ContainersDocker container  associated with UUI components
DocumentationUUI 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 APIAPI 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 APIAPI for NS instantiation and termination


DataLake APIAPI for FCAPS (VNF/VM monitoring)


External APIAPI for external data


...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out


Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...