Note
This feature is available starting from the MCP 2019.2.5 maintenance update. Before enabling the feature, follow the steps described in Apply maintenance updates.
This section provides an instruction on how to configure the parameters of the HAProxy configuration file by overriding them on the cluster level of the Reclass model. For the list of all available global parameters, see the official HAProxy documentation.
To configure global parameters of the HAProxy configuration file:
Open your project Git repository with the Reclass model on the cluster level.
In cluster/<cluster_name>/openstack/init.yml, define the parameters in
the global section using the haproxy:proxy:global pillar and the
following pattern:
parameters:
haproxy:
proxy:
global:
<key>: <value>
In the configuration above, <key> is any required parameter and
<value> is its value that can be a number, string, or boolean.
Replace all dot . signs in the parameter key names with
undescores _ in the pillar definiton. For example, the
tune.ssl.cachesize parameter must be tune_ssl_cachesize in the
pillar configuration.
Example configuration:
parameters:
haproxy:
proxy:
global:
tune_ssl_cachesize: 4
Some keys in the global configuration have dedicated
configurable pillar keys in the pillar structure and are kept for the
backward compatibility. If both parameters are defined, the one from
haproxy:proxy:global pillar has higher priority and overwrites any
other values. For example, the nbproc value can be defined with both
haproxy:proxy:nbproc and haproxy:proxy:global:nbproc parameters.
The timeout values are assumed to be defined in ms if no other unit
is specifically defined. For details,
see HAProxy documentation.