Product SiteDocumentation Site

Chapter 8. Conversion to Active/Active

Table of Contents

8.1. Requirements
8.2. Adding CMAN Support
8.2.1. Installing the required Software
8.2.2. Configuring CMAN
8.2.3. Redundant Rings
8.2.4. Configuring CMAN Fencing
8.2.5. Bringing the Cluster Online with CMAN
8.3. Create a GFS2 Filesystem
8.3.1. Preparation
8.3.2. Create and Populate an GFS2 Partition
8.4. Reconfigure the Cluster for GFS2
8.5. Reconfigure Pacemaker for Active/Active
8.5.1. Testing Recovery

8.1. Requirements

The primary requirement for an Active/Active cluster is that the data required for your services is available, simultaneously, on both machines. Pacemaker makes no requirement on how this is achieved, you could use a SAN if you had one available, however since DRBD supports multiple Primaries, we can also use that.
The only hitch is that we need to use a cluster-aware filesystem. The one we used earlier with DRBD, ext4, is not one of those. Both OCFS2 and GFS2 are supported, however here we will use GFS2 which comes with Fedora.
We’ll also need to use CMAN for Cluster Membership and Quorum instead of our Corosync plugin.