From df63282b329965b03a8956170aa0b5406a894e56 Mon Sep 17 00:00:00 2001 From: Michal Nasiadka Date: Wed, 11 Mar 2026 12:10:25 +0100 Subject: cinder: Change default destination for cinder-volume/backup containers Kolla-Ansible defaulted for long time to deploy cinder-volume/backup containers on storage group, which is good for Cinder LVM deployments. Problem is - majority of deployments does not use Cinder LVM backend - they use mainly Ceph (based on OpenStack User Survey) and probably some other proprietary vendors which are API driven. Let's change the default to reflect reality. If a user has cinder lvm enabled - we will deploy it as it was before If a user has both cinder lvm and something else enabled - we will deploy cinder-volume and cinder-backup in both places (cinder group and storage group) If a user doesn't have cinder lvm enabled - we deploy only in the cinder group Change-Id: Ia4a874de8f1b8eab8ff688eab4c6af013449c18c Signed-off-by: Michal Nasiadka --- ansible/site.yml | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'ansible/site.yml') diff --git a/ansible/site.yml b/ansible/site.yml index 18d9c3c92..6e286397c 100644 --- a/ansible/site.yml +++ b/ansible/site.yml @@ -602,8 +602,12 @@ hosts: - cinder-api - cinder-backup + - cinder-backup-lvm + - cinder-backup-multiple - cinder-scheduler - cinder-volume + - cinder-volume-lvm + - cinder-volume-multiple - "&enable_cinder_True" serial: '{{ kolla_serial|default("0") }}' max_fail_percentage: >- -- cgit v1.2.3