cinder/per-backend-az-28727aca360a1cc8.yaml at e3a873dbd8ab1f7452f6b65b6d55830c4236a307 - cinder - OpenDev: Free Software Needs Free Tools

openstack/cinder

Sean McGinnis 7c1e92278c Add per-backend availability zones

When volume backends were defined in the [DEFAULT] cinder.conf config
section, it did not make sense to have more than one AZ config setting.
Now that we have multibackend and we have deprecated the ability to
configure backends in DEFAULT, we can set AZs per backend section.

This previously required setting up a separate service using a different
cinder.conf to have more than one AZ. But since the vast majority of
backends are separate physical devices, there is no reason to restrict
the control plane service to be on separate nodes to support separate AZ
configurations.

Change-Id: I0d7669718a1d1e03e3dd42d1a19b70ff03342bd7
Implements: bp multibackend-az-support

2017-03-03 09:35:00 -06:00

8 lines

305 B

YAML

Raw Blame History

 ---
 features:
   - |
     Availability zones may now be configured per backend in a multi-backend
     configuration. Individual backend sections can now set the configuration
     option ``backend_availability_zone``. If set, this value will override
     the [DEFAULT] ``storage_availability_zone`` setting.