Bug 1466000 - [RFE][cinder] Add per-backend availability zones
[RFE][cinder] Add per-backend availability zones
Status: POST
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
high Severity medium
: Upstream M1
: 13.0 (Queens)
Assigned To: Gorka Eguileor
Avi Avraham
: FutureFeature, TestOnly, Triaged
Depends On:
Blocks: 1419948 1452704 1459148 1488390 1510931
  Show dependency treegraph
Reported: 2017-06-28 12:44 EDT by Bertrand
Modified: 2017-11-08 08:07 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 433437 None None None 2017-09-28 13:51 EDT

  None (edit)
Description Bertrand 2017-06-28 12:44:15 EDT
Description of problem:

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

[1] https://blueprints.launchpad.net/cinder/+spec/multibackend-az-support
[2] https://review.openstack.org/#/c/433437/

Note You need to log in before you can comment on or make changes to this bug.