heartbeat v2版CRM的高可用web集群的实现
2015-01-03 17:17
351 查看
接上一篇文章:heartbeat v1版CRM的高可用集群的实现
架构图:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/6697aa6bc66b88eafe739dbaeed81e11.jpg)
网络地址规划:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/db21dfc581bf8c899d0c9a2413170cf0.jpg)
一.关闭heartbeat服务
node1和node2都需要关闭:
二.正式开始配置heartbeat v2 版本的CRM
开启heartbeat v2版本的CRM,只需要在ha.cf主配置文件末尾加入“crm on”即可,而且haresources文件设置的资源就会失效。
三.集群配置
1.由于我们需要使用图形化界面配置heartbeatv2集群,而安装heartbeat后会生成一个hacluster用户,我们需要设置密码,可以让我们来访问图形化界面:
node1和node2主机都要配置:
2.使用Linux的GNONE桌面进入heartbeatv2 版本的图形化CRM配置:
首先开启heartbeat服务:
由于无资源配置文件,启动非常快速。
查看监听端口:
3.图形化配置
登录GUI界面
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/de3cd55c14ddd6588aa243586117ed5e.jpg)
输入用户名密码登录:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/7c8696cce043333ac6aec07186be32df.jpg)
4.新建资源类型webip:定义VIP
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/ae02aecb358c73dc6ac2b9aa8d13d753.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/17115389fe5ff52591d81fe02dc4653d.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/10f2f4a818409a9e56c44cae92bc7574.jpg)
添加完成后就点击Add即可:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/bd236dc27d21de19803c7e080944dac3.jpg)
5.新建资源类型webserver,定义httpd服务
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/1beaa99627729e82a2b9fa805c4a6d6a.jpg)
完成后启动资源测试:启动webip和webserver即可
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/56d4b7419eb9638a043ae2653828f081.jpg)
启动完成,但是资源未一起在同一节点启动,符合公平分配原则,我们需要使用排列约束,分组,顺序约束实现资源的启动节点。
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/165bcacce6e193c8b50ef0a1aae33d0c.jpg)
6.协同限制配置
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/0398ca3d320ac3fb846417ad477f2e3a.jpg)
设置成webip所在节点,webserver也会在那个节点启动:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/d78f7d0ece7c680b5506dbc55ad5d228.jpg)
效果出现,因为开始webip在node2节点启动,所以配置协同约束后,webserver自动就切换到node2启动:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/957f0887ffa8ca678eb71a5007bd2a5f.jpg)
7.顺序约束配置:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/6cfcb0044cb10b0346296cf38a049581.jpg)
设置先启动webip资源,然后再启动webserver资源:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/b0d6efc4b671a06dfec817d71b704d2c.jpg)
8.位置约束:让资源偏向运行于某个节点
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/5bf59557a40e6a4d5fc234c218e682a3.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/4d7f0afecd1188f0dfc2d5b61ade4256.jpg)
表达式判断:uname eq node1.stu31.com ,偏向于node1节点:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/8b40b79f9cc126b06634097986e9e1c1.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/2a5787a913b8f8355b2a0b2c7f76e66e.jpg)
9.配置NFS服务器
配置nfs服务器
客户端node1挂载nfs文件系统:
访问测试:
卸载nfs:
10.使用集群图形化客户端配置添加存储资源
添加存储:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/da5ddbc512b63e0e0ea8fab382bfd24b.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/403c2e682917a0188aea546e8a264eaa.jpg)
启动存储
11.协同约束配置
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/32cf4207cac4c04df5185f8afd45f04c.jpg)
顺序约束配置:
先启动webip,然后启动webstore,最后启动webserver
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/a8391779a6bd7fc9bb2b70621f4ff483.jpg)
查看节点IP地址:主节点在node1上
网页访问:
架构图:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/6697aa6bc66b88eafe739dbaeed81e11.jpg)
网络地址规划:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/db21dfc581bf8c899d0c9a2413170cf0.jpg)
一.关闭heartbeat服务
node1和node2都需要关闭:
# service heartbeat stop Stopping High-Availability services: Done.
二.正式开始配置heartbeat v2 版本的CRM
开启heartbeat v2版本的CRM,只需要在ha.cf主配置文件末尾加入“crm on”即可,而且haresources文件设置的资源就会失效。
[root@node1 ~]# cat /etc/ha.d/ha.cf |grep-v ^# logfacility local0 mcast eth0 225.131.31.23 694 1 0 auto_failback on node node1.stu31.com node node2.stu31.com ping 172.16.0.1 crm on
三.集群配置
1.由于我们需要使用图形化界面配置heartbeatv2集群,而安装heartbeat后会生成一个hacluster用户,我们需要设置密码,可以让我们来访问图形化界面:
node1和node2主机都要配置:
# echo oracle |passwd --stdinhacluster
2.使用Linux的GNONE桌面进入heartbeatv2 版本的图形化CRM配置:
首先开启heartbeat服务:
[root@node1 ~]# /etc/init.d/heartbeat start ; ssh node2 'service heartbeat start' logd is already running Starting High-Availability services: Done. logd is already running Starting High-Availability services: Done.
由于无资源配置文件,启动非常快速。
查看监听端口:
[root@node1 ~]# ss -tunl |grep 5560 tcp LISTEN 0 10 *:5560 *:*
3.图形化配置
登录GUI界面
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/de3cd55c14ddd6588aa243586117ed5e.jpg)
输入用户名密码登录:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/7c8696cce043333ac6aec07186be32df.jpg)
4.新建资源类型webip:定义VIP
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/ae02aecb358c73dc6ac2b9aa8d13d753.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/17115389fe5ff52591d81fe02dc4653d.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/10f2f4a818409a9e56c44cae92bc7574.jpg)
添加完成后就点击Add即可:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/bd236dc27d21de19803c7e080944dac3.jpg)
5.新建资源类型webserver,定义httpd服务
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/1beaa99627729e82a2b9fa805c4a6d6a.jpg)
完成后启动资源测试:启动webip和webserver即可
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/56d4b7419eb9638a043ae2653828f081.jpg)
启动完成,但是资源未一起在同一节点启动,符合公平分配原则,我们需要使用排列约束,分组,顺序约束实现资源的启动节点。
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/165bcacce6e193c8b50ef0a1aae33d0c.jpg)
6.协同限制配置
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/0398ca3d320ac3fb846417ad477f2e3a.jpg)
设置成webip所在节点,webserver也会在那个节点启动:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/d78f7d0ece7c680b5506dbc55ad5d228.jpg)
效果出现,因为开始webip在node2节点启动,所以配置协同约束后,webserver自动就切换到node2启动:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/957f0887ffa8ca678eb71a5007bd2a5f.jpg)
7.顺序约束配置:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/6cfcb0044cb10b0346296cf38a049581.jpg)
设置先启动webip资源,然后再启动webserver资源:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/b0d6efc4b671a06dfec817d71b704d2c.jpg)
8.位置约束:让资源偏向运行于某个节点
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/5bf59557a40e6a4d5fc234c218e682a3.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/4d7f0afecd1188f0dfc2d5b61ade4256.jpg)
表达式判断:uname eq node1.stu31.com ,偏向于node1节点:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/8b40b79f9cc126b06634097986e9e1c1.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/2a5787a913b8f8355b2a0b2c7f76e66e.jpg)
9.配置NFS服务器
配置nfs服务器
[root@nfs ~]# mkdir /www/htdocs -pv [root@nfs ~]# vim /etc/exports www/htdocs 172.16.31.0/16(rw,no_root_squash)
[root@nfs ~]# service nfs start [root@nfs ~]# showmount -e172.16.31.12 Export list for 172.16.31.12: /www/htdocs 172.16.31.0/16创建一个测试网页:
[root@nfs ~]# echo "page from nfsfilesystem" > /www/htdocs/index.html
客户端node1挂载nfs文件系统:
[root@node1 ~]# mount -t nfs 172.16.31.12:/www/htdocs/var/www/html/ [root@node1 ~]# ls /var/www/html/ index.html
访问测试:
[root@nfs ~]# curl http://172.16.31.166 page from nfs filesystem
卸载nfs:
[root@node1 ~]# umount /var/www/html/
10.使用集群图形化客户端配置添加存储资源
添加存储:
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/da5ddbc512b63e0e0ea8fab382bfd24b.jpg)
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/403c2e682917a0188aea546e8a264eaa.jpg)
启动存储
11.协同约束配置
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/32cf4207cac4c04df5185f8afd45f04c.jpg)
顺序约束配置:
先启动webip,然后启动webstore,最后启动webserver
![](https://oscdn.geek-share.com/Uploads/Images/Content/202001/08/a8391779a6bd7fc9bb2b70621f4ff483.jpg)
查看节点IP地址:主节点在node1上
[root@node1 ~]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0:<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen1000 link/ether 08:00:27:db:35:e6 brd ff:ff:ff:ff:ff:ff inet 172.16.31.10/16 brd 172.16.255.255 scope global eth0 inet 172.16.31.166/16 brd 172.16.31.255 scope global secondary eth0:0 inet6 fe80::a00:27ff:fedb:35e6/64 scope link valid_lft forever preferred_lft forever
网页访问:
[root@nfs ~]# curl http://172.16.31.166 page from nfs filesystem由于使用的是共享文件系统,所以访问的网页是文件系统中的资源!
相关文章推荐
- heartbeat v2版CRM的高可用web集群的实现
- heartbeat v1版CRM的高可用web集群的实现
- 轻松实现基于Heartbeat的高可用web服务集群
- heartbeat v1版CRM的高可用web集群的实现
- heartbeat httpd nfs 实现高可用web集群
- 高可用集群之heartbeat配置,实现web服务的高可用以及Mariadb高可用 推荐
- 轻松实现基于Heartbeat的高可用web服务集群
- heartbeat httpd nfs 实现高可用web集群
- 高可用集群之heartbeat v2--基于CRM实现mysql高可用集群(未完)
- Heartbeat+MySQL+NFS 实现高可用(HA)的MySQL集群
- 使用LVS+heartbeat构建高可用web集群
- 集群之heartbeat(v2){haresource}实现httpd高可用
- linux高可用集群heartbeat实现http的高可用
- corosync+pacemaker实现web集群高可用 推荐
- heartbeat v2配置高可用web集群和基于nfs搭建MySQL高可用集群
- CentOS 6.4 Heartbeat+mysql+nfs实现高可用的mysql集群 推荐
- Heartbeat实现Web服务的高可用群集
- 初接触Linux,基于corosync+pacemaker实现web集群高可用
- 基于heartbeat+nfs的高可用web(三种方式实现)
- 搭建基于Heartbeat v2+NFS的高可用Web集群