Browse Source

OvS DPDK parameters failing in NIC Partitioning

This change is to fix the finding DPDK device name issue in
OvS DPDK derive parameters logic. Currently mistral fails to
derive OvS DPDK parameters in NIC Partitioning and getting
error 'Unable to determine NUMA node for DPDK NIC:'

Change-Id: I8dfc2494d35d5fce52d573f9edcafbe11ab7faac
Closes-Bug: #1855159
(cherry picked from commit 9641cc2ccb)
(cherry picked from commit dd354ee4d6)
(cherry picked from commit 068f8d1ae1)
changes/52/699552/1
Jaganathan Palanisamy 2 months ago
parent
commit
0c490b8c11
1 changed files with 5 additions and 1 deletions
  1. +5
    -1
      tripleo_common/actions/derive_params.py

+ 5
- 1
tripleo_common/actions/derive_params.py View File

@@ -147,7 +147,11 @@ class GetDpdkNicsNumaInfoAction(base.TripleOAction):
members = config.get('members', [])
dpdk_ifaces, mtu = self.get_dpdk_interfaces(members)
for dpdk_iface in dpdk_ifaces:
name = dpdk_iface.get('name', '')
type = dpdk_iface.get('type', '')
if type == 'sriov_vf':
name = dpdk_iface.get('device', '')
else:
name = dpdk_iface.get('name', '')
phy_name = self.get_physical_iface_name(
ordered_nics, name)
node = self.find_numa_node_id(numa_nics, phy_name)

Loading…
Cancel
Save