Nova feature numa-aware-vswitches not enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Zhang Kunpeng |
Bug Description
Brief Description
-----------------
The following nova feature https:/
This was on the planned list for StarlingX migration to Stein. Without this feature enabled there is no mechanism to ensure VM's are pinned to the same numa node as the data networks/vswitch.
Helm system overrides need to be generated for each hypervisor instance based on the system configuration. Ex:
nova.conf:
[neutron]
physnets = physnet0,physnet1
[neutron_
numa_nodes = 0
[neutron_
numa_nodes = 0,1
Severity
--------
Major
Steps to Reproduce
------------------
N/A
Expected Behavior
------------------
N/A
Actual Behavior
----------------
N/A
Reproducibility
---------------
100%
System Configuration
-------
Any multi-numa worker node
Branch/Pull Time/Commit
-------
Current Load
Last Pass
---------
Never
Timestamp/Logs
--------------
N/A
Test Activity
-------------
N/A
tags: | added: stx.distro.openstack |
tags: |
added: stx.config removed: stx.containers |
Changed in starlingx: | |
assignee: | Shuquan Huang (shuquan) → Zhang Kunpeng (zhangkunpeng) |
tags: | added: in-r-stx20 |
Marking as stx.2.0. This was identified as one of the items to be supported as part of the migration to Stein. As per above, a nova helm override is required to enable this capability.