internet => vyatta => cloud

user_variables.yml

haproxy_keepalived_external_vip_cidr: "172.29.236.3/22"
haproxy_keepalived_internal_vip_cidr: "172.29.236.5/22"
haproxy_keepalived_external_interface: "br-mgmt"
haproxy_keepalived_internal_interface: "br-mgmt"


openstack_user_config.yml

  internal_lb_vip_address: cloudint.domain.com   # this points to 172.29.236.3
  external_lb_vip_address: cloud.domain.com      # this points to a.b.c.d which is 1:1 nat via vyatta to 172.29.236.5


keepalive has correct IPs:

but in netstat, I see keystone listeing on like this ( on controllers )

tcp        0      0 a.b.c.d:5000        0.0.0.0:*               LISTEN      2331/haproxy
tcp        0      0 172.29.236.3:5000       0.0.0.0:*               LISTEN      2331/haproxy


# this a.b.c.d lives in vyatta ..  how did it came here ?
I check and I see this:

keystone_service:bind cloud.domain.com:5000  [which points to the public IP]