| commit | b784da4b931ec6b7400ff745d9846fe18e5ff7fa | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Oct 07 13:09:41 2022 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Jan 23 10:48:47 2023 +0000 |
| tree | 562bdae48c49f5afdd5f88f2d3b834fa0f225ed9 | |
| parent | 2f43e96c6a84b737590cc4db8a5d53fbac8fd586 [diff] |
[PLATFORM] Add Keycloak ONAP REALM import As part of the ServiceMesh solution Keycloak will be used to enable a central authentication and authorization for ONAP Service Access. This chart provides the import of a default ONAP Realm to an existing Keycloak Instance (alternative to a combined KC+REALM installation). It contains clients for the planned portal-ng. Make all subcomponents selectable Issue-ID: OOM-3021 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I677a3b9e200299c2cde7774e09db6cf33ac510b7
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.