| commit | 53490fa3240d2c1d9b4e4948f85d2a3ef0df3746 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Apr 17 09:42:16 2024 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Apr 17 14:58:50 2024 +0200 |
| tree | 8fb6af947b0dac1cb019c86544af8830dbe06d14 | |
| parent | f8a899c48c91681eb61f3968583862ffc9e9ad73 [diff] |
[MARIADB][POLICY] Correct the MariaDB ReadinessCheck The configuration of an external MariaDB did not fit with the template function of _mariadb.tpl and additionally the template function has a bug in the service information. Issue-ID: OOM-3290 Change-Id: I92f758647012ebf289549665f7f5c20e94c9ff66 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.