[rdo-list] tripleo ha topology

Raoul Scarazzini rasca at redhat.com
Thu Dec 15 08:54:11 UTC 2016

On 15/12/2016 09:42, Dotan, Alon wrote:
> So if understood correctly HAproxy is basically a component in pcs?

It is a systemd resource managed by Pacemaker.

Raoul Scarazzini
rasca at redhat.com

> -----Original Message-----
> From: Raoul Scarazzini [mailto:rasca at redhat.com] 
> Sent: Thursday, December 15, 2016 10:33 AM
> To: Dotan, Alon <alon.dotan at hpe.com>; rdo-list at redhat.com
> Subject: Re: [rdo-list] tripleo ha topology
> On 14/12/2016 22:59, Dotan, Alon wrote:
>> Hey,
>> Some can provide link or explanation about the use of haproxy and 
>> pacemaker together in tripleo?
>> Why need pcs if there is galera and haproxy?
> Galera is managed via a specific resource agent which takes care of all the stuff needed to start, stop and, most of all, recover. It automates a lot of tasks which otherwise will be manual.
> Haproxy is managed by Pacemaker because of the Vips. There are specific constraints that ensures that whether a Vip change the host, haproxy service will follow.
> Hope this helps,
> --
> Raoul Scarazzini
> rasca at redhat.com

More information about the dev mailing list