From 610293fdd5686e4126f67de62076a906cc345569 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Tue, 11 Oct 2016 19:47:40 -0400 Subject: [PATCH] doc: note the future of out of tree support The out of tree support section of the nova dev policy document was pretty old and basically said hooks and extension points are buyer beware, but doesn't mention anything about why we don't want them (interoperability) and the efforts the last few releases to actively deprecate and remove hooks/extension points/classloading. This change adds some more wording to that effect to the doc. Change-Id: Iaa1cf3ef7ac6e8e1d75f94e17aaba1058474acca --- doc/source/policies.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/source/policies.rst b/doc/source/policies.rst index a3850ce700fc..da828dd20615 100644 --- a/doc/source/policies.rst +++ b/doc/source/policies.rst @@ -22,6 +22,11 @@ wiring in out of tree code, upstream doesn't actively make any guarantees about these extensibility points; we don't support them, make any guarantees about compatibility, stability, etc. +Furthermore, hooks and extension points in the code impede efforts in Nova to +support interoperability between OpenStack clouds. Therefore an effort is +being made to systematically deprecate and remove hooks, extension points, and +classloading of managers and other services. + Public Contractual APIs ========================