| commit | 3c9a839dec53d453bd86692ae7ba08bc116bd12b | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Thu Apr 11 14:01:24 2024 +0200 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Thu Apr 11 14:59:13 2024 +0200 |
| tree | 6a28c5616ce5d66ad8cbe5e783780a018310c7b3 | |
| parent | 16d200e4f99dbad508156d936b9481bed051055b [diff] |
[PORTALNG] Remove hardcoded /auth from the keycloak urls in bff - add /auth to bff KEYCLOAK_URL [1] - adjust KEYCLOAK_URL's to use keycloakx-http.keycloak [1] since it was removed from the application.yml Issue-ID: PORTALNG-85 Change-Id: I919cfc29494e30e891e732f63f56edd9f6579864 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
The ONAP Operations Manager (OOM) is responsible for life-cycle management of the ONAP platform itself; components such as SO, SDNC, etc.
It is not responsible for the management of services, VNFs or infrastructure instantiated by ONAP or used by ONAP to host such services or VNFs.
OOM uses the open-source Kubernetes container management system as a means to manage the containers that compose ONAP where the containers are hosted either directly on bare-metal servers or on VMs hosted by a 3rd party management system.
OOM ensures that ONAP is easily deployable and maintainable throughout its life cycle while using hardware resources efficiently.
Full documentation is available in ONAP documentation in operations and administration guides.
Please see contributing file to learn on how to contribute
All issues should be filled in ONAP Jira.