4.1 - Example Topology
In this example, we have two servers: romulus
and three ZFS pools. The ZFS pools (POOLA, POOLB and POOLC) have all been created on top of the underlying shared storage and both servers have the capability to import and export them.
We are going to use two network heartbeats: one private (shown below as a red dotted line) and one public (shown in orange). We'll also use three independent disk heartbeats, one per ZFS pool, (shown as black dotted lines).
The system hostnames and identities on the public network are romulus
respectively, and romulus_priv
respectively on the private network.
Let's assume we want to set up an Active/Active cluster configuration with two RSF-1 Services, the first (which we'll call POOLA
) consisting of ZFS pools A and C, and the second (called POOLB
) just ZFS pool B.
For service POOLA
, we'll associate the VIP sales_staff-public
and for service POOLB
, we'll use support_staff-public
. User access to ZFS pools A and C is therefore via the sales_staff-public
VIP address, and access to ZFS pool B via the support_staff-public
NOTE - When the POOLA service is failed over between servers, both ZFS pools A and C and the VIP sales_staff-public will migrate as part of that service. When POOLB service is failed over, only pool B is moved together with the support_staff-public VIP.
Before we start to configure RSF-1, we need to ensure the ZFS pools can be successfully imported and exported between the two servers.