Hi, Just place it into /etc/kolla/config/haproxy/services.d/vault.cfg Michal Arbet ( kevko ) Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet@ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline> po 15. 1. 2024 v 13:02 odesílatel Jan Wasilewski <finarffin@gmail.com> napsal:
Hi,
I wanted to inquire about the possibility of configuring the haproxy service for a non-standard OpenStack service. Specifically, I'm referring to Vault, which I use as a backend for the Barbican service. I would like to configure the haproxy settings somewhat "statically," but I want this configuration to be applied during deployment with kolla-ansible.
While inserting non-standard configurations for OpenStack services like Cinder or Barbican in the directory */etc/kolla/config/<openstack_service>/<openstack_service.conf>* works, the same approach doesn't seem to work for haproxy. I have created a configuration for vault.cfg as outlined in [1], but when executing:
kolla-ansible -i multinode --tags common,haproxy deploy
the configured settings are not being read into the haproxy settings. Am I doing something wrong, or is this functionality not possible in this manner, requiring a different configuration approach? I would appreciate any advice and guidance on this matter.
Best regards,
/JW
References: