4.7. Configuring the load balancer resource agent
After creating the health probe, you must configure the load balancer resource agent. This resource agent runs a service that responds health probe requests from the Azure load balancer and removes cluster nodes that do not respond requests.
Prerequisites
- You have completed the process of creating an Azure load balancer.
Procedure
Install the
nmap-ncatresource agents on all nodes:# dnf install nmap-ncat resource-agents-cloudPerform the following steps on a single node:
Create the
pcsresources and group by using theFrontendIPload balancer for theIPaddr2address:# pcs resource create resource-name IPaddr2 ip="10.0.0.7" --group <cluster_resources_group>Configure the
load balancerresource agent:# pcs resource create resource-loadbalancer-name azure-lb port=port-number --group <cluster_resources_group>
Verification
Run
pcs statusto see the results.[root@node01 clouduser]# pcs status Cluster name: clusterfence01 Stack: corosync Current DC: node02 (version 1.1.16-12.el7_4.7-94ff4df) - partition with quorum Last updated: Tue Jan 30 12:42:35 2018 Last change: Tue Jan 30 12:26:42 2018 by root via cibadmin on node01 3 nodes configured 3 resources configured Online: [ node01 node02 node03 ] Full list of resources: clusterfence (stonith:fence_azure_arm): Started node01 Resource Group: g_azure vip_azure (ocf::heartbeat:IPaddr2): Started node02 lb_azure (ocf::heartbeat:azure-lb): Started node02 Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled