Topic: Distributed Replicated Block Device (DRBD) on SME8 ?

[fpausp]

I would like to use drbd on sme8, can anyone tell me how to install and maybe configure drbd on sme8 ?

regards
fpausp

[Jean-Philippe Pialasse]

as SME8 is based on centos 5 , this how to should do the trick : https://blogs.it.ox.ac.uk/jamest/2011/06/03/replicating-block-devices-with-drbd/

but I can suggest you to have a look to affa to sync two server, or some alternatives like heartbeat etc.

[fpausp]

Hi, thanks for your reply, I found alsa a nice howto:


http://www.sherin.co.in/drbd-heartbeat-active-passive-high-availability-cluster/


DRBD is working ... I need more time to finish the cluster ...

[janet]

fpausp

This old howto may be of historical interest
http://distro.ibiblio.org/smeserver/contribs/rmitchell/smeserver/howto/High%20Availability%20How-To%20for%20Linux%20Mitel%20SME%20v5.htm

[fpausp]

I try to do this on sme8:

http://wiki.centos.org/HowTos/Ha-Drbd


I use two virtual sme8 server with an additional hdd (/dev/vdb).


I started to write a howto, its just an early version v0.1 ...:

Code: [Select]

### sme8 cluster howto v.01 ###


# Install packages (on each host)

yum install drbd82 kmod-drbd82 --enablerepo=extras

yum install heartbeat --enablerepo=extras

signal-event post-upgrade; signal-event reboot


# ssh-keygen -t rsa

On each side ...

# copy the key to the other side

# on sme8test1
ssh-copy-id -i ~/.ssh/id_rsa.pub "root@10.10.10.110 -p 11022"


# on sme8test2
ssh-copy-id -i ~/.ssh/id_rsa.pub "root@10.10.10.109 -p 11022"



Test connection with:

ssh -p 11022 root@10.10.10.110

and vice versa ...

ssh -p 11022 root@10.10.10.109



# create template (on each host)

mkdir -p /etc/e-smith/templates-custom/etc/hosts

nano /etc/e-smith/templates-custom/etc/hosts/30hosts



# on sme8test1
10.10.10.110   sme8test2.mydomain.at sme8test2

# on sme8test2
10.10.10.109   sme8test1.mydomain.at sme8test1



# expand template (on each host)

/sbin/e-smith/expand-template /etc/hosts




# configure drbd

nano /etc/drbd.conf

resource r0 {
protocol      C;

on sme8test1 {
device /dev/drbd1;
disk /dev/vdb1;
address 10.10.10.109:7789;
meta-disk internal;
}
on sme8test2 {
device /dev/drbd1;
disk /dev/vdb1;
address 10.10.10.110:7789;
meta-disk internal;
}
}


# create a primary partition on /dev/vdb
fdisk /dev/vdb


# create resource
drbdadm create-md r0



# start drbd service
/etc/init.d/drbd start





nano /etc/rc.d/rc.local

Add the following line to the end of the file
/etc/rc.d/init.d/drbd start



# chose a server as master (sme8test1), and start replication
drbdadm -- --overwrite-data-of-peer primary r0



# temporary speedup sync (680 for virtual lan)
drbdsetup /dev/drbd1 syncer -r 680M



# make mountpoint on each side
mkdir -p /media/drbd


# we can now format /dev/drbd1 and mount it on sme8test1:
mke2fs -j /dev/drbd1 ; mkdir /media/drbd ; mount /dev/drbd1 /media/drbd



# create a testfile
touch /media/drbd/testfile-sme8test1.txt



# umount and make sme8sme1 secondary
umount /media/drbd
drbdadm secondary r0



# on sme8test2
drbdadm primary r0
mount /dev/drbd1 /media/drbd


# take a look
ls -alih /media/drbd


# write testfile on sme8test2
touch /media/drbd/testfile-sme8test2.txt


# lets switch back to sme8test1, umount drbd and make sme8sme2 secondary
umount /media/drbd
drbdadm secondary r0


# on sme8test1
drbdadm primary r0
mount /dev/drbd1 /media/drbd


# take a look
ls -alih /media/drbd



# start drbd service on boot (on each server)
config setprop drbd status enabled
signal-event post-upgrade;signal-event reboot




### Heartbeat V2 Configuration ###


# Let's configure a simple /etc/ha.d/ha.cf file

nano /etc/ha.d/ha.cf


keepalive 2
deadtime 30
warntime 10
initdead 120
bcast   eth0
node sme8test1
node sme8test2
crm yes


