Add API document for 'list_volume' in Group
show&list APIs.
Code patch: https://review.openstack.org/#/c/409694
Change-Id: Ib328b62c61ec8b8afed3de07020c7ae2bfb163be
the status of volume must be available.
the size of the volume must be equal to or greater than
the backup size.
Change-Id: I89bb72741aec5e73789a5a5cec1bc363f79c766c
The attachment create call was returning HTTP ACCEPTED, which
implies an asynchronous operation. This call is not async, so
corrected this to return SUCCESS instead.
Change-Id: Ieae4e883a77ede0ba0c8a5fca4423f45e0212b2b
Closes-bug: #1747481
I had to dig into the code to figure out that the force
detach volume action was for admins by default. We should
make that clear in the API reference.
Change-Id: I3493e23dba8267fb7e403d30dd0d1e90c8f7726b
Cinder REST API allows one to use a special query parameter
named "all_tenants" to list resources from all projects (tenants)
through the REST API:
`/v3/{project_id}/volumes/detail?all_tenants=1`
However, this option is hardly documented anywhere besides
`/v3/{project_id}/volumes/summary`. So add them.
Change-Id: Ia9cc9e20c3b333a054c90f07e952b61dfad8529e
Closes-Bug: #1743800
Update API document for API 'workers/cleanup',
also remove 'until' from allowed clean keys as
its value is always assigned in code.
Change-Id: Iea940d7c7e52718b8e5e8dcf706aa5d1126860ef
This adds some notes about two things to consider with a volume
retype operation on an in-use multiattach volume:
1. The volume API will reject a retype operation on an in-use volume
where the volume's multiattach value would change.
2. Retyping an in-use volume that has more than one active read/write
attachment is not recommended because on the nova side the swap
volume operation performs a blockRebase which could potentially
lead to data corruption.
In the future, we (nova or cinder or both) will likely need to make
some changes as to what the default attach_mode is for secondary
attachments to a multiattach volume, since today we default to read/write
if it's not specified by the caller when making the attachment.
Change-Id: Ib5a2830ea3cd37236947677225252ef42edaa347
Nova has historically not supported swap volume operations (via
cinder volume retype / volume migration) for an in-use encrypted
volume.
That was recently addressed via nova bug 1739593.
However, as of change Ibfa64f18bbd2fb70db7791330ed1a64fe61c1355
in nova, depending on the version of libvirt/qemu on the compute host,
a luks-encrypted volume will use native qemu luks decryption. That
does not yet support blockRebase operations which are used during
swap volume due to https://bugzilla.redhat.com/show_bug.cgi?id=760547.
So it's safe to say that for now, a retype which involves a volume
migration is not supported for an in-use encrypted volume.
Change-Id: I7ce992f51d50d00950d3fc4ebb44b69a31a94787
Related-Bug: #1739593
This patch is mainly to fix api-ref for v3 volume group types,
including:
1. add description and example for the API: show defaut group type
2. fix parameters: 'is_public' and 'description'
3. remove unused sample file: group-type-show-request.json
Change-Id: I29f160d8ed24473debb345b4ea91ee0545d711b1
This patch dome some fixs on api-ref for v3 volume types, including:
1. add api-ref and sample file for show default volume type API
2. remove unused sample file: volume-type-show-request.json
3. fix parameters: 'name', 'extra_specs', 'is_public', 'description',
and 'os-volume-type-access:is_public'
Change-Id: I6fdcb66d3a56643a5e71bcd68f4bcdc08fc4866b
1 The 'volume_type' shoud be required in the rest_method of request.
So fix the request paremeter about volume_type
2 Fix the parameters of 'volume_type' in the volumes-v3-volumes.inc
Change-Id: I585db62579ac134885a49dc020508a9f0fba3c78
The multiattach parameter is optional when creating
a volume but is required to be in the response when
showing a volume.
This fixes the parameter usage, renames the parameters
so they are more clear (multiattach_1 was for the response
but was never used), and also adds a note to the multiattach
request parameter about how support is dependent on the volume
type being used to create the volume.
Change-Id: Ifaa29140a8e8a9b8090f33fb83e4bb5c98ee847f
Client were receiving the 302/Found when using the url "/v3".
For showing API v3 details, it should have a '/' behind.
Closes-Bug:#1734053
Change-Id: I7e6cb991151fba19dcaecaf95b332fddc1c02deb
Signed-off-by: Xiaojun Liao <xiaojunliao85@gmail.com>
Adding the 'service_uuid' and 'shared_targets' to the API Reference
documentation with a short description.
Closes-Bug: #1739640
Change-Id: I6866a8da47c6910ce8d2a6802839e9a06eb596a5
This patch is mainly to remove some redundant description and modify
wrongly used HTTP method in api-ref for v3 volume types.
Change-Id: I6f8911d9bc80f1c9d9889ebdf8e1bc2480df06d4
most places use description of backup, such as groups,
consistency groups, snapshots .etc, this is incorrect
this patch is to correct them.
Change-Id: I079f0351c93b5f19e87a42b4b0b84ff086b83820
This patch prints a deprecation message when CG APIs are used and
prompts users to swich to Generic Volume Group APIs instead. CG APIs
are also marked as deprecated in API reference docs. CG APIs will be
removed in a future release when it is appropriate and will be
decided by the Cinder team. This was communicated in Pike.
Change-Id: Ib6751fae6b5fb78de98a2ea62f507f9102f71b76
This patch aims to fix http method in api-ref for updating encryption
type, changing from 'POST' to 'PUT'.
Change-Id: Ief48c73eb09afe2b5ff8c391f06013ab7eebd670
