openstack/sunbeam-charms
Code Issues Proposed changes

Enable pci.report_in_placement

Browse Source 
We previously had some issues with SR-IOV devices and placement
reporting. Nova docs also made it seem like this scenario is unsupported.

Those issues were addressed by explicitly whitelisting VFs instead
of PFs

Sample: https://paste.ubuntu.com/p/vTg3GZVKz6/plain/

VFs that have an associated physnet will not be reported to the
placement service, however they can still be attached, leveraging
the old Nova PCI tracker.

Snap PR: https://github.com/canonical/snap-openstack-hypervisor/pull/105

Change-Id: I61bfba7d710de289346660e1498129db4f41d7ba
Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
This commit is contained in:
Lucian Petrut
2025-08-07 10:11:35 +00:00
parent 6235f546bc
commit b8ea3ae085
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
charms/nova-k8s/src/templates/nova.conf.j2
View File

@@ -51,10 +51,8 @@ alias = {{ alias }}
[filter_scheduler]
enabled_filters = ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter, PciPassthroughFilter, NUMATopologyFilter
available_filters = nova.scheduler.filters.all_filters
# TODO: consider enabling the following once Nova supports
# tracking SR-IOV ports consumed by Neutron.
# https://docs.openstack.org/nova/latest/admin/pci-passthrough.html
pci_in_placement = False
pci_in_placement = True
[scheduler]
# NOTE(jamespage): perform automatic host cell mapping