Setup pcs cluster lab on kvm libvirt virtualization

-
~~~~~ Setup pcs cluster lab on kvm libvirt ~~~~~~~~~
----------------------------------------------------
host - kvm.mylab.local
guest- hanode1.mylab.local    | 192.168.122.83
guest- hanode2.mylab.local    | 192.168.122.84
~~~~~~~~~~~~~On KVM Host~~~~~~~~~~~~~
yum install fence-virt fence-virtd fence-virtd-libvirt fence-virtd-multicast fence-virtd-serial

 mkdir /etc/cluster
 dd if=/dev/urandom of=/etc/cluster/fence_xvm.key bs=4k count=1

 -- hit enter for all in above

 firewall-cmd --permanent --add-service=fence_virt
 firewall-cmd --permanent --add-port=1229/udp
 firewall-cmd --permanent --add-port=1229/tcp
 firewall-cmd --reload

 systemctl start fence_virtd.service
 systemctl enable fence_virtd.service
 systemctl status fence_virtd.service
  fence_virtd -c

 ssh [email protected] mkdir /etc/cluster
 ssh [email protected] mkdir /etc/cluster
 scp /etc/cluster/fence_xvm.key [email protected]:/etc/cluster/
 scp /etc/cluster/fence_xvm.key [email protected]:/etc/cluster/

 fence_xvm -o list
 ~~~~~~~~~~~on both nodes ~~~~~~~~~~~~~~~
yum install pcs pacemaker corosync fence-agents-virsh fence-virt \
pacemaker-remote fence-agents-all lvm2-cluster resource-agents \
psmisc policycoreutils-python gfs2-utils -y
echo "centos" | passwd hacluster --stdin
systemctl start pcsd.service; systemctl enable pcsd.service
firewall-cmd --permanent --add-service=high-availability
firewall-cmd --permanent --add-port=1229/tcp
firewall-cmd --reload

fence_xvm -o off -H hanode2  ## to check fencing
----Only if selinux was enabled during pcs setup
ls -Z /etc/cluster/fence_xvm.key
selinux_restorecon /etc/cluster/fence_xvm.key

 ~~~~~~~~~~~~~on any one of node~~~~~~~~~~~~

 pcs cluster auth hanode1.mylab.local hanode2.mylab.local -u hacluster -p centos
 pcs cluster setup --start --name webcluster hanode1.mylab.local hanode2.mylab.local
 pcs cluster enable --all
 pcs status
 crm_mon -r1
 pcs cluster status

 -- setup fencing part
 pcs stonith create fencedev1 fence_xvm pcmk_host_map="hanode1.mylab.local:hanode1 hanode2.mylab.local:hanode2" key_file=/etc/cluster/fence_xvm.key
 pcs stonith create fencedev2 fence_xvm pcmk_host_map="hanode1.mylab.local:hanode1 hanode2.mylab.local:hanode2" key_file=/etc/cluster/fence_xvm.key
 pcs constraint location fencedev1 prefers hanode1.mylab.local
 pcs constraint location fencedev2 prefers hanode2.mylab.local
 pcs constraint list
 pcs stonith
 pcs status
 --to check
 pcs stonith fence hanode2
 pcs stonith show --full
 pcs property --all | grep -i stonith

Comments

Post a Comment

Popular posts from this blog

using libguestfs virt-customize tool to modify qcow2 image and reset root password.

-
ibguestfs is a C library and a set of tools for accessing and modifying virtual disk images used in platform virtualization. The tools can be used for viewing and editing virtual machines managed by libvirt and files inside VMs, scripting changes to VMs, creating VMs, and much else beside. virt-customize is one of them as example. If you forgot root user password here is how you can modify . # virsh shutdown debian9-vm1 # virt-customize -a /var/lib/libvirt/images/debian9-vm1.qcow2 --root-password password:NewRootUserPasswordHere  not only this but you can edit many more. The –run-command option is used to execute any command inside a virtual image file. 1) register with rhel subscription virt-customize -a rhel-server-7.6.qcow2 --run-command 'subscription-manager attach --pool [subscription-pool]'     Install software or packages- virt-customize -a rhel-server-7.6.qcow2 --install net-tools  Upload a file into image virt-customize -a rhel-se...
Read more

Running cockpit behind nginx reverse proxy with nginx ssl and cockpit non ssl

-
Domain for web access to cockpit : cockpit.mylab.local cockpit server ip : 192.168.1.61 nginx server ip   : 192.168.1.65 Linux distro using is Centos 7.6 Login to cockpit server Create a file [root@repo ~]# vim /etc/cockpit/cockpit.conf content will be like [WebService] Origins = https://cockpit.mylab.local wss://cockpit.mylab.local ProtocolHeader = X-Forwarded-Proto AllowUnencrypted = true save and restart cockpit # systemctl restart cockpit now  login to your nginx webserver and install nginx # yum install nginx -y create a new file vim /etc/nginx/conf.d/cockpit.conf paste content as bellow server {     listen         80;     listen         443 ssl http2;     server_name    cockpit.mylab.local;     ssl_certificate /etc/ssl/certs/cockpit-selfsigned.crt;     ssl_certifica...
Read more

setting up openshift alert manager mail alerting based on critical and warning

-
Configure alert manager to send mail. This will send mail to 2 diffrent groups one is managemnet group for ciritical alerts only and second is default group for all alerts. $  oc project openshift-monitoring The secret file where alertmanager.yaml content ( encoded in base64 ) will remain is alertmanager-main convert the yaml content into base64 first $  cat alertmanager.yaml | base64 -w0 copy value now edit secret $ oc edit secret alertmanager-main find value starts with alertmanager.yaml: replace all base64 content from your own . save and exit now in order to take this secret in effect we must bounce the pod $  oc delete po -l alertmanager=main check if all pod came online $  oc get po -l alertmanager=main done! alertmanager.yaml content resolve_timeout : 5m route : group_wait : 30s group_interval : 5m repeat_interval : 12h ...
Read more