環境說明:
作業系統: centos 6.6 x64,本文采用rpm方式安裝corosync+pacemaker+drbd+nfs。
[root@app1 soft]# vi /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.0.24 app1
192.168.0.25 app2
10.10.10.24 app1-priv
10.10.10.25 app2-priv
說明：10段是心跳ip, 192.168段是業務ip, 采用vip位址是192.168.0.26。
sed -i '/selinux/s/enforcing/disabled/' /etc/selinux/config
setenforce 0
chkconfig iptables off
service iptables stop
app1:
[root@app1 ~]# ssh-keygen -t rsa -f ~/.ssh/id_rsa -p ''
[root@app1 ~]# ssh-copy-id -i .ssh/id_rsa.pub root@app2
app2:
[root@app2 ~]# ssh-keygen -t rsa -f ~/.ssh/id_rsa -p ''
[root@app2 ~]# ssh-copy-id -i .ssh/id_rsa.pub root@app1
app1: /dev/sdb1 —> app2: /dev/sdb1
(1) 下載下傳drbd安裝包, centos6.6采用kmod-drbd84-8.4.5-504.1安裝包才可用。
<a href="http://rpm.pbone.net/" target="_blank">http://rpm.pbone.net/</a>
drbd84-utils-8.9.1-1.el6.elrepo.x86_64.rpm
kmod-drbd84-8.4.5-504.1.el6.x86_64.rpm
# rpm -ivh drbd84-utils-8.9.5-1.el6.elrepo.x86_64.rpm kmod-drbd84-8.4.5-504.1.el6.x86_64.rpm
preparing... ########################################### [100%]
1:drbd84-utils ########################################### [ 50%]
2:kmod-drbd84 ########################################### [100%]
working. this may take some time ...
done.
#
(2) 加載drbd到核心子產品
app1,app2分别操作，并加入到/etc/rc.local檔案中。
modprobe drbd
lsmode |grep drbd
[root@app1 ~]# vi /etc/drbd.d/global_common.conf
global {
usage-count no;
}
common {
protocol c;
disk {
on-io-error detach;
no-disk-flushes;
no-md-flushes;
}
net {
sndbuf-size 512k;
max-buffers 8000;
unplug-watermark 1024;
max-epoch-size 8000;
cram-hmac-alg "sha1";
shared-secret "hdhwxes23syehart8t";
after-sb-0pri disconnect;
after-sb-1pri disconnect;
after-sb-2pri disconnect;
rr-conflict disconnect;
syncer {
rate 300m;
al-extents 517;
}
resource data {
on app1 {
device /dev/drbd0;
disk /dev/sdb1;
address 10.10.10.24:7788;
meta-disk internal;
}
on app2 {
device /dev/drbd0;
disk /dev/sdb1;
address 10.10.10.25:7788;
在app1和app2上分别執行：
# drbdadm create-md data
initializing activity log
not initializing bitmap
writing meta data...
new drbd meta data block successfully created.
在app1和app2上分别執行：或采用 drbdadm up data
# service drbd start
starting drbd resources: [
create res: data
prepare disk: data
adjust disk: data
adjust net: data
]
..........
cat /proc/drbd #或者直接使用指令drbd-overview
節點1:
[root@app1 drbd.d]# cat /proc/drbd
version: 8.4.5 (api:1/proto:86-101)
git-hash: 1d360bde0e095d495786eaeb2a1ac76888e4db96 build by [email protected], 2015-01-02 12:06:20
0: cs:connected ro:secondary/secondary ds:inconsistent/inconsistent c r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:20964116
節點2:
[root@app2 drbd.d]# cat /proc/drbd
我們需要将其中一個節點設定為primary，在要設定為primary的節點上執行如下兩條指令均可：
drbdadm -- --overwrite-data-of-peer primary data
主節點檢視同步狀态：
0: cs:syncsource ro:primary/secondary ds:uptodate/inconsistent c r-----
ns:1229428 nr:0 dw:0 dr:1230100 al:0 bm:0 lo:0 pe:2 ua:0 ap:0 ep:1 wo:d oos:19735828
[>...................] sync'ed: 5.9% (19272/20472)m
finish: 0:27:58 speed: 11,744 (11,808) k/sec
[root@app1 drbd.d]#
檔案系統的挂載隻能在primary節點進行，隻有在設定了主節點後才能對drbd裝置進行格式化, 格式化與手動挂載測試。
[root@app1 ~]# mkfs.ext4 /dev/drbd0
[root@app1 ~]# mount /dev/drbd0 /data
# vi /etc/exports
/data 192.168.0.0/24(rw,no_root_squash)
# service rpcbind start
# service nfs start
# chkconfig rpcbind on
# chkconfig nfs on
# yum install corosync pacemaker -y
rhel自6.4起不再提供叢集的指令行配置工具crmsh，要實作對叢集資源管理，還需要獨立安裝crmsh。
[root@app1 crm]# yum install python-dateutil -y
說明：python-pssh、pssh依懶于python-dateutil包
[root@app1 crm]# rpm -ivh pssh-2.3.1-4.2.x86_64.rpm python-pssh-2.3.1-4.2.x86_64.rpm crmsh-2.1-1.6.x86_64.rpm
warning: pssh-2.3.1-4.2.x86_64.rpm: header v3 rsa/sha1 signature, key id 17280ddf: nokey
1:python-pssh ########################################### [ 33%]
2:pssh ########################################### [ 67%]
3:crmsh ########################################### [100%]
[root@app1 crm]#
[root@app1 crm]#
cd /etc/corosync/
cp corosync.conf.example corosync.conf
vi /etc/corosync/corosync.conf
# please read the corosync.conf.5 manual page
compatibility: whitetank
totem {
version: 2
secauth: on
threads: 0
interface {
ringnumber: 0
bindnetaddr: 10.10.10.0
mcastaddr: 226.94.8.8
mcastport: 5405
ttl: 1
logging {
fileline: off
to_stderr: no
to_logfile: yes
to_syslog: no
logfile: /var/log/cluster/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: amf
debug: off
amf {
mode: disabled
service {
ver: 1
name: pacemaker
aisexec {
user: root
group: root
各節點之間通信需要安全認證，需要安全密鑰，生成後會自動儲存至目前目錄下，命名為authkey,權限為400。
[root@app1 corosync]# corosync-keygen
corosync cluster engine authentication key generator.
gathering 1024 bits for key from /dev/random.
press keys on your keyboard to generate entropy.
press keys on your keyboard to generate entropy (bits = 128).
press keys on your keyboard to generate entropy (bits = 192).
press keys on your keyboard to generate entropy (bits = 256).
press keys on your keyboard to generate entropy (bits = 320).
press keys on your keyboard to generate entropy (bits = 384).
press keys on your keyboard to generate entropy (bits = 448).
press keys on your keyboard to generate entropy (bits = 512).
press keys on your keyboard to generate entropy (bits = 576).
press keys on your keyboard to generate entropy (bits = 640).
press keys on your keyboard to generate entropy (bits = 704).
press keys on your keyboard to generate entropy (bits = 768).
press keys on your keyboard to generate entropy (bits = 832).
press keys on your keyboard to generate entropy (bits = 896).
press keys on your keyboard to generate entropy (bits = 960).
writing corosync key to /etc/corosync/authkey.
[root@app1 corosync]#
# scp authkeys corosync.conf root@app2:/etc/corosync/
節點1:
[root@app1 ~]# service corosync start
starting corosync cluster engine (corosync): [ok]
[root@app1 ~]# service pacemaker start
starting pacemaker cluster manager [ok]
配置服務開機自啟動：
chkconfig corosync on
chkconfig pacemaker on
節點2:
[root@app2 ~]# service corosync start
(1) 檢視節點情況
[root@app1 ~]# crm status
last updated: tue jan 26 13:13:19 2016
last change: mon jan 25 17:46:04 2016 via cibadmin on app1
stack: classic openais (with plugin)
current dc: app1 - partition with quorum
version: 1.1.10-14.el6-368c726
2 nodes configured, 2 expected votes
0 resources configured
online: [ app1 app2 ]
(2) 檢視端口啟動情況
# netstat -tunlp
active internet connections (only servers)
proto recv-q send-q local address foreign address state pid/program name
udp 0 0 10.10.10.25:5404 0.0.0.0:* 2828/corosync
udp 0 0 10.10.10.25:5405 0.0.0.0:* 2828/corosync
udp 0 0 226.94.8.8:5405 0.0.0.0:* 2828/corosync
(3) 檢視日志
[root@app1 corosync]# tail -f /var/log/cluster/corosync.log
可以檢視日志中關鍵資訊：
jan 23 16:09:30 corosync [main ] corosync cluster engine ('1.4.7'): started and ready to provide service.
jan 23 16:09:30 corosync [main ] successfully read main configuration file '/etc/corosync/corosync.conf'.
....
jan 23 16:09:30 corosync [totem ] initializing transmit/receive security: libtomcrypt sober128/sha1hmac (mode 0).
jan 23 16:09:31 corosync [totem ] the network interface [10.10.10.24] is now up.
jan 23 16:09:31 corosync [totem ] a processor joined or left the membership and a new membership was formed.
jan 23 16:09:48 corosync [totem ] a processor joined or left the membership and a new membership was formed.
corosync預設啟用了stonith功能，而我們要配置的叢集并沒有stonith裝置，是以在配置叢集的全局屬性時要對其禁用。
# crm
crm(live)# configure ##進入配置模式
crm(live)configure# property stonith-enabled=false ##禁用stonith裝置
crm(live)configure# property no-quorum-policy=ignore ##不具備法定票數時采取的動作
crm(live)configure# rsc_defaults resource-stickiness=100 ##設定預設的資源黏性，隻對目前節點有效。
crm(live)configure# verify ##校驗
crm(live)configure# commit ##校驗沒有錯誤再送出
crm(live)configure# show ##檢視目前配置
node app1
node app2
property cib-bootstrap-options: \
dc-version=1.1.11-97629de \
cluster-infrastructure="classic openais (with plugin)" \
expected-quorum-votes=2 \
stonith-enabled=false \
default-resource-stickiness=100 \
no-quorum-policy=ignore
或:
# crm configure property stonith-enabled=false
# crm configure property no-quorum-policy=ignore
# crm configure property default-resource-stickiness=100
#指令使用經驗說明：verify報錯的，可以直接退出，也可以采用edit編輯，修改正确為止。
# crm configure edit 可以直接編輯配置檔案
不要單個資源送出，等所有資源及限制一起建立之後送出。
crm(live)configure# primitive vip ocf:heartbeat:ipaddr params ip=192.168.0.26 cidr_netmask=24 nic=eth0:1 op monitor interval=30s timeout=20s on-fail=restart
crm(live)configure# verify #驗證一下參數是否正确
說明:
primitive :定義資源指令
myip :資源id名，可自行定義
ocf:heartbeat:ipaddr :資源代理(ra)
params ip=192.168.0.26 :定義vip
op monitor :監控該資源
interval=30s :間隔時間
timeout=20s :逾時時間
on-fail=restart :如服務非正常關閉，讓其重新開機，如重新開機不了，再轉移至其他節點
crm(live)configure# primitive mydrbd ocf:linbit:drbd params drbd_resource=data op monitor role=master interval=20 timeout=30 op monitor role=slave interval=30 timeout=30 op start timeout=240 op stop timeout=100
crm(live)configure# verify
crm(live)configure# ms ms_mydrbd mydrbd meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true
crm(live)configure# primitive mystore ocf:heartbeat:filesystem params device=/dev/drbd0 directory=/data fstype=ext4 op start timeout=60s op stop timeout=60s op monitor interval=30s timeout=40s on-fail=restart
建立組資源，vip與mystore一起。
crm(live)configure# group g_service vip mystore
建立位置限制，組資源的啟動依懶于drbd主節點
crm(live)configure# colocation c_g_service inf: g_service ms_mydrbd:master
建立位置約整，mystore存儲挂載依賴于drbd主節點
crm(live)configure# colocation mystore_with_drbd_master inf: mystore ms_mydrbd:master
啟動順序依懶，drbd啟動後，建立g_service組資源
crm(live)configure# order o_g_service inf: ms_mydrbd:promote g_service:start
crm(live)configure# verify
crm(live)configure# commit
last updated: mon jan 25 22:24:55 2016
last change: mon jan 25 22:24:46 2016
current dc: app2 - partition with quorum
version: 1.1.11-97629de
4 resources configured
master/slave set: ms_mydrbd [mydrbd]
masters: [ app1 ]
slaves: [ app2 ]
resource group: g_service
vip (ocf::heartbeat:ipaddr): started app1
mystore (ocf::heartbeat:filesystem): started app1
[root@app1 ~]#
#說明：切換測試時有時會出現警告提示，影響真實狀态檢視，可以采用如下方式清除，提示哪個資源報警就清哪個，清理後，再次crm status檢視狀态顯示正常。
failed actions:
mystore_stop_0 on app1 'unknown error' (1): call=97, status=complete, last-rc-change='tue jan 26 14:39:21 2016', queued=6390ms, exec=0ms
[root@app1 ~]# crm resource cleanup mystore
cleaning up mystore on app1
cleaning up mystore on app2
waiting for 2 replies from the crmd.. ok
(1) 檢視drbd挂載目錄
[root@app2 ~]# df -h
filesystem size used avail use% mounted on
/dev/mapper/vg_app2-lv_root
35g 3.7g 30g 11% /
tmpfs 497m 45m 452m 10% /dev/shm
/dev/sda1 477m 34m 418m 8% /boot
192.168.1.26:/data 20g 44m 19g 1% /mnt
/dev/drbd0 20g 44m 19g 1% /data
[root@app2 ~]#
(2) 檢視drbd主備情況
[root@app2 ~]# cat /proc/drbd
0: cs:connected ro:primary/secondary ds:uptodate/uptodate c r-----
ns:20484 nr:336 dw:468 dr:21757 al:4 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
[root@app1 ~]# cat /proc/drbd
0: cs:connected ro:secondary/primary ds:uptodate/uptodate c r-----
ns:0 nr:20484 dw:20484 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
(3) nfs用戶端挂載讀寫正常
[root@vm15 ~]# df -h
/dev/sda3 21g 4.6g 15g 24% /
/dev/sda1 99m 23m 72m 25% /boot
tmpfs 7.4g 0 7.4g 0% /dev/shm
/dev/mapper/vg-data 79g 71g 4.2g 95% /data
192.168.0.26:/data/ 5.0g 138m 4.6g 3% /mnt
[root@vm15 ~]#
[root@vm15 ~]# cd /mnt
[root@vm15 mnt]# ls
abc.txt lost+found
[root@vm15 mnt]# cp abc.txt a.txt
[root@vm15 mnt]#
a.txt abc.txt lost+found
[root@vm15 mnt]#
(1) 關閉app1節點，資源全都在節點2啟動
[root@app2 ~]# crm status
last updated: tue jan 26 13:31:54 2016
last change: tue jan 26 13:30:21 2016 via cibadmin on app1
online: [ app2 ]
offline: [ app1 ]
masters: [ app2 ]
stopped: [ app1 ]
vip (ocf::heartbeat:ipaddr): started app2
mystore (ocf::heartbeat:filesystem): started app2
(2) 磁盤目錄挂載成功
filesystem size used avail use% mounted on
/dev/mapper/vg_app2-lv_root 36g 3.7g 30g 11% /
tmpfs 1004m 44m 960m 5% /dev/shm
/dev/sda1 485m 39m 421m 9% /boot
/dev/drbd0 5.0g 138m 4.6g 3% /data
(3) drbd也切換成了主節點：
version: 8.4.3 (api:1/proto:86-101)
git-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:wfconnection ro:primary/unknown ds:uptodate/dunknown c r-----
ns:0 nr:144 dw:148 dr:689 al:1 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:4
節點1啟動後，可以直接加入，資源也無需要再次切換。
# crm node standby app2 #app2離線
檢視資源，節點資源直接切換到app1上面，還是重新開機效果好。
last updated: tue jan 26 14:30:05 2016
last change: tue jan 26 14:29:59 2016 via crm_attribute on app2
node app2: standby
online: [ app1 ]
stopped: [ app2 ]
本文采用vmware esxi5.1虛拟機，stonith也是采用vmware esxi的fence裝置fence_vmware_soap
注：在測試corosync+pacemaker過程中出現無法快速reboot/shutdown.stonith對一些伺服器無法重新開機時配置該操作很有用。
需要在app1,app2安裝fence-agents安裝包。
# yum install fence-agents
安裝之後位置以及stonith測試功能
[root@app1 ~]# /usr/sbin/fence_vmware_soap -a 192.168.0.61 -z -l root -p 876543 -o list
...
...
drbd_heartbeat_app1,564d09c3-e8ee-9a01-e5f4-f1b11f03c810
drbd_heartbeat_app2,564dddb8-f4bf-40e6-dbad-9b97b97d3d25
例如：重新開機虛拟機：
[root@app1 ~]# /usr/sbin/fence_vmware_soap -a 192.168.0.61 -z -l root -p 876543 -n drbd_heartbeat_app2 -o reboot
[root@app1 ~]# crm
crm(live)# configure
crm(live)configure# primitive vm-fence-app1 stonith:fence_vmware_soap params ipaddr=192.168.0.61 login=root passwd=876543 port=app1 ssl="1" pcmk_host_list="drbd_heartbeat_app1" retry_on="10" shell_timeout="120" login_timeout="120" action="reboot" op start interval="0" timeout="120"
crm(live)configure# primitive vm-fence-app2 stonith:fence_vmware_soap params ipaddr=192.168.0.61 login=root passwd=876543 port=app2 ssl="1" pcmk_host_list="drbd_heartbeat_app2" retry_on="10" shell_timeout="120" login_timeout="120" action="reboot" op start interval="0" timeout="120"
crm(live)configure# location l-vm-fence-app1 vm-fence-app1 -inf: app1
crm(live)configure# location l-vm-fence-app2 vm-fence-app2 -inf: app2
crm(live)configure# property stonith-enabled=true
[root@app1 ~]# crm status
last updated: tue jan 26 16:50:53 2016
last change: tue jan 26 16:50:27 2016 via crmd on app2
stack: classic openais (with plugin)
current dc: app2 - partition with quorum
version: 1.1.10-14.el6-368c726
2 nodes configured, 2 expected votes
6 resources configured
master/slave set: ms_mydrbd [mydrbd]
masters: [ app2 ]
slaves: [ app1 ]
resource group: g_service
vm-fence-app1 (stonith:fence_vmware_soap): started app2
vm-fence-app2 (stonith:fence_vmware_soap): started app1
[root@app1 ~]# crm
crm(live)configure# show xml
<?xml version="1.0" ?>
<cib num_updates="4" dc-uuid="app2" update-origin="app2" crm_feature_set="3.0.7" validate-with="pacemaker-1.2" update-client="crmd" epoch="91" admin_epoch="0" cib-last-written="tue jan 26 16:50:27 2016" have-quorum="1">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<nvpair id="cib-bootstrap-options-dc-version" name="dc-version" value="1.1.10-14.el6-368c726"/>
<nvpair id="cib-bootstrap-options-cluster-infrastructure" name="cluster-infrastructure" value="classic openais (with plugin)"/>
<nvpair id="cib-bootstrap-options-expected-quorum-votes" name="expected-quorum-votes" value="2"/>
<nvpair name="stonith-enabled" value="false" id="cib-bootstrap-options-stonith-enabled"/>
<nvpair name="no-quorum-policy" value="ignore" id="cib-bootstrap-options-no-quorum-policy"/>
<nvpair name="default-resource-stickiness" value="100" id="cib-bootstrap-options-default-resource-stickiness"/>
<nvpair id="cib-bootstrap-options-last-lrm-refresh" name="last-lrm-refresh" value="1453798227"/>
</cluster_property_set>
</crm_config>
<nodes>
<node id="app2" uname="app2">
<instance_attributes id="nodes-app2">
<nvpair id="nodes-app2-standby" name="standby" value="off"/>
</instance_attributes>
</node>
<node id="app1" uname="app1">
<instance_attributes id="nodes-app1">
<nvpair id="nodes-app1-standby" name="standby" value="off"/>
</nodes>
<resources>
<primitive id="vm-fence-app1" class="stonith" type="fence_vmware_soap">
<instance_attributes id="vm-fence-app1-instance_attributes">
<nvpair name="ipaddr" value="192.168.0.61" id="vm-fence-app1-instance_attributes-ipaddr"/>
<nvpair name="login" value="root" id="vm-fence-app1-instance_attributes-login"/>
<nvpair name="passwd" value="xjj876543" id="vm-fence-app1-instance_attributes-passwd"/>
<nvpair name="port" value="app1" id="vm-fence-app1-instance_attributes-port"/>
<nvpair name="ssl" value="1" id="vm-fence-app1-instance_attributes-ssl"/>
<nvpair name="pcmk_host_list" value="drbd_heartbeat_app1" id="vm-fence-app1-instance_attributes-pcmk_host_list"/>
<nvpair name="retry_on" value="10" id="vm-fence-app1-instance_attributes-retry_on"/>
<nvpair name="shell_timeout" value="120" id="vm-fence-app1-instance_attributes-shell_timeout"/>
<nvpair name="login_timeout" value="120" id="vm-fence-app1-instance_attributes-login_timeout"/>
<nvpair name="action" value="reboot" id="vm-fence-app1-instance_attributes-action"/>
<operations>
<op name="start" interval="0" timeout="120" id="vm-fence-app1-start-0"/>
</operations>
</primitive>
<primitive id="vm-fence-app2" class="stonith" type="fence_vmware_soap">
<instance_attributes id="vm-fence-app2-instance_attributes">
<nvpair name="ipaddr" value="192.168.0.61" id="vm-fence-app2-instance_attributes-ipaddr"/>
<nvpair name="login" value="root" id="vm-fence-app2-instance_attributes-login"/>
<nvpair name="passwd" value="xjj876543" id="vm-fence-app2-instance_attributes-passwd"/>
<nvpair name="port" value="app2" id="vm-fence-app2-instance_attributes-port"/>
<nvpair name="ssl" value="1" id="vm-fence-app2-instance_attributes-ssl"/>
<nvpair name="pcmk_host_list" value="drbd_heartbeat_app2" id="vm-fence-app2-instance_attributes-pcmk_host_list"/>
<nvpair name="retry_on" value="10" id="vm-fence-app2-instance_attributes-retry_on"/>
<nvpair name="shell_timeout" value="120" id="vm-fence-app2-instance_attributes-shell_timeout"/>
<nvpair name="login_timeout" value="120" id="vm-fence-app2-instance_attributes-login_timeout"/>
<nvpair name="action" value="reboot" id="vm-fence-app2-instance_attributes-action"/>
<op name="start" interval="0" timeout="120" id="vm-fence-app2-start-0"/>
<group id="g_service">
<primitive id="vip" class="ocf" provider="heartbeat" type="ipaddr">
<instance_attributes id="vip-instance_attributes">
<nvpair name="ip" value="192.168.0.26" id="vip-instance_attributes-ip"/>
<nvpair name="cidr_netmask" value="24" id="vip-instance_attributes-cidr_netmask"/>
<nvpair name="nic" value="eth0:1" id="vip-instance_attributes-nic"/>
</instance_attributes>
<operations>
<op name="monitor" interval="30s" timeout="20s" on-fail="restart" id="vip-monitor-30s"/>
</operations>
</primitive>
<primitive id="mystore" class="ocf" provider="heartbeat" type="filesystem">
<instance_attributes id="mystore-instance_attributes">
<nvpair name="device" value="/dev/drbd0" id="mystore-instance_attributes-device"/>
<nvpair name="directory" value="/data" id="mystore-instance_attributes-directory"/>
<nvpair name="fstype" value="ext4" id="mystore-instance_attributes-fstype"/>
<op name="start" timeout="60s" interval="0" id="mystore-start-0"/>
<op name="stop" timeout="60s" interval="0" id="mystore-stop-0"/>
<op name="monitor" interval="30s" timeout="40s" on-fail="restart" id="mystore-monitor-30s"/>
</group>
<master id="ms_mydrbd">
<meta_attributes id="ms_mydrbd-meta_attributes">
<nvpair name="master-max" value="1" id="ms_mydrbd-meta_attributes-master-max"/>
<nvpair name="master-node-max" value="1" id="ms_mydrbd-meta_attributes-master-node-max"/>
<nvpair name="clone-max" value="2" id="ms_mydrbd-meta_attributes-clone-max"/>
<nvpair name="clone-node-max" value="1" id="ms_mydrbd-meta_attributes-clone-node-max"/>
<nvpair name="notify" value="true" id="ms_mydrbd-meta_attributes-notify"/>
</meta_attributes>
<primitive id="mydrbd" class="ocf" provider="linbit" type="drbd">
<instance_attributes id="mydrbd-instance_attributes">
<nvpair name="drbd_resource" value="data" id="mydrbd-instance_attributes-drbd_resource"/>
<op name="monitor" role="master" interval="20" timeout="30" id="mydrbd-monitor-20"/>
<op name="monitor" role="slave" interval="30" timeout="30" id="mydrbd-monitor-30"/>
<op name="start" timeout="240" interval="0" id="mydrbd-start-0"/>
<op name="stop" timeout="100" interval="0" id="mydrbd-stop-0"/>
</master>
</resources>
<constraints>
<rsc_colocation id="c_g_service" score="infinity" rsc="g_service" with-rsc="ms_mydrbd" with-rsc-role="master"/>
<rsc_colocation id="mystore_with_drbd_master" score="infinity" rsc="mystore" with-rsc="ms_mydrbd" with-rsc-role="master"/>
<rsc_order id="o_g_service" score="infinity" first="ms_mydrbd" first-action="promote" then="g_service" then-action="start"/>
<rsc_location id="l-vm-fence-app1" rsc="vm-fence-app1" score="-infinity" node="app1"/>
<rsc_location id="l-vm-fence-app2" rsc="vm-fence-app2" score="-infinity" node="app2"/>
</constraints>
</configuration>
</cib>
清空資源，重新配置操作方法：
[root@app2 ~]# crm status
last updated: wed jan 27 10:39:24 2016
[root@app2 ~]#
先依次關閉資源 ：
[root@app2 ~]# crm resource stop vm-fence-app2
[root@app2 ~]# crm resource stop vm-fence-app1
[root@app2 ~]# crm resource stop mystore
[root@app2 ~]# crm resource stop vip
[root@app2 ~]# crm resource stop ms_mydrbd
[root@app2 ~]# crm status
last updated: wed jan 27 10:40:28 2016
last change: wed jan 27 10:40:23 2016 via cibadmin on app2
再清空配置：
[root@app2 ~]# crm configure erase
info: resource references in colocation:c_g_service updated
info: resource references in colocation:mystore_with_drbd_master updated
info: resource references in order:o_g_service updated
last updated: wed jan 27 10:40:58 2016
last change: wed jan 27 10:40:52 2016 via crmd on app2
就可以再次重新配置了。
之前多次未成功配置的成功主要在于資源的排列與定位啟動上面，造成切換，啟動均不成功，這個也是corosync+pacemaker的配置要了解的重點, drbd+可以實作很多種組合，本文僅提供技術實作參考。
![手機軟體抓包工具及其使用方法[圖]](data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=)