Hello all, Sean, Sorry I didn't understand the question, but at the end I got it. In the OpenStack environment deployed by FUEL 7, there is the HA proxy that does a bind to a VIP (it is not a floating IP). VIP is an additional (public in that case) IP managed by the Corosync/Pacemaker as a resource of the cluster. So basically each controller has a fixed public IP and the HA proxy sends the incoming requests to one the controllers. That is valid for all the endpoints of OpenStack (nova, neutron, etc.). Look at the image as example. So the endpoints are like this: http://<VIP_addrees>:<PORT> So if a controller goes down the endpoint is the same. The HAproxy sends the requests to the up & running controllers. As mentioned the VIP is managed by Corosync/Pacemaker. In order to see all the resources of the FUEL deployed environment, use that useful command "crm status". In this way you can see all the cluster resources, including the public VIP resource called "vip__public". There is also a private vip called "vip__management". Best Regards, Giuseppe -- -------------------------------------------------------- Giuseppe Cossu CREATE-NET Smart Infrastructures Research Engineer Via alla Cascata 56/D - 38123 Povo Trento (Italy) e-mail: giuseppe.cossu at create-net.org Tel: (+39) 0461312428 www.create-net.org -------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160119/a74b8e3d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: LB-1-e1346192625622.png Type: image/png Size: 17778 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160119/a74b8e3d/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy