Versions Compared

Key

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

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. In Honolulu Release, Usecase UI will continuously support the presentation of KPI monitoring data, as well as the configuration of KPI monitoring parameters.

  • Usecase-UI supports these use cases: CCVPN use case,  5G slicing use case and IBN use case. In Honolulu Release:

    • Usecase UI will support the endpoint related enhancements, as well as support the presentation of the detailed transportation process of AN/TN/CN region

    • Usecase UI will support the IBN module for translating users' requirements while creating 5G slicing via a new NLP micro-service

For more component description -  ARC Usecase-UI Component Description – Honolulu-R8

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

Functional enhancements

  1. Transport  5G Slicing: Supporting the endpoint related enhancements, as well as support the presentation of the detailed transportation process of AN/TN/CN region
  2. E2E Network Slicing: Supporting KPI  Monitoring data shown to users continuously and also supporting standard API interface for KPI monitoring, and KPI data reporting to tenant/operator
  3. IBN module: Supporting an entry for IBN module to creating 5G Slicing service via a new NLP micro-service, as well as receiving the response data from this new NLP module for creating CSMF Service

Platform enhancements

    1. Improve platform maturity (TSC must have items)

  • Remove GPLv3 from the dockers built by the ONAP community  
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyUSECASEUI-494

    2. Upgrade postgresql  

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-405

    3. Organize the existed API  

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyUSECASEUI-506

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

  • Remove GPLv3 from the dockers built by the ONAP community: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyUSECASEUI-494
  • Organize the existed API, clarify the data format and parameter of them and delete the useless ones: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyUSECASEUI-506
  • JDK upgrade evaluate and migrate (Depend on the commit resource) and Upgrade PostgreSQL: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyUSECASEUI-405

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

  • Support for CCVPN/5G Slicing/IBN DM and align with the above data model in Honolulu release