...
- KeyCloak server for Identity and Access Managmenet
- NGINX as a reverse proxy e.g. for deliveing the single page application
- MongoDB to store preferences and history entries
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
...
Other Dependencies
- Upstream open source projects:
- Keycloak
- NGINX
- MongoDB
- Non ONAP APIs/Interfaces:
- KeyCloak
- Specific IDE integration requirements:
- None
- Integration Testing:
- TBD and aligned with existing ONAP processes. Extensive E2E tests for DT use cases existing but not yet stripped down for smaller feature set
- etc.
- Upstream open source projects:
...