| commit | 7a24e5fedfafeab43c80403759507960abb3c2b0 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Oct 12 10:16:29 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Oct 16 08:15:36 2023 +0200 |
| tree | bd346c160e72af2274f1beb2a4987fb19ba3af51 | |
| parent | 11a7c5036e8d5b7e4c9bf3c2d0c06dc0ebef9ba8 [diff] |
[MARIADB] Update mariadb template to the 0.21.0 Operator In the mariadb-operator version 0.21.0 changes to the CRDs have been done, which require a change in the template. see: https://github.com/mariadb-operator/mariadb-operator/pull/248 PeerAuthentication depends on galera setting (not know why) Issue-ID: OOM-3236 Change-Id: Iaf3cd7128e4c9889c1d56b9b83a72a352e60a39d 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.