Open Stack

2017-09-21 11:32 GMT+02:00 谭 明宵 <tanmingxiao at outlook.com>:
>
> I had HA setup for placement api to work on high availability enviornment by
> using HAproxy on three controller nodes
>
> vim /etc/haproxy/haproxy.cfg
>
> listen nova_placement_cluster
>         bind 0.0.0.0:8778
>         http-request del-header X-Forwarded-Proto
>         server controller01 192.168.105.10:58778 check inter 2000 rise 2
> fall 5
>         server controller02 192.168.105.11:58778 check inter 2000 rise 2
> fall 5
>         server controller03 192.168.105.12:58778 check inter 2000 rise 2
> fall 5
>
> but nova-compute.log has some errors like:
>
> 2017-09-21 17:08:59.690 14155 WARNING nova.scheduler.client.report
> [req-6fefb3b1-fe0b-418e-b76a-2749613a6364 - - - - -] Placement API service
> is not responding.
> 2017-09-21 17:09:59.697 14155 WARNING nova.scheduler.client.report
> [req-6fefb3b1-fe0b-418e-b76a-2749613a6364 - - - - -] Placement API service
> is not responding.
> 2017-09-21 17:10:59.729 14155 WARNING nova.scheduler.client.report
> [req-6fefb3b1-fe0b-418e-b76a-2749613a6364 - - - - -] Placement API service
> is not responding.
>
> what is the correct configuration for placement api in haproxy?

Placement API responds with 401 to haproxy's probes, add something
like "http-check expect status 401" in order to make haproxy see the
backend as active.