| commit | 1ffb6511cab271601c17f6f8cad3ec0a91615c63 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Dec 12 15:03:24 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Dec 12 15:06:14 2022 +0100 |
| tree | 7ffd3b1d54e6085f7f78b09c92a7e45f264639fe | |
| parent | f37a1bd3481fbac86b18535a2ecdd3931420641a [diff] |
[MARIADB] Fix for helm compilation in local DB case The compilation of the job fails, as default values for mariadb-galera are missing in the values.yaml Issue-ID: OOM-3077 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Iafd7f8ecb2d3b2d3ae8b252e82a5b494516dfb43
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.