diff options
authorZuul <>2018-06-07 18:44:16 +0000
committerGerrit Code Review <>2018-06-07 18:44:16 +0000
commit8cdccfe68a2a66a289a5ffafc9bad5df57d874b8 (patch)
parent8fc2e8caa02e14ed3075973d94bbffd3e2e10b5c (diff)
parent83264db4eeb07472be189a036bb20daeb725ed77 (diff)
Merge "Deprecate store_capabilities_update_min_interval"
2 files changed, 52 insertions, 4 deletions
diff --git a/specs/rocky/approved/glance_store/deprecate-store_capabilities_update_min_interval.rst b/specs/rocky/approved/glance_store/deprecate-store_capabilities_update_min_interval.rst
new file mode 100644
index 0000000..cacc1ad
--- /dev/null
+++ b/specs/rocky/approved/glance_store/deprecate-store_capabilities_update_min_interval.rst
@@ -0,0 +1,47 @@
2 This work is licensed under a Creative Commons Attribution 3.0 Unported
3 License.
8Spec Lite: Deprecate store_capabilities_update_min_interval
11:project: glance_store
13:problem: The configuration option ``store_capabilities_update_min_interval``
14 is confusing because no existing stores implement the
15 StoreCapability.update_capabilities() method. This has come up in
16 the context of nfs being used for the filesystem backend. If nfs
17 is not ready for writing when the glance api starts, glance will
18 mark the filesystem as not writeable. Operators have tried to get
19 around this problem by setting a non-zero positive value for this
20 option only to find that it doesn't work.
22:solution: Use oslo.config to mark the option as 'deprecated' with an
23 appropriate note. Option will be deprecated in Rocky for removal
24 in 'S'.
26:alternatives: An alternative would be to rewrite the option help text to make
27 it clear that there is no current store for which the option is
28 actionable, but that a framework is in place through which
29 dynamic capability determination could be implemented.
30 Currently a debug level message to this effect is logged on
31 store startup although it is not obvious that the message is
32 related to the ineffectiveness of setting the
33 ``store_capabilities_update_min_interval`` option. The message
34 is: "Store %s doesn't support updating dynamic storage
35 capabilities. Please overwrite 'update_capabilities' method of
36 the store to implement updating logics if needed." (This
37 message is logged independently of setting the option.)
39 The advantage to this approach is that the framework would be
40 available to someone who wanted to implement dynamic updates
41 for a store, and the option would not have to be re-introduced.
43:impacts: None
45:timeline: Rocky milestone 2
47:assignee: rosmaita
diff --git a/specs/rocky/approved/index.rst b/specs/rocky/approved/index.rst
index 52e0d0c..9ca71a5 100644
--- a/specs/rocky/approved/index.rst
+++ b/specs/rocky/approved/index.rst
@@ -17,10 +17,11 @@ Rocky approved specs for Glance:
17 17
18Rocky approved specs for glance_store: 18Rocky approved specs for glance_store:
19 19
20 There are no specs approved for glance_store for Rocky. 20.. toctree::
21 Please consult the :doc:`../../untargeted/index` if 21 :glob:
22 you'd like to work on glance_store during the Rocky 22 :maxdepth: 1
23 development cycle. 23
24 glance_store/*
24 25
25Rocky approved specs for python-glanceclient: 26Rocky approved specs for python-glanceclient:
26 27