openstack
/
cinder
Code Issues Proposed changes

api-ref: clarify volume_type param in volume create API 

The volume_type parameter to the volume create API can be
either the volume type name or ID, the cinder-api will look
it up either way. This wasn't obvious from the API reference
and required digging into the code to figure it out. This change
simply clarifies the usage in the API reference.

Change-Id: Iae8c43374dee9767e17252279822ccd2121d8246
This commit is contained in:
Matt Riedemann 2018-09-24 11:13:05 -04:00
parent b2276d693a
commit 3eda3fa7a4
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-ref/source/v2/parameters.yaml
View File

@ -1751,7 +1751,7 @@ volume_type_1:
type: object
volume_type_2:
description: |
The volume type. To create an environment with
The volume type (either name or ID). To create an environment with
multiple-storage back ends, you must specify a volume type. Block
Storage volume back ends are spawned as children to ``cinder-
volume``, and they are keyed from a unique queue. They are named

2
api-ref/source/v3/parameters.yaml
View File

@ -2987,7 +2987,7 @@ volume_type_1:
type: object
volume_type_2:
description: |
The volume type. To create an environment with
The volume type (either name or ID). To create an environment with
multiple-storage back ends, you must specify a volume type. Block
Storage volume back ends are spawned as children to ``cinder-
volume``, and they are keyed from a unique queue. They are named