I have a customer who is affected by this issue as well.
They try to set up Ceilometer so that additional VMs could be launched automatically by some triggers.
In the heat.conf (heat_api_cfn section) Fuel specifies:
heat_metadata_server_url=http://<public vip>:8000
heat_waitcondition_server_url=http://<public vip>:8000/v1/waitcondition
heat_watch_server_url=http://<public vip>:8003
But they all are unusable because they are unavailavle in haproxy.
I have a customer who is affected by this issue as well. server_ url=http://<public vip>:8000 ion_server_ url=http://<public vip>:8000/ v1/waitconditio n server_ url=http://<public vip>:8003
They try to set up Ceilometer so that additional VMs could be launched automatically by some triggers.
In the heat.conf (heat_api_cfn section) Fuel specifies:
heat_metadata_
heat_waitcondit
heat_watch_
But they all are unusable because they are unavailavle in haproxy.