| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
This template is to be filled out for any project wishing to move to the "Mature" phase of the ONAP project lifecycle. 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 | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
| PTL | Sunder Tattavarada | tattasunder | |
| Committers | talasila | ||
Project & Release History
- How long the project has been an active: "At launch" : 9th November 2017
- Release Participation: Amsterdam through Frankfurt
- Engagement levels for past releases (up to 3):
- Commits per Release:
- Contributors per Release:
- Companies per release:
Statistics taken from Bitergia : https://onap.biterg.io/app/kibana#/dashboard/Overview
Release name and timeframe
commits
contributors
companies
Amsterdam ( 1/1/2017 to 11/16/2017 ) 183 14 5 Beijing ( 11/17/2017 to 6/7/2018 ) 146 22 8 Cassablanca ( 6/8/2018 to 11/30/2018 ) 149 31 9 Dublin ( 12/1/2018 to 7/9/2019 ) 219 27 8 El Alto ( 7/10/2019 to 10/24/2019 ) 285 14 4 Frankfurt ( 10/25/2019 to 6/18/2020 ) 433 28 6 - Use Cases:
- User/Access Management for GUI Applications (running with and without AAF)
- Drive Consistent User experience
- Single Point of Entry to GUI applications
Architecture Alignment:
Artifact Information:
- Code, Test Cases, documentation:
- https://gerrit.onap.org/r/admin/repos/portal
- https://gerrit.onap.org/r/admin/repos/portal/sdk
- https://gerrit.onap.org/r/gitweb?p=integration/csit.git;a=tree;f=tests/portal/testsuites;hb=HEAD
- https://gerrit.onap.org/r/gitweb?p=integration/csit.git;a=tree;f=tests/portal-sdk/testsuites;hb=HEAD
- https://docs.onap.org/projects/onap-portal/en/latest/index.html#master-index
- Successful Deployments and Integration Testing
- Portal is a critical GUI component and is required to be always up and running for Applications like SDC, VID, Policy Manager GUI, A&AI UI to be accessible
- It encapsulates AAF's RBAC functionality
- VID and Policy Manager GUI applications are built on the top of Portal SDK platform
- Portal Pair Wise Testing for Frankfurt Release (Integration Testing)
- Portal Pair Wise Testing for El Alto Release (Integration Testing)
- Portal is being used across the community for Access Management to ONAP GUI applications