Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Project Overview

  • Usecase-UI is an application portal which provides the ability to manage ONAP service instances. 

  • Usecase-UI allows customers to create/delete/update service instances, as well as to monitor the alarm and performance of these instances.

  • Usecase-UI supports these use cases: CCVPN use case and 5G slicing use case(added in Frankfurt Release).

For more component description -  ARC Usecase-UI Component Description – Frankfurt

New component capabilities for Frankfurt, i.e. the functional enhancements

Functional enhancements

    1. 5G Slicing Use Case

(1) Providing CSMF Portal for customers to support 5G Slicing business

(2) Providing NSMF Portal for ONAP operating staffs to support 5G Slicing management

    2. CCVPN Use Case

(1) Get and Show MDONS (L1) Service Instances

(2) Instantiate MDONS (L1) Service Instances

(3) Terminate MDONS (L1) Service Instances

(4) Service Provisioning: Adaption of single service template. UUI BE to SO call will be single now,（there were 2 calls from UUI BE to SO）

(5) Service Topology: Adaption of new schema in AAI（ the AAI schema for SOTN service had 2 service linked using allotted-resource）

Platform enhancements

    1. Upgrade all java component to java1.8

    2. TSC must have items

  • Document current upgrade component strategy(TSC must have)  USECASEUI-353 - Document current upgrade component strategy(TSC must have) OPEN
  • 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  USECASEUI-354 - SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must havve) OPEN
  • SECCOM Password removal from OOM HELM charts(TSC must have)  USECASEUI-355 - SECCOM Password removal from OOM HELM charts(TSC must havve) OPEN
  • SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution  USECASEUI-356 - SECCOM HTTPS communication vs. HTTP(TSC must havve) OPEN

New or modified interfaces

  • N/A

If they are modified, are the backwards compatible?

  • N/A

Interface naming

  • N/A

Reference to the interfaces

  • N/A

What are the system limits?

  • Now the component Redundancy and scaling depends on Kubernetes

Involved use cases, architectural capabilities or functional requirements

Platform Maturity Targets

  • Document current upgrade component strategy(TSC must have)  USECASEUI-353 - Document current upgrade component strategy(TSC must have) OPEN

  • 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  USECASEUI-354 - SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must havve) OPEN
  • SECCOM Password removal from OOM HELM charts(TSC must have)  USECASEUI-355 - SECCOM Password removal from OOM HELM charts(TSC must havve) OPEN
  • SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution  USECASEUI-356 - SECCOM HTTPS communication vs. HTTP(TSC must havve) OPEN

Listing of new or impacted models used by the project (for information only)

  • Support for CCVPN/5G Slicing DM and align with the above data model in Frankfurt release
  • No labels