Bug 1783354
Summary: | [OSP 15] Optional NUMA affinity for SR-IOV devices | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | smooney |
Component: | openstack-nova | Assignee: | smooney |
Status: | CLOSED ERRATA | QA Contact: | James Parker <jparker> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 15.0 (Stein) | CC: | amcleod, amodi, brault, broose, cswanson, dasmith, dhill, egallen, eglynn, fbaudin, gkadam, igallagh, jhakimra, jjoyce, jniu, jparker, jraju, kchamart, lmarsh, lyarwood, marjones, markmc, mbooth, mburns, mdeng, mschuppe, mvalsecc, nova-maint, oblaut, panbalag, rhos-maint, sbauza, sclewis, sferdjao, sgordon, slinaber, smooney, sputhenp, srevivo, stephenfin, supadhya, vromanso, weiyongjun, yrachman |
Target Milestone: | z2 | Keywords: | FeatureBackport, Patch, Triaged, ZStream |
Target Release: | 15.0 (Stein) | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://blueprints.launchpad.net/nova/+spec/share-pci-device-between-numa-nodes | ||
Whiteboard: | |||
Fixed In Version: | openstack-nova-19.0.4-0.20200131180450.bf9d9e5.el8ost | Doc Type: | Enhancement |
Doc Text: |
With this update, you can configure PCI NUMA affinity on an instance-level basis. This is required to configure NUMA affinity for instances with SR-IOV-based network interfaces. Previously, NUMA affinity was configurable only on a host-level basis for PCI passthrough devices.
|
Story Points: | --- |
Clone Of: | 1775575 | Environment: | |
Last Closed: | 2020-03-05 11:54:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1366208, 1446311, 1647536, 1775575, 1775576, 1791991, 1794010, 1810000 | ||
Bug Blocks: | 1188000, 1419231, 1419948, 1422243, 1427361, 1442136, 1561961, 1650606, 1653846, 1756916, 1757886 |
Comment 7
Alex McLeod
2020-02-19 12:49:04 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, 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/RHBA-2020:0711 |