Red Hat Bugzilla – Bug 1451714
DPDK minor update requires manual step after deployment
Last modified: 2017-11-09 03:28:26 EST
Description of problem: After minor update, openvswitch upgraded from ovs2.5 to ovs2.6 At ovs2.5 the lcores are provided as part of the DPDK_OPTIONS, At ovs2.6 it should be set inside openvswitch options as lcore-mask. So after the minor update we'll have to set it manually. Version-Release number of selected component (if applicable): OSPd10 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Problem in detail: In OSP10 (OvS2.5), following are the issues: 1) tuned is configured with wrong set of CPUs. Expected configuration is NeutronDpdkCoreList + NovaVcpuPinSet, but it has been configured as HostCpusList. 2) In post-config, the -l of DPDK_OPTIONS is set as 0 and NeutronDpdkdCoreList is configured as pmd-cpu-mask What needs to be corrected after update, manually? 1) Add the list of cpus to be isolated, which is NeutronDpdkCoreList + NovaVcpuPinSet to the tuned conf file. TUNED_CORES="<list of CPUs" sed -i 's/^isolated_cores=.*/isolated_cores=$TUNED_CORES/' $tuned_conf_path tuned-adm profile cpu-partitioning 2) lcore mask after the update will be set to 0. get the cpu mas with get_mask code from the first-boot script [1]. LCORE_MASK="<mask value output of get_mask" ovs-vsctl --no-wait set Open_vSwitch . other-config:dpdk-lcore-mask=$LCORE_MASK
Note this bug is raised for OSP10 minor update, I see the bz is targeting OSP11. For OSP10 (OvS2.5) to OSP11 upgrade, we need only one change out of the two mentioned above: 1) Add the list of cpus to be isolated, which is NeutronDpdkCoreList + NovaVcpuPinSet to the tuned conf file. TUNED_CORES="<list of CPUs" sed -i 's/^isolated_cores=.*/isolated_cores=$TUNED_CORES/' $tuned_conf_path tuned-adm profile cpu-partitioning
Its a tracking bug to highlight the manual steps. I remember the docs have been updated. Reopen if still something is pending.