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
31 lines
949 B
Django/Jinja
31 lines
949 B
Django/Jinja
{
|
|
"command": "/etc/haproxy/haproxy_run.sh",
|
|
"config_files": [
|
|
{
|
|
"source": "{{ container_config_directory }}/haproxy_run.sh",
|
|
"dest": "/etc/haproxy/haproxy_run.sh",
|
|
"owner": "root",
|
|
"perm": "0700"
|
|
},
|
|
{
|
|
"source": "{{ container_config_directory }}/haproxy.cfg",
|
|
"dest": "/etc/haproxy/haproxy.cfg",
|
|
"owner": "root",
|
|
"perm": "0600"
|
|
},
|
|
{
|
|
"source": "{{ container_config_directory }}/services.d/",
|
|
"dest": "/etc/haproxy/services.d",
|
|
"owner": "root",
|
|
"perm": "0700"
|
|
},
|
|
{
|
|
"source": "{{ container_config_directory }}/haproxy.pem",
|
|
"dest": "/etc/haproxy/haproxy.pem",
|
|
"owner": "root",
|
|
"perm": "0600",
|
|
"optional": {{ (not kolla_enable_tls_external | bool) | string | lower }}
|
|
}
|
|
]
|
|
}
|