1 High Level Component Definition and Architectural Relationships
Drawio | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 the following interfaces:
Interface Definition | Interface Capabilities | |
---|---|---|
UU-APIE-1 | Operator Portal | User interface for operators:
|
UU-APIE-2 | Customer Portal | User interface for customer:
|
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
...
*Current description is based on El Alto documentation, will be updated accordingly if correspondent API update in Frankfurt.
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
Usecase-UI use the following models:
- TOSCA - VNF Descriptor/NS Descriptor ETSI NFV SOL001 v2.4.1 & v2.5.1
6. System Deployment Architecture
Usecase-UI consists of 4 containers:
Usecase-UI-Operator Portal
Usecase-UI-Operator Server
- Usecase-UI-Customer Portal
- Usecase-UI-Customer Backend
7. New Release Capabilities
The Frankfurt Release supports two capabilities:
...
- 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
...