You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

ONAP Portal

Project Name:

  • Proposed name for the project: ONAP Portal Platform
  • Proposed name for the repository: "portal", "ecompsdkos"

Project description:

  • 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.

Scope:

  • 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 OpenECOMP 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.


Planned enhancements in following releases:

·       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 to Operations Management Framework (OMF).

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possible - {+}https://wiki.onap.org/display/DW/Portal+
    • What other ONAP projects does this project depend on? No dependecies. But will impact components - Policy, VID, SDC, DBC (DMaaP Bus Ctrl)
  • How does this align with external standards/specifications?
    •  For security - O-Auth
  • Are there dependencies with other open source projects?
    •  Application Authorization Framework (AAF)

Resources:

  • Primary Contact Person: Manoop Talasila
  • Names, gerrit IDs, and company affiliations of the committers
    • Manoop Talasila, talasila, AT&T
  • Names and affiliations of any other contributors
    • Sunder Tattavarada, st782s, AT&T
    • Chris Lott, cl778h, AT&T
    • Wei-Ting(Robert) Lo, wl849v, AT&T
  • Project Roles (include RACI chart, if applicable)

Other Information:

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name: Portal

  • JIRA project name: Portal
  • JIRA project prefix: enhancements


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
*Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels