|
Size: 3944
Comment:
|
Size: 4570
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 23: | Line 23: |
| cluster_name: www | |
| Line 28: | 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 42: | Line 43: |
| Copy the configuration `/etc/corosync/corosync.conf` and the authkey `/etc/corosync/authkey` to the other host. | |
| Line 43: | Line 45: |
| Restart corosync to load the new configuration. | Restart corosync on both hosts to load the new configuration. |
| Line 47: | 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 54: | Line 73: |
| This has to be done on both hosts. | |
| Line 56: | Line 76: |
| Do not kill the other node. | Do not kill the other node. This is needed as inactive nodes normally should be killed. It can be change later on, once fencing has been configured. |
| Line 60: | Line 80: |
| Disable quorum due to two nodes only. | Disable quorum due to two nodes only. This will make sure that the cluster keeps running if only one node is up. |
| Line 64: | Line 84: |
| Configure shared IP-address. | Configure shared IP-address. This is the virtual IP-address. |
| Line 66: | Line 86: |
| crm configure primitive haproxy_wwwSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.49 cidr_netmask=24 op monitor interval=5s | crm configure primitive wwwSharedIP ocf:heartbeat:IPaddr2 params ip=192.168.1.49 cidr_netmask=24 op monitor interval=5s |
| Line 70: | Line 90: |
| crm configure primitive haproxy_wwwLoadBalance ocf:heartbeat:haproxy params conffile=/etc/haproxy/haproxy.cfg op monitor interval=10s | crm configure primitive wwwLoadBalance ocf:heartbeat:haproxy params conffile=/etc/haproxy/haproxy.cfg op monitor interval=10s |
| Line 74: | Line 94: |
| crm configure group haproxy_www haproxy_wwwSharedIP haproxy_wwwLoadBalance | crm configure group www wwwSharedIP wwwLoadBalance |
| Line 77: | Line 97: |
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) |
|
| Line 86: | Line 98: |
| crm configure colocation haproxyWithIPs INFINITY: haproxy_wwwLoadBalance haproxy_wwwSharedIP | crm configure colocation haproxyWithIPs INFINITY: wwwLoadBalance wwwSharedIP |
| Line 90: | Line 102: |
| crm configure order haproxyAfterIPs mandatory: haproxy_wwwSharedIP haproxy_wwwLoadBalance | crm configure order haproxyAfterIP mandatory: wwwSharedIP wwwLoadBalance |
| Line 93: | Line 105: |
| === HA-proxy === | ==== Webfarm ==== |
| Line 106: | Line 118: |
| Copy the configuration `/etc/haproxy/haproxy.cfg` to the other host. | |
| Line 107: | Line 120: |
| Restart HA-proxy | Restart HA-proxy on both hosts to load the new configuration. |
| Line 119: | Line 132: |
| * https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-cluster-options.html |
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.
Nodes
Do not kill the other node. This is needed as inactive nodes normally should be killed. It 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.
crm configure colocation haproxyWithIPs INFINITY: wwwLoadBalance wwwSharedIP
IP-address should be up before haproxy starts.
crm configure order haproxyAfterIP mandatory: wwwSharedIP wwwLoadBalance
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.
Restart HA-proxy on both hosts to load the new configuration.
service haproxy restart
Test it
while true; do wget --quiet http://www/ -O /dev/stdout; sleep 1; done