Bug 1384848 – [RFE] Ironic Introspection for NUMA node & PCI Mapping with Numa and Memory Channel List

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1384848 - [RFE] Ironic Introspection for NUMA node & PCI Mapping with Numa and Memory Channel List

Summary:	[RFE] Ironic Introspection for NUMA node & PCI Mapping with Numa and Memory C...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-ironic-python-agent (Show other bugs)
Sub Component:
Version:	10.0 (Newton)
Hardware:	x86_64 Linux

Priority	high Severity high
Target Milestone:	Upstream M2
Target Release:	12.0 (Pike)
Assigned To:	RHOS Maint
QA Contact:	mlammon
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, Triaged

Depends On:
Blocks:	1389435 1442136 1404319 1469576
	Show dependency tree / graph

Reported:	2016-10-14 05:20 EDT by Franck Baudin
Modified:	2018-02-05 14:02 EST (History)
CC List:	18 users (show)

See Also:
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:
Clones:	1404319 (view as bug list)
Environment:
Last Closed:	2017-12-13 15:49:23 EST
Type:	Feature Request
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1635253	None	None	None	2016-11-10 07:13 EST
OpenStack gerrit	424729	None	None	None	2017-05-25 00:44 EDT
Red Hat Product Errata	RHEA-2017:3462	normal	SHIPPED_LIVE	Red Hat OpenStack Platform 12.0 Enhancement Advisory	2018-02-15 20:43:25 EST

Groups: None (edit)

Description Franck Baudin 2016-10-14 05:20:45 EDT

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 05:01:52 EST

Ironic RFE - https://bugs.launchpad.net/ironic-inspector/+bug/1635253

Comment 7 Vijay Chundury 2017-01-06 05:10:49 EST

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 07:03:06 EST

Patches being worked upstream by ksundara@redhat.com

Comment 9 Bertrand 2017-01-16 03:21:36 EST

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 2017-10-25 08:42:51 EDT

Has been verified.

Thanks,
Ziv

Comment 17 errata-xmlrpc 2017-12-13 15:49:23 EST

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

Note You need to log in before you can comment on or make changes to this bug.