[Fiware-lab-federation-nodes] HA Proxy and VIP

[Sean Murphy]

Hi Guiseppe,

That's great - thanks for that.

On a very related note, do you have some set of reasonable tests that you
run on
a HA system to determine if it is behaving itself? (I'm sure this would be
useful for
everyone).

BR,
Seán.


On Tue, Jan 19, 2016 at 11:16 AM, Giuseppe Cossu <
giuseppe.cossu at create-net.org> wrote:

> 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/5b566a9d/attachment.html>