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 requests.

• 192.168.1.49 haproxy01
• 192.168.1.50 haproxy02
• 192.168.1.51 www (virtual IP-address)
• 192.168.1.54 mariadb (virtual IP-address)
• 192.168.1.58 redis (virtual IP-address)

Software

apt-get install corosync haproxy crmsh

Configuration

Before binding to the DNS name www make sure the DNS server knows that name. There is no physical or virtual network interfaces, so the DNS updates has to be done manually.

HA-proxy

HA-proxy resource script

Download the HA-proxy resource script, place it in /usr/lib/ocf/resource.d/heartbeat/haproxy and make it executeable.

wget https://raw.githubusercontent.com/thisismitch/cluster-agents/master/haproxy -O /usr/lib/ocf/resource.d/heartbeat/haproxy
chmod +x /usr/lib/ocf/resource.d/heartbeat/haproxy

As we will let corosync start haproxy, we will have to disable haproxy as a service.

service haproxy stop
systemctl disable haproxy

Services

Add the configuration for the services to /etc/haproxy/haproxy.cfg. Notice that the galera cluster is checked with a mariadb user called haproxy. This user will be created when the galera cluster is configured.

listen www_farm 
        bind www:80
        mode http
        balance roundrobin
        cookie LBN insert indirect nocache
        option httpclose
        option forwardfor
        server www01 www01:80 cookie node1 check
        server www02 www02:80 cookie node2 check

listen galera_cluster
        bind mariadb:3306
        mode tcp
        balance roundrobin
        option tcpka
        option mysql-check user haproxy
        server mariadb01 mariadb01:3306 check weight 1 
        server mariadb02 mariadb02:3306 check weight 1
        server mariadb03 mariadb03:3306 check weight 1

listen redis
        bind redis:6379
        mode tcp
        balance first
        option tcp-check
        tcp-check send info\ replication\r\n
        tcp-check expect string role:master
        server redis01 redis01:6379 check inter 1s
        server redis02 redis02:6379 check inter 1s
        server redis03 redis03:6379 check inter 1s

Copy the configuration /etc/haproxy/haproxy.cfg to the other host.

Corosync

Encryption

Edit /etc/corosync/corosync.conf and make the following changes.

totem {
        cluster_name: www
        crypto_cipher: aes256
        crypto_hash: sha512

        interface {
                bindnetaddr: 192.168.1.0 
                mcastaddr: 239.192.1.1
        }
}

Authentication Key

Generate the authkey. Note that this requires entropy, so use your system and the entropy will be generated. Speed this up by running dd if=/dev/vda of=/dev/null in another terminal or install haveged.

corosync-keygen

Network

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
}

Copy the configuration /etc/corosync/corosync.conf and the authkey /etc/corosync/authkey to the other host.

Restart corosync on both hosts to load the new configuration.

service corosync restart

The two nodes should now be configured to see each other. Run crm status to check.

Stack: corosync
Current DC: haproxy01 (version 1.1.16-94ff4df) - partition with quorum
Last updated: Sat Feb  1 14:41:09 2020
Last change: Sat Feb  1 14:40:51 2020 by hacluster via crmd on haproxy01

2 nodes configured
0 resources configured

Online: [ haproxy01 haproxy02 ]

No resources

Nodes

Do not kill the other node. This is needed as inactive nodes normally should be killed. It can be change later on, but only after fencing has been configured.

crm configure property stonith-enabled=false

Disable quorum due to two nodes only. This will make sure that the cluster keeps running if only one node is up.

crm configure property no-quorum-policy=ignore

Configure shared IP-address for apache. This is the virtual IP-address shared by apache servers.

crm configure primitive wwwSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.51 cidr_netmask=24 op monitor interval=5s

Configure shared IP-address for mariadb. This is the virtual IP-address shared by the galera cluster.

crm configure primitive mariadbSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.54 cidr_netmask=24 op monitor interval=5s

Configure shared IP-address for redis. This is the virtual IP-address shared by the redis master/replicas.

crm configure primitive redisSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.54 cidr_netmask=24 op monitor interval=5s

Create heartbeat for haproxy.

crm configure primitive LoadBalance ocf:heartbeat:haproxy params conffile=/etc/haproxy/haproxy.cfg op monitor interval=10s

Make sure the same server has both IP and service at the same time.

crm configure group services wwwSharedIP mariadbSharedIP redisSharedIP LoadBalance

IP-address should be up before haproxy starts.

crm configure order haproxyAfterIP mandatory: wwwSharedIP mariadbSharedIP redisSharedIP LoadBalance

Test it

Apache

while true; do wget --quiet http://www/ -O /dev/stdout; sleep 1; done

Mariadb

while true; do mysql -u haproxy -p -h mariadb -e "select @@hostname"; sleep 1; done

References

• https://wiki.debian.org/Debian-HA/ClustersFromScratch

• https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-cluster-options.html

• https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-corosync-pacemaker-and-floating-ips-on-ubuntu-14-04

• https://www.howtoforge.com/tutorial/how-to-setup-haproxy-as-load-balancer-for-mariadb-on-centos-7/#b-install-mariadb-galera-server

• https://www.digitalocean.com/community/tutorials/how-to-use-haproxy-to-set-up-mysql-load-balancing--3