Differences between revisions 2 and 9 (spanning 7 versions)

Corosync and HA-proxy

We will use corosync to create a virtual IP-address which is shared by two systems. One of the systems has the virtual IP-address. If the system goes down, the other system will take over the virtual IP-address. HA-proxy will be running on each of the hosts relaying incoming HTTP-requests to two webservers.

192.168.1.47 virtual IP-address
192.168.1.48 haproxy01
192.168.1.49 haproxy02

Software

apt-get install corosync haproxy crmsh

Configuration

Add the local network and a multicast address to /etc/corosync/corosync.conf in the interface section

interface {
        bindnetaddr: 192.168.1.0 
        mcastaddr: 239.192.1.1
}

Restart corosync to load the new configuration.

service corosync restart

Commmands

Run the following on startup

None: Corosync and HA-proxy (last edited 2021-08-12 09:31:08 by Kristian Kallenberg)

-  ⇤ ← Revision 2 as of 2018-01-08 20:21:20 → 
  Size: 355
  Editor: Kristian Kallenberg
  Comment:
+   ← Revision 9 as of 2018-01-10 00:03:15 → ⇥
  Size: 870
  Editor: Kristian Kallenberg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-= Corosync =
+= Corosync and HA-proxy =
 Line 3:
+We will use corosync to create a virtual IP-address which is shared by two systems. One of the systems has the virtual IP-address. If the system goes down, the other system will take over the virtual IP-address. HA-proxy will be running on each of the hosts relaying incoming HTTP-requests to two webservers.
-Line 4:
+Line 5:
-None of what you see below is true!
+ * 192.168.1.47 virtual IP-address
 * 192.168.1.48 haproxy01
 * 192.168.1.49 haproxy02
-Line 6:
+Line 9:
-We will use corosync to create a virtual IP which is share by two systems
+== Software ==
{{{
apt-get install corosync haproxy crmsh
}}}
-Line 8:
+Line 14:
-This has to be configured before haproxy configuration makes any sense, since haproxy should listen on the virtual ip. also we need to configure the dns name for the virtual ip first. so this depends on dns updates too.
+== Configuration ==
Add the local network and a multicast address to `/etc/corosync/corosync.conf` in the `interface` section
{{{
interface {
        bindnetaddr: 192.168.1.0 
        mcastaddr: 239.192.1.1
}
}}}

Restart corosync to load the new configuration.
{{{
service corosync restart
}}}

== Commmands ==
Run the following on startup
{{{

}}}