Now that HAProxy configurations can leverage
frontend/backend statements [1], make this the new default
for this cycle, as it allows more complex proxying
scenario that are a prerequisite for optimizing the routing
of API calls in a HA control plane.
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/811723 /opendev. org/openstack/ tripleo- heat-templates/ commit/ c354d21131e9c25 4e611ef6ba31e6e 51611b4043
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit c354d21131e9c25 4e611ef6ba31e6e 51611b4043
Author: Damien Ciabrini <email address hidden>
Date: Wed Sep 29 14:21:17 2021 +0200
Use frontend/backend sections in HAProxy config
Now that HAProxy configurations can leverage backend statements [1], make this the new default
frontend/
for this cycle, as it allows more complex proxying
scenario that are a prerequisite for optimizing the routing
of API calls in a HA control plane.
[1] Ieb36f90c670993 4aa3aa6668d3929 bff872c30f5
Change-Id: Ic25c2588958722 10e7cf2d760769b 492842f0048
Related-Bug: #1941617