2020-03-02 09:15:03 |
Vladimir Grevtsev |
description |
https://docs.openstack.org/nova/queens/configuration/config.html
cross_az_attach
Type: boolean
Default: true
Allow attach between instance and volume in different availability zones.
If False, volumes attached to an instance must be in the same availability zone in Cinder as the instance availability zone in Nova. This also means care should be taken when booting an instance from a volume where source is not "volume" because Nova will attempt to create a volume using the same availability zone as what is assigned to the instance. If that AZ is not in Cinder (or allow_availability_zone_fallback=False in cinder.conf), the volume create request will fail and the instance will fail the build request. By default there is no availability zone restriction on volume attach.
Currently, there is no way to inject this config option to the nova.conf, as this option is under the "cinder" block. |
https://docs.openstack.org/nova/queens/configuration/config.html
cross_az_attach
Type: boolean
Default: true
Allow attach between instance and volume in different availability zones.
If False, volumes attached to an instance must be in the same availability zone in Cinder as the instance availability zone in Nova. This also means care should be taken when booting an instance from a volume where source is not "volume" because Nova will attempt to create a volume using the same availability zone as what is assigned to the instance. If that AZ is not in Cinder (or allow_availability_zone_fallback=False in cinder.conf), the volume create request will fail and the instance will fail the build request. By default there is no availability zone restriction on volume attach.
Currently, there is no way to inject this config option to the nova.conf, as this option is under the "cinder" block.
Reason for introducing this: We are planning to start a new deployment for our customer, who was asking for this (e.g they're going to do multi-DC cloud and they would like to have an option to enforce the instances and their volumes being created in a single AZ). |
|