haproxy double entries

[admin0]

stable/newton
ubuntu 16.04

multi-node install with SSL selected.

The deployed haproxy has double entries.

Example:

root@s10:/etc/haproxy# grep -ri api.cloudvpsnl.com:9292 *

conf.d/glance_api: bind api.cloudvpsnl.com:9292 ssl crt /etc/ssl/private/haproxy.pem ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS

haproxy.cfg: bind api.cloudvpsnl.com:9292 ssl crt /etc/ssl/private/haproxy.pem ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS

It should either be in only haproxy.cfg or in conf.d/glance_api
Good to have it it is not in one big cfg but into individual segments in the conf.d folder.

[Jean-Philippe Evrard (jean-philippe-evrard)]

haproxy packaging under centos/ubuntu doesn't work with folders.
We can't include folders without messing with the init scripts.

In order to not ship our own init scripts, like we used to do, we move to doing haproxy config in two steps: one for generating the files in conf.d and the last one by assembling the files for the haproxy.cfg.

That's by design.

[admin0 (shashi-eu)]

Then, can those unnecessary files or folders be deleted after the installation is done ? or maybe put a remark saying

## this file in this conf.d/ folder is for temporary purpose only and can be deleted.

[Kevin Carter (kevin-carter)]

so this is expected. the items in conf.d are concatenated into the single haproxy.cfg file. This is being done because systems that rely on systemd do not have the ability to source multiple conf.d files in a manner consistent with initV or upstart.