)]}'
{"specs/mitaka/approved/enhance-attach-volume-api.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"35fb3d60c565d8e4635aac2555cca262635d6981","unresolved":false,"context_lines":[{"line_number":131,"context_line":"        }"},{"line_number":132,"context_line":"    }"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"The \u0027bus\u0027 parameter is always return in the response."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Security impact"},{"line_number":137,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a8ffd7b_44900ced","line":134,"updated":"2015-11-24 13:05:41.000000000","message":"Do we not also need to modify the BDM v2.\n\nAlso, it feels like we need to have a way to find out the list of supported bus types for a particular instance?\n\nWe should probably specify what the image property now means. I presume its about what is chosen by default?","commit_id":"800f8820ff727fb5ad1668844959206d76bdf90a"},{"author":{"_account_id":11538,"name":"Zhang Ni","email":"zhangni@huawei.com","username":"zhangni"},"change_message_id":"378fdd2012e9f447df9d4103a79ac6c3d26bd42d","unresolved":false,"context_lines":[{"line_number":131,"context_line":"        }"},{"line_number":132,"context_line":"    }"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"The \u0027bus\u0027 parameter is always return in the response."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Security impact"},{"line_number":137,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a8ffd7b_f9489e2f","line":134,"in_reply_to":"9a8ffd7b_44900ced","updated":"2015-11-25 02:21:37.000000000","message":"\"bus\" already exist in BDM V2, but absent in the \"attach volume\" api.\n\nYes, the end user have to find the list of bus supported by the image, and it\u0027s complicated, maybe decided by the disk type(HDD\\SSD\\NVM), disk channel(SAS/NVME), image os and hypervisor. So bus should not be simply specified by the image parameters and cause the user no right to choose.\n\nThis BP is enhancement, aim to solve the following usecase, the more disk type, the more disk bus:\n* One VM to be able to attach different disks (thus different disk_bus)\n* One Image to be able to be used by different Hypervisors (each of which  has different disk_bus)\t\n* multi-channel (SCSI, NVMe) support for the volume attach process, it is  mainly for SSD disk, which can use qemu SCSI or NVMe bus, user can decide\tto use which bus from a performance view.","commit_id":"800f8820ff727fb5ad1668844959206d76bdf90a"}]}