openstack/kolla-ansible.git/ansible/mariadb_backup.yml, branch stable/2026.1

Standardize naming for MariaDB recovery and backup files

2026-01-06T19:28:48+00:00

This commit addresses and corrects the inconsistency in naming across multiple files within the project. Specifically, the terms mariadb_recovery and mariadb_backup have been replaced with mariadb-recovery and mariadb-backup respectively to adhere to the project's naming conventions and improve clarity. Change-Id: I47b80eaa0dc0487f506b47ca065951b5140e0d62 Signed-off-by: Piotr Milewski

ansible-lint: Remove yaml[truthy] from excludes

2025-11-28T09:06:26+00:00

Normalize quotes and some other easy fixes done by ansible-lint --fix Also drop etc from excludes and ignore comment check in etc/kolla/globals.yml Pinning to ansible-lint<25.11.0 because 25.11.1 is breaking without any messages Change-Id: I7dee3866191cef84cd12b1816cdab0a02380ec7f Signed-off-by: Michal Nasiadka

Support Ansible max_fail_percentage

2023-12-05T10:49:42+00:00

This allows us to continue execution until a certain proportion of hosts to fail. This can be useful at scale, where failures are common, and restarting a deployment is time-consuming. The default max failure percentage is 100, keeping the default behaviour. A global max failure percentage may be set via kolla_max_fail_percentage, and individual services may define a max failure percentage via _max_fail_percentage. Note that all hosts in the inventory must be reachable for fact gathering, even those not included in a --limit. Closes-Bug: #1833737 Change-Id: I808474a75c0f0e8b539dc0421374b06cea44be4f

Use mariabackup for database backups

2019-11-01T18:44:10+00:00

Currently, Xtrabackup is used for database backups. However, Xtrabackup is not compatible with MariaDB 10.3. This change switches to use mariabackup [1], which is available in the mariadb image. The documented full and incremental restore procedures have been modified to use mariabackup, following [2] and [3]. [1] https://mariadb.com/kb/en/library/mariabackup-overview/ [2] https://mariadb.com/kb/en/library/full-backup-and-restore-with-mariabackup/ [3] https://mariadb.com/kb/en/library/incremental-backup-and-restore-with-mariabackup/ Change-Id: Id52b9b1f7b013277e401b1f6b8aed34473d2b2c4 Closes-Bug: #1843043 Depends-On: https://review.opendev.org/691290

Update "openstack_release" variable to static brach name

2019-09-16T12:42:44+00:00

Since we use the release name as the default tag to publish images to Dockerhub, we should use this by default. This change also removes support for the magic value "auto". Change-Id: I5610cc7729e9311709147ba5532199a033dfd156 Closes-Bug: #1843518

Factor out OpenStack release detection playbook

2018-11-29T15:49:41+00:00

We copy-paste the same play into various playbooks to detect openstack_release. This change factors that code into a separate playbook that is imported. Change-Id: I5fea005642b960080bf5e43455618dc24766c386

Add new option to perform an on-demand backup of MariaDB

2018-11-22T09:20:59+00:00

blueprint database-backup-recovery Introduce a new option, mariadb_backup, which takes a backup of all databases hosted in MariaDB. Backups are performed using XtraBackup, the output of which is saved to a dedicated Docker volume on the target host (which defaults to the first node in the MariaDB cluster). It supports either full (the default) or incremental backups. Change-Id: Ied224c0d19b8734aa72092aaddd530155999dbc3