# Create also the /etc/ha.d/authkeys

auth 1
1 sha1 MySecret

# give permission 600
chmod 600 /etc/ha.d/authkeys


# start heartbeat service on sme8test1
/etc/init.d/heartbeat start


# Replicate now the ha.cf and authkeys to sme8test2
scp -P 11022 /etc/ha.d/ha.cf /etc/ha.d/authkeys root@sme8test2:/etc/ha.d/


# start heartbeat service on sme8test2
/etc/init.d/heartbeat start


# Verify cluster with crm_mon
crm_mon



# create a resource group with an ip-address, the drbd-device and filesystem mount operation

# edit cib.xml
nano /var/lib/heartbeat/crm.xml


?????????????????????????????


nano /etc/rc.d/rc.local

Add the following line to the end of the file
/etc/rc.d/init.d/heartbeat start


Maybe someone can help me to finish the howto (cib.xml) ?

[newburns]

I'll join with you. But I won't be able to test your howto until later this week.

[fpausp]

OK, I have made a new one (v0.2) ...

DRBD is working, what is left is the cib (cluster information base) and the test of the ha-cluster.

SME8 Ha-Drbd Howto v0.2:

Code: [Select]

### sme8 ha-drbd howto v0.2 ###



# Preparation, two SME8-Server with additional hdd for drbd:
node1 - sme8test1 - 10.10.10.109
node2 - sme8test2 - 10.10.10.110



### Installation ###


# Install packages (on each node)
yum -y install drbd82 kmod-drbd82 --enablerepo=extras; \
yum -y install heartbeat --enablerepo=extras


# Generate public-key (on each node)
ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa


# copy the key to the other side on node1 (sme8test1)
ssh-copy-id -i ~/.ssh/id_rsa.pub "root@10.10.10.110 -p 11022"


# copy the key to the other side on node2 (sme8test2)
ssh-copy-id -i ~/.ssh/id_rsa.pub "root@10.10.10.109 -p 11022"


# Test connection on node1 (sme8test1)
ssh -p 11022 root@10.10.10.110


# Test connection on node2 (sme8test2)
ssh -p 11022 root@10.10.10.109


# create template on node1 (sme8test1)
mkdir -p /etc/e-smith/templates-custom/etc/hosts
nano /etc/e-smith/templates-custom/etc/hosts/30hosts

----------------------- content of 30hosts -----------------------
10.10.10.110   sme8test2.mydomain.at sme8test2
----------------------- content of 30hosts -----------------------


# create template on node2 (sme8test2)
mkdir -p /etc/e-smith/templates-custom/etc/hosts
nano /etc/e-smith/templates-custom/etc/hosts/30hosts

----------------------- content of 30hosts -----------------------
10.10.10.109   sme8test1.mydomain.at sme8test1
----------------------- content of 30hosts -----------------------


# expand template (on each node)
/sbin/e-smith/expand-template /etc/hosts



### DRBD Configuration ###


# configure drbd (on each node)

nano /etc/drbd.conf

----------------------- content of drbd.conf -----------------------
resource r0 {
protocol      C;

on sme8test1 {
device /dev/drbd1;
disk /dev/vdb1;
address 10.10.10.109:7789;
meta-disk internal;
}
on sme8test2 {
device /dev/drbd1;
disk /dev/vdb1;
address 10.10.10.110:7789;
meta-disk internal;
}
}
----------------------- content of drbd.conf -----------------------



# create a primary partition on the additional hdd (on each node)
fdisk /dev/vdb


# create resource (on each node)
drbdadm create-md r0


# start drbd service (on each node)
/etc/init.d/drbd start


# chose a server as Primary - node1 (sme8test1), and start replication
drbdadm -- --overwrite-data-of-peer primary r0


# temporary speedup replication (680 for virtual lan)
drbdsetup /dev/drbd1 syncer -r 680M


# watch replication (on each node)
cat /proc/drbd


# create mountpoint (on each node)
mkdir -p /media/drbd


# we can now format /dev/drbd1 and mount it on node1 (sme8test1)
mke2fs -j /dev/drbd1 ; mount /dev/drbd1 /media/drbd


# create a testfile on node1 (sme8test1)
touch /media/drbd/testfile-1.txt


# umount drbd on node1 (sme8test1) and make node1 (sme8test1) secondary
umount /media/drbd
drbdadm secondary r0


# make sme8test2 primary and mount drbd on node2 (sme8test2)
drbdadm primary r0
mount /dev/drbd1 /media/drbd


