'''
@@ -205,7 +205,6 @@
// REQUIRED for JS logic
vol_create: false,
// May be null
- vol_device_name: 'vda',
vol_delete_on_instance_delete: false,
vol_size: 1
};
@@ -747,11 +746,9 @@
function setFinalSpecBootImageToVolume(finalSpec) {
if (finalSpec.vol_create) {
// Specify null to get Autoselection (not empty string)
- var deviceName = finalSpec.vol_device_name ? finalSpec.vol_device_name : null;
finalSpec.block_device_mapping_v2 = [];
finalSpec.block_device_mapping_v2.push(
{
- 'device_name': deviceName,
'source_type': bootSourceTypes.IMAGE,
'destination_type': bootSourceTypes.VOLUME,
'delete_on_termination': finalSpec.vol_delete_on_instance_delete,
'''
Forcing horizon not pushing device_name, seems to force cinder to take the decision, just like when adding additional volume to an existing VM where horizon doesn't passes devicename, and leave cinder to do the math instead.
With the above I was able to :
* VM boot volume without scsi meta data decoration:
Volumes Attached
Attached To
0a0cd660-7ce3-4033-9983-2e1099edc5f0 on /dev/vda
* VM boot volume with scsi meta data decoration:
Volumes Attached
Attached To
91f50dbc-8bdf-4293-84ea-fc5df27b5ee4 on /dev/sda
''' on_instance_ delete: false, tImageToVolume( finalSpec) { vol_create) { vol_device_ name ? finalSpec. vol_device_ name : null; block_device_ mapping_ v2 = []; block_device_ mapping_ v2.push( .IMAGE, .VOLUME, on_termination' : finalSpec. vol_delete_ on_instance_ delete,
@@ -205,7 +205,6 @@
// REQUIRED for JS logic
vol_create: false,
// May be null
- vol_device_name: 'vda',
vol_delete_
vol_size: 1
};
@@ -747,11 +746,9 @@
function setFinalSpecBoo
if (finalSpec.
// Specify null to get Autoselection (not empty string)
- var deviceName = finalSpec.
finalSpec.
finalSpec.
{
- 'device_name': deviceName,
'source_type': bootSourceTypes
'destination_type': bootSourceTypes
'delete_
'''
Forcing horizon not pushing device_name, seems to force cinder to take the decision, just like when adding additional volume to an existing VM where horizon doesn't passes devicename, and leave cinder to do the math instead.
With the above I was able to :
* VM boot volume without scsi meta data decoration: 7ce3-4033- 9983-2e1099edc5 f0 on /dev/vda
Volumes Attached
Attached To
0a0cd660-
* VM boot volume with scsi meta data decoration: 8bdf-4293- 84ea-fc5df27b5e e4 on /dev/sda
Volumes Attached
Attached To
91f50dbc-