| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
The ``storage_protocol`` treats all variants of the protocol name as the |
| 5 |
same regarding matches, so for example using FC, fc, or fibre_channel will |
| 6 |
be treated equally in the scheduler, be it when filtering using the volume |
| 7 |
type's extra specs or when using filter and goodness functions. |
| 8 |
|
| 9 |
The storage protocol reporting via the REST API will be now the same for |
| 10 |
them all, using the preferred naming, FC, NVMe-oF, iSCSI, NFS... |
| 11 |
|
| 12 |
If your deployment uses ``storage_protocol`` to differentiate between |
| 13 |
backends that use the same protocol but report it using different variants, |
| 14 |
be aware that they will no longer be differentiated. |
| 15 |
fixes: |
| 16 |
- | |
| 17 |
`Bug #1966103 <https://bugs.launchpad.net/cinder/+bug/1966103>`_: Fixed |
| 18 |
inconsistent behavior of ``storage_protocol`` among different backends that |
| 19 |
report variants of the protocol name, such as FC, fc, fibre_channel. |