Scroll to navigation

CRM(8) System Administration Utilities CRM(8)

NAME

crm - Initialize cluster

DESCRIPTION

usage: init [options] [STAGE]

Initialize a cluster from scratch. This command configures a complete cluster, and can also add additional cluster nodes to the initial one-node cluster using the --nodes option.

optional arguments:

Show this help message
Be quiet (don't describe what's happening, just do it)
Answer "yes" to all prompts (use with caution, this is destructive, especially those storage related configurations and stages. The /root/.ssh/id_rsa key will be overwritten unless the option "--no-overwritesshkey" is used)
Set the name of the configured cluster.
Additional nodes to add to the created cluster. May include the current node, which will always be the initial cluster node.
Enable SBD even if no SBD device is configured (diskless mode)
Use the given watchdog device or driver name
Avoid "/root/.ssh/id_rsa" overwrite if "-y" option is used (False by default)

Network configuration:

Options for configuring the network and messaging layer.
Bind to IP address on interface IF. Use -i second time for second interface
Configure corosync to communicate over unicast (UDP), and not multicast. Default is multicast unless an environment where multicast cannot be used is detected.
Configure IP address as an administration virtual IP
Configure corosync with second heartbeat line
Configure corosync use IPv6

QDevice configuration:

QDevice participates in quorum decisions. With the assistance of a third-party arbitrator Qnetd, it provides votes so that a cluster is able to sustain more node failures than standard quorum rules allow. It is recommended for clusters with an even number of nodes and highly recommended for 2 node clusters.
Options for configuring QDevice and QNetd.
HOST or IP of the QNetd server to be used
--qdevice-port PORT
TCP PORT of QNetd server (default:5403)
--qdevice-algo ALGORITHM
QNetd decision ALGORITHM (ffsplit/lms, default:ffsplit)
--qdevice-tie-breaker TIE_BREAKER
QNetd TIE_BREAKER (lowest/highest/valid_node_id, default:lowest)
--qdevice-tls TLS
Whether using TLS on QDevice/QNetd (on/off/required, default:on)
--qdevice-heuristics COMMAND
COMMAND to run with absolute path. For multiple commands, use ";" to separate (details about heuristics can see man 8 corosync-qdevice)
--qdevice-heuristics-mode MODE
MODE of operation of heuristics (on/sync/off, default:sync)

Storage configuration:

Options for configuring shared storage.
Block device to use for SBD fencing, use ";" as separator or -s multiple times for multi path (up to 3 devices)
Block device to use for OCFS2; When using Cluster LVM2 to manage the shared storage, user can specify one or multiple raw disks, use ";" as separator or -o multiple times for multi path (must specify -C option) NOTE: this is a Technical Preview
Use Cluster LVM2 (only valid together with -o option) NOTE: this is a Technical Preview
Mount point for OCFS2 device (default is /srv/clusterfs, only valid together with -o option) NOTE: this is a Technical Preview

Stage can be one of:

Create SSH keys for passwordless SSH between cluster nodes
Configure csync2
Configure corosync
Configure SBD (requires -s <dev>)
Bring the cluster online
Configure OCFS2 (requires -o <dev>) NOTE: this is a Technical Preview
Create volume group and filesystem (ocfs2 template only,
requires -o <dev>) NOTE: this stage is an alias of ocfs2 stage
Create administration virtual IP (optional)
Configure qdevice and qnetd

Note:

- If stage is not specified, the script will run through each stage
in sequence, with prompts for required information.

SEE ALSO

The full documentation for crm is maintained as a Texinfo manual. If the info and crm programs are properly installed at your site, the command

info crm

should give you access to the complete manual.

December 2021 crm 0.5