openstack/nova
Code Issues Proposed changes

Add release note for xenapi virt device tagging support

Browse Source 
Nova change I565617e05acf33e6254ea091b88d975270ffde05 added
the support for creating a server with tagged VIFs and BDMs
with the xenapi driver, but did not contain a release note.

This adds the release note, and much of the text is copied
from Tempest change I9fe520bc9b68d0bc7f879617f2cd27dd1029e4de.

Part of blueprint virt-device-role-tagging-xenapi

Change-Id: I330087944203ab6aa9cf64fd4d3f1909ce44b435
This commit is contained in:
Matt Riedemann 2017-07-06 12:38:30 -04:00
parent e2d0442b5e
commit 85e94cef77
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
releasenotes/notes/xenapi-virt-device-role-tagging-5ffb440f75fae834.yaml Normal file
View File

@ -0,0 +1,20 @@
---
features:
- |
The ``XenAPI`` compute driver now supports creating servers with virtual
interface and block device tags which was introduced in the ``2.32``
microversion.
Note that multiple paths will exist for a tagged disk for the following
reasons:
1. HVM guests may not have the paravirtualization (PV) drivers installed,
in which case the disk will be accessible on the ``ide`` bus. When the
PV drivers are installed the disk will be accessible on the ``xen`` bus.
2. Windows guests with PV drivers installed expose devices in a different
way to Linux guests with PV drivers. Linux systems will see disk paths
under ``/sys/devices/``, but Windows guests will see them in the
registry, for example ``HKLM\System\ControlSet001\Enum\SCSIDisk``. These
two disks are both on the ``xen`` bus.
See the following XenAPI documentation for details: http://xenbits.xen.org/docs/4.2-testing/misc/vbd-interface.txt