| 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-agent | Assignee: | 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 M2 | Keywords: | 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: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1389435, 1404319, 1442136, 1469576 | |||
|
Description
Franck Baudin
2016-10-14 09:20:45 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 Patches being worked upstream by ksundara 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 Has been verified. Thanks, Ziv 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 |