openstack/cinder
Code Issues Proposed changes

Make the volume-manage doc be more general

Browse Source 
Just as the following patches did, as sample, we'd
better use "source-name"/"source-id" instead of
"source-volume-name"/"source-volume-id" in the
cinder doc as well.

[1] https://review.openstack.org/#/c/76216/
[2] https://review.openstack.org/#/c/108488/

Change-Id: I7dbd6599c67e82bb38f1bc124ad74d04ad73fe32
This commit is contained in:
xiexs
2016-07-13 01:28:42 -04:00
parent 594ae5e40f
commit 1a94f7f73d
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
api-ref/v2/source/samples/volume-manage-request.json
View File

@@ -2,8 +2,8 @@
"volume": { "volume": {
"host": "geraint-VirtualBox", "host": "geraint-VirtualBox",
"ref": { "ref": {
"source-volume-name": "existingLV", "source-name": "existingLV",
"source-volume-id": "1234" "source-id": "1234"
}, },
"name": "New Volume", "name": "New Volume",
"availability_zone": "az2", "availability_zone": "az2",

4
api-ref/v2/source/volume-manage.inc
View File

@@ -18,8 +18,8 @@ Creates a Block Storage volume by using existing storage rather than allocating
The caller must specify a reference to an existing storage volume The caller must specify a reference to an existing storage volume
in the ref parameter in the request. Although each storage driver in the ref parameter in the request. Although each storage driver
might interpret this reference differently, the driver should might interpret this reference differently, the driver should
accept a reference structure that contains either a source-volume- accept a reference structure that contains either a source-id
id or source-volume-name element, if possible. or source-name element, if possible.
The API chooses the size of the volume by rounding up the size of The API chooses the size of the volume by rounding up the size of
the existing storage volume to the next gibibyte (GiB). the existing storage volume to the next gibibyte (GiB).