2 # The only global parameter at this time is ha_enabled, which will use
3 # the tripleo ha architecture described here:
4 # https://github.com/beekhof/osp-ha-deploy/blob/master/HA-keepalived.md
5 # with 3 controllers by default
7 # If ha_enabled is false, there will only be one controller.
12 # Which SDN controller to use. Valid options are 'opendaylight', 'onos',
13 # 'opendaylight-external', 'opencontrail' or false. A value of false will
14 # use Neutron's OVS ML2 controller.
15 sdn_controller: opendaylight
17 # Which version of ODL to use. This is only valid if 'opendaylight' was used
18 # above. Valid options are 'carbon'. If no value
19 # is specified, carbon will be used.
22 # Whether to configure ODL L3 support. This will disable the Neutron L3 Agent
23 # and use ODL instead.
26 # Whether to install and configure Tacker (VNF Manager)
29 # Whether to configure Congress (policy as a service) datasources
30 # Note: Congress is already installed by default
33 # Whether to configure ODL or ONOS with Service Function Chaining support.
34 # This requires the opnfv-apex-opendaylight-sfc package to be installed,
35 # since it uses a different overcloud image.
38 # Whether to configure ODL with SDNVPN support.
41 # Which dataplane to use for overcloud tenant networks. Valid options are
42 # 'ovs', 'ovs_dpdk' and 'fdio'.
45 # Whether to run the kvm real time kernel (rt_kvm) in the compute node(s) to
46 # reduce the network latencies caused by network function virtualization
49 # Whether to install and configure fdio functionality in the overcloud
50 # The dataplane should be specified as fdio if this is set to true
53 # Whether to run vsperf after the install has completed
56 # Specify a device for ceph to use for the OSDs. By default a virtual disk
57 # is created for the OSDs. This setting allows you to specify a different
58 # target for the OSDs. The setting must be valid on all overcloud nodes.
59 # The controllers and the compute nodes all have OSDs setup on them and
60 # therefore this device name must be valid on all overcloud nodes.
61 # ceph_device: /dev/sdb
63 # Set performance options on specific roles. The valid roles are 'Compute',
64 # 'Controller' and 'Storage', and the valid sections are 'kernel' and 'nova'
68 # # In this example, these three settings will be passed to the kernel
69 # # boot line. Any key/value pair can be entered here, so care should
70 # # be taken to ensure that machines do not fail to boot.
72 # # isolcpus is generally used to push host processes off a particular
73 # # core, so that it can be dedicated to a specific process. On control
74 # # nodes this could be an ovs_dpdk process.
76 # # Hugepages are required for ovs_dpdk support.
78 # # intel_iommu is also required for ovs_dpdk support.
82 # # This is currently the only available option in the nova section. It
83 # # will add the provided string to vcpu_pin_set in nova.conf. This is
84 # # used to pin guest VMs to a set of CPU cores, and is decsribed in
86 # # http://docs.openstack.org
87 # # /ocata/config-reference/compute/config-options.html
90 # # On compute nodes, isolcpus is usually used to reserve cores for use
91 # # either by VMs or ovs_dpdk
96 # Set yardstick option to install yardstick
99 # Set dovetail option to install dovetail