| commit | 060bc378e32c2ffba34f890c53cc359eb9ee64d0 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Mar 11 17:26:53 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Mar 11 17:31:04 2024 +0100 |
| tree | 8bb7de0ab8445dc7fbbc8831f2ad6a09e9c83381 | |
| parent | 9964927d8766c5c396ef2caf6f7aeb7494db279e [diff] |
[COMMON] Update MariaDB readinessChecks to fix Operator issues Give different readinessCheck rules depending on the usage of mariaDB Operator and local/global DB setup Apply these changes to CDS, NBI, SO, SDNC, Policy Issue-ID: OOM-3280 Change-Id: I4e6f584558ffebb6ab602db88a73c2f02891902e 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.