...
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Portal is a GUI platform that provides the ability to integrate different ONAP platform GUIs into a centralized portal.
...
- The capability to allow other ONAP components to run within their own infrastructure while providing common management services and capabilities in a centralized way
- Provides common capabilities such as application on-boarding and management, centralized access management and hosting application widgets, Context-Aware UIControls, Visualization & Reporting Engine
- Provides SDK capabilities to access portal capabilities
...
Portal does not in itself provide APIs to other ONAP components, the Portal users do. [Please replace this statement, as Portal do provide APIs like - https://docs.onap.org/en/beijing/submodules/portal.git/docs/platform/offeredapis.html]
Portal provides the following interfaces:
CLAMP provides the following interfaces:
Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
Interface Name | Interface Definition | Interface Capabilities |
| CLAMPE-1 | Control Loop Lifecycle Management Interface. | A user interface for:
|
| CLAMPE-2 | Control loop dashboard. User interface to show the status of the control loop | Display and update: xxxxx |
Portal Clamp however provides multi-language support. [I am not sure about CLAMP, CLAMP PTL have to confirm if this is true]
The multi-language support provides:
...
A more detailed figure and description of the component.
The main functional comonents of porta alre:
- Portal Core Integration: APIs in the SDK provide simplified integration between the ONAP Portal Core and ONAP applications. By default, any application built on the SDK will have implicit integration with the Portal Core.
- Centralized Access Control: The Portal core acts as a gatekeeper for all ONAP applications. Site administrators decide who gets access to which applications with a distributed access management scheme.
- Common UI Controls: These are used to ensure a common look and feel and a consistent user experience.
- Context-Aware UI Controls: Since the ONAP Portal Core serves both as the point of entry and as the provider of context-aware menus and UI controls, it can ensure that when a user jumps from one application to another, the application menu items remain consistent and comply with the user’s access level. (This property of access control is called "Single Sign-On (SSO)".)
- Visualization & Reporting Engine: This component is used to develop analytical reports and visualizations on AVP / RCloud / RSpeed / RAPTOR.
- Collaborative Services: Collaboration services include video, text chatting, and screen sharing.
- Web Component & Widget Development Framework: This framework is used to build widgets and visual components that will be hosted on the ONAP Portal Core. It has access to services exposed by ONAP applications running in separate environments.
- Management for Internal/External Users: The administrators will import, or integrate with, internal and external users.
- Dashboards: The Portal provides customizable dashboards tailored for each user, based on their access level. Dashboards are comprised of widgets that provide summary content hosted by applications.
- Application Administration: Portal Core administrators can on-board and manage applications.
- Services Registration/Discovery: Applications can publish or discover services & APIs.
4. known system limitations
...
None. Dependent on the user.
7 References
- Portal Architectural Description: https://onap.readthedocs.io/en/latest/submodules/portal.git/docs/platform/architecture.html
- Portal APIs Specification: https://docs.onap.org/en/beijing/submodules/portal.git/docs/platform/offeredapis.html