Page MenuHomeClusterLabs Projects
Files F1842531

No OneTemporary
Actions

View Options

diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Cluster-Setup.txt b/doc/Clusters_from_Scratch/en-US/Ch-Cluster-Setup.txt
new file mode 100644
index 0000000000..9cf6fbcce0
--- /dev/null
+++ b/doc/Clusters_from_Scratch/en-US/Ch-Cluster-Setup.txt
@@ -0,0 +1,333 @@
+:compat-mode: legacy
+= Set up a Cluster =
+
+== Simplify Administration With a Cluster Shell ==
+
+In the dark past, configuring Pacemaker required the administrator to
+read and write XML. In true UNIX style, there were also a number of
+different commands that specialized in different aspects of querying
+and updating the cluster.
+
+In addition, the various components of the cluster stack (corosync, pacemaker,
+etc.) had to be configured separately, with different configuration tools and
+formats.
+
+All of that has been greatly simplified with the creation of higher-level tools,
+whether command-line or GUIs, that hide all the mess underneath.
+
+Command-line cluster shells take all the individual aspects required for
+managing and configuring a cluster, and pack them into one simple-to-use
+command-line tool.
+
+They even allow you to queue up several changes at once and commit
+them all at once.
+
+Two popular command-line shells are `pcs` and `crmsh`. Clusters from Scratch is
+based on `pcs` because it comes with CentOS, but both have similar
+functionality. Choosing a shell or GUI is a matter of personal preference and
+what comes with (and perhaps is supported by) your choice of operating system.
+
+
+== Install the Cluster Software ==
+
+Fire up a shell on both nodes and run the following to install pacemaker, pcs,
+and some other command-line tools that will make our lives easier:
+----
+# yum install -y pacemaker pcs psmisc policycoreutils-python
+----
+
+[IMPORTANT]
+===========
+This document will show commands that need to be executed on both nodes
+with a simple `#` prompt. Be sure to run them on each node individually.
+===========
+
+[NOTE]
+===========
+This document uses `pcs` for cluster management. Other alternatives,
+such as `crmsh`, are available, but their syntax
+will differ from the examples used here.
+===========
+
+== Configure the Cluster Software ==
+
+=== Allow cluster services through firewall ===
+
+On each node, allow cluster-related services through the local firewall:
+----
+# firewall-cmd --permanent --add-service=high-availability
+success
+# firewall-cmd --reload
+success
+----
+
+[NOTE]
+======
+If you are using iptables directly, or some other firewall solution besides
+firewalld, simply open the following ports, which can be used by various
+clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405.
+
+If you run into any problems during testing, you might want to disable
+the firewall and SELinux entirely until you have everything working.
+This may create significant security issues and should not be performed on
+machines that will be exposed to the outside world, but may be appropriate
+during development and testing on a protected host.
+
+To disable security measures:
+----
+[root@pcmk-1 ~]# setenforce 0
+[root@pcmk-1 ~]# sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config
+[root@pcmk-1 ~]# systemctl mask firewalld.service
+[root@pcmk-1 ~]# systemctl stop firewalld.service
+[root@pcmk-1 ~]# iptables --flush
+----
+======
+
+=== Enable pcs Daemon ===
+
+Before the cluster can be configured, the pcs daemon must be started and enabled
+to start at boot time on each node. This daemon works with the pcs command-line interface
+to manage synchronizing the corosync configuration across all nodes in the cluster.
+
+Start and enable the daemon by issuing the following commands on each node:
+
+----
+# systemctl start pcsd.service
+# systemctl enable pcsd.service
+Created symlink from /etc/systemd/system/multi-user.target.wants/pcsd.service to /usr/lib/systemd/system/pcsd.service.
+----
+
+The installed packages will create a *hacluster* user with a disabled password.
+While this is fine for running `pcs` commands locally,
+the account needs a login password in order to perform such tasks as syncing
+the corosync configuration, or starting and stopping the cluster on other nodes.
+
+This tutorial will make use of such commands,
+so now we will set a password for the *hacluster* user, using the same password
+on both nodes:
+
+----
+# passwd hacluster
+Changing password for user hacluster.
+New password:
+Retype new password:
+passwd: all authentication tokens updated successfully.
+----
+
+[NOTE]
+===========
+Alternatively, to script this process or set the password on a
+different machine from the one you're logged into, you can use
+the `--stdin` option for `passwd`:
+
+----
+[root@pcmk-1 ~]# ssh pcmk-2 -- 'echo mysupersecretpassword | passwd --stdin hacluster'
+----
+===========
+
+=== Configure Corosync ===
+
+On either node, use `pcs cluster auth` to authenticate as the *hacluster* user:
+
+----
+[root@pcmk-1 ~]# pcs cluster auth pcmk-1 pcmk-2
+Username: hacluster
+Password:
+pcmk-2: Authorized
+pcmk-1: Authorized
+----
+
+.Note
+[NOTE]
+====
+In Fedora 29 and CentOS 8.0, the command has been changed to `pcs host auth`:
+----
+[root@pcmk-1 ~]# pcs host auth pcmk-1 pcmk-2
+Username: hacluster
+Password:
+pcmk-2: Authorized
+pcmk-1: Authorized
+----
+====
+
+Next, use `pcs cluster setup` on the same node to generate and synchronize the
+corosync configuration:
+----
+[root@pcmk-1 ~]# pcs cluster setup --name mycluster pcmk-1 pcmk-2
+Destroying cluster on nodes: pcmk-1, pcmk-2...
+pcmk-2: Stopping Cluster (pacemaker)...
+pcmk-1: Stopping Cluster (pacemaker)...
+pcmk-1: Successfully destroyed cluster
+pcmk-2: Successfully destroyed cluster
+
+Sending 'pacemaker_remote authkey' to 'pcmk-1', 'pcmk-2'
+pcmk-2: successful distribution of the file 'pacemaker_remote authkey'
+pcmk-1: successful distribution of the file 'pacemaker_remote authkey'
+Sending cluster config files to the nodes...
+pcmk-1: Succeeded
+pcmk-2: Succeeded
+
+Synchronizing pcsd certificates on nodes pcmk-1, pcmk-2...
+pcmk-2: Success
+pcmk-1: Success
+Restarting pcsd on the nodes in order to reload the certificates...
+pcmk-2: Success
+pcmk-1: Success
+----
+
+.Note
+[NOTE]
+====
+In Fedora 29 and CentOS 8.0, the syntax has been changed and the +--name+ option
+has been dropped:
+----
+[root@pcmk-1 ~]# pcs cluster setup mycluster pcmk-1 pcmk-2
+No addresses specified for host 'pcmk-1', using 'pcmk-1'
+No addresses specified for host 'pcmk-2', using 'pcmk-2'
+Destroying cluster on hosts: 'pcmk-1', 'pcmk-2'...
+pcmk-1: Successfully destroyed cluster
+pcmk-2: Successfully destroyed cluster
+Requesting remove 'pcsd settings' from 'pcmk-1', 'pcmk-2'
+pcmk-1: successful removal of the file 'pcsd settings'
+pcmk-2: successful removal of the file 'pcsd settings'
+Sending 'corosync authkey', 'pacemaker authkey' to 'pcmk-1', 'pcmk-2'
+pcmk-2: successful distribution of the file 'corosync authkey'
+pcmk-2: successful distribution of the file 'pacemaker authkey'
+pcmk-1: successful distribution of the file 'corosync authkey'
+pcmk-1: successful distribution of the file 'pacemaker authkey'
+Synchronizing pcsd SSL certificates on nodes 'pcmk-1', 'pcmk-2'...
+pcmk-1: Success
+pcmk-2: Success
+Sending 'corosync.conf' to 'pcmk-1', 'pcmk-2'
+pcmk-2: successful distribution of the file 'corosync.conf'
+pcmk-1: successful distribution of the file 'corosync.conf'
+Cluster has been successfully set up.
+----
+====
+
+If you received an authorization error for either of those commands, make
+sure you configured the *hacluster* user account on each node
+with the same password.
+
+[NOTE]
+======
+If you are not using `pcs` for cluster administration,
+follow whatever procedures are appropriate for your tools
+to create a corosync.conf and copy it to all nodes.
+
+The `pcs` command will configure corosync to use UDP unicast transport; if you
+choose to use multicast instead, choose a multicast address carefully.
+footnote:[For some subtle issues, see
+http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html[Topics
+in High-Performance Messaging: Multicast Address Assignment] or the more detailed treatment in
+https://www.cisco.com/c/dam/en/us/support/docs/ip/ip-multicast/ipmlt_wp.pdf[Cisco's
+Guidelines for Enterprise IP Multicast Address Allocation].]
+======
+
+The final corosync.conf configuration on each node should look
+something like the sample in <<ap-corosync-conf>>.
+
+== Explore pcs ==
+
+Start by taking some time to familiarize yourself with what `pcs` can do.
+
+----
+[root@pcmk-1 ~]# pcs
+
+Usage: pcs [-f file] [-h] [commands]...
+Control and configure pacemaker and corosync.
+
+Options:
+ -h, --help Display usage and exit.
+ -f file Perform actions on file instead of active CIB.
+ --debug Print all network traffic and external commands run.
+ --version Print pcs version information. List pcs capabilities if
+ --full is specified.
+ --request-timeout Timeout for each outgoing request to another node in
+ seconds. Default is 60s.
+ --force Override checks and errors, the exact behavior depends on
+ the command. WARNING: Using the --force option is
+ strongly discouraged unless you know what you are doing.
+
+Commands:
+ cluster Configure cluster options and nodes.
+ resource Manage cluster resources.
+ stonith Manage fence devices.
+ constraint Manage resource constraints.
+ property Manage pacemaker properties.
+ acl Manage pacemaker access control lists.
+ qdevice Manage quorum device provider on the local host.
+ quorum Manage cluster quorum settings.
+ booth Manage booth (cluster ticket manager).
+ status View cluster status.
+ config View and manage cluster configuration.
+ pcsd Manage pcs daemon.
+ node Manage cluster nodes.
+ alert Manage pacemaker alerts.
+
+----
+
+As you can see, the different aspects of cluster management are separated
+into categories. To discover the functionality available in each of these
+categories, one can issue the command +pcs pass:[<replaceable>category</replaceable>] help+. Below
+is an example of all the options available under the status category.
+
+----
+[root@pcmk-1 ~]# pcs status help
+
+Usage: pcs status [commands]...
+View current cluster and resource status
+Commands:
+ [status] [--full | --hide-inactive]
+ View all information about the cluster and resources (--full provides
+ more details, --hide-inactive hides inactive resources).
+
+ resources [<resource id> | --full | --groups | --hide-inactive]
+ Show all currently configured resources or if a resource is specified
+ show the options for the configured resource. If --full is specified,
+ all configured resource options will be displayed. If --groups is
+ specified, only show groups (and their resources). If --hide-inactive
+ is specified, only show active resources.
+
+ groups
+ View currently configured groups and their resources.
+
+ cluster
+ View current cluster status.
+
+ corosync
+ View current membership information as seen by corosync.
+
+ quorum
+ View current quorum status.
+
+ qdevice <device model> [--full] [<cluster name>]
+ Show runtime status of specified model of quorum device provider. Using
+ --full will give more detailed output. If <cluster name> is specified,
+ only information about the specified cluster will be displayed.
+
+ nodes [corosync | both | config]
+ View current status of nodes from pacemaker. If 'corosync' is
+ specified, view current status of nodes from corosync instead. If
+ 'both' is specified, view current status of nodes from both corosync &
+ pacemaker. If 'config' is specified, print nodes from corosync &
+ pacemaker configuration.
+
+ pcsd [<node>]...
+ Show current status of pcsd on nodes specified, or on all nodes
+ configured in the local cluster if no nodes are specified.
+
+ xml
+ View xml version of status (output from crm_mon -r -1 -X).
+
+----
+
+Additionally, if you are interested in the version and
+supported cluster stack(s) available with your Pacemaker
+installation, run:
+
+----
+[root@pcmk-1 ~]# pacemakerd --features
+Pacemaker 1.1.18-11.el7_5.3 (Build: 2b07d5c5a9)
+ Supporting v3.0.14: generated-manpages agent-manpages ncurses libqb-logging libqb-ipc systemd nagios corosync-native atomic-attrd acls
+----
diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt b/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt
index 8861dedf74..a91824ac32 100644
--- a/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt
+++ b/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt
@@ -1,557 +1,358 @@
:compat-mode: legacy
= Installation =
== Install &DISTRO; &DISTRO_VERSION; ==
=== Boot the Install Image ===
Download the 4GB
http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1804.iso[&DISTRO;
&DISTRO_VERSION; DVD ISO]. Use the image to boot a virtual machine, or
burn it to a DVD or USB drive and boot a physical server from that.
After starting the installation, select your language and keyboard layout at
the welcome screen.
.&DISTRO; &DISTRO_VERSION; Installation Welcome Screen
image::images/Welcome.png["Welcome to &DISTRO; &DISTRO_VERSION;",align="center",scaledwidth="100%"]
=== Installation Options ===
At this point, you get a chance to tweak the default installation options.
.&DISTRO; &DISTRO_VERSION; Installation Summary Screen
image::images/Installer.png["&DISTRO; &DISTRO_VERSION; Installation Summary",align="center",scaledwidth="100%"]
Ignore the *SOFTWARE SELECTION* section (try saying that 10 times quickly). The
*Infrastructure Server* environment does have add-ons with much of the software
we need, but we will leave it as a *Minimal Install* here, so that we can see
exactly what software is required later.
=== Configure Network ===
In the *NETWORK & HOSTNAME* section:
- Edit *Host Name:* as desired. For this example, we will use
*pcmk-1.localdomain*.
- Select your network device, press *Configure...*, and manually assign a fixed
IP address. For this example, we'll use 192.168.122.101 under *IPv4 Settings*
(with an appropriate netmask, gateway and DNS server).
- Flip the switch to turn your network device on, and press *Done*.
.&DISTRO; &DISTRO_VERSION; Network Interface Screen
image::images/Editing-eth0.png["&DISTRO; &DISTRO_VERSION; Editing eth0",align="center",scaledwidth="100%"]
[IMPORTANT]
===========
Do not accept the default network settings.
Cluster machines should never obtain an IP address via DHCP, because
DHCP's periodic address renewal will interfere with corosync.
===========
=== Configure Disk ===
By default, the installer's automatic partitioning will use LVM (which allows
us to dynamically change the amount of space allocated to a given partition).
However, it allocates all free space to the +/+ (aka. *root*) partition, which
cannot be reduced in size later (dynamic increases are fine).
In order to follow the DRBD and GFS2 portions of this guide, we need to reserve
space on each machine for a replicated volume.
Enter the *INSTALLATION DESTINATION* section, ensure the hard drive you want to
install to is selected, select *I will configure partitioning*, and press *Done*.
In the *MANUAL PARTITIONING* screen that comes next, click the option to create
mountpoints automatically. Select the +/+ mountpoint, and reduce the desired
capacity by 1GiB or so. Select *Modify...* by the volume group name, and change
the *Size policy:* to *As large as possible*, to make the reclaimed space
available inside the LVM volume group. We'll add the additional volume later.
.&DISTRO; &DISTRO_VERSION; Manual Partitioning Screen
image::images/Partitioning.png["&DISTRO; &DISTRO_VERSION; Partitioning",align="center",scaledwidth="100%"]
Press *Done*, then *Accept changes*.
=== Configure Time Synchronization ===
It is highly recommended to enable NTP on your cluster nodes. Doing so
ensures all nodes agree on the current time and makes reading log files
significantly easier.
&DISTRO; will enable NTP automatically. If you want to change any time-related
settings (such as time zone or NTP server), you can do this in the
*TIME & DATE* section.
=== Finish Install ===
Select *Begin Installation*. Once it completes, set a root password, and reboot
as instructed. For the purposes of this document, it is not necessary to create
any additional users. After the node reboots, you'll see a login prompt on
the console. Login using *root* and the password you created earlier.
.&DISTRO; &DISTRO_VERSION; Console Prompt
image::images/Console.png["&DISTRO; &DISTRO_VERSION; Console",align="center",scaledwidth="100%"]
[NOTE]
======
From here on, we're going to be working exclusively from the terminal.
======
== Configure the OS ==
=== Verify Networking ===
Ensure that the machine has the static IP address you configured earlier.
-----
[root@pcmk-1 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:8e:eb:41 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.101/24 brd 192.168.122.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::e45:c99b:34c0:c657/64 scope link noprefixroute
valid_lft forever preferred_lft forever
-----
[NOTE]
=====
If you ever need to change the node's IP address from the command line, follow
these instructions, replacing *${device}* with the name of your network device:
....
[root@pcmk-1 ~]# vi /etc/sysconfig/network-scripts/ifcfg-${device} # manually edit as desired
[root@pcmk-1 ~]# nmcli dev disconnect ${device}
[root@pcmk-1 ~]# nmcli con reload ${device}
[root@pcmk-1 ~]# nmcli con up ${device}
....
This makes *NetworkManager* aware that a change was made on the config file.
=====
Next, ensure that the routes are as expected:
-----
[root@pcmk-1 ~]# ip route
default via 192.168.122.1 dev eth0 proto static metric 100
192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.101 metric 100
-----
If there is no line beginning with *default via*, then you may need to add a line such as
[source,Bash]
GATEWAY="192.168.122.1"
to the device configuration using the same process as described above for
changing the IP address.
Now, check for connectivity to the outside world. Start small by
testing whether we can reach the gateway we configured.
-----
[root@pcmk-1 ~]# ping -c 1 192.168.122.1
PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data.
64 bytes from 192.168.122.1: icmp_seq=1 ttl=64 time=0.254 ms
--- 192.168.122.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.254/0.254/0.254/0.000 ms
-----
Now try something external; choose a location you know should be available.
-----
[root@pcmk-1 ~]# ping -c 1 www.clusterlabs.org
PING oss-uk-1.clusterlabs.org (109.74.197.241) 56(84) bytes of data.
64 bytes from oss-uk-1.clusterlabs.org (109.74.197.241): icmp_seq=1 ttl=49 time=333 ms
--- oss-uk-1.clusterlabs.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 333.204/333.204/333.204/0.000 ms
-----
=== Login Remotely ===
The console isn't a very friendly place to work from, so we will now
switch to accessing the machine remotely via SSH where we can
use copy and paste, etc.
From another host, check whether we can see the new host at all:
-----
beekhof@f16 ~ # ping -c 1 192.168.122.101
PING 192.168.122.101 (192.168.122.101) 56(84) bytes of data.
64 bytes from 192.168.122.101: icmp_req=1 ttl=64 time=1.01 ms
--- 192.168.122.101 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.012/1.012/1.012/0.000 ms
-----
Next, login as root via SSH.
-----
beekhof@f16 ~ # ssh -l root 192.168.122.101
The authenticity of host '192.168.122.101 (192.168.122.101)' can't be established.
ECDSA key fingerprint is 6e:b7:8f:e2:4c:94:43:54:a8:53:cc:20:0f:29:a4:e0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.122.101' (ECDSA) to the list of known hosts.
root@192.168.122.101's password:
Last login: Tue Aug 11 13:14:39 2015
[root@pcmk-1 ~]#
-----
=== Apply Updates ===
Apply any package updates released since your installation image was created:
----
[root@pcmk-1 ~]# yum update
----
=== Use Short Node Names ===
During installation, we filled in the machine's fully qualified domain
name (FQDN), which can be rather long when it appears in cluster logs and
status output. See for yourself how the machine identifies itself:
(((Nodes, short name)))
----
[root@pcmk-1 ~]# uname -n
pcmk-1.localdomain
----
(((Nodes, Domain name (Query))))
We can use the `hostnamectl` tool to strip off the domain name:
----
[root@pcmk-1 ~]# hostnamectl set-hostname $(uname -n | sed s/\\..*//)
----
(((Nodes, Domain name (Remove from host name))))
Now, check that the machine is using the correct name:
----
[root@pcmk-1 ~]# uname -n
pcmk-1
----
You may want to reboot to ensure all updates take effect.
== Repeat for Second Node ==
Repeat the Installation steps so far, so that you have two
nodes ready to have the cluster software installed.
For the purposes of this document, the additional node is called
pcmk-2 with address 192.168.122.102.
== Configure Communication Between Nodes ==
=== Configure Host Name Resolution ===
Confirm that you can communicate between the two new nodes:
----
[root@pcmk-1 ~]# ping -c 3 192.168.122.102
PING 192.168.122.102 (192.168.122.102) 56(84) bytes of data.
64 bytes from 192.168.122.102: icmp_seq=1 ttl=64 time=0.343 ms
64 bytes from 192.168.122.102: icmp_seq=2 ttl=64 time=0.402 ms
64 bytes from 192.168.122.102: icmp_seq=3 ttl=64 time=0.558 ms
--- 192.168.122.102 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.343/0.434/0.558/0.092 ms
----
Now we need to make sure we can communicate with the machines by their
name. If you have a DNS server, add additional entries for the two
machines. Otherwise, you'll need to add the machines to +/etc/hosts+
on both nodes. Below are the entries for my cluster nodes:
----
[root@pcmk-1 ~]# grep pcmk /etc/hosts
192.168.122.101 pcmk-1.clusterlabs.org pcmk-1
192.168.122.102 pcmk-2.clusterlabs.org pcmk-2
----
We can now verify the setup by again using ping:
----
[root@pcmk-1 ~]# ping -c 3 pcmk-2
PING pcmk-2.clusterlabs.org (192.168.122.101) 56(84) bytes of data.
64 bytes from pcmk-1.clusterlabs.org (192.168.122.101): icmp_seq=1 ttl=64 time=0.164 ms
64 bytes from pcmk-1.clusterlabs.org (192.168.122.101): icmp_seq=2 ttl=64 time=0.475 ms
64 bytes from pcmk-1.clusterlabs.org (192.168.122.101): icmp_seq=3 ttl=64 time=0.186 ms
--- pcmk-2.clusterlabs.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.164/0.275/0.475/0.141 ms
----
=== Configure SSH ===
SSH is a convenient and secure way to copy files and perform commands
remotely. For the purposes of this guide, we will create a key without a
password (using the -N option) so that we can perform remote actions
without being prompted.
(((SSH)))
[WARNING]
=========
Unprotected SSH keys (those without a password) are not recommended for servers exposed to the outside world.
We use them here only to simplify the demo.
=========
Create a new key and allow anyone with that key to log in:
.Creating and Activating a new SSH Key
----
[root@pcmk-1 ~]# ssh-keygen -t dsa -f ~/.ssh/id_dsa -N ""
Generating public/private dsa key pair.
Your identification has been saved in /root/.ssh/id_dsa.
Your public key has been saved in /root/.ssh/id_dsa.pub.
The key fingerprint is:
91:09:5c:82:5a:6a:50:08:4e:b2:0c:62:de:cc:74:44 root@pcmk-1.clusterlabs.org
The key's randomart image is:
+--[ DSA 1024]----+
|==.ooEo.. |
|X O + .o o |
| * A + |
| + . |
| . S |
| |
| |
| |
| |
+-----------------+
[root@pcmk-1 ~]# cp ~/.ssh/id_dsa.pub ~/.ssh/authorized_keys
----
(((Creating and Activating a new SSH Key)))
Install the key on the other node:
----
[root@pcmk-1 ~]# scp -r ~/.ssh pcmk-2:
The authenticity of host 'pcmk-2 (192.168.122.102)' can't be established.
ECDSA key fingerprint is SHA256:63xNPkPYq98rYznf3T9QYJAzlaGiAsSgFVNHOZjPWqc.
ECDSA key fingerprint is MD5:d9:bf:6e:32:88:be:47:3d:96:f1:96:27:65:05:0b:c3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'pcmk-2,192.168.122.102' (ECDSA) to the list of known hosts.
root@pcmk-2's password:
id_dsa
id_dsa.pub
authorized_keys
known_hosts
----
Test that you can now run commands remotely, without being prompted:
----
[root@pcmk-1 ~]# ssh pcmk-2 -- uname -n
pcmk-2
----
-
-== Install the Cluster Software ==
-
-Fire up a shell on both nodes and run the following to install pacemaker, and while
-we're at it, some command-line tools to make our lives easier:
-----
-# yum install -y pacemaker pcs psmisc policycoreutils-python
-----
-
-[IMPORTANT]
-===========
-This document will show commands that need to be executed on both nodes
-with a simple `#` prompt. Be sure to run them on each node individually.
-===========
-
-[NOTE]
-===========
-This document uses `pcs` for cluster management. Other alternatives,
-such as `crmsh`, are available, but their syntax
-will differ from the examples used here.
-===========
-
-== Configure the Cluster Software ==
-
-=== Allow cluster services through firewall ===
-
-On each node, allow cluster-related services through the local firewall:
-----
-# firewall-cmd --permanent --add-service=high-availability
-success
-# firewall-cmd --reload
-success
-----
-
-[NOTE]
-======
-If you are using iptables directly, or some other firewall solution besides
-firewalld, simply open the following ports, which can be used by various
-clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405.
-
-If you run into any problems during testing, you might want to disable
-the firewall and SELinux entirely until you have everything working.
-This may create significant security issues and should not be performed on
-machines that will be exposed to the outside world, but may be appropriate
-during development and testing on a protected host.
-
-To disable security measures:
-----
-[root@pcmk-1 ~]# setenforce 0
-[root@pcmk-1 ~]# sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config
-[root@pcmk-1 ~]# systemctl mask firewalld.service
-[root@pcmk-1 ~]# systemctl stop firewalld.service
-[root@pcmk-1 ~]# iptables --flush
-----
-======
-
-=== Enable pcs Daemon ===
-
-Before the cluster can be configured, the pcs daemon must be started and enabled
-to start at boot time on each node. This daemon works with the pcs command-line interface
-to manage synchronizing the corosync configuration across all nodes in the cluster.
-
-Start and enable the daemon by issuing the following commands on each node:
-
-----
-# systemctl start pcsd.service
-# systemctl enable pcsd.service
-Created symlink from /etc/systemd/system/multi-user.target.wants/pcsd.service to /usr/lib/systemd/system/pcsd.service.
-----
-
-The installed packages will create a *hacluster* user with a disabled password.
-While this is fine for running `pcs` commands locally,
-the account needs a login password in order to perform such tasks as syncing
-the corosync configuration, or starting and stopping the cluster on other nodes.
-
-This tutorial will make use of such commands,
-so now we will set a password for the *hacluster* user, using the same password
-on both nodes:
-
-----
-# passwd hacluster
-Changing password for user hacluster.
-New password:
-Retype new password:
-passwd: all authentication tokens updated successfully.
-----
-
-[NOTE]
-===========
-Alternatively, to script this process or set the password on a
-different machine from the one you're logged into, you can use
-the `--stdin` option for `passwd`:
-
-----
-[root@pcmk-1 ~]# ssh pcmk-2 -- 'echo mysupersecretpassword | passwd --stdin hacluster'
-----
-===========
-
-=== Configure Corosync ===
-
-On either node, use `pcs cluster auth` to authenticate as the *hacluster* user:
-
-----
-[root@pcmk-1 ~]# pcs cluster auth pcmk-1 pcmk-2
-Username: hacluster
-Password:
-pcmk-2: Authorized
-pcmk-1: Authorized
-----
-
-.Note
-[NOTE]
-====
-In Fedora 29 and CentOS 8.0, the command has been changed to `pcs host auth`:
-----
-[root@pcmk-1 ~]# pcs host auth pcmk-1 pcmk-2
-Username: hacluster
-Password:
-pcmk-2: Authorized
-pcmk-1: Authorized
-----
-====
-
-Next, use `pcs cluster setup` on the same node to generate and synchronize the
-corosync configuration:
-----
-[root@pcmk-1 ~]# pcs cluster setup --name mycluster pcmk-1 pcmk-2
-Destroying cluster on nodes: pcmk-1, pcmk-2...
-pcmk-2: Stopping Cluster (pacemaker)...
-pcmk-1: Stopping Cluster (pacemaker)...
-pcmk-1: Successfully destroyed cluster
-pcmk-2: Successfully destroyed cluster
-
-Sending 'pacemaker_remote authkey' to 'pcmk-1', 'pcmk-2'
-pcmk-2: successful distribution of the file 'pacemaker_remote authkey'
-pcmk-1: successful distribution of the file 'pacemaker_remote authkey'
-Sending cluster config files to the nodes...
-pcmk-1: Succeeded
-pcmk-2: Succeeded
-
-Synchronizing pcsd certificates on nodes pcmk-1, pcmk-2...
-pcmk-2: Success
-pcmk-1: Success
-Restarting pcsd on the nodes in order to reload the certificates...
-pcmk-2: Success
-pcmk-1: Success
-----
-
-.Note
-[NOTE]
-====
-In Fedora 29 and CentOS 8.0, the syntax has been changed and the +--name+ option
-has been dropped:
-----
-[root@pcmk-1 ~]# pcs cluster setup mycluster pcmk-1 pcmk-2
-No addresses specified for host 'pcmk-1', using 'pcmk-1'
-No addresses specified for host 'pcmk-2', using 'pcmk-2'
-Destroying cluster on hosts: 'pcmk-1', 'pcmk-2'...
-pcmk-1: Successfully destroyed cluster
-pcmk-2: Successfully destroyed cluster
-Requesting remove 'pcsd settings' from 'pcmk-1', 'pcmk-2'
-pcmk-1: successful removal of the file 'pcsd settings'
-pcmk-2: successful removal of the file 'pcsd settings'
-Sending 'corosync authkey', 'pacemaker authkey' to 'pcmk-1', 'pcmk-2'
-pcmk-2: successful distribution of the file 'corosync authkey'
-pcmk-2: successful distribution of the file 'pacemaker authkey'
-pcmk-1: successful distribution of the file 'corosync authkey'
-pcmk-1: successful distribution of the file 'pacemaker authkey'
-Synchronizing pcsd SSL certificates on nodes 'pcmk-1', 'pcmk-2'...
-pcmk-1: Success
-pcmk-2: Success
-Sending 'corosync.conf' to 'pcmk-1', 'pcmk-2'
-pcmk-2: successful distribution of the file 'corosync.conf'
-pcmk-1: successful distribution of the file 'corosync.conf'
-Cluster has been successfully set up.
-----
-====
-
-If you received an authorization error for either of those commands, make
-sure you configured the *hacluster* user account on each node
-with the same password.
-
-[NOTE]
-======
-If you are not using `pcs` for cluster administration,
-follow whatever procedures are appropriate for your tools
-to create a corosync.conf and copy it to all nodes.
-
-The `pcs` command will configure corosync to use UDP unicast transport; if you
-choose to use multicast instead, choose a multicast address carefully.
-footnote:[For some subtle issues, see
-http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html[Topics
-in High-Performance Messaging: Multicast Address Assignment] or the more detailed treatment in
-https://www.cisco.com/c/dam/en/us/support/docs/ip/ip-multicast/ipmlt_wp.pdf[Cisco's
-Guidelines for Enterprise IP Multicast Address Allocation].]
-======
-
-The final corosync.conf configuration on each node should look
-something like the sample in <<ap-corosync-conf>>.
diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt b/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt
deleted file mode 100644
index 1beaef9c87..0000000000
--- a/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt
+++ /dev/null
@@ -1,131 +0,0 @@
-:compat-mode: legacy
-= Pacemaker Tools =
-
-== Simplify administration using a cluster shell ==
-
-In the dark past, configuring Pacemaker required the administrator to
-read and write XML. In true UNIX style, there were also a number of
-different commands that specialized in different aspects of querying
-and updating the cluster.
-
-All of that has been greatly simplified with the creation of unified
-command-line shells (and GUIs) that hide all the messy XML
-scaffolding.
-
-These shells take all the individual aspects required for managing and
-configuring a cluster, and pack them into one simple-to-use command
-line tool.
-
-They even allow you to queue up several changes at once and commit
-them all at once.
-
-Two popular command-line shells are `pcs` and `crmsh`. Clusters from Scratch is
-based on `pcs` because it comes with CentOS, but both have similar
-functionality. Choosing a shell or GUI is a matter of personal preference and
-what comes with (and perhaps is supported by) your choice of operating system.
-
-== Explore pcs ==
-
-Start by taking some time to familiarize yourself with
-what `pcs` can do.
-
-----
-[root@pcmk-1 ~]# pcs
-
-Usage: pcs [-f file] [-h] [commands]...
-Control and configure pacemaker and corosync.
-
-Options:
- -h, --help Display usage and exit.
- -f file Perform actions on file instead of active CIB.
- --debug Print all network traffic and external commands run.
- --version Print pcs version information. List pcs capabilities if
- --full is specified.
- --request-timeout Timeout for each outgoing request to another node in
- seconds. Default is 60s.
- --force Override checks and errors, the exact behavior depends on
- the command. WARNING: Using the --force option is
- strongly discouraged unless you know what you are doing.
-
-Commands:
- cluster Configure cluster options and nodes.
- resource Manage cluster resources.
- stonith Manage fence devices.
- constraint Manage resource constraints.
- property Manage pacemaker properties.
- acl Manage pacemaker access control lists.
- qdevice Manage quorum device provider on the local host.
- quorum Manage cluster quorum settings.
- booth Manage booth (cluster ticket manager).
- status View cluster status.
- config View and manage cluster configuration.
- pcsd Manage pcs daemon.
- node Manage cluster nodes.
- alert Manage pacemaker alerts.
-
-----
-
-As you can see, the different aspects of cluster management are separated
-into categories. To discover the functionality available in each of these
-categories, one can issue the command +pcs pass:[<replaceable>category</replaceable>] help+. Below
-is an example of all the options available under the status category.
-
-----
-[root@pcmk-1 ~]# pcs status help
-
-Usage: pcs status [commands]...
-View current cluster and resource status
-Commands:
- [status] [--full | --hide-inactive]
- View all information about the cluster and resources (--full provides
- more details, --hide-inactive hides inactive resources).
-
- resources [<resource id> | --full | --groups | --hide-inactive]
- Show all currently configured resources or if a resource is specified
- show the options for the configured resource. If --full is specified,
- all configured resource options will be displayed. If --groups is
- specified, only show groups (and their resources). If --hide-inactive
- is specified, only show active resources.
-
- groups
- View currently configured groups and their resources.
-
- cluster
- View current cluster status.
-
- corosync
- View current membership information as seen by corosync.
-
- quorum
- View current quorum status.
-
- qdevice <device model> [--full] [<cluster name>]
- Show runtime status of specified model of quorum device provider. Using
- --full will give more detailed output. If <cluster name> is specified,
- only information about the specified cluster will be displayed.
-
- nodes [corosync | both | config]
- View current status of nodes from pacemaker. If 'corosync' is
- specified, view current status of nodes from corosync instead. If
- 'both' is specified, view current status of nodes from both corosync &
- pacemaker. If 'config' is specified, print nodes from corosync &
- pacemaker configuration.
-
- pcsd [<node>]...
- Show current status of pcsd on nodes specified, or on all nodes
- configured in the local cluster if no nodes are specified.
-
- xml
- View xml version of status (output from crm_mon -r -1 -X).
-
-----
-
-Additionally, if you are interested in the version and
-supported cluster stack(s) available with your Pacemaker
-installation, run:
-
-----
-[root@pcmk-1 ~]# pacemakerd --features
-Pacemaker 1.1.18-11.el7_5.3 (Build: 2b07d5c5a9)
- Supporting v3.0.14: generated-manpages agent-manpages ncurses libqb-logging libqb-ipc systemd nagios corosync-native atomic-attrd acls
-----
diff --git a/doc/Clusters_from_Scratch/en-US/Clusters_from_Scratch.xml b/doc/Clusters_from_Scratch/en-US/Clusters_from_Scratch.xml
index 4586c9ecd7..7893d91adc 100644
--- a/doc/Clusters_from_Scratch/en-US/Clusters_from_Scratch.xml
+++ b/doc/Clusters_from_Scratch/en-US/Clusters_from_Scratch.xml
@@ -1,24 +1,24 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Clusters_from_Scratch.ent">
%BOOK_ENTITIES;
]>
<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Ch-Tools.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Ch-Cluster-Setup.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Verification.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Active-Passive.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Apache.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Shared-Storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Stonith.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ch-Active-Active.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ap-Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ap-Corosync-Conf.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Ap-Reading.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<index />
</book>

File Metadata

Mime Type
text/x-diff
Expires
Sat, Nov 23, 5:01 PM (10 h, 46 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
1019019
Default Alt Text
(39 KB)

Event Timeline