39e518456c
Cinder has multiple drivers reporting the same storage_protocol in their stats but with different strings: For example we have the following variants: - nfs and NFS - nveof, NVMe-oF, NVMeOF - iSCSI, iscsi - FC, fc, fibre_channel This patch documents the right values (to use existing constants) and makes the scheduler treat all variants as if they were equal. This is done by changing the storage_protocol into a list in the scheduler upon reception of the stats from the volume. Most of the code in the scheduler is already able to handle this, the only changes necessary are on the filter and goodness function code, which will now run the respective functions for all the different protocol alternatives and select the right one, but only when the function actually uses the storage_protocol. The API will now report the preferred protocol name in operations like "cinder get-pools --detail". Closes-Bug: #1966103 Change-Id: I07d74078dbb102490dd722029e32c74cec3aa44c
20 lines
923 B
YAML
20 lines
923 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``storage_protocol`` treats all variants of the protocol name as the
|
|
same regarding matches, so for example using FC, fc, or fibre_channel will
|
|
be treated equally in the scheduler, be it when filtering using the volume
|
|
type's extra specs or when using filter and goodness functions.
|
|
|
|
The storage protocol reporting via the REST API will be now the same for
|
|
them all, using the preferred naming, FC, NVMe-oF, iSCSI, NFS...
|
|
|
|
If your deployment uses ``storage_protocol`` to differentiate between
|
|
backends that use the same protocol but report it using different variants,
|
|
be aware that they will no longer be differentiated.
|
|
fixes:
|
|
- |
|
|
`Bug #1966103 <https://bugs.launchpad.net/cinder/+bug/1966103>`_: Fixed
|
|
inconsistent behavior of ``storage_protocol`` among different backends that
|
|
report variants of the protocol name, such as FC, fc, fibre_channel.
|