1 # A Heat environment that can be used to deploy OpenDaylight with L3 DVR and DPDK
3 OS::TripleO::Services::NeutronOvsAgent: OS::Heat::None
4 OS::TripleO::Services::ComputeNeutronOvsAgent: OS::Heat::None
5 OS::TripleO::Services::ComputeNeutronCorePlugin: OS::Heat::None
6 OS::TripleO::Services::OpenDaylightApi: ../puppet/services/opendaylight-api.yaml
7 OS::TripleO::Services::OpenDaylightOvs: ../puppet/services/opendaylight-ovs.yaml
8 OS::TripleO::Services::NeutronL3Agent: OS::Heat::None
11 NeutronEnableForceMetadata: true
12 NeutronMechanismDrivers: 'opendaylight_v2'
13 NeutronServicePlugins: 'odl-router_v2'
14 NovaSchedulerDefaultFilters: "RamFilter,ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,NUMATopologyFilter"
15 ## Deploying DPDK requires enabling hugepages for the overcloud compute nodes.
16 ## It also requires enabling IOMMU when using the VFIO (vfio-pci) OvsDpdkDriverType.
17 ## This can be done using ComputeKernelArgs as shown below.
19 #ComputeKernelArgs: "intel_iommu=on default_hugepagesz=2MB hugepagesz=2MB hugepages=2048"
20 ## Attempting to deploy DPDK without appropriate values for the below parameters may lead to unstable deployments
21 ## due to CPU contention of DPDK PMD threads.
23 ## It is highly recommended to to enable isolcpus (via ComputeKernelArgs) on compute overcloud nodes and set the following parameters:
24 #OvsDpdkSocketMemory: "" # Sets the amount of hugepage memory to assign per NUMA node.
25 # It is recommended to use the socket closest to the PCIe slot used for the
26 # desired DPDK NIC. Format should be comma separated per socket string such as:
27 # "<socket 0 mem MB>,<socket 1 mem MB>", for example: "1024,0".
28 #OvsDpdkDriverType: "vfio-pci" # Ensure the Overcloud NIC to be used for DPDK supports this UIO/PMD driver.
29 #OvsPmdCoreList: "" # List or range of CPU cores for PMD threads to be pinned to. Note, NIC
30 # location to cores on socket, number of hyper-threaded logical cores, and
31 # desired number of PMD threads can all play a role in configuring this setting.
32 # These cores should be on the same socket where OvsDpdkSocketMemory is assigned.
33 # If using hyperthreading then specify both logical cores that would equal the
34 # physical core. Also, specifying more than one core will trigger multiple PMD
35 # threads to be spawned, which may improve dataplane performance.
36 #NovaVcpuPinSet: "" # Cores to pin Nova instances to. For maximum performance, select cores
37 # on the same NUMA node(s) selected for previous settings.