dhodovsk / source-git / pacemaker

Forked from source-git/pacemaker 3 years ago
Clone
Blob Blame History Raw
# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2018-05-14 18:03-0500\n"
"PO-Revision-Date: 2018-05-14 18:03-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#, no-c-format
msgid "Installation"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Install &DISTRO; &DISTRO_VERSION;"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Boot the Install Image"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Download the 4GB <ulink url=\"http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1708.iso\">&DISTRO; &DISTRO_VERSION; DVD ISO</ulink>. Use the image to boot a virtual machine, or burn it to a DVD or USB drive and boot a physical server from that."
msgstr ""

#. Tag: para
#, no-c-format
msgid "After starting the installation, select your language and keyboard layout at the welcome screen."
msgstr ""

#. Tag: title
#, no-c-format
msgid "&DISTRO; &DISTRO_VERSION; Installation Welcome Screen"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Installation Options"
msgstr ""

#. Tag: para
#, no-c-format
msgid "At this point, you get a chance to tweak the default installation options."
msgstr ""

#. Tag: title
#, no-c-format
msgid "&DISTRO; &DISTRO_VERSION; Installation Summary Screen"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Ignore the <emphasis role=\"strong\">SOFTWARE SELECTION</emphasis> section (try saying that 10 times quickly). The <emphasis role=\"strong\">Infrastructure Server</emphasis> environment does have add-ons with much of the software we need, but we will leave it as a <emphasis role=\"strong\">Minimal Install</emphasis> here, so that we can see exactly what software is required later."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure Network"
msgstr ""

#. Tag: para
#, no-c-format
msgid "In the <emphasis role=\"strong\">NETWORK &amp; HOSTNAME</emphasis> section:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Edit <emphasis role=\"strong\">Host Name:</emphasis> as desired. For this example, we will use <emphasis role=\"strong\">pcmk-1.localdomain</emphasis>."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Select your network device, press <emphasis role=\"strong\">Configure…</emphasis>, and manually assign a fixed IP address. For this example, we’ll use 192.168.122.101 under <emphasis role=\"strong\">IPv4 Settings</emphasis> (with an appropriate netmask, gateway and DNS server)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Flip the switch to turn your network device on."
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure Disk"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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 <literal>/</literal> (aka. <emphasis role=\"strong\">root</emphasis>) partition, which cannot be reduced in size later (dynamic increases are fine)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "In order to follow the DRBD and GFS2 portions of this guide, we need to reserve space on each machine for a replicated volume."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Enter the <emphasis role=\"strong\">INSTALLATION DESTINATION</emphasis> section, ensure the hard drive you want to install to is selected, select <emphasis role=\"strong\">I will configure partitioning</emphasis>, and press <emphasis role=\"strong\">Done</emphasis>."
msgstr ""

#. Tag: para
#, no-c-format
msgid "In the <emphasis role=\"strong\">MANUAL PARTITIONING</emphasis> screen that comes next, click the option to create mountpoints automatically. Select the <literal>/</literal> mountpoint, and reduce the desired capacity by 1GiB or so. Select <emphasis role=\"strong\">Modify…</emphasis> by the volume group name, and change the <emphasis role=\"strong\">Size policy:</emphasis> to <emphasis role=\"strong\">As large as possible</emphasis>, to make the reclaimed space available inside the LVM volume group. We’ll add the additional volume later."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure Time Synchronization"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "&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 <emphasis role=\"strong\">TIME &amp; DATE</emphasis> section."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Finish Install"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Select <emphasis role=\"strong\">Begin Installation</emphasis>. 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 <emphasis role=\"strong\">root</emphasis> and the password you created earlier."
msgstr ""

#. Tag: title
#, no-c-format
msgid "&DISTRO; &DISTRO_VERSION; Console Prompt"
msgstr ""

#. Tag: para
#, no-c-format
msgid "From here on, we’re going to be working exclusively from the terminal."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure the OS"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Verify Networking"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Ensure that the machine has the static IP address you configured earlier."
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ip addr\n"
"1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN\n"
"    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n"
"    inet 127.0.0.1/8 scope host lo\n"
"    inet6 ::1/128 scope host\n"
"       valid_lft forever preferred_lft forever\n"
"2: eth0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc pfifo_fast state UP qlen 1000\n"
"    link/ether 52:54:00:d7:d6:08 brd ff:ff:ff:ff:ff:ff\n"
"    inet 192.168.122.101/24 brd 192.168.122.255 scope global eth0\n"
"       valid_lft forever preferred_lft forever\n"
"    inet6 fe80::5054:ff:fed7:d608/64 scope link\n"
"       valid_lft forever preferred_lft forever"
msgstr ""

#. Tag: para
#, no-c-format
msgid "If you ever need to change the node’s IP address from the command line, follow"
msgstr ""

#. Tag: literallayout
#, no-c-format
msgid "[root@pcmk-1 ~]# vi /etc/sysconfig/network-scripts/ifcfg-${device} # manually edit as desired\n"
"[root@pcmk-1 ~]# nmcli dev disconnect ${device}\n"
"[root@pcmk-1 ~]# nmcli con reload ${device}\n"
"[root@pcmk-1 ~]# nmcli con up ${device}"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This makes <emphasis role=\"strong\">NetworkManager</emphasis> aware that a change was made on the config file."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Next, ensure that the routes are as expected:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ip route\n"
"default via 192.168.122.1 dev eth0  proto static  metric 100\n"
"192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.101  metric 100"
msgstr ""

#. Tag: para
#, no-c-format
msgid "If there is no line beginning with <emphasis role=\"strong\">default via</emphasis>, then you may need to add a line such as"
msgstr ""

#. Tag: programlisting
#, no-c-format
msgid "GATEWAY=\"192.168.122.1\""
msgstr ""

#. Tag: para
#, no-c-format
msgid "to the device configuration using the same process as described above for changing the IP address."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Now, check for connectivity to the outside world. Start small by testing whether we can reach the gateway we configured."
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ping -c 1 192.168.122.1\n"
"PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data.\n"
"64 bytes from 192.168.122.1: icmp_req=1 ttl=64 time=0.249 ms\n"
"\n"
" --- 192.168.122.1 ping statistics ---\n"
"1 packets transmitted, 1 received, 0% packet loss, time 0ms\n"
"rtt min/avg/max/mdev = 0.249/0.249/0.249/0.000 ms"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Now try something external; choose a location you know should be available."
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ping -c 1 www.google.com\n"
"PING www.l.google.com (173.194.72.106) 56(84) bytes of data.\n"
"64 bytes from tf-in-f106.1e100.net (173.194.72.106): icmp_req=1 ttl=41 time=167 ms\n"
"\n"
" --- www.l.google.com ping statistics ---\n"
"1 packets transmitted, 1 received, 0% packet loss, time 0ms\n"
"rtt min/avg/max/mdev = 167.618/167.618/167.618/0.000 ms"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Login Remotely"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "From another host, check whether we can see the new host at all:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "beekhof@f16 ~ # ping -c 1 192.168.122.101\n"
"PING 192.168.122.101 (192.168.122.101) 56(84) bytes of data.\n"
"64 bytes from 192.168.122.101: icmp_req=1 ttl=64 time=1.01 ms\n"
"\n"
"--- 192.168.122.101 ping statistics ---\n"
"1 packets transmitted, 1 received, 0% packet loss, time 0ms\n"
"rtt min/avg/max/mdev = 1.012/1.012/1.012/0.000 ms"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Next, login as root via SSH."
msgstr ""

#. Tag: screen
#, no-c-format
msgid "beekhof@f16 ~ # ssh -l root 192.168.122.101\n"
"The authenticity of host '192.168.122.101 (192.168.122.101)' can't be established.\n"
"ECDSA key fingerprint is 6e:b7:8f:e2:4c:94:43:54:a8:53:cc:20:0f:29:a4:e0.\n"
"Are you sure you want to continue connecting (yes/no)? yes\n"
"Warning: Permanently added '192.168.122.101' (ECDSA) to the list of known hosts.\n"
"root@192.168.122.101's password:\n"
"Last login: Tue Aug 11 13:14:39 2015\n"
"[root@pcmk-1 ~]#"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Apply Updates"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Apply any package updates released since your installation image was created:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# yum update"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Use Short Node Names"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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: <indexterm> <primary>Nodes</primary><secondary>short name</secondary> </indexterm> <indexterm> <primary>short name</primary> </indexterm>"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# uname -n\n"
"pcmk-1.localdomain"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Nodes</primary><secondary>Domain name (Query)</secondary> </indexterm> <indexterm> <primary>Domain name (Query)</primary> </indexterm>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "We can use the <literal>hostnamectl</literal> tool to strip off the domain name:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# hostnamectl set-hostname $(uname -n | sed s/\\\\..*//)"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Nodes</primary><secondary>Domain name (Remove from host name)</secondary> </indexterm> <indexterm> <primary>Domain name (Remove from host name)</primary> </indexterm>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Now, check that the machine is using the correct name:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# uname -n\n"
"pcmk-1"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Repeat for Second Node"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Repeat the Installation steps so far, so that you have two nodes ready to have the cluster software installed."
msgstr ""

