Portal
Project Name:
- Proposed name for the project: Portal
- Proposed name for the repository: portal
Project description:
- This sub-project is focused on enhancing the ONAP Portal.
Scope:
· Portal SDK
· Enabling centralized Authentication and Authorization.
· Enabling centralized User Management. Administrative tasks such as Role based access to Operations Management Framework (OMF)
- UI Application Onboarding / Management
· Execute workflow for network change
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? Policy, VID, SDC
- How does this align with external standards/specifications?
- Are there dependencies with other open source projects?
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
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable) –
- 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
- 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: 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: