Fix v2 volume create api-reference request parameters

This fixes several things:

1. The consistencygroup_id and metadata parameters are optional.
2. Several parameters used were for non-volume types, this changes
   the api-ref to use the proper parameters that have the correct
   descriptions for creating a volume.

At some point the parameter names in parameters.yaml need to have
more descriptive names than the lazy *_1, *_2, etc names so it's
easier to know what a parameter is for,
e.g. volume_description_body_required, but that's for a later
cleanup.

Change-Id: I1fb8ca507c85bfbf0add41b507c014ae995e17d0
Closes-Bug: #1642983
This commit is contained in:
Matt Riedemann 2016-11-18 10:23:15 -05:00
parent bfd6c48135
commit 33d1270dca

View File

@ -157,19 +157,19 @@ Request
.. rest_parameters:: parameters.yaml .. rest_parameters:: parameters.yaml
- size: size - size: size
- description: description - description: description_9
- imageRef: imageRef - imageRef: imageRef
- multiattach: multiattach - multiattach: multiattach
- availability_zone: availability_zone - availability_zone: availability_zone
- source_volid: source_volid - source_volid: source_volid
- name: name - name: name_13
- volume: volume - volume: volume
- consistencygroup_id: consistencygroup_id - consistencygroup_id: consistencygroup_id_1
- volume_type: volume_type - volume_type: volume_type_2
- snapshot_id: snapshot_id - snapshot_id: snapshot_id
- OS-SCH-HNT:scheduler_hints: OS-SCH-HNT:scheduler_hints - OS-SCH-HNT:scheduler_hints: OS-SCH-HNT:scheduler_hints
- source_replica: source_replica - source_replica: source_replica
- metadata: metadata - metadata: metadata_2
- tenant_id: tenant_id - tenant_id: tenant_id
Request Example Request Example