openstack
/
governance
Code Issues Proposed changes

Technical vision: hide implementation details 

As discussed at the Technical Vision session at the OpenStack Forum
in Berlin, make sure the interoperability guidance in the vision
calls out avoiding leakage of backend implementation details and
configuration choices into the end user experience (particularly
when it comes to altering API methods and their behaviors).

Change-Id: Ib15f7c20b4fc3f85dd90172373175b2b179d492e
This commit is contained in:
Jeremy Stanley 2019-01-03 13:41:58 +00:00
parent 158157ff4d
commit 7e4adc7554
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
reference/technical-vision.rst
View File

@ -117,7 +117,10 @@ public and private OpenStack clouds. Where requirements or common OpenStack
deployment patterns differ (for example between public and private cloud),
OpenStack should endeavour to design mechanisms that are usable in either
environment so that applications can be ported from one OpenStack cloud to
another.
another. Deployment implementation details like backend driver differences and
operators' partitioning_ configuration choices should, as much as possible, not
be allowed to leak through to the resource consumer experience; in particular,
they should not alter the behaviors of non-administrative API methods.
Bidirectional Compatibility
---------------------------