Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1354558 - [DOCS] [NUMA] NUMA and PCI SR-IOV correlation is missing in "Red Hat Solution for Network Functions Virtualization "
Summary: [DOCS] [NUMA] NUMA and PCI SR-IOV correlation is missing in "Red Hat Solution...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
Target Milestone: async
: 9.0 (Mitaka)
Assignee: Deepti Navale
QA Contact: Martin Lopes
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-11 14:49 UTC by Yariv
Modified: 2016-09-21 06:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-09-15 06:34:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Yariv 2016-07-11 14:49:30 UTC
Red Hat Solution for Network Functions Virtualization 

referring NUMA and CPU pinning, huge pages, see 2.1. Compute  reference to SRIOV, PCI per NUMA is missing.

Currently, deploying Guest VM over SRIOV compute with 2 NUMA nodes and single SRIOV card connected NUMA Cell 0, will fail, once NUMA Cell 0 is fully occupied, will fail

Nova scheduler will not use NUMA Cell 1 as a candidate, due to luck of SRIOV PCIs for this Cell.

I think that we should add
2.1.3. SRIOV support (PCIPathThrough)
SR-IOV enables a single root function, to appear as multiple, separate, physical devices.  

with link to the following

section 8.3.11. NUMA Node Locality for PCI Devices

Comment 3 Andrew Dahms 2016-09-08 00:14:38 UTC
Assigning to Deepti for review.

Comment 7 Deepti Navale 2016-09-15 02:51:17 UTC
Martin has completed peer review and merged the content to Liberty branch. I've cherry-picked the changes to the Mitaka branch. Published to Customer Portal for both releases.



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