#
# 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 "Configuration Basics"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configuration Layout"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster is defined by the Cluster Information Base (CIB), which uses XML notation. The simplest CIB, an empty one, looks like this:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An empty configuration"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\">\n"
" <configuration>\n"
" <crm_config/>\n"
" <nodes/>\n"
" <resources/>\n"
" <constraints/>\n"
" </configuration>\n"
" <status/>\n"
"</cib>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The empty configuration above contains the major sections that make up a CIB:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>cib</literal>: The entire CIB is enclosed with a <literal>cib</literal> tag. Certain fundamental settings are defined as attributes of this tag."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>configuration</literal>: This section — the primary focus of this document — contains traditional configuration information such as what resources the cluster serves and the relationships among them."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>crm_config</literal>: cluster-wide configuration options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>nodes</literal>: the machines that host the cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>resources</literal>: the services run by the cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>constraints</literal>: indications of how resources should be placed"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>status</literal>: This section contains the history of each resource on each node. Based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for this section is the local resource manager (lrmd process) on each cluster node, and the cluster will occasionally repopulate the entire section. For this reason, it is never written to disk, and administrators are advised against modifying it in any way."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In this document, configuration settings will be described as <emphasis>properties</emphasis> or <emphasis>options</emphasis> based on how they are defined in the CIB:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Properties are XML attributes of an XML element."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Options are name-value pairs expressed as <literal>nvpair</literal> child elements of an XML element."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Normally you will use command-line tools that abstract the XML, so the distinction will be unimportant; both properties and options are cluster settings you can tweak."
msgstr ""
#. Tag: title
#, no-c-format
msgid "The Current State of the Cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the <literal>crm_mon</literal> utility, which will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Details on all the available options can be obtained using the <literal>crm_mon --help</literal> command."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sample output from crm_mon"
msgstr ""
#. Tag: screen
#, no-c-format
msgid " ============\n"
" Last updated: Fri Nov 23 15:26:13 2007\n"
" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n"
" 3 Nodes configured.\n"
" 5 Resources configured.\n"
" ============\n"
"\n"
" Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n"
" 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n"
" 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n"
" 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n"
" rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n"
" child_DoFencing:2 (stonith:external/vmware): Started sles-1\n"
" Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n"
" Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n"
" rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n"
" rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n"
" child_DoFencing:0 (stonith:external/vmware): Started sles-3"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sample output from crm_mon -n"
msgstr ""
#. Tag: screen
#, no-c-format
msgid " ============\n"
" Last updated: Fri Nov 23 15:26:13 2007\n"
" Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n"
" 3 Nodes configured.\n"
" 5 Resources configured.\n"
" ============\n"
"\n"
" Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n"
" Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n"
" Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n"
"\n"
" Resource Group: group-1\n"
" 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n"
" 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n"
" 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n"
" rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n"
" rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n"
" rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n"
" Clone Set: DoFencing\n"
" child_DoFencing:0 (stonith:external/vmware): Started sles-3\n"
" child_DoFencing:1 (stonith:external/vmware): Stopped\n"
" child_DoFencing:2 (stonith:external/vmware): Started sles-1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The DC (Designated Controller) node is where all the decisions are made, and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting."
msgstr ""
#. Tag: title
#, no-c-format
msgid "How Should the Configuration be Updated?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are three basic rules for updating the cluster configuration:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rule 1 - Never edit the <literal>cib.xml</literal> file manually. Ever. I’m not making this up."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rule 2 - Read Rule 1 again."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that it is clear how <emphasis>not</emphasis> to update the configuration, we can begin to explain how you <emphasis>should</emphasis>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Editing the CIB Using XML"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The most powerful tool for modifying the configuration is the <literal>cibadmin</literal> command. With <literal>cibadmin</literal>, you can query, add, remove, update or replace any part of the configuration. All changes take effect immediately, so there is no need to perform a reload-like operation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The simplest way of using <literal>cibadmin</literal> is to use it to save the current configuration to a temporary file, edit that file with your favorite text or XML editor, and then upload the revised configuration. <footnote><para>This process might appear to risk overwriting changes that happen after the initial cibadmin call, but pacemaker will reject any update that is \"too old\". If the CIB is updated in some other fashion after the initial cibadmin, the second cibadmin will be rejected because the version number will be too low.</para></footnote>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Safely using an editor to modify the cluster configuration"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin --query > tmp.xml\n"
"# vi tmp.xml\n"
"# cibadmin --replace --xml-file tmp.xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing the configuration can be found in <literal>pacemaker.rng</literal>, which may be deployed in a location such as <literal>/usr/share/pacemaker</literal> or <literal>/usr/lib/heartbeat</literal> depending on your operating system and how you installed the software."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you want to modify just one section of the configuration, you can query and replace just that section to avoid modifying any others."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Safely using an editor to modify only the resources section"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin --query --scope resources > tmp.xml\n"
"# vi tmp.xml\n"
"# cibadmin --replace --scope resources --xml-file tmp.xml"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Quickly Deleting Part of the Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Identify the object you wish to delete by XML tag and id. For example, you might search the CIB for all STONITH-related configuration:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Searching for STONITH-related configuration items"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin -Q | grep stonith\n"
" <nvpair id=\"cib-bootstrap-options-stonith-action\" name=\"stonith-action\" value=\"reboot\"/>\n"
" <nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"1\"/>\n"
" <primitive id=\"child_DoFencing\" class=\"stonith\" type=\"external/vmware\">\n"
" <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n"
" <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n"
" <lrm_resource id=\"child_DoFencing:1\" type=\"external/vmware\" class=\"stonith\">\n"
" <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n"
" <lrm_resource id=\"child_DoFencing:2\" type=\"external/vmware\" class=\"stonith\">\n"
" <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n"
" <lrm_resource id=\"child_DoFencing:3\" type=\"external/vmware\" class=\"stonith\">"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you wanted to delete the <literal>primitive</literal> tag with id <literal>child_DoFencing</literal>, you would run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin --delete --xml-text '<primitive id=\"child_DoFencing\"/>'"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Updating the Configuration Without Using XML"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Most tasks can be performed with one of the other command-line tools provided with pacemaker, avoiding the need to read or edit XML."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To enable STONITH for example, one could run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute --name stonith-enabled --update 1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Or, to check whether <emphasis role=\"strong\">somenode</emphasis> is allowed to run resources, there is:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_standby --get-value --node somenode"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Or, to find the current location of <emphasis role=\"strong\">my-test-rsc</emphasis>, one can use:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --locate --resource my-test-rsc"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Examples of using these tools for specific cases will be given throughout this document where appropriate."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Old versions of pacemaker (1.0.3 and earlier) had different command-line tool syntax. If you are using an older version, check your installed manual pages for the proper syntax to use."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Making Configuration Changes in a Sandbox"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created <literal>crm_shadow</literal> which creates a \"shadow\" copy of the configuration and arranges for all the command line tools to use it."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To begin, simply invoke <literal>crm_shadow --create</literal> with the name of a configuration to create <footnote><para>Shadow copies are identified with a name, making it possible to have more than one.</para></footnote>, and follow the simple on-screen instructions."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Read this section and the on-screen instructions carefully; failure to do so could result in destroying the cluster’s active configuration!"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Creating and displaying the active sandbox"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_shadow --create test\n"
"Setting up shadow instance\n"
"Type Ctrl-D to exit the crm_shadow shell\n"
"shadow[test]:\n"
"shadow[test] # crm_shadow --which\n"
"test"
msgstr ""
#. Tag: para
#, no-c-format
msgid "From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster’s active configuration. Once you have finished experimenting, you can either make the changes active via the <literal>--commit</literal> option, or discard them using the <literal>--delete</literal> option. Again, be sure to follow the on-screen instructions carefully!"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For a full list of <literal>crm_shadow</literal> options and commands, invoke it with the <literal>--help</literal> option."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using a sandbox to make multiple changes atomically, discard them and verify the real configuration is untouched"
msgstr ""
#. Tag: screen
#, no-c-format
msgid " shadow[test] # crm_failcount -G -r rsc_c001n01\n"
" name=fail-count-rsc_c001n01 value=0\n"
" shadow[test] # crm_standby -v on -N c001n02\n"
" shadow[test] # crm_standby -G -N c001n02\n"
" name=c001n02 scope=nodes value=on\n"
" shadow[test] # cibadmin --erase --force\n"
" shadow[test] # cibadmin --query\n"
" <cib cib_feature_revision=\"1\" validate-with=\"pacemaker-1.0\" admin_epoch=\"0\" crm_feature_set=\"3.0\" have-quorum=\"1\" epoch=\"112\"\n"
" dc-uuid=\"c001n01\" num_updates=\"1\" cib-last-written=\"Fri Jun 27 12:17:10 2008\">\n"
" <configuration>\n"
" <crm_config/>\n"
" <nodes/>\n"
" <resources/>\n"
" <constraints/>\n"
" </configuration>\n"
" <status/>\n"
" </cib>\n"
" shadow[test] # crm_shadow --delete test --force\n"
" Now type Ctrl-D to exit the crm_shadow shell\n"
" shadow[test] # exit\n"
" # crm_shadow --which\n"
" No active shadow configuration defined\n"
" # cibadmin -Q\n"
" <cib cib_feature_revision=\"1\" validate-with=\"pacemaker-1.0\" admin_epoch=\"0\" crm_feature_set=\"3.0\" have-quorum=\"1\" epoch=\"110\"\n"
" dc-uuid=\"c001n01\" num_updates=\"551\">\n"
" <configuration>\n"
" <crm_config>\n"
" <cluster_property_set id=\"cib-bootstrap-options\">\n"
" <nvpair id=\"cib-bootstrap-1\" name=\"stonith-enabled\" value=\"1\"/>\n"
" <nvpair id=\"cib-bootstrap-2\" name=\"pe-input-series-max\" value=\"30000\"/>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Testing Your Configuration Changes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We saw previously how to make a series of changes to a \"shadow\" copy of the configuration. Before loading the changes back into the cluster (e.g. <literal>crm_shadow --commit mytest --force</literal>), it is often advisable to simulate the effect of the changes with <literal>crm_simulate</literal>. For example:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_simulate --live-check -VVVVV --save-graph tmp.graph --save-dotfile tmp.dot"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This tool uses the same library as the live cluster to show what it would have done given the supplied input. Its output, in addition to a significant amount of logging, is stored in two files <literal>tmp.graph</literal> and <literal>tmp.dot</literal>. Both files are representations of the same thing: the cluster’s response to your changes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The graph file stores the complete transition from the existing cluster state to your desired new state, containing a list of all the actions, their parameters and their pre-requisites. Because the transition graph is not terribly easy to read, the tool also generates a Graphviz <footnote><para>Graph visualization software. See <ulink url=\"http://www.graphviz.org/\">http://www.graphviz.org/</ulink> for details.</para></footnote> dot-file representing the same information."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For information on the options supported by <literal>crm_simulate</literal>, use its <literal>--help</literal> option."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Interpreting the Graphviz output"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Arrows indicate ordering dependencies"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Dashed arrows indicate dependencies that are not present in the transition graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a dashed border of any color do not form part of the transition graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a green border form part of the transition graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a red border are ones the cluster would like to execute but cannot run"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with a blue border are ones the cluster does not feel need to be executed"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Actions with black text are sent to the LRM"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource actions have text of the form <replaceable>rsc</replaceable>_<replaceable>action</replaceable>_<replaceable>interval</replaceable> <replaceable>node</replaceable>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any action depending on an action with a red border will not be able to execute."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Loops are <emphasis>really</emphasis> bad. Please report them to the development team."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Small Cluster Transition"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the above example, it appears that a new node, <emphasis role=\"strong\">pcmk-2</emphasis>, has come online and that the cluster is checking to make sure <emphasis role=\"strong\">rsc1</emphasis>, <emphasis role=\"strong\">rsc2</emphasis> and <emphasis role=\"strong\">rsc3</emphasis> are not already running there (Indicated by the <emphasis role=\"strong\">rscN_monitor_0</emphasis> entries). Once it did that, and assuming the resources were not active there, it would have liked to stop <emphasis role=\"strong\">rsc1</emphasis> and <emphasis role=\"strong\">rsc2</emphasis> on <emphasis role=\"strong\">pcmk-1</emphasis> and move them to <emphasis role=\"strong\">pcmk-2</emphasis>. However, there appears to be some problem and the cluster cannot or is not permitted to perform the stop actions which implies it also cannot perform the start actions. For some reason the cluster does not want to start <emphasis role=\"strong\">rsc3</emphasis> anywhere."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Complex Cluster Transition"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Do I Need to Update the Configuration on All Cluster Nodes?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "No. Any changes are immediately synchronized to the other active members of the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To reduce bandwidth, the cluster only broadcasts the incremental updates that result from your changes and uses MD5 checksums to ensure that each copy is completely consistent."
msgstr ""