Information for PTL

This template is to be filled out for any project wishing to move to the "Mature" phase of the ONAP project lifecycle.  
Once completed, remove this info box and the send the link for this page to onap-tsc@lists.onap.org to initiate the maturity review.  

Per the ONAP Technical Community Document, the metrics for maturity review are:

Successful participation in releases: The project demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.

Architecture has been reviewed by the Architecture Committee

Project is active and contributes to ONAP: The project demonstrates a stable or increasing number of contributions across recent releases. Contributions are commits which got merged to a repository of an ONAP project or a related upstream project. Commits can for example be patches to update the requirements document of a project, code addition to an ONAP or upstream project repository, new test cases and so forth.

Mature artifacts produced: The project demonstrates that the artifacts produced by the project are deployable (where applicable) and have been successfully deployed, configured and used by end users (typically, service providers).

Review Submission Date: 7/7/2020

Project Description: 

The ONAP Portal is a platform that provides the ability to integrate different ONAP applications into a centralized Portal Core. It 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.

Project Landing Page:  Portal Platform Project

Project Meeting Minutes: https://wiki.onap.org/pages/viewpage.action?pageId=45305320


Leadership Resources :

Role

Name
(must use @ macro )

Linux Foundation Login (LFID)

Email Address 
(if different from @ macro)

PTLSunder Tattavaradatattasunder
Committerstalasila












Project & Release History

Architecture Alignment:

Artifact Information:

Other Information:


Portal is a GUI platform that provides the ability to integrate different ONAP platform GUIs into a centralized portal.

It provides:

  • 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 is used by:

  • VID, Policy, AAI, SDC, MSB and CLI
  • VID, Policy, AAI UI, SDC applications require Portal to be up to be accessible to the end user as these applications contact Portal to retrieve roles of the user who is logging in.
  • VID, Policy, Portal are built completely on Portal SDK platform which promotes Rapid Application Development and encapsulates Rich UI templates, Security, Logging, communication with AAF/Portal, Transaction Management, Access Management, Reporting etc

In addition to regular user, there are admin roles available for Portal to perform some administrative activities of Portal itself and the administration of on-boarded apps.

From the ONAP Portal, administrators:

  • access the same functionality accessible to users
  • manage users and application admins
  • onboard applications and widgets (developed using the Portal as a platform)
  • edit the functional menu
  • No labels

4 Comments

  1. Can you provide some information about documentation and especially how to use the UI ?

  2. Sunder Tattavarada - can you please provide the date of the last architecture subcommittee review?  Also, any information you can provide about deployment/usage of portal by operators or others?  Thanks!

  3. Jason Hunt  , Please find the architecture review here: ARC Portal Component Description - Frankfurt . It was done in collaboration with Stephen Terrill  and Chaker Al-Hakim  in August 2019.


    I have added more details on how Portal is used by other in the "Other Information" section

    Important points are:

    • VID, Policy, AAI UI, SDC applications require Portal to be up to be accessible to the end user as these applications contact Portal to retrieve roles of the user who is logging in. 
    • VID, Policy are built completely on Portal SDK platform which promotes Rapid Application Development and encapsulates Rich UI templates, Security, Logging, communication with AAF/Portal, Transaction Management, Access Management, Reporting etc