Pacemaker - Revision history

Tony: /* Links */

2022-03-08T11:37:14Z

Links

← Older revision		Revision as of 11:37, 8 March 2022
Line 8:		Line 8:

	*[http://clusterlabs.org/ Cluster Labs]		*[http://clusterlabs.org/ Cluster Labs]
			*[https://github.com/ClusterLabs/resource-agents/ Pacemaker resource agents on github]
	*[http://www.linux-ha.org/doc/man-pages/ap-ra-man-pages.html Linux-HA manpages]		*[http://www.linux-ha.org/doc/man-pages/ap-ra-man-pages.html Linux-HA manpages]
	*[https://clusterlabs.org/quickstart.html pacemaker quickstart]		*[https://clusterlabs.org/quickstart.html pacemaker quickstart]

Tony at 14:35, 17 January 2022

2022-01-17T14:35:57Z

← Older revision		Revision as of 14:35, 17 January 2022
Line 3:		Line 3:




	= Links =		= Links =
Line 30:		Line 31:
	*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html]]		*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html]]
	*[https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html#sec-ha-maint-shutdown-node Implications of Taking Down a Cluster Node]		*[https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html#sec-ha-maint-shutdown-node Implications of Taking Down a Cluster Node]
			*[https://www.programmerall.com/article/11571745093/ Corosync + Pacemaker + CRMSH Build a web high available cluster]

	= Notes =		= Notes =

Tony at 09:34, 23 September 2021

2021-09-23T09:34:16Z

← Older revision		Revision as of 09:34, 23 September 2021
Line 70:		Line 70:

	= HOWTO =		= HOWTO =



Line 78:		Line 79:
	pcs resource group add GROUPID RESOURCEID		pcs resource group add GROUPID RESOURCEID


			=== Stop resource group ===
			pcs resource disable MYGROUP

	=== See if entire group is disabled ===		=== See if entire group is disabled ===
Line 84:		Line 88:

	Meta Attrs: target-role=Stopped		Meta Attrs: target-role=Stopped


	= FAQ =		= FAQ =

Tony at 14:44, 16 August 2021

2021-08-16T14:44:07Z

← Older revision		Revision as of 14:44, 16 August 2021
Line 84:		Line 84:

	Meta Attrs: target-role=Stopped		Meta Attrs: target-role=Stopped


	= FAQ =		= FAQ =
Line 102:		Line 103:



			== Remove resource group + members ==
			pcs resource delete whateverresource


	== Move resource to node ==		== Move resource to node ==

Tony at 09:42, 8 July 2021

2021-07-08T09:42:07Z

← Older revision		Revision as of 09:42, 8 July 2021
Line 71:		Line 71:
	= HOWTO =		= HOWTO =

	==Groups==
	===Add existing resource to group===		== Groups ==

			=== Add existing resource to group ===

	pcs resource group add GROUPID RESOURCEID		pcs resource group add GROUPID RESOURCEID


			=== See if entire group is disabled ===

			pcs resource show MYGROUP

			Meta Attrs: target-role=Stopped

	= FAQ =		= FAQ =

Tony at 12:43, 2 July 2021

2021-07-02T12:43:19Z

← Older revision		Revision as of 12:43, 2 July 2021
Line 1:		Line 1:
	~~uses [[Corosync]] or [[heartbeat]], (it seems) corosync is the one to go for.~~

			uses [[Corosync\|Corosync]] or [[Heartbeat\|heartbeat]], (it seems) corosync is the one to go for.



	= Links =		= Links =

	*[http://clusterlabs.org/ Cluster Labs]		*[http://clusterlabs.org/ Cluster Labs]
	*[http://www.linux-ha.org/doc/man-pages/ap-ra-man-pages.html Linux-HA manpages]		*[http://www.linux-ha.org/doc/man-pages/ap-ra-man-pages.html Linux-HA manpages]
	*[https://clusterlabs.org/quickstart.html pacemaker quickstart]		*[https://clusterlabs.org/quickstart.html pacemaker quickstart]
	*[https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md]		*[https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md]
Line 27:		Line 29:
	*[http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html The OCF Resource Agent Developer’s Guide]		*[http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html The OCF Resource Agent Developer’s Guide]
	*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html]]		*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html]]
	*[https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html#sec-ha-maint-shutdown-node Implications of Taking Down a Cluster Node]		*[https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html#sec-ha-maint-shutdown-node Implications of Taking Down a Cluster Node]

	=Notes=		= Notes =
	~~by specifying -INFINITY, the constraint is binding.~~

			by specifying -INFINITY, the constraint is binding.



			= Quickstart =

			Keep in mind you might want to use dedicated IPs for sync, so define those in /etc/hosts On both nodes

			#set password

	~~=Quickstart=~~
	~~Keep in mind you might want to use dedicated IPs for sync, so define those in /etc/hosts~~
	~~On both nodes~~
	~~#set password~~
	passwd hacluster		passwd hacluster

Line 42:		Line 48:
	systemctl enable pcsd.service		systemctl enable pcsd.service



			= Commands/tools =

			*crm
	~~=Commands/tools=~~		*crmadmin
			*cibadm
			*pcs
			*[[Corosync\|corosync]]

	*crm		= Useful commands =
	*crmadmin
	*cibadm		== save entire config ==
	*pcs
	*[[corosync]]

	~~=Useful commands=~~
	~~==save entire config==~~
	pcs config backup configfile		pcs config backup configfile

	==Dump entire crm==		== Dump entire crm ==

	cibadm -Q		cibadm -Q


			= HOWTO =

			==Groups==
			===Add existing resource to group===

			pcs resource group add GROUPID RESOURCEID



Line 239:		Line 257:

	== moving RES away after 1000000 failures ==		== moving RES away after 1000000 failures ==

	If failcount is 0, try pcs resource cleanup		If failcount is 0, try pcs resource cleanup

Tony at 17:10, 2 June 2021

2021-06-02T17:10:24Z

Show changes

Tony at 11:10, 1 June 2021

2021-06-01T11:10:24Z

← Older revision		Revision as of 11:10, 1 June 2021
Line 1:		Line 1:
	uses [[Corosync]] or [[heartbeat]], (it seems) corosync is the one to go for.		uses [[Corosync]] or [[heartbeat]], (it seems) corosync is the one to go for.

	=Links=
	*[http://clusterlabs.org/ Cluster Labs]		= Links =
	*[https://clusterlabs.org/quickstart.html pacemaker quickstart]
	*https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md		*[http://clusterlabs.org/ Cluster Labs]
	*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_pacemaker_architecture.html Pacemaker Architecture]		*[http://www.linux-ha.org/doc/man-pages/ap-ra-man-pages.html Linux-HA manpages]
	*[http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/ Pacemaker explained]		*[https://clusterlabs.org/quickstart.html pacemaker quickstart]
	*[http://fibrevillage.com/sysadmin/304-pcs-command-reference pcs command resference]		*[https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md https://github.com/ClusterLabs/pacemaker/blob/master/doc/pcs-crmsh-quick-ref.md]
	*[http://fibrevillage.com/sysadmin/321-pacemaker-and-pcs-on-linux-example-managing-cluster-resource Pacemaker and pcs on Linux example, managing cluster resource]		*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_pacemaker_architecture.html Pacemaker Architecture]
	*[http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs Building a high-available failover cluster with Pacemaker, Corosync & PCS]		*[http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/ Pacemaker explained]
	*[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Administration/index.html HIGH AVAILABILITY ADD-ON ADMINISTRATION]		*[http://fibrevillage.com/sysadmin/304-pcs-command-reference pcs command resference]
	*[https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-corosync-pacemaker-and-floating-ips-on-ubuntu-14-04 How To Create a High Availability Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04]		*[http://fibrevillage.com/sysadmin/321-pacemaker-and-pcs-on-linux-example-managing-cluster-resource Pacemaker and pcs on Linux example, managing cluster resource]
	*http://fibrevillage.com/sysadmin/304-pcs-command-reference		*[http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs Building a high-available failover cluster with Pacemaker, Corosync & PCS]
	*http://wiki.lustre.org/Creating_Pacemaker_Resources_for_Lustre_Storage_Services		*[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Administration/index.html HIGH AVAILABILITY ADD-ON ADMINISTRATION]
	*[http://fibrevillage.com/sysadmin/321-pacemaker-and-pcs-on-linux-example-managing-cluster-resource Pacemaker and pcs on Linux example, managing cluster resource]		*[https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-corosync-pacemaker-and-floating-ips-on-ubuntu-14-04 How To Create a High Availability Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04]
	*[http://djlab.com/2013/04/pacemaker-corosync-drbd-cheatsheet/ Cheatsheet]		*[http://fibrevillage.com/sysadmin/304-pcs-command-reference http://fibrevillage.com/sysadmin/304-pcs-command-reference]
	*[https://redhatlinux.guru/2018/05/22/pacemaker-cheat-sheet/ Pacemaker cheat sheet]		*[http://wiki.lustre.org/Creating_Pacemaker_Resources_for_Lustre_Storage_Services http://wiki.lustre.org/Creating_Pacemaker_Resources_for_Lustre_Storage_Services]
	*[https://www.freesoftwareservers.com/wiki/pcs-tips-n-tricks-constraints-delete-resources-3965539.html PCS tips&tricks]		*[http://fibrevillage.com/sysadmin/321-pacemaker-and-pcs-on-linux-example-managing-cluster-resource Pacemaker and pcs on Linux example, managing cluster resource]
	*[https://www.hastexo.com/resources/hints-and-kinks/mandatory-and-advisory-ordering-pacemaker/ Mandatory and advisory ordering in Pacemaker]		*[http://djlab.com/2013/04/pacemaker-corosync-drbd-cheatsheet/ Cheatsheet]
	*http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_specifying_a_preferred_location.html		*[https://redhatlinux.guru/2018/05/22/pacemaker-cheat-sheet/ Pacemaker cheat sheet]
	*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-sets-ordering.html resource sets]		*[https://www.freesoftwareservers.com/wiki/pcs-tips-n-tricks-constraints-delete-resources-3965539.html PCS tips&tricks]
	*[https://www.alteeve.com/w/History_of_HA_Clustering History of HA clustering]		*[https://www.hastexo.com/resources/hints-and-kinks/mandatory-and-advisory-ordering-pacemaker/ Mandatory and advisory ordering in Pacemaker]
	*[http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html The OCF Resource Agent Developer’s Guide]		*[http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_specifying_a_preferred_location.html http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_specifying_a_preferred_location.html]
	*https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html]		*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-sets-ordering.html resource sets]
			*[https://www.alteeve.com/w/History_of_HA_Clustering History of HA clustering]
			*[http://www.linux-ha.org/doc/dev-guides/ra-dev-guide.html The OCF Resource Agent Developer’s Guide]
			*[https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administration/_visualizing_the_action_sequence.html]]
	*[https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html#sec-ha-maint-shutdown-node Implications of Taking Down a Cluster Node]		*[https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-maintenance.html#sec-ha-maint-shutdown-node Implications of Taking Down a Cluster Node]

Tony: /* FAQ */

2020-08-07T13:06:09Z

FAQ

← Older revision		Revision as of 13:06, 7 August 2020
Line 182:		Line 182:
	You're supposed to use `hostname` in the 'on ...' bit		You're supposed to use `hostname` in the 'on ...' bit



			==corosync: active/disabled==
			As far as i can tell means some resources have been disabled

	==ocf-exit-reason:Undefined iSCSI target implementation==		==ocf-exit-reason:Undefined iSCSI target implementation==
	Install scsi-target-utils		Install scsi-target-utils

Tony: /* FAQ */

2020-07-27T10:53:02Z

FAQ

← Older revision		Revision as of 10:53, 27 July 2020
Line 179:		Line 179:
	Still not clear		Still not clear

	==drbdadm create-md test3		==drbdadm create-md test3 'test3' not defined in your config (for this host).==
	'test3' not defined in your config (for this host).==
	You're supposed to use `hostname` in the 'on ...' bit		You're supposed to use `hostname` in the 'on ...' bit


			==ocf-exit-reason:Undefined iSCSI target implementation==
			Install scsi-target-utils