| commit | 723038ed1a0d58dade5c3da643c92f1ff0063005 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Feb 07 10:31:05 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Feb 15 15:24:07 2024 +0100 |
| tree | 4ad0275b431f49d1603d97a19716db7a163ec4af | |
| parent | ad8e7c7a9b5da7c348d9c1c6a3eda61f49301150 [diff] |
[PLATFORM][KEYCLOAK] Update Keycloak instructions and Realm import Update Keycloak installation instructions to use keycloakx (Quarkus based) and update of REALM import Move the creation of the keycloak-ui ingress setup from helmchart to documentation. Issue-ID: OOM-3267 Change-Id: I3c79b05edd488f60a112590584974ba94a8c71a8 Signed-off-by: Andreas Geissler <andreas-geissler@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.