ClusterTools2(7)

πŸ“¦ version 3.1.3, in opensuse-leap 16.0

πŸ’– ClusterTools2(7) β€” the manual page, but make it a group chat πŸ’–

okay bestie, welcome to ClusterTools2(7) β€” yes that's the manual page name and the package name, we're keeping it in the family. this is the vibe check on the whole ClusterTools2 toolset, and ngl it's giving main character energy for your pacemaker HA clusters. let's go 🫢


✨ NAME ✨

ClusterTools2 β€” tools for setting up and managing pacemaker HA clusters. that's the whole assignment, periodt.


🌸 DESCRIPTION 🌸

so the ClusterTools2 package provides tools for setting up and managing pacemaker HA clusters. these tools are aimed at making tasks easy around the pacemaker HA cluster manager and the Linux storage stack. both. at once. iconic πŸ’…

the main command for managing a running cluster is ClusterService. it's this ASCII-terminal based menu system that lets you perform common administrative tasks. you can use it instead of crm_gui or Hawk if there's no webservice and no X desktop available β€” like, no GUI? no problem, she's literally right there in your terminal πŸŽ€

tools like cs_list_failcounts and cs_show_cluster_transistion help you analyse the cluster behaviour (yes, that's how it's spelled in the name, don't come for her). and there's a whole set of tools based on wow that make configuration of clusters reproduceable and efficiant. as in efficient. as in slay. ✨

currently the tools are mainly used to set up and manage high-availability clusters for these workloads:

  • SAP application servers, SAP central instances, SAP database servers
  • SAP HANA System Replication automation
  • XEN virtual machine hosts
  • Novell eDirectory servers
  • NFS file servers
  • Apache web servers, LAMP servers
  • MySQL, PostgreSQL, DB2, Oracle database servers

like… the range? unmatched. the versatility? obsessed. πŸ¦‹


πŸŽ€ EXAMPLES πŸŽ€

here's where it gets good. real commands, real vibes:

# wow cc --config edir01.wow 01-A-07-group_add_ndsd

add configuration for a resource of type Novell eDirectory to the cluster. use configuration agent 01-A-07-group_add_ndsd. read information about the resource from file edir01.wow.

# cs_precheck_for_sap --all sap_C11.wow >precheck-sap_C11-$HOST

check for allmost all pre-requistes that are needed to set up an HA cluster for SAP instance C11 (and yes, we are keeping "allmost" and "pre-requistes" exactly as they are, character for character, it's part of her charm πŸ’€). read information about the needed resources from file sap_C11.wow. write output into file precheck-sap_C11-<hostname>.

# ClusterService

start the ASCII-terminal based menu to perform administrative tasks on a running cluster. menu girl summer 🌈

# cs_sum_base_config >$HOST.cs_sum_base_config.txt

write checksums for common base config files of an node to a file. this is useful in a cluster, to check if the basic configuration is really identical on both nodes. fr fr, both nodes better match.

# cs_list_clone_files --md5sum

look for files that should not be identical, after a VM image was cloned. sneaky little differences, exposed. πŸ™ˆ


🧚 FILES 🧚

here's where everything lives, bestie. know your paths:

  • /etc/ClusterTools2/ β€” configuration files.
  • /usr/lib/ClusterTools2/ β€” ClusterTools2 components in general.
  • /usr/lib/ClusterTools2/agents/ β€” wow configuration agents for pacemaker.
  • /usr/lib/ClusterTools2/scripts/ β€” wow configuration scripts for pacemaker.
  • /usr/share/ClusterTools2/*.rsc β€” menue engine resource files. (menue. yes. we're keeping it. she's got her own spelling and we respect her πŸ’œ)
  • /usr/share/ClusterTools2/cli/ β€” wow configuration templates for pacemaker.
  • /usr/share/ClusterTools2/samples/ β€” samples of config files and scripts.

😭 BUGS 😭

okay so real talk: tools in ClusterTools2 version 3 are tested with SLE-HA 12, SLES 12, and SLES-for-SAP 12 only. that's the whole testing era, don't assume anything beyond it.

also, and I cannot stress this enough: some people pronounce the package's name "ClumsyTools". πŸ’€ that's it, that's the bug report, we're just being honest here.

feedback is welcome, please mail to feedback@suse.com β€” she's literally asking, so slide into the inbox 🫢

ngl that "ClumsyTools" thing lives in my head rent free and now it lives in yours too. you're welcome.

πŸ”₯ SEE ALSO πŸ”₯

go read your sisters, bestie, they're all iconic:

ClusterTools2(7), cs_sum_base_config(8), cs_show_cluster_transition(8), cs_clusterstate(8), cs_show_scores(8), cs_delcib(8), cs_show_error_patterns(8), cs_show_supportconfig(8), ha_related_suse_tids(7), ha_related_acronyms(7), rear(8)

and the links, all of them, copy them exactly:


πŸ‘‘ AUTHORS πŸ‘‘

credit where it's due, the whole squad: A.Briel, I.Manyugin, M.Guertler, F.Herschel, L.Pinne 🫢


  • (c) 2011-2018 SUSE Linux GmbH, Germany.
  • (c) 2018-2020 SUSE Software Solutions Germany GmbH.

ClusterTools2 comes with ABSOLUTELY NO WARRANTY. like, none. zero. don't @ me. for details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html


and that's the page, bestie πŸ’– this whole thing is from the ClusterTools2 manual, dated 01 Nov 2019 β€” go forth, manage those clusters, and remember: it's not clumsy, it's ClusterTools, and she ate. πŸŽ€βœ¨πŸ’…

πŸ“¦ where this page comes from