Marcus, Yes, that is correct! I don't think we need the public IP. But, then if the portal servers are spread across multiple datacenters, I am not pretty sure if private IP alone would help in that case.
I am still looking into this. ~Jerrin On Mon, Oct 16, 2017 at 9:33 AM, Christie, Marcus Aaron <[email protected]> wrote: > Jerrin, > > I’m not sure I completely understand, but if you are on openstack couldn’t > the load balancer connect over the internal network to the web server > instances and only the load balancer needs to connect out over the public > ip address? In other words, the load balancer accepts traffic on the > public ip address and forwards it to the web server instances on private ip > addresses. > > On Oct 9, 2017, at 10:05 PM, Jerrin Suresh <[email protected]> wrote: > > However, now I am facing an issue with binding the ports in consul and > ha-proxy. Within the openstack, there is no provision to access the public > ip of an instance. Hence, ha-proxy, consul-template and consul are > accessing the private IP of the portal server. > > I haven't moved the setup to production. This was the case when I tried > implementing the dummy concept on TACC openstack. So, is there a way in > which I can access the floating IP of instances within an instance? > > > -- MS CS Fall-2018 Indiana University www.linkedin.com/in/jerrinsuresh