#. Tag: para
#, no-c-format
msgid "For the purposes of this document, the additional node is called pcmk-2 with address 192.168.122.102."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure Communication Between Nodes"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure Host Name Resolution"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Confirm that you can communicate between the two new nodes:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ping -c 3 192.168.122.102\n"
"PING 192.168.122.102 (192.168.122.102) 56(84) bytes of data.\n"
"64 bytes from 192.168.122.102: icmp_seq=1 ttl=64 time=0.343 ms\n"
"64 bytes from 192.168.122.102: icmp_seq=2 ttl=64 time=0.402 ms\n"
"64 bytes from 192.168.122.102: icmp_seq=3 ttl=64 time=0.558 ms\n"
"\n"
"--- 192.168.122.102 ping statistics ---\n"
"3 packets transmitted, 3 received, 0% packet loss, time 2000ms\n"
"rtt min/avg/max/mdev = 0.343/0.434/0.558/0.092 ms"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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 <literal>/etc/hosts</literal> on both nodes. Below are the entries for my cluster nodes:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# grep pcmk /etc/hosts\n"
"192.168.122.101 pcmk-1.clusterlabs.org pcmk-1\n"
"192.168.122.102 pcmk-2.clusterlabs.org pcmk-2"
msgstr ""

#. Tag: para
#, no-c-format
msgid "We can now verify the setup by again using ping:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ping -c 3 pcmk-2\n"
"PING pcmk-2.clusterlabs.org (192.168.122.101) 56(84) bytes of data.\n"
"64 bytes from pcmk-1.clusterlabs.org (192.168.122.101): icmp_seq=1 ttl=64 time=0.164 ms\n"
"64 bytes from pcmk-1.clusterlabs.org (192.168.122.101): icmp_seq=2 ttl=64 time=0.475 ms\n"
"64 bytes from pcmk-1.clusterlabs.org (192.168.122.101): icmp_seq=3 ttl=64 time=0.186 ms\n"
"\n"
"--- pcmk-2.clusterlabs.org ping statistics ---\n"
"3 packets transmitted, 3 received, 0% packet loss, time 2001ms\n"
"rtt min/avg/max/mdev = 0.164/0.275/0.475/0.141 ms"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure SSH"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>SSH</primary> </indexterm>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Create a new key and allow anyone with that key to log in:"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Creating and Activating a new SSH Key"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ssh-keygen -t dsa -f ~/.ssh/id_dsa -N \"\"\n"
"Generating public/private dsa key pair.\n"
"Your identification has been saved in /root/.ssh/id_dsa.\n"
"Your public key has been saved in /root/.ssh/id_dsa.pub.\n"
"The key fingerprint is:\n"
"91:09:5c:82:5a:6a:50:08:4e:b2:0c:62:de:cc:74:44 root@pcmk-1.clusterlabs.org\n"
"The key's randomart image is:\n"
"+--[ DSA 1024]----+\n"
"|==.ooEo..        |\n"
"|X O + .o o       |\n"
"| * A    +        |\n"
"|  +      .       |\n"
"| .      S        |\n"
"|                 |\n"
"|                 |\n"
"|                 |\n"
"|                 |\n"
"+-----------------+\n"
"[root@pcmk-1 ~]# cp ~/.ssh/id_dsa.pub ~/.ssh/authorized_keys"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Creating and Activating a new SSH Key</primary> </indexterm>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Install the key on the other node:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# scp -r ~/.ssh pcmk-2:\n"
"The authenticity of host 'pcmk-2 (192.168.122.102)' can't be established.\n"
"ECDSA key fingerprint is a4:f5:b2:34:9d:86:2b:34:a2:87:37:b9:ca:68:52:ec.\n"
"Are you sure you want to continue connecting (yes/no)? yes\n"
"Warning: Permanently added 'pcmk-2,192.168.122.102' (ECDSA) to the list of known hosts.\n"
"root@pcmk-2's password:\n"
"id_dsa.pub                           100%  616     0.6KB/s   00:00\n"
"id_dsa                               100%  672     0.7KB/s   00:00\n"
"known_hosts                          100%  400     0.4KB/s   00:00\n"
"authorized_keys                      100%  616     0.6KB/s   00:00"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Test that you can now run commands remotely, without being prompted:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ssh pcmk-2 -- uname -n\n"
"pcmk-2"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Install the Cluster Software"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "# yum install -y pacemaker pcs psmisc policycoreutils-python"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This document will show commands that need to be executed on both nodes with a simple <literal>#</literal> prompt. Be sure to run them on each node individually."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This document uses <literal>pcs</literal> for cluster management. Other alternatives, such as <literal>crmsh</literal>, are available, but their syntax will differ from the examples used here."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure the Cluster Software"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Allow cluster services through firewall"
msgstr ""

