File: virtual-device-role-tagging-ec0c36226a3f2e4d.yaml

package info (click to toggle)
nova 2:14.0.0-4+deb9u1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 33,804 kB
  • sloc: python: 315,557; sh: 1,317; xml: 1,184; pascal: 1,168; makefile: 126; sql: 43
file content (30 lines) | stat: -rw-r--r-- 1,444 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
---
features:
  - |
    The 2.32 microversion adds support for virtual device
    role tagging. Device role tagging is an answer to the
    question 'Which device is which, 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.

    The 2.32 microversion also adds the 2016-06-30 version
    to the metadata API. Starting with 2016-06-30, the
    metadata contains a 'devices' sections which lists any
    devices that are tagged as described in the previous
    paragraph, along with their hardware metadata.
issues:
  - When using virtual device role tagging, the metadata on
    the config drive lags behind the metadata obtained from
    the metadata API. For example, if a tagged virtual
    network interface is detached from the instance, its tag
    remains in the metadata on the config drive. This is due
    to the nature of the config drive, which, once written,
    cannot be easily updated by Nova.