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

« Previous Version 6 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: E2E use case, NS use case, CCVPN use case and 5G slicing use case(added in Frankfurt Release).

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

  • Support 5G slicing functions
    • Providing CSMF Portal to support the customers to create 5G Slicing business
    • Providing NSMF Component to support the portal of checking and management the 5G Slicing which customers have created
  • Other functional enhancements
    • CCVPN Usecase Optimization

New or modified interfaces

  • N/A

If they are modified, are the backwards compatible?

Yes, almost APIs required parameters has been supported by previous version，the alignment will add more optional parameter support which can comply with previous APIs.

Interface naming

  • N/A

Reference to the interfaces

  • A&AI
  • SO
  • SDC
  • MSB

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 E2E/CCVPN/5G Slicing DM and align with the above data model in Frankfurt release



  • No labels