The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core.
The intention is to allow decentralized applications to run within their own infrastructure while providing common management services and connectivity.
The Portal core provides capabilities including application onboarding & management, centralized access management, and hosted application widgets.
Using the provided SDK, application developers can leverage the built-in capabilities (Services / API / UI controls) along with bundled tools and technologies.
High-level Scope Overview:
The Portal provides a web-based user interface that provides access to all of the subsystems of an instance of ONAP.
It offers both design-time tools and run-time monitoring and control (for example: access to SDC, Policy, VID applications).
Any user seeking access to an ONAP application will first visit the Portal, where authentication will be performed. Based on the user’s configured access level, the Portal will let the user access different application widgets, and might also redirect the user to a specific run-time environment.
From the Portal, users access applications and Key Performance Indicators.
Administrators onboard and manage applications and hosted application widgets, and manage user access.
ONAP applications can be divided into three main categories. Applications that are required at the design time, such as SDC, Policy creation, etc. Applications that support runtime time functions such as AAI, SO, DCAE, SDNC, APPC and VF-C. Finally, the applications that support administrative functions on the ONAP platform. As the number of applications grows, there is a need to have control over:
To address this, a platform and an SDK are being built to aid teams, who are tasked with building these ONAP applications. The platform includes two major modules: the SDK and the Application Portal Core. The SDK will provide a base framework for development teams, and will help in developing and releasing applications into production in a rapid and consistent manner. The applications built on this SDK will be controlled by a centralized ONAP Portal Core. Here are the details of both.
The SDK module will be used as a base for any ONAP application being built. It bundles together a host of different tools, technologies, and standards that will assist the teams during the development phase. It includes reusable UI components, authentication & authorization components, visualization & reporting engine, collaborative services, workflow manager, GIS / Map, web component, and widget development framework.
Any application based on the SDK will have implicit connectivity with a centralized ONAP Portal Core via a message-oriented middleware. It will be used for sending and receiving any data from the ONAP Portal.
This will be a centralized web-based application running in the cloud environment and will be responsible for orchestrating all the other ONAP web applications. The ONAP Portal Core will include centralized access control, user management for internal/external users, dashboards, application administration, common UI controls, system monitoring/alarms/audit, system notifications, user messaging widget, context-aware UI controls, access history, personalization, service registration/discovery etc.
Any user seeking access to an ONAP application will first land on the ONAP Portal Core where authentication will be performed. Based on the user’s access level, the ONAP Portal Core will let the user access different application widgets, and may also redirect them to their own run-time environments.
Designing Services
The Portal provides the following design-time features:
The Portal offers a Virtual Instantiation Deployment (VID) GUI to trigger SO instantiation of Services and components that have been certified and distributed for production. These services may include:
VID reads the models created in SDC, and, in turn, forwards the appropriate information to SO during the Service instantiation process.
From the ONAP Portal, administrators:
· Portal SDK - Digital Experience Control/UI Upgrade.
· Ability for admin to use notification and act on it w/o copy/paste, e.g. hyperlink to target function with context transfer.
· Enabling centralized Authentication and Authorization (AAF): Ability for centralized User Management and administrative tasks such as Role based access.
Overall ONAP Architecture showing relation to Portal component with other components:
Detailed Portal Architecture:
Farhan Mir, fm7890@att.com, AT&T
Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.
Use the above information to create a key project facts section on your project page
Project Name: Portal
*Repo name*: portal, ecompsdkos
*Lifecycle State*: enhancement
*Primary Contact*: Manoop Talasila
*Project Lead*: Manoop Talasila
*mailing list tag{*} \[Should match Jira Project Prefix\]
*Committers*: talasila@research.att.com; statta@research.att.com
*Link to TSC approval:
*Link to approval of additional submitters:{*} |