Кластер corosync+pacemaker

11.11.2019 - Записи в блоге

На всех узлах кластера требуется выполнить следующие действия:

[support@node1 ~]$ sudo yum install ntpdate pcs 
[support@node1 ~]$ sudo passwd hacluster
[support@node1 ~]$ sudo systemctl enable ntp
[support@node1 ~]$ sudo systemctl start ntp
[support@node1 ~]$ sudo systemctl enable pcsd	
[support@node1 ~]$ sudo systemctl start pcsd

На одном из узлов требуется выполнить следующие действия:

[support@node1 ~]$ sudo pcs cluster auth nd1 nd2 -u hacluster
[support@node1 ~]$ sudo pcs cluster setup --force --name clstrnm1 nd1 nd2
[support@node1 ~]$ sudo pcs cluster enable --all
[support@node1 ~]$ sudo pcs cluster start --all
[support@node1 ~]$ sudo pcs property set stonith-enabled=false
[support@node1 ~]$ sudo pcs property set no-quorum-policy=ignore
[support@node1 ~]$ sudo pcs resource create rsrc1_ip ocf:heartbeat:IPaddr2 ip=10.255.2.122 cidr_netmask=25 op monitor interval=1s
[support@node1 ~]$ sudo pcs resource create rsrc2_service systemd:nginx op monitor interval=1s
[support@node1 ~]$ sudo pcs constraint location rsrc1_ip prefers nd1=2 nd2=1
[support@node1 ~]$ sudo pcs constraint location rsrc2_service prefers nd1=2 nd2=1
[support@node1 ~]$ sudo pcs status
[support@node1 ~]$ sudo pcs cluster status
[support@node1 ~]$ sudo pcs resource show

 

› tags: CentOS / corosync / hacluster / pacemaker / pcs / pcs cluster / pcs constraint / pcs constraint location / pcs property / pcs resource /