實驗目的：完成一個高可用的基於資料庫存儲的文件伺服器 所需軟體包：cluster-glue-1.0.6-1.6.el5.i386.rpm cluster-glue-libs-1.0.6-1.6.el5.i386.rpm
corosync-1.2.7-1.1.el5.i386.rpm corosynclib-1.2.7-1.1.el5.i386.rpm heartbeat-3.0.3-2.3.el5.i386.rpm heartbeat-libs-3.0.3-2.3.el5.i386.rpm openais-1.1.3-1.6.el5.i386.rpm openaislib-1.1.3-1.6.el5.i386.rpm resource-agents-1.0.4-1.1.el5.i386.rpm pacemaker-1.0.11-1.2.el5.i386.rpm pacemaker-libs-1.0.11-1.2.el5.i386.rpm libesmtp-1.0.4-5.el5.i386.rpm 準備工作： 1. 所有節點的主機名稱和對應的IP地址解析服務可以正常工作,且每個節點的主機名稱需要跟"uname -n“命令的結果保持一致：所以在兩台主機的/etc/hosts添加如下內容 ：
192.168.16.5 node1.ykl.com node1
192.168.16.6 node2.ykl.com node2 為使系統重啟以後仍舊使用以上主機名,
node1： #vim /etc/sysconfig/network
HOATNAME=node1.ykl.com #hostname node1.ykl.com node2： #vim /etc/sysconfig/network
HOATNAME=node2.ykl.com #hostname node2.ykl.com 2.設定兩個節點可以使用基於密鑰的ssh通信
node1: # ssh-keygen -t rsa # ssh-copy-id -i ~/.ssh/id_rsa.pub root@node2 node2: # ssh-keygen -t rsa # ssh-copy-id -i ~/.ssh/id_rsa.pub root@node1 注意： 可以通過 ssh node1 ‘ifconfig’ 驗證是否成功 OK,準備工作完成！！！！ 一．安裝及配置corosync和 pacemaker 1. 將所用安裝包存放在/root/cluster 中,安裝
node1: # cd /cluster #yum –nogpgcheck localinstall –y *.rpm #scp -r cluster/ node2:/root/cluster node2: # cd /cluster #yum –nogpgcheck localinstall –y *.rpm 2.配置corosync.conf node1: #cp corosync.conf.example corosync.conf #vim corosync.conf bindnetaddr:192.168.16.0 //此配置文件中 bindnetaddr後面的IP地址為你的網卡所在網路的網路地址 service { ver: 0 name: pacemaker } aisexec { user: root group: root } #corosync-keygen //生成節點間通信時用到的認證密鑰文件 #scp -p corosync.conf authkey node2:/etc/corosync/ # mkdir /var/log/cluster //創建日誌文件 # ssh node2 'mkdir /var/log/cluster' 3.嘗試開啟corosync： node1： #service corosync start 4.通過查看以下信息判斷corosync是否正常工作 node1： 1. 查看corosync引擎是否正常啟動 # grep -e "Corosync Cluster Engine" -e "configuration file" /var/log/messages Dec 29 15:18:17 localhost corosync[5193]: [MAIN ] Corosync Cluster Engine ('1.2.7'): started and ready to provide service. Dec 29 15:18:17 localhost corosync[5193]: [MAIN ] Successfully read main configuration file '/etc/corosync/corosync.conf'. 2. 查看初始化成員節點通知是否正常發出 # grep TOTEM /var/log/messages Dec 29 15:18:17 localhost corosync[5193]: [TOTEM ] Initializing transport (UDP/IP). Dec 29 15:18:17 localhost corosync[5193]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). Dec 29 15:18:18 localhost corosync[5193]: [TOTEM ] The network interface [192.168.16.5] is now up. Dec 29 15:18:18 localhost corosync[5193]: [TOTEM ] A processor joined or left the membership and a new membership was formed. 3. 檢查啟動過程中是否有錯誤產生 # grep ERROR: /var/log/messages | grep -v unpack_resources 注意：沒有信息就是最好的信息！！！！ 4. 查看pacemaker是否正常啟動 #grep pcmk_startup /var/log/messages Dec 29 15:18:18 localhost corosync[5193]: [pcmk ] info: pcmk_startup: CRM: Initialized Dec 29 15:18:18 localhost corosync[5193]: [pcmk ] Logging: Initialized pcmk_startup Dec 29 15:18:18 localhost corosync[5193]: [pcmk ] info: pcmk_startup: Maximum core file size is: 4294967295 Dec 29 15:18:18 localhost corosync[5193]: [pcmk ] info: pcmk_startup: Service: 9 Dec 29 15:18:18 localhost corosync[5193]: [pcmk ] info: pcmk_startup: Local hostname: node1.ykl.com ssh node2 ‘serivoce corosync start’ 注意：在node2上重複上面的操作,如果你確信你的RP值足夠強大,也可以不做（後半句是我老師說的,嘿嘿） 5. 查看集群節點的啟動狀態： # crm status ============ Last updated: Thu Dec 29 15:29:19 2011 Stack: openais Current DC: node1.ykl.com - partition with quorum Version: 1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87 2 Nodes configured, 2 expected votes 0 Resources configured. ============ Online: [ node1.ykl.com node2.ykl.com ] 6.對屬性信息的一些修改 # crm configure property no-quorum-policy=ignore # crm configure property stonith-enabled=false # crm configure show node node1.ykl.com node node2.ykl.com property $id="cib-bootstrap-options" \ dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ no-quorum-policy="ignore" \ stonith-enabled="false"\ 說明：時間很晚了,剩下的明天再做！
本文出自 「狼馳草原」 博客,請務必保留此出處http://ykllang.blog.51cto.com/3778268/753357
