0ec9a3db94
As reported in the related bug below and merged for the undercloud with https://review.openstack.org/#/c/598167 the Ram/Disk filters are deprecated since [1] so we should stop using them. [1] https://review.openstack.org/#/c/596502/ Related-Bug: 1787910 Change-Id: Ib3585b4c04c974c34d61b868d0454df03c1a2aed
40 lines
3.1 KiB
YAML
40 lines
3.1 KiB
YAML
# A Heat environment that can be used to deploy DPDK with OVS
|
|
# Deploying DPDK requires enabling hugepages for the overcloud nodes
|
|
resource_registry:
|
|
OS::TripleO::Services::ComputeNeutronOvsDpdk: ../docker/services/neutron-ovs-dpdk-agent.yaml
|
|
|
|
parameter_defaults:
|
|
NeutronDatapathType: "netdev"
|
|
NeutronVhostuserSocketDir: "/var/lib/vhost_sockets"
|
|
NovaSchedulerDefaultFilters: "ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,NUMATopologyFilter"
|
|
OvsDpdkDriverType: "vfio-pci"
|
|
|
|
#ComputeOvsDpdkParameters:
|
|
## Host configuration Parameters
|
|
#TunedProfileName: "cpu-partitioning"
|
|
#IsolCpusList: "" # Logical CPUs list to be isolated from the host process (applied via cpu-partitioning tuned).
|
|
# It is mandatory to provide isolated cpus for tuned to achive optimal performance.
|
|
# Example: "3-8,12-15,18"
|
|
#KernelArgs: "" # Space separated kernel args to configure hugepage and IOMMU.
|
|
# Deploying DPDK requires enabling hugepages for the overcloud compute nodes.
|
|
# It also requires enabling IOMMU when using the VFIO (vfio-pci) OvsDpdkDriverType.
|
|
# This should be done by configuring parameters via host-config-and-reboot.yaml environment file.
|
|
|
|
## Attempting to deploy DPDK without appropriate values for the below parameters may lead to unstable deployments
|
|
## due to CPU contention of DPDK PMD threads.
|
|
## It is highly recommended to to enable isolcpus (via KernelArgs) on compute overcloud nodes and set the following parameters:
|
|
#OvsDpdkSocketMemory: "" # Sets the amount of hugepage memory to assign per NUMA node.
|
|
# It is recommended to use the socket closest to the PCIe slot used for the
|
|
# desired DPDK NIC. Format should be comma separated per socket string such as:
|
|
# "<socket 0 mem MB>,<socket 1 mem MB>", for example: "1024,0".
|
|
#OvsPmdCoreList: "" # List or range of CPU cores for PMD threads to be pinned to. Note, NIC
|
|
# location to cores on socket, number of hyper-threaded logical cores, and
|
|
# desired number of PMD threads can all play a role in configuring this setting.
|
|
# These cores should be on the same socket where OvsDpdkSocketMemory is assigned.
|
|
# If using hyperthreading then specify both logical cores that would equal the
|
|
# physical core. Also, specifying more than one core will trigger multiple PMD
|
|
# threads to be spawned, which may improve dataplane performance.
|
|
#NovaVcpuPinSet: "" # Cores to pin Nova instances to. For maximum performance, select cores
|
|
# on the same NUMA node(s) selected for previous settings.
|
|
#NumDpdkInterfaceRxQueues: 1
|