# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2017-05-08 11:19-0500\n"
"PO-Revision-Date: 2017-05-08 11:19-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 "Installing"
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "Most major Linux distributions have pacemaker packages in their standard package repositories, or the software can be built from source code. See the <ulink url=\"http://clusterlabs.org/wiki/Install\">Install wiki page</ulink> for details."
msgstr ""

#. Tag: para
#, no-c-format
msgid "See <link linkend=\"q-messaging-layer\">Which Messaging Layer Should I Choose?</link> for information about choosing a messaging layer."
msgstr ""

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

#. Tag: title
#, no-c-format
msgid "Enabling Pacemaker For Corosync 2.<emphasis>x</emphasis>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "High-level cluster management tools are available that can configure corosync for you. This document focuses on the lower-level details if you want to configure corosync yourself."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Corosync configuration is normally located in <literal>/etc/corosync/corosync.conf</literal>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Corosync 2.<emphasis>x</emphasis> configuration file for two nodes <emphasis role=\"strong\">myhost1</emphasis> and <emphasis role=\"strong\">myhost2</emphasis>"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "totem {\n"
"version: 2\n"
"secauth: off\n"
"cluster_name: mycluster\n"
"transport: udpu\n"
"}\n"
"\n"
"nodelist {\n"
"  node {\n"
"        ring0_addr: myhost1\n"
"        nodeid: 1\n"
"       }\n"
"  node {\n"
"        ring0_addr: myhost2\n"
"        nodeid: 2\n"
"       }\n"
"}\n"
"\n"
"quorum {\n"
"provider: corosync_votequorum\n"
"two_node: 1\n"
"}\n"
"\n"
"logging {\n"
"to_syslog: yes\n"
"}"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Corosync 2.<emphasis>x</emphasis> configuration file for three nodes <emphasis role=\"strong\">myhost1</emphasis>, <emphasis role=\"strong\">myhost2</emphasis> and <emphasis role=\"strong\">myhost3</emphasis>"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "totem {\n"
"version: 2\n"
"secauth: off\n"
"cluster_name: mycluster\n"
"transport: udpu\n"
"}\n"
"\n"
"nodelist {\n"
"  node {\n"
"        ring0_addr: myhost1\n"
"        nodeid: 1\n"
"       }\n"
"  node {\n"
"        ring0_addr: myhost2\n"
"        nodeid: 2\n"
"       }\n"
"  node {\n"
"        ring0_addr: myhost3\n"
"        nodeid: 3\n"
"       }\n"
"}\n"
"\n"
"quorum {\n"
"provider: corosync_votequorum\n"
"\n"
"}\n"
"\n"
"logging {\n"
"to_syslog: yes\n"
"}"
msgstr ""

#. Tag: para
#, no-c-format
msgid "In the above examples, the <literal>totem</literal> section defines what protocol version and options (including encryption) to use, <footnote><para> Please consult the Corosync website (<ulink url=\"http://www.corosync.org/\">http://www.corosync.org/</ulink>) and documentation for details on enabling encryption and peer authentication for the cluster. </para></footnote> and gives the cluster a unique name (<literal>mycluster</literal> in these examples)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <literal>node</literal> section lists the nodes in this cluster. (See <xref linkend=\"s-node-name\" /> for how this affects pacemaker.)"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <literal>quorum</literal> section defines how the cluster uses quorum. The important thing is that two-node clusters must be handled specially, so <literal>two_node: 1</literal> must be defined for two-node clusters (and only for two-node clusters)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <literal>logging</literal> section should be self-explanatory."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Enabling Pacemaker For Corosync 1.<emphasis>x</emphasis>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Corosync 1.<emphasis>x</emphasis> configuration file for a cluster with all nodes on the <literal>192.0.2.0/24</literal> network"
msgstr ""

#. Tag: programlisting
#, no-c-format
msgid "  totem {\n"
"      version: 2\n"
"      secauth: off\n"
"      threads: 0\n"
"      interface {\n"
"          ringnumber: 0\n"
"          bindnetaddr: 192.0.2.0\n"
"          mcastaddr: 239.255.1.1\n"
"          mcastport: 1234\n"
"      }\n"
"  }\n"
"  logging {\n"
"      fileline: off\n"
"      to_syslog: yes\n"
"      syslog_facility: daemon\n"
"  }\n"
"  amf {\n"
"      mode: disabled\n"
"  }"
msgstr ""

#. Tag: para
#, no-c-format
msgid "With corosync 1.<emphasis>x</emphasis>, the <literal>totem</literal> section contains the protocol version and options as with 2.<emphasis>x</emphasis>. However, nodes are also listed here, in the <literal>interface</literal> section. The <literal>bindnetaddr</literal> option is usually the <emphasis>network</emphasis> address, thus allowing the same configuration file to be used on all nodes. IPv4 or IPv6 addresses can be used with corosync."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <literal>amf</literal> section refers to the Availability Management Framework and is not covered in this document."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The above corosync configuration is enough for corosync to operate by itself, but corosync 1.<emphasis>x</emphasis> additionally needs to be told when it is being used in conjunction with Pacemaker. This can be accomplished in one of two ways:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Via the CMAN software provided with Red Hat Enterprise Linux 6 and its derivatives"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Via the pacemaker corosync plugin"
msgstr ""

#. Tag: para
#, no-c-format
msgid "To use CMAN, consult its documentation."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To use the pacemaker corosync plugin, add the following fragment to the corosync configuration and restart the cluster."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Corosync 1._x_configuration fragment to enable Pacemaker plugin"
msgstr ""

#. Tag: programlisting
#, no-c-format
msgid "aisexec {\n"
"    user:  root\n"
"    group: root\n"
"}\n"
"service {\n"
"    name: pacemaker\n"
"    ver: 0\n"
"}"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The cluster needs to be run as root so that its child processes (the <literal>lrmd</literal> in particular) have sufficient privileges to perform the actions requested of it. After all, a cluster manager that can’t add an IP address or start apache is of little use."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The second directive is the one that actually instructs the cluster to run Pacemaker."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Enabling Pacemaker For Heartbeat"
msgstr ""

#. Tag: para
#, no-c-format
msgid "See the heartbeat documentation for how to set up a <literal>ha.cf</literal> configuration file."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To enable the use of pacemaker with heartbeat, add the following to a functional <literal>ha.cf</literal> configuration file and restart Heartbeat:"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Heartbeat configuration fragment to enable Pacemaker"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "crm respawn"
msgstr ""