| commit | cabbb6f88df4e74f599920ebe2e7b0ae9f6ee2c8 | [log] [tgz] |
|---|---|---|
| author | Jozsef Csongvai <jozsef.csongvai@bell.ca> | Fri Mar 04 15:58:31 2022 -0500 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Fri Mar 18 16:11:27 2022 +0000 |
| tree | bdde2c4a96a77f39d3e18b7742c19afab4615912 | |
| parent | db93f8696ea251334f2b2a389843cec82a130e75 [diff] |
[COMMON][MARIADB] Fix backup job The backup job stopped working after upgrade to bitnami images. Mariabackup was not designed to work remotely, it is supposed to run on the database server. Because of this we need to mount the data pvc into the backup job pod. It will however connect to the database daemon using a hostname, so we need to connect to the first replica in the cluster. Also had to set readOnlyRootFilesystem=false and add emptyDir volumes to solve various permission issues. Issue-ID: OOM-2932 Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca> Change-Id: I776903f9ec541f8dc5818b2ba4c1292226ec2bc6
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.