Bug 1725733

Summary:	[Docs][EPIC][RFE][Compute] Document NUMA aware vSwitches
Product:	Red Hat OpenStack	Reporter:	Mikey Ariel <mariel>
Component:	documentation	Assignee:	Irina <igallagh>
Status:	CLOSED NOTABUG	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	15.0 (Stein)	CC:	igallagh
Target Milestone:	---	Keywords:	Documentation, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	docs-accepted
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-15 14:13:36 UTC	Type:	Bug
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:	1187945, 1591229, 1615670
Bug Blocks:

Description Mikey Ariel 2019-07-01 11:05:20 UTC

User story statement:

As an administrator, I want to use a vSwitch network solution without losing a lot of performance.

Purpose of function:

In OpenStack, Compute (Nova) is not aware of the NUMA locality of physical NICs when launching a nova instance. For example, when creating an instance nova attempts to pin the instance to a particular NUMA node, however nova is not aware of the locality of the DPDK enabled interfaces and will launch an instance pinned to a particular numa node, even if the virtual NIC is local to a different NUMA node.

Nova needs to be aware of NUMA locality of physical NICS when plugging instance DPDK VIFS from Neutron Networks.

Comment 2 Matthew Booth 2019-07-05 15:00:15 UTC

SME: Stephen Finucane (sfinucan) (or Sean Mooney)