# create a testfile on node2 (sme8test2)
touch /media/drbd/testfile-2.txt


# umount drbd and make sme8sme2 secondary again on node2 (sme8test2)
umount /media/drbd
drbdadm secondary r0


# finaly make sme8test1 primary again and mount drbd on node1 (sme8test1)
drbdadm primary r0
mount /dev/drbd1 /media/drbd


# take a look on node1 (sme8test1) if the two testfiles are there
ls -alih /media/drbd


# make sure that drbd starts on boot (on each node)
ln -s /etc/rc.d/init.d/drbd /etc/rc7.d/K36drbd ; \
ln -s /etc/rc.d/init.d/drbd /etc/rc7.d/S98drbd


# reboot and test if the service start on boot
reboot


### Heartbeat V2 Configuration ###


# Let's configure a simple /etc/ha.d/ha.cf file on node1 (sme8test1)

nano /etc/ha.d/ha.cf

----------------------- content of ha.cf -----------------------
keepalive 2
deadtime 30
warntime 10
initdead 120
bcast   eth0
node sme8test1
node sme8test2
crm yes
----------------------- content of ha.cf -----------------------


# Create also the /etc/ha.d/authkeys on node1 (sme8test1)

nano /etc/ha.d/authkeys

----------------------- content of authkeys -----------------------
auth 1
1 sha1 MySecret
----------------------- content of authkeys -----------------------


# give permission 600 on node1 (sme8test1)
chmod 600 /etc/ha.d/authkeys


# start heartbeat service on node1 (sme8test1)
/etc/init.d/heartbeat start


# Replicate now the ha.cf and authkeys to node2 (sme8test2)
scp -P 11022 /etc/ha.d/ha.cf /etc/ha.d/authkeys root@sme8test2:/etc/ha.d/


# start heartbeat service on node2 (sme8test2)
/etc/init.d/heartbeat start


# Verify cluster with crm_mon on node2 (sme8test2)
crm_mon


# create resourcefile on node1 (sme8test1)
nano /var/lib/heartbeat/myCluster.xml

---------------------------- content of myCluster.xml -----------------------------
<primitive id="IP-Addr" class="ocf" type="IPaddr2" provider="heartbeat">
           <instance_attributes id="IP-Addr_instance_attrs">
             <attributes>
               <nvpair id="IP-Addr_target_role" name="target_role" value="started"/>
               <nvpair id="2e967596-73fe-444e-82ea-18f61f3848d7" name="ip" value="10.10.10.222"/>
             </attributes>
           </instance_attributes>
         </primitive>
         <instance_attributes id="My-DRBD-group_instance_attrs">
           <attributes>
             <nvpair id="My-DRBD-group_target_role" name="target_role" value="started"/>
           </attributes>
         </instance_attributes>
         <primitive id="DRBD_data" class="heartbeat" type="drbddisk" provider="heartbeat">
           <instance_attributes id="DRBD_data_instance_attrs">
             <attributes>
               <nvpair id="DRBD_data_target_role" name="target_role" value="started"/>
               <nvpair id="93d753a8-e69a-4ea5-a73d-ab0d0367f001" name="1" value="/media/drbd"/>
             </attributes>
           </instance_attributes>
         </primitive>
         <primitive id="FS_repdata" class="ocf" type="Filesystem" provider="heartbeat">
           <instance_attributes id="FS_repdata_instance_attrs">
             <attributes>
               <nvpair id="FS_repdata_target_role" name="target_role" value="started"/>
               <nvpair id="96d659dd-0881-46df-86af-d2ec3854a73f" name="fstype" value="ext3"/>
               <nvpair id="8a150609-e5cb-4a75-99af-059ddbfbc635" name="device" value="/dev/drbd1"/>
               <nvpair id="de9706e8-7dfb-4505-b623-5f316b1920a3" name="directory" value="/media/drbd"/>
             </attributes>
           </instance_attributes>
         </primitive>
---------------------------- content of myCluster.xml -----------------------------


# add resource to the cluster on node1 (sme8test1)
cibadmin -C -o resources -x /var/lib/heartbeat/myCluster.xml


# make sure that heartbeat starts on boot (on each node)
ln -s /etc/rc.d/init.d/heartbeat /etc/rc7.d/K35heartbeat ; \
ln -s /etc/rc.d/init.d/heartbeat /etc/rc7.d/S99heartbeat



### Test the HA-DRBD Cluster ###


???????????????????????????????????????????????????????????????