For what it's worth, haproxy can be running on a server, and listening on IP addresses that aren't actually associated with that server. In linux, just make sure *net.ipv4.ip_nonlocal_bind* is set to 1, and this will allow haproxy to bind to addresses that aren't currently associated with that server. This is handy for very basic HA solutions like keepalived, where you may just want the HA service managing IPs, and not necessarily turning on and off haproxy as well.
-- Andy Walker System Administrator FBS - creators of flexmls 3415 39th St S Fargo, ND 58104 701-235-7300 On Mon, Mar 24, 2014 at 12:27 PM, Kobus Bensch < kobus.ben...@trustpayglobal.com> wrote: > I use corosync with pacemaker. I have multiple resources on my haproxy > and I use pacemaker to colocate all of the ip's i use on the master node. > As the IP's can't exist on 2 nodes at the same time, haproxy cant be > running on the standby nodes as haproxy will not be running on the standby > node. You will either need to add a lsb resource for haproxy, or do it some > other way. I am currently looking at the lsb resource, so I am doing it in > another way. > > > > On 24/03/2014 16:52, Thomas Heil wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > On 24.03.2014 17:40, Juan Pablo Lorier wrote: > > Hi, > > I'm trying to create a high available solution of load balancers and I > found haproxy that looks like all I need. The only thing I'm not shure > is if I can create a cluster of haproxy server as a built in function of > haproxy (all docs I find refer of a cluster of web servers, not the load > balancers) or if it's like nginx that need to manage HA with pacemaker > or somthing like that. > > Its like nginx. You would need to manage either with pacemaker or > keepalived. > There is no built-in high availability. > In case of pacemaker you could setup: > - floating ip and lsb service haproxy (in case of failover you should > just clone the > lsb ressource to all nodes, so that haproxy is running on all nodes > all the time. > - cluster_ip and lsb service haproxy. if your environment supports it > In case of keepalived: > - create a master slave VIP and ensure that haproxy is running. if it fails > let keepalived do a switchover to the over node, hopefully haproxy > runs there. > > Regards, > > Juan Pablo Lorier > > > > cheers > thomas > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJTMGLBAAoJEOH/xsXYK8GtfC8P/Rhp7nh9gnhx80A9gBddNkDL > IcfukVhPeYrKtn5ZFzWeHyKilPU3AX7XPACWVU9BQ55+wdF74ZbZMCcd7gQ/9DNt > 9LmyhwWqQhanb2JkDyFJR/DpZXNo9nHqF6q5w948KlOp7AvQRzHzgp7VlXG9Kkj3 > i7Kmgl7qYGWyFrrCQKsjgv+ZzYDjgUrQAkLZPy6Rv1WYnOqP33MRtQmbjo2zLH+8 > uiOz0b0SWYHurWWDM9JwIVjymKG2OApupPk4hT3hLm5xiBv866bNVHfyT2VO+3SV > 95G8DRs/73jFCElutbxBcHQGT95pcQ1Dcj4VI2Kq2yH7tm7lTX5tEhbRrnTIC2cN > u33q5NfzBaAiIBQBz/JowZdrnqoPcfQ8eyQqhzKWzscL5Aq72A+A+UYGASq9vxdI > ND7ybDyf1pZw6wkPzlLeRsvldFmvtNsR4a7+IxU6YSK6dBRk4V5F5irdcOx6v7zv > b2sIbVA5f8tXu1Yy//jQeJlF0WFRGoOghBqItz+xalTypshn2C1c8uAUykhKatof > gyRlg4Kk0wPVq1A1awP+GWNdJKSw82WpN+eeV+VrSX5KYToGVIww+Mk/Jqtz0bR0 > KNBOG2sggwQz1NwavxC5PkNgjdVu3LU41I0JT2u23eMcY3MA3daX357HeDr4lN9t > tH07VV9PMpbOQ93wa4sP > =R6lh > -----END PGP SIGNATURE----- > > > > > -- > Kobus Bensch > Senior Systems Administrator > Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD > DDI: 0207 871 3958 > Tel: 0207 871 3890 > Email: kobus.ben...@trustpayglobal.com > > Trustpay Global Limited is an authorised Electronic Money Institution > regulated by the Financial Conduct Authority registration number 900043. > Company No 07427913 Registered in England and Wales with registered address > 130 Wood Street, London, EC2V 6DL, United Kingdom. > > For further details please visit our website at www.trustpayglobal.com. > > The information in this email and any attachments are confidential and > remain the property of Trustpay Global Ltd unless agreed by contract. It is > intended solely for the person to whom or the entity to which it is > addressed. If you are not the intended recipient you may not use, disclose, > copy, distribute, print or rely on the content of this email or its > attachments. If this email has been received by you in error please advise > the sender and delete the email from your system. Trustpay Global Ltd does > not accept any liability for any personal view expressed in this message. >
<<inline: TrustPayGlobal_email_footer.png>>
