Provision backup configuration for cinder-backup group

While cinder-backup has it's own service and group, we still use
cinder-volume for conditioning some configuration, which makes
it untrivial to separate cinder-volume from cinder-backup in deployments

This improves some crucial conditions to work for cinder-backup
in case it's deployed separately.

Change-Id: Ie74931133b7e2bf4262bb48134e80a64c9779d04
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
This commit is contained in:
Dmitriy Rabotyagov
2025-08-13 16:50:39 +02:00
parent 453de43214
commit eb01602ebc
2 changed files with 2 additions and 2 deletions

View File

@@ -227,7 +227,7 @@
openstack_service_system_user: "{{ cinder_system_user_name }}"
openstack_service_venv_bin: "{{ (cinder_install_method == 'source') | ternary(cinder_bin, '') }}"
when:
- cinder_services['cinder-volume']['group'] in group_names
- cinder_services['cinder-volume']['group'] in group_names or cinder_services['cinder-backup']['group'] in group_names
- cinder_backend_rbd_inuse | bool
tags:
- ceph

View File

@@ -23,7 +23,7 @@ cluster = {{ cinder_active_active_cluster_name }}
scheduler_default_filters={{ cinder_scheduler_default_filters | join(',') }}
{% endif %}
{% if cinder_services['cinder-volume']['group'] in group_names %}
{% if cinder_services['cinder-backup']['group'] in group_names %}
{% if cinder_service_backup_program_enabled == true %}
## Cinder Backup