[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [rdo-list] tripleo ha topology



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 redhat com

> -----Original Message-----
> From: Raoul Scarazzini [mailto:rasca redhat com] 
> Sent: Thursday, December 15, 2016 10:33 AM
> To: Dotan, Alon <alon dotan hpe com>; rdo-list 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 redhat com
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]