|
Size: 3422
Comment:
|
Size: 4948
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Incomplete, do not use! |
|
| Line 7: | Line 5: |
| * 192.168.1.47 www (virtual IP-address) * 192.168.1.48 haproxy01 * 192.168.1.49 haproxy02 |
* 192.168.1.49 www (virtual IP-address) * 192.168.1.50 haproxy01 * 192.168.1.51 haproxy02 |
| Line 25: | Line 23: |
| cluster_name: www | |
| Line 30: | Line 29: |
| ==== Certificates ==== Generate the certificates. 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. |
==== 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. |
| Line 44: | Line 43: |
| Copy the configuration `/etc/corosync/corosync.conf` and the authkey `/etc/corosync/authkey` to the other host. | |
| Line 45: | Line 45: |
| Restart corosync to load the new configuration. | Restart corosync on both hosts to load the new configuration. |
| Line 49: | Line 49: |
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 }}} === HA-proxy === |
|
| Line 56: | Line 73: |
| This has to be done on both hosts. | |
| Line 57: | Line 75: |
| ==== Nodes ==== Do not kill the other node. {{{ crm configure property stonith-enabled=false }}} Disable quorum due to two nodes only. {{{ crm configure property no-quorum-policy=ignore }}} Configure shared IP-address. {{{ crm configure primitive haproxySharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.47 cidr_netmask=24 op monitor interval=5s }}} Create heartbeat for haproxy. {{{ crm configure primitive haproxyLoadBalance 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 haproxy haproxySharedIP haproxyLoadBalance }}} Create the relation between IP-address and haproxy servers. {{{ crm configure colocation haproxyWithIPs INFINITY: haproxyLoadBalance haproxySharedIP }}} IP-address should be up before haproxy starts. {{{ crm configure order haproxyAfterIPs mandatory: haproxySharedIP haproxyLoadBalance }}} === HA-proxy === |
==== Webfarm ==== |
| Line 100: | Line 88: |
| Copy the configuration `/etc/haproxy/haproxy.cfg` to the other host. | |
| Line 101: | Line 90: |
| Restart HA-proxy | ==== Nodes ==== Do not kill the other node. This can be change later on, once 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. This is the virtual IP-address. {{{ crm configure primitive wwwSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.49 cidr_netmask=24 op monitor interval=5s }}} Create heartbeat for haproxy. {{{ crm configure primitive wwwLoadBalance 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 www wwwSharedIP wwwLoadBalance }}} Create the relation between IP-address and haproxy servers. This is important, as it prevents both haproxy servers from listening on the virtual IP at the same time. currently gives: root@haproxy01:/etc/corosync# crm configure colocation haproxyWithIPs INFINITY: haproxy_wwwLoadBalance haproxy_wwwSharedIP WARNING: haproxyWithIPs: resource haproxy_wwwLoadBalance is grouped, constraints should apply to the group WARNING: haproxyWithIPs: resource haproxy_wwwSharedIP is grouped, constraints should apply to the group) {{{ crm configure colocation haproxyWithIPs INFINITY: wwwLoadBalance wwwSharedIP }}} IP-address should be up before haproxy starts. {{{ crm configure order haproxyAfterIPs mandatory: wwwSharedIP wwwLoadBalance }}} Restart HA-proxy on both hosts to load the new configuration. |
| Line 105: | Line 132: |
==== Start over ==== run this `rm /var/lib/heartbeat/pacemaker/cib*` |
|
| Line 113: | Line 144: |
| * https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-corosync-pacemaker-and-floating-ips-on-ubuntu-14-04 |
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.49 www (virtual IP-address)
- 192.168.1.50 haproxy01
- 192.168.1.51 haproxy02
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.
Corosync
Encryption
Edit /etc/corosync/corosync.conf and make the following changes.
totem {
cluster_name: www
crypto_cipher: aes256
crypto_hash: sha512
}
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.
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
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
This has to be done on both hosts.
Webfarm
Add the following to /etc/haproxy/haproxy.cfg
listen webfarm
bind www:80
mode http
balance roundrobin
cookie LBN insert indirect nocache
option httpclose
option forwardfor
server haproxy01 www01:80 cookie node1 check
server haproxy02 www02:80 cookie node2 checkCopy the configuration /etc/haproxy/haproxy.cfg to the other host.
Nodes
Do not kill the other node. This can be change later on, once 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. This is the virtual IP-address.
crm configure primitive wwwSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.49 cidr_netmask=24 op monitor interval=5s
Create heartbeat for haproxy.
crm configure primitive wwwLoadBalance 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 www wwwSharedIP wwwLoadBalance
Create the relation between IP-address and haproxy servers. This is important, as it prevents both haproxy servers from listening on the virtual IP at the same time.
currently gives: root@haproxy01:/etc/corosync# crm configure colocation haproxyWithIPs INFINITY: haproxy_wwwLoadBalance haproxy_wwwSharedIP
WARNING: haproxyWithIPs: resource haproxy_wwwLoadBalance is grouped, constraints should apply to the group
WARNING: haproxyWithIPs: resource haproxy_wwwSharedIP is grouped, constraints should apply to the group)
crm configure colocation haproxyWithIPs INFINITY: wwwLoadBalance wwwSharedIP
IP-address should be up before haproxy starts.
crm configure order haproxyAfterIPs mandatory: wwwSharedIP wwwLoadBalance
Restart HA-proxy on both hosts to load the new configuration.
service haproxy restart
Start over
run this rm /var/lib/heartbeat/pacemaker/cib*
Test it
while true; do wget --quiet http://www/ -O /dev/stdout; sleep 1; done