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.
10 # introspect defaults to True, if set false the introspection process will
11 # be skipped at deploy time.
15 # Which SDN controller to use. Valid options are 'opendaylight', 'onos',
16 # 'opendaylight-external', 'opencontrail' or false. A value of false will
17 # use Neutron's OVS ML2 controller.
18 sdn_controller: opendaylight
20 # Which version of ODL to use. This is only valid if 'opendaylight' was used
21 # above. Valid options are 'nitrogen', 'oxygen'. If no value
22 # is specified, nitrogen will be used.
23 # odl_version: nitrogen
25 # Whether to install and configure Tacker (VNF Manager)
28 # Whether to configure Congress (policy as a service) datasources
29 # Note: Congress is already installed by default
32 # Whether to configure ODL or ONOS with Service Function Chaining support.
33 # This requires the opnfv-apex-opendaylight-sfc package to be installed,
34 # since it uses a different overcloud image.
37 # Whether to configure ODL with SDNVPN support.
40 # Which dataplane to use for overcloud tenant networks. Valid options are
41 # 'ovs', 'ovs_dpdk' and 'fdio'.
44 # Whether to run the kvm real time kernel (rt_kvm) in the compute node(s) to
45 # reduce the network latencies caused by network function virtualization
48 # Whether to install and configure fdio functionality in the overcloud
49 # The dataplane should be specified as fdio if this is set to true
52 # Whether to run vsperf after the install has completed
55 # Specify a device for ceph to use for the OSDs. By default a virtual disk
56 # is created for the OSDs. This setting allows you to specify a different
57 # target for the OSDs. The setting must be valid on all overcloud nodes.
58 # The controllers and the compute nodes all have OSDs setup on them and
59 # therefore this device name must be valid on all overcloud nodes.
60 # ceph_device: /dev/sdb
62 # Set performance options on specific roles. The valid roles are 'Compute',
63 # 'Controller' and 'Storage', and the valid sections are 'kernel' and 'nova'
67 # # In this example, these three settings will be passed to the kernel
68 # # boot line. Any key/value pair can be entered here, so care should
69 # # be taken to ensure that machines do not fail to boot.
71 # # isolcpus is generally used to push host processes off a particular
72 # # core, so that it can be dedicated to a specific process. On control
73 # # nodes this could be an ovs_dpdk process.
75 # # Hugepages are required for ovs_dpdk support.
77 # # intel_iommu is also required for ovs_dpdk support.
81 # # This is currently the only available option in the nova section. It
82 # # will add the provided string to vcpu_pin_set in nova.conf. This is
83 # # used to pin guest VMs to a set of CPU cores, and is decsribed in
85 # # http://docs.openstack.org
86 # # /ocata/config-reference/compute/config-options.html
89 # # On compute nodes, isolcpus is usually used to reserve cores for use
90 # # either by VMs or ovs_dpdk
95 # Set yardstick option to install yardstick
98 # Set dovetail option to install dovetail