summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Riedemann <mriedem.os@gmail.com>2019-03-15 08:01:19 -0400
committerMatt Riedemann <mriedem.os@gmail.com>2019-03-15 08:01:19 -0400
commit5de08c096675378d865fdaabb970191c5db0456f (patch)
tree431c855812b0207c14b8034fdaa0291790b787b9
parent5ca858eaa72acd0513e27a4c9518980b769f5d6e (diff)
docs: cleanup driver parity scope section
This fixes some grammar issues, links to the interop page and fixes a misuse of tenant. Change-Id: I3ce0e130e3691240a625c67dfb6123bafe7f48b8
Notes
Notes (review): Code-Review+2: Stephen Finucane <stephenfin@redhat.com> Workflow+1: Stephen Finucane <stephenfin@redhat.com> Code-Review+1: Ed Leafe <ed@leafe.com> Verified+2: Zuul Submitted-by: Zuul Submitted-at: Fri, 15 Mar 2019 17:47:36 +0000 Reviewed-on: https://review.openstack.org/643566 Project: openstack/nova Branch: refs/heads/master
-rw-r--r--doc/source/contributor/project-scope.rst12
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/source/contributor/project-scope.rst b/doc/source/contributor/project-scope.rst
index 4a688fa..85b032d 100644
--- a/doc/source/contributor/project-scope.rst
+++ b/doc/source/contributor/project-scope.rst
@@ -89,15 +89,15 @@ it is expected that gap with shrink over time.
89Driver Parity 89Driver Parity
90************** 90**************
91 91
92Our goal for the Nova API to provide a consistent abstraction to access 92Our goal for the Nova API is to provide a consistent abstraction to access
93on demand compute resources. We are not aiming to expose all features of all 93on demand compute resources. We are not aiming to expose all features of all
94hypervisors. Where the details of the underlying hypervisor leak through 94hypervisors. Where the details of the underlying hypervisor leak through
95our APIs, we have failed in this goal, and we must work towards better 95our APIs, we have failed in this goal, and we must work towards better
96abstractions that are more interoperable. 96abstractions that are more `interoperable`_.
97This is one reason why we put so much emphasis on the use of Tempest in third 97This is one reason why we put so much emphasis on the use of Tempest in third
98party CI systems. 98party CI systems.
99 99
100The key tenant of driver parity is that if a feature is supported in a driver, 100The key tenet of driver parity is that if a feature is supported in a driver,
101it must feel the same to users, as if they where using any of the other 101it must feel the same to users, as if they where using any of the other
102drivers that also support that feature. The exception is that, if possible for 102drivers that also support that feature. The exception is that, if possible for
103widely different performance characteristics, but the effect of that API call 103widely different performance characteristics, but the effect of that API call
@@ -107,11 +107,13 @@ Following on from that, should a feature only be added to one of the drivers,
107we must make every effort to ensure another driver could be implemented to 107we must make every effort to ensure another driver could be implemented to
108match that behavior. 108match that behavior.
109 109
110Its important that drivers support enough features, so the API actually 110It is important that drivers support enough features, so the API actually
111provides a consistent abstraction. For example, being unable to create a 111provides a consistent abstraction. For example, being unable to create a
112server or delete a server, would severely undermine that goal. 112server or delete a server would severely undermine that goal.
113In fact, Nova only ever manages resources it creates. 113In fact, Nova only ever manages resources it creates.
114 114
115.. _interoperable: https://www.openstack.org/brand/interop/
116
115Upgrades 117Upgrades
116--------- 118---------
117 119