diff options
| author | Michal Nasiadka <mnasiadka@gmail.com> | 2026-03-11 12:10:25 +0100 |
|---|---|---|
| committer | Michal Nasiadka <mnasiadka@gmail.com> | 2026-04-17 13:43:47 +0000 |
| commit | df63282b329965b03a8956170aa0b5406a894e56 (patch) | |
| tree | 27e3f46f7e9e39590640b6b3950a4452f23f5cfc /ansible/site.yml | |
| parent | a69e952ccdd0e4ae3885f061fb14b3c5926bd17d (diff) | |
| download | kolla-ansible-df63282b329965b03a8956170aa0b5406a894e56.tar.gz kolla-ansible-df63282b329965b03a8956170aa0b5406a894e56.zip | |
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 <mnasiadka@gmail.com>
Diffstat (limited to 'ansible/site.yml')
| -rw-r--r-- | ansible/site.yml | 4 |
1 files changed, 4 insertions, 0 deletions
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: >- |