Do not specify device_name when creating server with BFV
When creating a server using an existing volume or volume snapshot,
horizon specified a device_name 'vda'.
However the device name depends on bus type or something and
this causes incorrect volume information in the instance detail page
(and nova volume-attachments CLI output).
For detail background, see bug 1560965.
block_device_mapping v1 required device_name but it is no longer
required to specify device_name 'vda' in block_device_mapping v2
in Nova create-server API.
This commit changes to use block_device_mapping v2 so that
we can avoid specifying device_name.
Reviewed: https:/ /review. opendev. org/648328 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=5ab15c49da8 f85f5855f949ad9 b1a4c95a50e714
Committed: https:/
Submitter: Zuul
Branch: master
commit 5ab15c49da8f85f 5855f949ad9b1a4 c95a50e714
Author: Akihiro Motoki <email address hidden>
Date: Thu Mar 28 15:33:51 2019 +0900
Do not specify device_name when creating server with BFV
When creating a server using an existing volume or volume snapshot,
horizon specified a device_name 'vda'.
However the device name depends on bus type or something and
this causes incorrect volume information in the instance detail page
(and nova volume-attachments CLI output).
For detail background, see bug 1560965.
block_ device_ mapping v1 required device_name but it is no longer mapping v2
required to specify device_name 'vda' in block_device_
in Nova create-server API.
This commit changes to use block_device_ mapping v2 so that
we can avoid specifying device_name.
Change-Id: Ice1a6bb2dcddab 0a89c99f345d1f2 cd101955b28
Partial-Bug: #1560965