Page Comparison

...

What is this release trying to address?

The Usecase-UI Guilin Honolulu release has following primary objectives:

...

E2E Network Slicing: KPI Monitoring

Transport Slicing for Guilin Release

POC: Support for Intent-based Networkand enhancement of endpoint design

Smart Operator Intent Translation: multiply methods of creating 5G service slicing based on IBN

2. UUI enhancement and new  features:

JDK upgrade evaluate and migrate (Depend on the commit resource) and Upgrade PostgreSQL:

Removed GPLv3 from the  dockers built by the ONAP community: 

Organize the existed API, clarify the data format and parameter of them and delete the useless ones: 

Use Cases

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

...

1. UUI BE Component  for supporting KPI Monitoring and Transporting Slicing, 5G Slicing enhancement and IBN input
2. UUI FE Component  for supporting KPI Monitoring and Transporting Slicing

POC:

1. UUI FE Component for providing the entry for IBN system
2. UUI BE Component for receiving the IBN datasupporting KPI Monitoring, 5G Slicing enhancement and IBN input
3. UUI NLP Component for supporting the smart operator intent translation based on IBN

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.

...

Please fill out the centralized wiki page: Guilin Honolulu Release Platform Maturity

API Incoming Dependencies

...

API Outgoing Dependencies

...