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
Client can still receive the 404/NotFound when attempting
the fetch of the volume.
Change-Id: Ieafaae5ccb5a23b4d3ad37b8e7eee40484346cfc
Signed-off-by: Xiaojun Liao <xiaojunliao85@gmail.com>
In the api ref document, for create volume_types 'extra_specs'
parameter is missing. And for parameter 'is_public', in code it
is used as 'os-volume-type-access:is_public'. For update volume_types
api as per api ref, 'name' and 'extra_specs' parameters are mandatory.
But in code 'name' is optional and 'extra_specs' implementation is not
done.
This patch fixes this discrepancy by updating the api-ref according to
the code.
Change-Id: I7faa711fc72cd81676812017a92ef40273f1bf7c
For create volume manage api, 'bootable', 'name', and 'metadata'
parameters are mandatory as per api ref document but as per code
these parameters are optional.
This patch fixes this discrepancy by updating the api-ref according
to the code.
Change-Id: I614c0866f52503ed7264f7bf74a193dd17590028
'name' is mentioned as an optional parameter in api-ref doc for
POST /v3/{project_id}/group_types API but in the code if we don't
pass 'name' it returns BadRequest. Also in create and update API,
'is_public' parameter is not added in api-ref document.
This patch fixes this discrepancy by updating the api-ref according
to the code.
Change-Id: I34e53ac72cbda9d8264e48e50f5a84ca09b850bd
'group_id' is mentioned as an optional parameter in api-ref doc for
POST /v3/{project_id}/group_snapshots API but in the code if we don't
pass group-id it returns BadRequest.
This patch fixes this discrepancy by updating the api-ref according
to the code.
Closes-Bug: #1735177
Change-Id: Id2165a07995ab706d4a327f7340dccee7799c7b6
This patch implements the spec of creating volume from backup.
Change-Id: Icdc6c7606c43243a9e12d7a42df293b729f589e5
Partial-Implements: blueprint support-create-volume-from-backup
