1 High Level Component Definition and Architectural Relationships
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.
2. API definitions
Usecase-UI provides NONE external interfaces.
Usecase-UI consumes the following interfaces:
Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| A&AI | ||
| SO | ||
| SDC | SDC Interface | An interface to receive resource Templates from SDC design catalog |
| MSB | Micro Service Bus Interface | An interface for registration and discovery with the ONAP Micro Service Bus. |
| VFC |
3. Component Description:
Usecase-UI is a web application which contains two parts:
- Usecase-UI GUI
- Usecase-UI Server
4. known system limitations
Now the component Redundancy and scaling depends on Kubernetes.
5. Used Models
......
6. System Deployment Architecture
......
7. New Release Capabilities
The Frankfurt Release supports two capabilities:
1. 5G Slicing Use Case
- Providing CSMF Portal for customers to support 5G Slicing business
- Providing NSMF Portal for ONAP operating staffs to support 5G Slicing management
2. CCVPN Use Case
- Get and Show MDONS (L1) Service Instances
- Instantiate MDONS (L1) Service Instances
- Terminate MDONS (L1) Service Instance
- 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）
- Service Topology: Adaption of new schema in AAI（ the AAI schema for SOTN service had 2 service linked using allotted-resource）
8. References
Usecase-UI Installation & User Guide: usecase-ui docs