#. Tag: para
#, no-c-format
msgid "On each node, allow cluster-related services through the local firewall:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "# firewall-cmd --permanent --add-service=high-availability\n"
"success\n"
"# firewall-cmd --reload\n"
"success"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To disable security measures:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# setenforce 0\n"
"[root@pcmk-1 ~]# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n"
"[root@pcmk-1 ~]# systemctl mask firewalld.service\n"
"[root@pcmk-1 ~]# systemctl stop firewalld.service\n"
"[root@pcmk-1 ~]# iptables --flush"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Enable pcs Daemon"
msgstr ""

#. Tag: para
#, no-c-format
msgid "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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Start and enable the daemon by issuing the following commands on each node:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "# systemctl start pcsd.service\n"
"# systemctl enable pcsd.service\n"
"ln -s '/usr/lib/systemd/system/pcsd.service' '/etc/systemd/system/multi-user.target.wants/pcsd.service'"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The installed packages will create a <emphasis role=\"strong\">hacluster</emphasis> user with a disabled password. While this is fine for running <literal>pcs</literal> 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."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This tutorial will make use of such commands, so now we will set a password for the <emphasis role=\"strong\">hacluster</emphasis> user, using the same password on both nodes:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "# passwd hacluster\n"
"Changing password for user hacluster.\n"
"New password:\n"
"Retype new password:\n"
"passwd: all authentication tokens updated successfully."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Alternatively, to script this process or set the password on a different machine from the one you’re logged into, you can use the <literal>--stdin</literal> option for <literal>passwd</literal>:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ssh pcmk-2 -- 'echo mysupersecretpassword | passwd --stdin hacluster'"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configure Corosync"
msgstr ""

#. Tag: para
#, no-c-format
msgid "On either node, use <literal>pcs cluster auth</literal> to authenticate as the <emphasis role=\"strong\">hacluster</emphasis> user:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster auth pcmk-1 pcmk-2\n"
"Username: hacluster\n"
"Password:\n"
"pcmk-1: Authorized\n"
"pcmk-2: Authorized"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Next, use <literal>pcs cluster setup</literal> on the same node to generate and synchronize the corosync configuration:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster setup --name mycluster pcmk-1 pcmk-2\n"
"Shutting down pacemaker/corosync services...\n"
"Redirecting to /bin/systemctl stop  pacemaker.service\n"
"Redirecting to /bin/systemctl stop  corosync.service\n"
"Killing any remaining services...\n"
"Removing all cluster configuration files...\n"
"pcmk-1: Succeeded\n"
"pcmk-2: Succeeded"
msgstr ""

#. Tag: para
#, no-c-format
msgid "If you received an authorization error for either of those commands, make sure you configured the <emphasis role=\"strong\">hacluster</emphasis> user account on each node with the same password."
msgstr ""

#. Tag: para
#, no-c-format
msgid "If you are not using <literal>pcs</literal> for cluster administration, follow whatever procedures are appropriate for your tools to create a corosync.conf and copy it to all nodes."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <literal>pcs</literal> command will configure corosync to use UDP unicast transport; if you choose to use multicast instead, choose a multicast address carefully. <footnote><para>For some subtle issues, see <ulink url=\"http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html\">Topics in High-Performance Messaging: Multicast Address Assignment</ulink> or the more detailed treatment in <ulink url=\"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</ulink>.</para></footnote>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The final corosync.conf configuration on each node should look something like the sample in <xref linkend=\"ap-corosync-conf\" />."
msgstr ""