# 
# 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 "Cluster Nodes"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Defining a Cluster Node"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Each node in the cluster will have an entry in the nodes section containing its UUID, uname, and type."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Example Corosync cluster node entry"
msgstr ""

#. Tag: programlisting
#, no-c-format
msgid "&lt;node id=\"101\" uname=\"pcmk-1\"/&gt;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Where Pacemaker Gets the Node Name"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Traditionally, Pacemaker required nodes to be referred to by the value returned by <literal>uname -n</literal>. This can be problematic for services that require the <literal>uname -n</literal> to be a specific value (e.g. for a licence file)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This requirement has been relaxed for clusters using Corosync 2.0 or later. The name Pacemaker uses is:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The value stored in <literal>corosync.conf</literal> under <emphasis role=\"strong\">ring0_addr</emphasis> in the <emphasis role=\"strong\">nodelist</emphasis>, if it does not contain an IP address; otherwise"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The value stored in <literal>corosync.conf</literal> under <emphasis role=\"strong\">name</emphasis> in the <emphasis role=\"strong\">nodelist</emphasis>; otherwise"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The value of <literal>uname -n</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Pacemaker provides the <literal>crm_node -n</literal> command which displays the name used by a running cluster."
msgstr ""

#. Tag: para
#, no-c-format
msgid "If a Corosync <emphasis role=\"strong\">nodelist</emphasis> is used, <literal>crm_node --name-for-id</literal> <replaceable>number</replaceable> is also available to display the name used by the node with the corosync <emphasis role=\"strong\">nodeid</emphasis> of <replaceable>number</replaceable>, for example: <literal>crm_node --name-for-id 2</literal>."
msgstr ""

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

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Node</primary><secondary>attribute</secondary> </indexterm> <indexterm> <primary>attribute</primary> </indexterm> <emphasis>Node attributes</emphasis> are a special type of option (name-value pair) that applies to a node object."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Beyond the basic definition of a node, the administrator can describe the node’s attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see <xref linkend=\"ch-rules\" />."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Node attributes can be specified ahead of time or populated later, when the cluster is running, using <literal>crm_attribute</literal>."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Below is what the node’s definition would look like if the admin ran the command:"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Result of using crm_attribute to specify which kernel pcmk-1 is running"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "# crm_attribute --type nodes --node pcmk-1 --name kernel --update $(uname -r)"
msgstr ""

#. Tag: programlisting
#, no-c-format
msgid "&lt;node uname=\"pcmk-1\" type=\"normal\" id=\"101\"&gt;\n"
"   &lt;instance_attributes id=\"nodes-101\"&gt;\n"
"     &lt;nvpair id=\"nodes-101-kernel\" name=\"kernel\" value=\"3.10.0-123.13.2.el7.x86_64\"/&gt;\n"
"   &lt;/instance_attributes&gt;\n"
"&lt;/node&gt;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Rather than having to read the XML, a simpler way to determine the current value of an attribute is to use <literal>crm_attribute</literal> again:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "# crm_attribute --type nodes --node pcmk-1 --name kernel --query\n"
"scope=nodes  name=kernel value=3.10.0-123.13.2.el7.x86_64"
msgstr ""

#. Tag: para
#, no-c-format
msgid "By specifying <literal>--type nodes</literal> the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are \"forgotten\" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node, but administrators can also read and write to this section by specifying <literal>--type status</literal>."
msgstr ""