Bug 1883554 - [RFE] `socket` PCI NUMA affinity policy
Summary: [RFE] `socket` PCI NUMA affinity policy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.0 (Wallaby)
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: ga
: 17.1
Assignee: Artom Lifshitz
QA Contact: James Parker
URL:
Whiteboard:
Depends On: 1827283
Blocks: 1820742 1880120 1905209
TreeView+ depends on / blocked
 
Reported: 2020-09-29 14:48 UTC by Erwan Gallen
Modified: 2023-08-16 01:10 UTC (History)
27 users (show)

Fixed In Version: openstack-nova-23.2.3-1.20230518170958.7e3a8a1.el9ost
Doc Type: Enhancement
Doc Text:
With this update, a RHOSP administrator can create a flavor that has a `socket` PCI NUMA affinity policy. You can use this policy to create an instance that requests a PCI device only when at least one of the instance NUMA nodes has affinity with a NUMA node in the same host socket as the PCI device.
Clone Of: 1827283
: 1905209 (view as bug list)
Environment:
Last Closed: 2023-08-16 01:09:23 UTC
Target Upstream Version: Wallaby
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1995153 0 None None None 2022-10-28 22:10:58 UTC
OpenStack gerrit 765551 0 None MERGED `socket` PCI NUMA-affinity Policy 2022-06-13 19:23:48 UTC
OpenStack gerrit 772779 0 None MERGED pci: implement the 'socket' NUMA affinity policy 2022-06-13 19:23:47 UTC
OpenStack gerrit 862964 0 None MERGED Save cell socket correctly when updating host NUMA topology 2023-06-07 17:03:21 UTC
Red Hat Issue Tracker OSP-3517 0 None None None 2022-01-19 12:17:33 UTC
Red Hat Issue Tracker RHOSPDOC-838 0 None None None 2022-01-19 12:11:20 UTC
Red Hat Product Errata RHEA-2023:4577 0 None None None 2023-08-16 01:10:54 UTC

Comment 19 Artom Lifshitz 2022-07-26 18:50:12 UTC 
I wonder if you're seeing:

                  LOG.warning('This host appears to have multiple sockets per '
                            'NUMA node. The `socket` PCI NUMA affinity '
                            'will not be supported.')

In the logs at libvirt drive init time, given that this is an AMD EPYC system. It would make sense for `socket` to not work on these, but we should definitely handle the failure better. If you do see it, I think we can verify the feature, but file a new bug to track the more graceful failure.
Comment 21 Artom Lifshitz 2022-07-26 21:43:38 UTC 
Could you provide a DB dump of the deployment? Specifically, I'm looking for the the numa_topology JSON blob column in the compute_node row.
Comment 51 errata-xmlrpc 2023-08-16 01:09:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577
Note You need to log in before you can comment on or make changes to this bug.