Browse Source

Merge "docs: cleanup driver parity scope section"

tags/19.0.0.0rc1
Zuul 2 months ago
parent
commit
d1797d8f58
1 changed files with 7 additions and 5 deletions
  1. 7
    5
      doc/source/contributor/project-scope.rst

+ 7
- 5
doc/source/contributor/project-scope.rst View File

@@ -89,15 +89,15 @@ it is expected that gap with shrink over time.
89 89
 Driver Parity
90 90
 **************
91 91
 
92
-Our goal for the Nova API to provide a consistent abstraction to access
92
+Our goal for the Nova API is to provide a consistent abstraction to access
93 93
 on demand compute resources. We are not aiming to expose all features of all
94 94
 hypervisors. Where the details of the underlying hypervisor leak through
95 95
 our APIs, we have failed in this goal, and we must work towards better
96
-abstractions that are more interoperable.
96
+abstractions that are more `interoperable`_.
97 97
 This is one reason why we put so much emphasis on the use of Tempest in third
98 98
 party CI systems.
99 99
 
100
-The key tenant of driver parity is that if a feature is supported in a driver,
100
+The key tenet of driver parity is that if a feature is supported in a driver,
101 101
 it must feel the same to users, as if they where using any of the other
102 102
 drivers that also support that feature. The exception is that, if possible for
103 103
 widely 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,
107 107
 we must make every effort to ensure another driver could be implemented to
108 108
 match that behavior.
109 109
 
110
-Its important that drivers support enough features, so the API actually
110
+It is important that drivers support enough features, so the API actually
111 111
 provides a consistent abstraction. For example, being unable to create a
112
-server or delete a server, would severely undermine that goal.
112
+server or delete a server would severely undermine that goal.
113 113
 In fact, Nova only ever manages resources it creates.
114 114
 
115
+.. _interoperable: https://www.openstack.org/brand/interop/
116
+
115 117
 Upgrades
116 118
 ---------
117 119
 

Loading…
Cancel
Save