7fb0bd4f35
In order to support virtual device role tagging that was introduced in microversion 2.32, this patch adds: * The 'tag' key to the --nic flag when booting an instance. * The 'tag' key to the --block-device flag when booting an instance. Change-Id: I1866c670994254bc2849b494e318f4ff8cc44eb7 Implements: blueprint virt-device-role-tagging
26 lines
1.1 KiB
YAML
26 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
The 2.32 microverison adds support for virtual device
|
|
role tagging. Device role tagging is an answer to the
|
|
question 'Which device is which?' from inside the guest.
|
|
When booting an instance, an optional arbitrary 'tag'
|
|
parameter can be set on virtual network interfaces
|
|
and/or block device mappings. This tag is exposed to the
|
|
instance through the metadata API and on the config
|
|
drive. Each tagged virtual network interface is listed
|
|
along with information about the virtual hardware, such
|
|
as bus type (ex: PCI), bus address (ex: 0000:00:02.0),
|
|
and MAC address. For tagged block devices, the exposed
|
|
hardware metadata includes the bus (ex: SCSI), bus
|
|
address (ex: 1:0:2:0) and serial number.
|
|
|
|
In the client, device tagging is exposed with the 'tag'
|
|
key in the --block-device and --nic boot arguments.
|
|
issues:
|
|
- |
|
|
While not an issue with the client itself, it should be
|
|
noted that if a tagged network interface or volume is
|
|
detached from a guest, its metadata will continue to
|
|
appear in the config drive, even after instance reboot.
|