f1c8136556
Having all services in one giant haproxy file makes altering configuration for a service both painful and dangerous. Each service should be configured with a simple set of variables and rendered with a single unified template. Available are two new templates: * haproxy_single_service_listen.cfg.j2: close to the original style, but only one service per file * haproxy_single_service_split.cfg.j2: using the newer haproxy syntax for separated frontend and backend For now the default will be the single listen block, for ease of transition. Change-Id: I6e237438fbc0aa3c89a3c8bd706a53b74e71904b
27 lines
1.1 KiB
YAML
27 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
HAProxy configuration is now split per service, which makes creating and
|
|
updating service configs much simpler.
|
|
upgrade:
|
|
- |
|
|
All haproxy related variables have been moved from the ``haproxy`` role to
|
|
the ``haproxy-common`` role, with the exception of the following which were
|
|
also split and renamed after the move\:
|
|
|
|
* ``haproxy_listen_tcp_extra`` becomes ``haproxy_frontend_tcp_extra`` and
|
|
``haproxy_backend_tcp_extra``
|
|
* ``haproxy_listen_http_extra`` becomes ``haproxy_frontend_http_extra`` and
|
|
``haproxy_backend_http_extra``
|
|
- |
|
|
The following additional haproxy related variables have been created in the
|
|
``haproxy-common`` role\:
|
|
|
|
* ``haproxy_http_request_timeout``\: default http request timeout for
|
|
haproxy
|
|
* ``haproxy_queue_timeout``\: default queue timeout for haproxy
|
|
* ``haproxy_connect_timeout``\: default connect timeout for haproxy
|
|
* ``haproxy_check_timeout``\: default check timeout for haproxy
|
|
* ``haproxy_health_check``\: default health check string for haproxy
|
|
* ``haproxy_service_template``\: select which haproxy config style to use
|