Configuration Dependent on HAProxy

[David McNally]

In a number of places in the image elements the configuration is dependent on ha proxy being set.

For example in elements/nova/os-apply-config/etc/nova/nova.conf:

{{#haproxy}}
{{#stunnel.connect_ip}}
osapi_compute_listen={{stunnel.connect_ip}}
ec2_listen={{stunnel.connect_ip}}
metadata_listen={{stunnel.connect_ip}}
{{/stunnel.connect_ip}}
{{^stunnel.connect_ip}}
osapi_compute_listen={{local-ipv4}}
ec2_listen={{local-ipv4}}
metadata_listen={{local-ipv4}}
{{/stunnel.connect_ip}}
{{/haproxy}}

This assumes HA Proxy is being used in all cases so if it was disabled (for example if the user had a hardware HA solution) required configurations would not be set.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/133518

[Gregory Haynes (greghaynes)]

AFAICT this is really just an issue where we are bad at naming things / we had to do some funkyness to maintain backwards compatibility from before we supported a load balancer. We should probably create a property called load_balancer or similar, but you can still just define haproxy: true in your heat template to work around this issue.

[OpenStack Infra (hudson-openstack)]

Change abandoned by dave-mcnally (<email address hidden>) on branch: master
Review: https://review.openstack.org/133518

[Emilien Macchi (emilienm)]

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]