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 --- tests/templates/inventory.j2 | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'tests') diff --git a/tests/templates/inventory.j2 b/tests/templates/inventory.j2 index 9a7787b31..769fcae29 100644 --- a/tests/templates/inventory.j2 +++ b/tests/templates/inventory.j2 @@ -352,14 +352,31 @@ network cinder [cinder-backup:children] +cinder + +[cinder-backup-lvm:children] +storage + +[cinder-backup-multiple:children] +cinder storage [cinder-scheduler:children] cinder [cinder-volume:children] +cinder + +[cinder-volume-lvm:children] storage +[cinder-volume-multiple:children] +cinder +storage + +[cinder-scheduler:children] +cinder + # Cloudkitty [cloudkitty-api:children] cloudkitty -- cgit v1.2.3