29.2. Configuring multi-site clusters with Pacemaker

Procedure

1. Install the booth-site Booth ticket manager package on each node of both clusters.

   [root@cluster1-node1 ~]# dnf install -y booth-site
   [root@cluster1-node2 ~]# dnf install -y booth-site
   [root@cluster2-node1 ~]# dnf install -y booth-site
   [root@cluster2-node2 ~]# dnf install -y booth-site

2. Install the pcs, booth-core, and booth-arbitrator packages on the arbitrator node.

   [root@arbitrator-node ~]# dnf install -y pcs booth-core booth-arbitrator

3. If you are running the firewalld daemon, execute the following commands on all nodes in both clusters as well as on the arbitrator node to enable the ports that are required by the Red Hat High Availability Add-On.

   # firewall-cmd --permanent --add-service=high-availability
   # firewall-cmd --add-service=high-availability

   You may need to modify which ports are open to suit local conditions. For more information about the ports that are required by the Red Hat High-Availability Add-On, see Enabling ports for the High Availability Add-On.

4. Create a Booth configuration on one node of one cluster. The addresses you specify for each cluster and for the arbitrator must be IP addresses. For each cluster, you specify a floating IP address.

   [cluster1-node1 ~] # pcs booth setup sites 192.168.11.100 192.168.22.100 arbitrators 192.168.99.100

   This command creates the configuration files /etc/booth/booth.conf and /etc/booth/booth.key on the node from which it is run.

5. Create a ticket for the Booth configuration. This is the ticket that you will use to define the resource constraint that will allow resources to run only when this ticket has been granted to the cluster.

   This basic failover configuration procedure uses only one ticket, but you can create additional tickets for more complicated scenarios where each ticket is associated with a different resource or resources.

   [cluster1-node1 ~] # pcs booth ticket add apacheticket

6. Synchronize the Booth configuration to all nodes in the current cluster.

   [cluster1-node1 ~] # pcs booth sync

7. From the arbitrator node, pull the Booth configuration to the arbitrator. If you have not previously done so, you must first authenticate pcs to the node from which you are pulling the configuration.

   [arbitrator-node ~] # pcs host auth cluster1-node1
   [arbitrator-node ~] # pcs booth pull cluster1-node1

8. Pull the Booth configuration to the other cluster and synchronize to all the nodes of that cluster. As with the arbitrator node, if you have not previously done so, you must first authenticate pcs to the node from which you are pulling the configuration.

   [cluster2-node1 ~] # pcs host auth cluster1-node1
   [cluster2-node1 ~] # pcs booth pull cluster1-node1
   [cluster2-node1 ~] # pcs booth sync

9. Start and enable Booth on the arbitrator.

   注意

   You must not manually start or enable Booth on any of the nodes of the clusters since Booth runs as a Pacemaker resource in those clusters.

   [arbitrator-node ~] # pcs booth start
   [arbitrator-node ~] # pcs booth enable

10. Configure Booth to run as a cluster resource on both cluster sites, using the floating IP addresses assigned to each cluster. This creates a resource group with booth-ip and booth-service as members of that group.

    [cluster1-node1 ~] # pcs booth create ip 192.168.11.100
    [cluster2-node1 ~] # pcs booth create ip 192.168.22.100

11. Add a ticket constraint to the resource group you have defined for each cluster.

    [cluster1-node1 ~] # pcs constraint ticket add apacheticket apachegroup
    [cluster2-node1 ~] # pcs constraint ticket add apacheticket apachegroup

    You can enter the following command to display the currently configured ticket constraints.

    pcs constraint ticket [config]

12. Grant the ticket you created for this setup to the first cluster.

    Note that it is not necessary to have defined ticket constraints before granting a ticket. Once you have initially granted a ticket to a cluster, then Booth takes over ticket management unless you override this manually with the pcs booth ticket revoke command. For information about the pcs booth administration commands, use the pcs booth --help command on your system.

    [cluster1-node1 ~] # pcs booth ticket grant apacheticket

    It is possible to add or remove tickets at any time, even after completing this procedure. After adding or removing a ticket, however, you must synchronize the configuration files to the other nodes and clusters as well as to the arbitrator and grant the ticket as is shown in this procedure.

    For a full procedure to remove a Booth ticket, see Removing a Booth ticket. For information about additional Booth administration commands, use the pcs booth --help command.