Public bug reported:
The behaviour of spawn() in the vmwareapi driver wrt images and block
device mappings is currently as follows:
If there are any block device mappings, images are ignored
If there are any block device mappings, the last becomes the root device and
all others are ignored
This means that, for example, the following scenarios are not possible:
1. Spawn an instance with a root device from an image, and a secondary volume
2. Spawn an instance with a volume as a root device, and a secondary volume
The behaviour of the libvirt driver is as follows:
If there is an image, it will be the root device unless there is also a block
device mapping for the root device
All block device mappings are used
If there are multiple block device mappings for the same device, the last one
is used
The vmwareapi driver's behaviour is surprising, and should be modified
to follow the libvirt driver.
** Affects: nova
Importance: Undecided
Status: New
** Tags: vmware
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1271966
Title:
Not possible to spawn vmware instance with multiple disks
Status in OpenStack Compute (Nova):
New
Bug description:
The behaviour of spawn() in the vmwareapi driver wrt images and block
device mappings is currently as follows:
If there are any block device mappings, images are ignored
If there are any block device mappings, the last becomes the root device and
all others are ignored
This means that, for example, the following scenarios are not
possible:
1. Spawn an instance with a root device from an image, and a secondary volume
2. Spawn an instance with a volume as a root device, and a secondary volume
The behaviour of the libvirt driver is as follows:
If there is an image, it will be the root device unless there is also a block
device mapping for the root device
All block device mappings are used
If there are multiple block device mappings for the same device, the last one
is used
The vmwareapi driver's behaviour is surprising, and should be modified
to follow the libvirt driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1271966/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
