womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "docs: add microversions description in the concept doc"

Browse Source
This commit is contained in:
Jenkins
2015-12-08 18:10:59 +00:00
committed by Gerrit Code Review
parent bd7fb7b85f 50aa74f91d
commit 92a4197545
1 changed files with 20 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
api-guide/source/microversions.rst
+20 -5
View File
@@ -11,11 +11,26 @@
License for the specific language governing permissions and limitations
under the License.
==============
=============
Microversions
==============
=============
API v2.1 users micro versions, instead of extensions, to allow for the API
to slowly evolve over time, without breaking any existing users.
API v2.1 supports Microversions. User uses Microversions to discover the
supported API version in the cloud. If cloud is upgraded to support newer
versions, it will still support all older versions to maintain the backward
compatibility for users using older versions. Also user can discover new
features easily with Microversions, then user can take all the advantages of
current cloud.
TODO - add more information.
There are multiple cases which you can resolve with Microversions:
Legacy v2 API user with new cloud
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The minimum version of Microversions is `2.1`, this is a version compatible
with legacy v2 API. The legacy v2 API user don't need to worry about that his
old client is broken with new cloud deployment. Cloud operator don't need to
worry that upgrading cloud to newer versions will break any user with old
client.
TODO: add more use-cases for Microversions