On 05/26/2015 11:13 AM, Daniel P. Berrange wrote: > On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote: >> Hi, >> >> When someone calls nova volume-attach or the block-device-mapping parameter >> at boot, it is possible to specify a device name for the guest. However I >> couldn't find any guest OS which would honor this. E.g. with libvirt/kvm, if >> the guest has two virtio disks already (vda and vdb), specifying vdf would >> be ignored and the disk will be attached as vdc in the guest. >> I propose to deprecate this option and at boot where it is not optional to >> accept only auto as an option. > > This was a design mistake in the original API which we can't now remove > without breaking backcompatibility. While it is still supported, many > hypervisors will completely ignore it, so we discourage people from ever > using it. Just allow the hypervisor and/or guest OS to pick the device > name >
I have just proposed this yesterday: https://review.openstack.org/#/c/185438/ Removing it from the API is a little bit trickier because it will require a backwards incompatible version bump (this is allowed and all good), but is probably the right thing to do in the long run. I will see if I can propose a patch for this. N. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
