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.

Designing Services

The Portal provides the following design-time features:

- Service Design and Creation (SDC): visual design tools for Services
- Policy creation (editing and conflict identification tools)
- Visual design tools for Analytic Applications (out-of-scope for first OpenECOMP release)

Instantiating Services

The Portal offers a Virtual Instantiation Deployment (VID) GUI to trigger MSO instantiation of Services and components that have been certified and distributed for production. These services may include:

Infrastructure Services (such as compute and storage resources)
Network Services (Virtual Network Functions)
Application Services (such as a load-balancing function)

VID reads the models created in SDC, and, in turn, forwards the appropriate information to MSO during the Service instantiation process.

Administration

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

Future enhancements in the 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.

Architecture Alignment:

Overall ONAP Architecture showing relation to Portal component with other components:

Developer Wiki > Portal Platform Project Proposal (5/12/17) > image2017-5-12_10-1-30.png

Detailed Portal Architecture:

Developer Wiki > Portal Platform Project Proposal (5/12/17) > image2017-5-11_16-34-48.png

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@att.com, AT&T
- Chris Lott, cl778h@att.com, AT&T
- Wei-Ting(Robert) Lo, wl849v@att.com, AT&T
- Anandarup Sarkar, as0481@att.com, AT&T
- Leimeng Shi, ls3297@att.com, AT&T
- Lorraine A Welch, lb2391@att.com, AT&T
- Abbas Fazal, af9900@att.com, AT&T
- Ikram Ikramullah, fi241c@att.com, AT&T
- Farhan Mir, fm7890@att.com, AT&T
Project Roles (include RACI chart, if applicable)

Other Information:

link to seed code (if applicable) –
- https://gerrit.onap.org/r/#/admin/projects/portal
- https://gerrit.onap.org/r/#/admin/projects/ecompsdkos
Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed? yes
  The current seed code has been already scanned and cleanup to remove all proprietary trademarks, logos, etc. except openecomp to be replaced by onap
  Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.
Meets Board policy (including IPR)

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