On 4/2/2017 10:13 AM, Matt Riedemann wrote:
On 4/1/2017 1:01 PM, Matt Riedemann wrote:
I know we've talked about this over and over and another bug [1]
reminded me of it. We have long talked about removing the ability to
specify a block device name when creating a server or attaching a volume
because we can't honor the requested device name anyway and trying to do
so just causes issues. That's part of the reason why the libvirt driver
stopped honoring the block device name in requests back in Liberty [2].
I think we all agree on removing the device name from the API, but I'm
having a hard time remembering if someone signed up to write a spec for
this. I could have sworn this came up recently and someone said they'd
write a spec, but I can't remember.
So this is my attempt at remembering and if it's all a dream, then is
anyone interested in owning this? If not, I'll start writing the spec
this week.
[1] https://bugs.launchpad.net/nova/+bug/1648323
One thing I thought about with this is if you want to identify the block
device after it's attached to the server, you can use device tags to do
that (introduced in microversion 2.32). But that's only at server create
time until [1] is merged. So removing the device from attach volume
requests is probably dependent on completing Artom's blueprint first for
tagging volumes when you attach them to an existing server.
[1]
https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/virt-device-tagged-attach-detach.html
Spec started here:
https://review.openstack.org/#/c/452546/
--
Thanks,
Matt
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
