| 1 |
--- |
| 2 |
issues: |
| 3 |
- | |
| 4 |
For the convenience of operators, the `unsupported driver removal policy |
| 5 |
<https://docs.openstack.org/cinder/ussuri/drivers-all-about.html#driver-removal>`_ |
| 6 |
was changed during the Ussuri development cycle to allow unsupported |
| 7 |
drivers to remain in the Cinder source code repository at the discretion |
| 8 |
of the Cinder team (basically, this means the vendor has not explicitly |
| 9 |
declared the driver EOL or the vendor has expressed interest in getting |
| 10 |
the third-party CI system working again). Be aware, however, that |
| 11 |
such drivers are subject to immediate removal if they begin failing |
| 12 |
the general Cinder gating tests. |
| 13 |
|
| 14 |
The following drivers were classified as unsupported in the Train |
| 15 |
release and continue as unspported in this release: |
| 16 |
|
| 17 |
- IBM FlashSystem drivers: FC and iSCSI |
| 18 |
- ProphetStor drivers: FC and iSCSI |
| 19 |
- Veritas ACCESS iSCSI driver |
| 20 |
- Virtuozzo Storage driver |
| 21 |
|
| 22 |
For completeness, here is the list of drivers first marked unsupported |
| 23 |
in the Ussuri release. See the "Deprecation Notes" section of this |
| 24 |
document for details. |
| 25 |
|
| 26 |
- Brocade Fibre Channel Zone Manager driver |
| 27 |
- MacroSAN drivers: FC and iSCSI |
| 28 |
- Veritas Clustered NFS driver |
| 29 |
|
| 30 |
In order to use an unsupported driver, ``enable_unsupported_driver`` must |
| 31 |
be set to ``True`` in the driver's section in the cinder.conf file. If |
| 32 |
you are the consumer of such a driver, we encourage you to contact the |
| 33 |
vendor to make them aware of your concerns. |
| 34 |
- | |
| 35 |
A key aspect of *supported* drivers is that there is a fully functioning |
| 36 |
third-party CI system that reports on all proposed changes to the cinder |
| 37 |
code. However, the fact that there are 'unsupported' drivers at all |
| 38 |
indicates that third-party CI systems are unfortunately not always |
| 39 |
fully functioning. You may consult the report at the following link |
| 40 |
to learn the extent to which a particular driver's CI system is reporting |
| 41 |
on the development branch of cinder: |
| 42 |
|
| 43 |
http://cinderstats.ivehearditbothways.com/cireport.txt |
| 44 |
upgrade: |
| 45 |
- | |
| 46 |
The following drivers were classified as unsupported in the Train |
| 47 |
release and continue as unspported in this release. See the "Known |
| 48 |
Issues" section of this document for details. |
| 49 |
|
| 50 |
- IBM FlashSystem drivers: FC and iSCSI |
| 51 |
- ProphetStor drivers: FC and iSCSI |
| 52 |
- Veritas ACCESS iSCSI driver |
| 53 |
- Virtuozzo Storage driver |
| 54 |
|
| 55 |
In order to use an unsupported driver, ``enable_unsupported_driver`` must |
| 56 |
be set to ``True`` in the driver's section in the cinder.conf file. If |
| 57 |
you are the consumer of such a driver, we encourage you to contact the |
| 58 |
vendor to make them aware of your concerns. |
| 59 |
deprecations: |
| 60 |
- | |
| 61 |
The following drivers were deprecated in the Train release but have not |
| 62 |
yet been removed. They continue as unsupported and deprecated in this |
| 63 |
release. See the "Known Issues" section of this document for details. |
| 64 |
|
| 65 |
- IBM FlashSystem drivers: FC and iSCSI |
| 66 |
- ProphetStor drivers: FC and iSCSI |
| 67 |
- Veritas ACCESS iSCSI driver |
| 68 |
- Virtuozzo Storage driver |
| 69 |
|
| 70 |
In order to use an unsupported driver, ``enable_unsupported_driver`` must |
| 71 |
be set to ``True`` in the driver's section in the cinder.conf file. If |
| 72 |
you are the consumer of such a driver, we encourage you to contact the |
| 73 |
vendor to make them aware of your concerns. |