Warning |
---|
The Portal project was moved to "unmaintained" status by the TSC on |
Welcome to the Portal Project space.
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.
Useful Links: | Maturity: | Docs: Architecture, APIs, Release Notes Developer Guides: https://safratech.net/onapdocs/ |
Release Planning
El Alto Release (2019)
Logistics
For details on people involved and the repositories go to Resources and Repositories for Portal Project.
If you are interested in working on the project, please list yourself as a contributor.
The mailing list uses the tag "[portal]" or #portal. For more details go to Email Tags
Weekly meeting schedule and details - [portal] Team ONAP11, Wed UTC 13:00 / China 21:00 / Eastern 09:00 / Pacific 06:00
Rocket Chat channel - http://onap-integration.eastus.cloudapp.azure.com:3000/channel/portal, http://onap-integration.eastus.cloudapp.azure.com:3000/channel/onap-integration
CII Badging overall - http://tlhansen.us/onap/cii.html
Status on JIRA items (counts of Open and InProgress):
Jira Charts | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Jira Charts | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Jira Charts | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Bugs Created vs Resolved:
Jira Charts | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Each project should have its own page with all of the associated project pages/attachments under it.
For consistency, use the same <project Name> as recorded in the list of Resources and Repositories
Approved Project Proposal
Release Planning
Amsterdam Release (Nov 2017)
- M1 Release Planning Checklist link
- M2 Functionality Freeze Checklist link
- M3 API Freeze Checklist link
- M4 Code Freeze Checklist link
- RC0 Checklist link due
- RC1 Checklist link due
- RC2 Checklist link due
- Sign-Off Checklist link
Beijing Release (May 2018)
C Release
...