From 2ad6aa911640f506b884d7142a6d4df93059e41b Mon Sep 17 00:00:00 2001
From: tamilhce <tamilhce@gmail.com>
Date: Sat, 3 Sep 2016 16:04:38 +0000
Subject: [PATCH] fixing block_device_mapping_v2 data_type

 'block_device_mapping_v2' should be an list type
Closes-Bug: #1619833

Change-Id: Id7fa0e1dc2cff6438e82ad83b2087f67e0fa628b
---
 api-ref/source/parameters.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml
index f613a9d620ad..6863ecdcc123 100644
--- a/api-ref/source/parameters.yaml
+++ b/api-ref/source/parameters.yaml
@@ -1131,14 +1131,14 @@ block_device_mapping_v2:
 
       .. code-block:: javascript
 
-        "block_device_mapping_v2": {
+        "block_device_mapping_v2": [{
             "boot_index": "0",
             "uuid": "ac408821-c95a-448f-9292-73986c790911",
             "source_type": "image",
             "volume_size": "25",
             "destination_type": "volume",
             "delete_on_termination": true,
-            "tag": "disk1" }
+            "tag": "disk1" }]
 
     Starting in microversion 2.32, the tag is an optional, arbitrary attribute
     that can be used to assign a tag to the block device. This tag is then