When using eilometer in an HA configuration with two VIPs (public private) only the local units public IP is being rendered as an available back-end in haproxy.
Relevant Config: ================= "openstack-origin": "cloud:trusty-liberty" "os-admin-network": 192.168.1.0/22 "os-internal-network": 192.168.1.0/22 "os-public-network": 1.2.1.0/24 vip: "192.168.1.208 1.2.1.247" ceilometer-hacluster: corosync_transport: unicast
Snippet from haproxy.cfg ====================== backend ceilometer_api_1.2.1.13 balance leastconn server ceilometer-3 1.2.1.13:8767 check
backend ceilometer_api_192.168.1.47 balance leastconn server ceilometer-6 192.168.1.134:8767 check server ceilometer-4 192.168.1.45:8767 check server ceilometer-3 192.168.1.47:8767 check
Note the missing public backends for 'ceilometer-4' and 'ceilometer-6'
When using eilometer in an HA configuration with two VIPs (public private) only the local units public IP is being rendered as an available back-end in haproxy.
Relevant Config: trusty- liberty" network" : 192.168.1.0/22 network" : 1.2.1.0/24 hacluster:
=================
"openstack-origin": "cloud:
"os-admin-network": 192.168.1.0/22
"os-internal-
"os-public-
vip: "192.168.1.208 1.2.1.247"
ceilometer-
corosync_transport: unicast
Snippet from haproxy.cfg ======= ======= = api_1.2. 1.13
=======
backend ceilometer_
balance leastconn
server ceilometer-3 1.2.1.13:8767 check
backend ceilometer_ api_192. 168.1.47
balance leastconn
server ceilometer-6 192.168.1.134:8767 check
server ceilometer-4 192.168.1.45:8767 check
server ceilometer-3 192.168.1.47:8767 check
Note the missing public backends for 'ceilometer-4' and 'ceilometer-6'