diff options
| author | Zuul <zuul@review.opendev.org> | 2022-09-06 16:30:19 +0000 |
|---|---|---|
| committer | Gerrit Code Review <review@openstack.org> | 2022-09-06 16:30:19 +0000 |
| commit | b542b5358511ae569eb8d579ac5bdf8757798bb8 (patch) | |
| tree | db56e76ead2f27623ac617de39e70ac562f39174 /doc | |
| parent | 36091a7ed7ad553d5cbb5dcfde0090e1e762bc34 (diff) | |
| parent | efb6fd834eed77e0345ba88dc4e692426d7c12b7 (diff) | |
| download | nova-b542b5358511ae569eb8d579ac5bdf8757798bb8.tar.gz | |
Merge "Doc follow up for PCI in placement"
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/source/admin/pci-passthrough.rst | 21 |
1 files changed, 18 insertions, 3 deletions
diff --git a/doc/source/admin/pci-passthrough.rst b/doc/source/admin/pci-passthrough.rst index 32e5c2fee6..f79349aec7 100644 --- a/doc/source/admin/pci-passthrough.rst +++ b/doc/source/admin/pci-passthrough.rst @@ -51,6 +51,20 @@ capabilities. Nova will ignore PCI devices reported by the hypervisor if the address is outside of these ranges. +.. versionchanged:: 26.0.0 (Zed): + PCI passthrough device inventories now can be tracked in Placement. + For more information, refer to :ref:`pci-tracking-in-placement`. + +.. versionchanged:: 26.0.0 (Zed): + The nova-compute service will refuse to start if both the parent PF and its + children VFs are configured in :oslo.config:option:`pci.device_spec`. + For more information, refer to :ref:`pci-tracking-in-placement`. + +.. versionchanged:: 26.0.0 (Zed): + The nova-compute service will refuse to start with + :oslo.config:option:`pci.device_spec` configuration that uses the + ``devname`` field. + Enabling PCI passthrough ------------------------ @@ -348,6 +362,7 @@ You can also configure this for PCI passthrough devices by specifying the policy in the alias configuration via :oslo.config:option:`pci.alias`. For more information, refer to :oslo.config:option:`the documentation <pci.alias>`. +.. _pci-tracking-in-placement: PCI tracking in Placement ------------------------- @@ -402,13 +417,13 @@ be added to the resource provider representing the matching PCI devices. (Zed) the nova-compute service will refuse to start with such configuration. It is suggested to use the PCI address of the device instead. -The nova-compute service makes sure that already existing instances with PCI +The nova-compute service makes sure that existing instances with PCI allocations in the nova DB will have a corresponding PCI allocation in placement. This allocation healing also acts on any new instances regardless of the status of the scheduling part of this feature to make sure that the nova DB and placement are in sync. There is one limitation of the healing logic. It assumes that there is no in-progress migration when the nova-compute service -is upgraded. If there is an in-progress migration, then the PCI allocation on +is upgraded. If there is an in-progress migration then the PCI allocation on the source host of the migration will not be healed. The placement view will be consistent after such migration is completed or reverted. @@ -417,7 +432,7 @@ Reconfiguring the PCI devices on the hypervisor or changing the nova-compute service is supported in the following cases: * new devices are added -* devices without allocation is removed +* devices without allocation are removed Removing a device that has allocations is not supported. If a device having any allocation is removed then the nova-compute service will keep the device and |