This patch adds or updates the parameters by using 'min_version'
for these two patches below:
1. Added sorter, filter and pagination for group snapshot in v3.29
2. Added metadata in volume/summary response in v3.36
Change-Id: I09f6565d45ea2f346a09c8cb45ff24bec6f14acc
The user_id attribute should be shown for end user or other
project(eg:ceilometer, cloudkitty). And it should consistent
with other cinder command to be shown.
Change-Id: I629bacb73135fd7756f6008b5c376a8ab0f0df6a
Closes-Bug: #1614095
In api-ref/source/v3/volumes-v3-type.inc, the api for type-create is missing request
params, So the patch is to add the missing param as well as the sample JSON files.
Change-Id: Iac982462ea0afe8e388d9f6e26b89c01e9c46a8c
This patch implements the spec of reverting volume to
latest snapshot.
Related tempest and client patches:
[1] https://review.openstack.org/#/c/463906/
[2] https://review.openstack.org/#/c/464903/
APIImpact
DocImpact
Partial-Implements: blueprint revert-volume-to-snapshot
Change-Id: Ib20d749c2118c350b5fa0361ed1811296d518a17
The patch did:
1. Add the missing PUT api-ref for volume metadata key.
2. fix the metadata key api's request and response example.
Correct the "metadata" with "meta".
Change-Id: I315682ef86f660eb468991a336d9edae520a4189
Cinder's default policy allows the owner of a volume to initiate
a retype, even if they aren't an admin. However, if the volume
is going to be migrated during the retype operation, then Cinder
is going to call the Nova swap volume API, which by default is
admin-only. So if a non-admin user tries to retype and migrate
their volume, which is attached to a server instance, then it's
going to fail with a 403 error from Nova.
En lieu of a more complete solution, like Cinder using an
elevated service token to call Nova, this change just attempts
to document the restriction in the API reference.
Change-Id: I6282a6d319beead979780a33880947987906c2f3
Related-Bug: #1698224
The normal response code for update or delete API described in volume
attachments api-ref is 202, but the actual response code from the curl
request is 200. This patch is to fix the response codes of these two
APIs in api-ref.
Change-Id: I6eb43f63bb504cb64b12f55de759779058b2979d
From cinder api v3.8, manageable_volumes and manageable_snapshot
rest sources were added that were previously in api extensions.
This patch is to replace os-manage-[volume|snapshot] with
manageable_[volumes|snapshots] in v3 api-ref.
Change-Id: I7b9af1a1243adb082581bc3c67d8697eacc3e70a
In Volumes (volumes) v2/v3 API methods, the request parameter
'volume_id' should be a 'path' param in request param table,
not a 'body' param.
Closes-bug: #1691989
Change-Id: If931d05504d4f050e7da4f4df6f8d49d4318c95d
Cinder added updating backup support in V3.9.
This patch added related api-ref.
Change-Id: I537cb609240e3bcfa130a116e1912d1b660a21f8
Closes-bug: #1607388
There is no document about update a volume's bootable status,
so add the missing doc.
Change-Id: If706205678cfd7a803e2d7733bec34494b47fc66
Partial-Bug: #1607539
One of the purposes of force-detach is to help the admin clean up
if things are in a bad state, so there might not be a connector to
pass in. This is the case if Cinder thinks the volume is attached
but the Nova instance has already been deleted.
Change-Id: I417ed7b100dfe8402599028597511949e00725ac
Closes-Bug: #1619647
Current url scheme doesn't allow to skip admin_tenant_id
or tenant_id params. This change marks them as required
in api-ref. Get default quotas for a project signature
was changed on correct also.
Partial-Bug: #1415214
Change-Id: I0c528d1c49346477b608a12f8f35ee6d47404bd3
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
Add "snapshot_id" and "data_timestamp" and "volume_name" to
the response parameters and error response code in the api-ref of
ext-backups.inc.
Change-Id: I2e3a6c737a74816e5e56b5a435a73e0bf501bec8
Closes-bug: #1676693
There is no API doc found for force-delete volume in cinder.
We need to add the API doc for the operation with its description,
request and response parameters.
Change-Id: Id25b4070a3946d2d7d89f44bdc81039286a5d8fe
Closes-bug: #1673644
Now some API documents for volume actions like
extending volume(https://developer.openstack.org/api-ref/
block-storage/v3/?expanded=extend-a-volume-size-detail) are
using incorrect request argument description
'volume_id in body'.
It should be 'in path'.
Change-Id: I2006b4af4dfc09fb0403c1a78ecef4ac920a51c4
Closes-Bug: #1691358
Now cinder will raise 400 if invalid filter
keys are specified, Update the corresponding
list APIs.
DocImpact
Depends-On: ff3d41b15abb2915de87830980147be51e5da971
Change-Id: I8419b374d7f743e7e9fc88e31c8c4f7d9470059b
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
Since the v2 API is deprecated, put it in the index after
the v3 API which is current, since as a user the first thing
I want to see is the currently supported API reference, not
the deprecated stuff I shouldn't be using anyway.
Change-Id: I760533ca693cb8f678a6031e07789cd68f11bc47
Added volume type encryption sections to volumes v2 types and
added related parameters to parameters file.
Appropriate sample files added.
Had to add for v2 to several headings to pass tox/gates
Change-Id: I7a35551c4ebd345ce2d6c42217015b29c324d96c
Closes-Bug: #1679736
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
