From 86805ba4ba122b081c10edcd0a70462b93960e64 Mon Sep 17 00:00:00 2001 From: Tahlia Richardson <3069029+tahliar@users.noreply.github.com> Date: Fri, 16 Aug 2024 10:00:17 +1000 Subject: [PATCH] Improve the DRBD workflow to be easier to follow (#408) jsc#DOCTEAM-976 --- xml/ha_drbd.xml | 140 +++++++++++++++++++++++++++++------------------- 1 file changed, 86 insertions(+), 54 deletions(-) diff --git a/xml/ha_drbd.xml b/xml/ha_drbd.xml index 9838e002..a969a989 100644 --- a/xml/ha_drbd.xml +++ b/xml/ha_drbd.xml @@ -169,7 +169,7 @@ NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE - Setting up DRBD service + Setting up the DRBD service Adjustments needed @@ -185,15 +185,57 @@ NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE use an LV instead;band eg. "nfs" instead of "r0". - The following sections assumes you have two nodes, &node1; - and &node2;, and that they should use the TCP port 7788. + The following sections assume that the cluster nodes use the TCP port 7788. Make sure this port is open in your firewall. - - - Prepare your system: - + + Procedure overview + + To set up DRBD, perform the following procedures: + + + + + + + + + Configure DRBD using one of the following methods: + + + + + + + + + + + + + + + + + + + + + + + + + + + + Preparing your system to use DRBD + + Before you start configuring DRBD, you might need to perform some or + all of the following steps: + + + Preparing your system to use DRBD Make sure the block devices in your Linux nodes are ready and partitioned (if needed). @@ -214,49 +256,13 @@ NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE &prompt.root;crm maintenance on If you skip this step when your cluster already uses DRBD, a syntax error in the live configuration leads - to a service shutdown. - As an alternative, you can also use - drbdadm - to - test a configuration file. + to a service shutdown. + Alternatively, you can also use + drbdadm -c FILE + to test a configuration file. - - - - Configure DRBD by choosing your method: - - - - - - - - - - - - If you have configured &csync; (which should be the default), the - DRBD configuration files are already included in the list of files that - need to be synchronized. To synchronize them, run the following command: - - &prompt.root;csync2 -xv - - If you do not have &csync; (or do not want to use it), copy the DRBD - configuration files manually to the other node: - - &prompt.root;scp /etc/drbd.conf &node2;:/etc/ -&prompt.root;scp /etc/drbd.d/* &node2;:/etc/drbd.d/ - - - Perform the initial synchronization (see ). - - - - Reset the cluster's maintenance mode flag: - - &prompt.root;crm maintenance off - - + + Configuring DRBD manually @@ -432,8 +438,16 @@ NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE &prompt.root;drbdadm dump all - - Continue with . + + + Copy the DRBD configuration files to all nodes: + + &prompt.root;csync2 -xv + + By default, the DRBD configuration file /etc/drbd.conf + and the directory /etc/drbd.d/ are already included in the list + of files that &csync; synchronizes. + @@ -701,13 +715,21 @@ NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE Save your changes with Finish. - - Continue with . + + + Copy the DRBD configuration files to all nodes: + + &prompt.root;csync2 -xv + + By default, the DRBD configuration file /etc/drbd.conf + and the directory /etc/drbd.d/ are already included in the list + of files that &csync; synchronizes. + - Initializing and formatting DRBD resource + Initializing and formatting DRBD resources After you have prepared your system and configured DRBD, initialize your disk for the first time: @@ -807,7 +829,17 @@ r0 role:Primary &prompt.crm.conf;commit + + + Exit the interactive shell: + +&prompt.crm.conf;quit + + + If you put the cluster in maintenance mode before configuring DRBD, you can now move + it back to normal operation with crm maintenance off. +