Differences between revisions 2 and 6 (spanning 4 versions)

Corosync

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.

192.168.1.47 virtual IP-address
192.168.1.48 haproxy01
192.168.1.49 haproxy02

Software

apt-get install corosync

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
}

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 6 as of 2018-01-09 23:42:34 → ⇥
  Size: 657
  Editor: Kristian Kallenberg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 2:
+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.
-Line 3:
+Line 4:
+ * 192.168.1.47 virtual IP-address
 * 192.168.1.48 haproxy01
 * 192.168.1.49 haproxy02
-Line 4:
+Line 8:
-None of what you see below is true!
+== Software ==
{{{
apt-get install corosync
}}}
-Line 6:
+Line 13:
-We will use corosync to create a virtual IP which is share by two systems
+== 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
}
}}}
-Line 8:
+Line 22:
-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.
+== Commmands ==
Run the following on startup
{{{

}}}