DRBD is actually one of the most difficult resources to manage with Pacemaker. Unlike a regular service that is started or stopped depending on where it is active, DRBD is always active. The only thing that changes between two nodes running DRBD is the
Secondary state ascribed to each.
Due to this complication, DRBD is not one resource, but two:
- A DRBD resource to manage starting and stopping DRBD
- A master/slave resource to control which node acts as the
In this recipe, we'll allocate both of these resources so that Pacemaker can manage DRBD properly.
As we're continuing to configure Pacemaker, make sure you've followed all previous recipes.