Mark the IBM Storwize driver unsupported

The IBM driver CIs stopped reporting some time
ago and attempts to reach out to driver maintainers
have failed.

As a result, we need to mark the drivers unsupported
for the T release.

Change-Id: I0a65e4b72e3739dac576924dec11cd8eab3fcccc
This commit is contained in:
Jay S. Bryant 2019-08-28 15:28:22 -05:00 committed by Jay Bryant
parent 6e585da2ff
commit 30630c9628
3 changed files with 18 additions and 1 deletions

View File

@ -2647,6 +2647,9 @@ class StorwizeSVCCommonDriver(san.SanDriver,
VDISKCOPYOPS_INTERVAL = 600
DEFAULT_GR_SLEEP = random.randint(20, 500) / 100.0
# TODO(jsbryant) Remove driver in the 'U' release if CI is not fixed.
SUPPORTED = False
def __init__(self, *args, **kwargs):
super(StorwizeSVCCommonDriver, self).__init__(*args, **kwargs)
self.configuration.append_config_values(storwize_svc_opts)

View File

@ -232,7 +232,7 @@ driver.infinidat=complete
driver.ibm_ds8k=complete
driver.ibm_flashsystem=complete
driver.ibm_gpfs=complete
driver.ibm_storwize=complete
driver.ibm_storwize=missing
driver.ibm_xiv=complete
driver.infortrend=complete
driver.inspur=complete

View File

@ -0,0 +1,14 @@
---
upgrade:
- |
The IBM Storwize drivers have been marked as unsupported
and are now deprecated. ``enable_unsupported_driver`` will need
to be set to ``True`` in the driver's section in cinder.conf to
continue to use them.
deprecations:
- |
The IBM Storwize drivers have been marked as unsupported
and are now deprecated. ``enable_unsupported_driver`` will need
to be set to ``True`` in the driver's section in cinder.conf to
continue to use them. If the support status does not change, they
will be removed in the 'U' development cycle.