4aab14a09f
Currently, even when [libvirt] volume_use_multipath is set to True, volume attachment silently falls back to single path if multipathd is not running in the host. This sometimes prevents operators from noticing the misconfiguration, until they face any issue caused by missing redundancy. Introduce the new [libvirt] volume_enforce_multipath option, which makes the attachment process fail if multipathd is not running. A similar parameter (enforce_multipath_for_image_xfer) was already implemented in cinder and this change follows how the parameter is implemented there. Also add the check in init phase to detect lack of mulitipath daemon during initializing driver. Min version of os-brick has to be bumped due to the interface change made by 8d919696a9f1b1361f00aac7032647b5e1656082 . Implements: blueprint enforce-multipath Change-Id: I828de70ca7b343a4562ace4049d2b3857dbf900a
10 lines
423 B
YAML
10 lines
423 B
YAML
---
|
|
features:
|
|
- |
|
|
The new ``[libvirt] volume_enforce_multipath`` option has been added. When
|
|
this option is set to ``True``, attachment of volumes is aborted when
|
|
multipathd is not running in the host. Otherwise it falls back to single
|
|
path. This option also makes the libvirt driver to check multipathd during
|
|
initialization, and the compute service fails to start if mulitipathd is
|
|
not running.
|