Calculation of OVS-DPDK parameters

The OVS-DPDK parameters used in the Input JSON file are named differently from the same parameters in RHOSP. The mapping between the OVS-DPDK parameters in RHOSP and the Input JSON file are listed in the following table:

Table 21: OVS-DPDK parameters mapped to Input JSON file
RHOSP OVS-DPDK parameters	Input JSON file parameters
`IsolCpusList`	`isolated_core_list`
`NovaReservedHostMemory`	`reserved_host_memory`
`NovaVcpuPinSet`	`vcpu_pin_set`
`OvsDpdkCoreList`	`core_list`
`OvsDpdkSocketMemory`	`socket_memory`
`OvsPmdCoreList`	`pmd_core_list`
`OvsDpdkMemoryChannels`	`memory_channels`

NOTE:

For more information about calculating the OVS-DPDK parameters, see Network Functions Virtualization Planning and Configuration Guide in Product Documentation for Red Hat OpenStack Platform 13.

NUMA/core allocation for HPE ProLiant DL360 Gen10 with Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz Processor (24/24 Cores in each NUMA)

The following is the NUMA/core allocation for DL360 Gen10 with Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz Processor:

NUMA node(s):          2
NUMA node0 CPU(s):     0-23,48-71
NUMA node1 CPU(s):     24-47,72-95

NOTE:

To find the NUMA/core allocation for a different server or processor, install the OS (example, Linux), on the server, and run the following command:

lscpu | grep -i numa

CPU parameters for OVS-DPDK

Sample configuration for HPE ProLiant DL360 Gen10 with Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz Processor (24/24 Cores in each NUMA):

IsolCpusList: "6-23,30-47"
NovaVcpuPinSet: [‘6-13’,’30-37’]
OvsDpdkCoreList: "1,2,3,4,5,25,26,27,28,29"
OvsPmdCoreList: "14,15,16,17,18,19,20,21,22,23,38,39,40,41,42,43,44,45,46,47"