From 1a94f7f73d2f1801bf2b8a08ede4997cfb6582d4 Mon Sep 17 00:00:00 2001 From: xiexs Date: Wed, 13 Jul 2016 01:28:42 -0400 Subject: [PATCH] Make the volume-manage doc be more general 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 --- api-ref/v2/source/samples/volume-manage-request.json | 4 ++-- api-ref/v2/source/volume-manage.inc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/api-ref/v2/source/samples/volume-manage-request.json b/api-ref/v2/source/samples/volume-manage-request.json index f84e8261dd9..36321478437 100644 --- a/api-ref/v2/source/samples/volume-manage-request.json +++ b/api-ref/v2/source/samples/volume-manage-request.json @@ -2,8 +2,8 @@ "volume": { "host": "geraint-VirtualBox", "ref": { - "source-volume-name": "existingLV", - "source-volume-id": "1234" + "source-name": "existingLV", + "source-id": "1234" }, "name": "New Volume", "availability_zone": "az2", diff --git a/api-ref/v2/source/volume-manage.inc b/api-ref/v2/source/volume-manage.inc index 42151651b15..5802dd3b320 100644 --- a/api-ref/v2/source/volume-manage.inc +++ b/api-ref/v2/source/volume-manage.inc @@ -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 in the ref parameter in the request. Although each storage driver might interpret this reference differently, the driver should -accept a reference structure that contains either a source-volume- -id or source-volume-name element, if possible. +accept a reference structure that contains either a source-id +or source-name element, if possible. The API chooses the size of the volume by rounding up the size of the existing storage volume to the next gibibyte (GiB).