diff --git a/xml/ha_drbd.xml b/xml/ha_drbd.xml index 4a06c2d8..08a693f9 100644 --- a/xml/ha_drbd.xml +++ b/xml/ha_drbd.xml @@ -174,7 +174,7 @@ NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE Adjustments Needed The following procedure uses the server names &node1; and &node2;, - and the cluster resource name r0. It sets up + and the DRBD resource name r0. It sets up &node1; as the primary node and /dev/disk/by-id/example-disk1 for storage. Make sure to modify the instructions to use your own nodes and file names. @@ -742,6 +742,45 @@ r0 role:Primary + + Creating Cluster Resources for DRBD + + After you have initialized your DRBD device, create a cluster resource to manage + the DRBD device, and a promotable clone to allow this resource to run on both nodes: + + + Creating cluster resources for DRBD + + + Start the crm interactive shell: + +&prompt.root;crm configure + + + + Create a primitive for the DRBD resource r0: + +&prompt.crm.conf;primitive drbd-r0 ocf:linbit:drbd \ + params drbd_resource="r0" \ + op monitor interval=15 role=Master \ + op monitor interval=30 role=Slave + + + + Create a promotable clone for the drbd-r0 primitive: + +&prompt.crm.conf;ms ms-drbd-r0 drbd-r0 \ + meta master-max="1" master-node-max="1" \ + clone-max="2" clone-node-max="1" notify="true" interleave=true + + + + Commit this configuration: + +&prompt.crm.conf;commit + + +