Fix discrepancy in api-ref for create volume manage api

For create volume manage api, 'bootable', 'name', and 'metadata'
parameters are mandatory as per api ref document but as per code
these parameters are optional.

This patch fixes this discrepancy by updating the api-ref according
to the code.

Change-Id: I614c0866f52503ed7264f7bf74a193dd17590028

api-ref/source/v3/parameters.yaml

@@ -607,6 +607,13 @@ bootable:
   in: body
   required: true
   type: boolean
+bootable_1:
+  description: |
+    Enables or disables the bootable attribute. You
+    can boot an instance from a bootable volume.
+  in: body
+  required: false
+  type: boolean
 bootable_response:
   description: |
     Enables or disables the bootable attribute. You
@@ -1599,6 +1606,13 @@ metadata_1:
   in: body
   required: true
   type: object
+metadata_10:
+  description: |
+    One or more metadata key and value pairs to be associated
+    with the new volume.
+  in: body
+  required: false
+  type: object
 metadata_2:
   description: |
     One or more metadata key and value pairs that are
@@ -2779,6 +2793,12 @@ volume_name:
   in: body
   required: true
   type: string
+volume_name_1:
+  description: |
+    The volume name.
+  in: body
+  required: false
+  type: string
 volume_type_1:
   description: |
     A ``volume_type`` object.

api-ref/source/v3/volume-manage.inc

@@ -40,13 +40,13 @@ Request
    - volume: volume
    - description: description
    - availability_zone: availability_zone
-   - bootable: bootable
+   - bootable: bootable_1
    - volume_type: volume_type
-   - name: volume_name
+   - name: volume_name_1
    - host: host_mutex
    - cluster: cluster_mutex
    - ref: ref
-   - metadata: metadata
+   - metadata: metadata_10
 
 Request Example
 ---------------