a75fe3d7cc
"storage_availability_zone" in the [DEFAULT] section of manila's configuration file has allowed deployers to configure and manage both service (scheduler, share manager) and storage system availability. However, quite often manila's services (api, scheduler, share and data managers) are run on a dedicated control plane that is a different failure domain from that of the storage that manila manages. Also, when using share replication, deployers would need to run multiple manila share manager services with different configuration files, each with their own "storage_availability_zone". To allow flexibility of separating service and storage availability zones, we introduce a new configuration option "backend_availability_zone" within the share driver/backend section. When this option is used, it will override the value of the "storage_availability_zone" from the [DEFAULT] section. Change-Id: Ice99a880dd7be7af94dea86b31a6db88be3d7d9b Implements: bp per-backend-availability-zones
15 lines
713 B
YAML
15 lines
713 B
YAML
---
|
|
features:
|
|
- |
|
|
Availability zones may now be configured per backend in a multi-backend
|
|
configuration. Individual back end sections can now have the configuration
|
|
option ``backend_availability_zone`` set. If set, this value will override
|
|
the ``storage_availability_zone`` option from the [DEFAULT] section.
|
|
upgrade:
|
|
- The ``storage_availability_zone`` option can now be overridden per
|
|
backend by using the ``backend_availability_zone`` option within the
|
|
backend stanza. This allows enabling multiple storage backends that may
|
|
be deployed in different AZs in the same ``manila.conf`` file if
|
|
desired, simplifying service architecture around the Share Replication
|
|
feature.
|