In the file api-ref/source/v3/index.rst, it missed include
volumes-v3-snapshots-actions.inc, This change is to add it
and fix doc format error.
Change-Id: Ib6dc549f8bc8da5dfd64d0e390cd70b27cd63177
Add APIs introduced for group replication.
Also corrected a few incorrectly referenced group ID
body parameters while I was at it.
Closes-bug: 1700882
Change-Id: I253099072dba9fb6b03f562466aad0ff36b4052f
Allow triggering cleanup from API was introduced in cinder[1], but it's
not documented in the API docs. This change is to add it in the API docs.
[1] https://review.openstack.org/#/c/363010/
Closes-bug: #1708809
Change-Id: Iadec39e8411a598372bc19bb566627a143faa0d8
This commit adds the api documentation for the
GET/PUT os-quota-class-set APIs (v2 and v3).
Change-Id: Idb51b7b90a081775d2d836bf6d9ec8b9c0399f1b
Closes-Bug: #1602400
The 'os-show_image_metadata' API is outdated.
Rewrite the document, also correct the response
codes for image metadata's create/delete APIs.
Change-Id: I50a5b3571973564b8b5010b412d94303866e8dcd
This patch did:
1. Add list manageable volumes API doc.
2. Add create and list manageable snapshots API doc.
Change-Id: Iccffb69b0ffb220f43258ee4c47d5d8964ae7836
Closes-bug: #1590977
This applies an order to the v3 API reference documents.
The idea being how does a new user come into and use the API
and what APIs should they see first when getting started.
Naturally they need to know about versions and microversions
that are avaible. Then they might need to know about volume
types before creating a volume. Once they create a volume
and know the basics of working with volumes, they can start
to take some actions on volumes. After that it's just kind
of a random free for all of APIs and the only order applied
to the rest is sorting alphabetically by title.
Change-Id: I8956de3e6907582f7115430eb959813a13e87a49
Add attachment API related Docs, please note we
use 'instance_uuid' in the request and 'instance' in
the response to represent the same thing 'server_id'.
DocImpact
Change-Id: I8bd5a9061af2b47fd227e8cf2f48f80f271bde14
The Cinder v3 API was marked CURRENT in Mitaka, but there no API ref
was ever created. This is problematic for end users and would hinder
the v3 API from being included in DefCore Interoperability Guidelines
somewhere down the line (since one of DefCore's Criteria[1] is that a
Capability be well documented). This patch creates an API ref for v3.
It also adds a header to the v2 index to show that it is SUPPORTED,
whereas v3 is CURRENT.
[1]
http://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/CoreCriteria.rst#n77
Change-Id: Ia3a8050cd04ad3a487a79d80acf9691feee6182e
Closes-Bug: #1616072
