From aded066c995d8b1a51aeb97b7d16c79024bbe639 Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Fri, 26 Aug 2016 09:51:26 -0500 Subject: [PATCH] Mark Scality volume driver as unsupported The Scality CI has not reported on a patch since 2016-04-12 09:44:38. This is well past our policy for CI reporting. Per Cinder's non-compliance policy [1] this patch marks the driver as unsupported and deprecated and it will be approved if the issue is not corrected by the next cycle. [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Non-Compliance_Policy Change-Id: Ic749db69d793359c9328c8c62b919197c1cec859 --- cinder/volume/drivers/scality.py | 4 ++++ .../mark-scality-unsupported-530370e034a6f488.yaml | 11 +++++++++++ 2 files changed, 15 insertions(+) create mode 100644 releasenotes/notes/mark-scality-unsupported-530370e034a6f488.yaml diff --git a/cinder/volume/drivers/scality.py b/cinder/volume/drivers/scality.py index eb1c6b76313..f3c9fdb5d73 100644 --- a/cinder/volume/drivers/scality.py +++ b/cinder/volume/drivers/scality.py @@ -85,6 +85,10 @@ class ScalityDriver(remotefs_drv.RemoteFSSnapDriver): # as a config switch to customers. self.configuration.scality_sofs_sparsed_volumes = True + # TODO(smcginnis) Either remove this if CI requirements are met, or + # remove this driver in the Ocata release per normal deprecation + self._supported = False + def check_for_setup_error(self): """Sanity checks before attempting to mount SOFS.""" diff --git a/releasenotes/notes/mark-scality-unsupported-530370e034a6f488.yaml b/releasenotes/notes/mark-scality-unsupported-530370e034a6f488.yaml new file mode 100644 index 00000000000..0aeb7c0e018 --- /dev/null +++ b/releasenotes/notes/mark-scality-unsupported-530370e034a6f488.yaml @@ -0,0 +1,11 @@ +--- +upgrade: + - The Scality driver has been marked as unsupported and is + now deprecated. enable_unsupported_drivers will need to + be set to True in cinder.conf to continue to use it. +deprecations: + - The Scality driver has been marked as unsupported and is + now deprecated. enable_unsupported_drivers will need to + be set to True in cinder.conf to continue to use it. If + its support status does not change it will be removed in + the next release.