openstack/nova
Code Issues Proposed changes

doc: note the future of out of tree support

Browse Source 
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
This commit is contained in:
Matt Riedemann
2016-10-11 19:47:40 -04:00
parent 77b23da9e8
commit 610293fdd5
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/policies.rst
View File

@@ -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
========================