2014-11-20 15:46:11 |
Denis M. |
description |
Block device type for block_mapping_device is not configurable.
In code we're doing something like this:
volume_info = {
'block_device': {'vdb': "%s:%s:%s:%s" % (volume.id '', volume.size, 1)},
'device_path': '/dev/vdb',
'mount_point': mount_point,
'volumes': [{'id': v_ref.id, 'size': v_ref.size}]
}
# <id>:[<type>]:[<size(GB)>]:[<delete_on_terminate>]
block_device_mapping = {'vdb': "%s:%s:%s:%s" % (volume.id, '', volume.size, 1)}
nova_client.servers.create(..., block_mapping_device=block_device_mapping)
As it can be seen, Trove hardcodes block device type to 'vdb' - it's only valid for "virtio", for example for iSCSI - sdb |
Block device type for block_mapping_device is not configurable.
In code we're doing something like this:
volume_info = {
'block_device': {'vdb': "%s:%s:%s:%s" % (volume.id '', volume.size, 1)},
'device_path': '/dev/vdb',
'mount_point': mount_point,
'volumes': [{'id': v_ref.id, 'size': v_ref.size}]
}
# <id>:[<type>]:[<size(GB)>]:[<delete_on_terminate>]
block_device_mapping = {'vdb': "%s:%s:%s:%s" % (volume.id, '', volume.size, 1)}
nova_client.servers.create(..., block_mapping_device=block_device_mapping)
As it can be seen, Trove hardcodes block device type to 'vdb' - it's only valid for "virtio", for example for iSCSI - sdb
And nova raises error - InvalidBDM: Block Device Mapping is Invalid
nova boot test-mysql-5.5 --image d57a0158-00ed-41ab-bac0-cb90c856dcc2 |
|
2014-11-20 15:46:19 |
Denis M. |
description |
Block device type for block_mapping_device is not configurable.
In code we're doing something like this:
volume_info = {
'block_device': {'vdb': "%s:%s:%s:%s" % (volume.id '', volume.size, 1)},
'device_path': '/dev/vdb',
'mount_point': mount_point,
'volumes': [{'id': v_ref.id, 'size': v_ref.size}]
}
# <id>:[<type>]:[<size(GB)>]:[<delete_on_terminate>]
block_device_mapping = {'vdb': "%s:%s:%s:%s" % (volume.id, '', volume.size, 1)}
nova_client.servers.create(..., block_mapping_device=block_device_mapping)
As it can be seen, Trove hardcodes block device type to 'vdb' - it's only valid for "virtio", for example for iSCSI - sdb
And nova raises error - InvalidBDM: Block Device Mapping is Invalid
nova boot test-mysql-5.5 --image d57a0158-00ed-41ab-bac0-cb90c856dcc2 |
Block device type for block_mapping_device is not configurable.
In code we're doing something like this:
volume_info = {
'block_device': {'vdb': "%s:%s:%s:%s" % (volume.id '', volume.size, 1)},
'device_path': '/dev/vdb',
'mount_point': mount_point,
'volumes': [{'id': v_ref.id, 'size': v_ref.size}]
}
# <id>:[<type>]:[<size(GB)>]:[<delete_on_terminate>]
block_device_mapping = {'vdb': "%s:%s:%s:%s" % (volume.id, '', volume.size, 1)}
nova_client.servers.create(..., block_mapping_device=block_device_mapping)
As it can be seen, Trove hardcodes block device type to 'vdb' - it's only valid for "virtio", for example for iSCSI - sdb
And nova raises error - InvalidBDM: Block Device Mapping is Invalid |
|