Bug 1384848

Summary: [RFE] Ironic Introspection for NUMA node & PCI Mapping with Numa and Memory Channel List
Product: Red Hat OpenStack Reporter: Franck Baudin <fbaudin>
Component: openstack-ironic-python-agentAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: mlammon
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: apevec, atelang, brault, dtantsur, jdonohue, lhh, mburns, nlevinki, radoslaw.smigielski, rhel-osp-director-maint, sclewis, skramaja, slinaber, tamar.inbar-shelach, tvignaud, vchundur, yrachman, zgreenbe
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 12.0 (Pike)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-ironic-python-agent-2.1.1-0.20170614134215.30e0da1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1404319 (view as bug list) Environment:
Last Closed: 2017-12-13 20:49:23 UTC Type: Feature Request
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:    
Bug Blocks: 1389435, 1404319, 1442136, 1469576    

Description Franck Baudin 2016-10-14 09:20:45 UTC 
Description of problem:

The numa node associated with the PCI devices (NICs) and the  list of CPU cores available on each NUMA nodes shall be introspected. The Operator will require these details for configuring the DPDK options in openvswitch.

For instance, the operator will aim to configure two cores / 4 hyperthread of socket 0 to process packets related to the socket 0 NIC, and the same for the numa node 1.
Comment 1 Saravanan KR 2016-11-07 10:01:52 UTC 
Ironic RFE - https://bugs.launchpad.net/ironic-inspector/+bug/1635253
Comment 7 Vijay Chundury 2017-01-06 10:10:49 UTC 
Anjali and Franck,
This the blue print:
https://review.openstack.org/#/c/396147/9/specs/NUMA_node_info.rst

We are still targeting M3 release.
Once the spec gets workflowed we should be on track.

Regards
Vijay
Comment 8 atelang 2017-01-09 12:03:06 UTC 
Patches being worked upstream by ksundara
Comment 9 Bertrand 2017-01-16 08:21:36 UTC 
Additional comment from partner:
The introspected information should also include the entire cpu topology including cpu IDs and siblings mapping .  (such as accepted by “virsh capabilities” command).

Sincerely,

Bertrand
Comment 14 Ziv Greenberg 2017-10-25 12:42:51 UTC 
Has been verified.

Thanks,
Ziv
Comment 17 errata-xmlrpc 2017-12-13 20:49: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, 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-2017:3462