Skip to content
Snippets Groups Projects
Commit 144d9bbc authored by Duc Nguyen Cong's avatar Duc Nguyen Cong Committed by Dai Dang Van
Browse files

Support list of controller ip for the amphorae heartbeat receiver


In multi controller deployment, kolla will generate
"controller_ip_port_list option" in [health_manager] section with
ONLY IP of that node instead of a list of controller ip.
Therefor, "amphora-agent.conf" file of amphora instance will
contain IP of ONLY ONE controller node.
In case of that node fail, amphora agent won't send heartbeat
message to other health manager node, and the loadbalancer will
go to ERROR state.

Change-Id: I102ed6ba3fff2c12cc6d37f81ad59508eacc859c
Co-Authored-By: default avatarHieu LE <hieulq2@viettel.com.vn>
parent ac398c99
No related branches found
No related tags found
No related merge requests found
......@@ -52,8 +52,8 @@ memcached_servers = {% for host in groups['memcached'] %}{{ hostvars[host]['ansi
[health_manager]
bind_port = {{ octavia_health_manager_port }}
bind_ip = {{ octavia_network_interface_address }}
controller_ip_port_list = {{ octavia_network_interface_address }}:{{ octavia_health_manager_port }}
heartbeat_key =insecure
heartbeat_key = insecure
controller_ip_port_list = {% for host in groups['octavia-health-manager'] %}{{ hostvars[host]['ansible_' + hostvars[host]['octavia_network_interface']]['ipv4']['address'] }}:{{ octavia_health_manager_port }}{% if not loop.last %},{% endif %}{% endfor %}
[controller_worker]
amp_boot_network_list = {{ octavia_amp_boot_network_list }}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment