1a94f7f73d
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
51 lines
1.3 KiB
ReStructuredText
51 lines
1.3 KiB
ReStructuredText
.. -*- rst -*-
|
|
|
|
==========================================
|
|
Volume manage extension (os-volume-manage)
|
|
==========================================
|
|
|
|
Creates volumes by using existing storage instead of allocating new
|
|
storage.
|
|
|
|
|
|
Manage existing volume
|
|
======================
|
|
|
|
.. rest_method:: POST /v2/{tenant_id}/os-volume-manage
|
|
|
|
Creates a Block Storage volume by using existing storage rather than allocating new storage.
|
|
|
|
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-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).
|
|
|
|
Error response codes:202,
|
|
|
|
|
|
Request
|
|
-------
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
- description: description
|
|
- availability_zone: availability_zone
|
|
- bootable: bootable
|
|
- volume_type: volume_type
|
|
- name: name
|
|
- volume: volume
|
|
- host: host
|
|
- ref: ref
|
|
- metadata: metadata
|
|
- tenant_id: tenant_id
|
|
|
|
Request Example
|
|
---------------
|
|
|
|
.. literalinclude:: ./samples/volume-manage-request.json
|
|
:language: javascript
|