| Info |
|---|
Approved by the TSC on TSC 2022-12-08 |
...
- Build on top of an existing and tested base implementation that was developed during the last 18 month by a scrum team at DTAG
- As a web based GUI it will serve as a discovery point for the existing ONAP system web GUIs
- Support for internationalization
- Support for theme implementation
Scope:
In Scope: Please provide an overview of the intended scope of the project over several years, not just what you hope to accomplish for the project's first release.
- Starting point for user management and authorization
- App starter for discovery and access of ONAP applications
- Dashboard for status of ONAP services in cloud
- History of portal actions
- Model discovery
- Model instantiation
- Instance managment
- Topology view
- Develop into a framework to provide generic network automation while enabling specific domain functions
...
- KeyCloak server for Identity and Access Managmenet
Interoperability
- SDO (Standards Developing Organization) specifications supported:
- APIs/Interfaces:
- http/https northbound towards web browser
- southbound ONAP APIs used as they are
- Information/data models:
- Relies on customer data from keycloak
- Current approach is to work dataless except for caching southbound requests
- If there is an existing ONAP project that does something similar to this project explain why this being a new stand-alone project?
- ONAP project is unmaintained. Telekom has a portal it uses internally and would like to donate parts of it's code
...
Component Name | Repository name | Component Description |
|---|---|---|
| portal-ui | The Portal user interface is an Angular web application | |
| portal-bff | The Portal Backend for Frontend (BFF) bundles all API access for the portal-ui and reduces the complexity of API calls for the UI. It is a proxy application that in some cases aggregates multiple calls to southbound systems (the ONAP systems) and also potentially passes less complex objects to the UI. | |
| portal-prefs | The portal-prefs is a spring boot backend application that serves user preferences, like column order of data tables in the portal-ui or which dashboard component is viewed on which place in the portal-ui. The data are stored in the portal-prefs-db. | |
| portal-history | The portal-history is a spring boot backend application that server user history, such as info about user searches, instantiations, deletions. This data is stored for predefined amount of time (for example 72 hours) then they are automatically deleted. | |
| portal-bff-cache | FUTURE ROADMAP The "portal-bff cache" caches certain responses received from systems such as: A&AI, SDC, CDS. The cached "REST requests" contain the data for required by the portal-ui for:
The request from the portal-ui will get the response from the cache if available. The cache will be refreshed after each request too. |
Resources committed to the project: (add/delete rows as necessary)
...