Page MenuHomeClusterLabs Projects
Files F1842305

No OneTemporary
Actions

View Options

This file is larger than 256 KB, so syntax highlighting was skipped.
diff --git a/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot b/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot
index ba038a3181..8f0cdfeee7 100644
--- a/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot
+++ b/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot
@@ -1,536 +1,532 @@
#
# 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"
+"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 "Configuration Recap"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Final Cluster Configuration"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: dlm-clone [dlm]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: ClusterIP-clone [ClusterIP] (unique)\n"
" ClusterIP:0 (ocf::heartbeat:IPaddr2): Started\n"
" ClusterIP:1 (ocf::heartbeat:IPaddr2): Started\n"
" Clone Set: WebFS-clone [WebFS]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: WebSite-clone [WebSite]\n"
" Started: [ pcmk-1 pcmk-2 ]"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource op defaults\n"
"timeout: 240s"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs stonith\n"
" impi-fencing (stonith:fence_ipmilan) Started"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
" start ClusterIP-clone then start WebSite-clone (kind:Mandatory)\n"
" promote WebDataClone then start WebFS-clone (kind:Mandatory)\n"
" start WebFS-clone then start WebSite-clone (kind:Mandatory)\n"
" start dlm-clone then start WebFS-clone (kind:Mandatory)\n"
"Colocation Constraints:\n"
" WebSite-clone with ClusterIP-clone (score:INFINITY)\n"
" WebFS-clone with WebDataClone (score:INFINITY) (with-rsc-role:Master)\n"
" WebSite-clone with WebFS-clone (score:INFINITY)\n"
-" WebFS-clone with dlm-clone (score:INFINITY)"
+" WebFS-clone with dlm-clone (score:INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 14 12:05:37 2015\n"
-"Last change: Fri Aug 14 11:49:29 2015\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"11 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 12:05:37 2018\n"
+"Last change: Fri Jan 12 11:49:29 2018\n"
"\n"
+"2 nodes configured\n"
+"11 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" impi-fencing (stonith:fence_ipmilan): Started pcmk-1\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: dlm-clone [dlm]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: ClusterIP-clone [ClusterIP] (unique)\n"
" ClusterIP:0 (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" ClusterIP:1 (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
" Clone Set: WebFS-clone [WebFS]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: WebSite-clone [WebSite]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "&lt;cib crm_feature_set=\"3.0.9\" validate-with=\"pacemaker-2.3\" epoch=\"51\" num_updates=\"16\" admin_epoch=\"0\" cib-last-written=\"Fri Aug 14 11:49:29 2015\" have-quorum=\"1\" dc-uuid=\"1\"&gt;\n"
+msgid "&lt;cib crm_feature_set=\"3.0.12\" validate-with=\"pacemaker-2.8\" epoch=\"51\" num_updates=\"16\" admin_epoch=\"0\" cib-last-written=\"Fri Jan 12 11:49:29 2018\" have-quorum=\"1\" dc-uuid=\"1\"&gt;\n"
" &lt;crm_config&gt;\n"
" &lt;cluster_property_set id=\"cib-bootstrap-options\"&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-have-watchdog\" name=\"have-watchdog\" value=\"false\"/&gt;\n"
-" &lt;nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.12-a14efad\"/&gt;\n"
+" &lt;nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.16-12.el7_4.5-94ff4df\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-cluster-infrastructure\" name=\"cluster-infrastructure\" value=\"corosync\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-cluster-name\" name=\"cluster-name\" value=\"mycluster\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-last-lrm-refresh\" name=\"last-lrm-refresh\" value=\"1419129162\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"true\"/&gt;\n"
" &lt;/cluster_property_set&gt;\n"
" &lt;/crm_config&gt;\n"
" &lt;nodes&gt;\n"
" &lt;node id=\"1\" uname=\"pcmk-1\"&gt;\n"
" &lt;instance_attributes id=\"nodes-1\"/&gt;\n"
" &lt;/node&gt;\n"
" &lt;node id=\"2\" uname=\"pcmk-2\"&gt;\n"
" &lt;instance_attributes id=\"nodes-2\"/&gt;\n"
" &lt;/node&gt;\n"
" &lt;/nodes&gt;\n"
" &lt;resources&gt;\n"
" &lt;primitive class=\"stonith\" id=\"impi-fencing\" type=\"fence_ipmilan\"&gt;\n"
" &lt;instance_attributes id=\"impi-fencing-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"impi-fencing-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"pcmk-1 pcmk-2\"/&gt;\n"
" &lt;nvpair id=\"impi-fencing-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"10.0.0.1\"/&gt;\n"
" &lt;nvpair id=\"impi-fencing-instance_attributes-login\" name=\"login\" value=\"testuser\"/&gt;\n"
" &lt;nvpair id=\"impi-fencing-instance_attributes-passwd\" name=\"passwd\" value=\"acd123\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"impi-fencing-interval-60s\" interval=\"60s\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;master id=\"WebDataClone\"&gt;\n"
" &lt;primitive class=\"ocf\" id=\"WebData\" provider=\"linbit\" type=\"drbd\"&gt;\n"
" &lt;instance_attributes id=\"WebData-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"WebData-instance_attributes-drbd_resource\" name=\"drbd_resource\" value=\"wwwdata\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"WebData-start-timeout-240\" interval=\"0s\" name=\"start\" timeout=\"240\"/&gt;\n"
" &lt;op id=\"WebData-promote-timeout-90\" interval=\"0s\" name=\"promote\" timeout=\"90\"/&gt;\n"
" &lt;op id=\"WebData-demote-timeout-90\" interval=\"0s\" name=\"demote\" timeout=\"90\"/&gt;\n"
" &lt;op id=\"WebData-stop-timeout-100\" interval=\"0s\" name=\"stop\" timeout=\"100\"/&gt;\n"
" &lt;op id=\"WebData-monitor-interval-60s\" interval=\"60s\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;meta_attributes id=\"WebDataClone-meta_attributes\"&gt;\n"
" &lt;nvpair id=\"WebDataClone-meta_attributes-master-max\" name=\"master-max\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"WebDataClone-meta_attributes-master-node-max\" name=\"master-node-max\" value=\"1\"/&gt;\n"
" &lt;nvpair id=\"WebDataClone-meta_attributes-clone-max\" name=\"clone-max\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"WebDataClone-meta_attributes-clone-node-max\" name=\"clone-node-max\" value=\"1\"/&gt;\n"
" &lt;nvpair id=\"WebDataClone-meta_attributes-notify\" name=\"notify\" value=\"true\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/master&gt;\n"
" &lt;clone id=\"dlm-clone\"&gt;\n"
" &lt;primitive class=\"ocf\" id=\"dlm\" provider=\"pacemaker\" type=\"controld\"&gt;\n"
" &lt;instance_attributes id=\"dlm-instance_attributes\"/&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"dlm-start-timeout-90\" interval=\"0s\" name=\"start\" timeout=\"90\"/&gt;\n"
" &lt;op id=\"dlm-stop-timeout-100\" interval=\"0s\" name=\"stop\" timeout=\"100\"/&gt;\n"
" &lt;op id=\"dlm-monitor-interval-60s\" interval=\"60s\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;meta_attributes id=\"dlm-clone-meta\"&gt;\n"
" &lt;nvpair id=\"dlm-clone-max\" name=\"clone-max\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"dlm-clone-node-max\" name=\"clone-node-max\" value=\"1\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/clone&gt;\n"
" &lt;clone id=\"ClusterIP-clone\"&gt;\n"
" &lt;primitive class=\"ocf\" id=\"ClusterIP\" provider=\"heartbeat\" type=\"IPaddr2\"&gt;\n"
" &lt;instance_attributes id=\"ClusterIP-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"ClusterIP-instance_attributes-ip\" name=\"ip\" value=\"192.168.122.120\"/&gt;\n"
" &lt;nvpair id=\"ClusterIP-instance_attributes-cidr_netmask\" name=\"cidr_netmask\" value=\"32\"/&gt;\n"
" &lt;nvpair id=\"ClusterIP-instance_attributes-clusterip_hash\" name=\"clusterip_hash\" value=\"sourceip\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"ClusterIP-start-timeout-20s\" interval=\"0s\" name=\"start\" timeout=\"20s\"/&gt;\n"
" &lt;op id=\"ClusterIP-stop-timeout-20s\" interval=\"0s\" name=\"stop\" timeout=\"20s\"/&gt;\n"
" &lt;op id=\"ClusterIP-monitor-interval-30s\" interval=\"30s\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;meta_attributes id=\"ClusterIP-meta_attributes\"/&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;meta_attributes id=\"ClusterIP-clone-meta\"&gt;\n"
" &lt;nvpair id=\"ClusterIP-clone-max\" name=\"clone-max\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"ClusterIP-clone-node-max\" name=\"clone-node-max\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"ClusterIP-globally-unique\" name=\"globally-unique\" value=\"true\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/clone&gt;\n"
" &lt;clone id=\"WebFS-clone\"&gt;\n"
" &lt;primitive class=\"ocf\" id=\"WebFS\" provider=\"heartbeat\" type=\"Filesystem\"&gt;\n"
" &lt;instance_attributes id=\"WebFS-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"WebFS-instance_attributes-device\" name=\"device\" value=\"/dev/drbd1\"/&gt;\n"
" &lt;nvpair id=\"WebFS-instance_attributes-directory\" name=\"directory\" value=\"/var/www/html\"/&gt;\n"
" &lt;nvpair id=\"WebFS-instance_attributes-fstype\" name=\"fstype\" value=\"gfs2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"WebFS-start-timeout-60\" interval=\"0s\" name=\"start\" timeout=\"60\"/&gt;\n"
" &lt;op id=\"WebFS-stop-timeout-60\" interval=\"0s\" name=\"stop\" timeout=\"60\"/&gt;\n"
" &lt;op id=\"WebFS-monitor-interval-20\" interval=\"20\" name=\"monitor\" timeout=\"40\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;meta_attributes id=\"WebFS-meta_attributes\"/&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;meta_attributes id=\"WebFS-clone-meta\"/&gt;\n"
" &lt;/clone&gt;\n"
" &lt;clone id=\"WebSite-clone\"&gt;\n"
" &lt;primitive class=\"ocf\" id=\"WebSite\" provider=\"heartbeat\" type=\"apache\"&gt;\n"
" &lt;instance_attributes id=\"WebSite-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"WebSite-instance_attributes-configfile\" name=\"configfile\" value=\"/etc/httpd/conf/httpd.conf\"/&gt;\n"
" &lt;nvpair id=\"WebSite-instance_attributes-statusurl\" name=\"statusurl\" value=\"http://localhost/server-status\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"WebSite-start-timeout-40s\" interval=\"0s\" name=\"start\" timeout=\"40s\"/&gt;\n"
" &lt;op id=\"WebSite-stop-timeout-60s\" interval=\"0s\" name=\"stop\" timeout=\"60s\"/&gt;\n"
" &lt;op id=\"WebSite-monitor-interval-1min\" interval=\"1min\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;meta_attributes id=\"WebSite-clone-meta\"/&gt;\n"
" &lt;/clone&gt;\n"
" &lt;/resources&gt;\n"
" &lt;constraints&gt;\n"
" &lt;rsc_colocation id=\"colocation-WebSite-ClusterIP-INFINITY\" rsc=\"WebSite-clone\" score=\"INFINITY\" with-rsc=\"ClusterIP-clone\"/&gt;\n"
" &lt;rsc_order first=\"ClusterIP-clone\" first-action=\"start\" id=\"order-ClusterIP-WebSite-mandatory\" then=\"WebSite-clone\" then-action=\"start\"/&gt;\n"
" &lt;rsc_colocation id=\"colocation-WebFS-WebDataClone-INFINITY\" rsc=\"WebFS-clone\" score=\"INFINITY\" with-rsc=\"WebDataClone\" with-rsc-role=\"Master\"/&gt;\n"
" &lt;rsc_order first=\"WebDataClone\" first-action=\"promote\" id=\"order-WebDataClone-WebFS-mandatory\" then=\"WebFS-clone\" then-action=\"start\"/&gt;\n"
" &lt;rsc_colocation id=\"colocation-WebSite-WebFS-INFINITY\" rsc=\"WebSite-clone\" score=\"INFINITY\" with-rsc=\"WebFS-clone\"/&gt;\n"
" &lt;rsc_order first=\"WebFS-clone\" first-action=\"start\" id=\"order-WebFS-WebSite-mandatory\" then=\"WebSite-clone\" then-action=\"start\"/&gt;\n"
" &lt;rsc_colocation id=\"colocation-WebFS-clone-dlm-clone-INFINITY\" rsc=\"WebFS-clone\" score=\"INFINITY\" with-rsc=\"dlm-clone\"/&gt;\n"
" &lt;rsc_order first=\"dlm-clone\" first-action=\"start\" id=\"order-dlm-clone-WebFS-clone-mandatory\" then=\"WebFS-clone\" then-action=\"start\"/&gt;\n"
" &lt;/constraints&gt;\n"
" &lt;rsc_defaults&gt;\n"
" &lt;meta_attributes id=\"rsc_defaults-options\"&gt;\n"
" &lt;nvpair id=\"rsc_defaults-options-resource-stickiness\" name=\"resource-stickiness\" value=\"100\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/rsc_defaults&gt;\n"
" &lt;op_defaults&gt;\n"
" &lt;meta_attributes id=\"op_defaults-options\"&gt;\n"
" &lt;nvpair id=\"op_defaults-options-timeout\" name=\"timeout\" value=\"240s\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/op_defaults&gt;\n"
" &lt;/configuration&gt;\n"
" &lt;status&gt;\n"
" &lt;node_state id=\"1\" uname=\"pcmk-1\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_update_resource\" join=\"member\" expected=\"member\"&gt;\n"
" &lt;lrm id=\"1\"&gt;\n"
" &lt;lrm_resources&gt;\n"
" &lt;lrm_resource id=\"WebData\" type=\"drbd\" class=\"ocf\" provider=\"linbit\"&gt;\n"
-" &lt;lrm_rsc_op id=\"WebData_last_0\" operation_key=\"WebData_promote_0\" operation=\"promote\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"13:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;13:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"44\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"26\" queue-time=\"0\" op-digest=\"bc5c2e08730036ec602d79a958821da4\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebData_last_0\" operation_key=\"WebData_promote_0\" operation=\"promote\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"13:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;13:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"44\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"26\" queue-time=\"0\" op-digest=\"bc5c2e08730036ec602d79a958821da4\" on_node=\"pcmk-1\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"dlm\" type=\"controld\" class=\"ocf\" provider=\"pacemaker\"&gt;\n"
-" &lt;lrm_rsc_op id=\"dlm_last_0\" operation_key=\"dlm_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"37:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;37:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"37\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"1041\" queue-time=\"0\" op-digest=\"f2317cad3d54cec5d7d7aa7d0bf35cf8\" on_node=\"pcmk-1\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"dlm_monitor_60000\" operation_key=\"dlm_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"39:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;39:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"38\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264507\" exec-time=\"11\" queue-time=\"0\" op-digest=\"968cc450c09e98fdac3043cb6a194d3d\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"dlm_last_0\" operation_key=\"dlm_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"37:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;37:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"37\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"1041\" queue-time=\"0\" op-digest=\"f2317cad3d54cec5d7d7aa7d0bf35cf8\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"dlm_monitor_60000\" operation_key=\"dlm_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"39:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;39:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"38\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264507\" exec-time=\"11\" queue-time=\"0\" op-digest=\"968cc450c09e98fdac3043cb6a194d3d\" on_node=\"pcmk-1\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"ClusterIP:0\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"ClusterIP:0_last_0\" operation_key=\"ClusterIP:0_monitor_0\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"7:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:7;7:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"19\" rc-code=\"7\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"28\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"ClusterIP:0_last_0\" operation_key=\"ClusterIP:0_monitor_0\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"7:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:7;7:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"19\" rc-code=\"7\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"28\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-1\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"ClusterIP:1\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"ClusterIP:1_last_0\" operation_key=\"ClusterIP:1_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"49:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;49:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"40\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264507\" last-rc-change=\"1419264507\" exec-time=\"190\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-1\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"ClusterIP:1_monitor_30000\" operation_key=\"ClusterIP:1_monitor_30000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"50:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;50:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"41\" rc-code=\"0\" op-status=\"0\" interval=\"30000\" last-rc-change=\"1419264507\" exec-time=\"27\" queue-time=\"0\" op-digest=\"8ce33853c31576b708595f1d8a4a215c\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"ClusterIP:1_last_0\" operation_key=\"ClusterIP:1_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"49:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;49:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"40\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264507\" last-rc-change=\"1419264507\" exec-time=\"190\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"ClusterIP:1_monitor_30000\" operation_key=\"ClusterIP:1_monitor_30000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"50:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;50:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"41\" rc-code=\"0\" op-status=\"0\" interval=\"30000\" last-rc-change=\"1419264507\" exec-time=\"27\" queue-time=\"0\" op-digest=\"8ce33853c31576b708595f1d8a4a215c\" on_node=\"pcmk-1\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"WebFS\" type=\"Filesystem\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"WebFS_last_0\" operation_key=\"WebFS_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"62:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;62:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"46\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"585\" queue-time=\"0\" op-digest=\"9d797b0e3b7f9729195992c0dafb5a9e\" on_node=\"pcmk-1\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"WebFS_monitor_20000\" operation_key=\"WebFS_monitor_20000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"62:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;62:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"47\" rc-code=\"0\" op-status=\"0\" interval=\"20000\" last-rc-change=\"1419264508\" exec-time=\"21\" queue-time=\"1\" op-digest=\"099af723b175851f09e5391e0c13854e\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebFS_last_0\" operation_key=\"WebFS_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"62:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;62:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"46\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"585\" queue-time=\"0\" op-digest=\"9d797b0e3b7f9729195992c0dafb5a9e\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebFS_monitor_20000\" operation_key=\"WebFS_monitor_20000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"62:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;62:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"47\" rc-code=\"0\" op-status=\"0\" interval=\"20000\" last-rc-change=\"1419264508\" exec-time=\"21\" queue-time=\"1\" op-digest=\"099af723b175851f09e5391e0c13854e\" on_node=\"pcmk-1\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"WebSite\" type=\"apache\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"WebSite_last_0\" operation_key=\"WebSite_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"72:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;72:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"48\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"65\" queue-time=\"0\" op-digest=\"49ba395a3f2c142631c2ef2c431a29d9\" on_node=\"pcmk-1\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"WebSite_monitor_60000\" operation_key=\"WebSite_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"73:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;73:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"49\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264508\" exec-time=\"26\" queue-time=\"0\" op-digest=\"eddc33bef3f1592ad847638ee485316f\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebSite_last_0\" operation_key=\"WebSite_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"72:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;72:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"48\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"65\" queue-time=\"0\" op-digest=\"49ba395a3f2c142631c2ef2c431a29d9\" on_node=\"pcmk-1\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebSite_monitor_60000\" operation_key=\"WebSite_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"73:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;73:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"49\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264508\" exec-time=\"26\" queue-time=\"0\" op-digest=\"eddc33bef3f1592ad847638ee485316f\" on_node=\"pcmk-1\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;/lrm_resources&gt;\n"
" &lt;/lrm&gt;\n"
" &lt;transient_attributes id=\"1\"&gt;\n"
" &lt;instance_attributes id=\"status-1\"&gt;\n"
" &lt;nvpair id=\"status-1-shutdown\" name=\"shutdown\" value=\"0\"/&gt;\n"
" &lt;nvpair id=\"status-1-probe_complete\" name=\"probe_complete\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"status-1-master-WebData\" name=\"master-WebData\" value=\"10000\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/transient_attributes&gt;\n"
" &lt;/node_state&gt;\n"
" &lt;node_state id=\"2\" uname=\"pcmk-2\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_update_resource\" join=\"member\" expected=\"member\"&gt;\n"
" &lt;transient_attributes id=\"2\"&gt;\n"
" &lt;instance_attributes id=\"status-2\"&gt;\n"
" &lt;nvpair id=\"status-2-shutdown\" name=\"shutdown\" value=\"0\"/&gt;\n"
" &lt;nvpair id=\"status-2-probe_complete\" name=\"probe_complete\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"status-2-master-WebData\" name=\"master-WebData\" value=\"10000\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/transient_attributes&gt;\n"
" &lt;lrm id=\"2\"&gt;\n"
" &lt;lrm_resources&gt;\n"
" &lt;lrm_resource id=\"WebData\" type=\"drbd\" class=\"ocf\" provider=\"linbit\"&gt;\n"
-" &lt;lrm_rsc_op id=\"WebData_last_0\" operation_key=\"WebData_promote_0\" operation=\"promote\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"16:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;16:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"41\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"26\" queue-time=\"0\" op-digest=\"bc5c2e08730036ec602d79a958821da4\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebData_last_0\" operation_key=\"WebData_promote_0\" operation=\"promote\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"16:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;16:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"41\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"26\" queue-time=\"0\" op-digest=\"bc5c2e08730036ec602d79a958821da4\" on_node=\"pcmk-2\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"dlm\" type=\"controld\" class=\"ocf\" provider=\"pacemaker\"&gt;\n"
-" &lt;lrm_rsc_op id=\"dlm_last_0\" operation_key=\"dlm_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"35:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;35:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"34\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"1053\" queue-time=\"0\" op-digest=\"f2317cad3d54cec5d7d7aa7d0bf35cf8\" on_node=\"pcmk-2\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"dlm_monitor_60000\" operation_key=\"dlm_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"42:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;42:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"35\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264507\" exec-time=\"19\" queue-time=\"0\" op-digest=\"968cc450c09e98fdac3043cb6a194d3d\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"dlm_last_0\" operation_key=\"dlm_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"35:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;35:2:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"34\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"1053\" queue-time=\"0\" op-digest=\"f2317cad3d54cec5d7d7aa7d0bf35cf8\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"dlm_monitor_60000\" operation_key=\"dlm_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"42:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;42:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"35\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264507\" exec-time=\"19\" queue-time=\"0\" op-digest=\"968cc450c09e98fdac3043cb6a194d3d\" on_node=\"pcmk-2\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"ClusterIP:0\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"ClusterIP:0_last_0\" operation_key=\"ClusterIP:0_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"47:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;47:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"36\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264507\" last-rc-change=\"1419264507\" exec-time=\"237\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-2\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"ClusterIP:0_monitor_30000\" operation_key=\"ClusterIP:0_monitor_30000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"51:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;51:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"39\" rc-code=\"0\" op-status=\"0\" interval=\"30000\" last-rc-change=\"1419264507\" exec-time=\"34\" queue-time=\"0\" op-digest=\"8ce33853c31576b708595f1d8a4a215c\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"ClusterIP:0_last_0\" operation_key=\"ClusterIP:0_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"47:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;47:3:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"36\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264507\" last-rc-change=\"1419264507\" exec-time=\"237\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"ClusterIP:0_monitor_30000\" operation_key=\"ClusterIP:0_monitor_30000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"51:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;51:4:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"39\" rc-code=\"0\" op-status=\"0\" interval=\"30000\" last-rc-change=\"1419264507\" exec-time=\"34\" queue-time=\"0\" op-digest=\"8ce33853c31576b708595f1d8a4a215c\" on_node=\"pcmk-2\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"ClusterIP:1\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"ClusterIP:1_last_0\" operation_key=\"ClusterIP:1_monitor_0\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"16:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:7;16:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"23\" rc-code=\"7\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"28\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"ClusterIP:1_last_0\" operation_key=\"ClusterIP:1_monitor_0\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"16:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:7;16:0:7:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"23\" rc-code=\"7\" op-status=\"0\" interval=\"0\" last-run=\"1419264506\" last-rc-change=\"1419264506\" exec-time=\"28\" queue-time=\"0\" op-digest=\"ac61ecc765070218997f6d876fa1d76c\" on_node=\"pcmk-2\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"WebFS\" type=\"Filesystem\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"WebFS_last_0\" operation_key=\"WebFS_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"60:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;60:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"43\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"662\" queue-time=\"0\" op-digest=\"9d797b0e3b7f9729195992c0dafb5a9e\" on_node=\"pcmk-2\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"WebFS_monitor_20000\" operation_key=\"WebFS_monitor_20000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"65:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;65:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"44\" rc-code=\"0\" op-status=\"0\" interval=\"20000\" last-rc-change=\"1419264508\" exec-time=\"29\" queue-time=\"0\" op-digest=\"099af723b175851f09e5391e0c13854e\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebFS_last_0\" operation_key=\"WebFS_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"60:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;60:5:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"43\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"662\" queue-time=\"0\" op-digest=\"9d797b0e3b7f9729195992c0dafb5a9e\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebFS_monitor_20000\" operation_key=\"WebFS_monitor_20000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"65:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;65:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"44\" rc-code=\"0\" op-status=\"0\" interval=\"20000\" last-rc-change=\"1419264508\" exec-time=\"29\" queue-time=\"0\" op-digest=\"099af723b175851f09e5391e0c13854e\" on_node=\"pcmk-2\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;lrm_resource id=\"WebSite\" type=\"apache\" class=\"ocf\" provider=\"heartbeat\"&gt;\n"
-" &lt;lrm_rsc_op id=\"WebSite_last_0\" operation_key=\"WebSite_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"70:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;70:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"45\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"64\" queue-time=\"0\" op-digest=\"49ba395a3f2c142631c2ef2c431a29d9\" on_node=\"pcmk-2\"/&gt;\n"
-" &lt;lrm_rsc_op id=\"WebSite_monitor_60000\" operation_key=\"WebSite_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.9\" transition-key=\"71:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;71:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"46\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264508\" exec-time=\"28\" queue-time=\"0\" op-digest=\"eddc33bef3f1592ad847638ee485316f\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebSite_last_0\" operation_key=\"WebSite_start_0\" operation=\"start\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"70:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;70:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"45\" rc-code=\"0\" op-status=\"0\" interval=\"0\" last-run=\"1419264508\" last-rc-change=\"1419264508\" exec-time=\"64\" queue-time=\"0\" op-digest=\"49ba395a3f2c142631c2ef2c431a29d9\" on_node=\"pcmk-2\"/&gt;\n"
+" &lt;lrm_rsc_op id=\"WebSite_monitor_60000\" operation_key=\"WebSite_monitor_60000\" operation=\"monitor\" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.12\" transition-key=\"71:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" transition-magic=\"0:0;71:6:0:225c8bc5-8fb0-49b6-9f75-337085b080de\" call-id=\"46\" rc-code=\"0\" op-status=\"0\" interval=\"60000\" last-rc-change=\"1419264508\" exec-time=\"28\" queue-time=\"0\" op-digest=\"eddc33bef3f1592ad847638ee485316f\" on_node=\"pcmk-2\"/&gt;\n"
" &lt;/lrm_resource&gt;\n"
" &lt;/lrm_resources&gt;\n"
" &lt;/lrm&gt;\n"
" &lt;/node_state&gt;\n"
" &lt;/status&gt;\n"
"&lt;/cib&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node List"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status nodes\n"
"Pacemaker Nodes:\n"
" Online: pcmk-1 pcmk-2\n"
" Standby:\n"
" Offline:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Cluster Options"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs property\n"
"Cluster Properties:\n"
" cluster-infrastructure: corosync\n"
" cluster-name: mycluster\n"
-" dc-version: 1.1.12-a14efad\n"
+" dc-version: 1.1.16-12.el7_4.5-94ff4df\n"
" have-watchdog: false\n"
" last-lrm-refresh: 1439569053\n"
" stonith-enabled: true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The output shows state information automatically obtained about the cluster, including:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">cluster-infrastructure</emphasis> - the cluster communications layer in use (heartbeat or corosync)"
+msgid "<emphasis role=\"strong\">cluster-infrastructure</emphasis> - the cluster communications layer in use"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">cluster-name</emphasis> - the cluster name chosen by the administrator when the cluster was created"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">dc-version</emphasis> - the version (including upstream source-code hash) of Pacemaker used on the Designated Controller"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The output also shows options set by the administrator that control the way the cluster operates, including:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">stonith-enabled=true</emphasis> - whether the cluster is allowed to use STONITH resources"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resources"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Default Options"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource defaults\n"
"resource-stickiness: 100"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This shows cluster option defaults that apply to every resource that does not explicitly set the option itself. Above:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">resource-stickiness</emphasis> - Specify the aversion to moving healthy resources to other machines"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Fencing"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs stonith show\n"
" ipmi-fencing (stonith:fence_ipmilan) Started\n"
"[root@pcmk-1 ~]# pcs stonith show ipmi-fencing\n"
" Resource: ipmi-fencing (class=stonith type=fence_ipmilan)\n"
" Attributes: ipaddr=\"10.0.0.1\" login=\"testuser\" passwd=\"acd123\" pcmk_host_list=\"pcmk-1 pcmk-2\"\n"
" Operations: monitor interval=60s (fence-monitor-interval-60s)"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Service Address"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Users of the services provided by the cluster require an unchanging address with which to access it. Additionally, we cloned the address so it will be active on both nodes. An iptables rule (created as part of the resource agent) is used to ensure that each request only gets processed by one of the two clone instances. The additional meta options tell the cluster that we want two instances of the clone (one \"request bucket\" for each node) and that if one node fails, then the remaining node should hold both."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource show ClusterIP-clone\n"
" Clone: ClusterIP-clone\n"
" Meta Attrs: clone-max=2 clone-node-max=2 globally-unique=true\n"
" Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2)\n"
" Attributes: ip=192.168.122.120 cidr_netmask=32 clusterip_hash=sourceip\n"
" Operations: start interval=0s timeout=20s (ClusterIP-start-timeout-20s)\n"
" stop interval=0s timeout=20s (ClusterIP-stop-timeout-20s)\n"
" monitor interval=30s (ClusterIP-monitor-interval-30s)"
msgstr ""
#. Tag: title
#, no-c-format
msgid "DRBD - Shared Storage"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here, we define the DRBD service and specify which DRBD resource (from /etc/drbd.d/*.res) it should manage. We make it a master/slave resource and, in order to have an active/active setup, allow both instances to be promoted to master at the same time. We also set the notify option so that the cluster will tell DRBD agent when its peer changes state."
+msgid "Here, we define the DRBD service and specify which DRBD resource (from /etc/drbd.d/*.res) it should manage. We make it a promotable clone resource and, in order to have an active/active setup, allow both instances to be promoted to master at the same time. We also set the notify option so that the cluster will tell DRBD agent when its peer changes state."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource show WebDataClone\n"
" Master: WebDataClone\n"
" Meta Attrs: master-max=2 master-node-max=1 clone-max=2 clone-node-max=1 notify=true\n"
" Resource: WebData (class=ocf provider=linbit type=drbd)\n"
" Attributes: drbd_resource=wwwdata\n"
" Operations: start interval=0s timeout=240 (WebData-start-timeout-240)\n"
" promote interval=0s timeout=90 (WebData-promote-timeout-90)\n"
" demote interval=0s timeout=90 (WebData-demote-timeout-90)\n"
" stop interval=0s timeout=100 (WebData-stop-timeout-100)\n"
" monitor interval=60s (WebData-monitor-interval-60s)\n"
"[root@pcmk-1 ~]# pcs constraint ref WebDataClone\n"
"Resource: WebDataClone\n"
" colocation-WebFS-WebDataClone-INFINITY\n"
" order-WebDataClone-WebFS-mandatory"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Cluster Filesystem"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster filesystem ensures that files are read and written correctly. We need to specify the block device (provided by DRBD), where we want it mounted and that we are using GFS2. Again, it is a clone because it is intended to be active on both nodes. The additional constraints ensure that it can only be started on nodes with active DLM and DRBD instances."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource show WebFS-clone\n"
" Clone: WebFS-clone\n"
" Resource: WebFS (class=ocf provider=heartbeat type=Filesystem)\n"
" Attributes: device=/dev/drbd1 directory=/var/www/html fstype=gfs2\n"
" Operations: start interval=0s timeout=60 (WebFS-start-timeout-60)\n"
" stop interval=0s timeout=60 (WebFS-stop-timeout-60)\n"
" monitor interval=20 timeout=40 (WebFS-monitor-interval-20)\n"
"[root@pcmk-1 ~]# pcs constraint ref WebFS-clone\n"
"Resource: WebFS-clone\n"
" colocation-WebFS-WebDataClone-INFINITY\n"
" colocation-WebSite-WebFS-INFINITY\n"
" colocation-WebFS-clone-dlm-clone-INFINITY\n"
" order-WebDataClone-WebFS-mandatory\n"
" order-WebFS-WebSite-mandatory\n"
" order-dlm-clone-WebFS-clone-mandatory"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Apache"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Lastly, we have the actual service, Apache. We need only tell the cluster where to find its main configuration file and restrict it to running on nodes that have the required filesystem mounted and the IP address active."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource show WebSite-clone\n"
" Clone: WebSite-clone\n"
" Resource: WebSite (class=ocf provider=heartbeat type=apache)\n"
" Attributes: configfile=/etc/httpd/conf/httpd.conf statusurl=http://localhost/server-status\n"
" Operations: start interval=0s timeout=40s (WebSite-start-timeout-40s)\n"
" stop interval=0s timeout=60s (WebSite-stop-timeout-60s)\n"
" monitor interval=1min (WebSite-monitor-interval-1min)\n"
"[root@pcmk-1 ~]# pcs constraint ref WebSite-clone\n"
"Resource: WebSite-clone\n"
" colocation-WebSite-ClusterIP-INFINITY\n"
" colocation-WebSite-WebFS-INFINITY\n"
" order-ClusterIP-WebSite-mandatory\n"
" order-WebFS-WebSite-mandatory"
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot b/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot
index 9ccad5cdc1..20fa36d0fe 100644
--- a/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot
+++ b/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot
@@ -1,54 +1,54 @@
#
# 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"
+"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 "Sample Corosync Configuration"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sample <literal>corosync.conf</literal> for two-node cluster created by <literal>pcs</literal>."
msgstr ""
#. Tag: literallayout
#, 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: pcmk-1\n"
" nodeid: 1\n"
" }\n"
" node {\n"
" ring0_addr: pcmk-2\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 ""
diff --git a/doc/Clusters_from_Scratch/pot/Ap-Reading.pot b/doc/Clusters_from_Scratch/pot/Ap-Reading.pot
index 80f31804e5..924b9cfdc0 100644
--- a/doc/Clusters_from_Scratch/pot/Ap-Reading.pot
+++ b/doc/Clusters_from_Scratch/pot/Ap-Reading.pot
@@ -1,34 +1,34 @@
#
# 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"
+"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 "Further Reading"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Project Website <ulink url=\"http://www.clusterlabs.org/\">http://www.clusterlabs.org/</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "SuSE has a comprehensive guide to cluster commands (though using the <literal>crmsh</literal> command-line shell rather than <literal>pcs</literal>) at: <ulink url=\"https://www.suse.com/documentation/sle_ha/book_sleha/data/book_sleha.html\">https://www.suse.com/documentation/sle_ha/book_sleha/data/book_sleha.html</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Corosync <ulink url=\"http://www.corosync.org/\">http://www.corosync.org/</ulink>"
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Author_Group.pot b/doc/Clusters_from_Scratch/pot/Author_Group.pot
index 82963b7dd2..82db9d5ef0 100644
--- a/doc/Clusters_from_Scratch/pot/Author_Group.pot
+++ b/doc/Clusters_from_Scratch/pot/Author_Group.pot
@@ -1,64 +1,34 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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: firstname
#, no-c-format
msgid "Andrew"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Beekhof"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "Red Hat"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Primary author"
msgstr ""
-#. Tag: firstname
-#, no-c-format
-msgid "Raoul"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "Scarazzini"
-msgstr ""
-
-#. Tag: contrib
-#, no-c-format
-msgid "Italian translation"
-msgstr ""
-
-#. Tag: firstname
-#, no-c-format
-msgid "Dan"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "Frîncu"
-msgstr ""
-
-#. Tag: contrib
-#, no-c-format
-msgid "Romanian translation"
-msgstr ""
-
diff --git a/doc/Clusters_from_Scratch/pot/Book_Info.pot b/doc/Clusters_from_Scratch/pot/Book_Info.pot
index 059d4534e9..6a06d70d88 100644
--- a/doc/Clusters_from_Scratch/pot/Book_Info.pot
+++ b/doc/Clusters_from_Scratch/pot/Book_Info.pot
@@ -1,69 +1,69 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Clusters from Scratch"
msgstr ""
#. Tag: subtitle
#, no-c-format
msgid "Step-by-Step Instructions for Building Your First High-Availability Cluster"
msgstr ""
#. Tag: productname
#, no-c-format
msgid "Pacemaker"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The purpose of this document is to provide a start-to-finish guide to building an example active/passive cluster with Pacemaker and show how it can be converted to an active/active one."
+msgid "This document provides a step-by-step guide to building a simple high-availability cluster using Pacemaker."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The example cluster will use:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "&DISTRO; &DISTRO_VERSION; as the host operating system"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Corosync to provide messaging and membership services,"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker to perform resource management,"
+msgid "Pacemaker 1.1.16 <footnote><para>While this guide is part of the document set for Pacemaker 2.0, it demonstrates the version available in the standard &DISTRO; repositories</para></footnote> to perform resource management,"
msgstr ""
#. Tag: para
#, no-c-format
msgid "DRBD as a cost-effective alternative to shared storage,"
msgstr ""
#. Tag: para
#, no-c-format
msgid "GFS2 as the cluster filesystem (in active/active mode)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Given the graphical nature of the install process, a number of screenshots are included. However the guide is primarily composed of commands, the reasons for executing them and their expected outputs."
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot b/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot
index 5b1e4aa458..cfd2feb130 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot
@@ -1,489 +1,481 @@
#
# 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"
+"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 "Convert Cluster to Active/Active"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The primary requirement for an Active/Active cluster is that the data required for your services is available, simultaneously, on both machines. Pacemaker makes no requirement on how this is achieved; you could use a SAN if you had one available, but since DRBD supports multiple Primaries, we can continue to use it here."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Install Cluster Filesystem Software"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The only hitch is that we need to use a cluster-aware filesystem. The one we used earlier with DRBD, xfs, is not one of those. Both OCFS2 and GFS2 are supported; here, we will use GFS2."
msgstr ""
#. Tag: para
#, no-c-format
msgid "On both nodes, install the GFS2 command-line utilities and the Distributed Lock Manager (DLM) required by cluster filesystems:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y gfs2-utils dlm"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the Cluster for the DLM"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The DLM needs to run on both nodes, so we’ll start by creating a resource for it (using the <emphasis role=\"strong\">ocf:pacemaker:controld</emphasis> resource script), and clone it:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib dlm_cfg\n"
"[root@pcmk-1 ~]# pcs -f dlm_cfg resource create dlm ocf:pacemaker:controld op monitor interval=60s\n"
"[root@pcmk-1 ~]# pcs -f dlm_cfg resource clone dlm clone-max=2 clone-node-max=1\n"
"[root@pcmk-1 ~]# pcs -f dlm_cfg resource show\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started\n"
" WebSite (ocf::heartbeat:apache): Started\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-2 ]\n"
" Slaves: [ pcmk-1 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Started\n"
" Clone Set: dlm-clone [dlm]\n"
" Stopped: [ pcmk-1 pcmk-2 ]"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Activate our new configuration, and see how the cluster responds:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib-push dlm_cfg\n"
"CIB updated\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 14 11:19:36 2015\n"
-"Last change: Fri Aug 14 11:19:28 2015\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"8 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 11:19:36 2018\n"
+"Last change: Fri Jan 12 11:19:28 2018\n"
"\n"
+"2 nodes configured\n"
+"8 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-2\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-2 ]\n"
" Slaves: [ pcmk-1 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Started pcmk-2\n"
" ipmi-fencing (stonith:fence_ipmilan): Started pcmk-1\n"
" Clone Set: dlm-clone [dlm]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Create and Populate GFS2 Filesystem"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before we do anything to the existing partition, we need to make sure it is unmounted. We do this by telling the cluster to stop the WebFS resource. This will ensure that other resources (in our case, Apache) using WebFS are not only stopped, but stopped in the correct order."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource disable WebFS\n"
"[root@pcmk-1 ~]# pcs resource\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started\n"
" WebSite (ocf::heartbeat:apache): Stopped\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-2 ]\n"
" Slaves: [ pcmk-1 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Stopped\n"
" Clone Set: dlm-clone [dlm]\n"
" Started: [ pcmk-1 pcmk-2 ]"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can see that both Apache and WebFS have been stopped, and that <emphasis role=\"strong\">pcmk-2</emphasis> is the current master for the DRBD device."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now we can create a new GFS2 filesystem on the DRBD device."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This will erase all previous content stored on the DRBD device. Ensure you have a copy of any important data."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Run the next command on whichever node has the DRBD Primary role. Otherwise, you will receive the message:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "/dev/drbd1: Read-only file system"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-2 ~]# mkfs.gfs2 -p lock_dlm -j 2 -t mycluster:web /dev/drbd1\n"
"It appears to contain an existing filesystem (xfs)\n"
"This will destroy any data on /dev/drbd1\n"
"Are you sure you want to proceed? [y/n]y\n"
"Device: /dev/drbd1\n"
"Block size: 4096\n"
"Device size: 1.00 GB (262127 blocks)\n"
"Filesystem size: 1.00 GB (262126 blocks)\n"
"Journals: 2\n"
"Resource groups: 5\n"
"Locking protocol: \"lock_dlm\"\n"
"Lock table: \"mycluster:web\"\n"
"UUID: 9a72c488-d8a7-24c9-ceee-add7a8ca52c2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>mkfs.gfs2</literal> command required a number of additional parameters:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>-p lock_dlm</literal> specifies that we want to use the kernel’s DLM."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>-j 2</literal> indicates that the filesystem should reserve enough space for two journals (one for each node that will access the filesystem)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>-t mycluster:web</literal> specifies the lock table name. The format for this field is <literal><replaceable>clustername:fsname</replaceable></literal>. For <literal><replaceable>clustername</replaceable></literal>, we need to use the same value we specified originally with <literal>pcs cluster setup --name</literal> (which is also the value of <emphasis role=\"strong\">cluster_name</emphasis> in <literal>/etc/corosync/corosync.conf</literal>). If you are unsure what your cluster name is, you can look in <literal>/etc/corosync/corosync.conf</literal> or execute the command <literal>pcs cluster corosync pcmk-1 | grep cluster_name</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now we can (re-)populate the new filesystem with data (web pages). We’ll create yet another variation on our home page."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-2 ~]# mount /dev/drbd1 /mnt\n"
"[root@pcmk-2 ~]# cat &lt;&lt;-END &gt;/mnt/index.html\n"
"&lt;html&gt;\n"
"&lt;body&gt;My Test Site - GFS2&lt;/body&gt;\n"
"&lt;/html&gt;\n"
"END\n"
"[root@pcmk-2 ~]# chcon -R --reference=/var/www/html /mnt\n"
"[root@pcmk-2 ~]# umount /dev/drbd1\n"
"[root@pcmk-2 ~]# drbdadm verify wwwdata"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Reconfigure the Cluster for GFS2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "With the WebFS resource stopped, let’s update the configuration."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource show WebFS\n"
" Resource: WebFS (class=ocf provider=heartbeat type=Filesystem)\n"
" Attributes: device=/dev/drbd1 directory=/var/www/html fstype=xfs\n"
" Meta Attrs: target-role=Stopped\n"
" Operations: start interval=0s timeout=60 (WebFS-start-timeout-60)\n"
" stop interval=0s timeout=60 (WebFS-stop-timeout-60)\n"
" monitor interval=20 timeout=40 (WebFS-monitor-interval-20)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The fstype option needs to be updated to <emphasis role=\"strong\">gfs2</emphasis> instead of <emphasis role=\"strong\">xfs</emphasis>."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource update WebFS fstype=gfs2\n"
"[root@pcmk-1 ~]# pcs resource show WebFS\n"
" Resource: WebFS (class=ocf provider=heartbeat type=Filesystem)\n"
" Attributes: device=/dev/drbd1 directory=/var/www/html fstype=gfs2\n"
" Meta Attrs: target-role=Stopped\n"
" Operations: start interval=0s timeout=60 (WebFS-start-timeout-60)\n"
" stop interval=0s timeout=60 (WebFS-stop-timeout-60)\n"
" monitor interval=20 timeout=40 (WebFS-monitor-interval-20)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "GFS2 requires that DLM be running, so we also need to set up new colocation and ordering constraints for it:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint colocation add WebFS with dlm-clone INFINITY\n"
"[root@pcmk-1 ~]# pcs constraint order dlm-clone then WebFS\n"
"Adding dlm-clone WebFS (kind: Mandatory) (Options: first-action=start then-action=start)"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Clone the IP address"
msgstr ""
#. Tag: para
#, no-c-format
msgid "There’s no point making the services active on both locations if we can’t reach them both, so let’s clone the IP address."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <emphasis role=\"strong\">IPaddr2</emphasis> resource agent has built-in intelligence for when it is configured as a clone. It will utilize a multicast MAC address to have the local switch send the relevant packets to all nodes in the cluster, together with <emphasis role=\"strong\">iptables clusterip</emphasis> rules on the nodes so that any given packet will be grabbed by exactly one node. This will give us a simple but effective form of load-balancing requests between our two nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Let’s start a new config, and clone our IP:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib loadbalance_cfg\n"
"[root@pcmk-1 ~]# pcs -f loadbalance_cfg resource clone ClusterIP \\\n"
" clone-max=2 clone-node-max=2 globally-unique=true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>clone-max=2</literal> tells the resource agent to split packets this many ways. This should equal the number of nodes that can host the IP."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>clone-node-max=2</literal> says that one node can run up to 2 instances of the clone. This should also equal the number of nodes that can host the IP, so that if any node goes down, another node can take over the failed node’s \"request bucket\". Otherwise, requests intended for the failed node would be discarded."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>globally-unique=true</literal> tells the cluster that one clone isn’t identical to another (each handles a different \"bucket\"). This also tells the resource agent to insert <emphasis role=\"strong\">iptables</emphasis> rules so each host only processes packets in its bucket(s)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Notice that when the ClusterIP becomes a clone, the constraints referencing ClusterIP now reference the clone. This is done automatically by pcs."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f loadbalance_cfg constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
" start ClusterIP-clone then start WebSite (kind:Mandatory)\n"
" promote WebDataClone then start WebFS (kind:Mandatory)\n"
" start WebFS then start WebSite (kind:Mandatory)\n"
" start dlm-clone then start WebFS (kind:Mandatory)\n"
"Colocation Constraints:\n"
" WebSite with ClusterIP-clone (score:INFINITY)\n"
" WebFS with WebDataClone (score:INFINITY) (with-rsc-role:Master)\n"
" WebSite with WebFS (score:INFINITY)\n"
-" WebFS with dlm-clone (score:INFINITY)"
+" WebFS with dlm-clone (score:INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now we must tell the resource how to decide which requests are processed by which hosts. To do this, we specify the <emphasis role=\"strong\">clusterip_hash</emphasis> parameter. The value of <emphasis role=\"strong\">sourceip</emphasis> means that the source IP address of incoming packets will be hashed; each node will process a certain range of hashes."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f loadbalance_cfg resource update ClusterIP clusterip_hash=sourceip"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Load our configuration to the cluster, and see how it responds."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib-push loadbalance_cfg\n"
"CIB updated\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 14 11:32:07 2015\n"
-"Last change: Fri Aug 14 11:32:04 2015\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"9 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 11:32:07 2018\n"
+"Last change: Fri Jan 12 11:32:04 2018\n"
"\n"
+"2 nodes configured\n"
+"9 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" WebSite (ocf::heartbeat:apache): Stopped\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 ]\n"
" Slaves: [ pcmk-2 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Stopped\n"
" ipmi-fencing (stonith:fence_ipmilan): Started pcmk-1\n"
" Clone Set: dlm-clone [dlm]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: ClusterIP-clone [ClusterIP] (unique)\n"
" ClusterIP:0 (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
" ClusterIP:1 (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If desired, you can demonstrate that all request buckets are working by using a tool such as <literal>arping</literal> from several source hosts to see which host responds to each."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Clone the Filesystem and Apache Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that we have a cluster filesystem ready to go, and our nodes can load-balance requests to a shared IP address, we can configure the cluster so both nodes mount the filesystem and respond to web requests."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Clone the filesystem and Apache resources in a new configuration. Notice how pcs automatically updates the relevant constraints again."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib active_cfg\n"
"[root@pcmk-1 ~]# pcs -f active_cfg resource clone WebFS\n"
"[root@pcmk-1 ~]# pcs -f active_cfg resource clone WebSite\n"
"[root@pcmk-1 ~]# pcs -f active_cfg constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
" start ClusterIP-clone then start WebSite-clone (kind:Mandatory)\n"
" promote WebDataClone then start WebFS-clone (kind:Mandatory)\n"
" start WebFS-clone then start WebSite-clone (kind:Mandatory)\n"
" start dlm-clone then start WebFS-clone (kind:Mandatory)\n"
"Colocation Constraints:\n"
" WebSite-clone with ClusterIP-clone (score:INFINITY)\n"
" WebFS-clone with WebDataClone (score:INFINITY) (with-rsc-role:Master)\n"
" WebSite-clone with WebFS-clone (score:INFINITY)\n"
-" WebFS-clone with dlm-clone (score:INFINITY)"
+" WebFS-clone with dlm-clone (score:INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Tell the cluster that it is now allowed to promote both instances to be DRBD Primary (aka. master)."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f active_cfg resource update WebDataClone master-max=2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Finally, load our configuration to the cluster, and re-enable the WebFS resource (which we disabled earlier)."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib-push active_cfg\n"
"CIB updated\n"
"[root@pcmk-1 ~]# pcs resource enable WebFS"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After all the processes are started, the status should look similar to this."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: dlm-clone [dlm]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: ClusterIP-clone [ClusterIP] (unique)\n"
" ClusterIP:0 (ocf::heartbeat:IPaddr2): Started\n"
" ClusterIP:1 (ocf::heartbeat:IPaddr2): Started\n"
" Clone Set: WebFS-clone [WebFS]\n"
" Started: [ pcmk-1 pcmk-2 ]\n"
" Clone Set: WebSite-clone [WebSite]\n"
" Started: [ pcmk-1 pcmk-2 ]"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Test Failover"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Testing failover is left as an exercise for the reader. For example, you can put one node into standby mode, use <literal>pcs status</literal> to confirm that its ClusterIP clone was moved to the other node, and use <literal>arping</literal> to verify that packets are not being lost from any source host."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You may find that when a failed node rejoins the cluster, both ClusterIP clones stay on one node, due to the resource stickiness. While this works fine, it effectively eliminates load-balancing and returns the cluster to an active-passive setup again. You can avoid this by disabling stickiness for the IP address resource:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource meta ClusterIP resource-stickiness=0"
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot b/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot
index ba981a7040..8f43b7011c 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot
@@ -1,508 +1,481 @@
#
# 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"
+"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 "Create an Active/Passive Cluster"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Explore the Existing Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When Pacemaker starts up, it automatically records the number and details of the nodes in the cluster, as well as which stack is being used and the version of Pacemaker being used."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The first few lines of output should look like this:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
"WARNING: no stonith devices and stonith-enabled is not false\n"
-"Last updated: Tue Dec 16 16:15:29 2014\n"
-"Last change: Tue Dec 16 15:49:47 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"0 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 16:15:29 2018\n"
+"Last change: Fri Jan 12 15:49:47 2018\n"
"\n"
+"2 nodes configured\n"
+"0 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For those who are not of afraid of XML, you can see the raw cluster configuration and status by using the <literal>pcs cluster cib</literal> command."
msgstr ""
#. Tag: title
#, no-c-format
msgid "The last XML you’ll see in this document"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "&lt;cib crm_feature_set=\"3.0.9\" validate-with=\"pacemaker-2.3\" epoch=\"5\" num_updates=\"8\" admin_epoch=\"0\" cib-last-written=\"Tue Dec 16 15:49:47 2014\" have-quorum=\"1\" dc-uuid=\"2\"&gt;\n"
+msgid "&lt;cib crm_feature_set=\"3.0.12\" validate-with=\"pacemaker-2.8\" epoch=\"5\" num_updates=\"8\" admin_epoch=\"0\" cib-last-written=\"Fri Jan 12 15:49:47 2018\" have-quorum=\"1\" dc-uuid=\"2\"&gt;\n"
" &lt;configuration&gt;\n"
" &lt;crm_config&gt;\n"
" &lt;cluster_property_set id=\"cib-bootstrap-options\"&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-have-watchdog\" name=\"have-watchdog\" value=\"false\"/&gt;\n"
-" &lt;nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.12-a14efad\"/&gt;\n"
+" &lt;nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.16-12.el7_4.5-94ff4df\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-cluster-infrastructure\" name=\"cluster-infrastructure\" value=\"corosync\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-cluster-name\" name=\"cluster-name\" value=\"mycluster\"/&gt;\n"
" &lt;/cluster_property_set&gt;\n"
" &lt;/crm_config&gt;\n"
" &lt;nodes&gt;\n"
" &lt;node id=\"1\" uname=\"pcmk-1\"/&gt;\n"
" &lt;node id=\"2\" uname=\"pcmk-2\"/&gt;\n"
" &lt;/nodes&gt;\n"
" &lt;resources/&gt;\n"
" &lt;constraints/&gt;\n"
" &lt;/configuration&gt;\n"
" &lt;status&gt;\n"
" &lt;node_state id=\"2\" uname=\"pcmk-2\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_state_transition\" join=\"member\" expected=\"member\"&gt;\n"
" &lt;lrm id=\"2\"&gt;\n"
" &lt;lrm_resources/&gt;\n"
" &lt;/lrm&gt;\n"
" &lt;transient_attributes id=\"2\"&gt;\n"
" &lt;instance_attributes id=\"status-2\"&gt;\n"
" &lt;nvpair id=\"status-2-shutdown\" name=\"shutdown\" value=\"0\"/&gt;\n"
" &lt;nvpair id=\"status-2-probe_complete\" name=\"probe_complete\" value=\"true\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/transient_attributes&gt;\n"
" &lt;/node_state&gt;\n"
" &lt;node_state id=\"1\" uname=\"pcmk-1\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_state_transition\" join=\"member\" expected=\"member\"&gt;\n"
" &lt;lrm id=\"1\"&gt;\n"
" &lt;lrm_resources/&gt;\n"
" &lt;/lrm&gt;\n"
" &lt;transient_attributes id=\"1\"&gt;\n"
" &lt;instance_attributes id=\"status-1\"&gt;\n"
" &lt;nvpair id=\"status-1-shutdown\" name=\"shutdown\" value=\"0\"/&gt;\n"
" &lt;nvpair id=\"status-1-probe_complete\" name=\"probe_complete\" value=\"true\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/transient_attributes&gt;\n"
" &lt;/node_state&gt;\n"
" &lt;/status&gt;\n"
"&lt;/cib&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before we make any changes, it’s a good idea to check the validity of the configuration."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# crm_verify -L -V\n"
" error: unpack_resources: Resource start-up disabled since no STONITH resources have been defined\n"
" error: unpack_resources: Either configure some or disable STONITH with the stonith-enabled option\n"
" error: unpack_resources: NOTE: Clusters with shared data need STONITH to ensure data integrity\n"
"Errors found during check: config not valid"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As you can see, the tool has found some errors."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In order to guarantee the safety of your data, <footnote><para>If the data is corrupt, there is little point in continuing to make it available</para></footnote> the default for STONITH <footnote><para>A common node fencing mechanism. Used to ensure data integrity by powering off \"bad\" nodes</para></footnote> in Pacemaker is <emphasis role=\"strong\">enabled</emphasis>. However, it also knows when no STONITH configuration has been supplied and reports this as a problem (since the cluster would not be able to make progress if a situation requiring node fencing arose)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "We will disable this feature for now and configure it later."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To disable STONITH, set the <emphasis role=\"strong\">stonith-enabled</emphasis> cluster option to false:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs property set stonith-enabled=false\n"
"[root@pcmk-1 ~]# crm_verify -L"
msgstr ""
#. Tag: para
#, no-c-format
msgid "With the new cluster option set, the configuration is now valid."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The use of <literal>stonith-enabled=false</literal> is completely inappropriate for a production cluster. It tells the cluster to simply pretend that failed nodes are safely powered off. Some vendors will refuse to support clusters that have STONITH disabled."
msgstr ""
#. Tag: para
#, no-c-format
msgid "We disable STONITH here only to defer the discussion of its configuration, which can differ widely from one installation to the next. See <xref linkend=\"_what_is_stonith\" /> for information on why STONITH is important and details on how to configure it."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Add a Resource"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Our first resource will be a unique IP address that the cluster can bring up on either node. Regardless of where any cluster service(s) are running, end users need a consistent address to contact them on. Here, I will choose 192.168.122.120 as the floating address, give it the imaginative name ClusterIP and tell the cluster to check whether it is running every 30 seconds."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The chosen address must not already be in use on the network. Do not reuse an IP address one of the nodes already has configured."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource create ClusterIP ocf:heartbeat:IPaddr2 \\\n"
" ip=192.168.122.120 cidr_netmask=32 op monitor interval=30s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another important piece of information here is <emphasis role=\"strong\">ocf:heartbeat:IPaddr2</emphasis>. This tells Pacemaker three things about the resource you want to add:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The first field (<emphasis role=\"strong\">ocf</emphasis> in this case) is the standard to which the resource script conforms and where to find it."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The second field (<emphasis role=\"strong\">heartbeat</emphasis> in this case) is standard-specific; for OCF resources, it tells the cluster which OCF namespace the resource script is in."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The third field (<emphasis role=\"strong\">IPaddr2</emphasis> in this case) is the name of the resource script."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To obtain a list of the available resource standards (the <emphasis role=\"strong\">ocf</emphasis> part of <emphasis role=\"strong\">ocf:heartbeat:IPaddr2</emphasis>), run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource standards\n"
-"ocf\n"
"lsb\n"
+"ocf\n"
"service\n"
-"systemd\n"
-"stonith"
+"systemd"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To obtain a list of the available OCF resource providers (the <emphasis role=\"strong\">heartbeat</emphasis> part of <emphasis role=\"strong\">ocf:heartbeat:IPaddr2</emphasis>), run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource providers\n"
"heartbeat\n"
"openstack\n"
"pacemaker"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Finally, if you want to see all the resource agents available for a specific OCF provider (the <emphasis role=\"strong\">IPaddr2</emphasis> part of <emphasis role=\"strong\">ocf:heartbeat:IPaddr2</emphasis>), run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource agents ocf:heartbeat\n"
+"apache\n"
+"clvm\n"
+"conntrackd\n"
"CTDB\n"
+"db2\n"
"Delay\n"
-"Dummy\n"
-"Filesystem\n"
-"IPaddr\n"
-"IPaddr2\n"
".\n"
". (skipping lots of resources to save space)\n"
".\n"
-"rsyncd\n"
-"slapd\n"
"symlink\n"
-"tomcat"
+"tomcat\n"
+"VirtualDomain\n"
+"Xinetd"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, verify that the IP resource has been added, and display the cluster’s status to see that it is now active:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Tue Dec 16 17:44:40 2014\n"
-"Last change: Tue Dec 16 17:44:26 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"1 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 17:44:40 2018\n"
+"Last change: Fri Jan 12 17:44:26 2018\n"
"\n"
+"2 nodes configured\n"
+"1 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Perform a Failover"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Since our ultimate goal is high availability, we should test failover of our new resource before moving on."
msgstr ""
#. Tag: para
#, no-c-format
msgid "First, find the node on which the IP address is running."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Tue Dec 16 17:44:40 2014\n"
-"Last change: Tue Dec 16 17:44:26 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"1 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 17:44:40 2018\n"
+"Last change: Fri Jan 12 17:44:26 2018\n"
"\n"
+"2 nodes configured\n"
+"1 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can see that the status of the <emphasis role=\"strong\">ClusterIP</emphasis> resource is <emphasis role=\"strong\">Started</emphasis> on a particular node (in this example, <emphasis role=\"strong\">pcmk-1</emphasis>). Shut down Pacemaker and Corosync on that machine to trigger a failover."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster stop pcmk-1\n"
-"Stopping Cluster..."
+"Stopping Cluster (pacemaker)...\n"
+"Stopping Cluster (corosync)..."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A cluster command such as <literal>pcs cluster stop <replaceable>nodename</replaceable></literal> can be run from any node in the cluster, not just the affected node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify that pacemaker and corosync are no longer running:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Error: cluster is not currently running on this node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Go to the other node, and check the cluster status."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-2 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 10:30:56 2014\n"
-"Last change: Tue Dec 16 17:44:26 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"1 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 18:30:56 2018\n"
+"Last change: Fri Jan 12 17:44:26 2018\n"
"\n"
+"2 nodes configured\n"
+"1 resources configured\n"
"\n"
"Online: [ pcmk-2 ]\n"
"OFFLINE: [ pcmk-1 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that <emphasis role=\"strong\">pcmk-1</emphasis> is <emphasis role=\"strong\">OFFLINE</emphasis> for cluster purposes (its <emphasis role=\"strong\">PCSD</emphasis> is still <emphasis role=\"strong\">Online</emphasis>, allowing it to receive <literal>pcs</literal> commands, but it is not participating in the cluster)."
+msgid "Notice that <emphasis role=\"strong\">pcmk-1</emphasis> is <emphasis role=\"strong\">OFFLINE</emphasis> for cluster purposes (its <emphasis role=\"strong\">pcsd</emphasis> is still active, allowing it to receive <literal>pcs</literal> commands, but it is not participating in the cluster)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Also notice that <emphasis role=\"strong\">ClusterIP</emphasis> is now running on <emphasis role=\"strong\">pcmk-2</emphasis> — failover happened automatically, and no errors are reported."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Quorum"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If a cluster splits into two (or more) groups of nodes that can no longer communicate with each other (aka. <emphasis>partitions</emphasis>), <emphasis>quorum</emphasis> is used to prevent resources from starting on more nodes than desired, which would risk data corruption."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A cluster has quorum when more than half of all known nodes are online in the same partition, or for the mathematically inclined, whenever the following equation is true:"
msgstr ""
#. Tag: literallayout
#, no-c-format
msgid "total_nodes &lt; 2 * active_nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, if a 5-node cluster split into 3- and 2-node paritions, the 3-node partition would have quorum and could continue serving resources. If a 6-node cluster split into two 3-node partitions, neither partition would have quorum; pacemaker’s default behavior in such cases is to stop all resources, in order to prevent data corruption."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Two-node clusters are a special case. By the above definition, a two-node cluster would only have quorum when both nodes are running. This would make the creation of a two-node cluster pointless, <footnote><para>Some would argue that two-node clusters are always pointless, but that is an argument for another time</para></footnote> but corosync has the ability to treat two-node clusters as if only one node is required for quorum."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>pcs cluster setup</literal> command will automatically configure <emphasis role=\"strong\">two_node: 1</emphasis> in <literal>corosync.conf</literal>, so a two-node cluster will \"just work\"."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you are using a different cluster shell, you will have to configure <literal>corosync.conf</literal> appropriately yourself. If you are using older versions of corosync, you will have to ignore quorum at the pacemaker level, using <literal>pcs property set no-quorum-policy=ignore</literal> (or the equivalent command if you are using a different cluster shell)."
+msgid "If you are using a different cluster shell, you will have to configure <literal>corosync.conf</literal> appropriately yourself."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, simulate node recovery by restarting the cluster stack on <emphasis role=\"strong\">pcmk-1</emphasis>, and check the cluster’s status. (It may take a little while before the cluster gets going on the node, but it eventually will look like the below.)"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster start pcmk-1\n"
"pcmk-1: Starting Cluster...\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 10:50:11 2014\n"
-"Last change: Tue Dec 16 17:44:26 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"1 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 18:50:11 2018\n"
+"Last change: Fri Jan 12 17:44:26 2018\n"
"\n"
+"2 nodes configured\n"
+"1 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "With older versions of pacemaker, the cluster might move the IP back to its original location (<emphasis role=\"strong\">pcmk-1</emphasis>). Usually, this is no longer the case."
-msgstr ""
-
#. Tag: title
#, no-c-format
msgid "Prevent Resources from Moving after Recovery"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In most circumstances, it is highly desirable to prevent healthy resources from being moved around the cluster. Moving resources almost always requires a period of downtime. For complex services such as databases, this period can be quite long."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To address this, Pacemaker has the concept of resource <emphasis>stickiness</emphasis>, which controls how strongly a service prefers to stay running where it is. You may like to think of it as the \"cost\" of any downtime. By default, Pacemaker assumes there is zero cost associated with moving resources and will do so to achieve \"optimal\" <footnote><para>Pacemaker’s definition of optimal may not always agree with that of a human’s. The order in which Pacemaker processes lists of resources and nodes creates implicit preferences in situations where the administrator has not explicitly specified them.</para></footnote> resource placement. We can specify a different stickiness for every resource, but it is often sufficient to change the default."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource defaults resource-stickiness=100\n"
"[root@pcmk-1 ~]# pcs resource defaults\n"
"resource-stickiness: 100"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Older versions of <literal>pcs</literal> required that <literal>rsc</literal> be added after <literal>resource</literal> in the above commands."
-msgstr ""
-
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Apache.pot b/doc/Clusters_from_Scratch/pot/Ch-Apache.pot
index eef0478953..929e15a7fb 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Apache.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Apache.pot
@@ -1,503 +1,484 @@
#
# 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"
+"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 "Add Apache HTTP Server as a Cluster Service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Apache HTTP Server</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that we have a basic but functional active/passive two-node cluster, we’re ready to add some real services. We’re going to start with Apache HTTP Server because it is a feature of many clusters and relatively simple to configure."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Install Apache"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before continuing, we need to make sure Apache is installed on both hosts. We also need the wget tool in order for the cluster to be able to check the status of the Apache server."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y httpd wget\n"
"# firewall-cmd --permanent --add-service=http\n"
"# firewall-cmd --reload"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do <emphasis role=\"strong\">not</emphasis> enable the httpd service. Services that are intended to be managed via the cluster software should never be managed by the OS."
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is often useful, however, to manually start the service, verify that it works, then stop it again, before adding it to the cluster. This allows you to resolve any non-cluster-related problems before continuing. Since this is a simple example, we’ll skip that step here."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Create Website Documents"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We need to create a page for Apache to serve. On &DISTRO; &DISTRO_VERSION;, the default Apache document root is /var/www/html, so we’ll create an index file there. For the moment, we will simplify things by serving a static site and manually synchronizing the data between the two nodes, so run this command on both nodes:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cat &lt;&lt;-END &gt;/var/www/html/index.html\n"
" &lt;html&gt;\n"
" &lt;body&gt;My Test Site - $(hostname)&lt;/body&gt;\n"
" &lt;/html&gt;\n"
"END"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Enable the Apache status URL"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Apache HTTP Server</primary><secondary>/server-status</secondary> </indexterm> <indexterm> <primary>/server-status</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In order to monitor the health of your Apache instance, and recover it if it fails, the resource agent used by Pacemaker assumes the server-status URL is available. On both nodes, enable the URL with:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cat &lt;&lt;-END &gt;/etc/httpd/conf.d/status.conf\n"
" &lt;Location /server-status&gt;\n"
" SetHandler server-status\n"
" Require local\n"
" &lt;/Location&gt;\n"
"END"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you are using a different operating system, server-status may already be enabled or may be configurable in a different location. If you are using a version of Apache HTTP Server less than 2.4, the syntax will be different."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the Cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Apache HTTP Server</primary><secondary>Apache resource configuration</secondary> </indexterm> <indexterm> <primary>Apache resource configuration</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "At this point, Apache is ready to go, and all that needs to be done is to add it to the cluster. Let’s call the resource WebSite. We need to use an OCF resource script called apache in the heartbeat namespace. <footnote><para>Compare the key used here, <emphasis role=\"strong\">ocf:heartbeat:apache</emphasis>, with the one we used earlier for the IP address, <emphasis role=\"strong\">ocf:heartbeat:IPaddr2</emphasis></para></footnote> The script’s only required parameter is the path to the main Apache configuration file, and we’ll tell the cluster to check once a minute that Apache is still running."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource create WebSite ocf:heartbeat:apache \\\n"
" configfile=/etc/httpd/conf/httpd.conf \\\n"
" statusurl=\"http://localhost/server-status\" \\\n"
" op monitor interval=1min"
msgstr ""
#. Tag: para
#, no-c-format
msgid "By default, the operation timeout for all resources' start, stop, and monitor operations is 20 seconds. In many cases, this timeout period is less than a particular resource’s advised timeout period. For the purposes of this tutorial, we will adjust the global operation timeout default to 240 seconds."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs resource op defaults timeout=240s\n"
"[root@pcmk-1 ~]# pcs resource op defaults\n"
"timeout: 240s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In a production cluster, it is usually better to adjust each resource’s start, stop, and monitor timeouts to values that are appropriate to the behavior observed in your environment, rather than adjust the global default."
msgstr ""
#. Tag: para
#, no-c-format
msgid "After a short delay, we should see the cluster start Apache."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 12:40:41 2014\n"
-"Last change: Wed Dec 17 12:40:05 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"2 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 12:40:41 2018\n"
+"Last change: Fri Jan 12 12:40:05 2018\n"
"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-1\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Wait a moment, the WebSite resource isn’t running on the same host as our IP address!"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If, in the <literal>pcs status</literal> output, you see the WebSite resource has failed to start, then you’ve likely not enabled the status URL correctly. You can check whether this is the problem by running:"
msgstr ""
#. Tag: literallayout
#, no-c-format
msgid "wget -O - http://localhost/server-status"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you see <emphasis role=\"strong\">Not Found</emphasis> or <emphasis role=\"strong\">Forbidden</emphasis> in the output, then this is likely the problem. Ensure that the <emphasis role=\"strong\">&lt;Location /server-status&gt;</emphasis> block is correct."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ensure Resources Run on the Same Host"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To reduce the load on any one machine, Pacemaker will generally try to spread the configured resources across the cluster nodes. However, we can tell the cluster that two resources are related and need to run on the same host (or not at all). Here, we instruct the cluster that WebSite can only run on the host that ClusterIP is active on."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To achieve this, we use a <emphasis>colocation constraint</emphasis> that indicates it is mandatory for WebSite to run on the same node as ClusterIP. The \"mandatory\" part of the colocation constraint is indicated by using a score of INFINITY. The INFINITY score also means that if ClusterIP is not active anywhere, WebSite will not be permitted to run."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If ClusterIP is not active anywhere, WebSite will not be permitted to run anywhere."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Colocation constraints are \"directional\", in that they imply certain things about the order in which the two resources will have a location chosen. In this case, we’re saying that <emphasis role=\"strong\">WebSite</emphasis> needs to be placed on the same machine as <emphasis role=\"strong\">ClusterIP</emphasis>, which implies that the cluster must know the location of <emphasis role=\"strong\">ClusterIP</emphasis> before choosing a location for <emphasis role=\"strong\">WebSite</emphasis>."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint colocation add WebSite with ClusterIP INFINITY\n"
"[root@pcmk-1 ~]# pcs constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
"Colocation Constraints:\n"
" WebSite with ClusterIP (score:INFINITY)\n"
+"Ticket Constraints:\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 13:57:58 2014\n"
-"Last change: Wed Dec 17 13:57:22 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"2 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 13:57:58 2018\n"
+"Last change: Fri Jan 12 13:57:22 2018\n"
"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ensure Resources Start and Stop in Order"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Like many services, Apache can be configured to bind to specific IP addresses on a host or to the wildcard IP address. If Apache binds to the wildcard, it doesn’t matter whether an IP address is added before or after Apache starts; Apache will respond on that IP just the same. However, if Apache binds only to certain IP address(es), the order matters: If the address is added after Apache starts, Apache won’t respond on that address."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To be sure our WebSite responds regardless of Apache’s address configuration, we need to make sure ClusterIP not only runs on the same node, but starts before WebSite. A colocation constraint only ensures the resources run together, not the order in which they are started and stopped."
msgstr ""
#. Tag: para
#, no-c-format
msgid "We do this by adding an ordering constraint. By default, all order constraints are mandatory, which means that the recovery of ClusterIP will also trigger the recovery of WebSite."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint order ClusterIP then WebSite\n"
"Adding ClusterIP WebSite (kind: Mandatory) (Options: first-action=start then-action=start)\n"
"[root@pcmk-1 ~]# pcs constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
" start ClusterIP then start WebSite (kind:Mandatory)\n"
"Colocation Constraints:\n"
-" WebSite with ClusterIP (score:INFINITY)"
+" WebSite with ClusterIP (score:INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prefer One Node Over Another"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker does not rely on any sort of hardware symmetry between nodes, so it may well be that one machine is more powerful than the other. In such cases, it makes sense to host the resources on the more powerful node if it is available. To do this, we create a location constraint."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the location constraint below, we are saying the WebSite resource prefers the node pcmk-1 with a score of 50. Here, the score indicates how badly we’d like the resource to run at this location."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint location WebSite prefers pcmk-1=50\n"
"[root@pcmk-1 ~]# pcs constraint\n"
"Location Constraints:\n"
" Resource: WebSite\n"
" Enabled on: pcmk-1 (score:50)\n"
"Ordering Constraints:\n"
" start ClusterIP then start WebSite (kind:Mandatory)\n"
"Colocation Constraints:\n"
" WebSite with ClusterIP (score:INFINITY)\n"
+"Ticket Constraints:\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 14:11:49 2014\n"
-"Last change: Wed Dec 17 14:11:20 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"2 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 14:11:49 2018\n"
+"Last change: Fri Jan 12 14:11:20 2018\n"
"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Wait a minute, the resources are still on pcmk-2!"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Even though WebSite now prefers to run on pcmk-1, that preference is (intentionally) less than the resource stickiness (how much we preferred not to have unnecessary downtime)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To see the current placement scores, you can use a tool called crm_simulate."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# crm_simulate -sL\n"
"\n"
"Current cluster status:\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-2\n"
"\n"
"Allocation scores:\n"
"native_color: ClusterIP allocation score on pcmk-1: 50\n"
"native_color: ClusterIP allocation score on pcmk-2: 200\n"
"native_color: WebSite allocation score on pcmk-1: -INFINITY\n"
"native_color: WebSite allocation score on pcmk-2: 100\n"
"\n"
"Transition Summary:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Move Resources Manually"
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are always times when an administrator needs to override the cluster and force resources to move to a specific location. In this example, we will force the WebSite to move to pcmk-1 by updating our previous location constraint with a score of INFINITY."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint location WebSite prefers pcmk-1=INFINITY\n"
"[root@pcmk-1 ~]# pcs constraint\n"
"Location Constraints:\n"
" Resource: WebSite\n"
" Enabled on: pcmk-1 (score:INFINITY)\n"
"Ordering Constraints:\n"
" start ClusterIP then start WebSite (kind:Mandatory)\n"
"Colocation Constraints:\n"
" WebSite with ClusterIP (score:INFINITY)\n"
+"Ticket Constraints:\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 14:19:34 2014\n"
-"Last change: Wed Dec 17 14:18:37 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"2 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 14:19:34 2018\n"
+"Last change: Fri Jan 12 14:18:37 2018\n"
"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-1\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once we’ve finished whatever activity required us to move the resources to pcmk-1 (in our case nothing), we can then allow the cluster to resume normal operation by removing the new constraint. Since we previously configured a default stickiness, the resources will remain on pcmk-1."
msgstr ""
#. Tag: para
#, no-c-format
msgid "First, use the <literal>--full</literal> option to get the constraint’s ID:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint --full\n"
"Location Constraints:\n"
" Resource: WebSite\n"
" Enabled on: pcmk-1 (score:INFINITY) (id:location-WebSite-pcmk-1-INFINITY)\n"
"Ordering Constraints:\n"
" start ClusterIP then start WebSite (kind:Mandatory) (id:order-ClusterIP-WebSite-mandatory)\n"
"Colocation Constraints:\n"
-" WebSite with ClusterIP (score:INFINITY) (id:colocation-WebSite-ClusterIP-INFINITY)"
+" WebSite with ClusterIP (score:INFINITY) (id:colocation-WebSite-ClusterIP-INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then remove the desired contraint using its ID:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs constraint remove location-WebSite-pcmk-1-INFINITY\n"
"[root@pcmk-1 ~]# pcs constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
" start ClusterIP then start WebSite (kind:Mandatory)\n"
"Colocation Constraints:\n"
-" WebSite with ClusterIP (score:INFINITY)"
+" WebSite with ClusterIP (score:INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Note that the location constraint is now gone. If we check the cluster status, we can also see that (as expected) the resources are still active on pcmk-1."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Wed Dec 17 14:25:21 2014\n"
-"Last change: Wed Dec 17 14:24:29 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"2 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 14:25:21 2018\n"
+"Last change: Fri Jan 12 14:24:29 2018\n"
"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-1\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Installation.pot b/doc/Clusters_from_Scratch/pot/Ch-Installation.pot
index 235bfe96d2..7dc5969367 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Installation.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Installation.pot
@@ -1,712 +1,707 @@
#
# 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"
+"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-1503-01.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."
+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 redhat1 | passwd --stdin hacluster'"
+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 "Early versions of pcs required that <literal>--name</literal> be omitted from the above command."
-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 the now-defunct <ulink url=\"http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html\">http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html</ulink> or the more detailed treatment in <ulink url=\"http://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> paper.</para></footnote>"
+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 /etc/corosync.conf configuration on each node should look something like the sample in <xref linkend=\"ap-corosync-conf\" />."
+msgid "The final corosync.conf configuration on each node should look something like the sample in <xref linkend=\"ap-corosync-conf\" />."
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot b/doc/Clusters_from_Scratch/pot/Ch-Intro.pot
index aac7c18789..b330726596 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Intro.pot
@@ -1,289 +1,369 @@
#
# 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"
+"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 "Read-Me-First"
msgstr ""
#. Tag: title
#, no-c-format
msgid "The Scope of this Document"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Computer clusters can be used to provide highly available services or resources. The redundancy of multiple machines is used to guard against failures of many types."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This document will walk through the installation and setup of simple clusters using the &DISTRO; distribution, version &DISTRO_VERSION;."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The clusters described here will use Pacemaker and Corosync to provide resource management and messaging. Required packages and modifications to their configuration files are described along with the use of the Pacemaker command line tool for generating the XML used for cluster control."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker is a central component and provides the resource management required in these systems. This management includes detecting and recovering from the failure of various nodes, resources and services under its control."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When more in depth information is required and for real world usage, please refer to the <ulink url=\"http://www.clusterlabs.org/doc/\">Pacemaker Explained</ulink> manual."
+msgid "When more in-depth information is required, and for real-world usage, please refer to the <ulink url=\"https://www.clusterlabs.org/pacemaker/doc/\">Pacemaker Explained</ulink> manual."
msgstr ""
#. Tag: title
#, no-c-format
msgid "What Is <emphasis>Pacemaker</emphasis>?"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker is a <emphasis>cluster resource manager</emphasis>, that is, a logic responsible for a life-cycle of deployed software — indirectly perhaps even whole systems or their interconnections — under its control within a set of computers (a.k.a. <emphasis>nodes</emphasis>) and driven by prescribed rules."
+msgid "<emphasis role=\"strong\">Pacemaker</emphasis> is a high-availability <emphasis>cluster resource manager</emphasis> — software that runs on a set of hosts (a <emphasis>cluster</emphasis> of <emphasis>nodes</emphasis>) in order to minimize downtime of desired services (<emphasis>resources</emphasis>). <footnote><para> <emphasis>Cluster</emphasis> is sometimes used in other contexts to refer to hosts grouped together for other purposes, such as high-performance computing (HPC), but Pacemaker is not intended for those purposes. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It achieves maximum availability for your cluster services (a.k.a. <emphasis>resources</emphasis>) by detecting and recovering from node- and resource-level failures by making use of the messaging and membership capabilities provided by your preferred cluster infrastructure (either <ulink url=\"http://www.corosync.org/\">Corosync</ulink> or <ulink url=\"http://linux-ha.org/wiki/Heartbeat\">Heartbeat</ulink>), and possibly by utilizing other parts of the overall cluster stack."
+msgid "Pacemaker’s key features include:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For <emphasis role=\"strong\">the goal of minimal downtime</emphasis> a term <emphasis>high availability</emphasis> was coined and together with its acronym, <emphasis>HA</emphasis>, is well-established in the sector. To differentiate this sort of clusters from high performance computing (<emphasis>HPC</emphasis>) ones, should a context require it (apparently, not the case in this document), using <emphasis>HA cluster</emphasis> is an option."
+msgid "Detection of and recovery from node- and service-level failures"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker’s key features include:"
+msgid "Ability to ensure data integrity by fencing faulty nodes"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Detection and recovery of node and service-level failures"
+msgid "Support for one or more nodes per cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Storage agnostic, no requirement for shared storage"
+msgid "Support for multiple resource interface standards (anything that can be scripted can be clustered)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resource agnostic, anything that can be scripted can be clustered"
+msgid "Support (but no requirement) for shared storage"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports <emphasis>fencing</emphasis> (also referred to as the <emphasis>STONITH</emphasis> acronym, <link linkend=\"s-intro-stonith\">deciphered</link> later on) for ensuring data integrity"
+msgid "Support for practically any redundancy configuration (active/passive, N+1, etc.)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports large and small clusters"
+msgid "Automatically replicated configuration that can be updated from any node"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports both quorate and resource-driven clusters"
+msgid "Ability to specify cluster-wide relationships between services, such as ordering, colocation and anti-colocation"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports practically any redundancy configuration"
+msgid "Support for advanced service types, such as <emphasis>clones</emphasis> (services that need to be active on multiple nodes), <emphasis>stateful resources</emphasis> (clones that can run in one of two modes), and containerized services"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Automatically replicated configuration that can be updated from any node"
+msgid "Unified, scriptable cluster management tools"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fencing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fencing</emphasis>, also known as <emphasis>STONITH</emphasis> (an acronym for Shoot The Other Node In The Head), is the ability to ensure that it is not possible for a node to be running a service. This is accomplished via <emphasis>fence devices</emphasis> such as intelligent power switches that cut power to the target, or intelligent network switches that cut the target’s access to the local network."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Ability to specify cluster-wide service ordering, colocation and anti-colocation"
+msgid "Pacemaker represents fence devices as a special class of resource."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Support for advanced service types"
+msgid "A cluster cannot safely recover from certain failure conditions, such as an unresponsive node, without fencing."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Cluster Architecture"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Clones: for services which need to be active on multiple nodes"
+msgid "At a high level, a cluster can viewed as having these parts (which together are often referred to as the <emphasis>cluster stack</emphasis>):"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Multi-state: for services with multiple modes (e.g. master/slave, primary/secondary)"
+msgid "<emphasis role=\"strong\">Resources:</emphasis> These are the reason for the cluster’s being — the services that need to be kept highly available."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unified, scriptable cluster management tools"
+msgid "<emphasis role=\"strong\">Resource agents:</emphasis> These are scripts or operating system components that start, stop, and monitor resources, given a set of resource parameters. These provide a uniform interface between Pacemaker and the managed services."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Fence agents:</emphasis> These are scripts that execute node fencing actions, given a target and fence device parameters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster membership layer:</emphasis> This component provides reliable messaging, membership, and quorum information about the cluster. Currently, Pacemaker supports <ulink url=\"http://www.corosync.org/\">Corosync</ulink> as this layer."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster resource manager:</emphasis> Pacemaker provides the brain that processes and reacts to events that occur in the cluster. These events may include nodes joining or leaving the cluster; resource events caused by failures, maintenance, or scheduled activities; and other administrative actions. To achieve the desired availability, Pacemaker may start and stop resources and fence nodes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster tools:</emphasis> These provide an interface for users to interact with the cluster. Various command-line and graphical (GUI) interfaces are available."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most managed services are not, themselves, cluster-aware. However, many popular open-source cluster filesystems make use of a common <emphasis>Distributed Lock Manager</emphasis> (DLM), which makes direct use of Corosync for its messaging and membership capabilities and Pacemaker for the ability to fence nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example Cluster Stack"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Pacemaker Architecture"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the highest level, the cluster is made up of three pieces:"
+msgid "Pacemaker itself is composed of multiple daemons that work together:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">Non-cluster-aware components</emphasis>. These pieces include the resources themselves; scripts that start, stop and monitor them; and a local daemon that masks the differences between the different standards these scripts implement. Even though interactions of these resources when run as multiple instances can resemble a distributed system, they still lack the proper HA mechanisms and/or autonomous cluster-wide governance as subsumed in the following item."
+msgid "pacemakerd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">Resource management</emphasis>. Pacemaker provides the brain that processes and reacts to events regarding the cluster. These events include nodes joining or leaving the cluster; resource events caused by failures, maintenance and scheduled activities; and other administrative actions. Pacemaker will compute the ideal state of the cluster and plot a path to achieve it after any of these events. This may include moving resources, stopping nodes and even forcing them offline with remote power switches."
+msgid "pacemaker-attrd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">Low-level infrastructure</emphasis>. Projects like <emphasis>Corosync</emphasis>, <emphasis>CMAN</emphasis> and <emphasis>Heartbeat</emphasis> provide reliable messaging, membership and quorum information about the cluster."
+msgid "pacemaker-based"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems.<footnote><para> Even though Pacemaker also supports Heartbeat, the filesystems need to use the stack for messaging and membership, and Corosync seems to be what they’re standardizing on. Technically, it would be possible for them to support Heartbeat as well, but there seems little interest in this. </para></footnote>"
+msgid "pacemaker-controld"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Due to past standardization within the cluster filesystem community, cluster filesystems make use of a common <emphasis>distributed lock manager</emphasis>, which makes use of Corosync for its messaging and membership capabilities (which nodes are up/down) and Pacemaker for fencing services."
+msgid "pacemaker-execd"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "The Pacemaker Stack"
+msgid "pacemaker-fenced"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-schedulerd"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Internal Components"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker itself is composed of five key components:"
+msgid "The Pacemaker master process (pacemakerd) spawns all the other daemons, and respawns them if they unexpectedly exit."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Cluster Information Base</emphasis> (<emphasis>CIB</emphasis>)"
+msgid "The <emphasis>Cluster Information Base</emphasis> (CIB) is an <ulink url=\"https://en.wikipedia.org/wiki/XML\">XML</ulink> representation of the cluster’s configuration and the state of all nodes and resources. The <emphasis>CIB manager</emphasis> (pacemaker-based) keeps the CIB synchronized across the cluster, and handles requests to modify it."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Cluster Resource Management daemon</emphasis> (<emphasis>CRMd</emphasis>)"
+msgid "The attribute manager (pacemaker-attrd) maintains a database of attributes for all nodes, keeps it synchronized across the cluster, and handles requests to modify them. These attributes are usually recorded in the CIB."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Local Resource Management daemon</emphasis> (<emphasis>LRMd</emphasis>)"
+msgid "Given a snapshot of the CIB as input, the <emphasis>scheduler</emphasis> (pacemaker-schedulerd) determines what actions are necessary to achieve the desired state of the cluster."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Policy Engine</emphasis> (<emphasis>PEngine</emphasis> or <emphasis>PE</emphasis>)"
+msgid "The <emphasis>local executor</emphasis> (pacemaker-execd) handles requests to execute resource agents on the local cluster node, and returns the result."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Fencing daemon (<emphasis>STONITHd</emphasis>)"
+msgid "The <emphasis>fencer</emphasis> (pacemaker-fenced) handles requests to fence nodes. Given a target node, the fencer decides which cluster node(s) should execute which fencing device(s), and calls the necessary fencing agents (either directly, or via requests to the fencer peers on other nodes), and returns the result."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CIB uses XML to represent both the cluster’s configuration and current state of all resources in the cluster. The contents of the CIB are automatically kept in sync across the entire cluster and are used by the PEngine to compute the ideal state of the cluster and how it should be achieved."
+msgid "The <emphasis>controller</emphasis> (pacemaker-controld) is Pacemaker’s coordinator, maintaining a consistent view of the cluster membership and orchestrating all the other components."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This list of instructions is then fed to the <emphasis>Designated Controller</emphasis> (<emphasis>DC</emphasis>). Pacemaker centralizes all cluster decision making by electing one of the CRMd instances to act as a master. Should the elected CRMd process (or the node it is on) fail, a new one is quickly established."
+msgid "Pacemaker centralizes cluster decision-making by electing one of the controller instances as the <emphasis>Designated Controller</emphasis> (<emphasis>DC</emphasis>). Should the elected DC process (or the node it is on) fail, a new one is quickly established. The DC responds to cluster events by taking a current snapshot of the CIB, feeding it to the scheduler, then asking the executors (either directly on the local node, or via requests to controller peers on other nodes) and the fencer to execute any necessary actions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Old daemon names"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The DC carries out the PEngine’s instructions in the required order by passing them to either the Local Resource Management daemon (LRMd) or CRMd peers on other nodes via the cluster messaging infrastructure (which in turn passes them on to their LRMd process)."
+msgid "The Pacemaker daemons were renamed in version 2.0. You may still find references to the old names, especially in documentation targeted to version 1.1."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Old name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "New name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The peer nodes all report the results of their operations back to the DC and, based on the expected and actual results, will either execute any actions that needed to wait for the previous one to complete, or abort processing and ask the PEngine to recalculate the ideal cluster state based on the unexpected results."
+msgid "attrd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In some cases, it may be necessary to power off nodes in order to protect shared data or complete resource recovery. For this, Pacemaker comes with STONITHd."
+msgid "cib"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">STONITH</emphasis> is an acronym for <emphasis>Shoot-The-Other-Node-In-The-Head</emphasis>, a recommended practice that misbehaving node is best to be promptly <emphasis>fenced</emphasis> (shut off, cut from shared resources or otherwise immobilized), and is usually implemented with a remote power switch."
+msgid "crmd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In Pacemaker, STONITH devices are modeled as resources (and configured in the CIB) to enable them to be easily monitored for failure, however STONITHd takes care of understanding the STONITH topology such that its clients simply request a node be fenced, and it does the rest."
+msgid "lrmd"
msgstr ""
-#. Tag: title
+#. Tag: para
+#, no-c-format
+msgid "stonithd"
+msgstr ""
+
+#. Tag: para
#, no-c-format
-msgid "Types of Pacemaker Clusters"
+msgid "pacemaker_remoted"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker makes no assumptions about your environment. This allows it to support practically any <ulink url=\"http://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations\">redundancy configuration</ulink> including <emphasis>Active/Active</emphasis>, <emphasis>Active/Passive</emphasis>, <emphasis>N+1</emphasis>, <emphasis>N+M</emphasis>, <emphasis>N-to-1</emphasis> and <emphasis>N-to-N</emphasis>."
+msgid "pacemaker-remoted"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Active/Passive Redundancy"
+msgid "Node Redundancy Designs"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker supports practically any <ulink url=\"https://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations\">node redundancy configuration</ulink> including <emphasis>Active/Active</emphasis>, <emphasis>Active/Passive</emphasis>, <emphasis>N+1</emphasis>, <emphasis>N+M</emphasis>, <emphasis>N-to-1</emphasis> and <emphasis>N-to-N</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Two-node Active/Passive clusters using Pacemaker and <emphasis>DRBD</emphasis> are a cost-effective solution for many High Availability situations."
+msgid "Active/passive clusters with two (or more) nodes using Pacemaker and <ulink url=\"https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device:\">DRBD</ulink> are a cost-effective high-availability solution for many situations. One of the nodes provides the desired services, and if it fails, the other node takes over."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Shared Failover"
+msgid "Active/Passive Redundancy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "By supporting many nodes, Pacemaker can dramatically reduce hardware costs by allowing several active/passive clusters to be combined and share a common backup node."
+msgid "Pacemaker also supports multiple nodes in a shared-failover design, reducing hardware costs by allowing several active/passive clusters to be combined and share a common backup node."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "N to N Redundancy"
+msgid "Shared Failover"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When shared storage is available, every node can potentially be used for failover. Pacemaker can even run multiple copies of services to spread out the workload."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "N to N Redundancy"
+msgstr ""
+
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot b/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot
index 74c1e91548..f3544c316a 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot
@@ -1,695 +1,657 @@
#
# 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"
+"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 "Replicate Storage Using DRBD"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Even if you’re serving up static websites, having to manually synchronize the contents of that website to all the machines in the cluster is not ideal. For dynamic websites, such as a wiki, it’s not even an option. Not everyone care afford network-attached storage, but somehow the data needs to be kept in sync."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Enter DRBD, which can be thought of as network-based RAID-1. <footnote><para>See <ulink url=\"http://www.drbd.org/\">http://www.drbd.org/</ulink> for details.</para></footnote>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Install the DRBD Packages"
msgstr ""
#. Tag: para
#, no-c-format
msgid "DRBD itself is included in the upstream kernel,<footnote><para>Since version 2.6.33</para></footnote> but we do need some utilities to use it effectively."
msgstr ""
#. Tag: para
#, no-c-format
msgid "CentOS does not ship these utilities, so we need to enable a third-party repository to get them. Supported packages for many OSes are available from DRBD’s maker <ulink url=\"http://www.linbit.com/\">LINBIT</ulink>, but here we’ll use the free <ulink url=\"http://elrepo.org/\">ELRepo</ulink> repository."
msgstr ""
#. Tag: para
#, no-c-format
msgid "On both nodes, import the ELRepo package signing key, and enable the repository:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org\n"
-"# rpm -Uvh http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm"
+"# rpm -Uvh http://www.elrepo.org/elrepo-release-7.0-3.el7.elrepo.noarch.rpm"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, we can install the DRBD kernel module and utilities:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y kmod-drbd84 drbd84-utils"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "The version of drbd84-utils shipped with CentOS 7.1 has a bug in the Pacemaker integration script. Until a fix is packaged, download the affected script directly from the upstream, on both nodes:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# curl -o /usr/lib/ocf/resource.d/linbit/drbd 'http://git.linbit.com/gitweb.cgi?p=drbd-utils.git;a=blob_plain;f=scripts/drbd.ocf;h=cf6b966341377a993d1bf5f585a5b9fe72eaa5f2;hb=c11ba026bbbbc647b8112543df142f2185cb4b4b'"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This is a temporary fix that will be overwritten if the package is upgraded."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "DRBD will not be able to run under the default SELinux security policies. If you are familiar with SELinux, you can modify the policies in a more fine-grained manner, but here we will simply exempt DRBD processes from SELinux control:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# semanage permissive -a drbd_t"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We will configure DRBD to use port 7789, so allow that port from each host to the other:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# firewall-cmd --permanent --add-rich-rule='rule family=\"ipv4\" source address=\"192.168.122.102\" port port=\"7789\" protocol=\"tcp\" accept'\n"
"success\n"
"[root@pcmk-1 ~]# firewall-cmd --reload\n"
"success"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-2 ~]# firewall-cmd --permanent --add-rich-rule='rule family=\"ipv4\" source address=\"192.168.122.101\" port port=\"7789\" protocol=\"tcp\" accept'\n"
"success\n"
"[root@pcmk-2 ~]# firewall-cmd --reload\n"
"success"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In this example, we have only two nodes, and all network traffic is on the same LAN. In production, it is recommended to use a dedicated, isolated network for cluster-related traffic, so the firewall configuration would likely be different; one approach would be to add the dedicated network interfaces to the trusted zone."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Allocate a Disk Volume for DRBD"
msgstr ""
#. Tag: para
#, no-c-format
msgid "DRBD will need its own block device on each node. This can be a physical disk partition or logical volume, of whatever size you need for your data. For this document, we will use a 1GiB logical volume, which is more than sufficient for a single HTML file and (later) GFS2 metadata."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# vgdisplay | grep -e Name -e Free\n"
" VG Name centos_pcmk-1\n"
" Free PE / Size 382 / 1.49 GiB\n"
"[root@pcmk-1 ~]# lvcreate --name drbd-demo --size 1G centos_pcmk-1\n"
"Logical volume \"drbd-demo\" created\n"
"[root@pcmk-1 ~]# lvs\n"
" LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n"
" drbd-demo centos_pcmk-1 -wi-a----- 1.00g\n"
" root centos_pcmk-1 -wi-ao---- 5.00g\n"
" swap centos_pcmk-1 -wi-ao---- 1.00g"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Repeat for the second node, making sure to use the same size:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ssh pcmk-2 -- lvcreate --name drbd-demo --size 1G centos_pcmk-2\n"
"Logical volume \"drbd-demo\" created"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure DRBD"
msgstr ""
#. Tag: para
#, no-c-format
msgid "There is no series of commands for building a DRBD configuration, so simply run this on both nodes to use this sample configuration:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cat &lt;&lt;END &gt;/etc/drbd.d/wwwdata.res\n"
"resource wwwdata {\n"
" protocol C;\n"
" meta-disk internal;\n"
" device /dev/drbd1;\n"
" syncer {\n"
" verify-alg sha1;\n"
" }\n"
" net {\n"
" allow-two-primaries;\n"
" }\n"
" on pcmk-1 {\n"
" disk /dev/centos_pcmk-1/drbd-demo;\n"
" address 192.168.122.101:7789;\n"
" }\n"
" on pcmk-2 {\n"
" disk /dev/centos_pcmk-2/drbd-demo;\n"
" address 192.168.122.102:7789;\n"
" }\n"
"}\n"
"END"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Edit the file to use the hostnames, IP addresses and logical volume paths of your nodes if they differ from the ones used in this guide."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Detailed information on the directives used in this configuration (and other alternatives) is available at <ulink url=\"http://www.drbd.org/users-guide/ch-configure.html\">http://www.drbd.org/users-guide/ch-configure.html</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <emphasis role=\"strong\">allow-two-primaries</emphasis> option would not normally be used in an active/passive cluster. We are adding it here for the convenience of changing to an active/active cluster later."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Initialize DRBD"
msgstr ""
#. Tag: para
#, no-c-format
msgid "With the configuration in place, we can now get DRBD running."
msgstr ""
#. Tag: para
#, no-c-format
msgid "These commands create the local metadata for the DRBD resource, ensure the DRBD kernel module is loaded, and bring up the DRBD resource. Run them on one node:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# drbdadm create-md wwwdata\n"
"initializing activity log\n"
"NOT initializing bitmap\n"
"Writing meta data...\n"
"New drbd meta data block successfully created.\n"
"[root@pcmk-1 ~]# modprobe drbd\n"
"[root@pcmk-1 ~]# drbdadm up wwwdata"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We can confirm DRBD’s status on this node:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# cat /proc/drbd\n"
"version: 8.4.6 (api:1/proto:86-101)\n"
"GIT-hash: 833d830e0152d1e457fa7856e71e11248ccf3f70 build by phil@Build64R7, 2015-04-10 05:13:52\n"
"\n"
" 1: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown C r----s\n"
" ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:1048508"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Because we have not yet initialized the data, this node’s data is marked as <emphasis role=\"strong\">Inconsistent</emphasis>. Because we have not yet initialized the second node, the local state is <emphasis role=\"strong\">WFConnection</emphasis> (waiting for connection), and the partner node’s status is marked as <emphasis role=\"strong\">Unknown</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, repeat the above commands on the second node. This time, when we check the status, it shows:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-2 ~]# cat /proc/drbd\n"
"version: 8.4.6 (api:1/proto:86-101)\n"
"GIT-hash: 833d830e0152d1e457fa7856e71e11248ccf3f70 build by phil@Build64R7, 2015-04-10 05:13:52\n"
"\n"
" 1: cs:Connected ro:Secondary/Secondary ds:Inconsistent/Inconsistent C r-----\n"
" ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:1048508"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can see the state has changed to <emphasis role=\"strong\">Connected</emphasis>, meaning the two DRBD nodes are communicating properly, and both nodes are in <emphasis role=\"strong\">Secondary</emphasis> role with <emphasis role=\"strong\">Inconsistent</emphasis> data."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To make the data consistent, we need to tell DRBD which node should be considered to have the correct data. In this case, since we are creating a new resource, both have garbage, so we’ll just pick pcmk-1 and run this command on it:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# drbdadm primary --force wwwdata"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you are using an older version of DRBD, the required syntax may be different. See the documentation for your version for how to perform these commands."
+msgid "If you are using a different version of DRBD, the required syntax may be different. See the documentation for your version for how to perform these commands."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If we check the status immediately, we’ll see something like this:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# cat /proc/drbd\n"
"version: 8.4.6 (api:1/proto:86-101)\n"
"GIT-hash: 833d830e0152d1e457fa7856e71e11248ccf3f70 build by phil@Build64R7, 2015-04-10 05:13:52\n"
"\n"
" 1: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r-----\n"
" ns:2872 nr:0 dw:0 dr:3784 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:1045636\n"
" [&gt;....................] sync'ed: 0.4% (1045636/1048508)K\n"
" finish: 0:10:53 speed: 1,436 (1,436) K/sec"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We can see that this node has the <emphasis role=\"strong\">Primary</emphasis> role, the partner node has the <emphasis role=\"strong\">Secondary</emphasis> role, this node’s data is now considered <emphasis role=\"strong\">UpToDate</emphasis>, the partner node’s data is still <emphasis role=\"strong\">Inconsistent</emphasis>, and a progress bar shows how far along the partner node is in synchronizing the data."
msgstr ""
#. Tag: para
#, no-c-format
msgid "After a while, the sync should finish, and you’ll see something like:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# cat /proc/drbd\n"
"version: 8.4.6 (api:1/proto:86-101)\n"
"GIT-hash: 833d830e0152d1e457fa7856e71e11248ccf3f70 build by phil@Build64R7, 2015-04-10 05:13:52\n"
"\n"
" 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----\n"
" ns:1048508 nr:0 dw:0 dr:1049420 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Both sets of data are now <emphasis role=\"strong\">UpToDate</emphasis>, and we can proceed to creating and populating a filesystem for our WebSite resource’s documents."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Populate the DRBD Disk"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On the node with the primary role (pcmk-1 in this example), create a filesystem on the DRBD device:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# mkfs.xfs /dev/drbd1\n"
"meta-data=/dev/drbd1 isize=256 agcount=4, agsize=65532 blks\n"
" = sectsz=512 attr=2, projid32bit=1\n"
" = crc=0 finobt=0\n"
"data = bsize=4096 blocks=262127, imaxpct=25\n"
" = sunit=0 swidth=0 blks\n"
"naming =version 2 bsize=4096 ascii-ci=0 ftype=0\n"
"log =internal log bsize=4096 blocks=853, version=2\n"
" = sectsz=512 sunit=0 blks, lazy-count=1\n"
"realtime =none extsz=4096 blocks=0, rtextents=0"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In this example, we create an xfs filesystem with no special options. In a production environment, you should choose a filesystem type and options that are suitable for your application."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Mount the newly created filesystem, populate it with our web document, give it the same SELinux policy as the web document root, then unmount it (the cluster will handle mounting and unmounting it later):"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# mount /dev/drbd1 /mnt\n"
"[root@pcmk-1 ~]# cat &lt;&lt;-END &gt;/mnt/index.html\n"
" &lt;html&gt;\n"
" &lt;body&gt;My Test Site - DRBD&lt;/body&gt;\n"
" &lt;/html&gt;\n"
"END\n"
"[root@pcmk-1 ~]# chcon -R --reference=/var/www/html /mnt\n"
"[root@pcmk-1 ~]# umount /dev/drbd1"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the Cluster for the DRBD device"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "One handy feature <literal>pcs</literal> has is the ability to queue up several changes into a file and commit those changes atomically. To do this, start by populating the file with the current raw XML config from the CIB."
+msgid "One handy feature <literal>pcs</literal> has is the ability to queue up several changes into a file and commit those changes all at once. To do this, start by populating the file with the current raw XML config from the CIB."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib drbd_cfg"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Using the <literal>pcs -f</literal> option, make changes to the configuration saved in the <literal>drbd_cfg</literal> file. These changes will not be seen by the cluster until the <literal>drbd_cfg</literal> file is pushed into the live cluster’s CIB later."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Here, we create a cluster resource for the DRBD device, and an additional <emphasis>clone</emphasis> resource to allow the resource to run on both nodes at the same time."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f drbd_cfg resource create WebData ocf:linbit:drbd \\\n"
" drbd_resource=wwwdata op monitor interval=60s\n"
"[root@pcmk-1 ~]# pcs -f drbd_cfg resource master WebDataClone WebData \\\n"
" master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 \\\n"
" notify=true\n"
"[root@pcmk-1 ~]# pcs -f drbd_cfg resource show\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started\n"
" WebSite (ocf::heartbeat:apache): Started\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Stopped: [ pcmk-1 pcmk-2 ]"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After you are satisfied with all the changes, you can commit them all at once by pushing the drbd_cfg file into the live CIB."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib-push drbd_cfg\n"
"CIB updated"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Early versions of <literal>pcs</literal> required <literal>push cib</literal> in place of <literal>cib-push</literal> above."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "Let’s see what the cluster did with the new configuration:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 14 09:29:41 2015\n"
-"Last change: Fri Aug 14 09:29:25 2015\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"4 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 09:29:41 2018\n"
+"Last change: Fri Jan 12 09:29:25 2018\n"
"\n"
+"2 nodes configured\n"
+"4 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-1\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 ]\n"
" Slaves: [ pcmk-2 ]\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We can see that <emphasis role=\"strong\">WebDataClone</emphasis> (our DRBD device) is running as master (DRBD’s primary role) on <emphasis role=\"strong\">pcmk-1</emphasis> and slave (DRBD’s secondary role) on <emphasis role=\"strong\">pcmk-2</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource agent should load the DRBD module when needed if it’s not already loaded. If that does not happen, configure your operating system to load the module at boot time. For &DISTRO; &DISTRO_VERSION;, you would run this on both nodes:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# echo drbd &gt;/etc/modules-load.d/drbd.conf"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the Cluster for the Filesystem"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that we have a working DRBD device, we need to mount its filesystem."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In addition to defining the filesystem, we also need to tell the cluster where it can be located (only on the DRBD Primary) and when it is allowed to start (after the Primary was promoted)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "We are going to take a shortcut when creating the resource this time. Instead of explicitly saying we want the <emphasis role=\"strong\">ocf:heartbeat:Filesystem</emphasis> script, we are only going to ask for <emphasis role=\"strong\">Filesystem</emphasis>. We can do this because we know there is only one resource script named <emphasis role=\"strong\">Filesystem</emphasis> available to pacemaker, and that pcs is smart enough to fill in the <emphasis role=\"strong\">ocf:heartbeat:</emphasis> portion for us correctly in the configuration. If there were multiple <emphasis role=\"strong\">Filesystem</emphasis> scripts from different OCF providers, we would need to specify the exact one we wanted."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once again, we will queue our changes to a file and then push the new configuration to the cluster as the final step."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib fs_cfg\n"
"[root@pcmk-1 ~]# pcs -f fs_cfg resource create WebFS Filesystem \\\n"
" device=\"/dev/drbd1\" directory=\"/var/www/html\" fstype=\"xfs\"\n"
"[root@pcmk-1 ~]# pcs -f fs_cfg constraint colocation add WebFS with WebDataClone INFINITY with-rsc-role=Master\n"
"[root@pcmk-1 ~]# pcs -f fs_cfg constraint order promote WebDataClone then start WebFS\n"
"Adding WebDataClone WebFS (kind: Mandatory) (Options: first-action=promote then-action=start)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We also need to tell the cluster that Apache needs to run on the same machine as the filesystem and that it must be active before Apache can start."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f fs_cfg constraint colocation add WebSite with WebFS INFINITY\n"
"[root@pcmk-1 ~]# pcs -f fs_cfg constraint order WebFS then WebSite\n"
"Adding WebFS WebSite (kind: Mandatory) (Options: first-action=start then-action=start)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Review the updated configuration."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f fs_cfg constraint\n"
"Location Constraints:\n"
"Ordering Constraints:\n"
" start ClusterIP then start WebSite (kind:Mandatory)\n"
" promote WebDataClone then start WebFS (kind:Mandatory)\n"
" start WebFS then start WebSite (kind:Mandatory)\n"
"Colocation Constraints:\n"
" WebSite with ClusterIP (score:INFINITY)\n"
" WebFS with WebDataClone (score:INFINITY) (with-rsc-role:Master)\n"
-" WebSite with WebFS (score:INFINITY)"
+" WebSite with WebFS (score:INFINITY)\n"
+"Ticket Constraints:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f fs_cfg resource show\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started\n"
" WebSite (ocf::heartbeat:apache): Started\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 ]\n"
" Slaves: [ pcmk-2 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Stopped"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After reviewing the new configuration, upload it and watch the cluster put it into effect."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster cib-push fs_cfg\n"
"[root@pcmk-1 ~]# pcs status\n"
-"Last updated: Fri Aug 14 09:34:11 2015\n"
-"Last change: Fri Aug 14 09:34:09 2015\n"
+"Cluster name: mycluster\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"5 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 09:34:11 2018\n"
+"Last change: Fri Jan 12 09:34:09 2018\n"
"\n"
+"2 nodes configured\n"
+"5 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-1\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-1 ]\n"
" Slaves: [ pcmk-2 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Started pcmk-1\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Test Cluster Failover"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Previously, we used <literal>pcs cluster stop pcmk-1</literal> to stop all cluster services on <emphasis role=\"strong\">pcmk-1</emphasis>, failing over the cluster resources, but there is another way to safely simulate node failure."
msgstr ""
#. Tag: para
#, no-c-format
msgid "We can put the node into <emphasis>standby mode</emphasis>. Nodes in this state continue to run corosync and pacemaker but are not allowed to run resources. Any resources found active there will be moved elsewhere. This feature can be particularly useful when performing system administration tasks such as updating packages used by cluster resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Put the active node into standby mode, and observe the cluster move all the resources to the other node. The node’s status will change to indicate that it can no longer host resources."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster standby pcmk-1\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 14 09:36:49 2015\n"
-"Last change: Fri Aug 14 09:36:43 2015\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"5 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 09:36:49 2018\n"
+"Last change: Fri Jan 12 09:36:43 2018\n"
"\n"
+"2 nodes configured\n"
+"5 resources configured\n"
"\n"
"Node pcmk-1 (1): standby\n"
"Online: [ pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-2\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-2 ]\n"
" Stopped: [ pcmk-1 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once we’ve done everything we needed to on pcmk-1 (in this case nothing, we just wanted to see the resources move), we can allow the node to be a full cluster member again."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster unstandby pcmk-1\n"
"[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 14 09:38:02 2015\n"
-"Last change: Fri Aug 14 09:37:56 2015\n"
"Stack: corosync\n"
-"Current DC: pcmk-1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"5 Resources configured\n"
+"Current DC: pcmk-1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 09:38:02 2018\n"
+"Last change: Fri Jan 12 09:37:56 2018\n"
"\n"
+"2 nodes configured\n"
+"5 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2\n"
" WebSite (ocf::heartbeat:apache): Started pcmk-2\n"
" Master/Slave Set: WebDataClone [WebData]\n"
" Masters: [ pcmk-2 ]\n"
" Slaves: [ pcmk-1 ]\n"
" WebFS (ocf::heartbeat:Filesystem): Started pcmk-2\n"
"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Notice that <emphasis role=\"strong\">pcmk-1</emphasis> is back to the <emphasis role=\"strong\">Online</emphasis> state, and that the cluster resources stay where they are due to our resource stickiness settings configured earlier."
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot b/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot
index 4c7908f3aa..e469600f44 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot
@@ -1,252 +1,264 @@
#
# 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"
+"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 "Configure STONITH"
msgstr ""
#. Tag: title
#, no-c-format
msgid "What is STONITH?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "STONITH (Shoot The Other Node In The Head aka. fencing) protects your data from being corrupted by rogue nodes or unintended concurrent access."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Just because a node is unresponsive doesn’t mean it has stopped accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH to ensure that the node is truly offline before allowing the data to be accessed from another node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Choose a STONITH Device"
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is crucial that your STONITH device can allow the cluster to differentiate between a node failure and a network failure."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A common mistake people make when choosing a STONITH device is to use a remote power switch (such as many on-board IPMI controllers) that shares power with the node it controls. If the power fails in such a case, the cluster cannot be sure whether the node is really offline, or active and suffering from a network fault, so the cluster will stop all resources to avoid a possible split-brain situation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Likewise, any device that relies on the machine being active (such as SSH-based \"devices\" sometimes used during testing) is inappropriate."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the Cluster for STONITH"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Install the STONITH agent(s). To see what packages are available, run <literal>yum search fence-</literal>. Be sure to install the package(s) on all cluster nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Configure the STONITH device itself to be able to fence your nodes and accept fencing requests. This includes any necessary configuration on the device and on the nodes, and any firewall or SELinux changes needed. Test the communication between the device and your nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Find the correct STONITH agent script: <literal>pcs stonith list</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Find the parameters associated with the device: <literal>pcs stonith describe <replaceable>agent_name</replaceable></literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a local copy of the CIB: <literal>pcs cluster cib stonith_cfg</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create the fencing resource: <literal>pcs -f stonith_cfg stonith create <replaceable>stonith_id stonith_device_type [stonith_device_options]</replaceable></literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any flags that do not take arguments, such as <literal>--ssl</literal>, should be passed as <literal>ssl=1</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Enable STONITH in the cluster: <literal>pcs -f stonith_cfg property set stonith-enabled=true</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special <emphasis role=\"strong\">pcmk_host_map</emphasis> parameter. See <literal>man stonithd</literal> for details."
+msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special <emphasis role=\"strong\">pcmk_host_map</emphasis> parameter. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the device does not support the <emphasis role=\"strong\">list</emphasis> command, you may also need to set the special <emphasis role=\"strong\">pcmk_host_list</emphasis> and/or <emphasis role=\"strong\">pcmk_host_check</emphasis> parameters. See <literal>man stonithd</literal> for details."
+msgid "If the device does not support the <emphasis role=\"strong\">list</emphasis> command, you may also need to set the special <emphasis role=\"strong\">pcmk_host_list</emphasis> and/or <emphasis role=\"strong\">pcmk_host_check</emphasis> parameters. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the device does not expect the victim to be specified with the <emphasis role=\"strong\">port</emphasis> parameter, you may also need to set the special <emphasis role=\"strong\">pcmk_host_argument</emphasis> parameter. See <literal>man stonithd</literal> for details."
+msgid "If the device does not expect the victim to be specified with the <emphasis role=\"strong\">port</emphasis> parameter, you may also need to set the special <emphasis role=\"strong\">pcmk_host_argument</emphasis> parameter. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Commit the new configuration: <literal>pcs cluster cib-push stonith_cfg</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once the STONITH resource is running, test it (you might want to stop the cluster on that machine first): <literal>stonith_admin --reboot <replaceable>nodename</replaceable></literal>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For this example, assume we have a chassis containing four nodes and an IPMI device active on 10.0.0.1. Following the steps above would go something like this:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 1: Install the <emphasis role=\"strong\">fence-agents-ipmilan</emphasis> package on both nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 2: Configure the IP address, authentication credentials, etc. in the IPMI device itself."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 3: Choose the <emphasis role=\"strong\">fence_ipmilan</emphasis> STONITH agent."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 4: Obtain the agent’s possible parameters:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs stonith describe fence_ipmilan\n"
-"Stonith options for: fence_ipmilan\n"
+"fence_ipmilan - Fence agent for IPMI\n"
+"\n"
+"fence_ipmilan is an I/O Fencing agentwhich can be used with machines controlled by IPMI.This agent calls support software ipmitool (http://ipmitool.sf.net/). WARNING! This fence agent might report success before the node is powered off. You should use -m/method onoff if your fence device works correctly with that option.\n"
+"\n"
+"Stonith options:\n"
" ipport: TCP/UDP port to use for connection with device\n"
+" port: IP address or hostname of fencing device (together with --port-as-ip)\n"
" inet6_only: Forces agent to use IPv6 addresses only\n"
-" ipaddr (required): IP Address or Hostname\n"
+" ipaddr: IP Address or Hostname\n"
" passwd_script: Script to retrieve password\n"
" method: Method to fence (onoff|cycle)\n"
" inet4_only: Forces agent to use IPv4 addresses only\n"
" passwd: Login password or passphrase\n"
" lanplus: Use Lanplus to improve security of connection\n"
" auth: IPMI Lan Auth type.\n"
+" action: Fencing Action WARNING: specifying 'action' is deprecated and not necessary with current Pacemaker versions.\n"
" cipher: Ciphersuite to use (same as ipmitool -C parameter)\n"
+" target: Bridge IPMI requests to the remote target address\n"
" privlvl: Privilege level on IPMI device\n"
-" action (required): Fencing Action\n"
+" timeout: Timeout (sec) for IPMI operation\n"
" login: Login Name\n"
-" verbose: Verbose mode\n"
-" debug: Write debug information to given file\n"
-" version: Display version information and exit\n"
-" help: Display help and exit\n"
" power_wait: Wait X seconds after issuing ON/OFF\n"
" login_timeout: Wait X seconds for cmd prompt after login\n"
-" power_timeout: Test X seconds for status change after ON/OFF\n"
" delay: Wait X seconds before fencing is started\n"
+" power_timeout: Test X seconds for status change after ON/OFF\n"
" ipmitool_path: Path to ipmitool binary\n"
" shell_timeout: Wait X seconds for cmd prompt after issuing command\n"
+" port_as_ip: Make \"port/plug\" to be an alias to IP address\n"
" retry_on: Count of attempts to retry power on\n"
" sudo: Use sudo (without password) when calling 3rd party sotfware.\n"
-" stonith-timeout: How long to wait for the STONITH action (reboot, on, off) to complete per a stonith device.\n"
" priority: The priority of the stonith resource. Devices are tried in order of highest priority to lowest.\n"
-" pcmk_host_map: A mapping of host names to ports numbers for devices that do not support host names.\n"
+" pcmk_host_map: A mapping of host names to ports numbers for devices that do not support host names. Eg. node1:1;node2:2,3 would tell the cluster to use port 1 for node1 and ports\n"
+" 2 and 3 for node2\n"
" pcmk_host_list: A list of machines controlled by this device (Optional unless pcmk_host_check=static-list).\n"
-" pcmk_host_check: How to determine which machines are controlled by the device."
+" pcmk_host_check: How to determine which machines are controlled by the device. Allowed values: dynamic-list (query the device), static-list (check the pcmk_host_list attribute),\n"
+" none (assume every device can fence every machine)\n"
+" pcmk_delay_max: Enable random delay for stonith actions and specify the maximum of random delay This prevents double fencing when using slow devices such as sbd. Use this to\n"
+" enable random delay for stonith actions and specify the maximum of random delay.\n"
+" pcmk_action_limit: The maximum number of actions can be performed in parallel on this device Cluster property concurrent-fencing=true needs to be configured first. Then use this\n"
+" to specify the maximum number of actions can be performed in parallel on this device. -1 is unlimited.\n"
+"\n"
+"Default operations:\n"
+" monitor: interval=60s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 5: <literal>pcs cluster cib stonith_cfg</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 6: Here are example parameters for creating our STONITH resource:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f stonith_cfg stonith create ipmi-fencing fence_ipmilan \\\n"
" pcmk_host_list=\"pcmk-1 pcmk-2\" ipaddr=10.0.0.1 login=testuser \\\n"
" passwd=acd123 op monitor interval=60s\n"
"[root@pcmk-1 ~]# pcs -f stonith_cfg stonith\n"
" ipmi-fencing (stonith:fence_ipmilan): Stopped"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Steps 7-10: Enable STONITH in the cluster:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs -f stonith_cfg property set stonith-enabled=true\n"
"[root@pcmk-1 ~]# pcs -f stonith_cfg property\n"
"Cluster Properties:\n"
" cluster-infrastructure: corosync\n"
" cluster-name: mycluster\n"
-" dc-version: 1.1.12-a14efad\n"
+" dc-version: 1.1.16-12.el7_4.5-94ff4df\n"
" have-watchdog: false\n"
" stonith-enabled: true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 11: <literal>pcs cluster cib-push stonith_cfg</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Step 12: Test:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster stop pcmk-2\n"
"[root@pcmk-1 ~]# stonith_admin --reboot pcmk-2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After a successful test, login to any rebooted nodes, and start the cluster (with <literal>pcs cluster start</literal>)."
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Tools.pot b/doc/Clusters_from_Scratch/pot/Ch-Tools.pot
index c9fa2842f7..9ec41c98ce 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Tools.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Tools.pot
@@ -1,144 +1,163 @@
#
# 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"
+"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 "Pacemaker Tools"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Simplify administration using a cluster shell"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#, no-c-format
msgid "All of that has been greatly simplified with the creation of unified command-line shells (and GUIs) that hide all the messy XML scaffolding."
msgstr ""
#. Tag: para
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "They even allow you to queue up several changes at once and commit them atomically."
+msgid "They even allow you to queue up several changes at once and commit them all at once."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Two popular command-line shells are <literal>pcs</literal> and <literal>crmsh</literal>. This edition of Clusters from Scratch is based on <literal>pcs</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The two shells share many concepts but the scope, layout and syntax does differ, so make sure you read the version of this guide that corresponds to the software installed on your system."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Explore pcs"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Start by taking some time to familiarize yourself with what <literal>pcs</literal> can do."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs\n"
+"\n"
"Usage: pcs [-f file] [-h] [commands]...\n"
"Control and configure pacemaker and corosync.\n"
"\n"
"Options:\n"
-" -h, --help Display usage and exit\n"
-" -f file Perform actions on file instead of active CIB\n"
-" --debug Print all network traffic and external commands run\n"
-" --version Print pcs version information\n"
+" -h, --help Display usage and exit.\n"
+" -f file Perform actions on file instead of active CIB.\n"
+" --debug Print all network traffic and external commands run.\n"
+" --version Print pcs version information.\n"
+" --request-timeout Timeout for each outgoing request to another node in\n"
+" seconds. Default is 60s.\n"
"\n"
"Commands:\n"
-" cluster Configure cluster options and nodes\n"
-" resource Manage cluster resources\n"
-" stonith Configure fence devices\n"
-" constraint Set resource constraints\n"
-" property Set pacemaker properties\n"
-" acl Set pacemaker access control lists\n"
-" status View cluster status\n"
-" config View and manage cluster configuration"
+" cluster Configure cluster options and nodes.\n"
+" resource Manage cluster resources.\n"
+" stonith Manage fence devices.\n"
+" constraint Manage resource constraints.\n"
+" property Manage pacemaker properties.\n"
+" acl Manage pacemaker access control lists.\n"
+" qdevice Manage quorum device provider on the local host.\n"
+" quorum Manage cluster quorum settings.\n"
+" booth Manage booth (cluster ticket manager).\n"
+" status View cluster status.\n"
+" config View and manage cluster configuration.\n"
+" pcsd Manage pcs daemon.\n"
+" node Manage cluster nodes.\n"
+" alert Manage pacemaker alerts."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "As you can see, the different aspects of cluster management are separated into categories: resource, cluster, stonith, property, constraint, and status. To discover the functionality available in each of these categories, one can issue the command <literal>pcs <replaceable>category</replaceable> help</literal>. Below is an example of all the options available under the status category."
+msgid "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 <literal>pcs <replaceable>category</replaceable> help</literal>. Below is an example of all the options available under the status category."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status help\n"
+"\n"
"Usage: pcs status [commands]...\n"
"View current cluster and resource status\n"
"Commands:\n"
-" [status] [--full]\n"
+" [status] [--full | --hide-inactive]\n"
" View all information about the cluster and resources (--full provides\n"
-" more details)\n"
+" more details, --hide-inactive hides inactive resources).\n"
"\n"
-" resources\n"
-" View current status of cluster resources\n"
+" resources [&lt;resource id&gt; | --full | --groups | --hide-inactive]\n"
+" Show all currently configured resources or if a resource is specified\n"
+" show the options for the configured resource. If --full is specified,\n"
+" all configured resource options will be displayed. If --groups is\n"
+" specified, only show groups (and their resources). If --hide-inactive\n"
+" is specified, only show active resources.\n"
"\n"
" groups\n"
-" View currently configured groups and their resources\n"
+" View currently configured groups and their resources.\n"
"\n"
" cluster\n"
-" View current cluster status\n"
+" View current cluster status.\n"
"\n"
" corosync\n"
-" View current membership information as seen by corosync\n"
+" View current membership information as seen by corosync.\n"
+"\n"
+" quorum\n"
+" View current quorum status.\n"
+"\n"
+" qdevice &lt;device model&gt; [--full] [&lt;cluster name&gt;]\n"
+" Show runtime status of specified model of quorum device provider. Using\n"
+" --full will give more detailed output. If &lt;cluster name&gt; is specified,\n"
+" only information about the specified cluster will be displayed.\n"
"\n"
-" nodes [corosync|both|config]\n"
+" nodes [corosync | both | config]\n"
" View current status of nodes from pacemaker. If 'corosync' is\n"
-" specified, print nodes currently configured in corosync, if 'both'\n"
-" is specified, print nodes from both corosync &amp; pacemaker. If 'config'\n"
-" is specified, print nodes from corosync &amp; pacemaker configuration.\n"
+" specified, view current status of nodes from corosync instead. If\n"
+" 'both' is specified, view current status of nodes from both corosync &amp;\n"
+" pacemaker. If 'config' is specified, print nodes from corosync &amp;\n"
+" pacemaker configuration.\n"
"\n"
-" pcsd &lt;node&gt; ...\n"
-" Show the current status of pcsd on the specified nodes\n"
+" pcsd [&lt;node&gt;]...\n"
+" Show current status of pcsd on nodes specified, or on all nodes\n"
+" configured in the local cluster if no nodes are specified.\n"
"\n"
" xml\n"
-" View xml version of status (output from crm_mon -r -1 -X)"
+" View xml version of status (output from crm_mon -r -1 -X)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Additionally, if you are interested in the version and supported cluster stack(s) available with your Pacemaker installation, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pacemakerd --features\n"
-"Pacemaker 1.1.12 (Build: a14efad)\n"
-" Supporting v3.0.9: generated-manpages agent-manpages ascii-docs publican-docs ncurses libqb-logging libqb-ipc upstart systemd nagios corosync-native atomic-attrd acls"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If the SNMP and/or email options are not listed, then Pacemaker was not built to support them. This may be by the choice of your distribution, or the required libraries may not have been available. Please contact whoever supplied you with the packages for more details."
+"Pacemaker 1.1.16-12.el7_4.5 (Build: 94ff4df)\n"
+" Supporting v3.0.12: generated-manpages agent-manpages ncurses libqb-logging libqb-ipc systemd nagios corosync-native atomic-attrd acls"
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Ch-Verification.pot b/doc/Clusters_from_Scratch/pot/Ch-Verification.pot
index dbfa70e343..e2bf3ea75e 100644
--- a/doc/Clusters_from_Scratch/pot/Ch-Verification.pot
+++ b/doc/Clusters_from_Scratch/pot/Ch-Verification.pot
@@ -1,203 +1,197 @@
#
# 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"
+"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 "Start and Verify Cluster"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Start the Cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that corosync is configured, it is time to start the cluster. The command below will start corosync and pacemaker on both nodes in the cluster. If you are issuing the start command from a different node than the one you ran the <literal>pcs cluster auth</literal> command on earlier, you must authenticate on the current node you are logged into before you will be allowed to start the cluster."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs cluster start --all\n"
"pcmk-1: Starting Cluster...\n"
"pcmk-2: Starting Cluster..."
msgstr ""
#. Tag: para
#, no-c-format
msgid "An alternative to using the <literal>pcs cluster start --all</literal> command is to issue either of the below command sequences on each node in the cluster separately:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster start\n"
"Starting Cluster..."
msgstr ""
#. Tag: para
#, no-c-format
msgid "or"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# systemctl start corosync.service\n"
"# systemctl start pacemaker.service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In this example, we are not enabling the corosync and pacemaker services to start at boot. If a cluster node fails or is rebooted, you will need to run <literal>pcs cluster start <replaceable>nodename</replaceable></literal> (or <literal>--all</literal>) to start the cluster on it. While you could enable the services to start at boot, requiring a manual start of cluster services gives you the opportunity to do a post-mortem investigation of a node failure before returning it to the cluster."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Corosync Installation"
msgstr ""
#. Tag: para
#, no-c-format
msgid "First, use <literal>corosync-cfgtool</literal> to check whether cluster communication is happy:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# corosync-cfgtool -s\n"
"Printing ring status.\n"
"Local node ID 1\n"
"RING ID 0\n"
" id = 192.168.122.101\n"
" status = ring 0 active with no faults"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We can see here that everything appears normal with our fixed IP address (not a 127.0.0.x loopback address) listed as the <emphasis role=\"strong\">id</emphasis>, and <emphasis role=\"strong\">no faults</emphasis> for the status."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you see something different, you might want to start by checking the node’s network, firewall and selinux configurations."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Next, check the membership and quorum APIs:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# corosync-cmapctl | grep members\n"
"runtime.totem.pg.mrp.srp.members.1.config_version (u64) = 0\n"
"runtime.totem.pg.mrp.srp.members.1.ip (str) = r(0) ip(192.168.122.101)\n"
"runtime.totem.pg.mrp.srp.members.1.join_count (u32) = 1\n"
"runtime.totem.pg.mrp.srp.members.1.status (str) = joined\n"
"runtime.totem.pg.mrp.srp.members.2.config_version (u64) = 0\n"
"runtime.totem.pg.mrp.srp.members.2.ip (str) = r(0) ip(192.168.122.102)\n"
"runtime.totem.pg.mrp.srp.members.2.join_count (u32) = 2\n"
"runtime.totem.pg.mrp.srp.members.2.status (str) = joined\n"
"\n"
"[root@pcmk-1 ~]# pcs status corosync\n"
"Membership information\n"
" --------------------------\n"
" Nodeid Votes Name\n"
" 1 1 pcmk-1 (local)\n"
" 2 1 pcmk-2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You should see both nodes have joined the cluster."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Pacemaker Installation"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that we have confirmed that Corosync is functional, we can check the rest of the stack. Pacemaker has already been started, so verify the necessary processes are running:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# ps axf\n"
" PID TTY STAT TIME COMMAND\n"
" 2 ? S 0:00 [kthreadd]\n"
"...lots of processes...\n"
" 1362 ? Ssl 0:35 corosync\n"
" 1379 ? Ss 0:00 /usr/sbin/pacemakerd -f\n"
-" 1380 ? Ss 0:00 \\_ /usr/libexec/pacemaker/cib\n"
-" 1381 ? Ss 0:00 \\_ /usr/libexec/pacemaker/stonithd\n"
-" 1382 ? Ss 0:00 \\_ /usr/libexec/pacemaker/lrmd\n"
-" 1383 ? Ss 0:00 \\_ /usr/libexec/pacemaker/attrd\n"
-" 1384 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pengine\n"
-" 1385 ? Ss 0:00 \\_ /usr/libexec/pacemaker/crmd"
+" 1380 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-based\n"
+" 1381 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-fenced\n"
+" 1382 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-execd\n"
+" 1383 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-attrd\n"
+" 1384 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-schedulerd\n"
+" 1385 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pacemaker-controld"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If that looks OK, check the <literal>pcs status</literal> output:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status\n"
"Cluster name: mycluster\n"
"WARNING: no stonith devices and stonith-enabled is not false\n"
-"Last updated: Tue Dec 16 16:15:29 2014\n"
-"Last change: Tue Dec 16 15:49:47 2014\n"
"Stack: corosync\n"
-"Current DC: pcmk-2 (2) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"0 Resources configured\n"
+"Current DC: pcmk-2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 16:15:29 2018\n"
+"Last change: Fri Jan 12 15:49:47 2018\n"
"\n"
+"2 nodes configured\n"
+"0 resources configured\n"
"\n"
"Online: [ pcmk-1 pcmk-2 ]\n"
"\n"
-"Full list of resources:\n"
-"\n"
-"\n"
-"PCSD Status:\n"
-" pcmk-1: Online\n"
-" pcmk-2: Online\n"
+"No active resources\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Finally, ensure there are no startup errors (aside from messages relating to not having STONITH configured, which are OK at this point):"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# journalctl | grep -i error"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Other operating systems may report startup errors in other locations, for example <literal>/var/log/messages</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Repeat these checks on the other node. The results should be the same."
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Preface.pot b/doc/Clusters_from_Scratch/pot/Preface.pot
index f84c72b747..44e91d0ec7 100644
--- a/doc/Clusters_from_Scratch/pot/Preface.pot
+++ b/doc/Clusters_from_Scratch/pot/Preface.pot
@@ -1,19 +1,19 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Preface"
msgstr ""
diff --git a/doc/Clusters_from_Scratch/pot/Revision_History.pot b/doc/Clusters_from_Scratch/pot/Revision_History.pot
index 7f577ac31b..c413a628cc 100644
--- a/doc/Clusters_from_Scratch/pot/Revision_History.pot
+++ b/doc/Clusters_from_Scratch/pot/Revision_History.pot
@@ -1,109 +1,114 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Revision History"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Andrew"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Beekhof"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Import from Pages.app"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Raoul"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Scarazzini"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Italian translation"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for Fedora 13"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update the GFS2 section to use CMAN"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Generate docbook content from asciidoc sources"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for Fedora 17"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "David"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Vossel"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for pcs"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for Fedora 21"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Minor corrections, plus use include file for intro"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for CentOS 7.1 and leaving firewalld/SELinux enabled"
msgstr ""
+#. Tag: member
+#, no-c-format
+msgid "Update banner for Pacemaker 2.0 and content for CentOS 7.4 with Pacemaker 1.1.16"
+msgstr ""
+
diff --git a/doc/Pacemaker_Development/pot/Author_Group.pot b/doc/Pacemaker_Administration/pot/Author_Group.pot
similarity index 87%
copy from doc/Pacemaker_Development/pot/Author_Group.pot
copy to doc/Pacemaker_Administration/pot/Author_Group.pot
index 4c66589225..b5a55a50e4 100644
--- a/doc/Pacemaker_Development/pot/Author_Group.pot
+++ b/doc/Pacemaker_Administration/pot/Author_Group.pot
@@ -1,44 +1,44 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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: firstname
#, no-c-format
msgid "Andrew"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Beekhof"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "Red Hat"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Co-author"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Book_Info.pot b/doc/Pacemaker_Administration/pot/Book_Info.pot
similarity index 54%
copy from doc/Pacemaker_Development/pot/Book_Info.pot
copy to doc/Pacemaker_Administration/pot/Book_Info.pot
index c994d01a2f..68a2cdb5f2 100644
--- a/doc/Pacemaker_Development/pot/Book_Info.pot
+++ b/doc/Pacemaker_Administration/pot/Book_Info.pot
@@ -1,29 +1,29 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Pacemaker Development"
+msgid "Pacemaker Administration"
msgstr ""
#. Tag: subtitle
#, no-c-format
-msgid "Working with the Pacemaker Code Base"
+msgid "Managing Pacemaker Clusters"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This document has guidelines and tips for developers interested in editing Pacemaker source code and submitting changes for inclusion in the project."
+msgid "This document has instructions and tips for system administrators who need to manage high-availability clusters using Pacemaker."
msgstr ""
diff --git a/doc/Pacemaker_Administration/pot/Ch-Agents.pot b/doc/Pacemaker_Administration/pot/Ch-Agents.pot
new file mode 100644
index 0000000000..93f76c2158
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Agents.pot
@@ -0,0 +1,644 @@
+#
+# 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 "Resource Agents"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "OCF Resource Agents"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Location of Custom Scripts"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>OCF Resource Agents</primary> </indexterm> OCF Resource Agents are found in <literal>/usr/lib/ocf/resource.d/<replaceable>provider</replaceable></literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When creating your own agents, you are encouraged to create a new directory under <literal>/usr/lib/ocf/resource.d/</literal> so that they are not confused with (or overwritten by) the agents shipped by existing providers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "So, for example, if you choose the provider name of bigCorp and want a new resource named bigApp, you would create a resource agent called <literal>/usr/lib/ocf/resource.d/bigCorp/bigApp</literal> and define a resource:"
+msgstr ""
+
+#. Tag: programlisting
+#, no-c-format
+msgid "&lt;primitive id=\"custom-app\" class=\"ocf\" provider=\"bigCorp\" type=\"bigApp\"/&gt;"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Actions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All OCF resource agents are required to implement the following actions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Required Actions for OCF Agents"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Action"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Instructions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>start</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Start the resource"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully active. <indexterm> <primary>start</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>start</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>start</secondary> </indexterm> <indexterm> <primary>start</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>stop</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Stop the resource"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully stopped. <indexterm> <primary>stop</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>stop</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>stop</secondary> </indexterm> <indexterm> <primary>stop</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>monitor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Check the resource’s state"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Exit 0 if the resource is running, 7 if it is stopped, and anything else if it is failed. <indexterm> <primary>monitor</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>monitor</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>monitor</secondary> </indexterm> <indexterm> <primary>monitor</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "NOTE: The monitor script should test the state of the resource on the local machine only."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>meta-data</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Describe the resource"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Provide information about this resource as an XML snippet. Exit with 0. <indexterm> <primary>meta-data</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>meta-data</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>meta-data</secondary> </indexterm> <indexterm> <primary>meta-data</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "NOTE: This is <emphasis>not</emphasis> performed as root."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>validate-all</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Verify the supplied parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return 0 if parameters are valid, 2 if not valid, and 6 if resource is not configured. <indexterm> <primary>validate-all</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>validate-all</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>validate-all</secondary> </indexterm> <indexterm> <primary>validate-all</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional requirements (not part of the OCF specification) are placed on agents that will be used for advanced concepts such as clone resources."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Optional Actions for OCF Resource Agents"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>promote</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Promote the local instance of a promotable clone resource to the master (primary) state."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return 0 on success <indexterm> <primary>promote</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>promote</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>promote</secondary> </indexterm> <indexterm> <primary>promote</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>demote</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Demote the local instance of a promotable clone resource to the slave (secondary) state."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return 0 on success <indexterm> <primary>demote</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>demote</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>demote</secondary> </indexterm> <indexterm> <primary>demote</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>notify</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Used by the cluster to send the agent pre- and post-notification events telling the resource what has happened and will happen."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Must not fail. Must exit with 0 <indexterm> <primary>notify</primary><secondary>OCF Action</secondary> </indexterm> <indexterm> <primary>OCF Action</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Action</secondary><tertiary>notify</tertiary> </indexterm> <indexterm> <primary>Action</primary><secondary>notify</secondary> </indexterm> <indexterm> <primary>notify</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One action specified in the OCF specs, <literal>recover</literal>, is not currently used by the cluster. It is intended to be a variant of the <literal>start</literal> action that tries to recover a resource locally."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you create a new OCF resource agent, use <indexterm> <primary>ocf-tester</primary> </indexterm><literal>ocf-tester</literal> to verify that the agent complies with the OCF standard properly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How are OCF Return Codes Interpreted?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first thing the cluster does is to check the return code against the expected result. If the result does not match the expected value, then the operation is considered to have failed, and recovery action is initiated."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are three types of failure recovery:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Types of recovery performed by the cluster"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Type"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Action Taken by the Cluster"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>soft</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A transient error occurred"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Restart the resource or move it to a new location <indexterm> <primary>soft</primary><secondary>OCF error</secondary> </indexterm> <indexterm> <primary>OCF error</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>error</secondary><tertiary>soft</tertiary> </indexterm> <indexterm> <primary>error</primary><secondary>soft</secondary> </indexterm> <indexterm> <primary>soft</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hard</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A non-transient error that may be specific to the current node occurred"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Move the resource elsewhere and prevent it from being retried on the current node <indexterm> <primary>hard</primary><secondary>OCF error</secondary> </indexterm> <indexterm> <primary>OCF error</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>error</secondary><tertiary>hard</tertiary> </indexterm> <indexterm> <primary>error</primary><secondary>hard</secondary> </indexterm> <indexterm> <primary>hard</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fatal</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A non-transient error that will be common to all cluster nodes (e.g. a bad configuration was specified)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Stop the resource and prevent it from being started on any cluster node <indexterm> <primary>fatal</primary><secondary>OCF error</secondary> </indexterm> <indexterm> <primary>OCF error</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>error</secondary><tertiary>fatal</tertiary> </indexterm> <indexterm> <primary>error</primary><secondary>fatal</secondary> </indexterm> <indexterm> <primary>fatal</primary> </indexterm>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "OCF Return Codes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table outlines the different OCF return codes and the type of recovery the cluster will initiate when a failure code is received. Although counterintuitive, even actions that return 0 (aka. <literal>OCF_SUCCESS</literal>) can be considered to have failed, if 0 was not the expected return value."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "OCF Return Codes and their Recovery Types"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RC"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "OCF Alias"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>0</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_SUCCESS</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Success. The command completed successfully. This is the expected result for all start, stop, promote and demote commands. <indexterm> <primary>Return Code</primary><secondary>OCF_SUCCESS</secondary> </indexterm> <indexterm> <primary>OCF_SUCCESS</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>0</secondary><tertiary>OCF_SUCCESS</tertiary> </indexterm> <indexterm> <primary>0</primary><secondary>OCF_SUCCESS</secondary> </indexterm> <indexterm> <primary>OCF_SUCCESS</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>1</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_ERR_GENERIC</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Generic \"there was a problem\" error code. <indexterm> <primary>Return Code</primary><secondary>OCF_ERR_GENERIC</secondary> </indexterm> <indexterm> <primary>OCF_ERR_GENERIC</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>1</secondary><tertiary>OCF_ERR_GENERIC</tertiary> </indexterm> <indexterm> <primary>1</primary><secondary>OCF_ERR_GENERIC</secondary> </indexterm> <indexterm> <primary>OCF_ERR_GENERIC</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>2</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_ERR_ARGS</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The resource’s configuration is not valid on this machine. E.g. it refers to a location not found on the node. <indexterm> <primary>Return Code</primary><secondary>OCF_ERR_ARGS</secondary> </indexterm> <indexterm> <primary>OCF_ERR_ARGS</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>2</secondary><tertiary>OCF_ERR_ARGS</tertiary> </indexterm> <indexterm> <primary>2</primary><secondary>OCF_ERR_ARGS</secondary> </indexterm> <indexterm> <primary>OCF_ERR_ARGS</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>3</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_ERR_UNIMPLEMENTED</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The requested action is not implemented. <indexterm> <primary>Return Code</primary><secondary>OCF_ERR_UNIMPLEMENTED</secondary> </indexterm> <indexterm> <primary>OCF_ERR_UNIMPLEMENTED</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>3</secondary><tertiary>OCF_ERR_UNIMPLEMENTED</tertiary> </indexterm> <indexterm> <primary>3</primary><secondary>OCF_ERR_UNIMPLEMENTED</secondary> </indexterm> <indexterm> <primary>OCF_ERR_UNIMPLEMENTED</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>4</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_ERR_PERM</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The resource agent does not have sufficient privileges to complete the task. <indexterm> <primary>Return Code</primary><secondary>OCF_ERR_PERM</secondary> </indexterm> <indexterm> <primary>OCF_ERR_PERM</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>4</secondary><tertiary>OCF_ERR_PERM</tertiary> </indexterm> <indexterm> <primary>4</primary><secondary>OCF_ERR_PERM</secondary> </indexterm> <indexterm> <primary>OCF_ERR_PERM</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>5</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_ERR_INSTALLED</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The tools required by the resource are not installed on this machine. <indexterm> <primary>Return Code</primary><secondary>OCF_ERR_INSTALLED</secondary> </indexterm> <indexterm> <primary>OCF_ERR_INSTALLED</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>5</secondary><tertiary>OCF_ERR_INSTALLED</tertiary> </indexterm> <indexterm> <primary>5</primary><secondary>OCF_ERR_INSTALLED</secondary> </indexterm> <indexterm> <primary>OCF_ERR_INSTALLED</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>6</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_ERR_CONFIGURED</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The resource’s configuration is invalid. E.g. required parameters are missing. <indexterm> <primary>Return Code</primary><secondary>OCF_ERR_CONFIGURED</secondary> </indexterm> <indexterm> <primary>OCF_ERR_CONFIGURED</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>6</secondary><tertiary>OCF_ERR_CONFIGURED</tertiary> </indexterm> <indexterm> <primary>6</primary><secondary>OCF_ERR_CONFIGURED</secondary> </indexterm> <indexterm> <primary>OCF_ERR_CONFIGURED</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>7</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_NOT_RUNNING</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The resource is safely stopped. The cluster will not attempt to stop a resource that returns this for any action. <indexterm> <primary>Return Code</primary><secondary>OCF_NOT_RUNNING</secondary> </indexterm> <indexterm> <primary>OCF_NOT_RUNNING</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>7</secondary><tertiary>OCF_NOT_RUNNING</tertiary> </indexterm> <indexterm> <primary>7</primary><secondary>OCF_NOT_RUNNING</secondary> </indexterm> <indexterm> <primary>OCF_NOT_RUNNING</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>N/A</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>8</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_RUNNING_MASTER</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The resource is running in master mode. <indexterm> <primary>Return Code</primary><secondary>OCF_RUNNING_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_RUNNING_MASTER</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>8</secondary><tertiary>OCF_RUNNING_MASTER</tertiary> </indexterm> <indexterm> <primary>8</primary><secondary>OCF_RUNNING_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_RUNNING_MASTER</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>9</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>OCF_FAILED_MASTER</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The resource is in master mode but has failed. The resource will be demoted, stopped and then started (and possibly promoted) again. <indexterm> <primary>Return Code</primary><secondary>OCF_FAILED_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_FAILED_MASTER</primary> </indexterm> <indexterm> <primary>Return Code</primary><secondary>9</secondary><tertiary>OCF_FAILED_MASTER</tertiary> </indexterm> <indexterm> <primary>9</primary><secondary>OCF_FAILED_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_FAILED_MASTER</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>other</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom error code. <indexterm> <primary>Return Code</primary><secondary>other</secondary> </indexterm> <indexterm> <primary>other</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Exceptions to the recovery handling described above:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Probes (non-recurring monitor actions) that find a resource active (or in master mode) will not result in recovery action unless it is also found active elsewhere."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The recovery action taken when a resource is found active more than once is determined by the resource’s <literal>multiple-active</literal> property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recurring actions that return <literal>OCF_ERR_UNIMPLEMENTED</literal> do not cause any type of recovery."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Init Script LSB Compliance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The relevant part of the <ulink url=\"http://refspecs.linuxfoundation.org/lsb.shtml\">LSB specifications</ulink> includes a description of all the return codes listed here."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Assuming <literal>some_service</literal> is configured correctly and currently inactive, the following sequence will help you determine if it is LSB-compatible:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Start (stopped):"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# /etc/init.d/some_service start ; echo \"result: $?\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Did the service start?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Did the command print <emphasis role=\"strong\">result: 0</emphasis> (in addition to its usual output)?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Status (running):"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# /etc/init.d/some_service status ; echo \"result: $?\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Did the script accept the command?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Did the script indicate the service was running?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Start (running):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Is the service still running?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Stop (running):"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# /etc/init.d/some_service stop ; echo \"result: $?\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Was the service stopped?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Status (stopped):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Did the script indicate the service was not running?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Did the command print <emphasis role=\"strong\">result: 3</emphasis> (in addition to its usual output)?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Stop (stopped):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Is the service still stopped?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Status (failed):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This step is not readily testable and relies on manual inspection of the script."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The script can use one of the error codes (other than 3) listed in the LSB spec to indicate that it is active but failed. This tells the cluster that before moving the resource to another node, it needs to stop it on the existing one first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the answer to any of the above questions is no, then the script is not LSB-compliant. Your options are then to either fix the script or write an OCF agent based on the existing script."
+msgstr ""
+
diff --git a/doc/Pacemaker_Administration/pot/Ch-Cluster.pot b/doc/Pacemaker_Administration/pot/Ch-Cluster.pot
new file mode 100644
index 0000000000..26ac4169bb
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Cluster.pot
@@ -0,0 +1,139 @@
+#
+# 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 "The Cluster Layer"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Pacemaker and the Cluster Layer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker utilizes an underlying cluster layer for two purposes:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "obtaining quorum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "messaging between nodes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Currently, only Corosync 2 and later is supported for this layer."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managing Nodes in a Corosync-Based Cluster"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding a New Corosync Node"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>Corosync</primary><secondary>Add Cluster Node</secondary> </indexterm> <indexterm> <primary>Add Cluster Node</primary> </indexterm> <indexterm> <primary>Add Cluster Node</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To add a new node:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Install Corosync and Pacemaker on the new host."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy <literal>/etc/corosync/corosync.conf</literal> and <literal>/etc/corosync/authkey</literal> (if it exists) from an existing node. You may need to modify the <emphasis role=\"strong\">mcastaddr</emphasis> option to match the new node’s IP address."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Start the cluster software on the new host. If a log message containing \"Invalid digest\" appears from Corosync, the keys are not consistent between the machines."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Removing a Corosync Node"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>Corosync</primary><secondary>Remove Cluster Node</secondary> </indexterm> <indexterm> <primary>Remove Cluster Node</primary> </indexterm> <indexterm> <primary>Remove Cluster Node</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a complete solution. First, one must arrange for corosync to forget about the node (<emphasis role=\"strong\">pcmk-1</emphasis> in the example below)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Stop the cluster on the host to be removed. How to do this will vary with your operating system and installed versions of cluster software, for example, <literal>pcs cluster stop</literal> if you are using pcs for cluster management."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From one of the remaining active cluster nodes, tell Pacemaker to forget about the removed host, which will also delete the node from the CIB:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_node -R pcmk-1"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Replacing a Corosync Node"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>Corosync</primary><secondary>Replace Cluster Node</secondary> </indexterm> <indexterm> <primary>Replace Cluster Node</primary> </indexterm> <indexterm> <primary>Replace Cluster Node</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To replace an existing cluster node:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Make sure the old node is completely stopped."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Give the new machine the same hostname and IP address as the old one."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Follow the procedure above for adding a node."
+msgstr ""
+
diff --git a/doc/Pacemaker_Administration/pot/Ch-Configuring.pot b/doc/Pacemaker_Administration/pot/Ch-Configuring.pot
new file mode 100644
index 0000000000..3c0acd109e
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Configuring.pot
@@ -0,0 +1,679 @@
+#
+# 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 "Configuring Pacemaker"
+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 &amp; 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 &gt; 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 &gt; 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"
+" &lt;nvpair id=\"cib-bootstrap-options-stonith-action\" name=\"stonith-action\" value=\"reboot\"/&gt;\n"
+" &lt;nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"1\"/&gt;\n"
+" &lt;primitive id=\"child_DoFencing\" class=\"stonith\" type=\"external/vmware\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:1\" type=\"external/vmware\" class=\"stonith\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:2\" type=\"external/vmware\" class=\"stonith\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\"&gt;\n"
+" &lt;lrm_resource id=\"child_DoFencing:3\" type=\"external/vmware\" class=\"stonith\"&gt;"
+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 '&lt;primitive id=\"child_DoFencing\"/&gt;'"
+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 --query --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: 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 all at once. 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 "Use sandbox to make multiple changes all at once, discard them, and verify real configuration is untouched"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid " shadow[test] # crm_failcount -r rsc_c001n01 -G\n"
+" scope=status name=fail-count-rsc_c001n01 value=0\n"
+" shadow[test] # crm_standby --node c001n02 -v on\n"
+" shadow[test] # crm_standby --node c001n02 -G\n"
+" scope=nodes name=standby value=on\n"
+"\n"
+" shadow[test] # cibadmin --erase --force\n"
+" shadow[test] # cibadmin --query\n"
+" &lt;cib crm_feature_set=\"3.0.14\" validate-with=\"pacemaker-3.0\" epoch=\"112\" num_updates=\"2\" admin_epoch=\"0\" cib-last-written=\"Mon Jan 8 23:26:47 2018\" update-origin=\"rhel7-1\" update-client=\"crm_node\" update-user=\"root\" have-quorum=\"1\" dc-uuid=\"1\"&gt;\n"
+" &lt;configuration&gt;\n"
+" &lt;crm_config/&gt;\n"
+" &lt;nodes/&gt;\n"
+" &lt;resources/&gt;\n"
+" &lt;constraints/&gt;\n"
+" &lt;/configuration&gt;\n"
+" &lt;status/&gt;\n"
+" &lt;/cib&gt;\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"
+" &lt;cib crm_feature_set=\"3.0.14\" validate-with=\"pacemaker-3.0\" epoch=\"110\" num_updates=\"2\" admin_epoch=\"0\" cib-last-written=\"Mon Jan 8 23:26:47 2018\" update-origin=\"rhel7-1\" update-client=\"crm_node\" update-user=\"root\" have-quorum=\"1\"&gt;\n"
+" &lt;configuration&gt;\n"
+" &lt;crm_config&gt;\n"
+" &lt;cluster_property_set id=\"cib-bootstrap-options\"&gt;\n"
+" &lt;nvpair id=\"cib-bootstrap-1\" name=\"stonith-enabled\" value=\"1\"/&gt;\n"
+" &lt;nvpair id=\"cib-bootstrap-2\" name=\"pe-input-series-max\" value=\"30000\"/&gt;"
+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 ""
+
+#. Tag: title
+#, no-c-format
+msgid "Working with CIB Properties"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Although these fields can be written to by the user, in most cases the cluster will overwrite any values specified by the user with the \"correct\" ones."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To change the ones that can be specified by the user, for example <literal>admin_epoch</literal>, one should use:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# cibadmin --modify --xml-text '&lt;cib admin_epoch=\"42\"/&gt;'"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A complete set of CIB properties will look something like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Attributes set for a cib object"
+msgstr ""
+
+#. Tag: programlisting
+#, no-c-format
+msgid "&lt;cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\"\n"
+" admin_epoch=\"42\" epoch=\"116\" num_updates=\"1\"\n"
+" cib-last-written=\"Mon Jan 12 15:46:39 2015\" update-origin=\"rhel7-1\"\n"
+" update-client=\"crm_attribute\" have-quorum=\"1\" dc-uuid=\"1\"&gt;"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Querying and Setting Cluster Options"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>Querying</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Setting</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Querying Options</secondary> </indexterm> <indexterm> <primary>Querying Options</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Setting Options</secondary> </indexterm> <indexterm> <primary>Setting Options</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cluster options can be queried and modified using the <literal>crm_attribute</literal> tool. To get the current value of <literal>cluster-delay</literal>, you can run:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute --query --name cluster-delay"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "which is more simply written as"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute -G -n cluster-delay"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If a value is found, you’ll see a result like this:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute -G -n cluster-delay\n"
+"scope=crm_config name=cluster-delay value=60s"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If no value is found, the tool will display an error:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute -G -n clusta-deway\n"
+"scope=crm_config name=clusta-deway value=(null)\n"
+"Error performing operation: No such device or address"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use a different value (for example, 30 seconds), simply run:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute --name cluster-delay --update 30s"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To go back to the cluster’s default value, you can delete the value, for example:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute --name cluster-delay --delete\n"
+"Deleted crm_config option: id=cib-bootstrap-options-cluster-delay name=cluster-delay"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When Options are Listed More Than Once"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you ever see something like the following, it means that the option you’re modifying is present more than once."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Deleting an option that is listed twice"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute --name batch-limit --delete\n"
+"\n"
+"Multiple attributes match name=batch-limit in crm_config:\n"
+"Value: 50 (set=cib-bootstrap-options, id=cib-bootstrap-options-batch-limit)\n"
+"Value: 100 (set=custom, id=custom-batch-limit)\n"
+"Please choose from one of the matches above and supply the 'id' with --id"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In such cases, follow the on-screen instructions to perform the requested action. To determine which value is currently being used by the cluster, refer to the <emphasis>Rules</emphasis> section of <emphasis>Pacemaker Explained</emphasis>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Connecting from a Remote Machine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>Cluster</primary><secondary>Remote connection</secondary> </indexterm> <indexterm> <primary>Remote connection</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Remote administration</secondary> </indexterm> <indexterm> <primary>Remote administration</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Provided Pacemaker is installed on a machine, it is possible to connect to the cluster even if the machine itself is not in the same cluster. To do this, one simply sets up a number of environment variables and runs the same commands as when working on a cluster node."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Environment Variables Used to Connect to Remote Instances of the CIB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Environment Variable"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>CIB_user</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "$USER"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The user to connect as. Needs to be part of the <literal>haclient</literal> group on the target host. <indexterm> <primary>Environment Variable</primary><secondary>CIB_user</secondary> </indexterm> <indexterm> <primary>CIB_user</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>CIB_passwd</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The user’s password. Read from the command line if unset. <indexterm> <primary>Environment Variable</primary><secondary>CIB_passwd</secondary> </indexterm> <indexterm> <primary>CIB_passwd</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>CIB_server</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "localhost"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The host to contact <indexterm> <primary>Environment Variable</primary><secondary>CIB_server</secondary> </indexterm> <indexterm> <primary>CIB_server</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>CIB_port</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The port on which to contact the server; required. <indexterm> <primary>Environment Variable</primary><secondary>CIB_port</secondary> </indexterm> <indexterm> <primary>CIB_port</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>CIB_encrypted</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "TRUE"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Whether to encrypt network traffic <indexterm> <primary>Environment Variable</primary><secondary>CIB_encrypted</secondary> </indexterm> <indexterm> <primary>CIB_encrypted</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "So, if <emphasis role=\"strong\">c001n01</emphasis> is an active cluster node and is listening on port 1234 for connections, and <emphasis role=\"strong\">someuser</emphasis> is a member of the <emphasis role=\"strong\">haclient</emphasis> group, then the following would prompt for <emphasis role=\"strong\">someuser</emphasis>'s password and return the cluster’s current configuration:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someuser;\n"
+"# cibadmin -Q"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For security reasons, the cluster does not listen for remote connections by default. If you wish to allow remote access, you need to set the <literal>remote-tls-port</literal> (encrypted) or <literal>remote-clear-port</literal> (unencrypted) CIB properties (i.e., those kept in the <literal>cib</literal> tag, like <literal>num_updates</literal> and <literal>epoch</literal>)."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extra top-level CIB properties for remote access"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Field"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>remote-tls-port</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>none</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Listen for encrypted remote connections on this port. <indexterm> <primary>remote-tls-port</primary><secondary>Remote Connection Option</secondary> </indexterm> <indexterm> <primary>Remote Connection Option</primary> </indexterm> <indexterm> <primary>Remote Connection</primary><secondary>Option</secondary><tertiary>remote-tls-port</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>remote-tls-port</secondary> </indexterm> <indexterm> <primary>remote-tls-port</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>remote-clear-port</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Listen for plaintext remote connections on this port. <indexterm> <primary>remote-clear-port</primary><secondary>Remote Connection Option</secondary> </indexterm> <indexterm> <primary>Remote Connection Option</primary> </indexterm> <indexterm> <primary>Remote Connection</primary><secondary>Option</secondary><tertiary>remote-clear-port</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>remote-clear-port</secondary> </indexterm> <indexterm> <primary>remote-clear-port</primary> </indexterm>"
+msgstr ""
+
diff --git a/doc/Pacemaker_Administration/pot/Ch-Installing.pot b/doc/Pacemaker_Administration/pot/Ch-Installing.pot
new file mode 100644
index 0000000000..912a1bfe3b
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Installing.pot
@@ -0,0 +1,143 @@
+#
+# 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 "Installing Cluster Software"
+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: title
+#, no-c-format
+msgid "Enabling Pacemaker"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Enabling Pacemaker For Corosync version 2 and greater"
+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 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 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."
+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 ""
+
diff --git a/doc/Pacemaker_Administration/pot/Ch-Intro.pot b/doc/Pacemaker_Administration/pot/Ch-Intro.pot
new file mode 100644
index 0000000000..8d89892d23
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Intro.pot
@@ -0,0 +1,359 @@
+#
+# 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 "Read-Me-First"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "The Scope of this Document"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The purpose of this document is to help system administrators learn how to manage a Pacemaker cluster."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "System administrators may be interested in other parts of the <ulink url=\"https://www.clusterlabs.org/pacemaker/doc/\">Pacemaker documentation set</ulink>, such as <emphasis>Clusters from Scratch</emphasis>, a step-by-step guide to setting up an example cluster, and <emphasis>Pacemaker Explained</emphasis>, an exhaustive reference for cluster configuration."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Multiple higher-level tools (both command-line and GUI) are available to simplify cluster management. However, this document focuses on the lower-level command-line tools that come with Pacemaker itself. The concepts are applicable to the higher-level tools, though the syntax would differ."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What Is <emphasis>Pacemaker</emphasis>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Pacemaker</emphasis> is a high-availability <emphasis>cluster resource manager</emphasis> — software that runs on a set of hosts (a <emphasis>cluster</emphasis> of <emphasis>nodes</emphasis>) in order to minimize downtime of desired services (<emphasis>resources</emphasis>). <footnote><para> <emphasis>Cluster</emphasis> is sometimes used in other contexts to refer to hosts grouped together for other purposes, such as high-performance computing (HPC), but Pacemaker is not intended for those purposes. </para></footnote>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker’s key features include:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Detection of and recovery from node- and service-level failures"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Ability to ensure data integrity by fencing faulty nodes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support for one or more nodes per cluster"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support for multiple resource interface standards (anything that can be scripted can be clustered)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support (but no requirement) for shared storage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support for practically any redundancy configuration (active/passive, N+1, etc.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Automatically replicated configuration that can be updated from any node"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Ability to specify cluster-wide relationships between services, such as ordering, colocation and anti-colocation"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support for advanced service types, such as <emphasis>clones</emphasis> (services that need to be active on multiple nodes), <emphasis>stateful resources</emphasis> (clones that can run in one of two modes), and containerized services"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Unified, scriptable cluster management tools"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fencing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fencing</emphasis>, also known as <emphasis>STONITH</emphasis> (an acronym for Shoot The Other Node In The Head), is the ability to ensure that it is not possible for a node to be running a service. This is accomplished via <emphasis>fence devices</emphasis> such as intelligent power switches that cut power to the target, or intelligent network switches that cut the target’s access to the local network."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker represents fence devices as a special class of resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A cluster cannot safely recover from certain failure conditions, such as an unresponsive node, without fencing."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Cluster Architecture"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "At a high level, a cluster can viewed as having these parts (which together are often referred to as the <emphasis>cluster stack</emphasis>):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Resources:</emphasis> These are the reason for the cluster’s being — the services that need to be kept highly available."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Resource agents:</emphasis> These are scripts or operating system components that start, stop, and monitor resources, given a set of resource parameters. These provide a uniform interface between Pacemaker and the managed services."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Fence agents:</emphasis> These are scripts that execute node fencing actions, given a target and fence device parameters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster membership layer:</emphasis> This component provides reliable messaging, membership, and quorum information about the cluster. Currently, Pacemaker supports <ulink url=\"http://www.corosync.org/\">Corosync</ulink> as this layer."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster resource manager:</emphasis> Pacemaker provides the brain that processes and reacts to events that occur in the cluster. These events may include nodes joining or leaving the cluster; resource events caused by failures, maintenance, or scheduled activities; and other administrative actions. To achieve the desired availability, Pacemaker may start and stop resources and fence nodes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster tools:</emphasis> These provide an interface for users to interact with the cluster. Various command-line and graphical (GUI) interfaces are available."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most managed services are not, themselves, cluster-aware. However, many popular open-source cluster filesystems make use of a common <emphasis>Distributed Lock Manager</emphasis> (DLM), which makes direct use of Corosync for its messaging and membership capabilities and Pacemaker for the ability to fence nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example Cluster Stack"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Pacemaker Architecture"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker itself is composed of multiple daemons that work together:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemakerd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-attrd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-based"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-controld"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-execd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-fenced"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-schedulerd"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Internal Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Pacemaker master process (pacemakerd) spawns all the other daemons, and respawns them if they unexpectedly exit."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Cluster Information Base</emphasis> (CIB) is an <ulink url=\"https://en.wikipedia.org/wiki/XML\">XML</ulink> representation of the cluster’s configuration and the state of all nodes and resources. The <emphasis>CIB manager</emphasis> (pacemaker-based) keeps the CIB synchronized across the cluster, and handles requests to modify it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The attribute manager (pacemaker-attrd) maintains a database of attributes for all nodes, keeps it synchronized across the cluster, and handles requests to modify them. These attributes are usually recorded in the CIB."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Given a snapshot of the CIB as input, the <emphasis>scheduler</emphasis> (pacemaker-schedulerd) determines what actions are necessary to achieve the desired state of the cluster."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>local executor</emphasis> (pacemaker-execd) handles requests to execute resource agents on the local cluster node, and returns the result."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>fencer</emphasis> (pacemaker-fenced) handles requests to fence nodes. Given a target node, the fencer decides which cluster node(s) should execute which fencing device(s), and calls the necessary fencing agents (either directly, or via requests to the fencer peers on other nodes), and returns the result."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>controller</emphasis> (pacemaker-controld) is Pacemaker’s coordinator, maintaining a consistent view of the cluster membership and orchestrating all the other components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker centralizes cluster decision-making by electing one of the controller instances as the <emphasis>Designated Controller</emphasis> (<emphasis>DC</emphasis>). Should the elected DC process (or the node it is on) fail, a new one is quickly established. The DC responds to cluster events by taking a current snapshot of the CIB, feeding it to the scheduler, then asking the executors (either directly on the local node, or via requests to controller peers on other nodes) and the fencer to execute any necessary actions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Old daemon names"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Pacemaker daemons were renamed in version 2.0. You may still find references to the old names, especially in documentation targeted to version 1.1."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Old name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "New name"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "attrd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "cib"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "crmd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "lrmd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "stonithd"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker_remoted"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-remoted"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Node Redundancy Designs"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker supports practically any <ulink url=\"https://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations\">node redundancy configuration</ulink> including <emphasis>Active/Active</emphasis>, <emphasis>Active/Passive</emphasis>, <emphasis>N+1</emphasis>, <emphasis>N+M</emphasis>, <emphasis>N-to-1</emphasis> and <emphasis>N-to-N</emphasis>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Active/passive clusters with two (or more) nodes using Pacemaker and <ulink url=\"https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device:\">DRBD</ulink> are a cost-effective high-availability solution for many situations. One of the nodes provides the desired services, and if it fails, the other node takes over."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Active/Passive Redundancy"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker also supports multiple nodes in a shared-failover design, reducing hardware costs by allowing several active/passive clusters to be combined and share a common backup node."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Shared Failover"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When shared storage is available, every node can potentially be used for failover. Pacemaker can even run multiple copies of services to spread out the workload."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "N to N Redundancy"
+msgstr ""
+
diff --git a/doc/Pacemaker_Administration/pot/Ch-Monitoring.pot b/doc/Pacemaker_Administration/pot/Ch-Monitoring.pot
new file mode 100644
index 0000000000..c6fcb4e113
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Monitoring.pot
@@ -0,0 +1,91 @@
+#
+# 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 "Monitoring a Pacemaker Cluster"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using crm_mon"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>crm_mon</literal> utility displays the current state of an active cluster. It can show the cluster status organized by node or by resource, and can be used in either single-shot or dynamically updating mode. It can also display operations performed and 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 "See the manual page or the output of <literal>crm_mon --help</literal> for a full description of its many options."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sample output from crm_mon -1"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "Stack: corosync\n"
+"Current DC: node2 (version 2.0.0-1) - partition with quorum\n"
+"Last updated: Mon Jan 29 12:18:42 2018\n"
+"Last change: Mon Jan 29 12:18:40 2018 by root via crm_attribute on node3\n"
+"\n"
+"5 nodes configured\n"
+"2 resources configured\n"
+"\n"
+"Online: [ node1 node2 node3 node4 node5 ]\n"
+"\n"
+"Active resources:\n"
+"\n"
+"Fencing (stonith:fence_xvm): Started node1\n"
+"IP (ocf:heartbeat:IPaddr2): Started node2"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sample output from crm_mon -n -1"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "Stack: corosync\n"
+"Current DC: node2 (version 2.0.0-1) - partition with quorum\n"
+"Last updated: Mon Jan 29 12:21:48 2018\n"
+"Last change: Mon Jan 29 12:18:40 2018 by root via crm_attribute on node3\n"
+"\n"
+"5 nodes configured\n"
+"2 resources configured\n"
+"\n"
+"Node node1: online\n"
+" Fencing (stonith:fence_xvm): Started\n"
+"Node node2: online\n"
+" IP (ocf:heartbeat:IPaddr2): Started\n"
+"Node node3: online\n"
+"Node node4: online\n"
+"Node node5: online"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in an earlier section, the DC is the node is where decisions are made. The cluster elects a node to be DC as needed. The only significance of the choice of DC to an administrator is the fact that its logs will have the most information about why decisions were made."
+msgstr ""
+
diff --git a/doc/Pacemaker_Administration/pot/Ch-Upgrading.pot b/doc/Pacemaker_Administration/pot/Ch-Upgrading.pot
new file mode 100644
index 0000000000..fd7eb35bdf
--- /dev/null
+++ b/doc/Pacemaker_Administration/pot/Ch-Upgrading.pot
@@ -0,0 +1,800 @@
+#
+# 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 "Upgrading a Pacemaker Cluster"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Pacemaker Versioning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker has an overall release version, plus separate version numbers for certain internal components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Pacemaker release version:</emphasis> This version consists of three numbers (<emphasis>x.y.z</emphasis>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The major version number (the <emphasis>x</emphasis> in <emphasis>x.y.z</emphasis>) increases when at least some rolling upgrades are not possible from the previous major version. For example, a rolling upgrade from 1.0.8 to 1.1.15 should always be supported, but a rolling upgrade from 1.0.8 to 2.0.0 may not be possible."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The minor version (the <emphasis>y</emphasis> in <emphasis>x.y.z</emphasis>) increases when there are significant changes in cluster default behavior, tool behavior, and/or the API interface (for software that utilizes Pacemaker libraries). The main benefit is to alert you to pay closer attention to the release notes, to see if you might be affected."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The release counter (the <emphasis>z</emphasis> in <emphasis>x.y.z</emphasis>) is increased with all public releases of Pacemaker, which typically include both bug fixes and new features."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">CRM feature set:</emphasis> This version number applies to the communication between full cluster nodes, and is used to avoid problems in mixed-version clusters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The major version number increases when nodes with different versions would not work (rolling upgrades are not allowed). The minor version number increases when mixed-version clusters are allowed only during rolling upgrades. The minor-minor version number is ignored, but allows resource agents to detect cluster support for various features. <footnote><para> Before CRM feature set 3.1.0 (Pacemaker 2.0.0), the minor-minor version number was treated the same as the minor version. </para></footnote>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker ensures that the longest-running node is the cluster’s DC. This ensures new features are not enabled until all nodes are upgraded to support them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">LRMD protocol version:</emphasis> This version applies to communication between a Pacemaker Remote node and the cluster. It increases when an older cluster node would have problems hosting the connection to a newer Pacemaker Remote node. To avoid these problems, Pacemaker Remote nodes will accept connections only from cluster nodes with the same or newer LRMD protocol version."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Unlike with CRM feature set differences between full cluster nodes, mixed LRMD protocol versions between Pacemaker Remote nodes and full cluster nodes are fine, as long as the Pacemaker Remote nodes have the older version. This can be useful, for example, to host a legacy application in an older operating system version used as a Pacemaker Remote node."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">XML schema version:</emphasis> Pacemaker’s configuration syntax — what’s allowed in the Configuration Information Base (CIB) — has its own version. This allows the configuration syntax to evolve over time while still allowing clusters with older configurations to work without change."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Upgrading Cluster Software"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are three approaches to upgrading a cluster, each with advantages and disadvantages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Upgrade Methods"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Method"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Available between all versions"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Can be used with Pacemaker Remote nodes"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Service outage during upgrade"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Service recovery during upgrade"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Exercises failover logic"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Allows change of messaging layer <indexterm> <primary>Cluster</primary><secondary>switching between stacks</secondary> </indexterm> <indexterm> <primary>switching between stacks</primary> </indexterm> <indexterm> <primary>Changing cluster stack</primary> </indexterm> <footnote><para>Currently, Corosync version 2 and greater is the only supported cluster stack, but other stacks have been supported by past versions, and may be supported by future versions.</para></footnote>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Complete cluster shutdown <indexterm> <primary>upgrade</primary><secondary>shutdown</secondary> </indexterm> <indexterm> <primary>shutdown</primary> </indexterm> <indexterm> <primary>shutdown upgrade</primary> </indexterm></emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "yes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "always"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "N/A"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "no"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Rolling (node by node) <indexterm> <primary>upgrade</primary><secondary>rolling</secondary> </indexterm> <indexterm> <primary>rolling</primary> </indexterm> <indexterm> <primary>rolling upgrade</primary> </indexterm></emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "always <footnote><para>Any active resources will be moved off the node being upgraded, so there will be at least a brief outage unless all resources can be migrated \"live\".</para></footnote>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Detach and reattach <indexterm> <primary>upgrade</primary><secondary>reattach</secondary> </indexterm> <indexterm> <primary>reattach</primary> </indexterm> <indexterm> <primary>reattach upgrade</primary> </indexterm></emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "only due to failure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Complete Cluster Shutdown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this scenario, one shuts down all cluster nodes and resources, then upgrades all the nodes before restarting the cluster."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "On each node:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shutdown the cluster software (pacemaker and the messaging layer)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Upgrade the Pacemaker software. This may also include upgrading the messaging layer and/or the underlying operating system."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Check the configuration with the <literal>crm_verify</literal> tool."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Start the cluster software. Currently, only Corosync version 2 and greater is supported as the cluster layer, but if another stack is supported in the future, the stack does not need to be the same one before the upgrade."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One variation of this approach is to build a new cluster on new hosts. This allows the new version to be tested beforehand, and minimizes downtime by having the new nodes ready to be placed in production as soon as the old nodes are shut down."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rolling (node by node)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this scenario, each node is removed from the cluster, upgraded, and then brought back online, until all nodes are running the newest version."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Special considerations when planning a rolling upgrade:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you plan to upgrade other cluster software — such as the messaging layer —  at the same time, consult that software’s documentation for its compatibility with a rolling upgrade."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the major version number is changing in the Pacemaker version you are upgrading to, a rolling upgrade may not be possible. Read the new version’s release notes (as well the information here) for what limitations may exist."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the CRM feature set is changing in the Pacemaker version you are upgrading to, you should run a mixed-version cluster only during a small rolling upgrade window. If one of the older nodes drops out of the cluster for any reason, it will not be able to rejoin until it is upgraded."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the LRMD protocol version is changing, all cluster nodes should be upgraded before upgrading any Pacemaker Remote nodes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "See the ClusterLabs wiki’s <ulink url=\"http://clusterlabs.org/wiki/ReleaseCalendar\">Release Calendar</ulink> to figure out whether the CRM feature set and/or LRMD protocol version changed between the the Pacemaker release versions in your rolling upgrade."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To perform a rolling upgrade, on each node in turn:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Put the node into standby mode, and wait for any active resources to be moved cleanly to another node. (This step is optional, but allows you to deal with any resource issues before the upgrade.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shutdown the cluster software (pacemaker and the messaging layer) on the node."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If this is the first node to be upgraded, check the configuration with the <literal>crm_verify</literal> tool."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Start the messaging layer. This must be the same messaging layer (currently only Corosync version 2 and greater is supported) that the rest of the cluster is using."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Even if a rolling upgrade from the current version of the cluster to the newest version is not directly possible, it may be possible to perform a rolling upgrade in multiple steps, by upgrading to an intermediate version first."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Version Compatibility Table"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Version being Installed"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Oldest Compatible Version"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker 2.y.z"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker 1.1.11 <footnote><para>Rolling upgrades from Pacemaker 1.1.z to 2.y.z are possible only if the cluster uses corosync version 2 or greater as its messaging layer, and the Cluster Information Base (CIB) uses schema 1.0 or higher in its validate-with property.</para></footnote>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker 1.y.z"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker 1.0.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker 0.7.z"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker 0.6.z"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Detach and Reattach"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The reattach method is a variant of a complete cluster shutdown, where the resources are left active and get re-detected when the cluster is restarted."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method may not be used if the cluster contains any Pacemaker Remote nodes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Tell the cluster to stop managing services. This is required to allow the services to remain active after the cluster shuts down."
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute --name maintenance-mode --update true"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "On each node, shutdown the cluster software (pacemaker and the messaging layer), and upgrade the Pacemaker software. This may also include upgrading the messaging layer. While the underlying operating system may be upgraded at the same time, that will be more likely to cause outages in the detached services (certainly, if a reboot is required)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "On each node, start the cluster software. Currently, only Corosync version 2 and greater is supported as the cluster layer, but if another stack is supported in the future, the stack does not need to be the same one before the upgrade."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Verify that the cluster re-detected all resources correctly."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Allow the cluster to resume managing resources again:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_attribute --name maintenance-mode --delete"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Upgrading the Configuration"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>upgrade</primary><secondary>Configuration</secondary> </indexterm> <indexterm> <primary>Configuration</primary> </indexterm> <indexterm> <primary>Configuration</primary><secondary>upgrading</secondary> </indexterm> <indexterm> <primary>upgrading</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The CIB schema version can change from one Pacemaker version to another."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After cluster software is upgraded, the cluster will continue to use the older schema version that it was previously using. This can be useful, for example, when administrators have written tools that modify the configuration, and are based on the older syntax. <footnote><para>As of Pacemaker 2.0.0, only schema versions pacemaker-1.0 and higher are supported (excluding pacemaker-1.1, which was an experimental schema now known as pacemaker-next).</para></footnote>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "However, when using an older syntax, new features may be unavailable, and there is a performance impact, since the cluster must do a non-persistent configuration upgrade before each transition. So while using the old syntax is possible, it is not advisable to continue using it indefinitely."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Even if you wish to continue using the old syntax, it is a good idea to follow the upgrade procedure outlined below, except for the last step, to ensure that the new software has no problems with your existing configuration (since it will perform much the same task internally)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are brave, it is sufficient simply to run <literal>cibadmin --upgrade</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A more cautious approach would proceed like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a shadow copy of the configuration. The later commands will automatically operate on this copy, rather than the live configuration."
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_shadow --create shadow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Verify the configuration is valid with the new software (which may be stricter about syntax mistakes, or may have dropped support for deprecated features): <indexterm> <primary>Configuration</primary><secondary>verify</secondary> </indexterm> <indexterm> <primary>verify</primary> </indexterm> <indexterm> <primary>verify</primary><secondary>Configuration</secondary> </indexterm> <indexterm> <primary>Configuration</primary> </indexterm>"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_verify --live-check"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fix any errors or warnings."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Perform the upgrade:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# cibadmin --upgrade"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If this step fails, there are three main possibilities:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The configuration was not valid to start with (did you do steps 2 and 3?)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transformation failed - <ulink url=\"http://bugs.clusterlabs.org/\">report a bug</ulink> or <ulink url=\"mailto:users@clusterlabs.org?subject=Transformation%20failed%20during%20upgrade\">email the project</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transformation was successful but produced an invalid result."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the result of the transformation is invalid, you may see a number of errors from the validation library. If these are not helpful, visit the <ulink url=\"http://clusterlabs.org/wiki/Validation_FAQ\">Validation FAQ wiki page</ulink> and/or try the manual upgrade procedure described below."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Check the changes:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_shadow --diff"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If at this point there is anything about the upgrade that you wish to fine-tune (for example, to change some of the automatic IDs), now is the time to do so:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_shadow --edit"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This will open the configuration in your favorite editor (whichever is specified by the standard <emphasis role=\"strong\">$EDITOR</emphasis> environment variable)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Preview how the cluster will react:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_simulate --live-check --save-dotfile shadow.dot -S\n"
+"# graphviz shadow.dot"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Verify that either no resource actions will occur or that you are happy with any that are scheduled. If the output contains actions you do not expect (possibly due to changes to the score calculations), you may need to make further manual changes. See <xref linkend=\"s-config-testing-changes\" /> for further details on how to interpret the output of <literal>crm_simulate</literal> and <literal>graphviz</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Upload the changes:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# crm_shadow --commit shadow --force"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the unlikely event this step fails, please report a bug."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>Configuration</primary><secondary>upgrade manually</secondary> </indexterm> <indexterm> <primary>upgrade manually</primary> </indexterm> It is also possible to perform the configuration upgrade steps manually:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Locate the <literal>upgrade*.xsl</literal> conversion scripts provided with the source code. These will often be installed in a location such as <literal>/usr/share/pacemaker</literal>, or may be obtained from the <ulink url=\"https://github.com/ClusterLabs/pacemaker/tree/master/xml\">source repository</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the conversion scripts that apply to your older version, for example: <indexterm> <primary>XML</primary><secondary>convert</secondary> </indexterm> <indexterm> <primary>convert</primary> </indexterm>"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# xsltproc /path/to/upgrade06.xsl config06.xml &gt; config10.xml"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Locate the <literal>pacemaker.rng</literal> script (from the same location as the xsl files)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Check the XML validity: <indexterm> <primary>validate configuration</primary> </indexterm><indexterm> <primary>Configuration</primary><secondary>validate XML</secondary> </indexterm> <indexterm> <primary>validate XML</primary> </indexterm>"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "# xmllint --relaxng /path/to/pacemaker.rng config10.xml"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The advantage of this method is that it can be performed without the cluster running, and any validation errors are often more informative."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What Changed in 2.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main goal of the 2.0 release was to remove support for deprecated syntax, along with some small changes in default configuration behavior and tool behavior. Highlights:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Only Corosync version 2 and greater is now supported as the underlying cluster layer. Support for Heartbeat and Corosync 1 (including CMAN) is removed."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Pacemaker detail log file is now stored in /var/log/pacemaker/pacemaker.log by default."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The record-pending cluster property now defaults to true, which allows status tools such as crm_mon to show operations that are in progress."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support for a number of deprecated build options, environment variables, and configuration settings has been removed."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>master</literal> tag has been deprecated in favor of using a <literal>clone</literal> tag with the new <literal>promotable</literal> meta-attribute set to <literal>true</literal>. \"Master/slave\" clone resources are now referred to as \"promotable\" clone resources, though it will take longer for the full terminology change to be completed."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The public API for Pacemaker libraries that software applications can use has changed significantly."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a detailed list of changes, see the release notes and the <ulink url=\"https://wiki.clusterlabs.org/wiki/Pacemaker_2.0_Changes\">Pacemaker 2.0 Changes</ulink> page on the ClusterLabs wiki."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What Changed in 1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "New"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Failure timeouts."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "New section for resource and operation defaults."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Tool for making offline configuration changes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>Rules, instance_attributes, meta_attributes</literal> and sets of operations can be defined once and referenced in multiple places."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The CIB now accepts XPath-based create/modify/delete operations. See the <command>cibadmin</command> help text."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Multi-dimensional colocation and ordering constraints."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The ability to connect to the CIB from non-cluster machines."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Allow recurring actions to be triggered at known times."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changed"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Syntax"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All resource and cluster options now use dashes (-) instead of underscores (_)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>master_slave</literal> was renamed to <literal>master</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>attributes</literal> container tag was removed"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The operation field <literal>pre-req</literal> has been renamed <literal>requires</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All operations must have an <literal>interval</literal>, <literal>start</literal>/<literal>stop</literal> must have it set to zero"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>stonith-enabled</literal> option now defaults to true."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The cluster will refuse to start resources if <literal>stonith-enabled</literal> is true (or unset) and no STONITH resources have been defined"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The attributes of colocation and ordering constraints were renamed for clarity."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>resource-failure-stickiness</literal> has been replaced by <literal>migration-threshold</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The parameters for command-line tools have been made consistent"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Switched to <emphasis>RelaxNG</emphasis> schema validation and <emphasis>libxml2</emphasis> parser"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "id fields are now XML IDs which have the following limitations:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "id’s cannot contain colons (:)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "id’s cannot begin with a number"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "id’s must be globally unique (not just unique for that tag)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Some fields (such as those in constraints that refer to resources) are IDREFs."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that they must reference existing resources or objects in order for the configuration to be valid. Removing an object which is referenced elsewhere will therefore fail."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The CIB representation, from which a MD5 digest is calculated to verify CIBs on the nodes, has changed."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that every CIB update will require a full refresh on any upgraded nodes until the cluster is fully upgraded to 1.0. This will result in significant performance degradation and it is therefore highly inadvisable to run a mixed 1.0/0.6 cluster for any longer than absolutely necessary."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Ping node information no longer needs to be added to <emphasis>ha.cf</emphasis>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simply include the lists of hosts in your ping resource(s)."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Removed"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "It is no longer possible to set resource meta options as top-level attributes. Use meta attributes instead."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resource and operation defaults are no longer read from <literal>crm_config</literal>."
+msgstr ""
+
diff --git a/doc/Clusters_from_Scratch/pot/Preface.pot b/doc/Pacemaker_Administration/pot/Preface.pot
similarity index 78%
copy from doc/Clusters_from_Scratch/pot/Preface.pot
copy to doc/Pacemaker_Administration/pot/Preface.pot
index f84c72b747..44e91d0ec7 100644
--- a/doc/Clusters_from_Scratch/pot/Preface.pot
+++ b/doc/Pacemaker_Administration/pot/Preface.pot
@@ -1,19 +1,19 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Preface"
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Revision_History.pot b/doc/Pacemaker_Administration/pot/Revision_History.pot
similarity index 64%
copy from doc/Pacemaker_Development/pot/Revision_History.pot
copy to doc/Pacemaker_Administration/pot/Revision_History.pot
index 66ca5f9801..4a7d96cce1 100644
--- a/doc/Pacemaker_Development/pot/Revision_History.pot
+++ b/doc/Pacemaker_Administration/pot/Revision_History.pot
@@ -1,39 +1,34 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Revision History"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
#. Tag: member
#, no-c-format
-msgid "Convert coding guidelines and developer FAQ to Publican document"
-msgstr ""
-
-#. Tag: member
-#, no-c-format
-msgid "Add Python coding guidelines, and more about licensing"
+msgid "Move administration-oriented information from Pacemaker Explained into its own book"
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Author_Group.pot b/doc/Pacemaker_Development/pot/Author_Group.pot
index 4c66589225..b5a55a50e4 100644
--- a/doc/Pacemaker_Development/pot/Author_Group.pot
+++ b/doc/Pacemaker_Development/pot/Author_Group.pot
@@ -1,44 +1,44 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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: firstname
#, no-c-format
msgid "Andrew"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Beekhof"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "Red Hat"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Co-author"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Book_Info.pot b/doc/Pacemaker_Development/pot/Book_Info.pot
index c994d01a2f..6ab595ef31 100644
--- a/doc/Pacemaker_Development/pot/Book_Info.pot
+++ b/doc/Pacemaker_Development/pot/Book_Info.pot
@@ -1,29 +1,29 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Pacemaker Development"
msgstr ""
#. Tag: subtitle
#, no-c-format
msgid "Working with the Pacemaker Code Base"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This document has guidelines and tips for developers interested in editing Pacemaker source code and submitting changes for inclusion in the project."
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Ch-Coding.pot b/doc/Pacemaker_Development/pot/Ch-Coding.pot
index d1716d820e..a539502969 100644
--- a/doc/Pacemaker_Development/pot/Ch-Coding.pot
+++ b/doc/Pacemaker_Development/pot/Ch-Coding.pot
@@ -1,276 +1,276 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "C Coding Guidelines"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<anchor id=\"ch-c-coding\" xreflabel=\"Chapter 2, C Coding Guidelines\"></anchor>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "C Boilerplate"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>C</primary><secondary>boilerplate</secondary> </indexterm> <indexterm> <primary>boilerplate</primary> </indexterm> <indexterm> <primary>licensing</primary><secondary>C boilerplate</secondary> </indexterm> <indexterm> <primary>C boilerplate</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Every C file should start like this:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "/*\n"
-" * Copyright (C) &lt;YYYY[-YYYY]&gt; Andrew Beekhof &lt;andrew@beekhof.net&gt;\n"
+" * Copyright &lt;YYYY[-YYYY]&gt; Andrew Beekhof &lt;andrew@beekhof.net&gt;\n"
" *\n"
" * This source code is licensed under &lt;LICENSE&gt; WITHOUT ANY WARRANTY.\n"
" */"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>&lt;YYYY&gt;</literal> is the year the code was <emphasis>originally</emphasis> created (it is the most important date for copyright purposes, as it establishes priority and the point from which expiration is calculated). If the code is modified in later years, add <literal>-YYYY</literal> with the most recent year of modification."
+msgid "<literal>&lt;YYYY&gt;</literal> is the year the code was <emphasis>originally</emphasis> created. <footnote><para> See the U.S. Copyright Office’s <ulink url=\"https://www.copyright.gov/comp3/\">\"Compendium of U.S. Copyright Office Practices\"</ulink>, particularly \"Chapter 2200: Notice of Copyright\", sections 2205.1(A) and 2205.1(F), or <ulink url=\"https://techwhirl.com/updating-copyright-notices/\">\"Updating Copyright Notices\"</ulink> for a more readable summary. </para></footnote> If the code is modified in later years, add <literal>-YYYY</literal> with the most recent year of modification."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>&lt;LICENSE&gt;</literal> should follow the policy set forth in the <ulink url=\"https://github.com/ClusterLabs/pacemaker/blob/master/COPYING\"><literal>COPYING</literal></ulink> file, generally one of \"GNU General Public License version 2 or later (GPLv2+)\" or \"GNU Lesser General Public License version 2.1 or later (LGPLv2.1+)\"."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Formatting"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Whitespace"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>C</primary><secondary>whitespace</secondary> </indexterm> <indexterm> <primary>whitespace</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Indentation must be 4 spaces, no tabs."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do not leave trailing whitespace."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Line Length"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Lines should be no longer than 80 characters unless limiting line length significantly impacts readability."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Pointers"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>C</primary><secondary>pointers</secondary> </indexterm> <indexterm> <primary>pointers</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>*</literal> goes by the variable name, not the type:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "char *foo;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Use a space before the <literal>*</literal> and after the closing parenthesis in a cast:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "char *foo = (char *) bar;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Functions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>C</primary><secondary>functions</secondary> </indexterm> <indexterm> <primary>functions</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the function definition, put the return type on its own line, and place the opening brace by itself on a line:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "static int\n"
"foo(void)\n"
"{"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For functions with enough arguments that they must break to the next line, align arguments with the first argument:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "static int\n"
"function_name(int bar, const char *a, const char *b,\n"
" const char *c, const char *d)\n"
"{"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If a function name gets really long, start the arguments on their own line with 8 spaces of indentation:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "static int\n"
"really_really_long_function_name_this_is_getting_silly_now(\n"
" int bar, const char *a, const char *b,\n"
" const char *c, const char *d)\n"
"{"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Control Statements (if, else, while, for, switch)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The keyword is followed by one space, then left parenthesis without space, condition, right parenthesis, space, opening bracket on the same line. <literal>else</literal> and <literal>else if</literal> are on the same line with the ending brace and opening brace, separated by a space:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "if (condition1) {\n"
" statement1;\n"
"} else if (condition2) {\n"
" statement2;\n"
"} else {\n"
" statement3;\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In a <literal>switch</literal> statement, <literal>case</literal> is indented one level, and the body of each <literal>case</literal> is indented by another level. The opening brace is on the same line as <literal>switch</literal>."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "switch (expression) {\n"
" case 0:\n"
" command1;\n"
" break;\n"
" case 1:\n"
" command2;\n"
" break;\n"
" default:\n"
" command3;\n"
"}"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Operators"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>C</primary><secondary>operators</secondary> </indexterm> <indexterm> <primary>operators</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Operators have spaces from both sides. Do not rely on operator precedence; use parentheses when mixing operators with different priority."
msgstr ""
#. Tag: para
#, no-c-format
msgid "No space is used after opening parenthesis and before closing parenthesis."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "x = a + b - (c * d);"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Naming Conventions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>C</primary><secondary>naming</secondary> </indexterm> <indexterm> <primary>naming</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any exposed symbols in libraries (non-<literal>static</literal> function names, type names, etc.) must begin with a prefix appropriate to the library, for example, <literal>crm_</literal>, <literal>pe_</literal>, <literal>st_</literal>, <literal>lrm_</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "vim Settings"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>vim</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Developers who use <literal>vim</literal> to edit source code can add the following settings to their <literal>~/.vimrc</literal> file to follow Pacemaker C coding guidelines:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "\" follow Pacemaker coding guidelines when editing C source code files\n"
"filetype plugin indent on\n"
"au FileType c setlocal expandtab tabstop=4 softtabstop=4 shiftwidth=4 textwidth=80\n"
"autocmd BufNewFile,BufRead *.h set filetype=c\n"
"let c_space_errors = 1"
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Ch-FAQ.pot b/doc/Pacemaker_Development/pot/Ch-FAQ.pot
index fda0b2f70b..47402a11a5 100644
--- a/doc/Pacemaker_Development/pot/Ch-FAQ.pot
+++ b/doc/Pacemaker_Development/pot/Ch-FAQ.pot
@@ -1,139 +1,139 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Frequently Asked Questions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Who is this document intended for?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Anyone who wishes to read and/or edit the Pacemaker source code. Casual contributors should feel free to read just this FAQ, and consult other sections as needed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Where is the source code for Pacemaker?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>downloads</primary> </indexterm> <indexterm> <primary>source code</primary> </indexterm> <indexterm> <primary>git</primary><secondary>GitHub</secondary> </indexterm> <indexterm> <primary>GitHub</primary> </indexterm> The <ulink url=\"https://github.com/ClusterLabs/pacemaker\">source code for Pacemaker</ulink> is kept on <ulink url=\"https://github.com/\">GitHub</ulink>, as are all software projects under the <ulink url=\"https://github.com/ClusterLabs\">ClusterLabs</ulink> umbrella. Pacemaker uses <ulink url=\"https://git-scm.com/\">Git</ulink> for source code management. If you are a Git newbie, the <ulink url=\"http://schacon.github.io/git/gittutorial.html\">gittutorial(7) man page</ulink> is an excellent starting point. If you’re familiar with using Git from the command line, you can create a local copy of the Pacemaker source code with: <literal>git clone https://github.com/ClusterLabs/pacemaker.git pacemaker</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "What are the different Git branches and repositories used for?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>branches</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <ulink url=\"https://github.com/ClusterLabs/pacemaker/tree/master\">master branch</ulink> is the primary branch used for development."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <ulink url=\"https://github.com/ClusterLabs/pacemaker/tree/1.1\">1.1 branch</ulink> contains the latest official release, and normally does not receive any changes. During the release cycle, it will contain release candidates for the next official release, and will receive only bug fixes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <ulink url=\"https://github.com/ClusterLabs/pacemaker-1.0\">1.0 repository</ulink> is a frozen snapshot of the 1.0 release series, and is no longer developed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Messages will be posted to the <ulink url=\"http://clusterlabs.org/mailman/listinfo/developers\">developers@clusterlabs.org</ulink> mailing list during the release cycle, with instructions about which branches to use when submitting requests."
msgstr ""
#. Tag: para
#, no-c-format
msgid "How do I build from the source code?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "See <ulink url=\"https://github.com/ClusterLabs/pacemaker/blob/master/INSTALL.md\">INSTALL.md</ulink> in the main checkout directory."
msgstr ""
#. Tag: para
#, no-c-format
msgid "What coding style should I follow?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You’ll be mostly fine if you simply follow the example of existing code. When unsure, see the relevant section of this document for language-specific recommendations. Pacemaker has grown and evolved organically over many years, so you will see much code that doesn’t conform to the current guidelines. We discourage making changes solely to bring code into conformance, as any change requires developer time for review and opens the possibility of adding bugs. However, new code should follow the guidelines, and it is fine to bring lines of older code into conformance when modifying that code for other reasons."
msgstr ""
#. Tag: para
#, no-c-format
msgid "How should I format my Git commit messages?"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>git</primary><secondary>commit messages</secondary> </indexterm> <indexterm> <primary>commit messages</primary> </indexterm> See existing examples in the git log. The first line should look like <literal>change-type: affected-code: explanation</literal> where <literal>change-type</literal> can be <literal>Fix</literal> or <literal>Bug</literal> for most bug fixes, <literal>Feature</literal> for new features, <literal>Log</literal> for changes to log messages or handling, <literal>Doc</literal> for changes to documentation or comments, or <literal>Test</literal> for changes in CTS and regression tests. You will sometimes see <literal>Low</literal>, <literal>Med</literal> (or <literal>Mid</literal>) and <literal>High</literal> used instead for bug fixes, to indicate the severity. The important thing is that only commits with <literal>Feature</literal>, <literal>Fix</literal>, <literal>Bug</literal>, or <literal>High</literal> will automatically be included in the change log for the next release. The <literal>affected-code</literal> is the name of the component(s) being changed, for example, <literal>crmd</literal> or <literal>libcrmcommon</literal> (it’s more free-form, so don’t sweat getting it exact). The <literal>explanation</literal> briefly describes the change. The git project recommends the entire summary line stay under 50 characters, but more is fine if needed for clarity. Except for the most simple and obvious of changes, the summary should be followed by a blank line and then a longer explanation of <emphasis>why</emphasis> the change was made."
+msgid "<indexterm> <primary>git</primary><secondary>commit messages</secondary> </indexterm> <indexterm> <primary>commit messages</primary> </indexterm> See existing examples in the git log. The first line should look like <literal>change-type: affected-code: explanation</literal> where <literal>change-type</literal> can be <literal>Fix</literal> or <literal>Bug</literal> for most bug fixes, <literal>Feature</literal> for new features, <literal>Log</literal> for changes to log messages or handling, <literal>Doc</literal> for changes to documentation or comments, or <literal>Test</literal> for changes in CTS and regression tests. You will sometimes see <literal>Low</literal>, <literal>Med</literal> (or <literal>Mid</literal>) and <literal>High</literal> used instead for bug fixes, to indicate the severity. The important thing is that only commits with <literal>Feature</literal>, <literal>Fix</literal>, <literal>Bug</literal>, or <literal>High</literal> will automatically be included in the change log for the next release. The <literal>affected-code</literal> is the name of the component(s) being changed, for example, <literal>pacemaker-controld</literal> or <literal>libcrmcommon</literal> (it’s more free-form, so don’t sweat getting it exact). The <literal>explanation</literal> briefly describes the change. The git project recommends the entire summary line stay under 50 characters, but more is fine if needed for clarity. Except for the most simple and obvious of changes, the summary should be followed by a blank line and then a longer explanation of <emphasis>why</emphasis> the change was made."
msgstr ""
#. Tag: para
#, no-c-format
msgid "How can I test my changes?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Most importantly, Pacemaker has regression tests for most major components; these will automatically be run for any pull requests submitted through GitHub. Additionally, Pacemaker’s Cluster Test Suite (CTS) can be used to set up a test cluster and run a wide variety of complex tests. This document will have more detail on testing in the future."
msgstr ""
#. Tag: para
#, no-c-format
msgid "What is Pacemaker’s license?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>licensing</primary> </indexterm> Except where noted otherwise in the file itself, the source code for all Pacemaker programs is licensed under version 2 or later of the GNU General Public License (<ulink url=\"https://www.gnu.org/licenses/gpl-2.0.html\">GPLv2+</ulink>), its headers and libraries under version 2.1 or later of the less restrictive GNU Lesser General Public License (<ulink url=\"https://www.gnu.org/licenses/lgpl-2.1.html\">LGPLv2.1+</ulink>), its documentation under version 4.0 or later of the Creative Commons Attribution-ShareAlike International Public License (<ulink url=\"https://creativecommons.org/licenses/by-sa/4.0/legalcode\">CC-BY-SA</ulink>), and its init scripts under the <ulink url=\"https://opensource.org/licenses/BSD-3-Clause\">Revised BSD</ulink> license. If you find any deviations from this policy, or wish to inquire about alternate licensing arrangements, please e-mail <ulink url=\"mailto:andrew@beekhof.net\">andrew@beekhof.net</ulink>. Licensing issues are also discussed on the <ulink url=\"http://clusterlabs.org/wiki/License\">ClusterLabs wiki</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "How can I contribute my changes to the project?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Contributions of bug fixes or new features are very much appreciated! Patches can be submitted as <ulink url=\"https://help.github.com/articles/using-pull-requests/\">pull requests</ulink> via GitHub (the preferred method, due to its excellent <ulink url=\"https://github.com/features/\">features</ulink>), or e-mailed to the <ulink url=\"http://clusterlabs.org/mailman/listinfo/developers\">developers@clusterlabs.org</ulink> mailing list as an attachment in a format Git can import."
msgstr ""
#. Tag: para
#, no-c-format
msgid "What if I still have questions?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>mailing lists</primary> </indexterm> Ask on the <ulink url=\"http://clusterlabs.org/mailman/listinfo/developers\">developers@clusterlabs.org</ulink> mailing list for development-related questions, or on the <ulink url=\"http://clusterlabs.org/mailman/listinfo/users\">users@clusterlabs.org</ulink> mailing list for general questions about using Pacemaker. Developers often also hang out on <ulink url=\"http://freenode.net/\">freenode’s</ulink> #clusterlabs IRC channel."
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Ch-Python.pot b/doc/Pacemaker_Development/pot/Ch-Python.pot
index 6d40d89b9b..ed71331cef 100644
--- a/doc/Pacemaker_Development/pot/Ch-Python.pot
+++ b/doc/Pacemaker_Development/pot/Ch-Python.pot
@@ -1,297 +1,296 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Python Coding Guidelines"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<anchor id=\"ch-python-coding\" xreflabel=\"Chapter 3, Python Coding Guidelines\"></anchor>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Python Boilerplate"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Python</primary><secondary>boilerplate</secondary> </indexterm> <indexterm> <primary>boilerplate</primary> </indexterm> <indexterm> <primary>licensing</primary><secondary>Python boilerplate</secondary> </indexterm> <indexterm> <primary>Python boilerplate</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Every Python file should start like this:"
+msgid "If a Python file is meant to be executed (as opposed to imported), it should have a <literal>.in</literal> extension, and its first line should be:"
+msgstr ""
+
+#. Tag: screen
+#, no-c-format
+msgid "#!@PYTHON@"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "which will be replaced with the appropriate python executable when Pacemaker is built. To make that happen, add an AC_CONFIG_FILES() line to configure.ac, and add the file name without .in to .gitignore (see existing examples)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After the above line if any, every Python file should start like this:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "[&lt;SHEBANG&gt;]\n"
-"\"\"\" &lt;BRIEF-DESCRIPTION&gt;\n"
+msgid "\"\"\" &lt;BRIEF-DESCRIPTION&gt;\n"
"\"\"\"\n"
"\n"
-"# Pacemaker targets compatibility with Python 2.6+ and 3.2+\n"
+"# Pacemaker targets compatibility with Python 2.7 and 3.2+\n"
"from __future__ import print_function, unicode_literals, absolute_import, division\n"
"\n"
-"__copyright__ = \"Copyright (C) &lt;YYYY[-YYYY]&gt; Andrew Beekhof &lt;andrew@beekhof.net&gt;\"\n"
+"__copyright__ = \"Copyright &lt;YYYY[-YYYY]&gt; Andrew Beekhof &lt;andrew@beekhof.net&gt;\"\n"
"__license__ = \"&lt;LICENSE&gt; WITHOUT ANY WARRANTY\""
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the file is meant to be directly executed, the first line (<literal>&lt;SHEBANG&gt;</literal>) should be <literal>#!/usr/bin/python</literal>. If it is meant to be imported, omit this line."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>&lt;BRIEF-DESCRIPTION&gt;</literal> is obviously a brief description of the file’s purpose. The string may contain any other information typically used in a Python file <ulink url=\"https://www.python.org/dev/peps/pep-0257/\">docstring</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>import</literal> statement is discussed further in <xref linkend=\"s-python-future-imports\" />."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>&lt;YYYY&gt;</literal> is the year the code was <emphasis>originally</emphasis> created (it is the most important date for copyright purposes, as it establishes priority and the point from which expiration is calculated). If the code is modified in later years, add <literal>-YYYY</literal> with the most recent year of modification."
+msgid "<literal>&lt;YYYY&gt;</literal> is the year the code was <emphasis>originally</emphasis> created. <footnote><para> See the U.S. Copyright Office’s <ulink url=\"https://www.copyright.gov/comp3/\">\"Compendium of U.S. Copyright Office Practices\"</ulink>, particularly \"Chapter 2200: Notice of Copyright\", sections 2205.1(A) and 2205.1(F), or <ulink url=\"https://techwhirl.com/updating-copyright-notices/\">\"Updating Copyright Notices\"</ulink> for a more readable summary. </para></footnote> If the code is modified in later years, add <literal>-YYYY</literal> with the most recent year of modification."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>&lt;LICENSE&gt;</literal> should follow the policy set forth in the <ulink url=\"https://github.com/ClusterLabs/pacemaker/blob/master/COPYING\"><literal>COPYING</literal></ulink> file, generally one of \"GNU General Public License version 2 or later (GPLv2+)\" or \"GNU Lesser General Public License version 2.1 or later (LGPLv2.1+)\"."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Python Compatibility"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Python</primary><secondary>2</secondary> </indexterm> <indexterm> <primary>2</primary> </indexterm> <indexterm> <primary>Python</primary><secondary>3</secondary> </indexterm> <indexterm> <primary>3</primary> </indexterm> <indexterm> <primary>Python</primary><secondary>versions</secondary> </indexterm> <indexterm> <primary>versions</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker targets compatibility with Python 2.6 and later, and Python 3.2 and later. These versions have added features to be more compatible with each other, allowing us to support both the 2 and 3 series with the same code. It is a good idea to test any changes with both Python 2 and 3."
+msgid "Pacemaker targets compatibility with Python 2.7, and Python 3.2 and later. These versions have added features to be more compatible with each other, allowing us to support both the 2 and 3 series with the same code. It is a good idea to test any changes with both Python 2 and 3."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Python Future Imports"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The future imports used in <xref linkend=\"s-python-boilerplate\" /> mean:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "All print statements must use parentheses, and printing without a newline is accomplished with the <literal>end=' '</literal> parameter rather than a trailing comma."
msgstr ""
#. Tag: para
#, no-c-format
msgid "All string literals will be treated as Unicode (the <literal>u</literal> prefix is unnecessary, and must not be used, because it is not available in Python 3.2)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Local modules must be imported using <literal>from . import</literal> (rather than just <literal>import</literal>). To import one item from a local module, use <literal>from .modulename import</literal> (rather than <literal>from modulename import</literal>)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Division using <literal>/</literal> will always return a floating-point result (use <literal>//</literal> if you want the integer floor instead)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Other Python Compatibility Requirements"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When specifying an exception variable, always use <literal>as</literal> instead of a comma (e.g. <literal>except Exception as e</literal> or <literal>except (TypeError, IOError) as e</literal>). Use <literal>e.args</literal> to access the error arguments (instead of iterating over or subscripting <literal>e</literal>)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Use <literal>in</literal> (not <literal>has_key()</literal>) to determine if a dictionary has a particular key."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Always use the I/O functions from the <literal>io</literal> module rather than the native I/O functions (e.g. <literal>io.open()</literal> rather than <literal>open()</literal>)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When opening a file, always use the <literal>t</literal> (text) or <literal>b</literal> (binary) mode flag."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When creating classes, always specify a parent class to ensure that it is a \"new-style\" class (e.g. <literal>class Foo(object):</literal> rather than <literal>class Foo:</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Be aware of the bytes type added in Python 3. Many places where strings are used in Python 2 use bytes or bytearrays in Python 3 (for example, the pipes used with <literal>subprocess.Popen()</literal>). Code should handle both possibilities."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Be aware that the <literal>items()</literal>, <literal>keys()</literal>, and <literal>values()</literal> methods of dictionaries return lists in Python 2 and views in Python 3. In many case, no special handling is required, but if the code needs to use list methods on the result, cast the result to list first."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Do not name variables <literal>with</literal> or <literal>as</literal>."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "Do not raise or catch strings as exceptions (e.g. <literal>raise \"Bad thing\"</literal>)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do not use the <literal>cmp</literal> parameter of sorting functions (use <literal>key</literal> instead, if needed) or the <literal>__cmp__()</literal> method of classes (implement rich comparison methods such as <literal>__lt__()</literal> instead, if needed)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do not use the <literal>buffer</literal> type."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do not use features not available in all targeted Python versions. Common examples include:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The <literal>argparse</literal>, <literal>html</literal>, <literal>ipaddress</literal>, <literal>sysconfig</literal>, and <literal>UserDict</literal> modules"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The <literal>collections.OrderedDict</literal> class"
+msgid "The <literal>html</literal>, <literal>ipaddress</literal>, and <literal>UserDict</literal> modules"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>subprocess.run()</literal> function"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>subprocess.DEVNULL</literal> constant"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>subprocess</literal> module-specific exceptions"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Set literals (<literal>{1, 2, 3}</literal>)"
-msgstr ""
-
#. Tag: title
#, no-c-format
msgid "Python Usages to Avoid"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Avoid the following if possible, otherwise research the compatibility issues involved (hacky workarounds are often available):"
msgstr ""
#. Tag: para
#, no-c-format
msgid "long integers"
msgstr ""
#. Tag: para
#, no-c-format
msgid "octal integer literals"
msgstr ""
#. Tag: para
#, no-c-format
msgid "mixed binary and string data in one data file or variable"
msgstr ""
#. Tag: para
#, no-c-format
msgid "metaclasses"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>locale.strcoll</literal> and <literal>locale.strxfrm</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "the <literal>configparser</literal> and <literal>ConfigParser</literal> modules"
msgstr ""
#. Tag: para
#, no-c-format
msgid "importing compatibility modules such as <literal>six</literal> (so we don’t have to add them to Pacemaker’s dependencies)"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Formatting Python Code"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Python</primary><secondary>formatting</secondary> </indexterm> <indexterm> <primary>formatting</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Indentation must be 4 spaces, no tabs."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do not leave trailing whitespace."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Lines should be no longer than 80 characters unless limiting line length significantly impacts readability. For Python, this limitation is flexible since breaking a line often impacts readability, but definitely keep it under 120 characters."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Where not conflicting with this style guide, it is recommended (but not required) to follow <ulink url=\"https://www.python.org/dev/peps/pep-0008/:\">PEP 8</ulink>."
+msgid "Where not conflicting with this style guide, it is recommended (but not required) to follow <ulink url=\"https://www.python.org/dev/peps/pep-0008/\">PEP 8</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is recommended (but not required) to format Python code such that <literal>pylint --disable=line-too-long,too-many-lines,too-many-instance-attributes,too-many-arguments,too-many-statements</literal> produces minimal complaints (even better if you don’t need to disable all those checks)."
msgstr ""
diff --git a/doc/Pacemaker_Development/pot/Revision_History.pot b/doc/Pacemaker_Development/pot/Revision_History.pot
index 66ca5f9801..81e2cdc373 100644
--- a/doc/Pacemaker_Development/pot/Revision_History.pot
+++ b/doc/Pacemaker_Development/pot/Revision_History.pot
@@ -1,39 +1,44 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Revision History"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Convert coding guidelines and developer FAQ to Publican document"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Add Python coding guidelines, and more about licensing"
msgstr ""
+#. Tag: member
+#, no-c-format
+msgid "Drop support for Python 2.6"
+msgstr ""
+
diff --git a/doc/Pacemaker_Explained/pot/Ap-FAQ.pot b/doc/Pacemaker_Explained/pot/Ap-FAQ.pot
index caf2881461..96cb58ddc7 100644
--- a/doc/Pacemaker_Explained/pot/Ap-FAQ.pot
+++ b/doc/Pacemaker_Explained/pot/Ap-FAQ.pot
@@ -1,124 +1,94 @@
#
# 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"
+"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 "FAQ"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Why is the Project Called Pacemaker?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Pacemaker</primary> </indexterm> First of all, the reason it’s not called the CRM is because of the abundance of terms <footnote><para><ulink url=\"http://en.wikipedia.org/wiki/CRM\">http://en.wikipedia.org/wiki/CRM</ulink></para></footnote> that are commonly abbreviated to those three letters. The Pacemaker name came from Kham, <footnote><para><ulink url=\"http://khamsouk.souvanlasy.com/\">http://khamsouk.souvanlasy.com/</ulink></para></footnote> a good friend of Pacemaker developer Andrew Beekhof’s, and was originally used by a Java GUI that Beekhof was prototyping in early 2007. Alas, other commitments prevented the GUI from progressing much and, when it came time to choose a name for this project, Lars Marowsky-Bree suggested it was an even better fit for an independent CRM. The idea stems from the analogy between the role of this software and that of the little device that keeps the human heart pumping. Pacemaker monitors the cluster and intervenes when necessary to ensure the smooth operation of the services it provides. There were a number of other names (and acronyms) tossed around, but suffice to say \"Pacemaker\" was the best."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Why was the Pacemaker Project Created?"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The decision was made to spin-off the CRM into its own project after the 2.1.3 Heartbeat release in order to:"
+msgid "Pacemaker was spun off from an earlier project called <ulink url=\"http://linux-ha.org/\">Heartbeat</ulink>, which combined a cluster layer and a cluster resource manager. The CRM was made into its own project, Pacemaker, in order to:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "support both the Corosync and Heartbeat cluster stacks equally"
+msgid "support both the Corosync and Heartbeat cluster stacks equally (Heartbeat support was dropped in Pacemaker 2.0, as the project had faded out by then)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "decouple the release cycles of two projects at very different stages of their life-cycles"
+msgid "decouple the release cycles of the cluster layer and the cluster resource manager at very different stages of their life-cycles"
msgstr ""
#. Tag: para
#, no-c-format
msgid "foster clearer package boundaries, thus leading to better and more stable interfaces"
msgstr ""
#. Tag: para
#, no-c-format
msgid "What Messaging Layers are Supported?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Messaging Layers</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<ulink url=\"http://www.corosync.org/\">Corosync</ulink>"
+msgid "<ulink url=\"http://www.corosync.org/\">Corosync</ulink> version 2 and greater"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<ulink url=\"http://linux-ha.org/\">Heartbeat</ulink>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Can I Choose Which Messaging Layer to Use at Run Time?"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Yes. The CRM will automatically detect which started it and behave accordingly."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Can I Have a Mixed Heartbeat-Corosync Cluster?"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "No."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<anchor id=\"q-messaging-layer\" xreflabel=\"[q-messaging-layer]\"></anchor> Which Messaging Layer Should I Choose?"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Cluster</primary><secondary>Choosing Between Heartbeat and Corosync</secondary> </indexterm> <indexterm> <primary>Choosing Between Heartbeat and Corosync</primary> </indexterm> <indexterm> <primary>Cluster Stack</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm> <indexterm> <primary>Cluster Stack</primary><secondary>Heartbeat</secondary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm> You can choose from multiple messaging layers, including heartbeat, corosync 1 (with or without CMAN), and corosync 2. Corosync 2 is the current state of the art due to its more advanced features and better support for pacemaker, but often the best choice is to use whatever comes with your Linux distribution, and follow the distribution’s setup instructions."
+msgid "Historically, Pacemaker 1 also supported Corosync version 1 (with either CMAN or a pacemaker plugin) and Heartbeat. Support for these legacy stacks was dropped with Pacemaker 2.0."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Where Can I Get Pre-built Packages?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Most major Linux distributions have pacemaker packages in their standard package repositories. See the <ulink url=\"http://clusterlabs.org/wiki/Install\">Install wiki page</ulink> for details."
msgstr ""
#. Tag: para
#, no-c-format
msgid "What Versions of Pacemaker Are Supported?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some Linux distributions (such as Red Hat Enterprise Linux and SUSE Linux Enterprise) offer technical support for their customers; contact them for details of such support. For help within the community (mailing lists, IRC, etc.) from Pacemaker developers and users, refer to the <ulink url=\"http://clusterlabs.org/wiki/Releases\">Releases wiki page</ulink> for an up-to-date list of versions considered to be supported by the project. When seeking assistance, please try to ensure you have one of these versions."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ap-Samples.pot b/doc/Pacemaker_Explained/pot/Ap-Samples.pot
index c2f128751a..fc10785fdc 100644
--- a/doc/Pacemaker_Explained/pot/Ap-Samples.pot
+++ b/doc/Pacemaker_Explained/pot/Ap-Samples.pot
@@ -1,184 +1,184 @@
#
# 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"
+"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 "Sample Configurations"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Empty"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An Empty Configuration"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\"&gt;\n"
" &lt;configuration&gt;\n"
" &lt;crm_config/&gt;\n"
" &lt;nodes/&gt;\n"
" &lt;resources/&gt;\n"
" &lt;constraints/&gt;\n"
" &lt;/configuration&gt;\n"
" &lt;status/&gt;\n"
"&lt;/cib&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Simple"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A simple configuration with two nodes, some cluster options and a resource"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\"&gt;\n"
" &lt;configuration&gt;\n"
" &lt;crm_config&gt;\n"
" &lt;cluster_property_set id=\"cib-bootstrap-options\"&gt;\n"
" &lt;nvpair id=\"option-1\" name=\"symmetric-cluster\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"option-2\" name=\"no-quorum-policy\" value=\"stop\"/&gt;\n"
" &lt;nvpair id=\"option-3\" name=\"stonith-enabled\" value=\"0\"/&gt;\n"
" &lt;/cluster_property_set&gt;\n"
" &lt;/crm_config&gt;\n"
" &lt;nodes&gt;\n"
" &lt;node id=\"xxx\" uname=\"c001n01\" type=\"normal\"/&gt;\n"
" &lt;node id=\"yyy\" uname=\"c001n02\" type=\"normal\"/&gt;\n"
" &lt;/nodes&gt;\n"
" &lt;resources&gt;\n"
" &lt;primitive id=\"myAddr\" class=\"ocf\" provider=\"heartbeat\" type=\"IPaddr\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"myAddr-monitor\" name=\"monitor\" interval=\"300s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"myAddr-params\"&gt;\n"
" &lt;nvpair id=\"myAddr-ip\" name=\"ip\" value=\"192.0.2.10\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;/resources&gt;\n"
" &lt;constraints&gt;\n"
" &lt;rsc_location id=\"myAddr-prefer\" rsc=\"myAddr\" node=\"c001n01\" score=\"INFINITY\"/&gt;\n"
" &lt;/constraints&gt;\n"
" &lt;rsc_defaults&gt;\n"
" &lt;meta_attributes id=\"rsc_defaults-options\"&gt;\n"
" &lt;nvpair id=\"rsc-default-1\" name=\"resource-stickiness\" value=\"100\"/&gt;\n"
" &lt;nvpair id=\"rsc-default-2\" name=\"migration-threshold\" value=\"10\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/rsc_defaults&gt;\n"
" &lt;op_defaults&gt;\n"
" &lt;meta_attributes id=\"op_defaults-options\"&gt;\n"
" &lt;nvpair id=\"op-default-1\" name=\"timeout\" value=\"30s\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/op_defaults&gt;\n"
" &lt;/configuration&gt;\n"
" &lt;status/&gt;\n"
"&lt;/cib&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the above example, we have one resource (an IP address) that we check every five minutes and will run on host <literal>c001n01</literal> until either the resource fails 10 times or the host shuts down."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advanced Configuration"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An advanced configuration with groups, clones and STONITH"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\"&gt;\n"
" &lt;configuration&gt;\n"
" &lt;crm_config&gt;\n"
" &lt;cluster_property_set id=\"cib-bootstrap-options\"&gt;\n"
" &lt;nvpair id=\"option-1\" name=\"symmetric-cluster\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"option-2\" name=\"no-quorum-policy\" value=\"stop\"/&gt;\n"
" &lt;nvpair id=\"option-3\" name=\"stonith-enabled\" value=\"true\"/&gt;\n"
" &lt;/cluster_property_set&gt;\n"
" &lt;/crm_config&gt;\n"
" &lt;nodes&gt;\n"
" &lt;node id=\"xxx\" uname=\"c001n01\" type=\"normal\"/&gt;\n"
" &lt;node id=\"yyy\" uname=\"c001n02\" type=\"normal\"/&gt;\n"
" &lt;node id=\"zzz\" uname=\"c001n03\" type=\"normal\"/&gt;\n"
" &lt;/nodes&gt;\n"
" &lt;resources&gt;\n"
" &lt;primitive id=\"myAddr\" class=\"ocf\" provider=\"heartbeat\" type=\"IPaddr\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"myAddr-monitor\" name=\"monitor\" interval=\"300s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"myAddr-attrs\"&gt;\n"
" &lt;nvpair id=\"myAddr-attr-1\" name=\"ip\" value=\"192.0.2.10\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;group id=\"myGroup\"&gt;\n"
" &lt;primitive id=\"database\" class=\"lsb\" type=\"oracle\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"database-monitor\" name=\"monitor\" interval=\"300s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive id=\"webserver\" class=\"lsb\" type=\"apache\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"webserver-monitor\" name=\"monitor\" interval=\"300s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;/group&gt;\n"
" &lt;clone id=\"STONITH\"&gt;\n"
" &lt;meta_attributes id=\"stonith-options\"&gt;\n"
" &lt;nvpair id=\"stonith-option-1\" name=\"globally-unique\" value=\"false\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;primitive id=\"stonithclone\" class=\"stonith\" type=\"external/ssh\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"stonith-op-mon\" name=\"monitor\" interval=\"5s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"stonith-attrs\"&gt;\n"
" &lt;nvpair id=\"stonith-attr-1\" name=\"hostlist\" value=\"c001n01,c001n02\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;/clone&gt;\n"
" &lt;/resources&gt;\n"
" &lt;constraints&gt;\n"
" &lt;rsc_location id=\"myAddr-prefer\" rsc=\"myAddr\" node=\"c001n01\"\n"
" score=\"INFINITY\"/&gt;\n"
" &lt;rsc_colocation id=\"group-with-ip\" rsc=\"myGroup\" with-rsc=\"myAddr\"\n"
" score=\"INFINITY\"/&gt;\n"
" &lt;/constraints&gt;\n"
" &lt;op_defaults&gt;\n"
" &lt;meta_attributes id=\"op_defaults-options\"&gt;\n"
" &lt;nvpair id=\"op-default-1\" name=\"timeout\" value=\"30s\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/op_defaults&gt;\n"
" &lt;rsc_defaults&gt;\n"
" &lt;meta_attributes id=\"rsc_defaults-options\"&gt;\n"
" &lt;nvpair id=\"rsc-default-1\" name=\"resource-stickiness\" value=\"100\"/&gt;\n"
" &lt;nvpair id=\"rsc-default-2\" name=\"migration-threshold\" value=\"10\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/rsc_defaults&gt;\n"
" &lt;/configuration&gt;\n"
" &lt;status/&gt;\n"
"&lt;/cib&gt;"
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Author_Group.pot b/doc/Pacemaker_Explained/pot/Author_Group.pot
index 22b49850dc..67679820a5 100644
--- a/doc/Pacemaker_Explained/pot/Author_Group.pot
+++ b/doc/Pacemaker_Explained/pot/Author_Group.pot
@@ -1,139 +1,124 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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: firstname
#, no-c-format
msgid "Andrew"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Beekhof"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "Red Hat"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Primary author"
msgstr ""
-#. Tag: firstname
-#, no-c-format
-msgid "Dan"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "Frîncu"
-msgstr ""
-
-#. Tag: contrib
-#, no-c-format
-msgid "Romanian translation"
-msgstr ""
-
#. Tag: firstname
#, no-c-format
msgid "Philipp"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Marek"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "LINBit"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Style and formatting updates. Indexing."
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Tanja"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Roth"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "SUSE"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Utilization chapter"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Resource Templates chapter"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Multi-Site Clusters chapter"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Lars"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Marowsky-Bree"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Yan"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gao"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Thomas"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Schraitle"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Dejan"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Muhamedagic"
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Book_Info.pot b/doc/Pacemaker_Explained/pot/Book_Info.pot
index 775016e5af..28164ac30e 100644
--- a/doc/Pacemaker_Explained/pot/Book_Info.pot
+++ b/doc/Pacemaker_Explained/pot/Book_Info.pot
@@ -1,34 +1,34 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Configuration Explained"
msgstr ""
#. Tag: subtitle
#, no-c-format
msgid "An A-Z guide to Pacemaker's Configuration Options"
msgstr ""
#. Tag: productname
#, no-c-format
msgid "Pacemaker"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this, it will focus exclusively on the XML syntax used to configure Pacemaker's Cluster Information Base (CIB)."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot
index ee3f283356..8dc7e1bec7 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot
@@ -1,1198 +1,976 @@
#
# 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"
+"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 "Advanced Configuration"
msgstr ""
-#. Tag: title
-#, no-c-format
-msgid "Connecting from a Remote Machine"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Cluster</primary><secondary>Remote connection</secondary> </indexterm> <indexterm> <primary>Remote connection</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Remote administration</secondary> </indexterm> <indexterm> <primary>Remote administration</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Provided Pacemaker is installed on a machine, it is possible to connect to the cluster even if the machine itself is not in the same cluster. To do this, one simply sets up a number of environment variables and runs the same commands as when working on a cluster node."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Environment Variables Used to Connect to Remote Instances of the CIB"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "Environment Variable"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "Default"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "Description"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>CIB_user</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "$USER"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The user to connect as. Needs to be part of the <literal>haclient</literal> group on the target host. <indexterm> <primary>Environment Variable</primary><secondary>CIB_user</secondary> </indexterm> <indexterm> <primary>CIB_user</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>CIB_passwd</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The user’s password. Read from the command line if unset. <indexterm> <primary>Environment Variable</primary><secondary>CIB_passwd</secondary> </indexterm> <indexterm> <primary>CIB_passwd</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>CIB_server</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "localhost"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The host to contact <indexterm> <primary>Environment Variable</primary><secondary>CIB_server</secondary> </indexterm> <indexterm> <primary>CIB_server</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>CIB_port</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The port on which to contact the server; required. <indexterm> <primary>Environment Variable</primary><secondary>CIB_port</secondary> </indexterm> <indexterm> <primary>CIB_port</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>CIB_encrypted</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "TRUE"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Whether to encrypt network traffic <indexterm> <primary>Environment Variable</primary><secondary>CIB_encrypted</secondary> </indexterm> <indexterm> <primary>CIB_encrypted</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "So, if <emphasis role=\"strong\">c001n01</emphasis> is an active cluster node and is listening on port 1234 for connections, and <emphasis role=\"strong\">someuser</emphasis> is a member of the <emphasis role=\"strong\">haclient</emphasis> group, then the following would prompt for <emphasis role=\"strong\">someuser</emphasis>'s password and return the cluster’s current configuration:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someuser;\n"
-"# cibadmin -Q"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For security reasons, the cluster does not listen for remote connections by default. If you wish to allow remote access, you need to set the <literal>remote-tls-port</literal> (encrypted) or <literal>remote-clear-port</literal> (unencrypted) CIB properties (i.e., those kept in the <literal>cib</literal> tag, like <literal>num_updates</literal> and <literal>epoch</literal>)."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Extra top-level CIB properties for remote access"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "Field"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>remote-tls-port</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>none</emphasis>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Listen for encrypted remote connections on this port. <indexterm> <primary>remote-tls-port</primary><secondary>Remote Connection Option</secondary> </indexterm> <indexterm> <primary>Remote Connection Option</primary> </indexterm> <indexterm> <primary>Remote Connection</primary><secondary>Option</secondary><tertiary>remote-tls-port</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>remote-tls-port</secondary> </indexterm> <indexterm> <primary>remote-tls-port</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>remote-clear-port</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Listen for plaintext remote connections on this port. <indexterm> <primary>remote-clear-port</primary><secondary>Remote Connection Option</secondary> </indexterm> <indexterm> <primary>Remote Connection Option</primary> </indexterm> <indexterm> <primary>Remote Connection</primary><secondary>Option</secondary><tertiary>remote-clear-port</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>remote-clear-port</secondary> </indexterm> <indexterm> <primary>remote-clear-port</primary> </indexterm>"
-msgstr ""
-
#. Tag: title
#, no-c-format
msgid "Specifying When Recurring Actions are Performed"
msgstr ""
#. Tag: para
#, no-c-format
msgid "By default, recurring actions are scheduled relative to when the resource started. So if your resource was last started at 14:32 and you have a backup set to be performed every 24 hours, then the backup will always run in the middle of the business day — hardly desirable."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To specify a date and time that the operation should be relative to, set the operation’s <literal>interval-origin</literal>. The cluster uses this point to calculate the correct <literal>start-delay</literal> such that the operation will occur at <emphasis>origin + (interval * N)</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "So, if the operation’s interval is 24h, its interval-origin is set to 02:00 and it is currently 14:32, then the cluster would initiate the operation with a start delay of 11 hours and 28 minutes. If the resource is moved to another node before 2am, then the operation is cancelled."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The value specified for <literal>interval</literal> and <literal>interval-origin</literal> can be any date/time conforming to the <ulink url=\"http://en.wikipedia.org/wiki/ISO_8601\">ISO8601 standard</ulink>. By way of example, to specify an operation that would run on the first Monday of 2009 and every Monday after that, you would add:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Specifying a Base for Recurring Action Intervals"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;op id=\"my-weekly-action\" name=\"custom-action\" interval=\"P7D\" interval-origin=\"2009-W01-1\"/&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Handling Resource Failure"
msgstr ""
#. Tag: para
#, no-c-format
msgid "By default, Pacemaker will attempt to recover failed resources by restarting them. However, failure recovery is highly configurable."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Failure Counts"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker tracks resource failures for each combination of node, resource, and operation (start, stop, monitor, etc.)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can query the fail count for a particular node, resource, and/or operation using the <literal>crm_failcount</literal> command. For example, to see how many times the 10-second monitor for <literal>myrsc</literal> has failed on <literal>node1</literal>, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_failcount --query -r myrsc -N node1 -n monitor -I 10s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you omit the node, <literal>crm_failcount</literal> will use the local node. If you omit the operation and interval, <literal>crm_failcount</literal> will display the sum of the fail counts for all operations on the resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can use <literal>crm_resource --cleanup</literal> or <literal>crm_failcount --delete</literal> to clear fail counts. For example, to clear the above monitor failures, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --cleanup -r myrsc -N node1 -n monitor -I 10s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you omit the resource, <literal>crm_resource --cleanup</literal> will clear failures for all resources. If you omit the node, it will clear failures on all nodes. If you omit the operation and interval, it will clear the failures for all operations on the resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Even when cleaning up only a single operation, all failed operations will disappear from the status display. This allows us to trigger a re-check of the resource’s current status."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Higher-level tools may provide other commands for querying and clearing fail counts."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>crm_mon</literal> tool shows the current cluster status, including any failed operations. To see the current fail counts for any failed resources, call <literal>crm_mon</literal> with the <literal>--failcounts</literal> option. This shows the fail counts per resource (that is, the sum of any operation fail counts for the resource)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Failure Response"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Normally, if a running resource fails, pacemaker will try to stop it and start it again. Pacemaker will choose the best location to start it each time, which may be the same node that it failed on."
msgstr ""
#. Tag: para
#, no-c-format
msgid "However, if a resource fails repeatedly, it is possible that there is an underlying problem on that node, and you might desire trying a different node in such a case. Pacemaker allows you to set your preference via the <literal>migration-threshold</literal> resource meta-attribute. <footnote><para> The naming of this option was perhaps unfortunate as it is easily confused with live migration, the process of moving a resource from one node to another without stopping it. Xen virtual guests are the most common example of resources that can be migrated in this manner. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you define <literal>migration-threshold=<replaceable>N</replaceable></literal> for a resource, it will be banned from the original node after <emphasis>N</emphasis> failures."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>migration-threshold</literal> is per <emphasis>resource</emphasis>, even though fail counts are tracked per <emphasis>operation</emphasis>. The operation fail counts are added together to compare against the <literal>migration-threshold</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "By default, fail counts remain until manually cleared by an administrator using <literal>crm_resource --cleanup</literal> or <literal>crm_failcount --delete</literal> (hopefully after first fixing the failure’s cause). It is possible to have fail counts expire automatically by setting the <literal>failure-timeout</literal> resource meta-attribute."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A successful operation does not clear past failures. If a recurring monitor operation fails once, succeeds many times, then fails again days later, its fail count is 2. Fail counts are cleared only by manual intervention or falure timeout."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, a setting of <literal>migration-threshold=2</literal> and <literal>failure-timeout=60s</literal> would cause the resource to move to a new node after 2 failures, and allow it to move back (depending on stickiness and constraint scores) after one minute."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>failure-timeout</literal> is measured since the most recent failure. That is, older failures do not individually time out and lower the fail count. Instead, all failures are timed out simultaneously (and the fail count is reset to 0) if there is no new failure for the timeout period."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are two exceptions to the migration threshold concept: when a resource either fails to start or fails to stop."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the cluster property <literal>start-failure-is-fatal</literal> is set to <literal>true</literal> (which is the default), start failures cause the fail count to be set to <literal>INFINITY</literal> and thus always cause the resource to move immediately."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Stop failures are slightly different and crucial. If a resource fails to stop and STONITH is enabled, then the cluster will fence the node in order to be able to start the resource elsewhere. If STONITH is not enabled, then the cluster has no way to continue and will not try to start the resource elsewhere, but will try to stop it again after the failure timeout."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Please read <xref linkend=\"s-rules-recheck\" /> to understand how timeouts work before configuring a <literal>failure-timeout</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Moving Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Moving</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Moving</secondary> </indexterm> <indexterm> <primary>Moving</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Moving Resources Manually"
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are primarily two occasions when you would want to move a resource from its current location: when the whole node is under maintenance, and when a single resource needs to be moved."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Standby Mode"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Since everything eventually comes down to a score, you could create constraints for every resource to prevent them from running on one node. While pacemaker configuration can seem convoluted at times, not even we would require this of administrators."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Instead, one can set a special node attribute which tells the cluster \"don’t let anything run here\". There is even a helpful tool to help query and set it, called <literal>crm_standby</literal>. To check the standby status of the current machine, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_standby -G"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A value of <literal>on</literal> indicates that the node is <emphasis>not</emphasis> able to host any resources, while a value of <literal>off</literal> says that it <emphasis>can</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can also check the status of other nodes in the cluster by specifying the <literal>--node</literal> option:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_standby -G --node sles-2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To change the current node’s standby status, use <literal>-v</literal> instead of <literal>-G</literal>:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_standby -v on"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Again, you can change another host’s value by supplying a hostname with <literal>--node</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Moving One Resource"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When only one resource is required to move, we could do this by creating location constraints. However, once again we provide a user-friendly shortcut as part of the <literal>crm_resource</literal> command, which creates and modifies the extra constraints for you. If <literal>Email</literal> were running on <literal>sles-1</literal> and you wanted it moved to a specific location, the command would look something like:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource -M -r Email -H sles-2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Behind the scenes, the tool will create the following location constraint:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location rsc=\"Email\" node=\"sles-2\" score=\"INFINITY\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is important to note that subsequent invocations of <literal>crm_resource -M</literal> are not cumulative. So, if you ran these commands"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource -M -r Email -H sles-2\n"
"# crm_resource -M -r Email -H sles-3"
msgstr ""
#. Tag: para
#, no-c-format
msgid "then it is as if you had never performed the first command."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To allow the resource to move back again, use:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource -U -r Email"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Note the use of the word <emphasis>allow</emphasis>. The resource can move back to its original location but, depending on <literal>resource-stickiness</literal>, it might stay where it is. To be absolutely certain that it moves back to <literal>sles-1</literal>, move it there before issuing the call to <literal>crm_resource -U</literal>:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource -M -r Email -H sles-1\n"
"# crm_resource -U -r Email"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alternatively, if you only care that the resource should be moved from its current location, try:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource -B -r Email"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Which will instead create a negative constraint, like"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location rsc=\"Email\" node=\"sles-1\" score=\"-INFINITY\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This will achieve the desired effect, but will also have long-term consequences. As the tool will warn you, the creation of a <literal>-INFINITY</literal> constraint will prevent the resource from running on that node until <literal>crm_resource -U</literal> is used. This includes the situation where every other cluster node is no longer available!"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In some cases, such as when <literal>resource-stickiness</literal> is set to <literal>INFINITY</literal>, it is possible that you will end up with the problem described in <xref linkend=\"node-score-equal\" />. The tool can detect some of these cases and deals with them by creating both positive and negative constraints. E.g."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Email</literal> prefers <literal>sles-1</literal> with a score of <literal>-INFINITY</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Email</literal> prefers <literal>sles-2</literal> with a score of <literal>INFINITY</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "which has the same long-term consequences as discussed earlier."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Moving Resources Due to Connectivity Changes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can configure the cluster to move resources when external connectivity is lost in two steps."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Tell Pacemaker to Monitor Connectivity"
msgstr ""
#. Tag: para
#, no-c-format
msgid "First, add an <emphasis role=\"strong\">ocf:pacemaker:ping</emphasis> resource to the cluster. The <emphasis role=\"strong\">ping</emphasis> resource uses the system utility of the same name to a test whether list of machines (specified by DNS hostname or IPv4/IPv6 address) are reachable and uses the results to maintain a node attribute called <literal>pingd</literal> by default. <footnote><para> The attribute name is customizable, in order to allow multiple ping groups to be defined. </para></footnote>"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Older versions of Heartbeat required users to add ping nodes to <literal>ha.cf</literal>, but this is no longer required."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "Older versions of Pacemaker used a different agent <emphasis role=\"strong\">ocf:pacemaker:pingd</emphasis> which is now deprecated in favor of <emphasis role=\"strong\">ping</emphasis>. If your version of Pacemaker does not contain the <emphasis role=\"strong\">ping</emphasis> resource agent, download the latest version from <ulink url=\"https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping\">https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Normally, the ping resource should run on all cluster nodes, which means that you’ll need to create a clone. A template for this can be found below along with a description of the most interesting parameters."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Common Options for a <emphasis>ping</emphasis> Resource"
msgstr ""
+#. Tag: entry
+#, no-c-format
+msgid "Field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "<literal>dampen</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The time to wait (dampening) for further changes to occur. Use this to prevent a resource from bouncing around the cluster when cluster nodes notice the loss of connectivity at slightly different times. <indexterm> <primary>dampen</primary><secondary>Ping Resource Option</secondary> </indexterm> <indexterm> <primary>Ping Resource Option</primary> </indexterm> <indexterm> <primary>Ping Resource</primary><secondary>Option</secondary><tertiary>dampen</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>dampen</secondary> </indexterm> <indexterm> <primary>dampen</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>multiplier</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The number of connected ping nodes gets multiplied by this value to get a score. Useful when there are multiple ping nodes configured. <indexterm> <primary>multiplier</primary><secondary>Ping Resource Option</secondary> </indexterm> <indexterm> <primary>Ping Resource Option</primary> </indexterm> <indexterm> <primary>Ping Resource</primary><secondary>Option</secondary><tertiary>multiplier</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>multiplier</secondary> </indexterm> <indexterm> <primary>multiplier</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>host_list</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The machines to contact in order to determine the current connectivity status. Allowed values include resolvable DNS host names, IPv4 and IPv6 addresses. <indexterm> <primary>host_list</primary><secondary>Ping Resource Option</secondary> </indexterm> <indexterm> <primary>Ping Resource Option</primary> </indexterm> <indexterm> <primary>Ping Resource</primary><secondary>Option</secondary><tertiary>host_list</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>host_list</secondary> </indexterm> <indexterm> <primary>host_list</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An example ping cluster resource that checks node connectivity once every minute"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;clone id=\"Connected\"&gt;\n"
" &lt;primitive id=\"ping\" provider=\"pacemaker\" class=\"ocf\" type=\"ping\"&gt;\n"
" &lt;instance_attributes id=\"ping-attrs\"&gt;\n"
" &lt;nvpair id=\"pingd-dampen\" name=\"dampen\" value=\"5s\"/&gt;\n"
" &lt;nvpair id=\"pingd-multiplier\" name=\"multiplier\" value=\"1000\"/&gt;\n"
" &lt;nvpair id=\"pingd-hosts\" name=\"host_list\" value=\"my.gateway.com www.bigcorp.com\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"ping-monitor-60s\" interval=\"60s\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;/primitive&gt;\n"
"&lt;/clone&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You’re only half done. The next section deals with telling Pacemaker how to deal with the connectivity status that <literal>ocf:pacemaker:ping</literal> is recording."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Tell Pacemaker How to Interpret the Connectivity Data"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before attempting the following, make sure you understand <xref linkend=\"ch-rules\" />."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are a number of ways to use the connectivity data."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The most common setup is for people to have a single ping target (e.g. the service network’s default gateway), to prevent the cluster from running a resource on any unconnected node."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Don’t run a resource on unconnected nodes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"WebServer-no-connectivity\" rsc=\"Webserver\"&gt;\n"
" &lt;rule id=\"ping-exclude-rule\" score=\"-INFINITY\" &gt;\n"
" &lt;expression id=\"ping-exclude\" attribute=\"pingd\" operation=\"not_defined\"/&gt;\n"
" &lt;/rule&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A more complex setup is to have a number of ping targets configured. You can require the cluster to only run resources on nodes that can connect to all (or a minimum subset) of them."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Run only on nodes connected to three or more ping targets."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"ping\" provider=\"pacemaker\" class=\"ocf\" type=\"ping\"&gt;\n"
"... &lt;!-- omitting some configuration to highlight important parts --&gt;\n"
" &lt;nvpair id=\"pingd-multiplier\" name=\"multiplier\" value=\"1000\"/&gt;\n"
"...\n"
"&lt;/primitive&gt;\n"
"...\n"
"&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
" &lt;rule id=\"ping-prefer-rule\" score=\"-INFINITY\" &gt;\n"
" &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/&gt;\n"
" &lt;/rule&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alternatively, you can tell the cluster only to <emphasis>prefer</emphasis> nodes with the best connectivity. Just be sure to set <literal>multiplier</literal> to a value higher than that of <literal>resource-stickiness</literal> (and don’t set either of them to <literal>INFINITY</literal>)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prefer the node with the most connected ping nodes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
" &lt;rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" &gt;\n"
" &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/&gt;\n"
" &lt;/rule&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is perhaps easier to think of this in terms of the simple constraints that the cluster translates it into. For example, if <emphasis role=\"strong\">sles-1</emphasis> is connected to all five ping nodes but <emphasis role=\"strong\">sles-2</emphasis> is only connected to two, then it would be as if you instead had the following constraints in your configuration:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "How the cluster translates the above location constraint"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"ping-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"5000\"/&gt;\n"
"&lt;rsc_location id=\"ping-2\" rsc=\"Webserver\" node=\"sles-2\" score=\"2000\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The advantage is that you don’t have to manually update any constraints whenever your network connectivity changes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can also combine the concepts above into something even more complex. The example below shows how you can prefer the node with the most connected ping nodes provided they have connectivity to at least three (again assuming that <literal>multiplier</literal> is set to 1000)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A more complex example of choosing a location based on connectivity"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
" &lt;rule id=\"ping-exclude-rule\" score=\"-INFINITY\" &gt;\n"
" &lt;expression id=\"ping-exclude\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/&gt;\n"
" &lt;/rule&gt;\n"
" &lt;rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" &gt;\n"
" &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/&gt;\n"
" &lt;/rule&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Migrating Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Normally, when the cluster needs to move a resource, it fully restarts the resource (i.e. stops the resource on the current node and starts it on the new node)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "However, some types of resources, such as Xen virtual guests, are able to move to another location without loss of state (often referred to as live migration or hot migration). In pacemaker, this is called resource migration. Pacemaker can be configured to migrate a resource when moving it, rather than restarting it."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Not all resources are able to migrate; see the Migration Checklist below, and those that can, won’t do so in all situations. Conceptually, there are two requirements from which the other prerequisites follow:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource must be active and healthy at the old location; and"
msgstr ""
#. Tag: para
#, no-c-format
msgid "everything required for the resource to run must be available on both the old and new locations."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster is able to accommodate both <emphasis>push</emphasis> and <emphasis>pull</emphasis> migration models by requiring the resource agent to support two special actions: <literal>migrate_to</literal> (performed on the current location) and <literal>migrate_from</literal> (performed on the destination)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In push migration, the process on the current location transfers the resource to the new location where is it later activated. In this scenario, most of the work would be done in the <literal>migrate_to</literal> action and, if anything, the activation would occur during <literal>migrate_from</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Conversely for pull, the <literal>migrate_to</literal> action is practically empty and <literal>migrate_from</literal> does most of the work, extracting the relevant resource state from the old location and activating it."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There is no wrong or right way for a resource agent to implement migration, as long as it works."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Migration Checklist"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource may not be a clone."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource must use an OCF style agent."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource must not be in a failed or degraded state."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource agent must support <literal>migrate_to</literal> and <literal>migrate_from</literal> actions, and advertise them in its metadata."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource must have the <literal>allow-migrate</literal> meta-attribute set to <literal>true</literal> (which is not the default)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If an otherwise migratable resource depends on another resource via an ordering constraint, there are special situations in which it will be restarted rather than migrated."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For example, if the resource depends on a clone, and at the time the resource needs to be moved, the clone has instances that are stopping and instances that are starting, then the resource will be restarted. The Policy Engine is not yet able to model this situation correctly and so takes the safer (if less optimal) path."
+msgid "For example, if the resource depends on a clone, and at the time the resource needs to be moved, the clone has instances that are stopping and instances that are starting, then the resource will be restarted. The scheduler is not yet able to model this situation correctly and so takes the safer (if less optimal) path."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In pacemaker 1.1.11 and earlier, a migratable resource will be restarted when moving if it directly or indirectly depends on <emphasis>any</emphasis> primitive or group resources."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Even in newer versions, if a migratable resource depends on a non-migratable resource, and both need to be moved, the migratable resource will be restarted."
+msgid "Also, if a migratable resource depends on a non-migratable resource, and both need to be moved, the migratable resource will be restarted."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Tracking Node Health"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A node may be functioning adequately as far as cluster membership is concerned, and yet be \"unhealthy\" in some respect that makes it an undesirable location for resources. For example, a disk drive may be reporting SMART errors, or the CPU may be highly loaded."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker offers a way to automatically move resources off unhealthy nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Health Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker will treat any node attribute whose name starts with <literal>#health</literal> as an indicator of node health. Node health attributes may have one of the following values:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Allowed Values for Node Health Attributes"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Value"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Intended significance"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>red</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This indicator is unhealthy <indexterm> <primary>Node health</primary><secondary>red</secondary> </indexterm> <indexterm> <primary>red</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>yellow</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This indicator is becoming unhealthy <indexterm> <primary>Node health</primary><secondary>yellow</secondary> </indexterm> <indexterm> <primary>yellow</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>green</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This indicator is healthy <indexterm> <primary>Node health</primary><secondary>green</secondary> </indexterm> <indexterm> <primary>green</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>integer</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A numeric score to apply to all resources on this node (0 or positive is healthy, negative is unhealthy) <indexterm> <primary>Node health</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Health Strategy"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker assigns a node health score to each node, as the sum of the values of all its node health attributes. This score will be used as a location constraint applied to this node for all resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>node-health-strategy</literal> cluster option controls how Pacemaker responds to changes in node health attributes, and how it translates <literal>red</literal>, <literal>yellow</literal>, and <literal>green</literal> to scores."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values are:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Health Strategies"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Effect"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>none</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Do not track node health attributes at all. <indexterm> <primary>Node health</primary><secondary>none</secondary> </indexterm> <indexterm> <primary>none</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>migrate-on-red</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Assign the value of <literal>-INFINITY</literal> to <literal>red</literal>, and 0 to <literal>yellow</literal> and <literal>green</literal>. This will cause all resources to move off the node if any attribute is <literal>red</literal>. <indexterm> <primary>Node health</primary><secondary>migrate-on-red</secondary> </indexterm> <indexterm> <primary>migrate-on-red</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>only-green</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Assign the value of <literal>-INFINITY</literal> to <literal>red</literal> and <literal>yellow</literal>, and 0 to <literal>green</literal>. This will cause all resources to move off the node if any attribute is <literal>red</literal> or <literal>yellow</literal>. <indexterm> <primary>Node health</primary><secondary>only-green</secondary> </indexterm> <indexterm> <primary>only-green</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>progressive</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Assign the value of the <literal>node-health-red</literal> cluster option to <literal>red</literal>, the value of <literal>node-health-yellow</literal> to <literal>yellow</literal>, and the value of <literal>node-health-green</literal> to <literal>green</literal>. Each node is additionally assigned a score of <literal>node-health-base</literal> (this allows resources to start even if some attributes are <literal>yellow</literal>). This strategy gives the administrator finer control over how important each value is. <indexterm> <primary>Node health</primary><secondary>progressive</secondary> </indexterm> <indexterm> <primary>progressive</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>custom</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Track node health attributes using the same values as <literal>progressive</literal> for <literal>red</literal>, <literal>yellow</literal>, and <literal>green</literal>, but do not take them into account. The administrator is expected to implement a policy by defining rules (see <xref linkend=\"ch-rules\" />) referencing node health attributes. <indexterm> <primary>Node health</primary><secondary>custom</secondary> </indexterm> <indexterm> <primary>custom</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Measuring Node Health"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Since Pacemaker calculates node health based on node attributes, any method that sets node attributes may be used to measure node health. The most common ways are resource agents or separate daemons."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker provides examples that can be used directly or as a basis for custom code. The <literal>ocf:pacemaker:HealthCPU</literal> and <literal>ocf:pacemaker:HealthSMART</literal> resource agents set node health attributes based on CPU and disk parameters. The <literal>ipmiservicelogd</literal> daemon sets node health attributes based on IPMI values (the <literal>ocf:pacemaker:SystemHealth</literal> resource agent can be used to manage the daemon as a cluster resource)."
msgstr ""
-#. Tag: title
-#, no-c-format
-msgid "Reusing Rules, Options and Sets of Operations"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Sometimes a number of constraints need to use the same set of rules, and resources need to set the same options and parameters. To simplify this situation, you can refer to an existing object using an <literal>id-ref</literal> instead of an id."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "So if for one resource you have"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Then instead of duplicating the rule for all your other resources, you can instead specify:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Referencing rules from other constraints"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;rsc_location id=\"WebDB-connectivity\" rsc=\"WebDB\"&gt;\n"
-" &lt;rule id-ref=\"ping-prefer-rule\"/&gt;\n"
-"&lt;/rsc_location&gt;"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The cluster will insist that the <literal>rule</literal> exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a <literal>rule</literal> that is referenced elsewhere."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The same principle applies for <literal>meta_attributes</literal> and <literal>instance_attributes</literal> as illustrated in the example below:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Referencing attributes, options, and operations from other resources"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\"&gt;\n"
-" &lt;instance_attributes id=\"mySpecialRsc-attrs\" score=\"1\" &gt;\n"
-" &lt;nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/&gt;\n"
-" &lt;nvpair id=\"default-port\" name=\"port\" value=\"9999\"/&gt;\n"
-" &lt;/instance_attributes&gt;\n"
-" &lt;meta_attributes id=\"mySpecialRsc-options\"&gt;\n"
-" &lt;nvpair id=\"failure-timeout\" name=\"failure-timeout\" value=\"5m\"/&gt;\n"
-" &lt;nvpair id=\"migration-threshold\" name=\"migration-threshold\" value=\"1\"/&gt;\n"
-" &lt;nvpair id=\"stickiness\" name=\"resource-stickiness\" value=\"0\"/&gt;\n"
-" &lt;/meta_attributes&gt;\n"
-" &lt;operations id=\"health-checks\"&gt;\n"
-" &lt;op id=\"health-check\" name=\"monitor\" interval=\"60s\"/&gt;\n"
-" &lt;op id=\"health-check\" name=\"monitor\" interval=\"30min\"/&gt;\n"
-" &lt;/operations&gt;\n"
-"&lt;/primitive&gt;\n"
-"&lt;primitive id=\"myOtherlRsc\" class=\"ocf\" type=\"Other\" provider=\"me\"&gt;\n"
-" &lt;instance_attributes id-ref=\"mySpecialRsc-attrs\"/&gt;\n"
-" &lt;meta_attributes id-ref=\"mySpecialRsc-options\"/&gt;\n"
-" &lt;operations id-ref=\"health-checks\"/&gt;\n"
-"&lt;/primitive&gt;"
-msgstr ""
-
#. Tag: title
#, no-c-format
msgid "Reloading Services After a Definition Change"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster automatically detects changes to the definition of services it manages. The normal response is to stop the service (using the old definition) and start it again (with the new definition). This works well, but some services are smarter and can be told to use a new set of options without restarting."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To take advantage of this capability, the resource agent must:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Accept the <literal>reload</literal> operation and perform any required actions. <emphasis>The actions here depend completely on your application!</emphasis>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "The DRBD agent’s logic for supporting <literal>reload</literal>"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "case $1 in\n"
" start)\n"
" drbd_start\n"
" ;;\n"
" stop)\n"
" drbd_stop\n"
" ;;\n"
" reload)\n"
" drbd_reload\n"
" ;;\n"
" monitor)\n"
" drbd_monitor\n"
" ;;\n"
" *)\n"
" drbd_usage\n"
" exit $OCF_ERR_UNIMPLEMENTED\n"
" ;;\n"
"esac\n"
"exit $?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Advertise the <literal>reload</literal> operation in the <literal>actions</literal> section of its metadata"
msgstr ""
#. Tag: title
#, no-c-format
msgid "The DRBD Agent Advertising Support for the <literal>reload</literal> Operation"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;?xml version=\"1.0\"?&gt;\n"
" &lt;!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\"&gt;\n"
" &lt;resource-agent name=\"drbd\"&gt;\n"
" &lt;version&gt;1.1&lt;/version&gt;\n"
"\n"
" &lt;longdesc&gt;\n"
" Master/Slave OCF Resource Agent for DRBD\n"
" &lt;/longdesc&gt;\n"
"\n"
" ...\n"
"\n"
" &lt;actions&gt;\n"
" &lt;action name=\"start\" timeout=\"240\" /&gt;\n"
" &lt;action name=\"reload\" timeout=\"240\" /&gt;\n"
" &lt;action name=\"promote\" timeout=\"90\" /&gt;\n"
" &lt;action name=\"demote\" timeout=\"90\" /&gt;\n"
" &lt;action name=\"notify\" timeout=\"90\" /&gt;\n"
" &lt;action name=\"stop\" timeout=\"100\" /&gt;\n"
" &lt;action name=\"meta-data\" timeout=\"5\" /&gt;\n"
" &lt;action name=\"validate-all\" timeout=\"30\" /&gt;\n"
" &lt;/actions&gt;\n"
" &lt;/resource-agent&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Advertise one or more parameters that can take effect using <literal>reload</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any parameter with the <literal>unique</literal> set to 0 is eligible to be used in this way."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Parameter that can be changed using reload"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;parameter name=\"drbdconf\" unique=\"0\"&gt;\n"
" &lt;longdesc&gt;Full path to the drbd.conf file.&lt;/longdesc&gt;\n"
" &lt;shortdesc&gt;Path to drbd.conf&lt;/shortdesc&gt;\n"
" &lt;content type=\"string\" default=\"${OCF_RESKEY_drbdconf_default}\"/&gt;\n"
"&lt;/parameter&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once these requirements are satisfied, the cluster will automatically know to reload the resource (instead of restarting) when a non-unique field changes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Metadata will not be re-read unless the resource needs to be started. This may mean that the resource will be restarted the first time, even though you changed a parameter with <literal>unique=0</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If both a unique and non-unique field are changed simultaneously, the resource will still be restarted."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot b/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot
index c61da6076f..08a2402c9d 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot
@@ -1,1807 +1,1881 @@
#
# 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"
+"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 "Advanced Resource Types"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Groups - A Syntactic Shortcut"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Group Resources</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Groups</secondary> </indexterm> <indexterm> <primary>Groups</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "One of the most common elements of a cluster is a set of resources that need to be located together, start sequentially, and stop in the reverse order. To simplify this configuration, we support the concept of groups."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A group of two primitive resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;group id=\"shortcut\"&gt;\n"
" &lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive id=\"Email\" class=\"lsb\" type=\"exim\"/&gt;\n"
"&lt;/group&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Although the example above contains only two resources, there is no limit to the number of resources a group can contain. The example is also sufficient to explain the fundamental properties of a group:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources are started in the order they appear in (<literal>Public-IP</literal> first, then <literal>Email</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources are stopped in the reverse order to which they appear in (<literal>Email</literal> first, then <literal>Public-IP</literal>)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If a resource in the group can’t run anywhere, then nothing after that is allowed to run, too."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>Public-IP</literal> can’t run anywhere, neither can <literal>Email</literal>;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "but if <literal>Email</literal> can’t run anywhere, this does not affect <literal>Public-IP</literal> in any way"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The group above is logically equivalent to writing:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "How the cluster sees a group resource"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;resources&gt;\n"
" &lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive id=\"Email\" class=\"lsb\" type=\"exim\"/&gt;\n"
" &lt;/resources&gt;\n"
" &lt;constraints&gt;\n"
" &lt;rsc_colocation id=\"xxx\" rsc=\"Email\" with-rsc=\"Public-IP\" score=\"INFINITY\"/&gt;\n"
" &lt;rsc_order id=\"yyy\" first=\"Public-IP\" then=\"Email\"/&gt;\n"
" &lt;/constraints&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Obviously as the group grows bigger, the reduced configuration effort can become significant."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another (typical) example of a group is a DRBD volume, the filesystem mount, an IP address, and an application that uses them."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Group Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Group Resource"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the group <indexterm> <primary>id</primary><secondary>Group Resource Property</secondary> </indexterm> <indexterm> <primary>Group Resource Property</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Group Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Group Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Group Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Groups inherit the <literal>priority</literal>, <literal>target-role</literal>, and <literal>is-managed</literal> properties from primitive resources. See <xref linkend=\"s-resource-options\" /> for information about those properties."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Group Instance Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Groups have no instance attributes. However, any that are set for the group object will be inherited by the group’s children."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Group Contents"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Groups may only contain a collection of cluster resources (see <xref linkend=\"primitive-resource\" />). To refer to a child of a group resource, just use the child’s <literal>id</literal> instead of the group’s."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Group Constraints"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Although it is possible to reference a group’s children in constraints, it is usually preferable to reference the group itself."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Some constraints involving groups"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_location id=\"group-prefers-node1\" rsc=\"shortcut\" node=\"node1\" score=\"500\"/&gt;\n"
" &lt;rsc_colocation id=\"webserver-with-group\" rsc=\"Webserver\" with-rsc=\"shortcut\"/&gt;\n"
" &lt;rsc_order id=\"start-group-then-webserver\" first=\"Webserver\" then=\"shortcut\"/&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Group Stickiness"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>resource-stickiness</primary><secondary>Groups</secondary> </indexterm> <indexterm> <primary>Groups</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Stickiness, the measure of how much a resource wants to stay where it is, is additive in groups. Every active resource of the group will contribute its stickiness value to the group’s total. So if the default <literal>resource-stickiness</literal> is 100, and a group has seven members, five of which are active, then the group as a whole will prefer its current location with a score of 500."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Clones - Resources That Get Active on Multiple Hosts"
+msgid "Clones - Resources That Can Have Multiple Active Instances"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Clone Resources</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Clones</secondary> </indexterm> <indexterm> <primary>Clones</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Clones were initially conceived as a convenient way to start multiple instances of an IP address resource and have them distributed throughout the cluster for load balancing. They have turned out to quite useful for a number of purposes including integrating with the Distributed Lock Manager (used by many cluster filesystems), the fencing subsystem, and OCFS2."
+msgid "<emphasis>Clone</emphasis> resources are resources that can have more than one copy active at the same time. This allows you, for example, to run a copy of a daemon on every node. You can clone any primitive or group resource. <footnote><para> Of course, the service must support running multiple instances. </para></footnote>"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "You can clone any resource, provided the resource agent supports it."
+msgid "Anonymous versus Unique Clones"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Three types of cloned resources exist:"
+msgid "A clone resource is configured to be either <emphasis>anonymous</emphasis> or <emphasis>globally unique</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Anonymous"
+msgid "Anonymous clones are the simplest. These behave completely identically everywhere they are running. Because of this, there can be only one instance of an anonymous clone active per node."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Globally unique"
+msgid "The instances of globally unique clones are distinct entities. All instances are launched identically, but one instance of the clone is not identical to any other instance, whether running on the same node or a different node. As an example, a cloned IP address can use special kernel functionality such that each instance handles a subset of requests for the same IP address."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Stateful"
+msgid "Promotable clones"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Anonymous</emphasis> clones are the simplest. These behave completely identically everywhere they are running. Because of this, there can be only one copy of an anonymous clone active per machine."
+msgid "<indexterm> <primary>Promotable Clone Resources</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Promotable</secondary> </indexterm> <indexterm> <primary>Promotable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Globally unique</emphasis> clones are distinct entities. A copy of the clone running on one machine is not equivalent to another instance on another node, nor would any two copies on the same node be equivalent."
+msgid "If a clone is <emphasis>promotable</emphasis>, its instances can perform a special role that Pacemaker will manage via the <literal>promote</literal> and <literal>demote</literal> actions of the resource agent."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Stateful</emphasis> clones are covered later in <xref linkend=\"s-resource-multistate\" />."
+msgid "Services that support such a special role have various terms for the special role and the default role: primary and secondary, master and replica, controller and worker, etc. Pacemaker uses the terms <emphasis>master</emphasis> and <emphasis>slave</emphasis>, <footnote><para> These are historical terms that will eventually be replaced, but the extensive use of them and the need for backward compatibility makes it a long process. You may see examples using a <literal>master</literal> tag instead of a <literal>clone</literal> tag with the <literal>promotable</literal> meta-attribute set to <literal>true</literal>; the <literal>master</literal> tag is supported, but deprecated, and will be removed in a future version. You may also see such services referred to as <emphasis>multi-state</emphasis> or <emphasis>stateful</emphasis>; these means the same thing as <emphasis>promotable</emphasis>. </para></footnote> but is agnostic to what the service calls them or what they do."
msgstr ""
-#. Tag: title
-#, no-c-format
-msgid "A clone of an LSB resource"
-msgstr ""
-
-#. Tag: programlisting
+#. Tag: para
#, no-c-format
-msgid "&lt;clone id=\"apache-clone\"&gt;\n"
-" &lt;meta_attributes id=\"apache-clone-meta\"&gt;\n"
-" &lt;nvpair id=\"apache-unique\" name=\"globally-unique\" value=\"false\"/&gt;\n"
-" &lt;/meta_attributes&gt;\n"
-" &lt;primitive id=\"apache\" class=\"lsb\" type=\"apache\"/&gt;\n"
-"&lt;/clone&gt;"
+msgid "All that Pacemaker cares about is that an instance comes up in the default role when started, and the resource agent supports the <literal>promote</literal> and <literal>demote</literal> actions to manage entering and exiting the special role."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Clone Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Clone Resource"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the clone <indexterm> <primary>id</primary><secondary>Clone Property</secondary> </indexterm> <indexterm> <primary>Clone Property</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Clone Options"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Options inherited from <link linkend=\"s-resource-options\">primitive</link> resources: <literal>priority, target-role, is-managed</literal>"
+msgid "<link linkend=\"s-resource-options\">Options</link> inherited from primitive resources: <literal>priority, target-role, is-managed</literal>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Clone-specific configuration options"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>clone-max</literal>"
+msgid "<literal>globally-unique</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "number of nodes in cluster"
+msgid "false"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "How many copies of the resource to start <indexterm> <primary>clone-max</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>clone-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>clone-max</secondary> </indexterm> <indexterm> <primary>clone-max</primary> </indexterm>"
+msgid "If <literal>true</literal>, each clone instance performs a distinct function <indexterm> <primary>globally-unique</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>globally-unique</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>globally-unique</secondary> </indexterm> <indexterm> <primary>globally-unique</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>clone-node-max</literal>"
+msgid "<literal>clone-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "1"
+msgid "number of nodes in cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "How many copies of the resource can be started on a single node <indexterm> <primary>clone-node-max</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>clone-node-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>clone-node-max</secondary> </indexterm> <indexterm> <primary>clone-node-max</primary> </indexterm>"
+msgid "The maximum number of clone instances that can be started across the entire cluster <indexterm> <primary>clone-max</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>clone-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>clone-max</secondary> </indexterm> <indexterm> <primary>clone-max</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>clone-min</literal>"
+msgid "<literal>clone-node-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Require at least this number of clone instances to be runnable before allowing resources depending on the clone to be runnable <emphasis>(since 1.1.14)</emphasis> <indexterm> <primary>clone-min</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>clone-min</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>clone-min</secondary> </indexterm> <indexterm> <primary>clone-min</primary> </indexterm>"
+msgid "1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>notify</literal>"
+msgid "If <literal>globally-unique</literal> is <literal>true</literal>, the maximum number of clone instances that can be started on a single node <indexterm> <primary>clone-node-max</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>clone-node-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>clone-node-max</secondary> </indexterm> <indexterm> <primary>clone-node-max</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "true"
+msgid "<literal>clone-min</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When stopping or starting a copy of the clone, tell all the other copies beforehand and again when the action was successful. Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>notify</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>notify</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>notify</secondary> </indexterm> <indexterm> <primary>notify</primary> </indexterm>"
+msgid "0"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>globally-unique</literal>"
+msgid "Require at least this number of clone instances to be runnable before allowing resources depending on the clone to be runnable. A value of 0 means require all clone instances to be runnable. <indexterm> <primary>clone-min</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>clone-min</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>clone-min</secondary> </indexterm> <indexterm> <primary>clone-min</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "false"
+msgid "<literal>notify</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Does each copy of the clone perform a different function? Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>globally-unique</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>globally-unique</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>globally-unique</secondary> </indexterm> <indexterm> <primary>globally-unique</primary> </indexterm>"
+msgid "Call the resource agent’s <literal>notify</literal> action for all active instances, before and after starting or stopping any clone instance. The resource agent must support this action. Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>notify</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>notify</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>notify</secondary> </indexterm> <indexterm> <primary>notify</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>ordered</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Should the copies be started in series (instead of in parallel)? Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>ordered</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>ordered</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>ordered</secondary> </indexterm> <indexterm> <primary>ordered</primary> </indexterm>"
+msgid "If <literal>true</literal>, clone instances must be started sequentially instead of in parallel Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>ordered</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>ordered</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>ordered</secondary> </indexterm> <indexterm> <primary>ordered</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>interleave</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If this clone depends on another clone via an ordering constraint, is it allowed to start after the local instance of the other clone starts, rather than wait for all instances of the other clone to start? Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>interleave</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>interleave</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>interleave</secondary> </indexterm> <indexterm> <primary>interleave</primary> </indexterm>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Clone Instance Attributes"
+msgid "When this clone is ordered relative to another clone, if this option is <literal>false</literal> (the default), the ordering is relative to <emphasis>all</emphasis> instances of the other clone, whereas if this option is <literal>true</literal>, the ordering is relative only to instances on the same node. Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>interleave</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>interleave</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>interleave</secondary> </indexterm> <indexterm> <primary>interleave</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Clones have no instance attributes; however, any that are set here will be inherited by the clone’s children."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Clone Contents"
+msgid "<literal>promotable</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Clones must contain exactly one primitive or group resource."
+msgid "If <literal>true</literal>, clone instances can perform a special role that Pacemaker will manage via the resource agent’s <literal>promote</literal> and <literal>demote</literal> actions. The resource agent must support these actions. Allowed values: <literal>false</literal>, <literal>true</literal> <indexterm> <primary>promotable</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>promotable</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>promotable</secondary> </indexterm> <indexterm> <primary>promotable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You should never reference the name of a clone’s child. If you think you need to do this, you probably need to re-evaluate your design."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Clone Constraints"
+msgid "<literal>promoted-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In most cases, a clone will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently from those for primitive resources except that the clone’s <literal>id</literal> is used."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Some constraints involving clones"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;constraints&gt;\n"
-" &lt;rsc_location id=\"clone-prefers-node1\" rsc=\"apache-clone\" node=\"node1\" score=\"500\"/&gt;\n"
-" &lt;rsc_colocation id=\"stats-with-clone\" rsc=\"apache-stats\" with=\"apache-clone\"/&gt;\n"
-" &lt;rsc_order id=\"start-clone-then-stats\" first=\"apache-clone\" then=\"apache-stats\"/&gt;\n"
-"&lt;/constraints&gt;"
+msgid "If <literal>promotable</literal> is <literal>true</literal>, the number of instances that can be promoted at one time across the entire cluster <indexterm> <primary>promoted-max</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>promoted-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>promoted-max</secondary> </indexterm> <indexterm> <primary>promoted-max</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Ordering constraints behave slightly differently for clones. In the example above, <literal>apache-stats</literal> will wait until all copies of <literal>apache-clone</literal> that need to be started have done so before being started itself. Only if <emphasis>no</emphasis> copies can be started will <literal>apache-stats</literal> be prevented from being active. Additionally, the clone will wait for <literal>apache-stats</literal> to be stopped before stopping itself."
+msgid "<literal>promoted-node-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Colocation of a primitive or group resource with a clone means that the resource can run on any machine with an active copy of the clone. The cluster will choose a copy based on where the clone is running and the resource’s own location preferences."
+msgid "If <literal>promotable</literal> is <literal>true</literal> and <literal>globally-unique</literal> is <literal>false</literal>, the number of clone instances can be promoted at one time on a single node <indexterm> <primary>promoted-node-max</primary><secondary>Clone Option</secondary> </indexterm> <indexterm> <primary>Clone Option</primary> </indexterm> <indexterm> <primary>Clone</primary><secondary>Option</secondary><tertiary>promoted-node-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>promoted-node-max</secondary> </indexterm> <indexterm> <primary>promoted-node-max</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Colocation between clones is also possible. If one clone <literal>A</literal> is colocated with another clone <literal>B</literal>, the set of allowed locations for <literal>A</literal> is limited to nodes on which <literal>B</literal> is (or will be) active. Placement is then performed normally."
+msgid "For backward compatibility, <literal>master-max</literal> and <literal>master-node-max</literal> are accepted as aliases for <literal>promoted-max</literal> and <literal>promoted-node-max</literal>, but are deprecated since 2.0.0, and support for them will be removed in a future version."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Clone Stickiness"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>resource-stickiness</primary><secondary>Clones</secondary> </indexterm> <indexterm> <primary>Clones</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for <literal>resource-stickiness</literal> is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster."
+msgid "Clone Contents"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For globally unique clones, this may result in multiple instances of the clone staying on a single node, even after another eligible node becomes active (for example, after being put into standby mode then made active again). If you do not want this behavior, specify a <literal>resource-stickiness</literal> of 0 for the clone temporarily and let the cluster adjust, then set it back to 1 if you want the default behavior to apply again."
+msgid "Clones must contain exactly one primitive or group resource."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Clone Resource Agent Requirements"
+msgid "A clone that runs a web server on all nodes"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Any resource can be used as an anonymous clone, as it requires no additional support from the resource agent. Whether it makes sense to do so depends on your resource and its resource agent."
-msgstr ""
-
-#. Tag: para
+#. Tag: programlisting
#, no-c-format
-msgid "Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with <literal>${OCF_SUCCESS}</literal> if the node has that exact instance active. All other probes for instances of the clone should result in <literal>${OCF_NOT_RUNNING}</literal> (or one of the other OCF error codes if they are failed)."
+msgid "&lt;clone id=\"apache-clone\"&gt;\n"
+" &lt;primitive id=\"apache\" class=\"lsb\" type=\"apache\"&gt;\n"
+" &lt;operations&gt;\n"
+" &lt;op id=\"apache-monitor\" name=\"monitor\" interval=\"30\"/&gt;\n"
+" &lt;/operations&gt;\n"
+" &lt;/primitive&gt;\n"
+"&lt;/clone&gt;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Individual instances of a clone are identified by appending a colon and a numerical offset, e.g. <literal>apache:2</literal>."
+msgid "You should never reference the name of a clone’s child (the primitive or group resource being cloned). If you think you need to do this, you probably need to re-evaluate your design."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Resource agents can find out how many copies there are by examining the <literal>OCF_RESKEY_CRM_meta_clone_max</literal> environment variable and which copy it is by examining <literal>OCF_RESKEY_CRM_meta_clone</literal>."
+msgid "Clone Instance Attributes"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The resource agent must not make any assumptions (based on <literal>OCF_RESKEY_CRM_meta_clone</literal>) about which numerical instances are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0."
+msgid "Clones have no instance attributes; however, any that are set here will be inherited by the clone’s child."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Clone Notifications"
+msgid "Clone Constraints"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supporting notifications requires the <literal>notify</literal> action to be implemented. If supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it."
+msgid "In most cases, a clone will have a single instance on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently from those for primitive resources except that the clone’s <literal>id</literal> is used."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Environment variables supplied with Clone notify actions"
+msgid "Some constraints involving clones"
msgstr ""
-#. Tag: entry
+#. Tag: programlisting
#, no-c-format
-msgid "Variable"
+msgid "&lt;constraints&gt;\n"
+" &lt;rsc_location id=\"clone-prefers-node1\" rsc=\"apache-clone\" node=\"node1\" score=\"500\"/&gt;\n"
+" &lt;rsc_colocation id=\"stats-with-clone\" rsc=\"apache-stats\" with=\"apache-clone\"/&gt;\n"
+" &lt;rsc_order id=\"start-clone-then-stats\" first=\"apache-clone\" then=\"apache-stats\"/&gt;\n"
+"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_type"
+msgid "Ordering constraints behave slightly differently for clones. In the example above, <literal>apache-stats</literal> will wait until all copies of <literal>apache-clone</literal> that need to be started have done so before being started itself. Only if <emphasis>no</emphasis> copies can be started will <literal>apache-stats</literal> be prevented from being active. Additionally, the clone will wait for <literal>apache-stats</literal> to be stopped before stopping itself."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Allowed values: <literal>pre</literal>, <literal>post</literal> <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>type</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>type</secondary> </indexterm> <indexterm> <primary>type</primary> </indexterm> <indexterm> <primary>type</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Colocation of a primitive or group resource with a clone means that the resource can run on any node with an active instance of the clone. The cluster will choose an instance based on where the clone is running and the resource’s own location preferences."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_operation"
+msgid "Colocation between clones is also possible. If one clone <literal>A</literal> is colocated with another clone <literal>B</literal>, the set of allowed locations for <literal>A</literal> is limited to nodes on which <literal>B</literal> is (or will be) active. Placement is then performed normally."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Allowed values: <literal>start</literal>, <literal>stop</literal> <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm> <indexterm> <primary>operation</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Promotable Clone Constraints"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_start_resource"
+msgid "For promotable clone resources, the <literal>first-action</literal> and/or <literal>then-action</literal> fields for ordering constraints may be set to <literal>promote</literal> or <literal>demote</literal> to constrain the master role, and colocation constraints may contain <literal>rsc-role</literal> and/or <literal>with-rsc-role</literal> fields."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Resources to be started <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>start_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>start_resource</secondary> </indexterm> <indexterm> <primary>start_resource</primary> </indexterm> <indexterm> <primary>start_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Additional colocation constraint options for promotable clone resources"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_stop_resource"
+msgid "<literal>rsc-role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resources to be stopped <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>stop_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>stop_resource</secondary> </indexterm> <indexterm> <primary>stop_resource</primary> </indexterm> <indexterm> <primary>stop_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Started"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_active_resource"
+msgid "An additional attribute of colocation constraints that specifies the role that <literal>rsc</literal> must be in. Allowed values: <literal>Started</literal>, <literal>Master</literal>, <literal>Slave</literal>. <indexterm> <primary>rsc-role</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>rsc-role</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>rsc-role</secondary> </indexterm> <indexterm> <primary>rsc-role</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resources that are running <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>active_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>active_resource</secondary> </indexterm> <indexterm> <primary>active_resource</primary> </indexterm> <indexterm> <primary>active_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "<literal>with-rsc-role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_inactive_resource"
+msgid "An additional attribute of colocation constraints that specifies the role that <literal>with-rsc</literal> must be in. Allowed values: <literal>Started</literal>, <literal>Master</literal>, <literal>Slave</literal>. <indexterm> <primary>with-rsc-role</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>with-rsc-role</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>with-rsc-role</secondary> </indexterm> <indexterm> <primary>with-rsc-role</primary> </indexterm>"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Resources that are not running <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>inactive_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>inactive_resource</secondary> </indexterm> <indexterm> <primary>inactive_resource</primary> </indexterm> <indexterm> <primary>inactive_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Constraints involving promotable clone resources"
msgstr ""
-#. Tag: para
+#. Tag: programlisting
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_start_uname"
+msgid "&lt;constraints&gt;\n"
+" &lt;rsc_location id=\"db-prefers-node1\" rsc=\"database\" node=\"node1\" score=\"500\"/&gt;\n"
+" &lt;rsc_colocation id=\"backup-with-db-slave\" rsc=\"backup\"\n"
+" with-rsc=\"database\" with-rsc-role=\"Slave\"/&gt;\n"
+" &lt;rsc_colocation id=\"myapp-with-db-master\" rsc=\"myApp\"\n"
+" with-rsc=\"database\" with-rsc-role=\"Master\"/&gt;\n"
+" &lt;rsc_order id=\"start-db-before-backup\" first=\"database\" then=\"backup\"/&gt;\n"
+" &lt;rsc_order id=\"promote-db-then-app\" first=\"database\" first-action=\"promote\"\n"
+" then=\"myApp\" then-action=\"start\"/&gt;\n"
+"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Nodes on which resources will be started <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>start_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>start_uname</secondary> </indexterm> <indexterm> <primary>start_uname</primary> </indexterm> <indexterm> <primary>start_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "In the example above, <literal>myApp</literal> will wait until one of the database copies has been started and promoted to master before being started itself on the same node. Only if no copies can be promoted will <literal>myApp</literal> be prevented from being active. Additionally, the cluster will wait for <literal>myApp</literal> to be stopped before demoting the database."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_stop_uname"
+msgid "Colocation of a primitive or group resource with a promotable clone resource means that it can run on any node with an active instance of the promotable clone resource that has the specified role (<literal>master</literal> or <literal>slave</literal>). In the example above, the cluster will choose a location based on where database is running as a <literal>master</literal>, and if there are multiple <literal>master</literal> instances it will also factor in <literal>myApp</literal>'s own location preferences when deciding which location to choose."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Nodes on which resources will be stopped <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>stop_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>stop_uname</secondary> </indexterm> <indexterm> <primary>stop_uname</primary> </indexterm> <indexterm> <primary>stop_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Colocation with regular clones and other promotable clone resources is also possible. In such cases, the set of allowed locations for the <literal>rsc</literal> clone is (after role filtering) limited to nodes on which the <literal>with-rsc</literal> promotable clone resource is (or will be) in the specified role. Placement is then performed as normal."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_active_uname"
+msgid "Using Promotable Clone Resources in Colocation Sets"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Nodes on which resources are running <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>active_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>active_uname</secondary> </indexterm> <indexterm> <primary>active_uname</primary> </indexterm> <indexterm> <primary>active_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
+msgid "Additional colocation set options relevant to promotable clone resources"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The variables come in pairs, such as <literal>OCF_RESKEY_CRM_meta_notify_start_resource</literal> and <literal>OCF_RESKEY_CRM_meta_notify_start_uname</literal> and should be treated as an array of whitespace-separated elements."
+msgid "<literal>role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>OCF_RESKEY_CRM_meta_notify_inactive_resource</literal> is an exception as the matching <literal>uname</literal> variable does not exist since inactive resources are not running on any node."
+msgid "The role that <emphasis>all members</emphasis> of the set must be in. Allowed values: <literal>Started</literal>, <literal>Master</literal>, <literal>Slave</literal>. <indexterm> <primary>role</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thus in order to indicate that <literal>clone:0</literal> will be started on <literal>sles-1</literal>, <literal>clone:2</literal> will be started on <literal>sles-3</literal>, and <literal>clone:3</literal> will be started on <literal>sles-2</literal>, the cluster would set"
+msgid "In the following example <literal>B</literal>'s master must be located on the same node as <literal>A</literal>'s master. Additionally resources <literal>C</literal> and <literal>D</literal> must be located on the same node as <literal>A</literal>'s and <literal>B</literal>'s masters."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Notification variables"
+msgid "Colocate C and D with A’s and B’s master instances"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "OCF_RESKEY_CRM_meta_notify_start_resource=\"clone:0 clone:2 clone:3\"\n"
-"OCF_RESKEY_CRM_meta_notify_start_uname=\"sles-1 sles-3 sles-2\""
+msgid "&lt;constraints&gt;\n"
+" &lt;rsc_colocation id=\"coloc-1\" score=\"INFINITY\" &gt;\n"
+" &lt;resource_set id=\"colocated-set-example-1\" sequential=\"true\" role=\"Master\"&gt;\n"
+" &lt;resource_ref id=\"A\"/&gt;\n"
+" &lt;resource_ref id=\"B\"/&gt;\n"
+" &lt;/resource_set&gt;\n"
+" &lt;resource_set id=\"colocated-set-example-2\" sequential=\"true\"&gt;\n"
+" &lt;resource_ref id=\"C\"/&gt;\n"
+" &lt;resource_ref id=\"D\"/&gt;\n"
+" &lt;/resource_set&gt;\n"
+" &lt;/rsc_colocation&gt;\n"
+"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Proper Interpretation of Notification Environment Variables"
+msgid "Using Promotable Clone Resources in Ordered Sets"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Pre-notification (stop):"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Active resources: <literal>$OCF_RESKEY_CRM_meta_notify_active_resource</literal>"
+msgid "Additional ordered set options relevant to promotable clone resources"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Inactive resources: <literal>$OCF_RESKEY_CRM_meta_notify_inactive_resource</literal>"
+msgid "<literal>action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resources to be started: <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
+msgid "value of <literal>first-action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resources to be stopped: <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
+msgid "An additional attribute of ordering constraint sets that specifies the action that applies to <emphasis>all members</emphasis> of the set. Allowed values: <literal>start</literal>, <literal>stop</literal>, <literal>promote</literal>, <literal>demote</literal>. <indexterm> <primary>action</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>action</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>action</secondary> </indexterm> <indexterm> <primary>action</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Post-notification (stop) / Pre-notification (start):"
+msgid "Start C and D after first promoting A and B"
msgstr ""
-#. Tag: para
+#. Tag: programlisting
#, no-c-format
-msgid "Active resources"
+msgid "&lt;constraints&gt;\n"
+" &lt;rsc_order id=\"order-1\" score=\"INFINITY\" &gt;\n"
+" &lt;resource_set id=\"ordered-set-1\" sequential=\"true\" action=\"promote\"&gt;\n"
+" &lt;resource_ref id=\"A\"/&gt;\n"
+" &lt;resource_ref id=\"B\"/&gt;\n"
+" &lt;/resource_set&gt;\n"
+" &lt;resource_set id=\"ordered-set-2\" sequential=\"true\" action=\"start\"&gt;\n"
+" &lt;resource_ref id=\"C\"/&gt;\n"
+" &lt;resource_ref id=\"D\"/&gt;\n"
+" &lt;/resource_set&gt;\n"
+" &lt;/rsc_order&gt;\n"
+"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>$OCF_RESKEY_CRM_meta_notify_active_resource</literal>"
+msgid "In the above example, <literal>B</literal> cannot be promoted to a master role until <literal>A</literal> has been promoted. Additionally, resources <literal>C</literal> and <literal>D</literal> must wait until <literal>A</literal> and <literal>B</literal> have been promoted before they can start."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "minus <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
+msgid "Clone Stickiness"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Inactive resources"
+msgid "<indexterm> <primary>resource-stickiness</primary><secondary>Clones</secondary> </indexterm> <indexterm> <primary>Clones</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>$OCF_RESKEY_CRM_meta_notify_inactive_resource</literal>"
+msgid "To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for <literal>resource-stickiness</literal> is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "plus <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
+msgid "For globally unique clones, this may result in multiple instances of the clone staying on a single node, even after another eligible node becomes active (for example, after being put into standby mode then made active again). If you do not want this behavior, specify a <literal>resource-stickiness</literal> of 0 for the clone temporarily and let the cluster adjust, then set it back to 1 if you want the default behavior to apply again."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Resources that were started: <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
+msgid "Clone Resource Agent Requirements"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resources that were stopped: <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
+msgid "Any resource can be used as an anonymous clone, as it requires no additional support from the resource agent. Whether it makes sense to do so depends on your resource and its resource agent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Post-notification (start):"
+msgid "Resource Agent Requirements for Globally Unique Clones"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Active resources:"
+msgid "Globally unique clones require additional support in the resource agent. In particular, it must only respond with <literal>${OCF_SUCCESS}</literal> if the node has that exact instance active. All other probes for instances of the clone should result in <literal>${OCF_NOT_RUNNING}</literal> (or one of the other OCF error codes if they are failed)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "plus <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
+msgid "Individual instances of a clone are identified by appending a colon and a numerical offset, e.g. <literal>apache:2</literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Inactive resources:"
+msgid "Resource agents can find out how many copies there are by examining the <literal>OCF_RESKEY_CRM_meta_clone_max</literal> environment variable and which instance it is by examining <literal>OCF_RESKEY_CRM_meta_clone</literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "minus <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
+msgid "The resource agent must not make any assumptions (based on <literal>OCF_RESKEY_CRM_meta_clone</literal>) about which numerical instances are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Multi-state - Resources That Have Multiple Modes"
+msgid "Resource Agent Requirements for Promotable Clones"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>Multi-state Resources</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Multi-state</secondary> </indexterm> <indexterm> <primary>Multi-state</primary> </indexterm>"
+msgid "Promotable clone resources require two extra actions, <literal>demote</literal> and <literal>promote</literal>, which are responsible for changing the state of the resource. Like <literal>start</literal> and <literal>stop</literal>, they should return <literal>${OCF_SUCCESS}</literal> if they completed successfully or a relevant error code if they did not."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Multi-state resources are a specialization of clone resources; please ensure you understand <xref linkend=\"s-resource-clone\" /> before continuing!"
+msgid "The states can mean whatever you wish, but when the resource is started, it must come up in the mode called <literal>slave</literal>. From there the cluster will decide which instances to promote to <literal>master</literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Multi-state resources allow the instances to be in one of two operating modes (called <emphasis>roles</emphasis>). The roles are called <emphasis>master</emphasis> and <emphasis>slave</emphasis>, but can mean whatever you wish them to mean. The only limitation is that when an instance is started, it must come up in the slave role."
+msgid "In addition to the clone requirements for monitor actions, agents must also <emphasis>accurately</emphasis> report which state they are in. The cluster relies on the agent to report its status (including role) accurately and does not indicate to the agent what role it currently believes it to be in."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Multi-state Properties"
+msgid "Role implications of OCF return codes"
msgstr ""
-#. Tag: title
+#. Tag: entry
#, no-c-format
-msgid "Properties of a Multi-State Resource"
+msgid "Monitor Return Code"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Your name for the multi-state resource <indexterm> <primary>id</primary><secondary>Multi-State Property</secondary> </indexterm> <indexterm> <primary>Multi-State Property</primary> </indexterm> <indexterm> <primary>Multi-State</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Multi-state Options"
+msgid "OCF_NOT_RUNNING"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Options inherited from <link linkend=\"s-resource-options\">primitive</link> resources: <literal>priority</literal>, <literal>target-role</literal>, <literal>is-managed</literal>"
+msgid "Stopped <indexterm> <primary>Return Code</primary><secondary>OCF_NOT_RUNNING</secondary> </indexterm> <indexterm> <primary>OCF_NOT_RUNNING</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Options inherited from <link linkend=\"s-resource-clone\">clone</link> resources: <literal>clone-max</literal>, <literal>clone-node-max</literal>, <literal>notify</literal>, <literal>globally-unique</literal>, <literal>ordered</literal>, <literal>interleave</literal>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Multi-state-specific resource configuration options"
+msgid "OCF_SUCCESS"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>master-max</literal>"
+msgid "Running (Slave) <indexterm> <primary>Return Code</primary><secondary>OCF_SUCCESS</secondary> </indexterm> <indexterm> <primary>OCF_SUCCESS</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "How many copies of the resource can be promoted to the <literal>master</literal> role <indexterm> <primary>master-max</primary><secondary>Multi-State Option</secondary> </indexterm> <indexterm> <primary>Multi-State Option</primary> </indexterm> <indexterm> <primary>Multi-State</primary><secondary>Option</secondary><tertiary>master-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>master-max</secondary> </indexterm> <indexterm> <primary>master-max</primary> </indexterm>"
+msgid "OCF_RUNNING_MASTER"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>master-node-max</literal>"
+msgid "Running (Master) <indexterm> <primary>Return Code</primary><secondary>OCF_RUNNING_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_RUNNING_MASTER</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "How many copies of the resource can be promoted to the <literal>master</literal> role on a single node <indexterm> <primary>master-node-max</primary><secondary>Multi-State Option</secondary> </indexterm> <indexterm> <primary>Multi-State Option</primary> </indexterm> <indexterm> <primary>Multi-State</primary><secondary>Option</secondary><tertiary>master-node-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>master-node-max</secondary> </indexterm> <indexterm> <primary>master-node-max</primary> </indexterm>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Multi-state Instance Attributes"
+msgid "OCF_FAILED_MASTER"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Multi-state resources have no instance attributes; however, any that are set here will be inherited by a master’s children."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Multi-state Contents"
+msgid "Failed (Master) <indexterm> <primary>Return Code</primary><secondary>OCF_FAILED_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_FAILED_MASTER</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Masters must contain exactly one primitive or group resource."
+msgid "Other"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You should never reference the name of a master’s child. If you think you need to do this, you probably need to re-evaluate your design."
+msgid "Failed (Slave)"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Monitoring Multi-State Resources"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The usual monitor actions are insufficient to monitor a multi-state resource, because pacemaker needs to verify not only that the resource is active, but also that its actual role matches its intended one."
+msgid "Clone Notifications"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Define two monitoring actions: the usual one will cover the slave role, and an additional one with <literal>role=\"master\"</literal> will cover the master role."
+msgid "If the clone has the <literal>notify</literal> meta-attribute set to <literal>true</literal>, and the resource agent supports the <literal>notify</literal> action, Pacemaker will call the action when appropriate, passing a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Monitoring both states of a multi-state resource"
+msgid "Environment variables supplied with Clone notify actions"
msgstr ""
-#. Tag: programlisting
+#. Tag: entry
#, no-c-format
-msgid "&lt;master id=\"myMasterRsc\"&gt;\n"
-" &lt;primitive id=\"myRsc\" class=\"ocf\" type=\"myApp\" provider=\"myCorp\"&gt;\n"
-" &lt;operations&gt;\n"
-" &lt;op id=\"public-ip-slave-check\" name=\"monitor\" interval=\"60\"/&gt;\n"
-" &lt;op id=\"public-ip-master-check\" name=\"monitor\" interval=\"61\" role=\"Master\"/&gt;\n"
-" &lt;/operations&gt;\n"
-" &lt;/primitive&gt;\n"
-"&lt;/master&gt;"
+msgid "Variable"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is crucial that <emphasis>every</emphasis> monitor operation has a different interval! Pacemaker currently differentiates between operations only by resource and interval; so if (for example) a master/slave resource had the same monitor interval for both roles, Pacemaker would ignore the role when checking the status — which would cause unexpected return codes, and therefore unnecessary complications."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Multi-state Constraints"
+msgid "OCF_RESKEY_CRM_meta_notify_type"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In most cases, multi-state resources will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently from those for primitive resources except that the master’s <literal>id</literal> is used."
+msgid "Allowed values: <literal>pre</literal>, <literal>post</literal> <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>type</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>type</secondary> </indexterm> <indexterm> <primary>type</primary> </indexterm> <indexterm> <primary>type</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When considering multi-state resources in constraints, for most purposes it is sufficient to treat them as clones. The exception is that the <literal>first-action</literal> and/or <literal>then-action</literal> fields for ordering constraints may be set to <literal>promote</literal> or <literal>demote</literal> to constrain the master role, and colocation constraints may contain <literal>rsc-role</literal> and/or <literal>with-rsc-role</literal> fields."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Additional colocation constraint options for multi-state resources"
+msgid "OCF_RESKEY_CRM_meta_notify_operation"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>rsc-role</literal>"
+msgid "Allowed values: <literal>start</literal>, <literal>stop</literal> <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm> <indexterm> <primary>operation</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Started"
+msgid "OCF_RESKEY_CRM_meta_notify_start_resource"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An additional attribute of colocation constraints that specifies the role that <literal>rsc</literal> must be in. Allowed values: <literal>Started</literal>, <literal>Master</literal>, <literal>Slave</literal>. <indexterm> <primary>rsc-role</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>rsc-role</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>rsc-role</secondary> </indexterm> <indexterm> <primary>rsc-role</primary> </indexterm>"
+msgid "Resources to be started <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>start_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>start_resource</secondary> </indexterm> <indexterm> <primary>start_resource</primary> </indexterm> <indexterm> <primary>start_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>with-rsc-role</literal>"
+msgid "OCF_RESKEY_CRM_meta_notify_stop_resource"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An additional attribute of colocation constraints that specifies the role that <literal>with-rsc</literal> must be in. Allowed values: <literal>Started</literal>, <literal>Master</literal>, <literal>Slave</literal>. <indexterm> <primary>with-rsc-role</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>with-rsc-role</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>with-rsc-role</secondary> </indexterm> <indexterm> <primary>with-rsc-role</primary> </indexterm>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Constraints involving multi-state resources"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;constraints&gt;\n"
-" &lt;rsc_location id=\"db-prefers-node1\" rsc=\"database\" node=\"node1\" score=\"500\"/&gt;\n"
-" &lt;rsc_colocation id=\"backup-with-db-slave\" rsc=\"backup\"\n"
-" with-rsc=\"database\" with-rsc-role=\"Slave\"/&gt;\n"
-" &lt;rsc_colocation id=\"myapp-with-db-master\" rsc=\"myApp\"\n"
-" with-rsc=\"database\" with-rsc-role=\"Master\"/&gt;\n"
-" &lt;rsc_order id=\"start-db-before-backup\" first=\"database\" then=\"backup\"/&gt;\n"
-" &lt;rsc_order id=\"promote-db-then-app\" first=\"database\" first-action=\"promote\"\n"
-" then=\"myApp\" then-action=\"start\"/&gt;\n"
-"&lt;/constraints&gt;"
+msgid "Resources to be stopped <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>stop_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>stop_resource</secondary> </indexterm> <indexterm> <primary>stop_resource</primary> </indexterm> <indexterm> <primary>stop_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the example above, <literal>myApp</literal> will wait until one of the database copies has been started and promoted to master before being started itself on the same node. Only if no copies can be promoted will <literal>myApp</literal> be prevented from being active. Additionally, the cluster will wait for <literal>myApp</literal> to be stopped before demoting the database."
+msgid "OCF_RESKEY_CRM_meta_notify_active_resource"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Colocation of a primitive or group resource with a multi-state resource means that it can run on any machine with an active copy of the multi-state resource that has the specified role (<literal>master</literal> or <literal>slave</literal>). In the example above, the cluster will choose a location based on where database is running as a <literal>master</literal>, and if there are multiple <literal>master</literal> instances it will also factor in <literal>myApp</literal>'s own location preferences when deciding which location to choose."
+msgid "Resources that are running <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>active_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>active_resource</secondary> </indexterm> <indexterm> <primary>active_resource</primary> </indexterm> <indexterm> <primary>active_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Colocation with regular clones and other multi-state resources is also possible. In such cases, the set of allowed locations for the <literal>rsc</literal> clone is (after role filtering) limited to nodes on which the <literal>with-rsc</literal> multi-state resource is (or will be) in the specified role. Placement is then performed as normal."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Using Multi-state Resources in Colocation Sets"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Additional colocation set options relevant to multi-state resources"
+msgid "OCF_RESKEY_CRM_meta_notify_inactive_resource"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>role</literal>"
+msgid "Resources that are not running <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>inactive_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>inactive_resource</secondary> </indexterm> <indexterm> <primary>inactive_resource</primary> </indexterm> <indexterm> <primary>inactive_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The role that <emphasis>all members</emphasis> of the set must be in. Allowed values: <literal>Started</literal>, <literal>Master</literal>, <literal>Slave</literal>. <indexterm> <primary>role</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
+msgid "OCF_RESKEY_CRM_meta_notify_start_uname"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the following example <literal>B</literal>'s master must be located on the same node as <literal>A</literal>'s master. Additionally resources <literal>C</literal> and <literal>D</literal> must be located on the same node as <literal>A</literal>'s and <literal>B</literal>'s masters."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Colocate C and D with A’s and B’s master instances"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;constraints&gt;\n"
-" &lt;rsc_colocation id=\"coloc-1\" score=\"INFINITY\" &gt;\n"
-" &lt;resource_set id=\"colocated-set-example-1\" sequential=\"true\" role=\"Master\"&gt;\n"
-" &lt;resource_ref id=\"A\"/&gt;\n"
-" &lt;resource_ref id=\"B\"/&gt;\n"
-" &lt;/resource_set&gt;\n"
-" &lt;resource_set id=\"colocated-set-example-2\" sequential=\"true\"&gt;\n"
-" &lt;resource_ref id=\"C\"/&gt;\n"
-" &lt;resource_ref id=\"D\"/&gt;\n"
-" &lt;/resource_set&gt;\n"
-" &lt;/rsc_colocation&gt;\n"
-"&lt;/constraints&gt;"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Using Multi-state Resources in Ordering Sets"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Additional ordered set options relevant to multi-state resources"
+msgid "Nodes on which resources will be started <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>start_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>start_uname</secondary> </indexterm> <indexterm> <primary>start_uname</primary> </indexterm> <indexterm> <primary>start_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>action</literal>"
+msgid "OCF_RESKEY_CRM_meta_notify_stop_uname"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "value of <literal>first-action</literal>"
+msgid "Nodes on which resources will be stopped <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>stop_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>stop_uname</secondary> </indexterm> <indexterm> <primary>stop_uname</primary> </indexterm> <indexterm> <primary>stop_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An additional attribute of ordering constraint sets that specifies the action that applies to <emphasis>all members</emphasis> of the set. Allowed values: <literal>start</literal>, <literal>stop</literal>, <literal>promote</literal>, <literal>demote</literal>. <indexterm> <primary>action</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>action</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>action</secondary> </indexterm> <indexterm> <primary>action</primary> </indexterm>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Start C and D after first promoting A and B"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;constraints&gt;\n"
-" &lt;rsc_order id=\"order-1\" score=\"INFINITY\" &gt;\n"
-" &lt;resource_set id=\"ordered-set-1\" sequential=\"true\" action=\"promote\"&gt;\n"
-" &lt;resource_ref id=\"A\"/&gt;\n"
-" &lt;resource_ref id=\"B\"/&gt;\n"
-" &lt;/resource_set&gt;\n"
-" &lt;resource_set id=\"ordered-set-2\" sequential=\"true\" action=\"start\"&gt;\n"
-" &lt;resource_ref id=\"C\"/&gt;\n"
-" &lt;resource_ref id=\"D\"/&gt;\n"
-" &lt;/resource_set&gt;\n"
-" &lt;/rsc_order&gt;\n"
-"&lt;/constraints&gt;"
+msgid "OCF_RESKEY_CRM_meta_notify_active_uname"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the above example, <literal>B</literal> cannot be promoted to a master role until <literal>A</literal> has been promoted. Additionally, resources <literal>C</literal> and <literal>D</literal> must wait until <literal>A</literal> and <literal>B</literal> have been promoted before they can start."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Multi-state Stickiness"
+msgid "Nodes on which resources are running <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>active_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>active_uname</secondary> </indexterm> <indexterm> <primary>active_uname</primary> </indexterm> <indexterm> <primary>active_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>resource-stickiness</primary><secondary>Multi-State</secondary> </indexterm> <indexterm> <primary>Multi-State</primary> </indexterm> As with regular clones, multi-state resources are slightly sticky by default. See <xref linkend=\"s-clone-stickiness\" /> for details."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Which Resource Instance is Promoted"
+msgid "The variables come in pairs, such as <literal>OCF_RESKEY_CRM_meta_notify_start_resource</literal> and <literal>OCF_RESKEY_CRM_meta_notify_start_uname</literal> and should be treated as an array of whitespace-separated elements."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "During the start operation, most resource agents should call the <literal>crm_master</literal> utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, <literal>master-max</literal>, and <literal>master-node-max</literal>, the instance(s) with the highest preference will be promoted."
+msgid "<literal>OCF_RESKEY_CRM_meta_notify_inactive_resource</literal> is an exception as the matching <literal>uname</literal> variable does not exist since inactive resources are not running on any node."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "An alternative is to create a location constraint that indicates which nodes are most preferred as masters."
+msgid "Thus in order to indicate that <literal>clone:0</literal> will be started on <literal>sles-1</literal>, <literal>clone:2</literal> will be started on <literal>sles-3</literal>, and <literal>clone:3</literal> will be started on <literal>sles-2</literal>, the cluster would set"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Explicitly preferring node1 to be promoted to master"
+msgid "Notification variables"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "&lt;rsc_location id=\"master-location\" rsc=\"myMasterRsc\"&gt;\n"
-" &lt;rule id=\"master-rule\" score=\"100\" role=\"Master\"&gt;\n"
-" &lt;expression id=\"master-exp\" attribute=\"#uname\" operation=\"eq\" value=\"node1\"/&gt;\n"
-" &lt;/rule&gt;\n"
-"&lt;/rsc_location&gt;"
+msgid "OCF_RESKEY_CRM_meta_notify_start_resource=\"clone:0 clone:2 clone:3\"\n"
+"OCF_RESKEY_CRM_meta_notify_start_uname=\"sles-1 sles-3 sles-2\""
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Interpretation of Notification Variables"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Requirements for Multi-state Resource Agents"
+msgid "Pre-notification (stop):"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since multi-state resources are an extension of cloned resources, all the requirements for resource agents that support clones are also requirements for resource agents that support multi-state resources."
+msgid "Active resources: <literal>$OCF_RESKEY_CRM_meta_notify_active_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Additionally, multi-state resources require two extra actions, <literal>demote</literal> and <literal>promote</literal>, which are responsible for changing the state of the resource. Like <literal>start</literal> and <literal>stop</literal>, they should return <literal>${OCF_SUCCESS}</literal> if they completed successfully or a relevant error code if they did not."
+msgid "Inactive resources: <literal>$OCF_RESKEY_CRM_meta_notify_inactive_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The states can mean whatever you wish, but when the resource is started, it must come up in the mode called <literal>slave</literal>. From there the cluster will decide which instances to promote to <literal>master</literal>."
+msgid "Resources to be started: <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to the clone requirements for monitor actions, agents must also <emphasis>accurately</emphasis> report which state they are in. The cluster relies on the agent to report its status (including role) accurately and does not indicate to the agent what role it currently believes it to be in."
+msgid "Resources to be stopped: <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Role implications of OCF return codes"
+msgid "Post-notification (stop) / Pre-notification (start):"
msgstr ""
-#. Tag: entry
+#. Tag: para
#, no-c-format
-msgid "Monitor Return Code"
+msgid "Active resources"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_NOT_RUNNING"
+msgid "<literal>$OCF_RESKEY_CRM_meta_notify_active_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stopped <indexterm> <primary>Return Code</primary><secondary>OCF_NOT_RUNNING</secondary> </indexterm> <indexterm> <primary>OCF_NOT_RUNNING</primary> </indexterm>"
+msgid "minus <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_SUCCESS"
+msgid "Inactive resources"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Running (Slave) <indexterm> <primary>Return Code</primary><secondary>OCF_SUCCESS</secondary> </indexterm> <indexterm> <primary>OCF_SUCCESS</primary> </indexterm>"
+msgid "<literal>$OCF_RESKEY_CRM_meta_notify_inactive_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_RUNNING_MASTER"
+msgid "plus <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Running (Master) <indexterm> <primary>Return Code</primary><secondary>OCF_RUNNING_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_RUNNING_MASTER</primary> </indexterm>"
+msgid "Resources that were started: <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "OCF_FAILED_MASTER"
+msgid "Resources that were stopped: <literal>$OCF_RESKEY_CRM_meta_notify_stop_resource</literal>"
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "Failed (Master) <indexterm> <primary>Return Code</primary><secondary>OCF_FAILED_MASTER</secondary> </indexterm> <indexterm> <primary>OCF_FAILED_MASTER</primary> </indexterm>"
+msgid "Post-notification (start):"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Other"
+msgid "Active resources:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Failed (Slave)"
+msgid "plus <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "Multi-state Notifications"
+msgid "Inactive resources:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like clones, supporting notifications requires the <literal>notify</literal> action to be implemented. If supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it."
+msgid "minus <literal>$OCF_RESKEY_CRM_meta_notify_start_resource</literal>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Environment variables supplied with multi-state notify actions <footnote><para>Emphasized variables are specific to <literal>Master</literal> resources, and all behave in the same manner as described for Clone resources.</para></footnote>"
+msgid "Extra Notifications for Promotable Clones"
msgstr ""
-#. Tag: para
+#. Tag: title
+#, no-c-format
+msgid "Extra environment variables supplied for promotable clones"
+msgstr ""
+
+#. Tag: entry
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_master_resource</emphasis>"
msgstr ""
-#. Tag: para
+#. Tag: entry
#, no-c-format
msgid "Resources that are running in <literal>Master</literal> mode <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>master_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>master_resource</secondary> </indexterm> <indexterm> <primary>master_resource</primary> </indexterm> <indexterm> <primary>master_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_slave_resource</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources that are running in <literal>Slave</literal> mode <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>slave_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>slave_resource</secondary> </indexterm> <indexterm> <primary>slave_resource</primary> </indexterm> <indexterm> <primary>slave_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_promote_resource</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources to be promoted <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>promote_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>promote_resource</secondary> </indexterm> <indexterm> <primary>promote_resource</primary> </indexterm> <indexterm> <primary>promote_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_demote_resource</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources to be demoted <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>demote_resource</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>demote_resource</secondary> </indexterm> <indexterm> <primary>demote_resource</primary> </indexterm> <indexterm> <primary>demote_resource</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_promote_uname</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nodes on which resources will be promoted <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>promote_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>promote_uname</secondary> </indexterm> <indexterm> <primary>promote_uname</primary> </indexterm> <indexterm> <primary>promote_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_demote_uname</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nodes on which resources will be demoted <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>demote_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>demote_uname</secondary> </indexterm> <indexterm> <primary>demote_uname</primary> </indexterm> <indexterm> <primary>demote_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_master_uname</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nodes on which resources are running in <literal>Master</literal> mode <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>master_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>master_uname</secondary> </indexterm> <indexterm> <primary>master_uname</primary> </indexterm> <indexterm> <primary>master_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>OCF_RESKEY_CRM_meta_notify_slave_uname</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nodes on which resources are running in <literal>Slave</literal> mode <indexterm> <primary>Environment Variable</primary><secondary>OCF_RESKEY_CRM_meta_notify_</secondary><tertiary>slave_uname</tertiary> </indexterm> <indexterm> <primary>OCF_RESKEY_CRM_meta_notify_</primary><secondary>slave_uname</secondary> </indexterm> <indexterm> <primary>slave_uname</primary> </indexterm> <indexterm> <primary>slave_uname</primary><secondary>Notification Environment Variable</secondary> </indexterm> <indexterm> <primary>Notification Environment Variable</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Proper Interpretation of Multi-state Notification Environment Variables"
+msgid "Interpretation of Promotable Notification Variables"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Pre-notification (demote):"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Active</literal> resources: <literal>$OCF_RESKEY_CRM_meta_notify_active_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Master</literal> resources: <literal>$OCF_RESKEY_CRM_meta_notify_master_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Slave</literal> resources: <literal>$OCF_RESKEY_CRM_meta_notify_slave_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources to be promoted: <literal>$OCF_RESKEY_CRM_meta_notify_promote_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources to be demoted: <literal>$OCF_RESKEY_CRM_meta_notify_demote_resource</literal>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Post-notification (demote) / Pre-notification (stop):"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Master</literal> resources:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>$OCF_RESKEY_CRM_meta_notify_master_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "minus <literal>$OCF_RESKEY_CRM_meta_notify_demote_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources that were demoted: <literal>$OCF_RESKEY_CRM_meta_notify_demote_resource</literal>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Post-notification (stop) / Pre-notification (start)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Active</literal> resources:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Slave</literal> resources:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>$OCF_RESKEY_CRM_meta_notify_slave_resource</literal>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Post-notification (start) / Pre-notification (promote)"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Post-notification (promote)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "plus <literal>$OCF_RESKEY_CRM_meta_notify_promote_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "minus <literal>$OCF_RESKEY_CRM_meta_notify_promote_resource</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources that were promoted: <literal>$OCF_RESKEY_CRM_meta_notify_promote_resource</literal>"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Monitoring Promotable Clone Resources"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The usual monitor actions are insufficient to monitor a promotable clone resource, because Pacemaker needs to verify not only that the resource is active, but also that its actual role matches its intended one."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Define two monitoring actions: the usual one will cover the slave role, and an additional one with <literal>role=\"master\"</literal> will cover the master role."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Monitoring both states of a promotable clone resource"
+msgstr ""
+
+#. Tag: programlisting
+#, no-c-format
+msgid "&lt;clone id=\"myMasterRsc\"&gt;\n"
+" &lt;meta_attributes id=\"myMasterRsc-meta\"&gt;\n"
+" &lt;nvpair name=\"promotable\" value=\"true\"/&gt;\n"
+" &lt;/meta_attributes&gt;\n"
+" &lt;primitive id=\"myRsc\" class=\"ocf\" type=\"myApp\" provider=\"myCorp\"&gt;\n"
+" &lt;operations&gt;\n"
+" &lt;op id=\"public-ip-slave-check\" name=\"monitor\" interval=\"60\"/&gt;\n"
+" &lt;op id=\"public-ip-master-check\" name=\"monitor\" interval=\"61\" role=\"Master\"/&gt;\n"
+" &lt;/operations&gt;\n"
+" &lt;/primitive&gt;\n"
+"&lt;/clone&gt;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "It is crucial that <emphasis>every</emphasis> monitor operation has a different interval! Pacemaker currently differentiates between operations only by resource and interval; so if (for example) a promotable clone resource had the same monitor interval for both roles, Pacemaker would ignore the role when checking the status — which would cause unexpected return codes, and therefore unnecessary complications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Determining Which Instance is Promoted"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker can choose a promotable clone instance to be promoted in one of two ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Promotion scores: These are node attributes set via the <literal>crm_master</literal> utility, which generally would be called by the resource agent’s start action if it supports promotable clones. This tool automatically detects both the resource and host, and should be used to set a preference for being promoted. Based on this, <literal>promoted-max</literal>, and <literal>promoted-node-max</literal>, the instance(s) with the highest preference will be promoted."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Constraints: Location constraints can indicate which nodes are most preferred as masters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Explicitly preferring node1 to be promoted to master"
+msgstr ""
+
+#. Tag: programlisting
+#, no-c-format
+msgid "&lt;rsc_location id=\"master-location\" rsc=\"myMasterRsc\"&gt;\n"
+" &lt;rule id=\"master-rule\" score=\"100\" role=\"Master\"&gt;\n"
+" &lt;expression id=\"master-exp\" attribute=\"#uname\" operation=\"eq\" value=\"node1\"/&gt;\n"
+" &lt;/rule&gt;\n"
+"&lt;/rsc_location&gt;"
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "Bundles - Isolated Environments"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm>"
+msgid "<indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker (version 1.1.17 and later) supports a special syntax for combining an isolated environment with the infrastructure support that it needs: the <emphasis>bundle</emphasis>."
+msgid "Pacemaker supports a special syntax for launching a <ulink url=\"https://en.wikipedia.org/wiki/Operating-system-level_virtualization\">container</ulink> with any infrastructure it requires: the <emphasis>bundle</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The only isolation technology currently supported by Pacemaker bundles is <ulink url=\"https://www.docker.com/\">Docker</ulink> containers. <footnote><para>Docker is a trademark of Docker, Inc. No endorsement by or association with Docker, Inc. is implied.</para></footnote>"
+msgid "Pacemaker bundles support <ulink url=\"https://www.docker.com/\">Docker</ulink> and <ulink url=\"https://coreos.com/rkt/\">rkt</ulink> container technologies. <footnote><para>Docker is a trademark of Docker, Inc. No endorsement by or association with Docker, Inc. is implied.</para></footnote>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A bundle for a containerized web server"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;bundle id=\"httpd-bundle\"&gt;\n"
" &lt;docker image=\"pcmk:http\" replicas=\"3\"/&gt;\n"
" &lt;network ip-range-start=\"192.168.122.131\"\n"
" host-netmask=\"24\"\n"
" host-interface=\"eth0\"&gt;\n"
" &lt;port-mapping id=\"httpd-port\" port=\"80\"/&gt;\n"
" &lt;/network&gt;\n"
" &lt;storage&gt;\n"
" &lt;storage-mapping id=\"httpd-syslog\"\n"
" source-dir=\"/dev/log\"\n"
" target-dir=\"/dev/log\"\n"
" options=\"rw\"/&gt;\n"
" &lt;storage-mapping id=\"httpd-root\"\n"
" source-dir=\"/srv/html\"\n"
" target-dir=\"/var/www/html\"\n"
" options=\"rw\"/&gt;\n"
" &lt;storage-mapping id=\"httpd-logs\"\n"
" source-dir-root=\"/var/log/pacemaker/bundles\"\n"
" target-dir=\"/etc/httpd/logs\"\n"
" options=\"rw\"/&gt;\n"
" &lt;/storage&gt;\n"
" &lt;primitive class=\"ocf\" id=\"httpd\" provider=\"heartbeat\" type=\"apache\"/&gt;\n"
"&lt;/bundle&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Bundle Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Bundle"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the bundle (required) <indexterm> <primary>id</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>bundle</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>description</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Arbitrary text (not used by Pacemaker) <indexterm> <primary>description</primary><secondary>bundle</secondary> </indexterm> <indexterm> <primary>bundle</primary> </indexterm> <indexterm> <primary>bundle</primary><secondary>Property</secondary><tertiary>description</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>description</secondary> </indexterm> <indexterm> <primary>description</primary> </indexterm>"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "Docker Properties"
+msgid "A bundle must contain exactly one <literal>&lt;docker&gt;</literal> or <literal>&lt;rkt&gt;</literal> element."
msgstr ""
-#. Tag: para
+#. Tag: title
#, no-c-format
-msgid "A bundle must contain exactly one <literal>&lt;docker&gt;</literal> element."
+msgid "Docker Properties"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Before configuring a bundle in Pacemaker, the user must install Docker and supply a fully configured Docker image on every node allowed to run the bundle."
+msgid "Before configuring a Docker bundle in Pacemaker, the user must install Docker and supply a fully configured Docker image on every node allowed to run the bundle."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker will create an implicit <literal>ocf:heartbeat:docker</literal> resource to manage a bundle’s Docker container."
+msgid "Pacemaker will create an implicit <literal>ocf:heartbeat:docker</literal> resource to manage a bundle’s Docker container. The user must ensure that resource agent is installed on every node allowed to run the bundle."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Bundle’s Docker Element"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>image</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Docker image tag (required) <indexterm> <primary>image</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>image</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>image</secondary> </indexterm> <indexterm> <primary>image</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>replicas</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Value of <literal>masters</literal> if that is positive, else 1"
+msgid "Value of <literal>promoted-max</literal> if that is positive, else 1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A positive integer specifying the number of container instances to launch <indexterm> <primary>replicas</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>replicas</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>replicas</secondary> </indexterm> <indexterm> <primary>replicas</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>replicas-per-host</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A positive integer specifying the number of container instances allowed to run on a single node <indexterm> <primary>replicas-per-host</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>replicas-per-host</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>replicas-per-host</secondary> </indexterm> <indexterm> <primary>replicas-per-host</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>masters</literal>"
+msgid "A non-negative integer that, if positive, indicates that the containerized service should be treated as a promotable service, with this many replicas allowed to run the service in the master role <indexterm> <primary>promoted-max</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>promoted-max</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>promoted-max</secondary> </indexterm> <indexterm> <primary>promoted-max</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "0"
+msgid "<literal>network</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A non-negative integer that, if positive, indicates that the containerized service should be treated as a multistate service, with this many replicas allowed to run the service in the master role <indexterm> <primary>masters</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>masters</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>masters</secondary> </indexterm> <indexterm> <primary>masters</primary> </indexterm>"
+msgid "If specified, this will be passed to <literal>docker run</literal> as the <ulink url=\"https://docs.docker.com/engine/reference/run/#network-settings\">network setting</ulink> for the Docker container. <indexterm> <primary>network</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>network</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>network</literal>"
+msgid "<literal>run-command</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If specified, this will be passed to <literal>docker run</literal> as the <ulink url=\"https://docs.docker.com/engine/reference/run/#network-settings\">network setting</ulink> for the Docker container. <indexterm> <primary>network</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>network</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm>"
+msgid "<literal>/usr/sbin/pacemaker-remoted</literal> if bundle contains a <literal>primitive</literal>, otherwise none"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>run-command</literal>"
+msgid "This command will be run inside the container when launching it (\"PID 1\"). If the bundle contains a <literal>primitive</literal>, this command <emphasis>must</emphasis> start pacemaker-remoted (but could, for example, be a script that does other stuff, too). If the container image has a pre-2.0.0 version of Pacemaker, set this to <literal>/usr/sbin/pacemaker_remoted</literal> (note the underbar instead of dash). <indexterm> <primary>run-command</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>run-command</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>run-command</secondary> </indexterm> <indexterm> <primary>run-command</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>/usr/sbin/pacemaker_remoted</literal> if bundle contains a <literal>primitive</literal>, otherwise none"
+msgid "<literal>options</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This command will be run inside the container when launching it (\"PID 1\"). If the bundle contains a <literal>primitive</literal>, this command <emphasis>must</emphasis> start pacemaker_remoted (but could, for example, be a script that does other stuff, too). <indexterm> <primary>network</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>network</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm>"
+msgid "Extra command-line options to pass to <literal>docker run</literal> <indexterm> <primary>options</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>options</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>options</secondary> </indexterm> <indexterm> <primary>options</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>options</literal>"
+msgid "For backward compatibility, <literal>masters</literal> is accepted as an alias for <literal>promoted-max</literal>, but is deprecated since 2.0.0, and support for it will be removed in a future version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "rkt Properties"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Extra command-line options to pass to <literal>docker run</literal> <indexterm> <primary>options</primary><secondary>Docker</secondary> </indexterm> <indexterm> <primary>Docker</primary> </indexterm> <indexterm> <primary>Docker</primary><secondary>Property</secondary><tertiary>options</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>options</secondary> </indexterm> <indexterm> <primary>options</primary> </indexterm>"
+msgid "Before configuring a rkt bundle in Pacemaker, the user must install rkt and supply a fully configured container image on every node allowed to run the bundle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker will create an implicit <literal>ocf:heartbeat:rkt</literal> resource to manage a bundle’s rkt container. The user must ensure that resource agent is installed on every node allowed to run the bundle."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Properties of a Bundle’s rkt Element"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Container image tag (required) <indexterm> <primary>image</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>image</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>image</secondary> </indexterm> <indexterm> <primary>image</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A positive integer specifying the number of container instances to launch <indexterm> <primary>replicas</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>replicas</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>replicas</secondary> </indexterm> <indexterm> <primary>replicas</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A positive integer specifying the number of container instances allowed to run on a single node <indexterm> <primary>replicas-per-host</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>replicas-per-host</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>replicas-per-host</secondary> </indexterm> <indexterm> <primary>replicas-per-host</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A non-negative integer that, if positive, indicates that the containerized service should be treated as a promotable service, with this many replicas allowed to run the service in the master role <indexterm> <primary>promoted-max</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>promoted-max</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>promoted-max</secondary> </indexterm> <indexterm> <primary>promoted-max</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If specified, this will be passed to <literal>rkt run</literal> as the network setting for the rkt container. <indexterm> <primary>network</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>network</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command will be run inside the container when launching it (\"PID 1\"). If the bundle contains a <literal>primitive</literal>, this command <emphasis>must</emphasis> start pacemaker-remoted (but could, for example, be a script that does other stuff, too). If the container image has a pre-2.0.0 version of Pacemaker, set this to <literal>/usr/sbin/pacemaker_remoted</literal> (note the underbar instead of dash). <indexterm> <primary>run-command</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>run-command</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>run-command</secondary> </indexterm> <indexterm> <primary>run-command</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extra command-line options to pass to <literal>rkt run</literal> <indexterm> <primary>options</primary><secondary>rkt</secondary> </indexterm> <indexterm> <primary>rkt</primary> </indexterm> <indexterm> <primary>rkt</primary><secondary>Property</secondary><tertiary>options</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>options</secondary> </indexterm> <indexterm> <primary>options</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Bundle Network Properties"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A bundle may optionally contain one <literal>&lt;network&gt;</literal> element. <indexterm> <primary>bundle</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Bundle’s Network Element"
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "<literal>add-host</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "TRUE"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If TRUE, and <literal>ip-range-start</literal> is used, Pacemaker will automatically ensure that <literal>/etc/hosts</literal> inside the containers has entries for each <link linkend=\"s-resource-bundle-note-replica-names\">replica name</link> and its assigned IP. <indexterm> <primary>add-host</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm> <indexterm> <primary>network</primary><secondary>Property</secondary><tertiary>add-host</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>add-host</secondary> </indexterm> <indexterm> <primary>add-host</primary> </indexterm>"
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "<literal>ip-range-start</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If specified, Pacemaker will create an implicit <literal>ocf:heartbeat:IPaddr2</literal> resource for each container instance, starting with this IP address, using up to <literal>replicas</literal> sequential addresses. These addresses can be used from the host’s network to reach the service inside the container, though it is not visible within the container itself. Only IPv4 addresses are currently supported. <indexterm> <primary>ip-range-start</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm> <indexterm> <primary>network</primary><secondary>Property</secondary><tertiary>ip-range-start</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>ip-range-start</secondary> </indexterm> <indexterm> <primary>ip-range-start</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>host-netmask</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "32"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>ip-range-start</literal> is specified, the IP addresses are created with this CIDR netmask (as a number of bits). <indexterm> <primary>host-netmask</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm> <indexterm> <primary>network</primary><secondary>Property</secondary><tertiary>host-netmask</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>host-netmask</secondary> </indexterm> <indexterm> <primary>host-netmask</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>host-interface</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>ip-range-start</literal> is specified, the IP addresses are created on this host interface (by default, it will be determined from the IP address). <indexterm> <primary>host-interface</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm> <indexterm> <primary>network</primary><secondary>Property</secondary><tertiary>host-interface</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>host-interface</secondary> </indexterm> <indexterm> <primary>host-interface</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>control-port</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the bundle contains a <literal>primitive</literal>, the cluster will use this integer TCP port for communication with Pacemaker Remote inside the container. This takes precedence over the value of any PCMK_remote_port environment variable set in the container image. This can allow a <literal>primitive</literal> to be specified without using <literal>ip-start-range</literal>, in which case <literal>replicas-per-host</literal> must be 1. <indexterm> <primary>control-port</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm> <indexterm> <primary>network</primary><secondary>Property</secondary><tertiary>control-port</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>control-port</secondary> </indexterm> <indexterm> <primary>control-port</primary> </indexterm>"
+msgid "3121"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If <literal>ip-range-start</literal> is used, Pacemaker will automatically ensure that <literal>/etc/hosts</literal> inside the containers has entries for each replica and its assigned IP. Replicas are named by the bundle id plus a dash and an integer counter starting with zero. For example, if a bundle named <literal>httpd-bundle</literal> has <literal>replicas=2</literal>, its containers will be named <literal>httpd-bundle-0</literal> and <literal>httpd-bundle-1</literal>."
+msgid "If the bundle contains a <literal>primitive</literal>, the cluster will use this integer TCP port for communication with Pacemaker Remote inside the container. Changing this is useful when the container is unable to listen on the default port, for example, when the container uses the host’s network rather than <literal>ip-range-start</literal> (in which case <literal>replicas-per-host</literal> must be 1), or when the bundle may run on a Pacemaker Remote node that is already listening on the default port. Any PCMK_remote_port environment variable set on the host or in the container is ignored for bundle connections. <indexterm> <primary>control-port</primary><secondary>network</secondary> </indexterm> <indexterm> <primary>network</primary> </indexterm> <indexterm> <primary>network</primary><secondary>Property</secondary><tertiary>control-port</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>control-port</secondary> </indexterm> <indexterm> <primary>control-port</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Replicas are named by the bundle id plus a dash and an integer counter starting with zero. For example, if a bundle named <literal>httpd-bundle</literal> has <literal>replicas=2</literal>, its containers will be named <literal>httpd-bundle-0</literal> and <literal>httpd-bundle-1</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Additionally, a <literal>&lt;network&gt;</literal> element may optionally contain one or more <literal>&lt;port-mapping&gt;</literal> elements. <indexterm> <primary>bundle</primary><secondary>network</secondary><tertiary>port-mapping</tertiary> </indexterm> <indexterm> <primary>network</primary><secondary>port-mapping</secondary> </indexterm> <indexterm> <primary>port-mapping</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Bundle’s Port-Mapping Element"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the port mapping (required) <indexterm> <primary>id</primary><secondary>port-mapping</secondary> </indexterm> <indexterm> <primary>port-mapping</primary> </indexterm> <indexterm> <primary>port-mapping</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>port</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If this is specified, connections to this TCP port number on the host network (on the container’s assigned IP address, if <literal>ip-range-start</literal> is specified) will be forwarded to the container network. Exactly one of <literal>port</literal> or <literal>range</literal> must be specified in a <literal>port-mapping</literal>. <indexterm> <primary>port</primary><secondary>port-mapping</secondary> </indexterm> <indexterm> <primary>port-mapping</primary> </indexterm> <indexterm> <primary>port-mapping</primary><secondary>Property</secondary><tertiary>port</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>port</secondary> </indexterm> <indexterm> <primary>port</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>internal-port</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "value of <literal>port</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>port</literal> and this are specified, connections to <literal>port</literal> on the host’s network will be forwarded to this port on the container network. <indexterm> <primary>internal-port</primary><secondary>port-mapping</secondary> </indexterm> <indexterm> <primary>port-mapping</primary> </indexterm> <indexterm> <primary>port-mapping</primary><secondary>Property</secondary><tertiary>internal-port</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>internal-port</secondary> </indexterm> <indexterm> <primary>internal-port</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>range</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If this is specified, connections to these TCP port numbers (expressed as <emphasis>first_port</emphasis>-<emphasis>last_port</emphasis>) on the host network (on the container’s assigned IP address, if <literal>ip-range-start</literal> is specified) will be forwarded to the same ports in the container network. Exactly one of <literal>port</literal> or <literal>range</literal> must be specified in a <literal>port-mapping</literal>. <indexterm> <primary>range</primary><secondary>port-mapping</secondary> </indexterm> <indexterm> <primary>port-mapping</primary> </indexterm> <indexterm> <primary>port-mapping</primary><secondary>Property</secondary><tertiary>range</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>range</secondary> </indexterm> <indexterm> <primary>range</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the bundle contains a <literal>primitive</literal>, Pacemaker will automatically map the <literal>control-port</literal>, so it is not necessary to specify that port in a <literal>port-mapping</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Bundle Storage Properties"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A bundle may optionally contain one <literal>&lt;storage&gt;</literal> element. A <literal>&lt;storage&gt;</literal> element has no properties of its own, but may contain one or more <literal>&lt;storage-mapping&gt;</literal> elements. <indexterm> <primary>bundle</primary><secondary>storage</secondary><tertiary>storage-mapping</tertiary> </indexterm> <indexterm> <primary>storage</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Bundle’s Storage-Mapping Element"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the storage mapping (required) <indexterm> <primary>id</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm> <indexterm> <primary>storage-mapping</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>source-dir</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The absolute path on the host’s filesystem that will be mapped into the container. Exactly one of <literal>source-dir</literal> and <literal>source-dir-root</literal> must be specified in a <literal>storage-mapping</literal>. <indexterm> <primary>source-dir</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm> <indexterm> <primary>storage-mapping</primary><secondary>Property</secondary><tertiary>source-dir</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>source-dir</secondary> </indexterm> <indexterm> <primary>source-dir</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>source-dir-root</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The start of a path on the host’s filesystem that will be mapped into the container, using a different subdirectory on the host for each container instance. Exactly one of <literal>source-dir</literal> and <literal>source-dir-root</literal> must be specified in a <literal>storage-mapping</literal>. <indexterm> <primary>source-dir-root</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm> <indexterm> <primary>storage-mapping</primary><secondary>Property</secondary><tertiary>source-dir-root</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>source-dir-root</secondary> </indexterm> <indexterm> <primary>source-dir-root</primary> </indexterm>"
+msgid "The start of a path on the host’s filesystem that will be mapped into the container, using a different subdirectory on the host for each container instance. The subdirectory will be named the same as the <link linkend=\"s-resource-bundle-note-replica-names\">replica name</link>. Exactly one of <literal>source-dir</literal> and <literal>source-dir-root</literal> must be specified in a <literal>storage-mapping</literal>. <indexterm> <primary>source-dir-root</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm> <indexterm> <primary>storage-mapping</primary><secondary>Property</secondary><tertiary>source-dir-root</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>source-dir-root</secondary> </indexterm> <indexterm> <primary>source-dir-root</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target-dir</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The path name within the container where the host storage will be mapped (required) <indexterm> <primary>target-dir</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm> <indexterm> <primary>storage-mapping</primary><secondary>Property</secondary><tertiary>target-dir</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>target-dir</secondary> </indexterm> <indexterm> <primary>target-dir</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "File system mount options to use when mapping the storage <indexterm> <primary>options</primary><secondary>storage-mapping</secondary> </indexterm> <indexterm> <primary>storage-mapping</primary> </indexterm> <indexterm> <primary>storage-mapping</primary><secondary>Property</secondary><tertiary>options</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>options</secondary> </indexterm> <indexterm> <primary>options</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the bundle contains a <literal>primitive</literal>, Pacemaker will automatically map the equivalent of <literal>source-dir=/etc/pacemaker/authkey target-dir=/etc/pacemaker/authkey</literal> and <literal>source-dir-root=/var/log/pacemaker/bundles target-dir=/var/log</literal> into the container, so it is not necessary to specify those paths in a <literal>storage-mapping</literal>. Newer versions of <literal>ocf:heartbeat:docker</literal> will automatically create the source directories if they do not exist, but the user may want to ensure they exist beforehand."
+msgid "Pacemaker does not define the behavior if the source directory does not already exist on the host. However, it is expected that the container technology and/or its resource agent will create the source directory in that case."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the bundle contains a <literal>primitive</literal>, Pacemaker will automatically map the equivalent of <literal>source-dir=/etc/pacemaker/authkey target-dir=/etc/pacemaker/authkey</literal> and <literal>source-dir-root=/var/log/pacemaker/bundles target-dir=/var/log</literal> into the container, so it is not necessary to specify those paths in a <literal>storage-mapping</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>PCMK_authkey_location</literal> environment variable must not be set to anything other than the default of <literal>/etc/pacemaker/authkey</literal> on any node in the cluster."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Bundle Primitive"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A bundle may optionally contain one <literal>&lt;primitive&gt;</literal> resource (see <xref linkend=\"s-resource-primitive\" />). The primitive may have operations, instance attributes and meta-attributes defined, as usual."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bundle contains a primitive resource, the container image must include the Pacemaker Remote daemon, and either <literal>ip-range-start</literal> or <literal>control-port</literal> must be configured in the bundle. Pacemaker will create an implicit <literal>ocf:pacemaker:remote</literal> resource for the connection, launch Pacemaker Remote within the container, and monitor and manage the primitive resource via Pacemaker Remote."
+msgid "If a bundle contains a primitive resource, the container image must include the Pacemaker Remote daemon, and at least one of <literal>ip-range-start</literal> or <literal>control-port</literal> must be configured in the bundle. Pacemaker will create an implicit <literal>ocf:pacemaker:remote</literal> resource for the connection, launch Pacemaker Remote within the container, and monitor and manage the primitive resource via Pacemaker Remote."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the bundle has more than one container instance (replica), the primitive resource will function as an implicit clone (see <xref linkend=\"s-resource-clone\" />) — a promotable clone if the bundle has <literal>masters</literal> greater than zero (see <xref linkend=\"s-resource-promotable\" />)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Containers in bundles with a <literal>primitive</literal> must have an accessible networking environment, so that Pacemaker on the cluster nodes can contact Pacemaker Remote inside the container. For example, the Docker option <literal>--net=none</literal> should not be used with a <literal>primitive</literal>. The default (using a distinct network space inside the container) works in combination with <literal>ip-range-start</literal>. If the Docker option <literal>--net=host</literal> is used (making the container share the host’s network space), a unique <literal>control-port</literal> should be specified for each bundle. Any firewall must allow access to the <literal>control-port</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Bundle Node Attributes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the bundle has a <literal>primitive</literal>, the primitive’s resource agent may want to set node attributes such as <link linkend=\"s-promotion-scores\">promotion scores</link>. However, with containers, it is not apparent which node should get the attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If the container uses shared storage that is the same no matter which node the container is hosted on, then it is appropriate to use the promotion score on the bundle node itself."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the bundle has more than one container instance (replica), the primitive resource will function as an implicit clone (see <xref linkend=\"s-resource-clone\" />) — a multistate clone if the bundle has <literal>masters</literal> greater than zero (see <xref linkend=\"s-resource-multistate\" />)."
+msgid "On the other hand, if the container uses storage exported from the underlying host, then it may be more appropriate to use the promotion score on the underlying host."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Containers in bundles with a <literal>primitive</literal> must have an accessible networking environment, so that Pacemaker can contact Pacemaker Remote inside the container. For example, the Docker option <literal>--net=none</literal> should not be used with a <literal>primitive</literal>. The default (using a distinct network space inside the container) works with <literal>ip-range-start</literal>. If the Docker option <literal>--net=host</literal> is used (making the container share the host’s network space), a unique <literal>control-port</literal> should be specified for each bundle."
+msgid "Since this depends on the particular situation, the <literal>container-attribute-target</literal> resource meta-attribute allows the user to specify which approach to use. If it is set to <literal>host</literal>, then user-defined node attributes will be checked on the underlying host. If it is anything else, the local node (in this case the bundle node) is used as usual."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This only applies to user-defined attributes; the cluster will always check the local node for cluster-defined attributes such as <literal>#uname</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If <literal>container-attribute-target</literal> is <literal>host</literal>, the cluster will pass additional environment variables to the primitive’s resource agent that allow it to set node attributes appropriately: <literal>container_attribute_target</literal> (identical to the meta-attribute value) and <literal>physical_host</literal> (the name of the underlying host)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "It is up to the resource agent to check for the additional variables and use them when setting node attributes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Bundle Meta-Attributes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Any meta-attribute set on a bundle will be inherited by the bundle’s primitive and any resources implicitly created by Pacemaker for the bundle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This includes options such as <literal>priority</literal>, <literal>target-role</literal>, and <literal>is-managed</literal>. See <xref linkend=\"s-resource-options\" /> for more information."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Limitations of Bundles"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Currently, bundles may not be cloned, or included in groups or colocation constraints. This includes the bundle’s primitive and any resources implicitly created by Pacemaker for the bundle."
+msgid "Restarting pacemaker while a bundle is unmanaged or the cluster is in maintenance mode may cause the bundle to fail."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Bundles may not be cloned or included in groups. This includes the bundle’s primitive and any resources implicitly created by Pacemaker for the bundle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Bundles do not have instance attributes, utilization attributes, or operations, though a bundle’s primitive may have them."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bundles do not have instance attributes, meta-attributes, utilization attributes, or operations of their own, though a primitive included in a bundle may."
+msgid "A bundle with a primitive can run on a Pacemaker Remote node only if the bundle uses a distinct <literal>control-port</literal>."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Alerts.pot b/doc/Pacemaker_Explained/pot/Ch-Alerts.pot
index 3a363f258c..06e66c3af8 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Alerts.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Alerts.pot
@@ -1,578 +1,593 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Alerts"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<anchor id=\"ch-alerts\" xreflabel=\"Chapter 7, Alerts\"></anchor> <indexterm> <primary>Resource</primary><secondary>Alerts</secondary> </indexterm> <indexterm> <primary>Alerts</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Alerts</emphasis> (available since Pacemaker 1.1.15) may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.)."
+msgid "<emphasis>Alerts</emphasis> may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert Agents"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As with resource agents, the cluster calls an external program (an <emphasis>alert agent</emphasis>) to handle alerts. The cluster passes information about the event to the agent via environment variables. Agents can do anything desired with this information (send an e-mail, log to a file, update a monitoring system, etc.)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Simple alert configuration"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"my-alert\" path=\"/path/to/my-script.sh\" /&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, the cluster will call <literal>my-script.sh</literal> for each event."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Multiple alert agents may be configured; the cluster will call all of them for each event."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alert agents will be called only on cluster nodes. They will be called for events involving Pacemaker Remote nodes, but they will never be called <emphasis>on</emphasis> those nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert Recipients"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Usually alerts are directed towards a recipient. Thus each alert may be additionally configured with one or more recipients. The cluster will call the agent separately for each recipient."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert configuration with recipient"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"my-alert\" path=\"/path/to/my-script.sh\"&gt;\n"
" &lt;recipient id=\"my-alert-recipient\" value=\"some-address\"/&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the above example, the cluster will call <literal>my-script.sh</literal> for each event, passing the recipient <literal>some-address</literal> as an environment variable."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The recipient may be anything the alert agent can recognize — an IP address, an e-mail address, a file name, whatever the particular agent supports."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert Meta-Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As with resource agents, meta-attributes can be configured for alert agents to affect how Pacemaker calls them."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Meta-Attributes of an Alert"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Meta-Attribute"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>timestamp-format</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "%H:%M:%S.%06N"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Format the cluster will use when sending the event’s timestamp to the agent. This is a string as used with the <literal>date(1)</literal> command. <indexterm> <primary>Alert</primary><secondary>Option</secondary><tertiary>timestamp-format</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>timestamp-format</secondary> </indexterm> <indexterm> <primary>timestamp-format</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "30s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the alert agent does not complete within this amount of time, it will be terminated. <indexterm> <primary>Alert</primary><secondary>Option</secondary><tertiary>timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>timeout</secondary> </indexterm> <indexterm> <primary>timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Meta-attributes can be configured per alert agent and/or per recipient."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert configuration with meta-attributes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"my-alert\" path=\"/path/to/my-script.sh\"&gt;\n"
" &lt;meta_attributes id=\"my-alert-attributes\"&gt;\n"
" &lt;nvpair id=\"my-alert-attributes-timeout\" name=\"timeout\"\n"
" value=\"15s\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"&gt;\n"
" &lt;meta_attributes id=\"my-alert-recipient1-attributes\"&gt;\n"
" &lt;nvpair id=\"my-alert-recipient1-timestamp-format\"\n"
" name=\"timestamp-format\" value=\"%D %H:%M\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/recipient&gt;\n"
" &lt;recipient id=\"my-alert-recipient2\" value=\"otheruser@example.com\"&gt;\n"
" &lt;meta_attributes id=\"my-alert-recipient2-attributes\"&gt;\n"
" &lt;nvpair id=\"my-alert-recipient2-timestamp-format\"\n"
" name=\"timestamp-format\" value=\"%c\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/recipient&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the above example, the <literal>my-script.sh</literal> will get called twice for each event, with each call using a 15-second timeout. One call will be passed the recipient <literal>someuser@example.com</literal> and a timestamp in the format <literal>%D %H:%M</literal>, while the other call will be passed the recipient <literal>otheruser@example.com</literal> and a timestamp in the format <literal>%c</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert Instance Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As with resource agents, agent-specific configuration values may be configured as instance attributes. These will be passed to the agent as additional environment variables. The number, names and allowed values of these instance attributes are completely up to the particular agent."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert configuration with instance attributes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"my-alert\" path=\"/path/to/my-script.sh\"&gt;\n"
" &lt;meta_attributes id=\"my-alert-attributes\"&gt;\n"
" &lt;nvpair id=\"my-alert-attributes-timeout\" name=\"timeout\"\n"
" value=\"15s\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;instance_attributes id=\"my-alert-options\"&gt;\n"
" &lt;nvpair id=\"my-alert-options-debug\" name=\"debug\" value=\"false\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert Filters"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Coming in 1.1.18</emphasis>"
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "By default, an alert agent will be called for node events, fencing events, and resource events. An agent may choose to ignore certain types of events, but there is still the overhead of calling it for those events. To eliminate that overhead, you may select which types of events the agent should receive."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert configuration to receive only node events and fencing events"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"my-alert\" path=\"/path/to/my-script.sh\"&gt;\n"
" &lt;select&gt;\n"
" &lt;select_nodes /&gt;\n"
" &lt;select_fencing /&gt;\n"
" &lt;/select&gt;\n"
" &lt;recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The possible options within <literal>&lt;select&gt;</literal> are <literal>&lt;select_nodes&gt;</literal>, <literal>&lt;select_fencing&gt;</literal>, <literal>&lt;select_resources&gt;</literal>, and <literal>&lt;select_attributes&gt;</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "With <literal>&lt;select_attributes&gt;</literal> (the only event type not enabled by default), the agent will receive alerts when a node attribute changes. If you wish the agent to be called only when certain attributes change, you can configure that as well."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Alert configuration to be called when certain node attributes change"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"my-alert\" path=\"/path/to/my-script.sh\"&gt;\n"
" &lt;select&gt;\n"
" &lt;select_attributes&gt;\n"
" &lt;attribute id=\"alert-standby\" name=\"standby\" /&gt;\n"
" &lt;attribute id=\"alert-shutdown\" name=\"shutdown\" /&gt;\n"
" &lt;/select_attributes&gt;\n"
" &lt;/select&gt;\n"
" &lt;recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node attribute alerts are currently considered experimental. Alerts may be limited to attributes set via attrd_updater, and agents may be called multiple times with the same attribute value."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using the Sample Alert Agents"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker provides several sample alert agents, installed in <literal>/usr/share/pacemaker/alerts</literal> by default."
msgstr ""
#. Tag: para
#, no-c-format
msgid "While these sample scripts may be copied and used as-is, they are provided mainly as templates to be edited to suit your purposes. See their source code for the full set of instance attributes they support."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sending cluster events as SNMP traps"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"snmp_alert\" path=\"/path/to/alert_snmp.sh\"&gt;\n"
" &lt;instance_attributes id=\"config_for_alert_snmp\"&gt;\n"
" &lt;nvpair id=\"trap_node_states\" name=\"trap_node_states\" value=\"all\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;meta_attributes id=\"config_for_timestamp\"&gt;\n"
" &lt;nvpair id=\"ts_fmt\" name=\"timestamp-format\"\n"
" value=\"%Y-%m-%d,%H:%M:%S.%01N\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;recipient id=\"snmp_destination\" value=\"192.168.1.2\"/&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
"&lt;/configuration&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sending cluster events as e-mails"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid " &lt;configuration&gt;\n"
" &lt;alerts&gt;\n"
" &lt;alert id=\"smtp_alert\" path=\"/path/to/alert_smtp.sh\"&gt;\n"
" &lt;instance_attributes id=\"config_for_alert_smtp\"&gt;\n"
" &lt;nvpair id=\"email_sender\" name=\"email_sender\"\n"
" value=\"donotreply@example.com\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;recipient id=\"smtp_destination\" value=\"admin@example.com\"/&gt;\n"
" &lt;/alert&gt;\n"
" &lt;/alerts&gt;\n"
" &lt;/configuration&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Writing an Alert Agent"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Environment variables passed to alert agents"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Environment Variable"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_kind</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The type of alert (<literal>node</literal>, <literal>fencing</literal>, <literal>resource</literal>, or <literal>attribute</literal>) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>kind</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>kind</secondary> </indexterm> <indexterm> <primary>kind</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_version</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The version of Pacemaker sending the alert <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>version</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>version</secondary> </indexterm> <indexterm> <primary>version</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_recipient</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The configured recipient <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>recipient</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>recipient</secondary> </indexterm> <indexterm> <primary>recipient</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_node_sequence</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A sequence number increased whenever an alert is being issued on the local node, which can be used to reference the order in which alerts have been issued by Pacemaker. An alert for an event that happened later in time reliably has a higher sequence number than alerts for earlier events. Be aware that this number has no cluster-wide meaning. <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_node_</secondary><tertiary>sequence</tertiary> </indexterm> <indexterm> <primary>CRM_alert_node_</primary><secondary>sequence</secondary> </indexterm> <indexterm> <primary>sequence</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_timestamp</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A timestamp created prior to executing the agent, in the format specified by the <literal>timestamp-format</literal> meta-attribute. This allows the agent to have a reliable, high-precision time of when the event occurred, regardless of when the agent itself was invoked (which could potentially be delayed due to system load, etc.). <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>timestamp</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>timestamp</secondary> </indexterm> <indexterm> <primary>timestamp</primary> </indexterm>"
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "<literal>CRM_alert_timestamp_epoch</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The same time as <literal>CRM_alert_timestamp</literal>, expressed as the integer number of seconds since January 1, 1970. This (along with <literal>CRM_alert_timestamp_usec</literal>) can be useful for alert agents that need to format time in a specific way rather than let the user configure it. <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>timestamp_epoch</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>timestamp_epoch</secondary> </indexterm> <indexterm> <primary>timestamp_epoch</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>CRM_alert_timestamp_usec</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The same time as <literal>CRM_alert_timestamp</literal>, expressed as the integer number of microseconds since <literal>CRM_alert_timestamp_epoch</literal>. <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>timestamp_usec</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>timestamp_usec</secondary> </indexterm> <indexterm> <primary>timestamp_usec</primary> </indexterm>"
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Name of affected node <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>node</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>node</secondary> </indexterm> <indexterm> <primary>node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_desc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Detail about event. For <literal>node</literal> alerts, this is the node’s current state (<literal>member</literal> or <literal>lost</literal>). For <literal>fencing</literal> alerts, this is a summary of the requested fencing operation, including origin, target, and fencing operation error code, if any. For <literal>resource</literal> alerts, this is a readable string equivalent of <literal>CRM_alert_status</literal>. <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>desc</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>desc</secondary> </indexterm> <indexterm> <primary>desc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_nodeid</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "ID of node whose status changed (provided with <literal>node</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>nodeid</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>nodeid</secondary> </indexterm> <indexterm> <primary>nodeid</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_task</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The requested fencing or resource operation (provided with <literal>fencing</literal> and <literal>resource</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>task</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>task</secondary> </indexterm> <indexterm> <primary>task</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_rc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The numerical return code of the fencing or resource operation (provided with <literal>fencing</literal> and <literal>resource</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>rc</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>rc</secondary> </indexterm> <indexterm> <primary>rc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_rsc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of the affected resource (<literal>resource</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>rsc</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>rsc</secondary> </indexterm> <indexterm> <primary>rsc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_interval</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The interval of the resource operation (<literal>resource</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>interval</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>interval</secondary> </indexterm> <indexterm> <primary>interval</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_target_rc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The expected numerical return code of the operation (<literal>resource</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>target_rc</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>target_rc</secondary> </indexterm> <indexterm> <primary>target_rc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_status</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A numerical code used by Pacemaker to represent the operation result (<literal>resource</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>status</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>status</secondary> </indexterm> <indexterm> <primary>status</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_attribute_name</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of the node attribute that changed (<literal>attribute</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>attribute_name</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>attribute_name</secondary> </indexterm> <indexterm> <primary>attribute_name</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>CRM_alert_attribute_value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The new value of the node attribute that changed (<literal>attribute</literal> alerts only) <indexterm> <primary>Environment Variable</primary><secondary>CRM_alert_</secondary><tertiary>attribute_value</tertiary> </indexterm> <indexterm> <primary>CRM_alert_</primary><secondary>attribute_value</secondary> </indexterm> <indexterm> <primary>attribute_value</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Special concerns when writing alert agents:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alert agents may be called with no recipient (if none is configured), so the agent must be able to handle this situation, even if it only exits in that case. (Users may modify the configuration in stages, and add a recipient later.)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If more than one recipient is configured for an alert, the alert agent will be called once per recipient. If an agent is not able to run concurrently, it should be configured with only a single recipient. The agent is free, however, to interpret the recipient as a list."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When a cluster event occurs, all alerts are fired off at the same time as separate processes. Depending on how many alerts and recipients are configured, and on what is done within the alert agents, a significant load burst may occur. The agent could be written to take this into consideration, for example by queueing resource-intensive actions into some other instance, instead of directly executing them."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alert agents are run as the <literal>hacluster</literal> user, which has a minimal set of permissions. If an agent requires additional privileges, it is recommended to configure <literal>sudo</literal> to allow the agent to run the necessary commands as another user with the appropriate privileges."
msgstr ""
#. Tag: para
#, no-c-format
msgid "As always, take care to validate and sanitize user-configured parameters, such as CRM_alert_timestamp (whose content is specified by the user-configured timestamp-format), CRM_alert_recipient, and all instance attributes. Mostly this is needed simply to protect against configuration errors, but if some user can modify the CIB without having hacluster-level access to the cluster nodes, it is a potential security concern as well, to avoid the possibility of code injection."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The alerts interface is designed to be backward compatible with the external scripts interface used by the <literal>ocf:pacemaker:ClusterMon</literal> resource, which is now deprecated. To preserve this compatibility, the environment variables passed to alert agents are available prepended with <literal>CRM_notify_</literal> as well as <literal>CRM_alert_</literal>. One break in compatibility is that ClusterMon ran external scripts as the <literal>root</literal> user, while alert agents are run as the <literal>hacluster</literal> user."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Constraints.pot b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot
index 6f6cc5b6fd..37f9cad7f1 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Constraints.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot
@@ -1,1071 +1,1101 @@
#
# 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"
+"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 "Resource Constraints"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraints</secondary> </indexterm> <indexterm> <primary>Constraints</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Scores"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Scores of all kinds are integral to how the cluster works. Practically everything from moving a resource to deciding which resource to stop in a degraded cluster is achieved by manipulating scores in some way."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Scores are calculated per resource and node. Any node with a negative score for a resource can’t run that resource. The cluster places a resource on the node with the highest score for it."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Infinity Math"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker implements <literal>INFINITY</literal> (or equivalently, <literal>+INFINITY</literal>) internally as a score of 1,000,000. Addition and subtraction with it follow these three basic rules:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any value + <literal>INFINITY</literal> = <literal>INFINITY</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Any value - <literal>INFINITY</literal> = <literal>-INFINITY</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>INFINITY</literal> - <literal>INFINITY</literal> = <literal>-INFINITY</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "What if you want to use a score higher than 1,000,000? Typically this possibility arises when someone wants to base the score on some external metric that might go above 1,000,000."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The short answer is you can’t."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The long answer is it is sometimes possible work around this limitation creatively. You may be able to set the score to some computed value based on the external metric rather than use the metric directly. For nodes, you can store the metric as a node attribute, and query the attribute when computing the score (possibly as part of a custom resource agent)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Deciding Which Nodes a Resource Can Run On"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraints</secondary><tertiary>Location</tertiary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary> </indexterm> <indexterm> <primary>Location</primary> </indexterm> <emphasis>Location constraints</emphasis> tell the cluster which nodes a resource can run on."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are two alternative strategies. One way is to say that, by default, resources can run anywhere, and then the location constraints specify nodes that are not allowed (an <emphasis>opt-out</emphasis> cluster). The other way is to start with nothing able to run anywhere, and use location constraints to selectively enable allowed nodes (an <emphasis>opt-in</emphasis> cluster)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Whether you should choose opt-in or opt-out depends on your personal preference and the make-up of your cluster. If most of your resources can run on most of the nodes, then an opt-out arrangement is likely to result in a simpler configuration. On the other-hand, if most resources can only run on a small subset of nodes, an opt-in configuration might be simpler."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Location Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a rsc_location Constraint"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the constraint <indexterm> <primary>id</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of the resource to which this constraint applies <indexterm> <primary>rsc</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>rsc</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>rsc</secondary> </indexterm> <indexterm> <primary>rsc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc-pattern</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A regular expression matching the names of resources to which this constraint applies, if <literal>rsc</literal> is not specified; if the regular expression contains submatches and the constraint is governed by a rule (see <xref linkend=\"ch-rules\" />), the submatches can be referenced as <literal>%0</literal> through <literal>%9</literal> in the rule’s <literal>score-attribute</literal> or a rule expression’s <literal>attribute</literal> <emphasis>(since 1.1.16)</emphasis> <indexterm> <primary>rsc-pattern</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>rsc-pattern</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>rsc-pattern</secondary> </indexterm> <indexterm> <primary>rsc-pattern</primary> </indexterm>"
+msgid "An extended regular expression (as defined in <ulink url=\"http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04\">POSIX</ulink>) matching the names of resources to which this constraint applies, if <literal>rsc</literal> is not specified; if the regular expression contains submatches and the constraint is governed by a rule (see <xref linkend=\"ch-rules\" />), the submatches can be referenced as <literal>%0</literal> through <literal>%9</literal> in the rule’s <literal>score-attribute</literal> or a rule expression’s <literal>attribute</literal> <indexterm> <primary>rsc-pattern</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>rsc-pattern</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>rsc-pattern</secondary> </indexterm> <indexterm> <primary>rsc-pattern</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A node’s name <indexterm> <primary>node</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>node</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>node</secondary> </indexterm> <indexterm> <primary>node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>score</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Positive values indicate a preference for running the affected resource(s) on this node — the higher the value, the stronger the preference. Negative values indicate the resource(s) should avoid this node (a value of <literal>-INFINITY</literal> changes \"should\" to \"must\"). <indexterm> <primary>score</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>resource-discovery</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "always"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Whether Pacemaker should perform resource discovery (that is, check whether the resource is already running) for this resource on this node. This should normally be left as the default, so that rogue instances of a service can be stopped when they are running where they are not supposed to be. However, there are two situations where disabling resource discovery is a good idea: when a service is not installed on a node, discovery might return an error (properly written OCF agents will not, so this is usually only seen with other agent types); and when Pacemaker Remote is used to scale a cluster to hundreds of nodes, limiting resource discovery to allowed nodes can significantly boost performance. <emphasis>(since 1.1.13)</emphasis>"
+msgid "Whether Pacemaker should perform resource discovery (that is, check whether the resource is already running) for this resource on this node. This should normally be left as the default, so that rogue instances of a service can be stopped when they are running where they are not supposed to be. However, there are two situations where disabling resource discovery is a good idea: when a service is not installed on a node, discovery might return an error (properly written OCF agents will not, so this is usually only seen with other agent types); and when Pacemaker Remote is used to scale a cluster to hundreds of nodes, limiting resource discovery to allowed nodes can significantly boost performance."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>always:</literal> Always perform resource discovery for the specified resource on this node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>never:</literal> Never perform resource discovery for the specified resource on this node. This option should generally be used with a -INFINITY score, although that is not strictly required."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>exclusive:</literal> Perform resource discovery for the specified resource only on this node (and other nodes similarly marked as <literal>exclusive</literal>). Multiple location constraints using <literal>exclusive</literal> discovery for the same resource across different nodes creates a subset of nodes resource-discovery is exclusive to. If a resource is marked for <literal>exclusive</literal> discovery on one or more nodes, that resource is only allowed to be placed within that subset of nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource Discovery</primary><secondary>Location Constraints</secondary> </indexterm> <indexterm> <primary>Location Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Location</secondary><tertiary>Resource Discovery</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>Resource Discovery</secondary> </indexterm> <indexterm> <primary>Resource Discovery</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Setting resource-discovery to <literal>never</literal> or <literal>exclusive</literal> removes Pacemaker’s ability to detect and stop unwanted instances of a service running where it’s not supposed to be. It is up to the system administrator (you!) to make sure that the service can <emphasis>never</emphasis> be active on nodes without resource-discovery (such as by leaving the relevant software uninstalled)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Asymmetrical \"Opt-In\" Clusters"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Asymmetrical Opt-In Clusters</primary> </indexterm> <indexterm> <primary>Cluster Type</primary><secondary>Asymmetrical Opt-In</secondary> </indexterm> <indexterm> <primary>Asymmetrical Opt-In</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To create an opt-in cluster, start by preventing resources from running anywhere by default:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute --name symmetric-cluster --update false"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then start enabling nodes. The following fragment says that the web server prefers <emphasis role=\"strong\">sles-1</emphasis>, the database prefers <emphasis role=\"strong\">sles-2</emphasis> and both can fail over to <emphasis role=\"strong\">sles-3</emphasis> if their most preferred node fails."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Opt-in location constraints for two resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"200\"/&gt;\n"
" &lt;rsc_location id=\"loc-2\" rsc=\"Webserver\" node=\"sles-3\" score=\"0\"/&gt;\n"
" &lt;rsc_location id=\"loc-3\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/&gt;\n"
" &lt;rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-3\" score=\"0\"/&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Symmetrical \"Opt-Out\" Clusters"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Symmetrical Opt-Out Clusters</primary> </indexterm> <indexterm> <primary>Cluster Type</primary><secondary>Symmetrical Opt-Out</secondary> </indexterm> <indexterm> <primary>Symmetrical Opt-Out</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To create an opt-out cluster, start by allowing resources to run anywhere by default:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute --name symmetric-cluster --update true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Opt-out location constraints for two resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"200\"/&gt;\n"
" &lt;rsc_location id=\"loc-2-dont-run\" rsc=\"Webserver\" node=\"sles-2\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"loc-3-dont-run\" rsc=\"Database\" node=\"sles-1\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "What if Two Nodes Have the Same Score"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If two nodes have the same score, then the cluster will choose one. This choice may seem random and may not be what was intended, however the cluster was not given enough information to know any better."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Constraints where a resource prefers two nodes equally"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"loc-2\" rsc=\"Webserver\" node=\"sles-2\" score=\"INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"loc-3\" rsc=\"Database\" node=\"sles-1\" score=\"500\"/&gt;\n"
" &lt;rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-2\" score=\"300\"/&gt;\n"
" &lt;rsc_location id=\"loc-5\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, assuming no other constraints and an inactive cluster, <literal>Webserver</literal> would probably be placed on <literal>sles-1</literal> and <literal>Database</literal> on <literal>sles-2</literal>. It would likely have placed <literal>Webserver</literal> based on the node’s uname and <literal>Database</literal> based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Specifying the Order in which Resources Should Start/Stop"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraints</secondary><tertiary>Ordering</tertiary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary> </indexterm> <indexterm> <primary>Ordering</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Start Order</secondary> </indexterm> <indexterm> <primary>Start Order</primary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Ordering constraints</emphasis> tell the cluster the order in which resources should start."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Ordering constraints affect <emphasis>only</emphasis> the ordering of resources; they do <emphasis>not</emphasis> require that the resources be placed on the same node. If you want resources to be started on the same node <emphasis>and</emphasis> in a specific order, you need both an ordering constraint <emphasis>and</emphasis> a colocation constraint (see <xref linkend=\"s-resource-colocation\" />), or alternatively, a group (see <xref linkend=\"group-resources\" />)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordering Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a rsc_order Constraint"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the constraint <indexterm> <primary>id</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>first</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Name of the resource that the <literal>then</literal> resource depends on <indexterm> <primary>first</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>first</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>first</secondary> </indexterm> <indexterm> <primary>first</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>then</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Name of the dependent resource <indexterm> <primary>then</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>then</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>then</secondary> </indexterm> <indexterm> <primary>then</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>first-action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "start"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The action that the <literal>first</literal> resource must complete before <literal>then-action</literal> can be initiated for the <literal>then</literal> resource. Allowed values: <literal>start</literal>, <literal>stop</literal>, <literal>promote</literal>, <literal>demote</literal>. <indexterm> <primary>first-action</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>first-action</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>first-action</secondary> </indexterm> <indexterm> <primary>first-action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>then-action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "value of <literal>first-action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The action that the <literal>then</literal> resource can execute only after the <literal>first-action</literal> on the <literal>first</literal> resource has completed. Allowed values: <literal>start</literal>, <literal>stop</literal>, <literal>promote</literal>, <literal>demote</literal>. <indexterm> <primary>then-action</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>then-action</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>then-action</secondary> </indexterm> <indexterm> <primary>then-action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>kind</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How to enforce the constraint. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Optional:</literal> Just a suggestion. Only applies if both resources are executing the specified actions. Any change in state by the <literal>first</literal> resource will have no effect on the <literal>then</literal> resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Mandatory:</literal> Always. If <literal>first</literal> does not perform <literal>first-action</literal>, <literal>then</literal> will not be allowed to performed <literal>then-action</literal>. If <literal>first</literal> is restarted, <literal>then</literal> (if running) will be stopped beforehand and started afterward."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Serialize:</literal> Ensure that no two stop/start actions occur concurrently for the resources. <literal>First</literal> and <literal>then</literal> can start in either order, but one must complete starting before the other can be started. A typical use case is when resource start-up puts a high load on the host."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>kind</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Ordering</secondary><tertiary>kind</tertiary> </indexterm> <indexterm> <primary>Ordering</primary><secondary>kind</secondary> </indexterm> <indexterm> <primary>kind</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>symmetrical</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "TRUE"
+msgid "TRUE for <literal>Mandatory</literal> and <literal>Optional</literal> kinds. FALSE for <literal>Serialize</literal> kind."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If true, the reverse of the constraint applies for the opposite action (for example, if B starts after A starts, then B stops before A stops). <indexterm> <primary>symmetrical</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Ordering Constraints</primary><secondary>symmetrical</secondary> </indexterm> <indexterm> <primary>symmetrical</primary> </indexterm>"
+msgid "If true, the reverse of the constraint applies for the opposite action (for example, if B starts after A starts, then B stops before A stops). <literal>Serialize</literal> orders cannot be symmetrical. <indexterm> <primary>symmetrical</primary><secondary>Ordering Constraints</secondary> </indexterm> <indexterm> <primary>Ordering Constraints</primary> </indexterm> <indexterm> <primary>Ordering Constraints</primary><secondary>symmetrical</secondary> </indexterm> <indexterm> <primary>symmetrical</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>Promote</literal> and <literal>demote</literal> apply to the master role of <link linkend=\"s-resource-multistate\">multi-state</link> resources."
+msgid "<literal>Promote</literal> and <literal>demote</literal> apply to the master role of <link linkend=\"s-resource-promotable\">promotable</link> resources."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Optional and mandatory ordering"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Here is an example of ordering constraints where <literal>Database</literal> <emphasis>must</emphasis> start before <literal>Webserver</literal>, and <literal>IP</literal> <emphasis>should</emphasis> start before <literal>Webserver</literal> if they both need to be started:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Optional and mandatory ordering constraints"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
"&lt;rsc_order id=\"order-1\" first=\"IP\" then=\"Webserver\" kind=\"Optional\"/&gt;\n"
"&lt;rsc_order id=\"order-2\" first=\"Database\" then=\"Webserver\" kind=\"Mandatory\" /&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Because the above example lets <literal>symmetrical</literal> default to TRUE, <literal>Webserver</literal> must be stopped before <literal>Database</literal> can be stopped, and <literal>Webserver</literal> should be stopped before <literal>IP</literal> if they both need to be stopped."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Placing Resources Relative to other Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraints</secondary><tertiary>Colocation</tertiary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary> </indexterm> <indexterm> <primary>Colocation</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Location Relative to other Resources</secondary> </indexterm> <indexterm> <primary>Location Relative to other Resources</primary> </indexterm> <emphasis>Colocation constraints</emphasis> tell the cluster that the location of one resource depends on the location of another one."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Colocation has an important side-effect: it affects the order in which resources are assigned to a node. Think about it: You can’t place A relative to B unless you know where B is. <footnote><para> While the human brain is sophisticated enough to read the constraint in any order and choose the correct one depending on the situation, the cluster is not quite so smart. Yet. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "So when you are creating colocation constraints, it is important to consider whether you should colocate A with B, or B with A."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another thing to keep in mind is that, assuming A is colocated with B, the cluster will take into account A’s preferences when deciding which node to choose for B."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For a detailed look at exactly how this occurs, see <ulink url=\"http://clusterlabs.org/doc/Colocation_Explained.pdf\">Colocation Explained</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Colocation constraints affect <emphasis>only</emphasis> the placement of resources; they do <emphasis>not</emphasis> require that the resources be started in a particular order. If you want resources to be started on the same node <emphasis>and</emphasis> in a specific order, you need both an ordering constraint (see <xref linkend=\"s-resource-ordering\" />) <emphasis>and</emphasis> a colocation constraint, or alternatively, a group (see <xref linkend=\"group-resources\" />)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Colocation Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a rsc_colocation Constraint"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A unique name for the constraint. <indexterm> <primary>id</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
+msgid "A unique name for the constraint (required). <indexterm> <primary>id</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of a resource that should be located relative to <literal>with-rsc</literal>. <indexterm> <primary>rsc</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>rsc</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>rsc</secondary> </indexterm> <indexterm> <primary>rsc</primary> </indexterm>"
+msgid "The name of a resource that should be located relative to <literal>with-rsc</literal> (required). <indexterm> <primary>rsc</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>rsc</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>rsc</secondary> </indexterm> <indexterm> <primary>rsc</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>with-rsc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the resource used as the colocation target. The cluster will decide where to put this resource first and then decide where to put <literal>rsc</literal>. <indexterm> <primary>with-rsc</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>with-rsc</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>with-rsc</secondary> </indexterm> <indexterm> <primary>with-rsc</primary> </indexterm>"
+msgid "The name of the resource used as the colocation target. The cluster will decide where to put this resource first and then decide where to put <literal>rsc</literal> (required). <indexterm> <primary>with-rsc</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>with-rsc</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>with-rsc</secondary> </indexterm> <indexterm> <primary>with-rsc</primary> </indexterm>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>node-attribute</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "#uname"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The node attribute that must be the same on the node running <literal>rsc</literal> and the node running <literal>with-rsc</literal> for the constraint to be satisfied. (For details, see <xref linkend=\"s-coloc-attribute\" />.) <indexterm> <primary>node-attribute</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>node-attribute</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>node-attribute</secondary> </indexterm> <indexterm> <primary>node-attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Positive values indicate the resources should run on the same node. Negative values indicate the resources should run on different nodes. Values of +/- <literal>INFINITY</literal> change \"should\" to \"must\". <indexterm> <primary>score</primary><secondary>Colocation Constraints</secondary> </indexterm> <indexterm> <primary>Colocation Constraints</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Colocation</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Colocation</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mandatory Placement"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Mandatory placement occurs when the constraint’s score is <literal>+INFINITY</literal> or <literal>-INFINITY</literal>. In such cases, if the constraint can’t be satisfied, then the <literal>rsc</literal> resource is not permitted to run. For <literal>score=INFINITY</literal>, this includes cases where the <literal>with-rsc</literal> resource is not active."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you need resource <literal>A</literal> to always run on the same machine as resource <literal>B</literal>, you would add the following constraint:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mandatory colocation constraint for two resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_colocation id=\"colocate\" rsc=\"A\" with-rsc=\"B\" score=\"INFINITY\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Remember, because <literal>INFINITY</literal> was used, if <literal>B</literal> can’t run on any of the cluster nodes (for whatever reason) then <literal>A</literal> will not be allowed to run. Whether <literal>A</literal> is running or not has no effect on <literal>B</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Alternatively, you may want the opposite — that <literal>A</literal> <emphasis>cannot</emphasis> run on the same machine as <literal>B</literal>. In this case, use <literal>score=\"-INFINITY\"</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mandatory anti-colocation constraint for two resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_colocation id=\"anti-colocate\" rsc=\"A\" with-rsc=\"B\" score=\"-INFINITY\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Again, by specifying <literal>-INFINITY</literal>, the constraint is binding. So if the only place left to run is where <literal>B</literal> already is, then <literal>A</literal> may not run anywhere."
msgstr ""
#. Tag: para
#, no-c-format
msgid "As with <literal>INFINITY</literal>, <literal>B</literal> can run even if <literal>A</literal> is stopped. However, in this case <literal>A</literal> also can run if <literal>B</literal> is stopped, because it still meets the constraint of <literal>A</literal> and <literal>B</literal> not running on the same node."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advisory Placement"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If mandatory placement is about \"must\" and \"must not\", then advisory placement is the \"I’d prefer if\" alternative. For constraints with scores greater than <literal>-INFINITY</literal> and less than <literal>INFINITY</literal>, the cluster will try to accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "As in life, where if enough people prefer something it effectively becomes mandatory, advisory colocation constraints can combine with other elements of the configuration to behave as if they were mandatory."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advisory colocation constraint for two resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_colocation id=\"colocate-maybe\" rsc=\"A\" with-rsc=\"B\" score=\"500\"/&gt;"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Colocation by Node Attribute"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>node-attribute</literal> property of a colocation constraints allows you to express the requirement, \"these resources must be on similar nodes\"."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you have two Storage Area Networks (SANs) that are not controlled by the cluster, and each node is connected to one or the other. You may have two resources <literal>r1</literal> and <literal>r2</literal> such that <literal>r2</literal> needs to use the same SAN as <literal>r1</literal>, but doesn’t necessarily have to be on the same exact node. In such a case, you could define a <link linkend=\"s-node-attributes\">node attribute</link> named <literal>san</literal>, with the value <literal>san1</literal> or <literal>san2</literal> on each node as appropriate. Then, you could colocate <literal>r2</literal> with <literal>r1</literal> using <literal>node-attribute</literal> set to <literal>san</literal>."
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "Resource Sets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Resource sets</emphasis> allow multiple resources to be affected by a single constraint."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A set of 3 resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;resource_set id=\"resource-set-example\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
"&lt;/resource_set&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource sets are valid inside <literal>rsc_location</literal>, <literal>rsc_order</literal> (see <xref linkend=\"s-resource-sets-ordering\" />), <literal>rsc_colocation</literal> (see <xref linkend=\"s-resource-sets-colocation\" />), and <literal>rsc_ticket</literal> (see <xref linkend=\"s-ticket-constraints\" />) constraints."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A resource set has a number of properties that can be set, though not all have an effect in all contexts."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a resource_set"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the set <indexterm> <primary>id</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>sequential</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Whether the members of the set must be acted on in order. Meaningful within <literal>rsc_order</literal> and <literal>rsc_colocation</literal>. <indexterm> <primary>sequential</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>sequential</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>sequential</secondary> </indexterm> <indexterm> <primary>sequential</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>require-all</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Whether all members of the set must be active before continuing. With the current implementation, the cluster may continue even if only one member of the set is started, but if more than one member of the set is starting at the same time, the cluster will still wait until all of those have started before continuing (this may change in future versions). Meaningful within <literal>rsc_order</literal>. <emphasis>(since 1.1.7)</emphasis> <indexterm> <primary>require-all</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>require-all</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>require-all</secondary> </indexterm> <indexterm> <primary>require-all</primary> </indexterm>"
+msgid "Whether all members of the set must be active before continuing. With the current implementation, the cluster may continue even if only one member of the set is started, but if more than one member of the set is starting at the same time, the cluster will still wait until all of those have started before continuing (this may change in future versions). Meaningful within <literal>rsc_order</literal>. <indexterm> <primary>require-all</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>require-all</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>require-all</secondary> </indexterm> <indexterm> <primary>require-all</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Limit the effect of the constraint to the specified role. Meaningful within <literal>rsc_location</literal>, <literal>rsc_colocation</literal> and <literal>rsc_ticket</literal>. <indexterm> <primary>role</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Limit the effect of the constraint to the specified action. Meaningful within <literal>rsc_order</literal>. <indexterm> <primary>action</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>action</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>action</secondary> </indexterm> <indexterm> <primary>action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Use a specific score for this set within the constraint. <indexterm> <primary>score</primary><secondary>Resource Sets</secondary> </indexterm> <indexterm> <primary>Resource Sets</primary> </indexterm> <indexterm> <primary>Constraints</primary><secondary>Resource Sets</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Resource Sets</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordering Sets of Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A common situation is for an administrator to create a chain of ordered resources, such as:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A chain of ordered resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_order id=\"order-1\" first=\"A\" then=\"B\" /&gt;\n"
" &lt;rsc_order id=\"order-2\" first=\"B\" then=\"C\" /&gt;\n"
" &lt;rsc_order id=\"order-3\" first=\"C\" then=\"D\" /&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of the four resources' start order for the above constraints"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordered Set"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To simplify this situation, resource sets (see <xref linkend=\"s-resource-sets\" />) can be used within ordering constraints:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A chain of ordered resources expressed as a set"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_order id=\"order-1\"&gt;\n"
" &lt;resource_set id=\"ordered-set-example\" sequential=\"true\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_order&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "While the set-based format is not less verbose, it is significantly easier to get right and maintain."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you use a higher-level tool, pay attention to how it exposes this functionality. Depending on the tool, creating a set <literal>A B</literal> may be equivalent to <literal>A then B</literal>, or <literal>B then A</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordering Multiple Sets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The syntax can be expanded to allow sets of resources to be ordered relative to each other, where the members of each individual set may be ordered or unordered (controlled by the <literal>sequential</literal> property). In the example below, <literal>A</literal> and <literal>B</literal> can both start in parallel, as can <literal>C</literal> and <literal>D</literal>, however <literal>C</literal> and <literal>D</literal> can only start once <emphasis>both</emphasis> <literal>A</literal> <emphasis>and</emphasis> <literal>B</literal> are active."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ordered sets of unordered resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_order id=\"order-1\"&gt;\n"
" &lt;resource_set id=\"ordered-set-1\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"ordered-set-2\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_order&gt;\n"
" &lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of the start order for two ordered sets of unordered resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Of course either set — or both sets — of resources can also be internally ordered (by setting <literal>sequential=\"true\"</literal>) and there is no limit to the number of sets that can be specified."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advanced use of set ordering - Three ordered sets, two of which are internally unordered"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_order id=\"order-1\"&gt;\n"
" &lt;resource_set id=\"ordered-set-1\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"ordered-set-2\" sequential=\"true\"&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"ordered-set-3\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"E\"/&gt;\n"
" &lt;resource_ref id=\"F\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_order&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation of the start order for the three sets defined above"
msgstr ""
#. Tag: para
#, no-c-format
msgid "An ordered set with <literal>sequential=false</literal> makes sense only if there is another set in the constraint. Otherwise, the constraint has no effect."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Set OR Logic"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The unordered set logic discussed so far has all been \"AND\" logic. To illustrate this take the 3 resource set figure in the previous section. Those sets can be expressed, <literal>(A and B) then (C) then (D) then (E and F)</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Say for example we want to change the first set, <literal>(A and B)</literal>, to use \"OR\" logic so the sets look like this: <literal>(A or B) then (C) then (D) then (E and F)</literal>. This functionality can be achieved through the use of the <literal>require-all</literal> option. This option defaults to TRUE which is why the \"AND\" logic is used by default. Setting <literal>require-all=false</literal> means only one resource in the set needs to be started before continuing on to the next set."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Set \"OR\" logic: Three ordered sets, where the first set is internally unordered with \"OR\" logic"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_order id=\"order-1\"&gt;\n"
" &lt;resource_set id=\"ordered-set-1\" sequential=\"false\" require-all=\"false\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"ordered-set-2\" sequential=\"true\"&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"ordered-set-3\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"E\"/&gt;\n"
" &lt;resource_ref id=\"F\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_order&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "An ordered set with <literal>require-all=false</literal> makes sense only in conjunction with <literal>sequential=false</literal>. Think of it like this: <literal>sequential=false</literal> modifies the set to be an unordered set using \"AND\" logic by default, and adding <literal>require-all=false</literal> flips the unordered set’s \"AND\" logic to \"OR\" logic."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Colocating Sets of Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another common situation is for an administrator to create a set of colocated resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "One way to do this would be to define a resource group (see <xref linkend=\"group-resources\" />), but that cannot always accurately express the desired state."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another way would be to define each relationship as an individual constraint, but that causes a constraint explosion as the number of resources and combinations grow. An example of this approach:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Chain of colocated resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_colocation id=\"coloc-1\" rsc=\"D\" with-rsc=\"C\" score=\"INFINITY\"/&gt;\n"
" &lt;rsc_colocation id=\"coloc-2\" rsc=\"C\" with-rsc=\"B\" score=\"INFINITY\"/&gt;\n"
" &lt;rsc_colocation id=\"coloc-3\" rsc=\"B\" with-rsc=\"A\" score=\"INFINITY\"/&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To make things easier, resource sets (see <xref linkend=\"s-resource-sets\" />) can be used within colocation constraints. As with the chained version, a resource that can’t be active prevents any resource that must be colocated with it from being active. For example, if <literal>B</literal> is not able to run, then both <literal>C</literal> and by inference <literal>D</literal> must also remain stopped. Here is an example <literal>resource_set</literal>:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Equivalent colocation chain expressed using <literal>resource_set</literal>"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_colocation id=\"coloc-1\" score=\"INFINITY\" &gt;\n"
" &lt;resource_set id=\"colocated-set-example\" sequential=\"true\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_colocation&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you use a higher-level tool, pay attention to how it exposes this functionality. Depending on the tool, creating a set <literal>A B</literal> may be equivalent to <literal>A with B</literal>, or <literal>B with A</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This notation can also be used to tell the cluster that sets of resources must be colocated relative to each other, where the individual members of each set may or may not depend on each other being active (controlled by the <literal>sequential</literal> property)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In this example, <literal>A</literal>, <literal>B</literal>, and <literal>C</literal> will each be colocated with <literal>D</literal>. <literal>D</literal> must be active, but any of <literal>A</literal>, <literal>B</literal>, or <literal>C</literal> may be inactive without affecting any other resources."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using colocated sets to specify a common peer"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_colocation id=\"coloc-1\" score=\"INFINITY\" &gt;\n"
" &lt;resource_set id=\"colocated-set-1\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"colocated-set-2\" sequential=\"true\"&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_colocation&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A colocated set with <literal>sequential=false</literal> makes sense only if there is another set in the constraint. Otherwise, the constraint has no effect."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There is no inherent limit to the number and size of the sets used. The only thing that matters is that in order for any member of one set in the constraint to be active, all members of sets listed after it must also be active (and naturally on the same node); and if a set has <literal>sequential=\"true\"</literal>, then in order for one member of that set to be active, all members listed before it must also be active."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If desired, you can restrict the dependency to instances of multistate resources that are in a specific role, using the set’s <literal>role</literal> property."
+msgid "If desired, you can restrict the dependency to instances of promotable clone resources that are in a specific role, using the set’s <literal>role</literal> property."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Colocation chain in which the members of the middle set have no interdependencies, and the last listed set (which the cluster places first) is restricted to instances in master status."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_colocation id=\"coloc-1\" score=\"INFINITY\" &gt;\n"
" &lt;resource_set id=\"colocated-set-1\" sequential=\"true\"&gt;\n"
" &lt;resource_ref id=\"B\"/&gt;\n"
" &lt;resource_ref id=\"A\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"colocated-set-2\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"C\"/&gt;\n"
" &lt;resource_ref id=\"D\"/&gt;\n"
" &lt;resource_ref id=\"E\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"colocated-set-3\" sequential=\"true\" role=\"Master\"&gt;\n"
" &lt;resource_ref id=\"G\"/&gt;\n"
" &lt;resource_ref id=\"F\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;/rsc_colocation&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Visual representation the above example (resources to the left are placed first)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pay close attention to the order in which resources and sets are listed. While the colocation dependency for members of any one set is last-to-first, the colocation dependency for multiple sets is first-to-last. In the above example, <literal>B</literal> is colocated with <literal>A</literal>, but <literal>colocated-set-1</literal> is colocated with <literal>colocated-set-2</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Unlike ordered sets, colocated sets do not use the <literal>require-all</literal> option."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Intro.pot b/doc/Pacemaker_Explained/pot/Ch-Intro.pot
index 0277bbcf0c..a15a99f61e 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Intro.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Intro.pot
@@ -1,284 +1,359 @@
#
# 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"
+"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 "Read-Me-First"
msgstr ""
#. Tag: title
#, no-c-format
msgid "The Scope of this Document"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this, it will focus exclusively on the XML syntax used to configure the CIB."
+msgid "This document is intended to be an exhaustive reference for configuring Pacemaker."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For those that are allergic to XML, there exist several unified shells and GUIs for Pacemaker. However these tools will not be covered at all in this document <footnote><para>I hope, however, that the concepts explained here make the functionality of these tools more easily understood.</para></footnote> , precisely because they hide the XML."
+msgid "To achieve this, it focuses on the XML syntax used to configure the CIB. For those that are allergic to XML, multiple higher-level front-ends (both command-line and GUI) are available. These tools will not be covered at all in this document <footnote><para> I hope, however, that the concepts explained here make the functionality of these tools more easily understood. </para></footnote>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Additionally, this document is NOT a step-by-step how-to guide for configuring a specific clustering scenario."
+msgid "Users may be interested in other parts of the <ulink url=\"https://www.clusterlabs.org/pacemaker/doc/\">Pacemaker documentation set</ulink>, such as <emphasis>Clusters from Scratch</emphasis>, a step-by-step guide to setting up an example cluster, and <emphasis>Pacemaker Administration</emphasis>, a guide to maintaining a cluster."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What Is <emphasis>Pacemaker</emphasis>?"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Although such guides exist, <footnote><para>For example, see the <ulink url=\"http://www.clusterlabs.org/doc/\">Clusters from Scratch</ulink> guide.</para></footnote> the purpose of this document is to provide an understanding of the building blocks that can be used to construct any type of Pacemaker cluster."
+msgid "<emphasis role=\"strong\">Pacemaker</emphasis> is a high-availability <emphasis>cluster resource manager</emphasis> — software that runs on a set of hosts (a <emphasis>cluster</emphasis> of <emphasis>nodes</emphasis>) in order to minimize downtime of desired services (<emphasis>resources</emphasis>). <footnote><para> <emphasis>Cluster</emphasis> is sometimes used in other contexts to refer to hosts grouped together for other purposes, such as high-performance computing (HPC), but Pacemaker is not intended for those purposes. </para></footnote>"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "What Is <emphasis>Pacemaker</emphasis>?"
+msgid "Pacemaker’s key features include:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker is a <emphasis>cluster resource manager</emphasis>, that is, a logic responsible for a life-cycle of deployed software — indirectly perhaps even whole systems or their interconnections — under its control within a set of computers (a.k.a. <emphasis>nodes</emphasis>) and driven by prescribed rules."
+msgid "Detection of and recovery from node- and service-level failures"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It achieves maximum availability for your cluster services (a.k.a. <emphasis>resources</emphasis>) by detecting and recovering from node- and resource-level failures by making use of the messaging and membership capabilities provided by your preferred cluster infrastructure (either <ulink url=\"http://www.corosync.org/\">Corosync</ulink> or <ulink url=\"http://linux-ha.org/wiki/Heartbeat\">Heartbeat</ulink>), and possibly by utilizing other parts of the overall cluster stack."
+msgid "Ability to ensure data integrity by fencing faulty nodes"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For <emphasis role=\"strong\">the goal of minimal downtime</emphasis> a term <emphasis>high availability</emphasis> was coined and together with its acronym, <emphasis>HA</emphasis>, is well-established in the sector. To differentiate this sort of clusters from high performance computing (<emphasis>HPC</emphasis>) ones, should a context require it (apparently, not the case in this document), using <emphasis>HA cluster</emphasis> is an option."
+msgid "Support for one or more nodes per cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker’s key features include:"
+msgid "Support for multiple resource interface standards (anything that can be scripted can be clustered)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Detection and recovery of node and service-level failures"
+msgid "Support (but no requirement) for shared storage"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Storage agnostic, no requirement for shared storage"
+msgid "Support for practically any redundancy configuration (active/passive, N+1, etc.)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Resource agnostic, anything that can be scripted can be clustered"
+msgid "Automatically replicated configuration that can be updated from any node"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports <emphasis>fencing</emphasis> (also referred to as the <emphasis>STONITH</emphasis> acronym, <link linkend=\"s-intro-stonith\">deciphered</link> later on) for ensuring data integrity"
+msgid "Ability to specify cluster-wide relationships between services, such as ordering, colocation and anti-colocation"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports large and small clusters"
+msgid "Support for advanced service types, such as <emphasis>clones</emphasis> (services that need to be active on multiple nodes), <emphasis>stateful resources</emphasis> (clones that can run in one of two modes), and containerized services"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports both quorate and resource-driven clusters"
+msgid "Unified, scriptable cluster management tools"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fencing"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Supports practically any redundancy configuration"
+msgid "<emphasis>Fencing</emphasis>, also known as <emphasis>STONITH</emphasis> (an acronym for Shoot The Other Node In The Head), is the ability to ensure that it is not possible for a node to be running a service. This is accomplished via <emphasis>fence devices</emphasis> such as intelligent power switches that cut power to the target, or intelligent network switches that cut the target’s access to the local network."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Automatically replicated configuration that can be updated from any node"
+msgid "Pacemaker represents fence devices as a special class of resource."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Ability to specify cluster-wide service ordering, colocation and anti-colocation"
+msgid "A cluster cannot safely recover from certain failure conditions, such as an unresponsive node, without fencing."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Cluster Architecture"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Support for advanced service types"
+msgid "At a high level, a cluster can viewed as having these parts (which together are often referred to as the <emphasis>cluster stack</emphasis>):"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Clones: for services which need to be active on multiple nodes"
+msgid "<emphasis role=\"strong\">Resources:</emphasis> These are the reason for the cluster’s being — the services that need to be kept highly available."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Multi-state: for services with multiple modes (e.g. master/slave, primary/secondary)"
+msgid "<emphasis role=\"strong\">Resource agents:</emphasis> These are scripts or operating system components that start, stop, and monitor resources, given a set of resource parameters. These provide a uniform interface between Pacemaker and the managed services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unified, scriptable cluster management tools"
+msgid "<emphasis role=\"strong\">Fence agents:</emphasis> These are scripts that execute node fencing actions, given a target and fence device parameters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster membership layer:</emphasis> This component provides reliable messaging, membership, and quorum information about the cluster. Currently, Pacemaker supports <ulink url=\"http://www.corosync.org/\">Corosync</ulink> as this layer."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster resource manager:</emphasis> Pacemaker provides the brain that processes and reacts to events that occur in the cluster. These events may include nodes joining or leaving the cluster; resource events caused by failures, maintenance, or scheduled activities; and other administrative actions. To achieve the desired availability, Pacemaker may start and stop resources and fence nodes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis role=\"strong\">Cluster tools:</emphasis> These provide an interface for users to interact with the cluster. Various command-line and graphical (GUI) interfaces are available."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most managed services are not, themselves, cluster-aware. However, many popular open-source cluster filesystems make use of a common <emphasis>Distributed Lock Manager</emphasis> (DLM), which makes direct use of Corosync for its messaging and membership capabilities and Pacemaker for the ability to fence nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example Cluster Stack"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Pacemaker Architecture"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At the highest level, the cluster is made up of three pieces:"
+msgid "Pacemaker itself is composed of multiple daemons that work together:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">Non-cluster-aware components</emphasis>. These pieces include the resources themselves; scripts that start, stop and monitor them; and a local daemon that masks the differences between the different standards these scripts implement. Even though interactions of these resources when run as multiple instances can resemble a distributed system, they still lack the proper HA mechanisms and/or autonomous cluster-wide governance as subsumed in the following item."
+msgid "pacemakerd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">Resource management</emphasis>. Pacemaker provides the brain that processes and reacts to events regarding the cluster. These events include nodes joining or leaving the cluster; resource events caused by failures, maintenance and scheduled activities; and other administrative actions. Pacemaker will compute the ideal state of the cluster and plot a path to achieve it after any of these events. This may include moving resources, stopping nodes and even forcing them offline with remote power switches."
+msgid "pacemaker-attrd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">Low-level infrastructure</emphasis>. Projects like <emphasis>Corosync</emphasis>, <emphasis>CMAN</emphasis> and <emphasis>Heartbeat</emphasis> provide reliable messaging, membership and quorum information about the cluster."
+msgid "pacemaker-based"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems.<footnote><para> Even though Pacemaker also supports Heartbeat, the filesystems need to use the stack for messaging and membership, and Corosync seems to be what they’re standardizing on. Technically, it would be possible for them to support Heartbeat as well, but there seems little interest in this. </para></footnote>"
+msgid "pacemaker-controld"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Due to past standardization within the cluster filesystem community, cluster filesystems make use of a common <emphasis>distributed lock manager</emphasis>, which makes use of Corosync for its messaging and membership capabilities (which nodes are up/down) and Pacemaker for fencing services."
+msgid "pacemaker-execd"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "The Pacemaker Stack"
+msgid "pacemaker-fenced"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "pacemaker-schedulerd"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Internal Components"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker itself is composed of five key components:"
+msgid "The Pacemaker master process (pacemakerd) spawns all the other daemons, and respawns them if they unexpectedly exit."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Cluster Information Base</emphasis> (<emphasis>CIB</emphasis>)"
+msgid "The <emphasis>Cluster Information Base</emphasis> (CIB) is an <ulink url=\"https://en.wikipedia.org/wiki/XML\">XML</ulink> representation of the cluster’s configuration and the state of all nodes and resources. The <emphasis>CIB manager</emphasis> (pacemaker-based) keeps the CIB synchronized across the cluster, and handles requests to modify it."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Cluster Resource Management daemon</emphasis> (<emphasis>CRMd</emphasis>)"
+msgid "The attribute manager (pacemaker-attrd) maintains a database of attributes for all nodes, keeps it synchronized across the cluster, and handles requests to modify them. These attributes are usually recorded in the CIB."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Local Resource Management daemon</emphasis> (<emphasis>LRMd</emphasis>)"
+msgid "Given a snapshot of the CIB as input, the <emphasis>scheduler</emphasis> (pacemaker-schedulerd) determines what actions are necessary to achieve the desired state of the cluster."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis>Policy Engine</emphasis> (<emphasis>PEngine</emphasis> or <emphasis>PE</emphasis>)"
+msgid "The <emphasis>local executor</emphasis> (pacemaker-execd) handles requests to execute resource agents on the local cluster node, and returns the result."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Fencing daemon (<emphasis>STONITHd</emphasis>)"
+msgid "The <emphasis>fencer</emphasis> (pacemaker-fenced) handles requests to fence nodes. Given a target node, the fencer decides which cluster node(s) should execute which fencing device(s), and calls the necessary fencing agents (either directly, or via requests to the fencer peers on other nodes), and returns the result."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CIB uses XML to represent both the cluster’s configuration and current state of all resources in the cluster. The contents of the CIB are automatically kept in sync across the entire cluster and are used by the PEngine to compute the ideal state of the cluster and how it should be achieved."
+msgid "The <emphasis>controller</emphasis> (pacemaker-controld) is Pacemaker’s coordinator, maintaining a consistent view of the cluster membership and orchestrating all the other components."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This list of instructions is then fed to the <emphasis>Designated Controller</emphasis> (<emphasis>DC</emphasis>). Pacemaker centralizes all cluster decision making by electing one of the CRMd instances to act as a master. Should the elected CRMd process (or the node it is on) fail, a new one is quickly established."
+msgid "Pacemaker centralizes cluster decision-making by electing one of the controller instances as the <emphasis>Designated Controller</emphasis> (<emphasis>DC</emphasis>). Should the elected DC process (or the node it is on) fail, a new one is quickly established. The DC responds to cluster events by taking a current snapshot of the CIB, feeding it to the scheduler, then asking the executors (either directly on the local node, or via requests to controller peers on other nodes) and the fencer to execute any necessary actions."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Old daemon names"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The DC carries out the PEngine’s instructions in the required order by passing them to either the Local Resource Management daemon (LRMd) or CRMd peers on other nodes via the cluster messaging infrastructure (which in turn passes them on to their LRMd process)."
+msgid "The Pacemaker daemons were renamed in version 2.0. You may still find references to the old names, especially in documentation targeted to version 1.1."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Old name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "New name"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The peer nodes all report the results of their operations back to the DC and, based on the expected and actual results, will either execute any actions that needed to wait for the previous one to complete, or abort processing and ask the PEngine to recalculate the ideal cluster state based on the unexpected results."
+msgid "attrd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In some cases, it may be necessary to power off nodes in order to protect shared data or complete resource recovery. For this, Pacemaker comes with STONITHd."
+msgid "cib"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<emphasis role=\"strong\">STONITH</emphasis> is an acronym for <emphasis>Shoot-The-Other-Node-In-The-Head</emphasis>, a recommended practice that misbehaving node is best to be promptly <emphasis>fenced</emphasis> (shut off, cut from shared resources or otherwise immobilized), and is usually implemented with a remote power switch."
+msgid "crmd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In Pacemaker, STONITH devices are modeled as resources (and configured in the CIB) to enable them to be easily monitored for failure, however STONITHd takes care of understanding the STONITH topology such that its clients simply request a node be fenced, and it does the rest."
+msgid "lrmd"
msgstr ""
-#. Tag: title
+#. Tag: para
+#, no-c-format
+msgid "stonithd"
+msgstr ""
+
+#. Tag: para
#, no-c-format
-msgid "Types of Pacemaker Clusters"
+msgid "pacemaker_remoted"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker makes no assumptions about your environment. This allows it to support practically any <ulink url=\"http://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations\">redundancy configuration</ulink> including <emphasis>Active/Active</emphasis>, <emphasis>Active/Passive</emphasis>, <emphasis>N+1</emphasis>, <emphasis>N+M</emphasis>, <emphasis>N-to-1</emphasis> and <emphasis>N-to-N</emphasis>."
+msgid "pacemaker-remoted"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Active/Passive Redundancy"
+msgid "Node Redundancy Designs"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Pacemaker supports practically any <ulink url=\"https://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations\">node redundancy configuration</ulink> including <emphasis>Active/Active</emphasis>, <emphasis>Active/Passive</emphasis>, <emphasis>N+1</emphasis>, <emphasis>N+M</emphasis>, <emphasis>N-to-1</emphasis> and <emphasis>N-to-N</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Two-node Active/Passive clusters using Pacemaker and <emphasis>DRBD</emphasis> are a cost-effective solution for many High Availability situations."
+msgid "Active/passive clusters with two (or more) nodes using Pacemaker and <ulink url=\"https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device:\">DRBD</ulink> are a cost-effective high-availability solution for many situations. One of the nodes provides the desired services, and if it fails, the other node takes over."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Shared Failover"
+msgid "Active/Passive Redundancy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "By supporting many nodes, Pacemaker can dramatically reduce hardware costs by allowing several active/passive clusters to be combined and share a common backup node."
+msgid "Pacemaker also supports multiple nodes in a shared-failover design, reducing hardware costs by allowing several active/passive clusters to be combined and share a common backup node."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "N to N Redundancy"
+msgid "Shared Failover"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When shared storage is available, every node can potentially be used for failover. Pacemaker can even run multiple copies of services to spread out the workload."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "N to N Redundancy"
+msgstr ""
+
diff --git a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot
index 83a796e634..daa2e994b6 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot
@@ -1,458 +1,458 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Multi-Site Clusters and Tickets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Apart from local clusters, Pacemaker also supports multi-site clusters. That means you can have multiple, geographically dispersed sites, each with a local cluster. Failover between these clusters can be coordinated manually by the administrator, or automatically by a higher-level entity called a <emphasis>Cluster Ticket Registry (CTR)</emphasis>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Challenges for Multi-Site Clusters"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Typically, multi-site environments are too far apart to support synchronous communication and data replication between the sites. That leads to significant challenges:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How do we make sure that a cluster site is up and running?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How do we make sure that resources are only started once?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How do we make sure that quorum can be reached between the different sites and a split-brain scenario avoided?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How do we manage failover between sites?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How do we deal with high latency in case of resources that need to be stopped?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the following sections, learn how to meet these challenges."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Conceptual Overview"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Multi-site clusters can be considered as “overlay” clusters where each cluster site corresponds to a cluster node in a traditional cluster. The overlay cluster can be managed by a CTR in order to guarantee that any cluster resource will be active on no more than one cluster site. This is achieved by using <emphasis>tickets</emphasis> that are treated as failover domain between cluster sites, in case a site should be down."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The following sections explain the individual components and mechanisms that were introduced for multi-site clusters in more detail."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ticket"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Tickets are, essentially, cluster-wide attributes. A ticket grants the right to run certain resources on a specific cluster site. Resources can be bound to a certain ticket by <literal>rsc_ticket</literal> constraints. Only if the ticket is available at a site can the respective resources be started there. Vice versa, if the ticket is revoked, the resources depending on that ticket must be stopped."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The ticket thus is similar to a <emphasis>site quorum</emphasis>, i.e. the permission to manage/own resources associated with that site. (One can also think of the current <literal>have-quorum</literal> flag as a special, cluster-wide ticket that is granted in case of node majority.)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Tickets can be granted and revoked either manually by administrators (which could be the default for classic enterprise clusters), or via the automated CTR mechanism described below."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A ticket can only be owned by one site at a time. Initially, none of the sites has a ticket. Each ticket must be granted once by the cluster administrator."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The presence or absence of tickets for a site is stored in the CIB as a cluster status. With regards to a certain ticket, there are only two states for a site: <literal>true</literal> (the site has the ticket) or <literal>false</literal> (the site does not have the ticket). The absence of a certain ticket (during the initial state of the multi-site cluster) is the same as the value <literal>false</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Dead Man Dependency"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A site can only activate resources safely if it can be sure that the other site has deactivated them. However after a ticket is revoked, it can take a long time until all resources depending on that ticket are stopped \"cleanly\", especially in case of cascaded resources. To cut that process short, the concept of a <emphasis>Dead Man Dependency</emphasis> was introduced."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If a dead man dependency is in force, if a ticket is revoked from a site, the nodes that are hosting dependent resources are fenced. This considerably speeds up the recovery process of the cluster and makes sure that resources can be migrated more quickly."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This can be configured by specifying a <literal>loss-policy=\"fence\"</literal> in <literal>rsc_ticket</literal> constraints."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Cluster Ticket Registry"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A CTR is a coordinated group of network daemons that automatically handles granting, revoking, and timing out tickets (instead of the administrator revoking the ticket somewhere, waiting for everything to stop, and then granting it on the desired site)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker does not implement its own CTR, but interoperates with external software designed for that purpose (similar to how resource and fencing agents are not directly part of pacemaker)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Participating clusters run the CTR daemons, which connect to each other, exchange information about their connectivity, and vote on which sites gets which tickets."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A ticket is granted to a site only once the CTR is sure that the ticket has been relinquished by the previous owner, implemented via a timer in most scenarios. If a site loses connection to its peers, its tickets time out and recovery occurs. After the connection timeout plus the recovery timeout has passed, the other sites are allowed to re-acquire the ticket and start the resources again."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This can also be thought of as a \"quorum server\", except that it is not a single quorum ticket, but several."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configuration Replication"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As usual, the CIB is synchronized within each cluster, but it is <emphasis>not</emphasis> synchronized across cluster sites of a multi-site cluster. You have to configure the resources that will be highly available across the multi-site cluster for every site accordingly."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configuring Ticket Dependencies"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>rsc_ticket</literal> constraint lets you specify the resources depending on a certain ticket. Together with the constraint, you can set a <literal>loss-policy</literal> that defines what should happen to the respective resources if the ticket is revoked."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The attribute <literal>loss-policy</literal> can have the following values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>fence:</literal> Fence the nodes that are running the relevant resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop:</literal> Stop the relevant resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>freeze:</literal> Do nothing to the relevant resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>demote:</literal> Demote relevant resources that are running in master mode to slave mode."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Constraint that fences node if <literal>ticketA</literal> is revoked"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" ticket=\"ticketA\" loss-policy=\"fence\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The example above creates a constraint with the ID <literal>rsc1-req-ticketA</literal>. It defines that the resource <literal>rsc1</literal> depends on <literal>ticketA</literal> and that the node running the resource should be fenced if <literal>ticketA</literal> is revoked."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If resource <literal>rsc1</literal> were a multi-state resource (i.e. it could run in master or slave mode), you might want to configure that only master mode depends on <literal>ticketA</literal>. With the following configuration, <literal>rsc1</literal> will be demoted to slave mode if <literal>ticketA</literal> is revoked:"
+msgid "If resource <literal>rsc1</literal> were a promotable resource (i.e. it could run in master or slave mode), you might want to configure that only master mode depends on <literal>ticketA</literal>. With the following configuration, <literal>rsc1</literal> will be demoted to slave mode if <literal>ticketA</literal> is revoked:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Constraint that demotes <literal>rsc1</literal> if <literal>ticketA</literal> is revoked"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" rsc-role=\"Master\" ticket=\"ticketA\" loss-policy=\"demote\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can create multiple <literal>rsc_ticket</literal> constraints to let multiple resources depend on the same ticket. However, <literal>rsc_ticket</literal> also supports resource sets (see <xref linkend=\"s-resource-sets\" />), so one can easily list all the resources in one <literal>rsc_ticket</literal> constraint instead."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ticket constraint for multiple resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_ticket id=\"resources-dep-ticketA\" ticket=\"ticketA\" loss-policy=\"fence\"&gt;\n"
" &lt;resource_set id=\"resources-dep-ticketA-0\" role=\"Started\"&gt;\n"
" &lt;resource_ref id=\"rsc1\"/&gt;\n"
" &lt;resource_ref id=\"group1\"/&gt;\n"
" &lt;resource_ref id=\"clone1\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"resources-dep-ticketA-1\" role=\"Master\"&gt;\n"
" &lt;resource_ref id=\"ms1\"/&gt;\n"
" &lt;/resource_set&gt;\n"
"&lt;/rsc_ticket&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, there are two resource sets, so we can list resources with different roles in a single <literal>rsc_ticket</literal> constraint. There’s no dependency between the two resource sets, and there’s no dependency among the resources within a resource set. Each of the resources just depends on <literal>ticketA</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Referencing resource templates in <literal>rsc_ticket</literal> constraints, and even referencing them within resource sets, is also supported."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you want other resources to depend on further tickets, create as many constraints as necessary with <literal>rsc_ticket</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Managing Multi-Site Clusters"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Granting and Revoking Tickets Manually"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can grant tickets to sites or revoke them from sites manually. If you want to re-distribute a ticket, you should wait for the dependent resources to stop cleanly at the previous site before you grant the ticket to the new site."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Use the <literal>crm_ticket</literal> command line tool to grant and revoke tickets."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To grant a ticket to this site:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_ticket --ticket ticketA --grant"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To revoke a ticket from this site:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_ticket --ticket ticketA --revoke"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you are managing tickets manually, use the <literal>crm_ticket</literal> command with great care, because it cannot check whether the same ticket is already granted elsewhere."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Granting and Revoking Tickets via a Cluster Ticket Registry"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We will use <ulink url=\"https://github.com/ClusterLabs/booth\">Booth</ulink> here as an example of software that can be used with pacemaker as a Cluster Ticket Registry. Booth implements the <ulink url=\"http://en.wikipedia.org/wiki/Raft_%28computer_science%29\">Raft</ulink> algorithm to guarantee the distributed consensus among different cluster sites, and manages the ticket distribution (and thus the failover process between sites)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Each of the participating clusters and <emphasis>arbitrators</emphasis> runs the Booth daemon <literal>boothd</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "An <emphasis>arbitrator</emphasis> is the multi-site equivalent of a quorum-only node in a local cluster. If you have a setup with an even number of sites, you need an additional instance to reach consensus about decisions such as failover of resources across sites. In this case, add one or more arbitrators running at additional sites. Arbitrators are single machines that run a booth instance in a special mode. An arbitrator is especially important for a two-site scenario, otherwise there is no way for one site to distinguish between a network failure between it and the other site, and a failure of the other site."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The most common multi-site scenario is probably a multi-site cluster with two sites and a single arbitrator on a third site. However, technically, there are no limitations with regards to the number of sites and the number of arbitrators involved."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Boothd</literal> at each site connects to its peers running at the other sites and exchanges connectivity details. Once a ticket is granted to a site, the booth mechanism will manage the ticket automatically: If the site which holds the ticket is out of service, the booth daemons will vote which of the other sites will get the ticket. To protect against brief connection failures, sites that lose the vote (either explicitly or implicitly by being disconnected from the voting body) need to relinquish the ticket after a time-out. Thus, it is made sure that a ticket will only be re-distributed after it has been relinquished by the previous site. The resources that depend on that ticket will fail over to the new site holding the ticket. The nodes that have run the resources before will be treated according to the <literal>loss-policy</literal> you set within the <literal>rsc_ticket</literal> constraint."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before the booth can manage a certain ticket within the multi-site cluster, you initially need to grant it to a site manually via the <literal>booth</literal> command-line tool. After you have initially granted a ticket to a site, <literal>boothd</literal> will take over and manage the ticket automatically."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <literal>booth</literal> command-line tool can be used to grant, list, or revoke tickets and can be run on any machine where <literal>boothd</literal> is running. If you are managing tickets via Booth, use only <literal>booth</literal> for manual intervention, not <literal>crm_ticket</literal>. That ensures the same ticket will only be owned by one cluster site at a time."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Booth Requirements"
msgstr ""
#. Tag: para
#, no-c-format
msgid "All clusters that will be part of the multi-site cluster must be based on Pacemaker."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Booth must be installed on all cluster nodes and on all arbitrators that will be part of the multi-site cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nodes belonging to the same cluster site should be synchronized via NTP. However, time synchronization is not required between the individual cluster sites."
msgstr ""
#. Tag: title
#, no-c-format
msgid "General Management of Tickets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Display the information of tickets:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_ticket --info"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Or you can monitor them with:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_mon --tickets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Display the <literal>rsc_ticket</literal> constraints that apply to a ticket:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_ticket --ticket ticketA --constraints"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When you want to do maintenance or manual switch-over of a ticket, revoking the ticket would trigger the loss policies. If <literal>loss-policy=\"fence\"</literal>, the dependent resources could not be gracefully stopped/demoted, and other unrelated resources could even be affected."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The proper way is making the ticket <emphasis>standby</emphasis> first with:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_ticket --ticket ticketA --standby"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then the dependent resources will be stopped or demoted gracefully without triggering the loss policies."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you have finished the maintenance and want to activate the ticket again, you can run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_ticket --ticket ticketA --activate"
msgstr ""
#. Tag: title
#, no-c-format
msgid "For more information"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://www.suse.com/documentation/sle-ha-geo-12/art_ha_geo_quick/data/art_ha_geo_quick.html\">SUSE’s Geo Clustering quick start</ulink>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<ulink url=\"https://github.com/ClusterLabs/booth\">Booth</ulink>"
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Nodes.pot b/doc/Pacemaker_Explained/pot/Ch-Nodes.pot
index bcb009a517..bb42e4ca02 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Nodes.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Nodes.pot
@@ -1,384 +1,144 @@
#
# 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"
+"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 Heartbeat cluster node entry"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "&lt;node id=\"1186dc9a-324d-425a-966e-d757e693dc86\" uname=\"pcmk-1\" type=\"normal\"/&gt;"
-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\" type=\"normal\"/&gt;"
+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. However for Heartbeat, one can use the <literal>crm_uuid</literal> tool to read an existing UUID or define a value before the cluster starts."
+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 ""
-#. Tag: title
-#, no-c-format
-msgid "Managing Nodes in a Corosync-Based Cluster"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Adding a New Corosync Node"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Corosync</primary><secondary>Add Cluster Node</secondary> </indexterm> <indexterm> <primary>Add Cluster Node</primary> </indexterm> <indexterm> <primary>Add Cluster Node</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To add a new node:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Install Corosync and Pacemaker on the new host."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy <literal>/etc/corosync/corosync.conf</literal> and <literal>/etc/corosync/authkey</literal> (if it exists) from an existing node. You may need to modify the <emphasis role=\"strong\">mcastaddr</emphasis> option to match the new node’s IP address."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the cluster software on the new host. If a log message containing \"Invalid digest\" appears from Corosync, the keys are not consistent between the machines."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Removing a Corosync Node"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Corosync</primary><secondary>Remove Cluster Node</secondary> </indexterm> <indexterm> <primary>Remove Cluster Node</primary> </indexterm> <indexterm> <primary>Remove Cluster Node</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a complete solution. First, one must arrange for corosync to forget about the node (<emphasis role=\"strong\">pcmk-1</emphasis> in the example below)."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Stop the cluster on the host to be removed. How to do this will vary with your operating system and installed versions of cluster software, for example, <literal>pcs cluster stop</literal> if you are using pcs for cluster management, or <literal>service corosync stop</literal> on a host using corosync 1.x with the pacemaker plugin."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "From one of the remaining active cluster nodes, tell Pacemaker to forget about the removed host, which will also delete the node from the CIB:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_node -R pcmk-1"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This procedure only works for pacemaker 1.1.8 and later."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Replacing a Corosync Node"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Corosync</primary><secondary>Replace Cluster Node</secondary> </indexterm> <indexterm> <primary>Replace Cluster Node</primary> </indexterm> <indexterm> <primary>Replace Cluster Node</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To replace an existing cluster node:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Make sure the old node is completely stopped."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Give the new machine the same hostname and IP address as the old one."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Follow the procedure above for adding a node."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Managing Nodes in a Heartbeat-based Cluster"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Adding a New Heartbeat Node"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Heartbeat</primary><secondary>Add Cluster Node</secondary> </indexterm> <indexterm> <primary>Add Cluster Node</primary> </indexterm> <indexterm> <primary>Add Cluster Node</primary><secondary>Heartbeat</secondary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Install heartbeat and pacemaker on the new host."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy <literal>ha.cf</literal> and <literal>authkeys</literal> from an existing node."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you do not use <emphasis role=\"strong\">autojoin any</emphasis> in <literal>ha.cf</literal>, run:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "hb_addnode $(uname -n)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the cluster software on the new node."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Removing a Heartbeat Node"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Heartbeat</primary><secondary>Remove Cluster Node</secondary> </indexterm> <indexterm> <primary>Remove Cluster Node</primary> </indexterm> <indexterm> <primary>Remove Cluster Node</primary><secondary>Heartbeat</secondary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a complete solution. First, one must arrange for Heartbeat to forget about the node (pcmk-1 in the example below)."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On the host to be removed, stop the cluster:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "service heartbeat stop"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "From one of the remaining active cluster nodes, tell Heartbeat the node should be removed:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "hb_delnode pcmk-1"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Tell Pacemaker to forget about the removed host:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "crm_node -R pcmk-1"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This procedure only works for pacemaker versions after 1.1.8."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Replacing a Heartbeat Node"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Heartbeat</primary><secondary>Replace Cluster Node</secondary> </indexterm> <indexterm> <primary>Replace Cluster Node</primary> </indexterm> <indexterm> <primary>Replace Cluster Node</primary><secondary>Heartbeat</secondary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm> To replace an existing cluster node:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Give the new machine the same hostname as the old one."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Go to an active cluster node and look up the UUID for the old node in <literal>/var/lib/heartbeat/hostcache</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Install the cluster software."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy <literal>ha.cf</literal> and <literal>authkeys</literal> to the new node."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On the new node, populate its UUID using <literal>crm_uuid -w</literal> and the UUID obtained earlier."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the new cluster node."
-msgstr ""
-
diff --git a/doc/Pacemaker_Explained/pot/Ch-Options.pot b/doc/Pacemaker_Explained/pot/Ch-Options.pot
index b62066d967..7492bf1dc2 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Options.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Options.pot
@@ -1,811 +1,737 @@
#
# 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"
+"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-Wide Configuration"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "CIB Properties"
+msgid "Configuration Layout"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Certain settings are defined by CIB properties (that is, attributes of the <literal>cib</literal> tag) rather than with the rest of the cluster configuration in the <literal>configuration</literal> section."
+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 "&lt;cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\"&gt;\n"
+" &lt;configuration&gt;\n"
+" &lt;crm_config/&gt;\n"
+" &lt;nodes/&gt;\n"
+" &lt;resources/&gt;\n"
+" &lt;constraints/&gt;\n"
+" &lt;/configuration&gt;\n"
+" &lt;status/&gt;\n"
+"&lt;/cib&gt;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reason is simply a matter of parsing. These options are used by the configuration database which is, by design, mostly ignorant of the content it holds. So the decision was made to place them in an easy-to-find location."
+msgid "The empty configuration above contains the major sections that make up a CIB:"
msgstr ""
-#. Tag: entry
+#. Tag: para
#, no-c-format
-msgid "Field"
+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: entry
+#. Tag: para
#, no-c-format
-msgid "Description"
+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>admin_epoch</literal>"
+msgid "<literal>crm_config</literal>: cluster-wide configuration options"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>Configuration Version</primary><secondary>Cluster</secondary> </indexterm> <indexterm> <primary>Cluster</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>Configuration Version</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>Configuration Version</secondary> </indexterm> <indexterm> <primary>Configuration Version</primary> </indexterm> <indexterm> <primary>admin_epoch</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>admin_epoch</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>admin_epoch</secondary> </indexterm> <indexterm> <primary>admin_epoch</primary> </indexterm> When a node joins the cluster, the cluster performs a check to see which node has the best configuration. It asks the node with the highest (<literal>admin_epoch</literal>, <literal>epoch</literal>, <literal>num_updates</literal>) tuple to replace the configuration on all the nodes — which makes setting them, and setting them correctly, very important. <literal>admin_epoch</literal> is never modified by the cluster; you can use this to make the configurations on any inactive nodes obsolete. <emphasis>Never set this value to zero</emphasis>. In such cases, the cluster cannot tell the difference between your configuration and the \"empty\" one used when nothing is found on disk."
+msgid "<literal>nodes</literal>: the machines that host the cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>epoch</literal>"
+msgid "<literal>resources</literal>: the services run by the cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>epoch</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>epoch</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>epoch</secondary> </indexterm> <indexterm> <primary>epoch</primary> </indexterm> The cluster increments this every time the configuration is updated (usually by the administrator)."
+msgid "<literal>constraints</literal>: indications of how resources should be placed"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>num_updates</literal>"
+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 executor (pacemaker-execd 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 "<indexterm> <primary>num_updates</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>num_updates</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>num_updates</secondary> </indexterm> <indexterm> <primary>num_updates</primary> </indexterm> The cluster increments this every time the configuration or status is updated (usually by the cluster) and resets it to 0 when epoch changes."
+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 "<literal>validate-with</literal>"
+msgid "Properties are XML attributes of an XML element."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>validate-with</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>validate-with</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>validate-with</secondary> </indexterm> <indexterm> <primary>validate-with</primary> </indexterm> Determines the type of XML validation that will be done on the configuration. If set to <literal>none</literal>, the cluster will not verify that updates conform to the DTD (nor reject ones that don’t). This option can be useful when operating a mixed-version cluster during an upgrade."
+msgid "Options are name-value pairs expressed as <literal>nvpair</literal> child elements of an XML element."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>cib-last-written</literal>"
+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 "CIB Properties"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>cib-last-written</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>cib-last-written</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>cib-last-written</secondary> </indexterm> <indexterm> <primary>cib-last-written</primary> </indexterm> Indicates when the configuration was last written to disk. Maintained by the cluster; for informational purposes only."
+msgid "Certain settings are defined by CIB properties (that is, attributes of the <literal>cib</literal> tag) rather than with the rest of the cluster configuration in the <literal>configuration</literal> section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>have-quorum</literal>"
+msgid "The reason is simply a matter of parsing. These options are used by the configuration database which is, by design, mostly ignorant of the content it holds. So the decision was made to place them in an easy-to-find location."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>have-quorum</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>have-quorum</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>have-quorum</secondary> </indexterm> <indexterm> <primary>have-quorum</primary> </indexterm> Indicates if the cluster has quorum. If false, this may mean that the cluster cannot start resources or fence other nodes (see <literal>no-quorum-policy</literal> below). Maintained by the cluster."
+msgid "<literal>admin_epoch</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>dc-uuid</literal>"
+msgid "<indexterm> <primary>Configuration Version</primary><secondary>Cluster</secondary> </indexterm> <indexterm> <primary>Cluster</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>Configuration Version</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>Configuration Version</secondary> </indexterm> <indexterm> <primary>Configuration Version</primary> </indexterm> <indexterm> <primary>admin_epoch</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>admin_epoch</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>admin_epoch</secondary> </indexterm> <indexterm> <primary>admin_epoch</primary> </indexterm> When a node joins the cluster, the cluster performs a check to see which node has the best configuration. It asks the node with the highest (<literal>admin_epoch</literal>, <literal>epoch</literal>, <literal>num_updates</literal>) tuple to replace the configuration on all the nodes — which makes setting them, and setting them correctly, very important. <literal>admin_epoch</literal> is never modified by the cluster; you can use this to make the configurations on any inactive nodes obsolete. <emphasis>Never set this value to zero</emphasis>. In such cases, the cluster cannot tell the difference between your configuration and the \"empty\" one used when nothing is found on disk."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>dc-uuid</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>dc-uuid</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>dc-uuid</secondary> </indexterm> <indexterm> <primary>dc-uuid</primary> </indexterm> Indicates which cluster node is the current leader. Used by the cluster when placing resources and determining the order of some events. Maintained by the cluster."
+msgid "<literal>epoch</literal>"
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "Working with CIB Properties"
+msgid "<indexterm> <primary>epoch</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>epoch</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>epoch</secondary> </indexterm> <indexterm> <primary>epoch</primary> </indexterm> The cluster increments this every time the configuration is updated (usually by the administrator)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Although these fields can be written to by the user, in most cases the cluster will overwrite any values specified by the user with the \"correct\" ones."
+msgid "<literal>num_updates</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To change the ones that can be specified by the user, for example <literal>admin_epoch</literal>, one should use:"
+msgid "<indexterm> <primary>num_updates</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>num_updates</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>num_updates</secondary> </indexterm> <indexterm> <primary>num_updates</primary> </indexterm> The cluster increments this every time the configuration or status is updated (usually by the cluster) and resets it to 0 when epoch changes."
msgstr ""
-#. Tag: screen
+#. Tag: para
#, no-c-format
-msgid "# cibadmin --modify --xml-text '&lt;cib admin_epoch=\"42\"/&gt;'"
+msgid "<literal>validate-with</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A complete set of CIB properties will look something like this:"
+msgid "<indexterm> <primary>validate-with</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>validate-with</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>validate-with</secondary> </indexterm> <indexterm> <primary>validate-with</primary> </indexterm> Determines the type of XML validation that will be done on the configuration. If set to <literal>none</literal>, the cluster will not verify that updates conform to the DTD (nor reject ones that don’t). This option can be useful when operating a mixed-version cluster during an upgrade."
msgstr ""
-#. Tag: title
+#. Tag: para
#, no-c-format
-msgid "Attributes set for a cib object"
+msgid "<literal>cib-last-written</literal>"
msgstr ""
-#. Tag: programlisting
+#. Tag: para
#, no-c-format
-msgid "&lt;cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\"\n"
-" admin_epoch=\"42\" epoch=\"116\" num_updates=\"1\"\n"
-" cib-last-written=\"Mon Jan 12 15:46:39 2015\" update-origin=\"rhel7-1\"\n"
-" update-client=\"crm_attribute\" have-quorum=\"1\" dc-uuid=\"1\"&gt;"
+msgid "<indexterm> <primary>cib-last-written</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>cib-last-written</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>cib-last-written</secondary> </indexterm> <indexterm> <primary>cib-last-written</primary> </indexterm> Indicates when the configuration was last written to disk. Maintained by the cluster; for informational purposes only."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>have-quorum</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>have-quorum</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>have-quorum</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>have-quorum</secondary> </indexterm> <indexterm> <primary>have-quorum</primary> </indexterm> Indicates if the cluster has quorum. If false, this may mean that the cluster cannot start resources or fence other nodes (see <literal>no-quorum-policy</literal> below). Maintained by the cluster."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dc-uuid</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>dc-uuid</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>dc-uuid</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>dc-uuid</secondary> </indexterm> <indexterm> <primary>dc-uuid</primary> </indexterm> Indicates which cluster node is the current leader. Used by the cluster when placing resources and determining the order of some events. Maintained by the cluster."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Cluster Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Cluster options, as you might expect, control how the cluster behaves when confronted with certain situations."
msgstr ""
#. Tag: para
#, no-c-format
msgid "They are grouped into sets within the <literal>crm_config</literal> section, and, in advanced configurations, there may be more than one set. (This will be described later in the section on <xref linkend=\"ch-rules\" /> where we will show how to have the cluster use different sets of options during working hours than during weekends.) For now, we will describe the simple case where each option is present at most once."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can obtain an up-to-date list of cluster options, including their default values, by running the <literal>man pengine</literal> and <literal>man crmd</literal> commands."
+msgid "You can obtain an up-to-date list of cluster options, including their default values, by running the <literal>man pacemaker-schedulerd</literal> and <literal>man pacemaker-controld</literal> commands."
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Option"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>dc-version</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>dc-version</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>dc-version</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>dc-version</secondary> </indexterm> <indexterm> <primary>dc-version</primary> </indexterm> Version of Pacemaker on the cluster’s DC. Determined automatically by the cluster. Often includes the hash which identifies the exact Git changeset it was built from. Used for diagnostic purposes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>cluster-infrastructure</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>cluster-infrastructure</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>cluster-infrastructure</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>cluster-infrastructure</secondary> </indexterm> <indexterm> <primary>cluster-infrastructure</primary> </indexterm> The messaging stack on which Pacemaker is currently running. Determined automatically by the cluster. Used for informational and diagnostic purposes."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<literal>expected-quorum-votes</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>expected-quorum-votes</primary><secondary>Cluster Property</secondary> </indexterm> <indexterm> <primary>Cluster Property</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Property</secondary><tertiary>expected-quorum-votes</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>expected-quorum-votes</secondary> </indexterm> <indexterm> <primary>expected-quorum-votes</primary> </indexterm> The number of nodes expected to be in the cluster. Determined automatically by the cluster. Used to calculate quorum in clusters that use Corosync 1.x without CMAN as the messaging layer."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "<literal>no-quorum-policy</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "stop"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>no-quorum-policy</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>no-quorum-policy</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>no-quorum-policy</secondary> </indexterm> <indexterm> <primary>no-quorum-policy</primary> </indexterm> What to do when the cluster does not have quorum. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>ignore:</literal> continue all resource management"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>freeze:</literal> continue resource management, but don’t recover resources from nodes not in the affected partition"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop:</literal> stop all resources in the affected cluster partition"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>suicide:</literal> fence all nodes in the affected cluster partition"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>batch-limit</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "30"
+msgid "0"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>batch-limit</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>batch-limit</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>batch-limit</secondary> </indexterm> <indexterm> <primary>batch-limit</primary> </indexterm> The number of jobs that the Transition Engine (TE) is allowed to execute in parallel. The TE is the logic in pacemaker’s CRMd that executes the actions determined by the Policy Engine (PE). The \"correct\" value will depend on the speed and load of your network and cluster nodes."
+msgid "<indexterm> <primary>batch-limit</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>batch-limit</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>batch-limit</secondary> </indexterm> <indexterm> <primary>batch-limit</primary> </indexterm> The maximum number of actions that the cluster may execute in parallel across all nodes. The \"correct\" value will depend on the speed and load of your network and cluster nodes. If zero, the cluster will impose a dynamically calculated limit only when any node has high load."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>migration-limit</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "-1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>migration-limit</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>migration-limit</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>migration-limit</secondary> </indexterm> <indexterm> <primary>migration-limit</primary> </indexterm> The number of migration jobs that the TE is allowed to execute in parallel on a node. A value of -1 means unlimited."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>symmetric-cluster</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "TRUE"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>symmetric-cluster</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>symmetric-cluster</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>symmetric-cluster</secondary> </indexterm> <indexterm> <primary>symmetric-cluster</primary> </indexterm> Can all resources run on any node by default?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop-all-resources</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "FALSE"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>stop-all-resources</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stop-all-resources</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stop-all-resources</secondary> </indexterm> <indexterm> <primary>stop-all-resources</primary> </indexterm> Should the cluster stop all resources?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop-orphan-resources</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>stop-orphan-resources</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stop-orphan-resources</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stop-orphan-resources</secondary> </indexterm> <indexterm> <primary>stop-orphan-resources</primary> </indexterm> Should deleted resources be stopped?"
+msgid "<indexterm> <primary>stop-orphan-resources</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stop-orphan-resources</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stop-orphan-resources</secondary> </indexterm> <indexterm> <primary>stop-orphan-resources</primary> </indexterm> Should deleted resources be stopped? This value takes precedence over <literal>is-managed</literal> (i.e. even unmanaged resources will be stopped if deleted from the configuration when this value is TRUE)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop-orphan-actions</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>stop-orphan-actions</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stop-orphan-actions</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stop-orphan-actions</secondary> </indexterm> <indexterm> <primary>stop-orphan-actions</primary> </indexterm> Should deleted actions be cancelled?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>start-failure-is-fatal</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>start-failure-is-fatal</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>start-failure-is-fatal</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>start-failure-is-fatal</secondary> </indexterm> <indexterm> <primary>start-failure-is-fatal</primary> </indexterm> Should a failure to start a resource on a particular node prevent further start attempts on that node? If FALSE, the cluster will decide whether the same node is still eligible based on the resource’s current failure count and <literal>migration-threshold</literal> (see <xref linkend=\"s-failure-handling\" />)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>enable-startup-probes</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>enable-startup-probes</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>enable-startup-probes</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>enable-startup-probes</secondary> </indexterm> <indexterm> <primary>enable-startup-probes</primary> </indexterm> Should the cluster check for active resources during startup?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>maintenance-mode</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>maintenance-mode</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>maintenance-mode</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>maintenance-mode</secondary> </indexterm> <indexterm> <primary>maintenance-mode</primary> </indexterm> Should the cluster refrain from monitoring, starting and stopping resources?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stonith-enabled</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>stonith-enabled</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stonith-enabled</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stonith-enabled</secondary> </indexterm> <indexterm> <primary>stonith-enabled</primary> </indexterm> Should failed nodes and nodes with resources that can’t be stopped be shot? If you value your data, set up a STONITH device and enable this."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If true, or unset, the cluster will refuse to start resources unless one or more STONITH resources have been configured. If false, unresponsive nodes are immediately assumed to be running no resources, and resource takeover to online nodes starts without any further protection (which means <emphasis>data loss</emphasis> if the unresponsive node still accesses shared storage, for example). See also the <literal>requires</literal> meta-attribute in <xref linkend=\"s-resource-options\" />."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stonith-action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "reboot"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>stonith-action</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stonith-action</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stonith-action</secondary> </indexterm> <indexterm> <primary>stonith-action</primary> </indexterm> Action to send to STONITH device. Allowed values are <literal>reboot</literal> and <literal>off</literal>. The value <literal>poweroff</literal> is also allowed, but is only used for legacy devices."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stonith-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "60s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>stonith-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stonith-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stonith-timeout</secondary> </indexterm> <indexterm> <primary>stonith-timeout</primary> </indexterm> How long to wait for STONITH actions (reboot, on, off) to complete"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stonith-max-attempts</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "10"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>stonith-max-attempts</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stonith-max-attempts</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stonith-max-attempts</secondary> </indexterm> <indexterm> <primary>stonith-max-attempts</primary> </indexterm> How many times fencing can fail for a target before the cluster will no longer immediately re-attempt it. <emphasis>(since 1.1.17)</emphasis>"
+msgid "<indexterm> <primary>stonith-max-attempts</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stonith-max-attempts</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stonith-max-attempts</secondary> </indexterm> <indexterm> <primary>stonith-max-attempts</primary> </indexterm> How many times fencing can fail for a target before the cluster will no longer immediately re-attempt it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>stonith-watchdog-timeout</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>stonith-watchdog-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>stonith-watchdog-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>stonith-watchdog-timeout</secondary> </indexterm> <indexterm> <primary>stonith-watchdog-timeout</primary> </indexterm> If nonzero, rely on hardware watchdog self-fencing. If positive, assume unseen nodes self-fence within this much time. If negative, and the SBD_WATCHDOG_TIMEOUT environment variable is set, use twice that value."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>concurrent-fencing</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>concurrent-fencing</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>concurrent-fencing</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>concurrent-fencing</secondary> </indexterm> <indexterm> <primary>concurrent-fencing</primary> </indexterm> Is the cluster allowed to initiate multiple fence actions concurrently? <emphasis>(since 1.1.15)</emphasis>"
+msgid "<indexterm> <primary>concurrent-fencing</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>concurrent-fencing</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>concurrent-fencing</secondary> </indexterm> <indexterm> <primary>concurrent-fencing</primary> </indexterm> Is the cluster allowed to initiate multiple fence actions concurrently?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>cluster-delay</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>cluster-delay</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>cluster-delay</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>cluster-delay</secondary> </indexterm> <indexterm> <primary>cluster-delay</primary> </indexterm> Estimated maximum round-trip delay over the network (excluding action execution). If the TE requires an action to be executed on another node, it will consider the action failed if it does not get a response from the other node in this time (after considering the action’s own timeout). The \"correct\" value will depend on the speed and load of your network and cluster nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>dc-deadtime</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "20s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>dc-deadtime</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>dc-deadtime</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>dc-deadtime</secondary> </indexterm> <indexterm> <primary>dc-deadtime</primary> </indexterm> How long to wait for a response from other nodes during startup."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The \"correct\" value will depend on the speed/load of your network and the type of switches used."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>cluster-recheck-interval</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "15min"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>cluster-recheck-interval</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>cluster-recheck-interval</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>cluster-recheck-interval</secondary> </indexterm> <indexterm> <primary>cluster-recheck-interval</primary> </indexterm> Polling interval for time-based changes to options, resource parameters and constraints."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The Cluster is primarily event-driven, but your configuration can have elements that take effect based on the time of day. To ensure these changes take effect, we can optionally poll the cluster’s status for changes. A value of 0 disables polling. Positive values are an interval (in seconds unless other SI units are specified, e.g. 5min)."
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "<literal>cluster-ipc-limit</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "500"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<indexterm> <primary>cluster-ipc-limit</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>cluster-ipc-limit</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>cluster-ipc-limit</secondary> </indexterm> <indexterm> <primary>cluster-ipc-limit</primary> </indexterm> The maximum IPC message backlog before one cluster daemon will disconnect another. This is of use in large clusters, for which a good value is the number of resources in the cluster multiplied by the number of nodes. The default of 500 is also the minimum. Raise this if you see \"Evicting client\" messages for cluster daemon PIDs in the logs."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "<literal>pe-error-series-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>pe-error-series-max</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>pe-error-series-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>pe-error-series-max</secondary> </indexterm> <indexterm> <primary>pe-error-series-max</primary> </indexterm> The number of PE inputs resulting in ERRORs to save. Used when reporting problems. A value of -1 means unlimited (report all)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pe-warn-series-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>pe-warn-series-max</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>pe-warn-series-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>pe-warn-series-max</secondary> </indexterm> <indexterm> <primary>pe-warn-series-max</primary> </indexterm> The number of PE inputs resulting in WARNINGs to save. Used when reporting problems. A value of -1 means unlimited (report all)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pe-input-series-max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>pe-input-series-max</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>pe-input-series-max</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>pe-input-series-max</secondary> </indexterm> <indexterm> <primary>pe-input-series-max</primary> </indexterm> The number of \"normal\" PE inputs to save. Used when reporting problems. A value of -1 means unlimited (report all)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>placement-strategy</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "default"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>placement-strategy</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>placement-strategy</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>placement-strategy</secondary> </indexterm> <indexterm> <primary>placement-strategy</primary> </indexterm> How the cluster should allocate resources to nodes (see <xref linkend=\"s-utilization\" />). Allowed values are <literal>default</literal>, <literal>utilization</literal>, <literal>balanced</literal>, and <literal>minimal</literal>. <emphasis>(since 1.1.0)</emphasis>"
+msgid "<indexterm> <primary>placement-strategy</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>placement-strategy</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>placement-strategy</secondary> </indexterm> <indexterm> <primary>placement-strategy</primary> </indexterm> How the cluster should allocate resources to nodes (see <xref linkend=\"s-utilization\" />). Allowed values are <literal>default</literal>, <literal>utilization</literal>, <literal>balanced</literal>, and <literal>minimal</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node-health-strategy</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "none"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>node-health-strategy</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>node-health-strategy</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>node-health-strategy</secondary> </indexterm> <indexterm> <primary>node-health-strategy</primary> </indexterm> How the cluster should react to node health attributes (see <xref linkend=\"s-node-health\" />). Allowed values are <literal>none</literal>, <literal>migrate-on-red</literal>, <literal>only-green</literal>, <literal>progressive</literal>, and <literal>custom</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node-health-base</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "0"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>node-health-base</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>node-health-base</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>node-health-base</secondary> </indexterm> <indexterm> <primary>node-health-base</primary> </indexterm> The base health score assigned to a node. Only used when <literal>node-health-strategy</literal> is <literal>progressive</literal>. <emphasis>(since 1.1.16)</emphasis>"
+msgid "<indexterm> <primary>node-health-base</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>node-health-base</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>node-health-base</secondary> </indexterm> <indexterm> <primary>node-health-base</primary> </indexterm> The base health score assigned to a node. Only used when <literal>node-health-strategy</literal> is <literal>progressive</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node-health-green</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>node-health-green</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>node-health-green</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>node-health-green</secondary> </indexterm> <indexterm> <primary>node-health-green</primary> </indexterm> The score to use for a node health attribute whose value is <literal>green</literal>. Only used when <literal>node-health-strategy</literal> is <literal>progressive</literal> or <literal>custom</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node-health-yellow</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>node-health-yellow</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>node-health-yellow</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>node-health-yellow</secondary> </indexterm> <indexterm> <primary>node-health-yellow</primary> </indexterm> The score to use for a node health attribute whose value is <literal>yellow</literal>. Only used when <literal>node-health-strategy</literal> is <literal>progressive</literal> or <literal>custom</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node-health-red</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>node-health-red</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>node-health-red</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>node-health-red</secondary> </indexterm> <indexterm> <primary>node-health-red</primary> </indexterm> The score to use for a node health attribute whose value is <literal>red</literal>. Only used when <literal>node-health-strategy</literal> is <literal>progressive</literal> or <literal>custom</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remove-after-stop</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>remove-after-stop</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>remove-after-stop</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>remove-after-stop</secondary> </indexterm> <indexterm> <primary>remove-after-stop</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> Should the cluster remove resources from the LRM after they are stopped? Values other than the default are, at best, poorly tested and potentially dangerous."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>startup-fencing</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>startup-fencing</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>startup-fencing</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>startup-fencing</secondary> </indexterm> <indexterm> <primary>startup-fencing</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> Should the cluster shoot unseen nodes? Not using the default is very unsafe!"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>election-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "2min"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>election-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>election-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>election-timeout</secondary> </indexterm> <indexterm> <primary>election-timeout</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> If you need to adjust this value, it probably indicates the presence of a bug."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>shutdown-escalation</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "20min"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>shutdown-escalation</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>shutdown-escalation</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>shutdown-escalation</secondary> </indexterm> <indexterm> <primary>shutdown-escalation</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> If you need to adjust this value, it probably indicates the presence of a bug."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>crmd-integration-timeout</literal>"
+msgid "<literal>join-integration-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "3min"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>crmd-integration-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>crmd-integration-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>crmd-integration-timeout</secondary> </indexterm> <indexterm> <primary>crmd-integration-timeout</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> If you need to adjust this value, it probably indicates the presence of a bug."
+msgid "<indexterm> <primary>join-integration-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>join-integration-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>join-integration-timeout</secondary> </indexterm> <indexterm> <primary>join-integration-timeout</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> If you need to adjust this value, it probably indicates the presence of a bug."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>crmd-finalization-timeout</literal>"
+msgid "<literal>join-finalization-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "30min"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>crmd-finalization-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>crmd-finalization-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>crmd-finalization-timeout</secondary> </indexterm> <indexterm> <primary>crmd-finalization-timeout</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> If you need to adjust this value, it probably indicates the presence of a bug."
+msgid "<indexterm> <primary>join-finalization-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>join-finalization-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>join-finalization-timeout</secondary> </indexterm> <indexterm> <primary>join-finalization-timeout</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> If you need to adjust this value, it probably indicates the presence of a bug."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>crmd-transition-delay</literal>"
+msgid "<literal>transition-delay</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "0s"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>crmd-transition-delay</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>crmd-transition-delay</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>crmd-transition-delay</secondary> </indexterm> <indexterm> <primary>crmd-transition-delay</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> Delay cluster recovery for the configured interval to allow for additional/related events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive. Enabling this option will slow down cluster recovery under all conditions."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>default-resource-stickiness</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>default-resource-stickiness</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>default-resource-stickiness</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>default-resource-stickiness</secondary> </indexterm> <indexterm> <primary>default-resource-stickiness</primary> </indexterm> <emphasis>Deprecated:</emphasis> See <xref linkend=\"s-resource-defaults\" /> instead"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>is-managed-default</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>is-managed-default</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>is-managed-default</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>is-managed-default</secondary> </indexterm> <indexterm> <primary>is-managed-default</primary> </indexterm> <emphasis>Deprecated:</emphasis> See <xref linkend=\"s-resource-defaults\" /> instead"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>default-action-timeout</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>default-action-timeout</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>default-action-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>default-action-timeout</secondary> </indexterm> <indexterm> <primary>default-action-timeout</primary> </indexterm> <emphasis>Deprecated:</emphasis> See <xref linkend=\"s-operation-defaults\" /> instead"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Querying and Setting Cluster Options"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>Querying</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Setting</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Querying Options</secondary> </indexterm> <indexterm> <primary>Querying Options</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Setting Options</secondary> </indexterm> <indexterm> <primary>Setting Options</primary> </indexterm>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Cluster options can be queried and modified using the <literal>crm_attribute</literal> tool. To get the current value of <literal>cluster-delay</literal>, you can run:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute --query --name cluster-delay"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "which is more simply written as"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute -G -n cluster-delay"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If a value is found, you’ll see a result like this:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute -G -n cluster-delay\n"
-"scope=crm_config name=cluster-delay value=60s"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If no value is found, the tool will display an error:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute -G -n clusta-deway\n"
-"scope=crm_config name=clusta-deway value=(null)\n"
-"Error performing operation: No such device or address"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To use a different value (for example, 30 seconds), simply run:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute --name cluster-delay --update 30s"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To go back to the cluster’s default value, you can delete the value, for example:"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute --name cluster-delay --delete\n"
-"Deleted crm_config option: id=cib-bootstrap-options-cluster-delay name=cluster-delay"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "When Options are Listed More Than Once"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you ever see something like the following, it means that the option you’re modifying is present more than once."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deleting an option that is listed twice"
-msgstr ""
-
-#. Tag: screen
-#, no-c-format
-msgid "# crm_attribute --name batch-limit --delete\n"
-"\n"
-"Multiple attributes match name=batch-limit in crm_config:\n"
-"Value: 50 (set=cib-bootstrap-options, id=cib-bootstrap-options-batch-limit)\n"
-"Value: 100 (set=custom, id=custom-batch-limit)\n"
-"Please choose from one of the matches above and supply the 'id' with --id"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In such cases, follow the on-screen instructions to perform the requested action. To determine which value is currently being used by the cluster, refer to <xref linkend=\"ch-rules\" />."
+msgid "<indexterm> <primary>transition-delay</primary><secondary>Cluster Option</secondary> </indexterm> <indexterm> <primary>Cluster Option</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Option</secondary><tertiary>transition-delay</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>transition-delay</secondary> </indexterm> <indexterm> <primary>transition-delay</primary> </indexterm> <emphasis>Advanced Use Only:</emphasis> Delay cluster recovery for the configured interval to allow for additional/related events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive. Enabling this option will slow down cluster recovery under all conditions."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Resources.pot b/doc/Pacemaker_Explained/pot/Ch-Resources.pot
index 05813ba47c..e8a1d88c88 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Resources.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Resources.pot
@@ -1,1250 +1,1260 @@
#
# 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"
+"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 Resources"
msgstr ""
#. Tag: title
#, no-c-format
msgid "What is a Cluster Resource?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A resource is a service made highly available by a cluster. The simplest type of resource, a <emphasis>primitive</emphasis> resource, is described in this section. More complex forms, such as groups and clones, are described in later sections."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Every primitive resource has a <emphasis>resource agent</emphasis>. A resource agent is an external program that abstracts the service it provides and present a consistent view to the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This allows the cluster to be agnostic about the resources it manages. The cluster doesn’t need to understand how the resource works because it relies on the resource agent to do the right thing when given a <literal>start</literal>, <literal>stop</literal> or <literal>monitor</literal> command. For this reason, it is crucial that resource agents are well-tested."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Typically, resource agents come in the form of shell scripts. However, they can be written using any technology (such as C, Python or Perl) that the author is comfortable with."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Classes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>class</secondary> </indexterm> <indexterm> <primary>class</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker supports several classes of agents:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "OCF"
msgstr ""
#. Tag: para
#, no-c-format
msgid "LSB"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Upstart"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Systemd"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Fencing"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nagios Plugins"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Open Cluster Framework"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>OCF</secondary> </indexterm> <indexterm> <primary>OCF</primary> </indexterm> <indexterm> <primary>OCF</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm> <indexterm> <primary>Open Cluster Framework</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The OCF standard <footnote><para>See <ulink url=\"http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD\">http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD</ulink>  — at least as it relates to resource agents. The Pacemaker implementation has been somewhat extended from the OCF specs, but none of those changes are incompatible with the original OCF specification.</para></footnote> is basically an extension of the Linux Standard Base conventions for init scripts to:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "support parameters,"
msgstr ""
#. Tag: para
#, no-c-format
msgid "make them self-describing, and"
msgstr ""
#. Tag: para
#, no-c-format
msgid "make them extensible"
msgstr ""
#. Tag: para
#, no-c-format
msgid "OCF specs have strict definitions of the exit codes that actions must return. <footnote><para> The resource-agents source code includes the <literal>ocf-tester</literal> script, which can be useful in this regard. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster follows these specifications exactly, and giving the wrong exit code will cause the cluster to behave in ways you will likely find puzzling and annoying. In particular, the cluster needs to distinguish a completely stopped resource from one which is in some erroneous and indeterminate state."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Parameters are passed to the resource agent as environment variables, with the special prefix <literal>OCF_RESKEY_</literal>. So, a parameter which the user thinks of as <literal>ip</literal> will be passed to the resource agent as <literal>OCF_RESKEY_ip</literal>. The number and purpose of the parameters is left to the resource agent; however, the resource agent should use the <literal>meta-data</literal> command to advertise any that it supports."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The OCF class is the most preferred as it is an industry standard, highly flexible (allowing parameters to be passed to agents in a non-positional manner) and self-describing."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For more information, see the <ulink url=\"http://www.linux-ha.org/wiki/OCF_Resource_Agents\">reference</ulink> and <xref linkend=\"ap-ocf\" />."
+msgid "For more information, see the <ulink url=\"http://www.linux-ha.org/wiki/OCF_Resource_Agents\">reference</ulink> and the <emphasis>Resource Agents</emphasis> section of <emphasis>Pacemaker Administration</emphasis>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Linux Standard Base"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>LSB</secondary> </indexterm> <indexterm> <primary>LSB</primary> </indexterm> <indexterm> <primary>LSB</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm> <indexterm> <primary>Linux Standard Base</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "LSB resource agents are those found in <literal>/etc/init.d</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Generally, they are provided by the OS distribution and, in order to be used with the cluster, they must conform to the LSB Spec. <footnote><para> See <ulink url=\"http://refspecs.linux-foundation.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html\">http://refspecs.linux-foundation.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html</ulink> for the LSB Spec as it relates to init scripts. </para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Many distributions claim LSB compliance but ship with broken init scripts. For details on how to check whether your init script is LSB-compatible, see <xref linkend=\"ap-lsb\" />. Common problematic violations of the LSB standard include:"
+msgid "Many distributions claim LSB compliance but ship with broken init scripts. For details on how to check whether your init script is LSB-compatible, see the <emphasis>Resource Agents</emphasis> section of <emphasis>Pacemaker Administration</emphasis>. Common problematic violations of the LSB standard include:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Not implementing the status operation at all"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Not observing the correct exit status codes for <literal>start/stop/status</literal> actions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Starting a started resource returns an error"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Stopping a stopped resource returns an error"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Remember to make sure the computer is <emphasis>not</emphasis> configured to start any services at boot time — that should be controlled by the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Systemd</secondary> </indexterm> <indexterm> <primary>Systemd</primary> </indexterm> <indexterm> <primary>Systemd</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some newer distributions have replaced the old <ulink url=\"http://en.wikipedia.org/wiki/Init#SysV-style\">\"SysV\"</ulink> style of initialization daemons and scripts with an alternative called <ulink url=\"http://www.freedesktop.org/wiki/Software/systemd\">Systemd</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker is able to manage these services <emphasis>if they are present</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Instead of init scripts, systemd has <emphasis>unit files</emphasis>. Generally, the services (unit files) are provided by the OS distribution, but there are online guides for converting from init scripts. <footnote><para>For example, <ulink url=\"http://0pointer.de/blog/projects/systemd-for-admins-3.html\">http://0pointer.de/blog/projects/systemd-for-admins-3.html</ulink></para></footnote>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Upstart</secondary> </indexterm> <indexterm> <primary>Upstart</primary> </indexterm> <indexterm> <primary>Upstart</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some newer distributions have replaced the old <ulink url=\"http://en.wikipedia.org/wiki/Init#SysV-style\">\"SysV\"</ulink> style of initialization daemons (and scripts) with an alternative called <ulink url=\"http://upstart.ubuntu.com/\">Upstart</ulink>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Instead of init scripts, upstart has <emphasis>jobs</emphasis>. Generally, the services (jobs) are provided by the OS distribution."
msgstr ""
#. Tag: title
#, no-c-format
msgid "System Services"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>System Services</secondary> </indexterm> <indexterm> <primary>System Services</primary> </indexterm> <indexterm> <primary>System Service</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Since there are various types of system services (<literal>systemd</literal>, <literal>upstart</literal>, and <literal>lsb</literal>), Pacemaker supports a special <literal>service</literal> alias which intelligently figures out which one applies to a given cluster node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This is particularly useful when the cluster contains a mix of <literal>systemd</literal>, <literal>upstart</literal>, and <literal>lsb</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In order, Pacemaker will try to find the named service as:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "an LSB init script"
msgstr ""
#. Tag: para
#, no-c-format
msgid "a Systemd unit file"
msgstr ""
#. Tag: para
#, no-c-format
msgid "an Upstart job"
msgstr ""
#. Tag: title
#, no-c-format
msgid "STONITH"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>STONITH</secondary> </indexterm> <indexterm> <primary>STONITH</primary> </indexterm> <indexterm> <primary>STONITH</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The STONITH class is used exclusively for fencing-related resources. This is discussed later in <xref linkend=\"ch-stonith\" />."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Nagios Plugins</secondary> </indexterm> <indexterm> <primary>Nagios Plugins</primary> </indexterm> <indexterm> <primary>Nagios Plugins</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Nagios Plugins <footnote><para>The project has two independent forks, hosted at <ulink url=\"https://www.nagios-plugins.org/\">https://www.nagios-plugins.org/</ulink> and <ulink url=\"https://www.monitoring-plugins.org/\">https://www.monitoring-plugins.org/</ulink>. Output from both projects' plugins is similar, so plugins from either project can be used with pacemaker.</para></footnote> allow us to monitor services on remote hosts."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker is able to do remote monitoring with the plugins <emphasis>if they are present</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A common use case is to configure them as resources belonging to a resource container (usually a virtual machine), and the container will be restarted if any of them has failed. Another use is to configure them as ordinary resources to be used for monitoring hosts or services via the network."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The supported parameters are same as the long options of the plugin."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Properties"
msgstr ""
#. Tag: para
#, no-c-format
msgid "These values tell the cluster which resource agent to use for the resource, where to find that resource agent and what standards it conforms to."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Primitive Resource"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Your name for the resource <indexterm> <primary>id</primary><secondary>Resource</secondary> </indexterm> <indexterm> <primary>Resource</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>class</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The standard the resource agent conforms to. Allowed values: <literal>lsb</literal>, <literal>nagios</literal>, <literal>ocf</literal>, <literal>service</literal>, <literal>stonith</literal>, <literal>systemd</literal>, <literal>upstart</literal> <indexterm> <primary>class</primary><secondary>Resource</secondary> </indexterm> <indexterm> <primary>Resource</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Property</secondary><tertiary>class</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>class</secondary> </indexterm> <indexterm> <primary>class</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>type</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of the Resource Agent you wish to use. E.g. <literal>IPaddr</literal> or <literal>Filesystem</literal> <indexterm> <primary>type</primary><secondary>Resource</secondary> </indexterm> <indexterm> <primary>Resource</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Property</secondary><tertiary>type</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>type</secondary> </indexterm> <indexterm> <primary>type</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>provider</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The OCF spec allows multiple vendors to supply the same resource agent. To use the OCF resource agents supplied by the Heartbeat project, you would specify <literal>heartbeat</literal> here. <indexterm> <primary>provider</primary><secondary>Resource</secondary> </indexterm> <indexterm> <primary>Resource</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Property</secondary><tertiary>provider</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>provider</secondary> </indexterm> <indexterm> <primary>provider</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The XML definition of a resource can be queried with the <literal>crm_resource</literal> tool. For example:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --resource Email --query-xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "might produce:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A system resource definition"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Email\" class=\"service\" type=\"exim\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "One of the main drawbacks to system services (LSB, systemd or Upstart) resources is that they do not allow any parameters!"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An OCF resource definition"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;instance_attributes id=\"Public-IP-params\"&gt;\n"
" &lt;nvpair id=\"Public-IP-ip\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resources have two types of options: <emphasis>meta-attributes</emphasis> and <emphasis>instance attributes</emphasis>. Meta-attributes apply to any type of resource, while instance attributes are specific to each resource agent."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Meta-Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Meta-attributes are used by the cluster to decide how a resource should behave and can be easily set using the <literal>--meta</literal> option of the <literal>crm_resource</literal> command."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Meta-attributes of a Primitive Resource"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>priority</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "0"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If not all resources can be active, the cluster will stop lower priority resources in order to keep higher priority ones active. <indexterm> <primary>priority</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>priority</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>priority</secondary> </indexterm> <indexterm> <primary>priority</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target-role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Started"
msgstr ""
#. Tag: para
#, no-c-format
msgid "What state should the cluster attempt to keep this resource in? Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Stopped:</literal> Force the resource to be stopped"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>Started:</literal> Allow the resource to be started (and in the case of <link linkend=\"s-resource-multistate\">multi-state</link> resources, promoted to master if appropriate)"
+msgid "<literal>Started:</literal> Allow the resource to be started (and in the case of <link linkend=\"s-resource-promotable\">promotable clone resources</link>, promoted to master if appropriate)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>Slave:</literal> Allow the resource to be started, but only in Slave mode if the resource is <link linkend=\"s-resource-multistate\">multi-state</link>"
+msgid "<literal>Slave:</literal> Allow the resource to be started, but only in Slave mode if the resource is <link linkend=\"s-resource-promotable\">promotable</link>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Master:</literal> Equivalent to <literal>Started</literal> <indexterm> <primary>target-role</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>target-role</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>target-role</secondary> </indexterm> <indexterm> <primary>target-role</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>is-managed</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "TRUE"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Is the cluster allowed to start and stop the resource? Allowed values: <literal>true</literal>, <literal>false</literal> <indexterm> <primary>is-managed</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>is-managed</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>is-managed</secondary> </indexterm> <indexterm> <primary>is-managed</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>resource-stickiness</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "value of <literal>resource-stickiness</literal> in the <literal>rsc_defaults</literal> section"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How much does the resource prefer to stay where it is? <indexterm> <primary>resource-stickiness</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>resource-stickiness</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>resource-stickiness</secondary> </indexterm> <indexterm> <primary>resource-stickiness</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>requires</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "fencing (unless <literal>stonith-enabled</literal> is <literal>false</literal> or <literal>class</literal> is <literal>stonith</literal>, in which case it defaults to quorum)"
+msgid "<literal>quorum</literal> for resources with a <literal>class</literal> of <literal>stonith</literal>, otherwise <literal>unfencing</literal> if unfencing is active in the cluster, otherwise <literal>fencing</literal> if <literal>stonith-enabled</literal> is true, otherwise <literal>quorum</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Conditions under which the resource can be started <emphasis>(since 1.1.8)</emphasis> Allowed values:"
+msgid "Conditions under which the resource can be started Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>nothing:</literal> can always be started"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>quorum:</literal> The cluster can only start this resource if a majority of the configured nodes are active"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>fencing:</literal> The cluster can only start this resource if a majority of the configured nodes are active <emphasis>and</emphasis> any failed or unknown nodes have been powered off"
+msgid "<literal>fencing:</literal> The cluster can only start this resource if a majority of the configured nodes are active <emphasis>and</emphasis> any failed or unknown nodes have been <link linkend=\"ch-stonith\">fenced</link>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>unfencing:</literal> The cluster can only start this resource if a majority of the configured nodes are active <emphasis>and</emphasis> any failed or unknown nodes have been powered off <emphasis>and</emphasis> only on nodes that have been <emphasis>unfenced</emphasis> <emphasis>(since 1.1.9)</emphasis>"
+msgid "<literal>unfencing:</literal> The cluster can only start this resource if a majority of the configured nodes are active <emphasis>and</emphasis> any failed or unknown nodes have been fenced <emphasis>and</emphasis> only on nodes that have been <link linkend=\"s-unfencing\">unfenced</link>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>requires</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>requires</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>requires</secondary> </indexterm> <indexterm> <primary>requires</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>migration-threshold</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "INFINITY"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How many failures may occur for this resource on a node, before this node is marked ineligible to host this resource. A value of 0 indicates that this feature is disabled (the node will never be marked ineligible); by constrast, the cluster treats INFINITY (the default) as a very large but finite number. This option has an effect only if the failed operation has on-fail=restart (the default), and additionally for failed start operations, if the cluster property start-failure-is-fatal is false. <indexterm> <primary>migration-threshold</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>migration-threshold</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>migration-threshold</secondary> </indexterm> <indexterm> <primary>migration-threshold</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>failure-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How many seconds to wait before acting as if the failure had not occurred, and potentially allowing the resource back to the node on which it failed. A value of 0 indicates that this feature is disabled. As with any time-based actions, this is not guaranteed to be checked more frequently than the value of <literal>cluster-recheck-interval</literal> (see <xref linkend=\"s-cluster-options\" />). <indexterm> <primary>failure-timeout</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>failure-timeout</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>failure-timeout</secondary> </indexterm> <indexterm> <primary>failure-timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>multiple-active</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "stop_start"
msgstr ""
#. Tag: para
#, no-c-format
msgid "What should the cluster do if it ever finds the resource active on more than one node? Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>block:</literal> mark the resource as unmanaged"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop_only:</literal> stop all active instances and leave them that way"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop_start:</literal> stop all active instances and start the resource in one location only"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>multiple-active</primary><secondary>Resource Option</secondary> </indexterm> <indexterm> <primary>Resource Option</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Option</secondary><tertiary>multiple-active</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>multiple-active</secondary> </indexterm> <indexterm> <primary>multiple-active</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>allow-migrate</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "TRUE for ocf:pacemaker:remote resources, FALSE otherwise"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Whether the cluster should try to \"live migrate\" this resource when it needs to be moved (see <xref linkend=\"s-migrating-resources\" />)"
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid "<literal>container-attribute-target</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Specific to bundle resources; see <xref linkend=\"s-bundle-attributes\" />"
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "<literal>remote-node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of the Pacemaker Remote guest node this resource is associated with, if any. If specified, this both enables the resource as a guest node and defines the unique name used to identify the guest node. The guest must be configured to run the Pacemaker Remote daemon when it is started. <literal>WARNING:</literal> This value cannot overlap with any resource or node IDs. <emphasis>(since 1.1.9)</emphasis>"
+msgid "The name of the Pacemaker Remote guest node this resource is associated with, if any. If specified, this both enables the resource as a guest node and defines the unique name used to identify the guest node. The guest must be configured to run the Pacemaker Remote daemon when it is started. <literal>WARNING:</literal> This value cannot overlap with any resource or node IDs."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-port</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "3121"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If <literal>remote-node</literal> is specified, the port on the guest used for its Pacemaker Remote connection. The Pacemaker Remote daemon on the guest must be configured to listen on this port. <emphasis>(since 1.1.9)</emphasis>"
+msgid "If <literal>remote-node</literal> is specified, the port on the guest used for its Pacemaker Remote connection. The Pacemaker Remote daemon on the guest must be configured to listen on this port."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-addr</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "value of <literal>remote-node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If <literal>remote-node</literal> is specified, the IP address or hostname used to connect to the guest via Pacemaker Remote. The Pacemaker Remote daemon on the guest must be configured to accept connections on this address. <emphasis>(since 1.1.9)</emphasis>"
+msgid "If <literal>remote-node</literal> is specified, the IP address or hostname used to connect to the guest via Pacemaker Remote. The Pacemaker Remote daemon on the guest must be configured to accept connections on this address."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-connect-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "60s"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If <literal>remote-node</literal> is specified, how long before a pending guest connection will time out. <emphasis>(since 1.1.10)</emphasis>"
+msgid "If <literal>remote-node</literal> is specified, how long before a pending guest connection will time out."
msgstr ""
#. Tag: para
#, no-c-format
msgid "As an example of setting resource options, if you performed the following commands on an LSB Email resource:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --meta --resource Email --set-parameter priority --parameter-value 100\n"
"# crm_resource -m -r Email -p multiple-active -v block"
msgstr ""
#. Tag: para
#, no-c-format
msgid "the resulting resource definition might be:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An LSB resource with cluster options"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Email\" class=\"lsb\" type=\"exim\"&gt;\n"
" &lt;meta_attributes id=\"Email-meta_attributes\"&gt;\n"
" &lt;nvpair id=\"Email-meta_attributes-priority\" name=\"priority\" value=\"100\"/&gt;\n"
" &lt;nvpair id=\"Email-meta_attributes-multiple-active\" name=\"multiple-active\" value=\"block\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Setting Global Defaults for Resource Meta-Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To set a default value for a resource option, add it to the <literal>rsc_defaults</literal> section with <literal>crm_attribute</literal>. For example,"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute --type rsc_defaults --name is-managed --update false"
msgstr ""
#. Tag: para
#, no-c-format
msgid "would prevent the cluster from starting or stopping any of the resources in the configuration (unless of course the individual resources were specifically enabled by having their <literal>is-managed</literal> set to <literal>true</literal>)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Instance Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource agents of some resource classes (lsb, systemd and upstart <emphasis>not</emphasis> among them) can be given parameters which determine how they behave and which instance of a service they control."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If your resource agent supports parameters, you can add them with the <literal>crm_resource</literal> command. For example,"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --resource Public-IP --set-parameter ip --parameter-value 192.0.2.2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "would create an entry in the resource like this:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An example OCF resource with instance attributes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For an OCF resource, the result would be an environment variable called <literal>OCF_RESKEY_ip</literal> with a value of <literal>192.0.2.2</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The list of instance attributes supported by an OCF resource agent can be found by calling the resource agent with the <literal>meta-data</literal> command. The output contains an XML description of all the supported attributes, their purpose and default values."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Displaying the metadata for the Dummy resource agent template"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# export OCF_ROOT=/usr/lib/ocf\n"
"# $OCF_ROOT/resource.d/pacemaker/Dummy meta-data"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;?xml version=\"1.0\"?&gt;\n"
"&lt;!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\"&gt;\n"
"&lt;resource-agent name=\"Dummy\" version=\"1.0\"&gt;\n"
"&lt;version&gt;1.0&lt;/version&gt;\n"
"\n"
"&lt;longdesc&gt;\n"
"This is a Dummy Resource Agent. It does absolutely nothing except\n"
"keep track of whether its running or not.\n"
"Its purpose in life is for testing and to serve as a template for RA writers.\n"
"\n"
"NB: Please pay attention to the timeouts specified in the actions\n"
"section below. They should be meaningful for the kind of resource\n"
"the agent manages. They should be the minimum advised timeouts,\n"
"but they shouldn't/cannot cover _all_ possible resource\n"
"instances. So, try to be neither overly generous nor too stingy,\n"
"but moderate. The minimum timeouts should never be below 10 seconds.\n"
"&lt;/longdesc&gt;\n"
"&lt;shortdesc&gt;Example stateless resource agent&lt;/shortdesc&gt;\n"
"\n"
"&lt;parameters&gt;\n"
"&lt;parameter name=\"state\" unique=\"1\"&gt;\n"
"&lt;longdesc&gt;\n"
"Location to store the resource state in.\n"
"&lt;/longdesc&gt;\n"
"&lt;shortdesc&gt;State file&lt;/shortdesc&gt;\n"
"&lt;content type=\"string\" default=\"/var/run/Dummy-default.state\" /&gt;\n"
"&lt;/parameter&gt;\n"
"\n"
"&lt;parameter name=\"fake\" unique=\"0\"&gt;\n"
"&lt;longdesc&gt;\n"
"Fake attribute that can be changed to cause a reload\n"
"&lt;/longdesc&gt;\n"
"&lt;shortdesc&gt;Fake attribute that can be changed to cause a reload&lt;/shortdesc&gt;\n"
"&lt;content type=\"string\" default=\"dummy\" /&gt;\n"
"&lt;/parameter&gt;\n"
"\n"
"&lt;parameter name=\"op_sleep\" unique=\"1\"&gt;\n"
"&lt;longdesc&gt;\n"
"Number of seconds to sleep during operations. This can be used to test how\n"
"the cluster reacts to operation timeouts.\n"
"&lt;/longdesc&gt;\n"
"&lt;shortdesc&gt;Operation sleep duration in seconds.&lt;/shortdesc&gt;\n"
"&lt;content type=\"string\" default=\"0\" /&gt;\n"
"&lt;/parameter&gt;\n"
"\n"
"&lt;/parameters&gt;\n"
"\n"
"&lt;actions&gt;\n"
"&lt;action name=\"start\" timeout=\"20\" /&gt;\n"
"&lt;action name=\"stop\" timeout=\"20\" /&gt;\n"
"&lt;action name=\"monitor\" timeout=\"20\" interval=\"10\" depth=\"0\"/&gt;\n"
"&lt;action name=\"reload\" timeout=\"20\" /&gt;\n"
"&lt;action name=\"migrate_to\" timeout=\"20\" /&gt;\n"
"&lt;action name=\"migrate_from\" timeout=\"20\" /&gt;\n"
"&lt;action name=\"validate-all\" timeout=\"20\" /&gt;\n"
"&lt;action name=\"meta-data\" timeout=\"5\" /&gt;\n"
"&lt;/actions&gt;\n"
"&lt;/resource-agent&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Operations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Action</secondary> </indexterm> <indexterm> <primary>Action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Operations</emphasis> are actions the cluster can perform on a resource by calling the resource agent. Resource agents must support certain common operations such as start, stop and monitor, and may implement any others."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some operations are generated by the cluster itself, for example, stopping and starting resources as needed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can configure operations in the cluster configuration. As an example, by default the cluster will <emphasis>not</emphasis> ensure your resources stay healthy once they are started. <footnote><para>Currently, anyway. Automatic monitoring operations may be added in a future version of Pacemaker.</para></footnote> To instruct the cluster to do this, you need to add a <literal>monitor</literal> operation to the resource’s definition."
msgstr ""
#. Tag: title
#, no-c-format
msgid "An OCF resource with a recurring health check"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"public-ip-check\" name=\"monitor\" interval=\"60s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of an Operation"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the operation. <indexterm> <primary>id</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>name</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The action to perform. This can be any action supported by the agent; common values include <literal>monitor</literal>, <literal>start</literal>, and <literal>stop</literal>. <indexterm> <primary>name</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>name</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>name</secondary> </indexterm> <indexterm> <primary>name</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>interval</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How frequently (in seconds) to perform the operation. A value of 0 means never. A positive value defines a <emphasis>recurring action</emphasis>, which is typically used with <link linkend=\"s-resource-monitoring\">monitor</link>. <indexterm> <primary>interval</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>interval</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>interval</secondary> </indexterm> <indexterm> <primary>interval</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How long to wait before declaring the action has failed <indexterm> <primary>timeout</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>timeout</secondary> </indexterm> <indexterm> <primary>timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>on-fail</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "restart <emphasis>(except for stop operations, which default to</emphasis> fence <emphasis>when STONITH is enabled and</emphasis> block <emphasis>otherwise)</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The action to take if this action ever fails. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>ignore:</literal> Pretend the resource did not fail."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>block:</literal> Don’t perform any further operations on the resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stop:</literal> Stop the resource and do not start it elsewhere."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>restart:</literal> Stop the resource and start it again (possibly on a different node)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>fence:</literal> STONITH the node on which the resource failed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>standby:</literal> Move <emphasis>all</emphasis> resources away from the node on which the resource failed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>on-fail</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>on-fail</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>on-fail</secondary> </indexterm> <indexterm> <primary>on-fail</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>enabled</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>false</literal>, ignore this operation definition. This is typically used to pause a particular recurring monitor operation; for instance, it can complement the respective resource being unmanaged (<literal>is-managed=false</literal>), as this alone will <link linkend=\"s-monitoring-unmanaged\">not block any configured monitoring</link>. Disabling the operation does not suppress all actions of the given type. Allowed values: <literal>true</literal>, <literal>false</literal>. <indexterm> <primary>enabled</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>enabled</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>enabled</secondary> </indexterm> <indexterm> <primary>enabled</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>record-pending</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "FALSE"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>true</literal>, the intention to perform the operation is recorded so that GUIs and CLI tools can indicate that an operation is in progress. This is best set as an <emphasis>operation default</emphasis> (see next section). Allowed values: <literal>true</literal>, <literal>false</literal>. <indexterm> <primary>enabled</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>enabled</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>enabled</secondary> </indexterm> <indexterm> <primary>enabled</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Run the operation only on node(s) that the cluster thinks should be in the specified role. This only makes sense for recurring monitor operations. Allowed (case-sensitive) values: <literal>Stopped</literal>, <literal>Started</literal>, and in the case of <link linkend=\"s-resource-multistate\">multi-state</link> resources, <literal>Slave</literal> and <literal>Master</literal>. <indexterm> <primary>role</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
+msgid "Run the operation only on node(s) that the cluster thinks should be in the specified role. This only makes sense for recurring monitor operations. Allowed (case-sensitive) values: <literal>Stopped</literal>, <literal>Started</literal>, and in the case of <link linkend=\"s-resource-promotable\">promotable clone resources</link>, <literal>Slave</literal> and <literal>Master</literal>. <indexterm> <primary>role</primary><secondary>Action Property</secondary> </indexterm> <indexterm> <primary>Action Property</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Property</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Monitoring Resources for Failure"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When Pacemaker first starts a resource, it runs one-time monitor operations (referred to as <emphasis>probes</emphasis>) to ensure the resource is running where it’s supposed to be, and not running where it’s not supposed to be. (This behavior can be affected by the <literal>resource-discovery</literal> location constraint property.)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Other than those initial probes, Pacemaker will not (by default) check that the resource continues to stay healthy. As in the example above, you must configure monitor operations explicitly to perform these checks."
msgstr ""
#. Tag: para
#, no-c-format
msgid "By default, a monitor operation will ensure that the resource is running where it is supposed to. The <literal>target-role</literal> property can be used for further checking."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, if a resource has one monitor operation with <literal>interval=10 role=Started</literal> and a second monitor operation with <literal>interval=11 role=Stopped</literal>, the cluster will run the first monitor on any nodes it thinks <emphasis>should</emphasis> be running the resource, and the second monitor on any nodes that it thinks <emphasis>should not</emphasis> be running the resource (for the truly paranoid, who want to know when an administrator manually starts a service by mistake)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Monitoring Resources When Administration is Disabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Recurring monitor operations behave differently under various administrative settings:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When a resource is unmanaged (by setting <literal>is-managed=false</literal>): No monitors will be stopped."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the unmanaged resource is stopped on a node where the cluster thinks it should be running, the cluster will detect and report that it is not, but it will not consider the monitor failed, and will not try to start the resource until it is managed again."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Starting the unmanaged resource on a different node is strongly discouraged and will at least cause the cluster to consider the resource failed, and may require the resource’s <literal>target-role</literal> to be set to <literal>Stopped</literal> then <literal>Started</literal> to be recovered."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When a node is put into standby: All resources will be moved away from the node, and all monitor operations will be stopped on the node, except those with <literal>role=Stopped</literal>. Monitor operations with <literal>role=Stopped</literal> will be started on the node if appropriate."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When the cluster is put into maintenance mode: All resources will be marked as unmanaged. All monitor operations will be stopped, except those with <literal>role=Stopped</literal>. As with single unmanaged resources, starting a resource on a node other than where the cluster expects it to be will cause problems."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Setting Global Defaults for Operations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can change the global default values for operation properties in a given cluster. These are defined in an <literal>op_defaults</literal> section of the CIB’s <literal>configuration</literal> section, and can be set with <literal>crm_attribute</literal>. For example,"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute --type op_defaults --name timeout --update 20s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "would default each operation’s <literal>timeout</literal> to 20 seconds. If an operation’s definition also includes a value for <literal>timeout</literal>, then that value would be used for that operation instead."
msgstr ""
#. Tag: title
#, no-c-format
msgid "When Implicit Operations Take a Long Time"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster will always perform a number of implicit operations: <literal>start</literal>, <literal>stop</literal> and a non-recurring <literal>monitor</literal> operation used at startup to check whether the resource is already active. If one of these is taking too long, then you can create an entry for them and specify a longer timeout."
msgstr ""
#. Tag: title
#, no-c-format
msgid "An OCF resource with custom timeouts for its implicit actions"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"public-ip-startup\" name=\"monitor\" interval=\"0\" timeout=\"90s\"/&gt;\n"
" &lt;op id=\"public-ip-start\" name=\"start\" interval=\"0\" timeout=\"180s\"/&gt;\n"
" &lt;op id=\"public-ip-stop\" name=\"stop\" interval=\"0\" timeout=\"15min\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Multiple Monitor Operations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Provided no two operations (for a single resource) have the same name and interval, you can have as many monitor operations as you like. In this way, you can do a superficial health check every minute and progressively more intense ones at higher intervals."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To tell the resource agent what kind of check to perform, you need to provide each monitor with a different value for a common parameter. The OCF standard creates a special parameter called <literal>OCF_CHECK_LEVEL</literal> for this purpose and dictates that it is \"made available to the resource agent without the normal <literal>OCF_RESKEY</literal> prefix\"."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Whatever name you choose, you can specify it by adding an <literal>instance_attributes</literal> block to the <literal>op</literal> tag. It is up to each resource agent to look for the parameter and decide how to use it."
msgstr ""
#. Tag: title
#, no-c-format
msgid "An OCF resource with two recurring health checks, performing different levels of checks specified via <literal>OCF_CHECK_LEVEL</literal>."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"public-ip-health-60\" name=\"monitor\" interval=\"60\"&gt;\n"
" &lt;instance_attributes id=\"params-public-ip-depth-60\"&gt;\n"
" &lt;nvpair id=\"public-ip-depth-60\" name=\"OCF_CHECK_LEVEL\" value=\"10\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/op&gt;\n"
" &lt;op id=\"public-ip-health-300\" name=\"monitor\" interval=\"300\"&gt;\n"
" &lt;instance_attributes id=\"params-public-ip-depth-300\"&gt;\n"
" &lt;nvpair id=\"public-ip-depth-300\" name=\"OCF_CHECK_LEVEL\" value=\"20\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/op&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-level\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Disabling a Monitor Operation"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The easiest way to stop a recurring monitor is to just delete it. However, there can be times when you only want to disable it temporarily. In such cases, simply add <literal>enabled=\"false\"</literal> to the operation’s definition."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example of an OCF resource with a disabled health check"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\"&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"public-ip-check\" name=\"monitor\" interval=\"60s\" enabled=\"false\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"params-public-ip\"&gt;\n"
" &lt;nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This can be achieved from the command line by executing:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin --modify --xml-text '&lt;op id=\"public-ip-check\" enabled=\"false\"/&gt;'"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once you’ve done whatever you needed to do, you can then re-enable it with"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin --modify --xml-text '&lt;op id=\"public-ip-check\" enabled=\"true\"/&gt;'"
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot b/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot
index 93e060a84e..2086e91684 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot
@@ -1,505 +1,505 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Reusing Parts of the Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker provides multiple ways to simplify the configuration XML by reusing parts of it in multiple places."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Besides simplifying the XML, this also allows you to manipulate multiple configuration elements with a single reference."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Reusing Resource Definitions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you want to create lots of resources with similar configurations, defining a <emphasis>resource template</emphasis> simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configuring Resources with Templates"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The primitives referencing the template will inherit all meta-attributes, instance attributes, utilization attributes and operations defined in the template. And you can define specific attributes and operations for any of the primitives. If any of these are defined in both the template and the primitive, the values defined in the primitive will take precedence over the ones defined in the template."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Hence, resource templates help to reduce the amount of configuration work. If any changes are needed, they can be done to the template definition and will take effect globally in all resource definitions referencing that template."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource templates have a syntax similar to that of primitives."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource template for a migratable Xen virtual machine"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;template id=\"vm-template\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\"&gt;\n"
" &lt;meta_attributes id=\"vm-template-meta_attributes\"&gt;\n"
" &lt;nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;utilization id=\"vm-template-utilization\"&gt;\n"
" &lt;nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/&gt;\n"
" &lt;/utilization&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/&gt;\n"
" &lt;op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/&gt;\n"
" &lt;/operations&gt;\n"
"&lt;/template&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once you define a resource template, you can use it in primitives by specifying the <literal>template</literal> property."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Xen primitive resource using a resource template"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"vm1\" template=\"vm-template\"&gt;\n"
" &lt;instance_attributes id=\"vm1-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/&gt;\n"
" &lt;nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, the new primitive <literal>vm1</literal> will inherit everything from <literal>vm-template</literal>. For example, the equivalent of the above two examples would be:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Equivalent Xen primitive resource not using a resource template"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"vm1\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\"&gt;\n"
" &lt;meta_attributes id=\"vm-template-meta_attributes\"&gt;\n"
" &lt;nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;utilization id=\"vm-template-utilization\"&gt;\n"
" &lt;nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/&gt;\n"
" &lt;/utilization&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/&gt;\n"
" &lt;op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;instance_attributes id=\"vm1-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/&gt;\n"
" &lt;nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you want to overwrite some attributes or operations, add them to the particular primitive’s definition."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Xen resource overriding template values"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"vm2\" template=\"vm-template\"&gt;\n"
" &lt;meta_attributes id=\"vm2-meta_attributes\"&gt;\n"
" &lt;nvpair id=\"vm2-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"false\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;utilization id=\"vm2-utilization\"&gt;\n"
" &lt;nvpair id=\"vm2-utilization-memory\" name=\"memory\" value=\"1024\"/&gt;\n"
" &lt;/utilization&gt;\n"
" &lt;instance_attributes id=\"vm2-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"vm2-instance_attributes-name\" name=\"name\" value=\"vm2\"/&gt;\n"
" &lt;nvpair id=\"vm2-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"vm2-monitor-30s\" interval=\"30s\" name=\"monitor\" timeout=\"120s\"/&gt;\n"
" &lt;op id=\"vm2-stop-0\" interval=\"0\" name=\"stop\" timeout=\"60s\"/&gt;\n"
" &lt;/operations&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, the new primitive <literal>vm2</literal> has special attribute values. Its <literal>monitor</literal> operation has a longer <literal>timeout</literal> and <literal>interval</literal>, and the primitive has an additional <literal>stop</literal> operation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To see the resulting definition of a resource, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --query-xml --resource vm2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To see the raw definition of a resource in the CIB, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_resource --query-xml-raw --resource vm2"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Templates in Constraints"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A resource template can be referenced in the following types of constraints:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>order</literal> constraints (see <xref linkend=\"s-resource-ordering\" />)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>colocation</literal> constraints (see <xref linkend=\"s-resource-colocation\" />)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc_ticket</literal> constraints (for multi-site clusters as described in <xref linkend=\"s-ticket-constraints\" />)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource templates referenced in constraints stand for all primitives which are derived from that template. This means, the constraint applies to all primitive resources referencing the resource template. Referencing resource templates in constraints is an alternative to resource sets and can simplify the cluster configuration considerably."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, given the example templates earlier in this section:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_colocation id=\"vm-template-colo-base-rsc\" rsc=\"vm-template\" rsc-role=\"Started\" with-rsc=\"base-rsc\" score=\"INFINITY\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "would colocate all VMs with <literal>base-rsc</literal> and is the equivalent of the following constraint configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_colocation id=\"vm-colo-base-rsc\" score=\"INFINITY\"&gt;\n"
" &lt;resource_set id=\"vm-colo-base-rsc-0\" sequential=\"false\" role=\"Started\"&gt;\n"
" &lt;resource_ref id=\"vm1\"/&gt;\n"
" &lt;resource_ref id=\"vm2\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"vm-colo-base-rsc-1\"&gt;\n"
" &lt;resource_ref id=\"base-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
"&lt;/rsc_colocation&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In a colocation constraint, only one template may be referenced from either <literal>rsc</literal> or <literal>with-rsc</literal>; the other reference must be a regular resource."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Templates in Resource Sets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Resource templates can also be referenced in resource sets."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, given the example templates earlier in this section, then:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_order id=\"order1\" score=\"INFINITY\"&gt;\n"
" &lt;resource_set id=\"order1-0\"&gt;\n"
" &lt;resource_ref id=\"base-rsc\"/&gt;\n"
" &lt;resource_ref id=\"vm-template\"/&gt;\n"
" &lt;resource_ref id=\"top-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
"&lt;/rsc_order&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "is the equivalent of the following constraint using a sequential resource set:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_order id=\"order1\" score=\"INFINITY\"&gt;\n"
" &lt;resource_set id=\"order1-0\"&gt;\n"
" &lt;resource_ref id=\"base-rsc\"/&gt;\n"
" &lt;resource_ref id=\"vm1\"/&gt;\n"
" &lt;resource_ref id=\"vm2\"/&gt;\n"
" &lt;resource_ref id=\"top-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
"&lt;/rsc_order&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Or, if the resources referencing the template can run in parallel, then:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_order id=\"order2\" score=\"INFINITY\"&gt;\n"
" &lt;resource_set id=\"order2-0\"&gt;\n"
" &lt;resource_ref id=\"base-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"order2-1\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"vm-template\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"order2-2\"&gt;\n"
" &lt;resource_ref id=\"top-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
"&lt;/rsc_order&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "is the equivalent of the following constraint configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_order id=\"order2\" score=\"INFINITY\"&gt;\n"
" &lt;resource_set id=\"order2-0\"&gt;\n"
" &lt;resource_ref id=\"base-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"order2-1\" sequential=\"false\"&gt;\n"
" &lt;resource_ref id=\"vm1\"/&gt;\n"
" &lt;resource_ref id=\"vm2\"/&gt;\n"
" &lt;/resource_set&gt;\n"
" &lt;resource_set id=\"order2-2\"&gt;\n"
" &lt;resource_ref id=\"top-rsc\"/&gt;\n"
" &lt;/resource_set&gt;\n"
"&lt;/rsc_order&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Reusing Rules, Options and Sets of Operations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Sometimes a number of constraints need to use the same set of rules, and resources need to set the same options and parameters. To simplify this situation, you can refer to an existing object using an <literal>id-ref</literal> instead of an <literal>id</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "So if for one resource you have"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
" &lt;rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" &gt;\n"
" &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/&gt;\n"
" &lt;/rule&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Then instead of duplicating the rule for all your other resources, you can instead specify:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Referencing rules from other constraints"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"WebDB-connectivity\" rsc=\"WebDB\"&gt;\n"
" &lt;rule id-ref=\"ping-prefer-rule\"/&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster will insist that the <literal>rule</literal> exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a <literal>rule</literal> that is referenced elsewhere."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The same principle applies for <literal>meta_attributes</literal> and <literal>instance_attributes</literal> as illustrated in the example below:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Referencing attributes, options, and operations from other resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\"&gt;\n"
" &lt;instance_attributes id=\"mySpecialRsc-attrs\" score=\"1\" &gt;\n"
" &lt;nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/&gt;\n"
" &lt;nvpair id=\"default-port\" name=\"port\" value=\"9999\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;meta_attributes id=\"mySpecialRsc-options\"&gt;\n"
" &lt;nvpair id=\"failure-timeout\" name=\"failure-timeout\" value=\"5m\"/&gt;\n"
" &lt;nvpair id=\"migration-threshold\" name=\"migration-threshold\" value=\"1\"/&gt;\n"
" &lt;nvpair id=\"stickiness\" name=\"resource-stickiness\" value=\"0\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;operations id=\"health-checks\"&gt;\n"
" &lt;op id=\"health-check\" name=\"monitor\" interval=\"60s\"/&gt;\n"
" &lt;op id=\"health-check\" name=\"monitor\" interval=\"30min\"/&gt;\n"
" &lt;/operations&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive id=\"myOtherlRsc\" class=\"ocf\" type=\"Other\" provider=\"me\"&gt;\n"
" &lt;instance_attributes id-ref=\"mySpecialRsc-attrs\"/&gt;\n"
" &lt;meta_attributes id-ref=\"mySpecialRsc-options\"/&gt;\n"
" &lt;operations id-ref=\"health-checks\"/&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Tagging Configuration Elements"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker allows you to <emphasis>tag</emphasis> any configuration element that has an XML ID."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The main purpose of tagging is to support higher-level user interface tools; Pacemaker itself only uses tags within constraints. Therefore, what you can do with tags mostly depends on the tools you use."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configuring Tags"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A tag is simply a named list of XML IDs."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Tag referencing three resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;tags&gt;\n"
" &lt;tag id=\"all-vms\"&gt;\n"
" &lt;obj_ref id=\"vm1\"/&gt;\n"
" &lt;obj_ref id=\"vm2\"/&gt;\n"
" &lt;obj_ref id=\"vm3\"/&gt;\n"
" &lt;/tag&gt;\n"
"&lt;/tags&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "What you can do with this new tag depends on what your higher-level tools support. For example, a tool might allow you to enable or disable all of the tagged resources at once, or show the status of just the tagged resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A single configuration element can be listed in any number of tags."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Tags in Constraints and Resource Sets"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker itself only uses tags in constraints. If you supply a tag name instead of a resource name in any constraint, the constraint will apply to all resources listed in that tag."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Constraint using a tag"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_order id=\"order1\" first=\"storage\" then=\"all-vms\" kind=\"Mandatory\" /&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, assuming the <literal>all-vms</literal> tag is defined as in the previous example, the constraint will behave the same as:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Equivalent constraints without tags"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_order id=\"order1-1\" first=\"storage\" then=\"vm1\" kind=\"Mandatory\" /&gt;\n"
"&lt;rsc_order id=\"order1-2\" first=\"storage\" then=\"vm2\" kind=\"Mandatory\" /&gt;\n"
"&lt;rsc_order id=\"order1-3\" first=\"storage\" then=\"vm2\" kind=\"Mandatory\" /&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A tag may be used directly in the constraint, or indirectly by being listed in a <link linkend=\"s-resource-sets\">resource set</link> used in the constraint. When used in a resource set, an expanded tag will honor the set’s <literal>sequential</literal> property."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Rules.pot b/doc/Pacemaker_Explained/pot/Ch-Rules.pot
index 828fe19745..4d64eaa948 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Rules.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Rules.pot
@@ -1,887 +1,937 @@
#
# 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"
+"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 "Rules"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<anchor id=\"ch-rules\" xreflabel=\"Chapter 8, Rules\"></anchor> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Rule</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary> </indexterm> <indexterm> <primary>Rule</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rules can be used to make your configuration more dynamic. One common example is to set one value for <literal>resource-stickiness</literal> during working hours, to prevent resources from being moved back to their most preferred location, and another on weekends when no-one is around to notice an outage."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another use of rules might be to assign machines to different processing groups (using a node attribute) based on time and to then use that attribute when creating location constraints."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Each rule can contain a number of expressions, date-expressions and even other rules. The results of the expressions are combined based on the rule’s <literal>boolean-op</literal> field to determine if the rule ultimately evaluates to <literal>true</literal> or <literal>false</literal>. What happens next depends on the context in which the rule is being used."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Rule Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Rule"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the rule (required) <indexterm> <primary>id</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Started</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Limits the rule to apply only when the resource is in the specified role. Allowed values are <literal>Started</literal>, <literal>Slave</literal>, and <literal>Master</literal>. A rule with <literal>role=\"Master\"</literal> cannot determine the initial location of a clone instance and will only affect which of the active instances will be promoted. <indexterm> <primary>role</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>score</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The score to apply if the rule evaluates to <literal>true</literal>. Limited to use in rules that are part of location constraints. <indexterm> <primary>score</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>score-attribute</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The node attribute to look up and use as a score if the rule evaluates to <literal>true</literal>. Limited to use in rules that are part of location constraints. <indexterm> <primary>score-attribute</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>score-attribute</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>score-attribute</secondary> </indexterm> <indexterm> <primary>score-attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>boolean-op</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>and</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How to combine the result of multiple expression objects. Allowed values are <literal>and</literal> and <literal>or</literal>. <indexterm> <primary>boolean-op</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>boolean-op</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>boolean-op</secondary> </indexterm> <indexterm> <primary>boolean-op</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Attribute Expressions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Attribute Expression</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary> </indexterm> <indexterm> <primary>Attribute Expression</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Expression objects are used to control a resource based on the attributes defined by a node or nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of an Expression"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the expression (required) <indexterm> <primary>id</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>attribute</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The node attribute to test (required) <indexterm> <primary>attribute</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>attribute</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>attribute</secondary> </indexterm> <indexterm> <primary>attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>type</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>string</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Determines how the value(s) should be tested. Allowed values are <literal>string</literal>, <literal>integer</literal>, and <literal>version</literal>. <indexterm> <primary>type</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>type</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>type</secondary> </indexterm> <indexterm> <primary>type</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>operation</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The comparison to perform (required). Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lt:</literal> True if the value of the node’s <literal>attribute</literal> is less than <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>gt:</literal> True if the value of the node’s <literal>attribute</literal> is greater than <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lte:</literal> True if the value of the node’s <literal>attribute</literal> is less than or equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>gte:</literal> True if the value of the node’s <literal>attribute</literal> is greater than or equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>eq:</literal> True if the value of the node’s <literal>attribute</literal> is equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>ne:</literal> True if the value of the node’s <literal>attribute</literal> is not equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>defined:</literal> True if the node has the named attribute"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>not_defined:</literal> True if the node does not have the named attribute <indexterm> <primary>operation</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "User-supplied value for comparison (required) <indexterm> <primary>value</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>value</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>value</secondary> </indexterm> <indexterm> <primary>value</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>value-source</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>literal</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "How the <literal>value</literal> is derived <emphasis>(since 1.1.17)</emphasis>. Allowed values:"
+msgid "How the <literal>value</literal> is derived. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>literal</literal>: <literal>value</literal> is a literal string to compare against"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>param</literal>: <literal>value</literal> is the name of a resource parameter to compare against (only valid in location constraints)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>meta</literal>: <literal>value</literal> is the name of a resource meta-attribute to compare against (only valid in location constraints) <indexterm> <primary>value</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>value</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>value</secondary> </indexterm> <indexterm> <primary>value</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In addition to any attributes added by the administrator, the cluster defines special, built-in node attributes for each node that can also be used."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Built-in node attributes"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Name"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Value"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#uname</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Node name"
+msgid "Node <link linkend=\"s-node-name\">name</link>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>#id</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Node ID"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#kind</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Node type. Possible values are <literal>cluster</literal>, <literal>remote</literal>, and <literal>container</literal>. Kind is <literal>remote</literal> for Pacemaker Remote nodes created with the <literal>ocf:pacemaker:remote</literal> resource, and <literal>container</literal> for Pacemaker Remote guest nodes (a legacy name unrelated to the now-common use of \"container\" for resource isolation). <emphasis>(since 1.1.13)</emphasis>"
+msgid "Node type. Possible values are <literal>cluster</literal>, <literal>remote</literal>, and <literal>container</literal>. Kind is <literal>remote</literal> for Pacemaker Remote nodes created with the <literal>ocf:pacemaker:remote</literal> resource, and <literal>container</literal> for Pacemaker Remote guest nodes and bundle nodes"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>#is_dc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "\"true\" if this node is a Designated Controller (DC), \"false\" otherwise"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>#cluster-name</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <literal>cluster-name</literal> cluster property, if set"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>#site-name</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <literal>site-name</literal> cluster property, if set, otherwise identical to <literal>#cluster-name</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>#role</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The role the relevant promotable clone resource has on this node. Valid only within a rule for a location constraint for a promotable clone resource."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Time- and Date-Based Expressions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Time Based Expressions</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Date/Time Expression</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary> </indexterm> <indexterm> <primary>Date/Time Expression</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As the name suggests, <literal>date_expressions</literal> are used to control a resource or cluster option based on the current date/time. They may contain an optional <literal>date_spec</literal> and/or <literal>duration</literal> object depending on the context."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Date Expression"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>start</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A date/time conforming to the <ulink url=\"http://en.wikipedia.org/wiki/ISO_8601\">ISO8601</ulink> specification. <indexterm> <primary>start</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary><tertiary>start</tertiary> </indexterm> <indexterm> <primary>Date/Time Expression</primary><secondary>start</secondary> </indexterm> <indexterm> <primary>start</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>end</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A date/time conforming to the <ulink url=\"http://en.wikipedia.org/wiki/ISO_8601\">ISO8601</ulink> specification. Can be inferred by supplying a value for <literal>start</literal> and a <literal>duration</literal>. <indexterm> <primary>end</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary><tertiary>end</tertiary> </indexterm> <indexterm> <primary>Date/Time Expression</primary><secondary>end</secondary> </indexterm> <indexterm> <primary>end</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Compares the current date/time with the start and/or end date, depending on the context. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>gt:</literal> True if the current date/time is after <literal>start</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lt:</literal> True if the current date/time is before <literal>end</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>in_range:</literal> True if the current date/time is after <literal>start</literal> and before <literal>end</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>date_spec:</literal> True if the current date/time matches a <literal>date_spec</literal> object (described below) <indexterm> <primary>operation</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>Date/Time Expression</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As these comparisons (except for <literal>date_spec</literal>) include the time, the <literal>eq</literal>, <literal>neq</literal>, <literal>gte</literal> and <literal>lte</literal> operators have not been implemented since they would only be valid for a single second."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Date Specifications"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Date Specification</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>date_spec</literal> objects are used to create cron-like expressions relating to time. Each field can contain a single number or a single range. Instead of defaulting to zero, any field not supplied is ignored."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, <literal>monthdays=\"1\"</literal> matches the first day of every month and <literal>hours=\"09-17\"</literal> matches the hours between 9am and 5pm (inclusive). At this time, multiple ranges (e.g. <literal>weekdays=\"1,2\"</literal> or <literal>weekdays=\"1-2,5-6\"</literal>) are not supported; depending on demand, this might be implemented in a future release."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Date Specification"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the object <indexterm> <primary>id</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>hours</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 0-23 <indexterm> <primary>hours</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>hours</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>hours</secondary> </indexterm> <indexterm> <primary>hours</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>monthdays</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-31 (depending on month and year) <indexterm> <primary>monthdays</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>monthdays</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>monthdays</secondary> </indexterm> <indexterm> <primary>monthdays</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>weekdays</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-7 (1=Monday, 7=Sunday) <indexterm> <primary>weekdays</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>weekdays</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>weekdays</secondary> </indexterm> <indexterm> <primary>weekdays</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>yeardays</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-366 (depending on the year) <indexterm> <primary>yeardays</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>yeardays</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>yeardays</secondary> </indexterm> <indexterm> <primary>yeardays</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>months</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-12 <indexterm> <primary>months</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>months</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>months</secondary> </indexterm> <indexterm> <primary>months</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>weeks</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-53 (depending on weekyear) <indexterm> <primary>weeks</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>weeks</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>weeks</secondary> </indexterm> <indexterm> <primary>weeks</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>years</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Year according to the Gregorian calendar <indexterm> <primary>years</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>years</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>years</secondary> </indexterm> <indexterm> <primary>years</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>weekyears</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Year in which the week started; e.g. 1 January 2005 can be specified as <emphasis>2005-001 Ordinal</emphasis>, <emphasis>2005-01-01 Gregorian</emphasis> or <emphasis>2004-W53-6 Weekly</emphasis> and thus would match <literal>years=\"2005\"</literal> or <literal>weekyears=\"2004\"</literal> <indexterm> <primary>weekyears</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>weekyears</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>weekyears</secondary> </indexterm> <indexterm> <primary>weekyears</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>moon</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values are 0-7 (0 is new, 4 is full moon). Seriously, you can use this. This was implemented to demonstrate the ease with which new comparisons could be added. <indexterm> <primary>moon</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>moon</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>moon</secondary> </indexterm> <indexterm> <primary>moon</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Durations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Duration</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Duration</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Duration</secondary> </indexterm> <indexterm> <primary>Duration</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Durations are used to calculate a value for <literal>end</literal> when one is not supplied to <literal>in_range</literal> operations. They contain the same fields as <literal>date_spec</literal> objects but without the limitations (e.g. you can have a duration of 19 months). As with <literal>date_specs</literal>, any field not supplied is ignored."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sample Time-Based Expressions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A small sample of how time-based expressions can be used:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "True if now is any time in the year 2005"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule1\"&gt;\n"
" &lt;date_expression id=\"date_expr1\" start=\"2005-001\" operation=\"in_range\"&gt;\n"
" &lt;duration years=\"1\"/&gt;\n"
" &lt;/date_expression&gt;\n"
"&lt;/rule&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Equivalent expression"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule2\"&gt;\n"
" &lt;date_expression id=\"date_expr2\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec years=\"2005\"/&gt;\n"
" &lt;/date_expression&gt;\n"
"&lt;/rule&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "9am-5pm Monday-Friday"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule3\"&gt;\n"
" &lt;date_expression id=\"date_expr3\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec hours=\"9-16\" days=\"1-5\"/&gt;\n"
" &lt;/date_expression&gt;\n"
"&lt;/rule&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Please note that the <literal>16</literal> matches up to <literal>16:59:59</literal>, as the numeric value (hour) still matches!"
msgstr ""
#. Tag: title
#, no-c-format
msgid "9am-6pm Monday through Friday or anytime Saturday"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule4\" boolean-op=\"or\"&gt;\n"
" &lt;date_expression id=\"date_expr4-1\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec hours=\"9-16\" days=\"1-5\"/&gt;\n"
" &lt;/date_expression&gt;\n"
" &lt;date_expression id=\"date_expr4-2\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec days=\"6\"/&gt;\n"
" &lt;/date_expression&gt;\n"
"&lt;/rule&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "9am-5pm or 9pm-12am Monday through Friday"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule5\" boolean-op=\"and\"&gt;\n"
" &lt;rule id=\"rule5-nested1\" boolean-op=\"or\"&gt;\n"
" &lt;date_expression id=\"date_expr5-1\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec hours=\"9-16\"/&gt;\n"
" &lt;/date_expression&gt;\n"
" &lt;date_expression id=\"date_expr5-2\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec hours=\"21-23\"/&gt;\n"
" &lt;/date_expression&gt;\n"
" &lt;/rule&gt;\n"
" &lt;date_expression id=\"date_expr5-3\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec days=\"1-5\"/&gt;\n"
" &lt;/date_expression&gt;\n"
" &lt;/rule&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mondays in March 2005"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule6\" boolean-op=\"and\"&gt;\n"
" &lt;date_expression id=\"date_expr6-1\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec weekdays=\"1\"/&gt;\n"
" &lt;/date_expression&gt;\n"
" &lt;date_expression id=\"date_expr6-2\" operation=\"in_range\"\n"
" start=\"2005-03-01\" end=\"2005-04-01\"/&gt;\n"
" &lt;/rule&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Because no time is specified with the above dates, 00:00:00 is implied. This means that the range includes all of 2005-03-01 but none of 2005-04-01. You may wish to write <literal>end=\"2005-03-31T23:59:59\"</literal> to avoid confusion."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A full moon on Friday the 13th"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"rule7\" boolean-op=\"and\"&gt;\n"
" &lt;date_expression id=\"date_expr7\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec weekdays=\"5\" monthdays=\"13\" moon=\"4\"/&gt;\n"
" &lt;/date_expression&gt;\n"
"&lt;/rule&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Rules to Determine Resource Location"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Rule</primary><secondary>Determine Resource Location</secondary> </indexterm> <indexterm> <primary>Determine Resource Location</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Location</secondary><tertiary>Determine by Rules</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>Determine by Rules</secondary> </indexterm> <indexterm> <primary>Determine by Rules</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A location constraint may contain rules. When the constraint’s outermost rule evaluates to <literal>false</literal>, the cluster treats the constraint as if it were not there. When the rule evaluates to <literal>true</literal>, the node’s preference for running the resource is updated with the score associated with the rule."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If this sounds familiar, it is because you have been using a simplified syntax for location constraint rules already. Consider the following location constraint:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prevent myApacheRsc from running on c001n03"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\"\n"
" score=\"-INFINITY\" node=\"c001n03\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This constraint can be more verbosely written as:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prevent myApacheRsc from running on c001n03 - expanded version"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\"&gt;\n"
" &lt;rule id=\"dont-run-apache-rule\" score=\"-INFINITY\"&gt;\n"
" &lt;expression id=\"dont-run-apache-expr\" attribute=\"#uname\"\n"
" operation=\"eq\" value=\"c00n03\"/&gt;\n"
" &lt;/rule&gt;\n"
"&lt;/rsc_location&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The advantage of using the expanded form is that one can then add extra clauses to the rule, such as limiting the rule such that it only applies during certain times of the day or days of the week."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Location Rules Based on Other Node Properties"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The expanded form allows us to match on node properties other than its name. If we rated each machine’s CPU power such that the cluster had the following nodes section:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A sample nodes section for use with score-attribute"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;nodes&gt;\n"
" &lt;node id=\"uuid1\" uname=\"c001n01\" type=\"normal\"&gt;\n"
" &lt;instance_attributes id=\"uuid1-custom_attrs\"&gt;\n"
" &lt;nvpair id=\"uuid1-cpu_mips\" name=\"cpu_mips\" value=\"1234\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/node&gt;\n"
" &lt;node id=\"uuid2\" uname=\"c001n02\" type=\"normal\"&gt;\n"
" &lt;instance_attributes id=\"uuid2-custom_attrs\"&gt;\n"
" &lt;nvpair id=\"uuid2-cpu_mips\" name=\"cpu_mips\" value=\"5678\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/node&gt;\n"
"&lt;/nodes&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "then we could prevent resources from running on underpowered machines with this rule:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rule id=\"need-more-power-rule\" score=\"-INFINITY\"&gt;\n"
" &lt;expression id=\"need-more-power-expr\" attribute=\"cpu_mips\"\n"
" operation=\"lt\" value=\"3000\"/&gt;\n"
"&lt;/rule&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using <literal>score-attribute</literal> Instead of <literal>score</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When using <literal>score-attribute</literal> instead of <literal>score</literal>, each node matched by the rule has its score adjusted differently, according to its value for the named node attribute. Thus, in the previous example, if a rule used <literal>score-attribute=\"cpu_mips\"</literal>, <literal>c001n01</literal> would have its preference to run the resource increased by <literal>1234</literal> whereas <literal>c001n02</literal> would have its preference increased by <literal>5678</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Rules to Control Resource Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Often some cluster nodes will be different from their peers. Sometimes, these differences — e.g. the location of a binary or the names of network interfaces — require resources to be configured differently depending on the machine they’re hosted on."
msgstr ""
#. Tag: para
#, no-c-format
msgid "By defining multiple <literal>instance_attributes</literal> objects for the resource and adding a rule to each, we can easily handle these special cases."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example below, <literal>mySpecialRsc</literal> will use eth1 and port 9999 when run on <literal>node1</literal>, eth2 and port 8888 on <literal>node2</literal> and default to eth0 and port 9999 for all other nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Defining different resource options based on the node name"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\"&gt;\n"
" &lt;instance_attributes id=\"special-node1\" score=\"3\"&gt;\n"
" &lt;rule id=\"node1-special-case\" score=\"INFINITY\" &gt;\n"
" &lt;expression id=\"node1-special-case-expr\" attribute=\"#uname\"\n"
" operation=\"eq\" value=\"node1\"/&gt;\n"
" &lt;/rule&gt;\n"
" &lt;nvpair id=\"node1-interface\" name=\"interface\" value=\"eth1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;instance_attributes id=\"special-node2\" score=\"2\" &gt;\n"
" &lt;rule id=\"node2-special-case\" score=\"INFINITY\"&gt;\n"
" &lt;expression id=\"node2-special-case-expr\" attribute=\"#uname\"\n"
" operation=\"eq\" value=\"node2\"/&gt;\n"
" &lt;/rule&gt;\n"
" &lt;nvpair id=\"node2-interface\" name=\"interface\" value=\"eth2\"/&gt;\n"
" &lt;nvpair id=\"node2-port\" name=\"port\" value=\"8888\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;instance_attributes id=\"defaults\" score=\"1\" &gt;\n"
" &lt;nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/&gt;\n"
" &lt;nvpair id=\"default-port\" name=\"port\" value=\"9999\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The order in which <literal>instance_attributes</literal> objects are evaluated is determined by their score (highest to lowest). If not supplied, score defaults to zero, and objects with an equal score are processed in listed order. If the <literal>instance_attributes</literal> object has no rule or a <literal>rule</literal> that evaluates to <literal>true</literal>, then for any parameter the resource does not yet have a value for, the resource will use the parameter values defined by the <literal>instance_attributes</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, given the configuration above, if the resource is placed on node1:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>special-node1</literal> has the highest score (3) and so is evaluated first; its rule evaluates to <literal>true</literal>, so <literal>interface</literal> is set to <literal>eth1</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>special-node2</literal> is evaluated next with score 2, but its rule evaluates to <literal>false</literal>, so it is ignored."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>defaults</literal> is evaluated last with score 1, and has no rule, so its values are examined; <literal>interface</literal> is already defined, so the value here is not used, but <literal>port</literal> is not yet defined, so <literal>port</literal> is set to <literal>9999</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Rules to Control Cluster Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Rule</primary><secondary>Controlling Cluster Options</secondary> </indexterm> <indexterm> <primary>Controlling Cluster Options</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Setting Options with Rules</secondary> </indexterm> <indexterm> <primary>Setting Options with Rules</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Controlling cluster options is achieved in much the same manner as specifying different resource options on different nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The difference is that because they are cluster options, one cannot (or should not, because they won’t work) use attribute-based expressions. The following example illustrates how to set a different <literal>resource-stickiness</literal> value during and outside work hours. This allows resources to automatically move back to their most preferred hosts, but at a time that (in theory) does not interfere with business activities."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Change <literal>resource-stickiness</literal> during working hours"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;rsc_defaults&gt;\n"
" &lt;meta_attributes id=\"core-hours\" score=\"2\"&gt;\n"
" &lt;rule id=\"core-hour-rule\" score=\"0\"&gt;\n"
" &lt;date_expression id=\"nine-to-five-Mon-to-Fri\" operation=\"date_spec\"&gt;\n"
" &lt;date_spec id=\"nine-to-five-Mon-to-Fri-spec\" hours=\"9-16\" weekdays=\"1-5\"/&gt;\n"
" &lt;/date_expression&gt;\n"
" &lt;/rule&gt;\n"
" &lt;nvpair id=\"core-stickiness\" name=\"resource-stickiness\" value=\"INFINITY\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;meta_attributes id=\"after-hours\" score=\"1\" &gt;\n"
" &lt;nvpair id=\"after-stickiness\" name=\"resource-stickiness\" value=\"0\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
"&lt;/rsc_defaults&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ensuring Time-Based Rules Take Effect"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A Pacemaker cluster is an event-driven system. As such, it won’t recalculate the best place for resources to run unless something (like a resource failure or configuration change) happens. This can mean that a location constraint that only allows resource X to run between 9am and 5pm is not enforced."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you rely on time-based rules, the <literal>cluster-recheck-interval</literal> cluster option (which defaults to 15 minutes) is essential. This tells the cluster to periodically recalculate the ideal state of the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, if you set <literal>cluster-recheck-interval=\"5m\"</literal>, then sometime between 09:00 and 09:05 the cluster would notice that it needs to start resource X, and between 17:00 and 17:05 it would realize that X needed to be stopped. The timing of the actual start and stop actions depends on what other actions the cluster may need to perform first."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Status.pot b/doc/Pacemaker_Explained/pot/Ch-Status.pot
index 94bf0af95e..1e5728c69d 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Status.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Status.pot
@@ -1,632 +1,622 @@
#
# 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"
+"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 "Status — Here be dragons"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Most users never need to understand the contents of the status section and can be happy with the output from <literal>crm_mon</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "However for those with a curious inclination, this section attempts to provide an overview of its contents."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Status"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Node</primary><secondary>Status</secondary> </indexterm> <indexterm> <primary>Status</primary> </indexterm> <indexterm> <primary>Status of a Node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In addition to the cluster’s configuration, the CIB holds an up-to-date representation of each cluster node in the <literal>status</literal> section."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A bare-bones status entry for a healthy node <emphasis role=\"strong\">cl-virt-1</emphasis>"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid " &lt;node_state id=\"cl-virt-1\" uname=\"cl-virt-2\" ha=\"active\" in_ccm=\"true\" crmd=\"online\" join=\"member\" expected=\"member\" crm-debug-origin=\"do_update_resource\"&gt;\n"
-" &lt;transient_attributes id=\"cl-virt-1\"/&gt;\n"
-" &lt;lrm id=\"cl-virt-1\"/&gt;\n"
+msgid " &lt;node_state id=\"1\" uname=\"cl-virt-1\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_update_resource\" join=\"member\" expected=\"member\"&gt;\n"
+" &lt;transient_attributes id=\"1\"/&gt;\n"
+" &lt;lrm id=\"1\"/&gt;\n"
" &lt;/node_state&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Users are highly recommended <emphasis>not</emphasis> to modify any part of a node’s state <emphasis>directly</emphasis>. The cluster will periodically regenerate the entire section from authoritative sources, so any changes should be done with the tools appropriate to those sources."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Authoritative Sources for State Information"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "CIB Object"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Authoritative Source"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>node_state</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "crmd"
+msgid "pacemaker-controld"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>transient_attributes</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "attrd"
+msgid "pacemaker-attrd"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lrm</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "lrmd"
+msgid "pacemaker-execd"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The fields used in the <literal>node_state</literal> objects are named as they are largely for historical reasons and are rooted in Pacemaker’s origins as the Heartbeat resource manager. They have remained unchanged to preserve compatibility with older versions."
+msgid "The fields used in the <literal>node_state</literal> objects are named as they are largely for historical reasons and are rooted in Pacemaker’s origins as the resource manager for the older Heartbeat project. They have remained unchanged to preserve compatibility with older versions."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Status Fields"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>id</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm> Unique identifier for the node. Corosync-based clusters use a numeric counter, while Heartbeat clusters use a (barely) human-readable UUID."
+msgid "<indexterm> <primary>id</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm> Unique identifier for the node. Corosync-based clusters use a numeric counter."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>uname</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>uname</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>uname</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>uname</secondary> </indexterm> <indexterm> <primary>uname</primary> </indexterm> The node’s machine name (output from <literal>uname -n</literal>)."
+msgid "<indexterm> <primary>uname</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>uname</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>uname</secondary> </indexterm> <indexterm> <primary>uname</primary> </indexterm> The node’s name as known by the cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>ha</literal>"
+msgid "<literal>in_ccm</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>ha</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>ha</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>ha</secondary> </indexterm> <indexterm> <primary>ha</primary> </indexterm> Is the cluster software active on this node? Allowed values: <literal>active</literal>, <literal>dead</literal>."
+msgid "<indexterm> <primary>in_ccm</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>in_ccm</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>in_ccm</secondary> </indexterm> <indexterm> <primary>in_ccm</primary> </indexterm> Is the node a member at the cluster communication layer? Allowed values: <literal>true</literal>, <literal>false</literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>in_ccm</literal>"
+msgid "<literal>crmd</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>in_ccm</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>in_ccm</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>in_ccm</secondary> </indexterm> <indexterm> <primary>in_ccm</primary> </indexterm> Is the node a member of the cluster? Allowed values: <literal>true</literal>, <literal>false</literal>."
+msgid "<indexterm> <primary>crmd</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>crmd</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>crmd</secondary> </indexterm> <indexterm> <primary>crmd</primary> </indexterm> Is the node a member at the pacemaker layer? Allowed values: <literal>online</literal>, <literal>offline</literal>."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>crmd</literal>"
+msgid "<literal>crm-debug-origin</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>crmd</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>crmd</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>crmd</secondary> </indexterm> <indexterm> <primary>crmd</primary> </indexterm> Is the crmd process active on the node? Allowed values: <literal>online</literal>, <literal>offline</literal>."
+msgid "<indexterm> <primary>crm-debug-origin</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>crm-debug-origin</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>crm-debug-origin</secondary> </indexterm> <indexterm> <primary>crm-debug-origin</primary> </indexterm> The name of the source function that made the most recent change (for debugging purposes)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>join</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>join</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>join</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>join</secondary> </indexterm> <indexterm> <primary>join</primary> </indexterm> Does the node participate in hosting resources? Allowed values: <literal>down</literal>, <literal>pending</literal>, <literal>member</literal>, <literal>banned</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>expected</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>expected</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>expected</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>expected</secondary> </indexterm> <indexterm> <primary>expected</primary> </indexterm> Expected value for <literal>join</literal>."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "<literal>crm-debug-origin</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<indexterm> <primary>crm-debug-origin</primary><secondary>Node Status</secondary> </indexterm> <indexterm> <primary>Node Status</primary> </indexterm> <indexterm> <primary>Node</primary><secondary>Status</secondary><tertiary>crm-debug-origin</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>crm-debug-origin</secondary> </indexterm> <indexterm> <primary>crm-debug-origin</primary> </indexterm> The origin of the most recent change(s). For diagnostic purposes."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "The cluster uses these fields to determine whether, at the node level, the node is healthy or is in a failed state and needs to be fenced."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Transient Node Attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Like regular <link linkend=\"s-node-attributes\">node attributes</link>, the name/value pairs listed in the <literal>transient_attributes</literal> section help to describe the node. However they are forgotten by the cluster when the node goes offline. This can be useful, for instance, when you want a node to be in standby mode (not able to run resources) just until the next reboot."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In addition to any values the administrator sets, the cluster will also store information about failed resources here."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A set of transient node attributes for node <emphasis role=\"strong\">cl-virt-1</emphasis>"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;transient_attributes id=\"cl-virt-1\"&gt;\n"
" &lt;instance_attributes id=\"status-cl-virt-1\"&gt;\n"
" &lt;nvpair id=\"status-cl-virt-1-pingd\" name=\"pingd\" value=\"3\"/&gt;\n"
" &lt;nvpair id=\"status-cl-virt-1-probe_complete\" name=\"probe_complete\" value=\"true\"/&gt;\n"
-" &lt;nvpair id=\"status-cl-virt-1-fail-count-pingd:0\" name=\"fail-count-pingd:0\" value=\"1\"/&gt;\n"
+" &lt;nvpair id=\"status-cl-virt-1-fail-count-pingd:0.monitor_30000\" name=\"fail-count-pingd:0#monitor_30000\" value=\"1\"/&gt;\n"
" &lt;nvpair id=\"status-cl-virt-1-last-failure-pingd:0\" name=\"last-failure-pingd:0\" value=\"1239009742\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/transient_attributes&gt;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the above example, we can see that the <literal>pingd:0</literal> resource has failed once, at 09:22:22 UTC 6 April 2009. <footnote><para> You can use the standard <literal>date</literal> command to print a human-readable version of any seconds-since-epoch value, for example <literal>date -d @1239009742</literal>. </para></footnote> We also see that the node is connected to three <emphasis role=\"strong\">pingd</emphasis> peers and that all known resources have been checked for on this machine (<literal>probe_complete</literal>)."
+msgid "In the above example, we can see that a monitor on the <literal>pingd:0</literal> resource has failed once, at 09:22:22 UTC 6 April 2009. <footnote><para> You can use the standard <literal>date</literal> command to print a human-readable version of any seconds-since-epoch value, for example <literal>date -d @1239009742</literal>. </para></footnote> We also see that the node is connected to three <emphasis role=\"strong\">pingd</emphasis> peers and that all known resources have been checked for on this machine (<literal>probe_complete</literal>)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Operation History"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Operation History</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A node’s resource history is held in the <literal>lrm_resources</literal> tag (a child of the <literal>lrm</literal> tag). The information stored here includes enough information for the cluster to stop the resource safely if it is removed from the <literal>configuration</literal> section. Specifically, the resource’s <literal>id</literal>, <literal>class</literal>, <literal>type</literal> and <literal>provider</literal> are stored."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A record of the <literal>apcstonith</literal> resource"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\"/&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Additionally, we store the last job for every combination of <literal>resource</literal>, <literal>action</literal> and <literal>interval</literal>. The concatenation of the values in this tuple are used to create the id of the <literal>lrm_rsc_op</literal> object."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Contents of an <literal>lrm_rsc_op</literal> job"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>id</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Identifier for the job constructed from the resource’s <literal>id</literal>, <literal>operation</literal> and <literal>interval</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>call-id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>call-id</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>call-id</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>call-id</secondary> </indexterm> <indexterm> <primary>call-id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The job’s ticket number. Used as a sort key to determine the order in which the jobs were executed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>operation</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>operation</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The action the resource agent was invoked with."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>interval</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>interval</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>interval</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>interval</secondary> </indexterm> <indexterm> <primary>interval</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The frequency, in milliseconds, at which the operation will be repeated. A one-off job is indicated by 0."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>op-status</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>op-status</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>op-status</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>op-status</secondary> </indexterm> <indexterm> <primary>op-status</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The job’s status. Generally this will be either 0 (done) or -1 (pending). Rarely used in favor of <literal>rc-code</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rc-code</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>rc-code</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>rc-code</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>rc-code</secondary> </indexterm> <indexterm> <primary>rc-code</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The job’s result. Refer to <xref linkend=\"s-ocf-return-codes\" /> for details on what the values here mean and how they are interpreted."
+msgid "The job’s result. Refer to the <emphasis>Resource Agents</emphasis> section of <emphasis>Pacemaker Administration</emphasis> for details on what the values here mean and how they are interpreted."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>last-run</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>last-run</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>last-run</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>last-run</secondary> </indexterm> <indexterm> <primary>last-run</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Machine-local date/time, in seconds since epoch, at which the job was executed. For diagnostic purposes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>last-rc-change</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>last-rc-change</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>last-rc-change</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>last-rc-change</secondary> </indexterm> <indexterm> <primary>last-rc-change</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Machine-local date/time, in seconds since epoch, at which the job first returned the current value of <literal>rc-code</literal>. For diagnostic purposes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>exec-time</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>exec-time</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>exec-time</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>exec-time</secondary> </indexterm> <indexterm> <primary>exec-time</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Time, in milliseconds, that the job was running for. For diagnostic purposes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>queue-time</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>queue-time</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>queue-time</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>queue-time</secondary> </indexterm> <indexterm> <primary>queue-time</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Time, in seconds, that the job was queued for in the LRMd. For diagnostic purposes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>crm_feature_set</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>crm_feature_set</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>crm_feature_set</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>crm_feature_set</secondary> </indexterm> <indexterm> <primary>crm_feature_set</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The version which this job description conforms to. Used when processing <literal>op-digest</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>transition-key</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>transition-key</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>transition-key</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>transition-key</secondary> </indexterm> <indexterm> <primary>transition-key</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A concatenation of the job’s graph action number, the graph number, the expected result and the UUID of the crmd instance that scheduled it. This is used to construct <literal>transition-magic</literal> (below)."
+msgid "A concatenation of the job’s graph action number, the graph number, the expected result and the UUID of the controller instance that scheduled it. This is used to construct <literal>transition-magic</literal> (below)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>transition-magic</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>transition-magic</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>transition-magic</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>transition-magic</secondary> </indexterm> <indexterm> <primary>transition-magic</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A concatenation of the job’s <literal>op-status</literal>, <literal>rc-code</literal> and <literal>transition-key</literal>. Guaranteed to be unique for the life of the cluster (which ensures it is part of CIB update notifications) and contains all the information needed for the crmd to correctly analyze and process the completed job. Most importantly, the decomposed elements tell the crmd if the job entry was expected and whether it failed."
+msgid "A concatenation of the job’s <literal>op-status</literal>, <literal>rc-code</literal> and <literal>transition-key</literal>. Guaranteed to be unique for the life of the cluster (which ensures it is part of CIB update notifications) and contains all the information needed for the controller to correctly analyze and process the completed job. Most importantly, the decomposed elements tell the controller if the job entry was expected and whether it failed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>op-digest</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>op-digest</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>op-digest</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>op-digest</secondary> </indexterm> <indexterm> <primary>op-digest</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "An MD5 sum representing the parameters passed to the job. Used to detect changes to the configuration, to restart resources if necessary."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>crm-debug-origin</primary><secondary>Action Status</secondary> </indexterm> <indexterm> <primary>Action Status</primary> </indexterm> <indexterm> <primary>Action</primary><secondary>Status</secondary><tertiary>crm-debug-origin</tertiary> </indexterm> <indexterm> <primary>Status</primary><secondary>crm-debug-origin</secondary> </indexterm> <indexterm> <primary>crm-debug-origin</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The origin of the current values. For diagnostic purposes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Simple Operation History Example"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A monitor operation (determines current state of the <literal>apcstonith</literal> resource)"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\"&gt;\n"
" &lt;lrm_rsc_op id=\"apcstonith_monitor_0\" operation=\"monitor\" call-id=\"2\"\n"
" rc-code=\"7\" op-status=\"0\" interval=\"0\"\n"
" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.1\"\n"
" op-digest=\"2e3da9274d3550dc6526fb24bfcbcba0\"\n"
" transition-key=\"22:2:7:2668bbeb-06d5-40f9-936d-24cb7f87006a\"\n"
" transition-magic=\"0:7;22:2:7:2668bbeb-06d5-40f9-936d-24cb7f87006a\"\n"
" last-run=\"1239008085\" last-rc-change=\"1239008085\" exec-time=\"10\" queue-time=\"0\"/&gt;\n"
"&lt;/lrm_resource&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the above example, the job is a non-recurring monitor operation often referred to as a \"probe\" for the <literal>apcstonith</literal> resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster schedules probes for every configured resource on a node when the node first starts, in order to determine the resource’s current state before it takes any further action."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "From the <literal>transition-key</literal>, we can see that this was the 22nd action of the 2nd graph produced by this instance of the crmd (2668bbeb-06d5-40f9-936d-24cb7f87006a)."
+msgid "From the <literal>transition-key</literal>, we can see that this was the 22nd action of the 2nd graph produced by this instance of the controller (2668bbeb-06d5-40f9-936d-24cb7f87006a)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The third field of the <literal>transition-key</literal> contains a 7, which indicates that the job expects to find the resource inactive. By looking at the <literal>rc-code</literal> property, we see that this was the case."
msgstr ""
#. Tag: para
#, no-c-format
msgid "As that is the only job recorded for this node, we can conclude that the cluster started the resource elsewhere."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Complex Operation History Example"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource history of a <literal>pingd</literal> clone with multiple jobs"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;lrm_resource id=\"pingd:0\" type=\"pingd\" class=\"ocf\" provider=\"pacemaker\"&gt;\n"
" &lt;lrm_rsc_op id=\"pingd:0_monitor_30000\" operation=\"monitor\" call-id=\"34\"\n"
" rc-code=\"0\" op-status=\"0\" interval=\"30000\"\n"
" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.1\"\n"
" transition-key=\"10:11:0:2668bbeb-06d5-40f9-936d-24cb7f87006a\"\n"
" ...\n"
" last-run=\"1239009741\" last-rc-change=\"1239009741\" exec-time=\"10\" queue-time=\"0\"/&gt;\n"
" &lt;lrm_rsc_op id=\"pingd:0_stop_0\" operation=\"stop\"\n"
" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.1\" call-id=\"32\"\n"
" rc-code=\"0\" op-status=\"0\" interval=\"0\"\n"
" transition-key=\"11:11:0:2668bbeb-06d5-40f9-936d-24cb7f87006a\"\n"
" ...\n"
" last-run=\"1239009741\" last-rc-change=\"1239009741\" exec-time=\"10\" queue-time=\"0\"/&gt;\n"
" &lt;lrm_rsc_op id=\"pingd:0_start_0\" operation=\"start\" call-id=\"33\"\n"
" rc-code=\"0\" op-status=\"0\" interval=\"0\"\n"
" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.1\"\n"
" transition-key=\"31:11:0:2668bbeb-06d5-40f9-936d-24cb7f87006a\"\n"
" ...\n"
" last-run=\"1239009741\" last-rc-change=\"1239009741\" exec-time=\"10\" queue-time=\"0\" /&gt;\n"
" &lt;lrm_rsc_op id=\"pingd:0_monitor_0\" operation=\"monitor\" call-id=\"3\"\n"
" rc-code=\"0\" op-status=\"0\" interval=\"0\"\n"
" crm-debug-origin=\"do_update_resource\" crm_feature_set=\"3.0.1\"\n"
" transition-key=\"23:2:7:2668bbeb-06d5-40f9-936d-24cb7f87006a\"\n"
" ...\n"
" last-run=\"1239008085\" last-rc-change=\"1239008085\" exec-time=\"20\" queue-time=\"0\"/&gt;\n"
" &lt;/lrm_resource&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When more than one job record exists, it is important to first sort them by <literal>call-id</literal> before interpreting them."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once sorted, the above example can be summarized as:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A non-recurring monitor operation returning 7 (not running), with a <literal>call-id</literal> of 3"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A stop operation returning 0 (success), with a <literal>call-id</literal> of 32"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A start operation returning 0 (success), with a <literal>call-id</literal> of 33"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A recurring monitor returning 0 (success), with a <literal>call-id</literal> of 34"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster processes each job record to build up a picture of the resource’s state. After the first and second entries, it is considered stopped, and after the third it considered active."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Based on the last operation, we can tell that the resource is currently active."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Additionally, from the presence of a <literal>stop</literal> operation with a lower <literal>call-id</literal> than that of the <literal>start</literal> operation, we can conclude that the resource has been restarted. Specifically this occurred as part of actions 11 and 31 of transition 11 from the crmd instance with the key <literal>2668bbeb…</literal>. This information can be helpful for locating the relevant section of the logs when looking for the source of a failure."
+msgid "Additionally, from the presence of a <literal>stop</literal> operation with a lower <literal>call-id</literal> than that of the <literal>start</literal> operation, we can conclude that the resource has been restarted. Specifically this occurred as part of actions 11 and 31 of transition 11 from the controller instance with the key <literal>2668bbeb…</literal>. This information can be helpful for locating the relevant section of the logs when looking for the source of a failure."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Ch-Stonith.pot b/doc/Pacemaker_Explained/pot/Ch-Stonith.pot
index 9a896c3ee8..85487a23eb 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Stonith.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Stonith.pot
@@ -1,1297 +1,1297 @@
#
# 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"
+"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 "STONITH"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<anchor id=\"ch-stonith\" xreflabel=\"Chapter 13, STONITH\"></anchor> <indexterm> <primary>STONITH</primary><secondary>Configuration</secondary> </indexterm> <indexterm> <primary>Configuration</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "What Is STONITH?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "STONITH (an acronym for \"Shoot The Other Node In The Head\"), also called <emphasis>fencing</emphasis>, protects your data from being corrupted by rogue nodes or concurrent access."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Just because a node is unresponsive, this doesn’t mean it isn’t accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere."
msgstr ""
#. Tag: title
#, no-c-format
msgid "What STONITH Device Should You Use?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The biggest mistake people make in choosing a STONITH device is to use a remote power switch (such as many on-board IPMI controllers) that shares power with the node it controls. In such cases, the cluster cannot be sure if the node is really offline, or active and suffering from a network fault."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Likewise, any device that relies on the machine being active (such as SSH-based \"devices\" used during testing) are inappropriate."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Special Treatment of STONITH Resources"
msgstr ""
#. Tag: para
#, no-c-format
msgid "STONITH resources are somewhat special in Pacemaker."
msgstr ""
#. Tag: para
#, no-c-format
msgid "STONITH may be initiated by pacemaker or by other parts of the cluster (such as resources like DRBD or DLM). To accommodate this, pacemaker does not require the STONITH resource to be in the <emphasis>started</emphasis> state in order to be used, thus allowing reliable use of STONITH devices in such a case."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "In pacemaker versions 1.1.9 and earlier, this feature either did not exist or did not work well. Only \"running\" STONITH resources could be used by Pacemaker for fencing, and if another component tried to fence a node while Pacemaker was moving STONITH resources, the fencing could fail."
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "All nodes have access to STONITH devices' definitions and instantiate them on-the-fly when needed, but preference is given to <emphasis>verified</emphasis> instances, which are the ones that are <emphasis>started</emphasis> according to the cluster’s knowledge."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the case of a cluster split, the partition with a verified instance will have a slight advantage, because the STONITH daemon in the other partition will have to hear from all its current peers before choosing a node to perform the fencing."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Fencing resources do work the same as regular resources in some respects:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target-role</literal> can be used to enable or disable the resource"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Location constraints can be used to prevent a specific node from using the resource"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Currently there is a limitation that fencing resources may only have one set of meta-attributes and one set of instance attributes. This can be revisited if it becomes a significant limitation for people."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "See the table below or run <literal>man stonithd</literal> to see special instance attributes that may be set for any fencing resource, regardless of fence agent."
+msgid "See the table below or run <literal>man pacemaker-fenced</literal> to see special instance attributes that may be set for any fencing resource, regardless of fence agent."
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Properties of Fencing Resources"
+msgid "Additional Properties of Fencing Resources"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Type"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>stonith-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "NA"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Older versions used this to override the default period to wait for a STONITH (reboot, on, off) action to complete for this device. It has been replaced by the <literal>pcmk_reboot_timeout</literal> and <literal>pcmk_off_timeout</literal> properties. <indexterm> <primary>stonith-timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>stonith-timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>stonith-timeout</secondary> </indexterm> <indexterm> <primary>stonith-timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>priority</literal>"
+msgid "<literal>provides</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "integer"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "0"
+msgid "string"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The priority of the STONITH resource. Devices are tried in order of highest priority to lowest. <indexterm> <primary>priority</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>priority</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>priority</secondary> </indexterm> <indexterm> <primary>priority</primary> </indexterm>"
+msgid "Any special capability provided by the fence device. Currently, only one such capability is meaningful: <literal>unfencing</literal> (see <xref linkend=\"s-unfencing\" />). <indexterm> <primary>priority</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>priority</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>priority</secondary> </indexterm> <indexterm> <primary>priority</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_host_map</literal>"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "string"
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "A mapping of host names to ports numbers for devices that do not support host names. Example: <literal>node1:1;node2:2,3</literal> tells the cluster to use port 1 for <emphasis role=\"strong\">node1</emphasis> and ports 2 and 3 for <emphasis role=\"strong\">node2</emphasis>. <indexterm> <primary>pcmk_host_map</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_host_map</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_host_map</secondary> </indexterm> <indexterm> <primary>pcmk_host_map</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_host_list</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A list of machines controlled by this device (optional unless <literal>pcmk_host_check</literal> is <literal>static-list</literal>). <indexterm> <primary>pcmk_host_list</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_host_list</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_host_list</secondary> </indexterm> <indexterm> <primary>pcmk_host_list</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_host_check</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "dynamic-list"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How to determine which machines are controlled by the device. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>dynamic-list:</literal> query the device"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>static-list:</literal> check the <literal>pcmk_host_list</literal> attribute"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>none:</literal> assume every device can fence every machine"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>pcmk_host_check</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_host_check</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_host_check</secondary> </indexterm> <indexterm> <primary>pcmk_host_check</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_delay_max</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "time"
msgstr ""
#. Tag: para
#, no-c-format
msgid "0s"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Enable a random delay of up to the time specified before executing stonith actions. This is sometimes used in two-node clusters to ensure that the nodes don’t fence each other at the same time. The overall delay is derived from this random delay value adding a static delay so that the sum is kept below the maximum delay."
+msgid "Enable a random delay of up to the time specified before executing stonith actions. This is sometimes used in two-node clusters to ensure that the nodes don’t fence each other at the same time. The overall delay introduced by pacemaker is derived from this random delay value adding a static delay so that the sum is kept below the maximum delay."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>pcmk_delay_max</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_delay_max</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_delay_max</secondary> </indexterm> <indexterm> <primary>pcmk_delay_max</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_delay_base</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "time"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "0s"
+msgid "Enable a static delay before executing stonith actions. This can be used e.g. in two-node clusters to ensure that the nodes don’t fence each other, by having separate fencing resources with different values. The node that is fenced with the shorter delay will lose a fencing race. The overall delay introduced by pacemaker is derived from this value plus a random delay such that the sum is kept below the maximum delay."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Enable a base delay for stonith actions and specify base delay value. This prevents double fencing when different delays are configured on the nodes. The overall delay is derived from a random delay value adding this static delay so that the sum is kept below the maximum delay."
+msgid "<indexterm> <primary>pcmk_delay_base</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_delay_base</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_delay_base</secondary> </indexterm> <indexterm> <primary>pcmk_delay_base</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<indexterm> <primary>pcmk_delay_base</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_delay_base</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_delay_base</secondary> </indexterm> <indexterm> <primary>pcmk_delay_base</primary> </indexterm>"
+msgid "<literal>pcmk_action_limit</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "<literal>pcmk_action_limit</literal>"
+msgid "integer"
msgstr ""
#. Tag: para
#, no-c-format
msgid "1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The maximum number of actions that can be performed in parallel on this device, if the cluster option <literal>concurrent-fencing</literal> is <literal>true</literal>. -1 is unlimited. <emphasis>(since 1.1.15)</emphasis>"
+msgid "The maximum number of actions that can be performed in parallel on this device, if the cluster option <literal>concurrent-fencing</literal> is <literal>true</literal>. -1 is unlimited."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>pcmk_action_limit</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_action_limit</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_action_limit</secondary> </indexterm> <indexterm> <primary>pcmk_action_limit</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_host_argument</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "port"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Which parameter should be supplied to the resource agent to identify the node to be fenced. Some devices do not support the standard <literal>port</literal> parameter or may provide additional ones. Use this to specify an alternate, device-specific parameter. A value of <literal>none</literal> tells the cluster not to supply any additional parameters. <indexterm> <primary>pcmk_host_argument</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_host_argument</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_host_argument</secondary> </indexterm> <indexterm> <primary>pcmk_host_argument</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_reboot_action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "reboot"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The command to send to the resource agent in order to reboot a node. Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific command. <indexterm> <primary>pcmk_reboot_action</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_reboot_action</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_reboot_action</secondary> </indexterm> <indexterm> <primary>pcmk_reboot_action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_reboot_timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "60s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Specify an alternate timeout to use for <literal>reboot</literal> actions instead of the value of <literal>stonith-timeout</literal>. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. <indexterm> <primary>pcmk_reboot_timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_reboot_timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_reboot_timeout</secondary> </indexterm> <indexterm> <primary>pcmk_reboot_timeout</primary> </indexterm> <indexterm> <primary>stonith-timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>stonith-timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>stonith-timeout</secondary> </indexterm> <indexterm> <primary>stonith-timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_reboot_retries</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The maximum number of times to retry the <literal>reboot</literal> command within the timeout period. Some devices do not support multiple connections, and operations may fail if the device is busy with another task, so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries before giving up. <indexterm> <primary>pcmk_reboot_retries</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_reboot_retries</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_reboot_retries</secondary> </indexterm> <indexterm> <primary>pcmk_reboot_retries</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_off_action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "off"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The command to send to the resource agent in order to shut down a node. Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific command. <indexterm> <primary>pcmk_off_action</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_off_action</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_off_action</secondary> </indexterm> <indexterm> <primary>pcmk_off_action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_off_timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Specify an alternate timeout to use for <literal>off</literal> actions instead of the value of <literal>stonith-timeout</literal>. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. <indexterm> <primary>pcmk_off_timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_off_timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_off_timeout</secondary> </indexterm> <indexterm> <primary>pcmk_off_timeout</primary> </indexterm> <indexterm> <primary>stonith-timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>stonith-timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>stonith-timeout</secondary> </indexterm> <indexterm> <primary>stonith-timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_off_retries</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The maximum number of times to retry the <literal>off</literal> command within the timeout period. Some devices do not support multiple connections, and operations may fail if the device is busy with another task, so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries before giving up. <indexterm> <primary>pcmk_off_retries</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_off_retries</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_off_retries</secondary> </indexterm> <indexterm> <primary>pcmk_off_retries</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_list_action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "list"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The command to send to the resource agent in order to list nodes. Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific command. <indexterm> <primary>pcmk_list_action</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_list_action</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_list_action</secondary> </indexterm> <indexterm> <primary>pcmk_list_action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_list_timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Specify an alternate timeout to use for <literal>list</literal> actions instead of the value of <literal>stonith-timeout</literal>. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. <indexterm> <primary>pcmk_list_timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_list_timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_list_timeout</secondary> </indexterm> <indexterm> <primary>pcmk_list_timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_list_retries</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The maximum number of times to retry the <literal>list</literal> command within the timeout period. Some devices do not support multiple connections, and operations may fail if the device is busy with another task, so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries before giving up. <indexterm> <primary>pcmk_list_retries</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_list_retries</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_list_retries</secondary> </indexterm> <indexterm> <primary>pcmk_list_retries</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_monitor_action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "monitor"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The command to send to the resource agent in order to report extended status. Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific command. <indexterm> <primary>pcmk_monitor_action</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_monitor_action</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_monitor_action</secondary> </indexterm> <indexterm> <primary>pcmk_monitor_action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_monitor_timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Specify an alternate timeout to use for <literal>monitor</literal> actions instead of the value of <literal>stonith-timeout</literal>. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. <indexterm> <primary>pcmk_monitor_timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_monitor_timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_monitor_timeout</secondary> </indexterm> <indexterm> <primary>pcmk_monitor_timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_monitor_retries</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The maximum number of times to retry the <literal>monitor</literal> command within the timeout period. Some devices do not support multiple connections, and operations may fail if the device is busy with another task, so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries before giving up. <indexterm> <primary>pcmk_monitor_retries</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_monitor_retries</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_monitor_retries</secondary> </indexterm> <indexterm> <primary>pcmk_monitor_retries</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_status_action</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "status"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The command to send to the resource agent in order to report status. Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific command. <indexterm> <primary>pcmk_status_action</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_status_action</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_status_action</secondary> </indexterm> <indexterm> <primary>pcmk_status_action</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_status_timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> Specify an alternate timeout to use for <literal>status</literal> actions instead of the value of <literal>stonith-timeout</literal>. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. <indexterm> <primary>pcmk_status_timeout</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_status_timeout</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_status_timeout</secondary> </indexterm> <indexterm> <primary>pcmk_status_timeout</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>pcmk_status_retries</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Advanced use only.</emphasis> The maximum number of times to retry the <literal>status</literal> command within the timeout period. Some devices do not support multiple connections, and operations may fail if the device is busy with another task, so Pacemaker will automatically retry the operation, if there is time remaining. Use this option to alter the number of times Pacemaker retries before giving up. <indexterm> <primary>pcmk_status_retries</primary><secondary>Fencing</secondary> </indexterm> <indexterm> <primary>Fencing</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>Property</secondary><tertiary>pcmk_status_retries</tertiary> </indexterm> <indexterm> <primary>Property</primary><secondary>pcmk_status_retries</secondary> </indexterm> <indexterm> <primary>pcmk_status_retries</primary> </indexterm>"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Unfencing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most fence devices cut the power to the target. By contrast, fence devices that perform <emphasis>fabric fencing</emphasis> cut off a node’s access to some critical resource, such as a shared disk or a network switch."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "With fabric fencing, it is expected that the cluster will fence the node, and then a system administrator must manually investigate what went wrong, correct any issues found, then reboot (or restart the cluster services on) the node."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once the node reboots and rejoins the cluster, some fabric fencing devices require that an explicit command to restore the node’s access to the critical resource. This capability is called <emphasis>unfencing</emphasis> and is typically implemented as the fence agent’s <literal>on</literal> command."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If any cluster resource has <literal>requires</literal> set to <literal>unfencing</literal>, then that resource will not be probed or started on a node until that node has been unfenced."
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "Configuring STONITH"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Higher-level configuration shells include functionality to simplify the process below, particularly the step for deciding which parameters are required. However since this document deals only with core components, you should refer to the STONITH section of the <ulink url=\"http://www.clusterlabs.org/doc/\">Clusters from Scratch</ulink> guide for those details."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Find the correct driver:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# stonith_admin --list-installed"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Find the required parameters associated with the device (replacing $AGENT_NAME with the name obtained from the previous step):"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# stonith_admin --metadata --agent $AGENT_NAME"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a file called <literal>stonith.xml</literal> containing a primitive resource with a class of <literal>stonith</literal>, a type equal to the agent name obtained earlier, and a parameter for each of the values returned in the previous step."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special <literal>pcmk_host_map</literal> parameter. See <literal>man stonithd</literal> for details."
+msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special <literal>pcmk_host_map</literal> parameter. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the device does not support the <literal>list</literal> command, you may also need to set the special <literal>pcmk_host_list</literal> and/or <literal>pcmk_host_check</literal> parameters. See <literal>man stonithd</literal> for details."
+msgid "If the device does not support the <literal>list</literal> command, you may also need to set the special <literal>pcmk_host_list</literal> and/or <literal>pcmk_host_check</literal> parameters. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the device does not expect the victim to be specified with the <literal>port</literal> parameter, you may also need to set the special <literal>pcmk_host_argument</literal> parameter. See <literal>man stonithd</literal> for details."
+msgid "If the device does not expect the victim to be specified with the <literal>port</literal> parameter, you may also need to set the special <literal>pcmk_host_argument</literal> parameter. See <literal>man pacemaker-fenced</literal> for details."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Upload it into the CIB using cibadmin:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cibadmin -C -o resources --xml-file stonith.xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Set <literal>stonith-enabled</literal> to true:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute -t crm_config -n stonith-enabled -v true"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once the stonith resource is running, you can test it by executing the following (although you might want to stop the cluster on that machine first):"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# stonith_admin --reboot nodename"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example STONITH Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Assume we have an chassis containing four nodes and an IPMI device active on 192.0.2.1. We would choose the <literal>fence_ipmilan</literal> driver, and obtain the following list of parameters:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Obtaining a list of STONITH Parameters"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# stonith_admin --metadata -a fence_ipmilan"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;resource-agent name=\"fence_ipmilan\" shortdesc=\"Fence agent for IPMI over LAN\"&gt;\n"
" &lt;symlink name=\"fence_ilo3\" shortdesc=\"Fence agent for HP iLO3\"/&gt;\n"
" &lt;symlink name=\"fence_ilo4\" shortdesc=\"Fence agent for HP iLO4\"/&gt;\n"
" &lt;symlink name=\"fence_idrac\" shortdesc=\"Fence agent for Dell iDRAC\"/&gt;\n"
" &lt;symlink name=\"fence_imm\" shortdesc=\"Fence agent for IBM Integrated Management Module\"/&gt;\n"
" &lt;longdesc&gt;\n"
" &lt;/longdesc&gt;\n"
" &lt;vendor-url&gt;\n"
" &lt;/vendor-url&gt;\n"
" &lt;parameters&gt;\n"
" &lt;parameter name=\"auth\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-A\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"ipaddr\" unique=\"0\" required=\"1\"&gt;\n"
" &lt;getopt mixed=\"-a\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"passwd\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-p\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"passwd_script\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-S\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"lanplus\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-P\"/&gt;\n"
" &lt;content type=\"boolean\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"login\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-l\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"action\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-o\"/&gt;\n"
" &lt;content type=\"string\" default=\"reboot\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"timeout\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-t\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"cipher\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-C\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"method\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-M\"/&gt;\n"
" &lt;content type=\"string\" default=\"onoff\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"power_wait\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-T\"/&gt;\n"
" &lt;content type=\"string\" default=\"2\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"delay\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-f\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"privlvl\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-L\"/&gt;\n"
" &lt;content type=\"string\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;parameter name=\"verbose\" unique=\"0\" required=\"0\"&gt;\n"
" &lt;getopt mixed=\"-v\"/&gt;\n"
" &lt;content type=\"boolean\"/&gt;\n"
" &lt;shortdesc&gt;\n"
" &lt;/shortdesc&gt;\n"
" &lt;/parameter&gt;\n"
" &lt;/parameters&gt;\n"
" &lt;actions&gt;\n"
" &lt;action name=\"on\"/&gt;\n"
" &lt;action name=\"off\"/&gt;\n"
" &lt;action name=\"reboot\"/&gt;\n"
" &lt;action name=\"status\"/&gt;\n"
" &lt;action name=\"diag\"/&gt;\n"
" &lt;action name=\"list\"/&gt;\n"
" &lt;action name=\"monitor\"/&gt;\n"
" &lt;action name=\"metadata\"/&gt;\n"
" &lt;action name=\"stop\" timeout=\"20s\"/&gt;\n"
" &lt;action name=\"start\" timeout=\"20s\"/&gt;\n"
" &lt;/actions&gt;\n"
"&lt;/resource-agent&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Based on that, we would create a STONITH resource fragment that might look like this:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "An IPMI-based STONITH Resource"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"Fencing\" class=\"stonith\" type=\"fence_ipmilan\" &gt;\n"
" &lt;instance_attributes id=\"Fencing-params\" &gt;\n"
" &lt;nvpair id=\"Fencing-passwd\" name=\"passwd\" value=\"testuser\" /&gt;\n"
" &lt;nvpair id=\"Fencing-login\" name=\"login\" value=\"abc123\" /&gt;\n"
" &lt;nvpair id=\"Fencing-ipaddr\" name=\"ipaddr\" value=\"192.0.2.1\" /&gt;\n"
" &lt;nvpair id=\"Fencing-pcmk_host_list\" name=\"pcmk_host_list\" value=\"pcmk-1 pcmk-2\" /&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations &gt;\n"
" &lt;op id=\"Fencing-monitor-10m\" interval=\"10m\" name=\"monitor\" timeout=\"300s\" /&gt;\n"
" &lt;/operations&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Finally, we need to enable STONITH:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Advanced STONITH Configurations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some people consider that having one fencing device is a single point of failure <footnote><para>Not true, since a node or resource must fail before fencing even has a chance to</para></footnote>; others prefer removing the node from the storage and network instead of turning it off."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Whatever the reason, Pacemaker supports fencing nodes with multiple devices through a feature called <emphasis>fencing topologies</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Simply create the individual devices as you normally would, then define one or more <literal>fencing-level</literal> entries in the <literal>fencing-topology</literal> section of the configuration."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Each fencing level is attempted in order of ascending <literal>index</literal>. Allowed values are 1 through 9."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If a device fails, processing terminates for the current level. No further devices in that level are exercised, and the next level is attempted instead."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the operation succeeds for all the listed devices in a level, the level is deemed to have passed."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The operation is finished when a level has passed (success), or all levels have been attempted (failed)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If the operation failed, the next step is determined by the Policy Engine and/or <literal>crmd</literal>."
+msgid "If the operation failed, the next step is determined by the scheduler and/or the controller."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Some possible uses of topologies include:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Try poison-pill and fail back to power"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Try disk and network, and fall back to power if either fails"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Initiate a kdump and then poweroff the node"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of Fencing Levels"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the level <indexterm> <primary>id</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The name of a single node to which this level applies <indexterm> <primary>target</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target</secondary> </indexterm> <indexterm> <primary>target</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target-pattern</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A regular expression matching the names of nodes to which this level applies <emphasis>(since 1.1.14)</emphasis> <indexterm> <primary>target-pattern</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target-pattern</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target-pattern</secondary> </indexterm> <indexterm> <primary>target-pattern</primary> </indexterm>"
+msgid "An extended regular expression (as defined in <ulink url=\"http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04\">POSIX</ulink>) matching the names of nodes to which this level applies <indexterm> <primary>target-pattern</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target-pattern</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target-pattern</secondary> </indexterm> <indexterm> <primary>target-pattern</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target-attribute</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The name of a node attribute that is set (to <literal>target-value</literal>) for nodes to which this level applies <emphasis>(since 1.1.14)</emphasis> <indexterm> <primary>target-attribute</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target-attribute</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target-attribute</secondary> </indexterm> <indexterm> <primary>target-attribute</primary> </indexterm>"
+msgid "The name of a node attribute that is set (to <literal>target-value</literal>) for nodes to which this level applies <indexterm> <primary>target-attribute</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target-attribute</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target-attribute</secondary> </indexterm> <indexterm> <primary>target-attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>target-value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The node attribute value (of <literal>target-attribute</literal>) that is set for nodes to which this level applies <emphasis>(since 1.1.14)</emphasis> <indexterm> <primary>target-attribute</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target-attribute</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target-attribute</secondary> </indexterm> <indexterm> <primary>target-attribute</primary> </indexterm>"
+msgid "The node attribute value (of <literal>target-attribute</literal>) that is set for nodes to which this level applies <indexterm> <primary>target-attribute</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>target-attribute</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>target-attribute</secondary> </indexterm> <indexterm> <primary>target-attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>index</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The order in which to attempt the levels. Levels are attempted in ascending order <emphasis>until one succeeds</emphasis>. Valid values are 1 through 9. <indexterm> <primary>index</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>index</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>index</secondary> </indexterm> <indexterm> <primary>index</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>devices</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A comma-separated list of devices that must all be tried for this level <indexterm> <primary>devices</primary><secondary>fencing-level</secondary> </indexterm> <indexterm> <primary>fencing-level</primary> </indexterm> <indexterm> <primary>Fencing</primary><secondary>fencing-level</secondary><tertiary>devices</tertiary> </indexterm> <indexterm> <primary>fencing-level</primary><secondary>devices</secondary> </indexterm> <indexterm> <primary>devices</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Fencing topology with different devices for different nodes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid " &lt;cib crm_feature_set=\"3.0.6\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\"&gt;\n"
" &lt;configuration&gt;\n"
" ...\n"
" &lt;fencing-topology&gt;\n"
" &lt;!-- For pcmk-1, try poison-pill and fail back to power --&gt;\n"
" &lt;fencing-level id=\"f-p1.1\" target=\"pcmk-1\" index=\"1\" devices=\"poison-pill\"/&gt;\n"
" &lt;fencing-level id=\"f-p1.2\" target=\"pcmk-1\" index=\"2\" devices=\"power\"/&gt;\n"
"\n"
" &lt;!-- For pcmk-2, try disk and network, and fail back to power --&gt;\n"
" &lt;fencing-level id=\"f-p2.1\" target=\"pcmk-2\" index=\"1\" devices=\"disk,network\"/&gt;\n"
" &lt;fencing-level id=\"f-p2.2\" target=\"pcmk-2\" index=\"2\" devices=\"power\"/&gt;\n"
" &lt;/fencing-topology&gt;\n"
" ...\n"
" &lt;configuration&gt;\n"
" &lt;status/&gt;\n"
"&lt;/cib&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example Dual-Layer, Dual-Device Fencing Topologies"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The following example illustrates an advanced use of <literal>fencing-topology</literal> in a cluster with the following properties:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "3 nodes (2 active prod-mysql nodes, 1 prod_mysql-rep in standby for quorum purposes)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "the active nodes have an IPMI-controlled power board reached at 192.0.2.1 and 192.0.2.2"
msgstr ""
#. Tag: para
#, no-c-format
msgid "the active nodes also have two independent PSUs (Power Supply Units) connected to two independent PDUs (Power Distribution Units) reached at 198.51.100.1 (port 10 and port 11) and 203.0.113.1 (port 10 and port 11)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "the first fencing method uses the <literal>fence_ipmi</literal> agent"
msgstr ""
#. Tag: para
#, no-c-format
msgid "the second fencing method uses the <literal>fence_apc_snmp</literal> agent targetting 2 fencing devices (one per PSU, either port 10 or 11)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "fencing is only implemented for the active nodes and has location constraints"
msgstr ""
#. Tag: para
#, no-c-format
msgid "fencing topology is set to try IPMI fencing first then default to a \"sure-kill\" dual PDU fencing"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In a normal failure scenario, STONITH will first select <literal>fence_ipmi</literal> to try to kill the faulty node. Using a fencing topology, if that first method fails, STONITH will then move on to selecting <literal>fence_apc_snmp</literal> twice:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "once for the first PDU"
msgstr ""
#. Tag: para
#, no-c-format
msgid "again for the second PDU"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The fence action is considered successful only if both PDUs report the required status. If any of them fails, STONITH loops back to the first fencing method, <literal>fence_ipmi</literal>, and so on until the node is fenced or fencing action is cancelled."
msgstr ""
#. Tag: title
#, no-c-format
msgid "First fencing method: single IPMI device"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Each cluster node has it own dedicated IPMI channel that can be called for fencing using the following primitives:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive class=\"stonith\" id=\"fence_prod-mysql1_ipmi\" type=\"fence_ipmilan\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql1_ipmi-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive class=\"stonith\" id=\"fence_prod-mysql2_ipmi\" type=\"fence_ipmilan\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql2_ipmi-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.2\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Second fencing method: dual PDU devices"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Each cluster node also has two distinct power channels controlled by two distinct PDUs. That means a total of 4 fencing devices configured as follows:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node 1, PDU 1, PSU 1 @ port 10"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node 1, PDU 2, PSU 2 @ port 10"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node 2, PDU 1, PSU 1 @ port 11"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node 2, PDU 2, PSU 2 @ port 11"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The matching fencing agents are configured as follows:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive class=\"stonith\" id=\"fence_prod-mysql1_apc1\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql1_apc1-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-port\" name=\"port\" value=\"10\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive class=\"stonith\" id=\"fence_prod-mysql1_apc2\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql1_apc2-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-port\" name=\"port\" value=\"10\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive class=\"stonith\" id=\"fence_prod-mysql2_apc1\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql2_apc1-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-port\" name=\"port\" value=\"11\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive class=\"stonith\" id=\"fence_prod-mysql2_apc2\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql2_apc2-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-port\" name=\"port\" value=\"11\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Location Constraints"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To prevent STONITH from trying to run a fencing agent on the same node it is supposed to fence, constraints are placed on all the fencing primitives:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;constraints&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql1_ipmi\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_ipmi\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql2_ipmi\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_ipmi\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql1_apc2\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc2\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql1_apc1\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc1\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql2_apc1\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc1\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql2_apc2\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc2\" score=\"-INFINITY\"/&gt;\n"
"&lt;/constraints&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Fencing topology"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now that all the fencing resources are defined, it’s time to create the right topology. We want to first fence using IPMI and if that does not work, fence both PDUs to effectively and surely kill the node."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;fencing-topology&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql1_ipmi\" id=\"fencing-2\" index=\"1\" target=\"prod-mysql1\"/&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql1_apc1,fence_prod-mysql1_apc2\" id=\"fencing-3\" index=\"2\" target=\"prod-mysql1\"/&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql2_ipmi\" id=\"fencing-0\" index=\"1\" target=\"prod-mysql2\"/&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql2_apc1,fence_prod-mysql2_apc2\" id=\"fencing-1\" index=\"2\" target=\"prod-mysql2\"/&gt;\n"
"&lt;/fencing-topology&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Please note, in <literal>fencing-topology</literal>, the lowest <literal>index</literal> value determines the priority of the first fencing method."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Final configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Put together, the configuration looks like this:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;cib admin_epoch=\"0\" crm_feature_set=\"3.0.7\" epoch=\"292\" have-quorum=\"1\" num_updates=\"29\" validate-with=\"pacemaker-1.2\"&gt;\n"
" &lt;configuration&gt;\n"
" &lt;crm_config&gt;\n"
" &lt;cluster_property_set id=\"cib-bootstrap-options\"&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-stonith-action\" name=\"stonith-action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"cib-bootstrap-options-expected-quorum-votes\" name=\"expected-quorum-votes\" value=\"3\"/&gt;\n"
" ...\n"
" &lt;/cluster_property_set&gt;\n"
" &lt;/crm_config&gt;\n"
" &lt;nodes&gt;\n"
" &lt;node id=\"prod-mysql1\" uname=\"prod-mysql1\"&gt;\n"
" &lt;node id=\"prod-mysql2\" uname=\"prod-mysql2\"/&gt;\n"
" &lt;node id=\"prod-mysql-rep1\" uname=\"prod-mysql-rep1\"/&gt;\n"
" &lt;instance_attributes id=\"prod-mysql-rep1\"&gt;\n"
" &lt;nvpair id=\"prod-mysql-rep1-standby\" name=\"standby\" value=\"on\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/node&gt;\n"
" &lt;/nodes&gt;\n"
" &lt;resources&gt;\n"
" &lt;primitive class=\"stonith\" id=\"fence_prod-mysql1_ipmi\" type=\"fence_ipmilan\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql1_ipmi-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive class=\"stonith\" id=\"fence_prod-mysql2_ipmi\" type=\"fence_ipmilan\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql2_ipmi-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.2\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive class=\"stonith\" id=\"fence_prod-mysql1_apc1\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql1_apc1-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-port\" name=\"port\" value=\"10\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive class=\"stonith\" id=\"fence_prod-mysql1_apc2\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql1_apc2-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-port\" name=\"port\" value=\"10\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive class=\"stonith\" id=\"fence_prod-mysql2_apc1\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql2_apc1-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-port\" name=\"port\" value=\"11\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;primitive class=\"stonith\" id=\"fence_prod-mysql2_apc2\" type=\"fence_apc_snmp\"&gt;\n"
" &lt;instance_attributes id=\"fence_prod-mysql2_apc2-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-port\" name=\"port\" value=\"11\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/&gt;\n"
" &lt;nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;/primitive&gt;\n"
" &lt;/resources&gt;\n"
" &lt;constraints&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql1_ipmi\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_ipmi\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql2_ipmi\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_ipmi\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql1_apc2\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc2\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql1_apc1\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc1\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql2_apc1\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc1\" score=\"-INFINITY\"/&gt;\n"
" &lt;rsc_location id=\"l_fence_prod-mysql2_apc2\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc2\" score=\"-INFINITY\"/&gt;\n"
" &lt;/constraints&gt;\n"
" &lt;fencing-topology&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql1_ipmi\" id=\"fencing-2\" index=\"1\" target=\"prod-mysql1\"/&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql1_apc1,fence_prod-mysql1_apc2\" id=\"fencing-3\" index=\"2\" target=\"prod-mysql1\"/&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql2_ipmi\" id=\"fencing-0\" index=\"1\" target=\"prod-mysql2\"/&gt;\n"
" &lt;fencing-level devices=\"fence_prod-mysql2_apc1,fence_prod-mysql2_apc2\" id=\"fencing-1\" index=\"2\" target=\"prod-mysql2\"/&gt;\n"
" &lt;/fencing-topology&gt;\n"
" ...\n"
" &lt;/configuration&gt;\n"
"&lt;/cib&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Remapping Reboots"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When the cluster needs to reboot a node, whether because <literal>stonith-action</literal> is <literal>reboot</literal> or because a reboot was manually requested (such as by <literal>stonith_admin --reboot</literal>), it will remap that to other commands in two cases:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the chosen fencing device does not support the <literal>reboot</literal> command, the cluster will ask it to perform <literal>off</literal> instead."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If a fencing topology level with multiple devices must be executed, the cluster will ask all the devices to perform <literal>off</literal>, then ask the devices to perform <literal>on</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To understand the second case, consider the example of a node with redundant power supplies connected to intelligent power switches. Rebooting one switch and then the other would have no effect on the node. Turning both switches off, and then on, actually reboots the node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In such a case, the fencing operation will be treated as successful as long as the <literal>off</literal> commands succeed, because then it is safe for the cluster to recover any resources that were on the node. Timeouts and errors in the <literal>on</literal> phase will be logged but ignored."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When a reboot operation is remapped, any action-specific timeout for the remapped action will be used (for example, <literal>pcmk_off_timeout</literal> will be used when executing the <literal>off</literal> command, not <literal>pcmk_reboot_timeout</literal>)."
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "In Pacemaker versions 1.1.13 and earlier, reboots will not be remapped in the second case. To achieve the same effect, separate fencing devices for off and on actions must be configured."
-msgstr ""
-
diff --git a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot
index 944ada7d9d..ef86bbccf4 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot
@@ -1,362 +1,362 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Utilization and Placement Strategy"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker decides where to place a resource according to the resource allocation scores on every node. The resource will be allocated to the node where the resource has the highest score."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the resource allocation scores on all the nodes are equal, by the default placement strategy, Pacemaker will choose a node with the least number of allocated resources for balancing the load. If the number of resources on each node is equal, the first eligible node listed in the CIB will be chosen to run the resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Often, in real-world situations, different resources use significantly different proportions of a node’s capacities (memory, I/O, etc.). We cannot balance the load ideally just according to the number of resources allocated to a node. Besides, if resources are placed such that their combined requirements exceed the provided capacity, they may fail to start completely or run with degraded performance."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To take these factors into account, Pacemaker allows you to configure:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The capacity a certain node provides."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The capacity a certain resource requires."
msgstr ""
#. Tag: para
#, no-c-format
msgid "An overall strategy for placement of resources."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Utilization attributes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "To configure the capacity that a node provides or a resource requires, you can use <emphasis>utilization attributes</emphasis> in <literal>node</literal> and <literal>resource</literal> objects. You can name utilization attributes according to your preferences and define as many name/value pairs as your configuration needs. However, the attributes' values must be integers."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Specifying CPU and RAM capacities of two nodes"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;node id=\"node1\" type=\"normal\" uname=\"node1\"&gt;\n"
" &lt;utilization id=\"node1-utilization\"&gt;\n"
" &lt;nvpair id=\"node1-utilization-cpu\" name=\"cpu\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"node1-utilization-memory\" name=\"memory\" value=\"2048\"/&gt;\n"
" &lt;/utilization&gt;\n"
"&lt;/node&gt;\n"
"&lt;node id=\"node2\" type=\"normal\" uname=\"node2\"&gt;\n"
" &lt;utilization id=\"node2-utilization\"&gt;\n"
" &lt;nvpair id=\"node2-utilization-cpu\" name=\"cpu\" value=\"4\"/&gt;\n"
" &lt;nvpair id=\"node2-utilization-memory\" name=\"memory\" value=\"4096\"/&gt;\n"
" &lt;/utilization&gt;\n"
"&lt;/node&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Specifying CPU and RAM consumed by several resources"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "&lt;primitive id=\"rsc-small\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\"&gt;\n"
" &lt;utilization id=\"rsc-small-utilization\"&gt;\n"
" &lt;nvpair id=\"rsc-small-utilization-cpu\" name=\"cpu\" value=\"1\"/&gt;\n"
" &lt;nvpair id=\"rsc-small-utilization-memory\" name=\"memory\" value=\"1024\"/&gt;\n"
" &lt;/utilization&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive id=\"rsc-medium\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\"&gt;\n"
" &lt;utilization id=\"rsc-medium-utilization\"&gt;\n"
" &lt;nvpair id=\"rsc-medium-utilization-cpu\" name=\"cpu\" value=\"2\"/&gt;\n"
" &lt;nvpair id=\"rsc-medium-utilization-memory\" name=\"memory\" value=\"2048\"/&gt;\n"
" &lt;/utilization&gt;\n"
"&lt;/primitive&gt;\n"
"&lt;primitive id=\"rsc-large\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\"&gt;\n"
" &lt;utilization id=\"rsc-large-utilization\"&gt;\n"
" &lt;nvpair id=\"rsc-large-utilization-cpu\" name=\"cpu\" value=\"3\"/&gt;\n"
" &lt;nvpair id=\"rsc-large-utilization-memory\" name=\"memory\" value=\"3072\"/&gt;\n"
" &lt;/utilization&gt;\n"
"&lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A node is considered eligible for a resource if it has sufficient free capacity to satisfy the resource’s requirements. The nature of the required or provided capacities is completely irrelevant to Pacemaker — it just makes sure that all capacity requirements of a resource are satisfied before placing a resource to a node."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Placement Strategy"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After you have configured the capacities your nodes provide and the capacities your resources require, you need to set the <literal>placement-strategy</literal> in the global cluster options, otherwise the capacity configurations have <emphasis>no effect</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Four values are available for the <literal>placement-strategy</literal>:"
msgstr ""
#. Tag: term
#, no-c-format
msgid "<literal>default</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Utilization values are not taken into account at all. Resources are allocated according to allocation scores. If scores are equal, resources are evenly distributed across nodes."
msgstr ""
#. Tag: term
#, no-c-format
msgid "<literal>utilization</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Utilization values are taken into account <emphasis>only</emphasis> when deciding whether a node is considered eligible (i.e. whether it has sufficient free capacity to satisfy the resource’s requirements). Load-balancing is still done based on the number of resources allocated to a node."
msgstr ""
#. Tag: term
#, no-c-format
msgid "<literal>balanced</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Utilization values are taken into account when deciding whether a node is eligible to serve a resource <emphasis>and</emphasis> when load-balancing, so an attempt is made to spread the resources in a way that optimizes resource performance."
msgstr ""
#. Tag: term
#, no-c-format
msgid "<literal>minimal</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Utilization values are taken into account <emphasis>only</emphasis> when deciding whether a node is eligible to serve a resource. For load-balancing, an attempt is made to concentrate the resources on as few nodes as possible, thereby enabling possible power savings on the remaining nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Set <literal>placement-strategy</literal> with <literal>crm_attribute</literal>:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_attribute --name placement-strategy --update balanced"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now Pacemaker will ensure the load from your resources will be distributed evenly throughout the cluster, without the need for convoluted sets of colocation constraints."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Allocation Details"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Which node is preferred to get consumed first when allocating resources?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The node with the highest node weight gets consumed first. Node weight is a score maintained by the cluster to represent node health."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If multiple nodes have the same node weight:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>placement-strategy</literal> is <literal>default</literal> or <literal>utilization</literal>, the node that has the least number of allocated resources gets consumed first."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If their numbers of allocated resources are equal, the first eligible node listed in the CIB gets consumed first."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>placement-strategy</literal> is <literal>balanced</literal>, the node that has the most free capacity gets consumed first."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the free capacities of the nodes are equal, the node that has the least number of allocated resources gets consumed first."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>placement-strategy</literal> is <literal>minimal</literal>, the first eligible node listed in the CIB gets consumed first."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Which node has more free capacity?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If only one type of utilization attribute has been defined, free capacity is a simple numeric comparison."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If multiple types of utilization attributes have been defined, then the node that is numerically highest in the the most attribute types has the most free capacity. For example:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>nodeA</literal> has more free <literal>cpus</literal>, and <literal>nodeB</literal> has more free <literal>memory</literal>, then their free capacities are equal."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If <literal>nodeA</literal> has more free <literal>cpus</literal>, while <literal>nodeB</literal> has more free <literal>memory</literal> and <literal>storage</literal>, then <literal>nodeB</literal> has more free capacity."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Which resource is preferred to be assigned first?"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The resource that has the highest <literal>priority</literal> (see <xref linkend=\"s-resource-options\" />) gets allocated first."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If their priorities are equal, check whether they are already running. The resource that has the highest score on the node where it’s running gets allocated first, to prevent resource shuffling."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the scores above are equal or the resources are not running, the resource has the highest score on the preferred node gets allocated first."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the scores above are equal, the first runnable resource listed in the CIB gets allocated first."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Limitations and Workarounds"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The type of problem Pacemaker is dealing with here is known as the <ulink url=\"http://en.wikipedia.org/wiki/Knapsack_problem\">knapsack problem</ulink> and falls into the <ulink url=\"http://en.wikipedia.org/wiki/NP-complete\">NP-complete</ulink> category of computer science problems — a fancy way of saying \"it takes a really long time to solve\"."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Clearly in a HA cluster, it’s not acceptable to spend minutes, let alone hours or days, finding an optimal solution while services remain unavailable."
msgstr ""
#. Tag: para
#, no-c-format
msgid "So instead of trying to solve the problem completely, Pacemaker uses a <emphasis>best effort</emphasis> algorithm for determining which node should host a particular service. This means it arrives at a solution much faster than traditional linear programming algorithms, but by doing so at the price of leaving some services stopped."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the contrived example at the start of this section:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc-small</literal> would be allocated to <literal>node1</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc-medium</literal> would be allocated to <literal>node2</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>rsc-large</literal> would remain inactive"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Which is not ideal."
msgstr ""
#. Tag: para
#, no-c-format
msgid "There are various approaches to dealing with the limitations of pacemaker’s placement strategy:"
msgstr ""
#. Tag: term
#, no-c-format
msgid "Ensure you have sufficient physical capacity."
msgstr ""
#. Tag: para
#, no-c-format
msgid "It might sound obvious, but if the physical capacity of your nodes is (close to) maxed out by the cluster under normal conditions, then failover isn’t going to go well. Even without the utilization feature, you’ll start hitting timeouts and getting secondary failures."
msgstr ""
#. Tag: term
#, no-c-format
msgid "Build some buffer into the capabilities advertised by the nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Advertise slightly more resources than we physically have, on the (usually valid) assumption that a resource will not use 100% of the configured amount of CPU, memory and so forth <emphasis>all</emphasis> the time. This practice is sometimes called <emphasis>overcommit</emphasis>."
msgstr ""
#. Tag: term
#, no-c-format
msgid "Specify resource priorities."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the cluster is going to sacrifice services, it should be the ones you care about (comparatively) the least. Ensure that resource priorities are properly set so that your most important resources are scheduled first."
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot
index 83087da995..f1cb2c996e 100644
--- a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot
+++ b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot
@@ -1,44 +1,39 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Further Reading"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Project Website: <ulink url=\"http://www.clusterlabs.org/\" />"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Project Documentation: <ulink url=\"http://www.clusterlabs.org/wiki/Documentation\" />"
msgstr ""
#. Tag: para
#, no-c-format
msgid "SUSE High Availibility Guide: <ulink url=\"http://www.suse.com/documentation/sle_ha/book_sleha/data/book_sleha.html\" />"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "Heartbeat configuration: <ulink url=\"http://www.linux-ha.org/\" />"
-msgstr ""
-
#. Tag: para
#, no-c-format
msgid "Corosync Configuration: <ulink url=\"http://www.corosync.org/\" />"
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Preface.pot b/doc/Pacemaker_Explained/pot/Preface.pot
index f84c72b747..44e91d0ec7 100644
--- a/doc/Pacemaker_Explained/pot/Preface.pot
+++ b/doc/Pacemaker_Explained/pot/Preface.pot
@@ -1,19 +1,19 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Preface"
msgstr ""
diff --git a/doc/Pacemaker_Explained/pot/Revision_History.pot b/doc/Pacemaker_Explained/pot/Revision_History.pot
index 56bf074103..241cd3f4a7 100644
--- a/doc/Pacemaker_Explained/pot/Revision_History.pot
+++ b/doc/Pacemaker_Explained/pot/Revision_History.pot
@@ -1,99 +1,104 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Revision History"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Andrew"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Beekhof"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Import from Pages.app"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Cleanup and reformatting of docbook xml complete"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Split book into chapters and pass validation"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Re-organize book for use with <ulink url=\"https://fedorahosted.org/publican/\">Publican</ulink>"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Converted to <ulink url=\"http://www.methods.co.nz/asciidoc\">asciidoc</ulink> (which is converted to docbook for use with <ulink url=\"https://fedorahosted.org/publican/\">Publican</ulink>)"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for clarity, stylistic consistency and current command-line syntax"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for Pacemaker 1.1.14"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for Pacemaker 1.1.15"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Overhaul upgrade documentation, and document node health strategies"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for Pacemaker 1.1.16"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for Pacemaker 1.1.17"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Update for Pacemaker 1.1.18"
msgstr ""
+#. Tag: member
+#, no-c-format
+msgid "Update for Pacemaker 2.0.0"
+msgstr ""
+
diff --git a/doc/Pacemaker_Remote/pot/Author_Group.pot b/doc/Pacemaker_Remote/pot/Author_Group.pot
index a6f1fbd132..73148d0dc5 100644
--- a/doc/Pacemaker_Remote/pot/Author_Group.pot
+++ b/doc/Pacemaker_Remote/pot/Author_Group.pot
@@ -1,34 +1,34 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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: firstname
#, no-c-format
msgid "David"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Vossel"
msgstr ""
#. Tag: orgname
#, no-c-format
msgid "Red Hat"
msgstr ""
#. Tag: contrib
#, no-c-format
msgid "Primary author"
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Book_Info.pot b/doc/Pacemaker_Remote/pot/Book_Info.pot
index fd3dd34d84..b6762b3074 100644
--- a/doc/Pacemaker_Remote/pot/Book_Info.pot
+++ b/doc/Pacemaker_Remote/pot/Book_Info.pot
@@ -1,74 +1,74 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Pacemaker Remote"
msgstr ""
#. Tag: subtitle
#, no-c-format
msgid "Scaling High Availablity Clusters"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The document exists as both a reference and deployment guide for the Pacemaker Remote service."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The example commands in this document will use:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "&DISTRO; &DISTRO_VERSION; as the host operating system"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker Remote to perform resource management within guest nodes and remote nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "KVM for virtualization"
msgstr ""
#. Tag: para
#, no-c-format
msgid "libvirt to manage guest nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Corosync to provide messaging and membership services on cluster nodes"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker to perform resource management on cluster nodes"
+msgid "Pacemaker 1.1.16 <footnote><para>While this guide is part of the document set for Pacemaker 2.0, it demonstrates the version available in the standard &DISTRO; repositories</para></footnote> to perform resource management on cluster nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "pcs as the cluster configuration toolset"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The concepts are the same for other distributions, virtualization platforms, toolsets, and messaging layers, and should be easily adaptable."
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot
index d0f9587009..cf05711beb 100644
--- a/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot
+++ b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot
@@ -1,109 +1,109 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Alternative Configurations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "These alternative configurations may be appropriate in limited cases, such as a test cluster, but are not the best method in most situations. They are presented here for completeness and as an example of Pacemaker’s flexibility to suit your needs."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Virtual Machines as Cluster Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The preferred use of virtual machines in a Pacemaker cluster is as a cluster resource, whether opaque or as a guest node. However, it is possible to run the full cluster stack on a virtual node instead."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This is commonly used to set up test environments; a single physical host (that does not participate in the cluster) runs two or more virtual machines, all running the full cluster stack. This can be used to simulate a larger cluster for testing purposes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In a production environment, fencing becomes more complicated, especially if the underlying hosts run any services besides the clustered VMs. If the VMs are not guaranteed a minimum amount of host resources, CPU and I/O contention can cause timing issues for cluster components."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another situation where this approach is sometimes used is when the cluster owner leases the VMs from a provider and does not have direct access to the underlying host. The main concerns in this case are proper fencing (usually via a custom resource agent that communicates with the provider’s APIs) and maintaining a static IP address between reboots, as well as resource contention issues."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Virtual Machines as Remote Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Virtual machines may be configured following the process for remote nodes rather than guest nodes (i.e., using an <emphasis role=\"strong\">ocf:pacemaker:remote</emphasis> resource rather than letting the cluster manage the VM directly)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This is mainly useful in testing, to use a single physical host to simulate a larger cluster involving remote nodes. Pacemaker’s Cluster Test Suite (CTS) uses this approach to test remote node functionality."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Containers as Guest Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Containers,<footnote><para><ulink url=\"https://en.wikipedia.org/wiki/Operating-system-level_virtualization\">https://en.wikipedia.org/wiki/Operating-system-level_virtualization</ulink></para></footnote> and in particular Linux containers (LXC) and Docker, have become a popular method of isolating services in a resource-efficient manner."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The preferred means of integrating containers into Pacemaker is as a cluster resource, whether opaque or using Pacemaker’s <emphasis>bundle</emphasis> resource type."
msgstr ""
#. Tag: para
#, no-c-format
msgid "However, it is possible to run <literal>pacemaker_remote</literal> inside a container, following the process for guest nodes. This is not recommended but can be useful, for example, in testing scenarios, to simulate a large number of guest nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The configuration process is very similar to that described for guest nodes using virtual machines. Key differences:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The underlying host must install the libvirt driver for the desired container technology — for example, the <literal>libvirt-daemon-lxc</literal> package to get the <ulink url=\"http://libvirt.org/drvlxc.html:\">libvirt-lxc</ulink> driver for LXC containers."
+msgid "The underlying host must install the libvirt driver for the desired container technology — for example, the <literal>libvirt-daemon-lxc</literal> package to get the <ulink url=\"http://libvirt.org/drvlxc.html\">libvirt-lxc</ulink> driver for LXC containers."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Libvirt XML definitions must be generated for the containers. The <literal>pacemaker-cts</literal> package includes a script for this purpose, <literal>/usr/share/pacemaker/tests/cts/lxc_autogen.sh</literal>. Run it with the <literal>--help</literal> option for details on how to use it. It is intended for testing purposes only, and hardcodes various parameters that would need to be set appropriately in real usage. Of course, you can create XML definitions manually, following the appropriate libvirt driver documentation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To share the authentication key, either share the host’s <literal>/etc/pacemaker</literal> directory with the container, or copy the key into the container’s filesystem."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The <emphasis role=\"strong\">VirtualDomain</emphasis> resource for a container will need <emphasis role=\"strong\">force_stop=\"true\"</emphasis> and an appropriate hypervisor option, for example <emphasis role=\"strong\">hypervisor=\"lxc:///\"</emphasis> for LXC containers."
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot
index 8d49324bca..fdfcbded28 100644
--- a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot
+++ b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot
@@ -1,458 +1,453 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Remote Node Walk-through"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">What this tutorial is:</emphasis> An in-depth walk-through of how to get Pacemaker to integrate a remote node into the cluster as a node capable of running cluster resources."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">What this tutorial is not:</emphasis> A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of remote nodes as quickly as possible."
msgstr ""
#. Tag: para
#, no-c-format
msgid "This tutorial requires three machines: two to act as cluster nodes, and a third to act as the remote node."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Remote Node"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Firewall on Remote Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "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 "# setenforce 0\n"
"# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n"
"# systemctl mask firewalld.service\n"
"# systemctl stop firewalld.service\n"
"# iptables --flush"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure pacemaker_remote on Remote Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Install the pacemaker_remote daemon on the remote node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y pacemaker-remote resource-agents pcs"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a location for the shared authentication key:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# mkdir -p --mode=0750 /etc/pacemaker\n"
"# chgrp haclient /etc/pacemaker"
msgstr ""
#. Tag: para
#, no-c-format
msgid "All nodes (both cluster nodes and remote nodes) must have the same authentication key installed for the communication to work correctly. If you already have a key on an existing node, copy it to the new remote node. Otherwise, create a new key, for example:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now start and enable the pacemaker_remote daemon on the remote node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# systemctl enable pacemaker_remote.service\n"
"# systemctl start pacemaker_remote.service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify the start is successful."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# systemctl status pacemaker_remote\n"
"pacemaker_remote.service - Pacemaker Remote Service\n"
" Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)\n"
-" Active: active (running) since Fri 2015-08-21 15:21:20 CDT; 20s ago\n"
+" Active: active (running) since Fri 2018-01-12 15:21:20 CDT; 20s ago\n"
" Main PID: 21273 (pacemaker_remot)\n"
" CGroup: /system.slice/pacemaker_remote.service\n"
-" └─21273 /usr/sbin/pacemaker_remoted\n"
+" └─21273 /usr/sbin/pacemaker-remoted\n"
"\n"
-"Aug 21 15:21:20 remote1 systemd[1]: Starting Pacemaker Remote Service...\n"
-"Aug 21 15:21:20 remote1 systemd[1]: Started Pacemaker Remote Service.\n"
-"Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log\n"
-"Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121.\n"
-"Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: bind_and_listen: Listening on address ::"
+"Jan 12 15:21:20 remote1 systemd[1]: Starting Pacemaker Remote Service...\n"
+"Jan 12 15:21:20 remote1 systemd[1]: Started Pacemaker Remote Service.\n"
+"Jan 12 15:21:20 remote1 pacemaker-remoted[21273]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log\n"
+"Jan 12 15:21:20 remote1 pacemaker-remoted[21273]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121.\n"
+"Jan 12 15:21:20 remote1 pacemaker-remoted[21273]: notice: bind_and_listen: Listening on address ::"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Connection to Remote Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before moving forward, it’s worth verifying that the cluster nodes can contact the remote node on port 3121. Here’s a trick you can use. Connect using ssh from each of the cluster nodes. The connection will get destroyed, but how it is destroyed tells you whether it worked or not."
msgstr ""
#. Tag: para
#, no-c-format
msgid "First, add the remote node’s hostname (we’re using <emphasis role=\"strong\">remote1</emphasis> in this tutorial) to the cluster nodes' <literal>/etc/hosts</literal> files if you haven’t already. This is required unless you have DNS set up in a way where remote1’s address can be discovered."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Execute the following on each cluster node, replacing the IP address with the actual IP address of the remote node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cat &lt;&lt; END &gt;&gt; /etc/hosts\n"
"192.168.122.10 remote1\n"
"END"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If running the ssh command on one of the cluster nodes results in this output before disconnecting, the connection works:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# ssh -p 3121 remote1\n"
"ssh_exchange_identification: read: Connection reset by peer"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you see one of these, the connection is not working:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# ssh -p 3121 remote1\n"
"ssh: connect to host remote1 port 3121: No route to host"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# ssh -p 3121 remote1\n"
"ssh: connect to host remote1 port 3121: Connection refused"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once you can successfully connect to the remote node from the both cluster nodes, move on to setting up Pacemaker on the cluster nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Cluster Nodes"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Firewall on Cluster Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On each cluster node, allow cluster-related services through the local firewall, following the same procedure as in <xref linkend=\"_configure_firewall_on_remote_node\" />."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Install Pacemaker on Cluster Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On the two cluster nodes, install the following packages."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y pacemaker corosync pcs resource-agents"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Copy Authentication Key to Cluster Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a location for the shared authentication key, and copy it from any existing node:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# mkdir -p --mode=0750 /etc/pacemaker\n"
"# chgrp haclient /etc/pacemaker\n"
"# scp remote1:/etc/pacemaker/authkey /etc/pacemaker/authkey"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Corosync on Cluster Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Corosync handles Pacemaker’s cluster membership and messaging. The corosync config file is located in <literal>/etc/corosync/corosync.conf</literal>. That config file must be initialized with information about the two cluster nodes before pacemaker can start."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To initialize the corosync config file, execute the following pcs command on both nodes, filling in the information in &lt;&gt; with your nodes' information."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster setup --force --local --name mycluster &lt;node1 ip or hostname&gt; &lt;node2 ip or hostname&gt;"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Start Pacemaker on Cluster Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Start the cluster stack on both cluster nodes using the following command."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster start"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify corosync membership"
msgstr ""
#. Tag: literallayout
#, no-c-format
msgid "# pcs status corosync\n"
"Membership information\n"
"----------------------\n"
" Nodeid Votes Name\n"
" 1 1 node1 (local)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify Pacemaker status. At first, the <literal>pcs cluster status</literal> output will look like this."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 21 16:14:05 2015\n"
-"Last change: Fri Aug 21 14:02:14 2015\n"
"Stack: corosync\n"
"Current DC: NONE\n"
-"Version: 1.1.12-a14efad\n"
-"1 Nodes configured, unknown expected votes\n"
-"0 Resources configured"
+"Last updated: Fri Jan 12 16:14:05 2018\n"
+"Last change: Fri Jan 12 14:02:14 2018\n"
+"\n"
+"1 node configured\n"
+"0 resources configured"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After about a minute, you should see your two cluster nodes come online."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Aug 21 16:16:32 2015\n"
-"Last change: Fri Aug 21 14:02:14 2015\n"
"Stack: corosync\n"
-"Current DC: node1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"2 Nodes configured\n"
-"0 Resources configured\n"
+"Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 16:16:32 2018\n"
+"Last change: Fri Jan 12 14:02:14 2018\n"
+"\n"
+"2 nodes configured\n"
+"0 resources configured\n"
"\n"
"Online: [ node1 node2 ]"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For the sake of this tutorial, we are going to disable stonith to avoid having to cover fencing device configuration."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs property set stonith-enabled=false"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Integrate Remote Node into Cluster"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Integrating a remote node into the cluster is achieved through the creation of a remote node connection resource. The remote node connection resource both establishes the connection to the remote node and defines that the remote node exists. Note that this resource is actually internal to Pacemaker’s crmd component. A metadata file for this resource can be found in the <literal>/usr/lib/ocf/resource.d/pacemaker/remote</literal> file that describes what options are available, but there is no actual <emphasis role=\"strong\">ocf:pacemaker:remote</emphasis> resource agent script that performs any work."
+msgid "Integrating a remote node into the cluster is achieved through the creation of a remote node connection resource. The remote node connection resource both establishes the connection to the remote node and defines that the remote node exists. Note that this resource is actually internal to Pacemaker’s controller. A metadata file for this resource can be found in the <literal>/usr/lib/ocf/resource.d/pacemaker/remote</literal> file that describes what options are available, but there is no actual <emphasis role=\"strong\">ocf:pacemaker:remote</emphasis> resource agent script that performs any work."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Define the remote node connection resource to our remote node, <emphasis role=\"strong\">remote1</emphasis>, using the following command on any cluster node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create remote1 ocf:pacemaker:remote"
msgstr ""
#. Tag: para
#, no-c-format
msgid "That’s it. After a moment you should see the remote node come online."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "Cluster name: mycluster\n"
-"Last updated: Fri Aug 21 17:13:09 2015\n"
-"Last change: Fri Aug 21 17:02:02 2015\n"
"Stack: corosync\n"
-"Current DC: node1 (1) - partition with quorum\n"
-"Version: 1.1.12-a14efad\n"
-"3 Nodes configured\n"
-"1 Resources configured\n"
+"Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 17:13:09 2018\n"
+"Last change: Fri Jan 12 17:02:02 2018\n"
"\n"
+"3 nodes configured\n"
+"1 resources configured\n"
"\n"
"Online: [ node1 node2 ]\n"
"RemoteOnline: [ remote1 ]\n"
"\n"
"Full list of resources:\n"
"\n"
" remote1 (ocf::pacemaker:remote): Started node1\n"
"\n"
-"PCSD Status:\n"
-" node1: Online\n"
-" node2: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Starting Resources on Remote Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once the remote node is integrated into the cluster, starting resources on a remote node is the exact same as on cluster nodes. Refer to the <ulink url=\"http://clusterlabs.org/doc/\"><emphasis>Clusters from Scratch</emphasis></ulink> document for examples of resource creation."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Never involve a remote node connection resource in a resource group, colocation constraint, or order constraint."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Fencing Remote Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Remote nodes are fenced the same way as cluster nodes. No special considerations are required. Configure fencing resources for use with remote nodes the same as you would with cluster nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Note, however, that remote nodes can never <emphasis>initiate</emphasis> a fencing action. Only cluster nodes are capable of actually executing a fencing operation against another node."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Accessing Cluster Tools from a Remote Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Besides allowing the cluster to manage resources on a remote node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (<literal>crm_resource</literal>, <literal>crm_mon</literal>, <literal>crm_attribute</literal>, <literal>crm_master</literal>, etc.) to work on remote nodes natively."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Try it: Run <literal>crm_mon</literal> on the remote node after pacemaker has integrated it into the cluster. These tools just work. These means resource agents such as master/slave resources which need access to tools like <literal>crm_master</literal> work seamlessly on the remote nodes."
+msgid "Try it: Run <literal>crm_mon</literal> on the remote node after pacemaker has integrated it into the cluster. These tools just work. These means resource agents such as promotable resources (which need access to tools like <literal>crm_master</literal>) work seamlessly on the remote nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Higher-level command shells such as <literal>pcs</literal> may have partial support on remote nodes, but it is recommended to run them from a cluster node."
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Ch-Example.pot b/doc/Pacemaker_Remote/pot/Ch-Example.pot
index f27a1eb1c6..bc665c19f0 100644
--- a/doc/Pacemaker_Remote/pot/Ch-Example.pot
+++ b/doc/Pacemaker_Remote/pot/Ch-Example.pot
@@ -1,174 +1,174 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Guest Node Quick Example"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you already know how to use Pacemaker, you’ll likely be able to grasp this new concept of guest nodes by reading through this quick example without having to sort through all the detailed walk-through steps. Here are the key configuration ingredients that make this possible using libvirt and KVM virtual guests. These steps strip everything down to the very basics. <indexterm> <primary>guest node</primary> </indexterm> <indexterm> <primary>node</primary><secondary>guest node</secondary> </indexterm> <indexterm> <primary>guest node</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mile-High View of Configuration Steps"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Give each virtual machine that will be used as a guest node a static network address and unique hostname."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Put the same authentication key with the path <literal>/etc/pacemaker/authkey</literal> on every cluster node and virtual machine. This secures remote communication."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Run this command if you want to make a somewhat random key:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Install pacemaker_remote on every virtual machine, enabling it to start at boot, and if a local firewall is used, allow the node to accept connections on TCP port 3121."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "yum install pacemaker-remote resource-agents\n"
"systemctl enable pacemaker_remote\n"
"firewall-cmd --add-port 3121/tcp --permanent"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you just want to see this work, you may want to simply disable the local firewall and put SELinux in permissive mode while testing. This creates security risks and should not be done on a production machine exposed to the Internet, but can be appropriate for a protected test machine."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a Pacemaker resource to launch each virtual machine, using the <emphasis role=\"strong\">remote-node</emphasis> meta-attribute to let Pacemaker know this will be a guest node capable of running resources."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create vm-guest1 VirtualDomain hypervisor=\"qemu:///system\" config=\"vm-guest1.xml\" meta remote-node=\"guest1\""
msgstr ""
#. Tag: para
#, no-c-format
msgid "The above command will create CIB XML similar to the following:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid " &lt;primitive class=\"ocf\" id=\"vm-guest1\" provider=\"heartbeat\" type=\"VirtualDomain\"&gt;\n"
" &lt;instance_attributes id=\"vm-guest-instance_attributes\"&gt;\n"
" &lt;nvpair id=\"vm-guest1-instance_attributes-hypervisor\" name=\"hypervisor\" value=\"qemu:///system\"/&gt;\n"
" &lt;nvpair id=\"vm-guest1-instance_attributes-config\" name=\"config\" value=\"guest1.xml\"/&gt;\n"
" &lt;/instance_attributes&gt;\n"
" &lt;operations&gt;\n"
" &lt;op id=\"vm-guest1-interval-30s\" interval=\"30s\" name=\"monitor\"/&gt;\n"
" &lt;/operations&gt;\n"
" &lt;meta_attributes id=\"vm-guest1-meta_attributes\"&gt;\n"
" &lt;nvpair id=\"vm-guest1-meta_attributes-remote-node\" name=\"remote-node\" value=\"guest1\"/&gt;\n"
" &lt;/meta_attributes&gt;\n"
" &lt;/primitive&gt;"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example above, the meta-attribute <emphasis role=\"strong\">remote-node=\"guest1\"</emphasis> tells Pacemaker that this resource is a guest node with the hostname <emphasis role=\"strong\">guest1</emphasis>. The cluster will attempt to contact the virtual machine’s pacemaker_remote service at the hostname <emphasis role=\"strong\">guest1</emphasis> after it launches."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The ID of the resource creating the virtual machine (<emphasis role=\"strong\">vm-guest1</emphasis> in the above example) <emphasis>must</emphasis> be different from the virtual machine’s uname (<emphasis role=\"strong\">guest1</emphasis> in the above example). Pacemaker will create an implicit internal resource for the pacemaker_remote connection to the guest, named with the value of <emphasis role=\"strong\">remote-node</emphasis>, so that value cannot be used as the name of any other resource."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using a Guest Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Guest nodes will show up in <literal>crm_mon</literal> output as normal:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Example <literal>crm_mon</literal> output after <emphasis role=\"strong\">guest1</emphasis> is integrated into cluster"
msgstr ""
#. Tag: screen
#, no-c-format
-msgid "Last updated: Wed Mar 13 13:52:39 2013\n"
-"Last change: Wed Mar 13 13:25:17 2013 via crmd on node1\n"
-"Stack: corosync\n"
-"Current DC: node1 (24815808) - partition with quorum\n"
-"Version: 1.1.10\n"
-"2 Nodes configured, unknown expected votes\n"
-"2 Resources configured.\n"
+msgid "Stack: corosync\n"
+"Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 13:52:39 2018\n"
+"Last change: Fri Jan 12 13:25:17 2018 via pacemaker-controld on node1\n"
+"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ node1 guest1]\n"
"\n"
"vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, you could place a resource, such as a webserver, on <emphasis role=\"strong\">guest1</emphasis>:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create webserver apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=30s\n"
"# pcs constraint location webserver prefers guest1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, the crm_mon output would show:"
msgstr ""
#. Tag: screen
#, no-c-format
-msgid "Last updated: Wed Mar 13 13:52:39 2013\n"
-"Last change: Wed Mar 13 13:25:17 2013 via crmd on node1\n"
-"Stack: corosync\n"
-"Current DC: node1 (24815808) - partition with quorum\n"
-"Version: 1.1.10\n"
-"2 Nodes configured, unknown expected votes\n"
-"2 Resources configured.\n"
+msgid "Stack: corosync\n"
+"Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 13:52:39 2018\n"
+"Last change: Fri Jan 12 13:25:17 2018 via pacemaker-controld on node1\n"
+"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ node1 guest1]\n"
"\n"
"vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1\n"
"webserver (ocf::heartbeat::apache): Started guest1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is worth noting that after <emphasis role=\"strong\">guest1</emphasis> is integrated into the cluster, nearly all the Pacemaker command-line tools immediately become available to the guest node. This means things like <literal>crm_mon</literal>, <literal>crm_resource</literal>, and <literal>crm_attribute</literal> will work natively on the guest node, as long as the connection between the guest node and a cluster node exists. This is particularly important for any master/slave resources executing on the guest node that need access to <literal>crm_master</literal> to set transient attributes."
+msgid "It is worth noting that after <emphasis role=\"strong\">guest1</emphasis> is integrated into the cluster, nearly all the Pacemaker command-line tools immediately become available to the guest node. This means things like <literal>crm_mon</literal>, <literal>crm_resource</literal>, and <literal>crm_attribute</literal> will work natively on the guest node, as long as the connection between the guest node and a cluster node exists. This is particularly important for any promotable clone resources executing on the guest node that need access to <literal>crm_master</literal> to set transient attributes."
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Ch-Intro.pot b/doc/Pacemaker_Remote/pot/Ch-Intro.pot
index dd7ee06b4d..3aca2dd335 100644
--- a/doc/Pacemaker_Remote/pot/Ch-Intro.pot
+++ b/doc/Pacemaker_Remote/pot/Ch-Intro.pot
@@ -1,379 +1,249 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Scaling a Pacemaker Cluster"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Overview"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In a basic Pacemaker high-availability cluster,<footnote><para>See the <ulink url=\"http://www.clusterlabs.org/doc/\">Pacemaker documentation</ulink>, especially <emphasis>Clusters From Scratch</emphasis> and <emphasis>Pacemaker Explained</emphasis>, for basic information about high-availability using Pacemaker</para></footnote> each node runs the full cluster stack of corosync and all Pacemaker components. This allows great flexibility but limits scalability to around 16 nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To allow for scalability to dozens or even hundreds of nodes, Pacemaker allows nodes not running the full cluster stack to integrate into the cluster and have the cluster manage their resources as if they were a cluster node."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Terms"
msgstr ""
#. Tag: term
#, no-c-format
msgid "cluster node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A node running the full high-availability stack of corosync and all Pacemaker components. Cluster nodes may run cluster resources, run all Pacemaker command-line tools (<literal>crm_mon</literal>, <literal>crm_resource</literal> and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster’s Designated Controller (DC). <indexterm> <primary>cluster node</primary> </indexterm> <indexterm> <primary>node</primary><secondary>cluster node</secondary> </indexterm> <indexterm> <primary>cluster node</primary> </indexterm>"
msgstr ""
#. Tag: term
#, no-c-format
msgid "pacemaker_remote"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A small service daemon that allows a host to be used as a Pacemaker node without running the full cluster stack. Nodes running pacemaker_remote may run cluster resources and most command-line tools, but cannot perform other functions of full cluster nodes such as fencing execution, quorum voting or DC eligibility. The pacemaker_remote daemon is an enhanced version of Pacemaker’s local resource management daemon (LRMD). <indexterm> <primary>pacemaker_remote</primary> </indexterm>"
msgstr ""
#. Tag: term
#, no-c-format
msgid "remote node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A physical host running pacemaker_remote. Remote nodes have a special resource that manages communication with the cluster. This is sometimes referred to as the <emphasis>baremetal</emphasis> case. <indexterm> <primary>remote node</primary> </indexterm> <indexterm> <primary>node</primary><secondary>remote node</secondary> </indexterm> <indexterm> <primary>remote node</primary> </indexterm>"
msgstr ""
#. Tag: term
#, no-c-format
msgid "guest node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A virtual host running pacemaker_remote. Guest nodes differ from remote nodes mainly in that the guest node is itself a resource that the cluster manages. <indexterm> <primary>guest node</primary> </indexterm> <indexterm> <primary>node</primary><secondary>guest node</secondary> </indexterm> <indexterm> <primary>guest node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>Remote</emphasis> in this document refers to the node not being a part of the underlying corosync cluster. It has nothing to do with physical proximity. Remote nodes and guest nodes are subject to the same latency requirements as cluster nodes, which means they are typically in the same data center."
msgstr ""
#. Tag: para
#, no-c-format
msgid "It is important to distinguish the various roles a virtual machine can serve in Pacemaker clusters:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A virtual machine can run the full cluster stack, in which case it is a cluster node and is not itself managed by the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A virtual machine can be managed by the cluster as a resource, without the cluster having any awareness of the services running inside the virtual machine. The virtual machine is <emphasis>opaque</emphasis> to the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A virtual machine can be a cluster resource, and run pacemaker_remote to make it a guest node, allowing the cluster to manage services inside it. The virtual machine is <emphasis>transparent</emphasis> to the cluster."
msgstr ""
-#. Tag: title
-#, no-c-format
-msgid "Support in Pacemaker Versions"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "It is recommended to run Pacemaker 1.1.12 or later when using pacemaker_remote due to important bug fixes. An overview of changes in pacemaker_remote capability by version (aside from bug fixes, which are included in every version):"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.16"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for watchdog-based fencing (sbd) on remote nodes"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.15"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If pacemaker_remote is stopped on an active node, it will wait for the cluster to migrate all resources off before exiting, rather than exit immediately and get fenced."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.14"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Resources that create guest nodes can be included in groups"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "reconnect_interval option for remote nodes"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.13"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for maintenance mode"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Remote nodes can recover without being fenced when the cluster node hosting their connection fails"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>#kind</literal> built-in node attribute for use with rules"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.12"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for permanent node attributes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for migration"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.11"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for IPv6"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for remote nodes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for transient node attributes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Support for clusters with mixed endian architectures"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.10"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "remote-connect-timeout for guest nodes"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "1.1.9"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Initial version to include pacemaker_remote"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Limited to guest nodes in KVM/LXC environments using only IPv4; all nodes' architectures must have same endianness"
-msgstr ""
-
#. Tag: title
#, no-c-format
msgid "Guest Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>guest node</primary> </indexterm> <indexterm> <primary>node</primary><secondary>guest node</secondary> </indexterm> <indexterm> <primary>guest node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">\"I want a Pacemaker cluster to manage virtual machine resources, but I also want Pacemaker to be able to manage the resources that live within those virtual machines.\"</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Without pacemaker_remote, the possibilities for implementing the above use case have significant limitations:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster stack could be run on the physical hosts only, which loses the ability to monitor resources within the guests."
msgstr ""
#. Tag: para
#, no-c-format
msgid "A separate cluster could be on the virtual guests, which quickly hits scalability issues."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster stack could be run on the guests using the same cluster as the physical hosts, which also hits scalability issues and complicates fencing."
msgstr ""
#. Tag: para
#, no-c-format
msgid "With pacemaker_remote:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The physical hosts are cluster nodes (running the full cluster stack)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The virtual machines are guest nodes (running the pacemaker_remote service). Nearly zero configuration is required on the virtual machine."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The cluster stack on the cluster nodes launches the virtual machines and immediately connects to the pacemaker_remote service on them, allowing the virtual machines to integrate into the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The key difference here between the guest nodes and the cluster nodes is that the guest nodes do not run the cluster stack. This means they will never become the DC, initiate fencing actions or participate in quorum voting."
msgstr ""
#. Tag: para
#, no-c-format
msgid "On the other hand, this also means that they are not bound to the scalability limits associated with the cluster stack (no 16-node corosync member limits to deal with). That isn’t to say that guest nodes can scale indefinitely, but it is known that guest nodes scale horizontally much further than cluster nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Other than the quorum limitation, these guest nodes behave just like cluster nodes with respect to resource management. The cluster is fully capable of managing and monitoring resources on each guest node. You can build constraints against guest nodes, put them in standby, or do whatever else you’d expect to be able to do with cluster nodes. They even show up in <literal>crm_mon</literal> output as nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To solidify the concept, below is an example that is very similar to an actual deployment we test in our developer environment to verify guest node scalability:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "16 cluster nodes running the full corosync + pacemaker stack"
msgstr ""
#. Tag: para
#, no-c-format
msgid "64 Pacemaker-managed virtual machine resources running pacemaker_remote configured as guest nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "64 Pacemaker-managed webserver and database resources configured to run on the 64 guest nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "With this deployment, you would have 64 webservers and databases running on 64 virtual machines on 16 hardware nodes, all of which are managed and monitored by the same Pacemaker deployment. It is known that pacemaker_remote can scale to these lengths and possibly much further depending on the specific scenario."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Remote Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>remote node</primary> </indexterm> <indexterm> <primary>node</primary><secondary>remote node</secondary> </indexterm> <indexterm> <primary>remote node</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">\"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer.\"</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Ultimately, the primary advantage of remote nodes over cluster nodes is scalability. There are likely some other use cases related to geographically distributed HA clusters that remote nodes may serve a purpose in, but those use cases are not well understood at this point."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Like guest nodes, remote nodes will never become the DC, initiate fencing actions or participate in quorum voting."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That is not to say, however, that fencing of a remote node works any differently than that of a cluster node. The Pacemaker policy engine understands how to fence remote nodes. As long as a fencing device exists, the cluster is capable of ensuring remote nodes are fenced in the exact same way as cluster nodes."
+msgid "That is not to say, however, that fencing of a remote node works any differently than that of a cluster node. The Pacemaker scheduler understands how to fence remote nodes. As long as a fencing device exists, the cluster is capable of ensuring remote nodes are fenced in the exact same way as cluster nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Expanding the Cluster Stack"
msgstr ""
#. Tag: para
#, no-c-format
msgid "With pacemaker_remote, the traditional view of the high-availability stack can be expanded to include a new layer:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Traditional HA Stack"
msgstr ""
#. Tag: title
#, no-c-format
msgid "HA Stack With Guest Nodes"
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot
index a20b5674e3..d5d024a056 100644
--- a/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot
+++ b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot
@@ -1,767 +1,762 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Guest Node Walk-through"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">What this tutorial is:</emphasis> An in-depth walk-through of how to get Pacemaker to manage a KVM guest instance and integrate that guest into the cluster as a guest node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"strong\">What this tutorial is not:</emphasis> A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of guest nodes as quickly as possible."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the Physical Host"
msgstr ""
#. Tag: para
#, no-c-format
msgid "For this example, we will use a single physical host named <emphasis role=\"strong\">example-host</emphasis>. A production cluster would likely have multiple physical hosts, in which case you would run the commands here on each one, unless noted otherwise."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Firewall on Host"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On the physical host, 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 "Install Cluster Software"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y pacemaker corosync pcs resource-agents"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Corosync"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Corosync handles pacemaker’s cluster membership and messaging. The corosync config file is located in <literal>/etc/corosync/corosync.conf</literal>. That config file must be initialized with information about the cluster nodes before pacemaker can start."
msgstr ""
#. Tag: para
#, no-c-format
msgid "To initialize the corosync config file, execute the following <literal>pcs</literal> command, replacing the cluster name and hostname as desired:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster setup --force --local --name mycluster example-host"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you have multiple physical hosts, you would execute the setup command on only one host, but list all of them at the end of the command."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Pacemaker for Remote Node Communication"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a place to hold an authentication key for use with pacemaker_remote:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# mkdir -p --mode=0750 /etc/pacemaker\n"
"# chgrp haclient /etc/pacemaker"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Generate a key:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you have multiple physical hosts, you would generate the key on only one host, and copy it to the same location on all hosts."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Cluster Software"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Start the cluster"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster start"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify corosync membership"
msgstr ""
#. Tag: literallayout
#, no-c-format
msgid "# pcs status corosync\n"
"\n"
"Membership information\n"
"----------------------\n"
" Nodeid Votes Name\n"
" 1 1 example-host (local)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Verify pacemaker status. At first, the output will look like this:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
"WARNING: no stonith devices and stonith-enabled is not false\n"
-"Last updated: Fri Oct 9 15:18:32 2015 Last change: Fri Oct 9 12:42:21 2015 by root via cibadmin on example-host\n"
"Stack: corosync\n"
"Current DC: NONE\n"
-"1 node and 0 resources configured\n"
+"Last updated: Fri Jan 12 15:18:32 2018\n"
+"Last change: Fri Jan 12 12:42:21 2018 by root via cibadmin on example-host\n"
"\n"
-"Node example-host: UNCLEAN (offline)\n"
-"\n"
-"Full list of resources:\n"
+"1 node configured\n"
+"0 resources configured\n"
"\n"
+"Node example-host: UNCLEAN (offline)\n"
"\n"
-"PCSD Status:\n"
-" example-host: Online\n"
+"No active resources\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "After a short amount of time, you should see your host as a single node in the cluster:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
"WARNING: no stonith devices and stonith-enabled is not false\n"
-"Last updated: Fri Oct 9 15:20:05 2015 Last change: Fri Oct 9 12:42:21 2015 by root via cibadmin on example-host\n"
"Stack: corosync\n"
-"Current DC: example-host (version 1.1.13-a14efad) - partition WITHOUT quorum\n"
-"1 node and 0 resources configured\n"
-"\n"
-"Online: [ example-host ]\n"
+"Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition WITHOUT quorum\n"
+"Last updated: Fri Jan 12 15:20:05 2018\n"
+"Last change: Fri Jan 12 12:42:21 2018 by root via cibadmin on example-host\n"
"\n"
-"Full list of resources:\n"
+"1 node configured\n"
+"0 resources configured\n"
"\n"
+"Online: [ example-host ]\n"
"\n"
-"PCSD Status:\n"
-" example-host: Online\n"
+"No active resources\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Disable STONITH and Quorum"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, enable the cluster to work without quorum or stonith. This is required for the sake of getting this tutorial to work with a single cluster node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs property set stonith-enabled=false\n"
"# pcs property set no-quorum-policy=ignore"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The use of <literal>stonith-enabled=false</literal> is completely inappropriate for a production cluster. It tells the cluster to simply pretend that failed nodes are safely powered off. Some vendors will refuse to support clusters that have STONITH disabled. We disable STONITH here only to focus the discussion on pacemaker_remote, and to be able to use a single physical host in the example."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, the status output should look similar to this:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Oct 9 15:22:49 2015 Last change: Fri Oct 9 15:22:46 2015 by root via cibadmin on example-host\n"
"Stack: corosync\n"
-"Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n"
-"1 node and 0 resources configured\n"
-"\n"
-"Online: [ example-host ]\n"
+"Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 15:22:49 2018\n"
+"Last change: Fri Jan 12 15:22:46 2018 by root via cibadmin on example-host\n"
"\n"
-"Full list of resources:\n"
+"1 node configured\n"
+"0 resources configured\n"
"\n"
+"Online: [ example-host ]\n"
"\n"
-"PCSD Status:\n"
-" example-host: Online\n"
+"No active resources\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Go ahead and stop the cluster for now after verifying everything is in order."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs cluster stop --force"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Install Virtualization Software"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y kvm libvirt qemu-system qemu-kvm bridge-utils virt-manager\n"
"# systemctl enable libvirtd.service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Reboot the host."
msgstr ""
#. Tag: para
#, no-c-format
msgid "While KVM is used in this example, any virtualization platform with a Pacemaker resource agent can be used to create a guest node. The resource agent needs only to support usual commands (start, stop, etc.); Pacemaker implements the <emphasis role=\"strong\">remote-node</emphasis> meta-attribute, independent of the agent."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure the KVM guest"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Create Guest"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We will not outline here the installation steps required to create a KVM guest. There are plenty of tutorials available elsewhere that do that. Just be sure to configure the guest with a hostname and a static IP address (as an example here, we will use guest1 and 192.168.122.10)."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure Firewall on Guest"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On each guest, allow cluster-related services through the local firewall, following the same procedure as in <xref linkend=\"_configure_firewall_on_host\" />."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Connectivity"
msgstr ""
#. Tag: para
#, no-c-format
msgid "At this point, you should be able to ping and ssh into guests from hosts, and vice versa."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Configure pacemaker_remote"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Install pacemaker_remote, and enable it to run at start-up. Here, we also install the pacemaker package; it is not required, but it contains the dummy resource agent that we will use later for testing."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# yum install -y pacemaker pacemaker-remote resource-agents\n"
"# systemctl enable pacemaker_remote.service"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Copy the authentication key from a host:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# mkdir -p --mode=0750 /etc/pacemaker\n"
"# chgrp haclient /etc/pacemaker\n"
"# scp root@example-host:/etc/pacemaker/authkey /etc/pacemaker"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Start pacemaker_remote, and verify the start was successful:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# systemctl start pacemaker_remote\n"
"# systemctl status pacemaker_remote\n"
"\n"
" pacemaker_remote.service - Pacemaker Remote Service\n"
" Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)\n"
" Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago\n"
" Main PID: 1233 (pacemaker_remot)\n"
" CGroup: name=systemd:/system/pacemaker_remote.service\n"
-" └─1233 /usr/sbin/pacemaker_remoted\n"
+" └─1233 /usr/sbin/pacemaker-remoted\n"
"\n"
" Mar 14 18:24:04 guest1 systemd[1]: Starting Pacemaker Remote Service...\n"
" Mar 14 18:24:04 guest1 systemd[1]: Started Pacemaker Remote Service.\n"
-" Mar 14 18:24:04 guest1 pacemaker_remoted[1233]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121."
+" Mar 14 18:24:04 guest1 pacemaker-remoted[1233]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Verify Host Connection to Guest"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Before moving forward, it’s worth verifying that the host can contact the guest on port 3121. Here’s a trick you can use. Connect using ssh from the host. The connection will get destroyed, but how it is destroyed tells you whether it worked or not."
msgstr ""
#. Tag: para
#, no-c-format
msgid "First add guest1 to the host machine’s <literal>/etc/hosts</literal> file if you haven’t already. This is required unless you have DNS setup in a way where guest1’s address can be discovered."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# cat &lt;&lt; END &gt;&gt; /etc/hosts\n"
"192.168.122.10 guest1\n"
"END"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If running the ssh command on one of the cluster nodes results in this output before disconnecting, the connection works:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# ssh -p 3121 guest1\n"
"ssh_exchange_identification: read: Connection reset by peer"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you see one of these, the connection is not working:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# ssh -p 3121 guest1\n"
"ssh: connect to host guest1 port 3121: No route to host"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# ssh -p 3121 guest1\n"
"ssh: connect to host guest1 port 3121: Connection refused"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once you can successfully connect to the guest from the host, shutdown the guest. Pacemaker will be managing the virtual machine from this point forward."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Integrate Guest into Cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now the fun part, integrating the virtual machine you’ve just created into the cluster. It is incredibly simple."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Start the Cluster"
msgstr ""
#. Tag: para
#, no-c-format
msgid "On the host, start pacemaker."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Wait for the host to become the DC. The output of <literal>pcs status</literal> should look as it did in <xref linkend=\"_disable_stonith_and_quorum\" />."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Integrate as Guest Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you didn’t already do this earlier in the verify host to guest connection section, add the KVM guest’s IP address to the host’s <literal>/etc/hosts</literal> file so we can connect by hostname. For this example:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "We will use the <emphasis role=\"strong\">VirtualDomain</emphasis> resource agent for the management of the virtual machine. This agent requires the virtual machine’s XML config to be dumped to a file on disk. To do this, pick out the name of the virtual machine you just created from the output of this list."
msgstr ""
#. Tag: literallayout
#, no-c-format
msgid "# virsh list --all\n"
" Id Name State\n"
"----------------------------------------------------\n"
" - guest1 shut off"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In my case I named it guest1. Dump the xml to a file somewhere on the host using the following command."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# virsh dumpxml guest1 &gt; /etc/pacemaker/guest1.xml"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now just register the resource with pacemaker and you’re set!"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create vm-guest1 VirtualDomain hypervisor=\"qemu:///system\" \\\n"
" config=\"/etc/pacemaker/guest1.xml\" meta remote-node=guest1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This example puts the guest XML under /etc/pacemaker because the permissions and SELinux labeling should not need any changes. If you run into trouble with this or any step, try disabling SELinux with <literal>setenforce 0</literal>. If it works after that, see SELinux documentation for how to troubleshoot, if you wish to reenable SELinux."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Pacemaker will automatically monitor pacemaker_remote connections for failure, so it is not necessary to create a recurring monitor on the VirtualDomain resource."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once the <emphasis role=\"strong\">vm-guest1</emphasis> resource is started you will see <emphasis role=\"strong\">guest1</emphasis> appear in the <literal>pcs status</literal> output as a node. The final <literal>pcs status</literal> output should look something like this."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Oct 9 18:00:45 2015 Last change: Fri Oct 9 17:53:44 2015 by root via crm_resource on example-host\n"
"Stack: corosync\n"
-"Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n"
-"2 nodes and 2 resources configured\n"
+"Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 18:00:45 2018\n"
+"Last change: Fri Jan 12 17:53:44 2018 by root via crm_resource on example-host\n"
+"\n"
+"2 nodes configured\n"
+"2 resources configured\n"
"\n"
"Online: [ example-host ]\n"
"GuestOnline: [ guest1@example-host ]\n"
"\n"
"Full list of resources:\n"
"\n"
" vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n"
"\n"
-"PCSD Status:\n"
-" example-host: Online\n"
-"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Starting Resources on KVM Guest"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The commands below demonstrate how resources can be executed on both the guest node and the cluster node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Create a few Dummy resources. Dummy resources are real resource agents used just for testing purposes. They actually execute on the host they are assigned to just like an apache server or database would, except their execution just means a file was created. When the resource is stopped, that the file it created is removed."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create FAKE1 ocf:pacemaker:Dummy\n"
"# pcs resource create FAKE2 ocf:pacemaker:Dummy\n"
"# pcs resource create FAKE3 ocf:pacemaker:Dummy\n"
"# pcs resource create FAKE4 ocf:pacemaker:Dummy\n"
"# pcs resource create FAKE5 ocf:pacemaker:Dummy"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now check your <literal>pcs status</literal> output. In the resource section, you should see something like the following, where some of the resources started on the cluster node, and some started on the guest node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "Full list of resources:\n"
"\n"
" vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n"
" FAKE1 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE2 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE3 (ocf::pacemaker:Dummy): Started example-host\n"
" FAKE4 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE5 (ocf::pacemaker:Dummy): Started example-host"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The guest node, <emphasis role=\"strong\">guest1</emphasis>, reacts just like any other node in the cluster. For example, pick out a resource that is running on your cluster node. For my purposes, I am picking FAKE3 from the output above. We can force FAKE3 to run on <emphasis role=\"strong\">guest1</emphasis> in the exact same way we would any other node."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs constraint location FAKE3 prefers guest1"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Now, looking at the bottom of the <literal>pcs status</literal> output you’ll see FAKE3 is on <emphasis role=\"strong\">guest1</emphasis>."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "Full list of resources:\n"
"\n"
" vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n"
" FAKE1 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE2 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE3 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE4 (ocf::pacemaker:Dummy): Started example-host\n"
" FAKE5 (ocf::pacemaker:Dummy): Started example-host"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Testing Recovery and Fencing"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pacemaker’s policy engine is smart enough to know fencing guest nodes associated with a virtual machine means shutting off/rebooting the virtual machine. No special configuration is necessary to make this happen. If you are interested in testing this functionality out, trying stopping the guest’s pacemaker_remote daemon. This would be equivalent of abruptly terminating a cluster node’s corosync membership without properly shutting it down."
+msgid "Pacemaker’s scheduler is smart enough to know fencing guest nodes associated with a virtual machine means shutting off/rebooting the virtual machine. No special configuration is necessary to make this happen. If you are interested in testing this functionality out, trying stopping the guest’s pacemaker_remote daemon. This would be equivalent of abruptly terminating a cluster node’s corosync membership without properly shutting it down."
msgstr ""
#. Tag: para
#, no-c-format
msgid "ssh into the guest and run this command."
msgstr ""
#. Tag: screen
#, no-c-format
-msgid "# kill -9 `pidof pacemaker_remoted`"
+msgid "# kill -9 $(pidof pacemaker-remoted)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Within a few seconds, your <literal>pcs status</literal> output will show a monitor failure, and the <emphasis role=\"strong\">guest1</emphasis> node will not be shown while it is being recovered."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs status\n"
"Cluster name: mycluster\n"
-"Last updated: Fri Oct 9 18:08:35 2015 Last change: Fri Oct 9 18:07:00 2015 by root via cibadmin on example-host\n"
"Stack: corosync\n"
-"Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n"
-"2 nodes and 7 resources configured\n"
+"Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 18:08:35 2018\n"
+"Last change: Fri Jan 12 18:07:00 2018 by root via cibadmin on example-host\n"
+"\n"
+"2 nodes configured\n"
+"7 resources configured\n"
"\n"
"Online: [ example-host ]\n"
"\n"
"Full list of resources:\n"
"\n"
" vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n"
" FAKE1 (ocf::pacemaker:Dummy): Stopped\n"
" FAKE2 (ocf::pacemaker:Dummy): Stopped\n"
" FAKE3 (ocf::pacemaker:Dummy): Stopped\n"
" FAKE4 (ocf::pacemaker:Dummy): Started example-host\n"
" FAKE5 (ocf::pacemaker:Dummy): Started example-host\n"
"\n"
"Failed Actions:\n"
"* guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none',\n"
-" last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms\n"
-"\n"
-"\n"
-"PCSD Status:\n"
-" example-host: Online\n"
+" last-rc-change='Fri Jan 12 18:08:29 2018', queued=0ms, exec=0ms\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A guest node involves two resources: the one you explicitly configured creates the guest, and Pacemaker creates an implicit resource for the pacemaker_remote connection, which will be named the same as the value of the <emphasis role=\"strong\">remote-node</emphasis> attribute of the explicit resource. When we killed pacemaker_remote, it is the implicit resource that failed, which is why the failed action starts with <emphasis role=\"strong\">guest1</emphasis> and not <emphasis role=\"strong\">vm-guest1</emphasis>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Once recovery of the guest is complete, you’ll see it automatically get re-integrated into the cluster. The final <literal>pcs status</literal> output should look something like this."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "Cluster name: mycluster\n"
-"Last updated: Fri Oct 9 18:18:30 2015 Last change: Fri Oct 9 18:07:00 2015 by root via cibadmin on example-host\n"
"Stack: corosync\n"
-"Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n"
-"2 nodes and 7 resources configured\n"
+"Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum\n"
+"Last updated: Fri Jan 12 18:18:30 2018\n"
+"Last change: Fri Jan 12 18:07:00 2018 by root via cibadmin on example-host\n"
+"\n"
+"2 nodes configured\n"
+"7 resources configured\n"
"\n"
"Online: [ example-host ]\n"
"GuestOnline: [ guest1@example-host ]\n"
"\n"
"Full list of resources:\n"
"\n"
" vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n"
" FAKE1 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE2 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE3 (ocf::pacemaker:Dummy): Started guest1\n"
" FAKE4 (ocf::pacemaker:Dummy): Started example-host\n"
" FAKE5 (ocf::pacemaker:Dummy): Started example-host\n"
"\n"
"Failed Actions:\n"
"* guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none',\n"
-" last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms\n"
-"\n"
-"\n"
-"PCSD Status:\n"
-" example-host: Online\n"
+" last-rc-change='Fri Jan 12 18:08:29 2018', queued=0ms, exec=0ms\n"
"\n"
"Daemon Status:\n"
" corosync: active/disabled\n"
" pacemaker: active/disabled\n"
" pcsd: active/enabled"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Normally, once you’ve investigated and addressed a failed action, you can clear the failure. However Pacemaker does not yet support cleanup for the implicitly created connection resource while the explicit resource is active. If you want to clear the failed action from the status output, stop the guest resource before clearing it. For example:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource disable vm-guest1 --wait\n"
"# pcs resource cleanup guest1\n"
"# pcs resource enable vm-guest1"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Accessing Cluster Tools from Guest Node"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Besides allowing the cluster to manage resources on a guest node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (<literal>crm_resource</literal>, <literal>crm_mon</literal>, <literal>crm_attribute</literal>, <literal>crm_master</literal>, etc.) to work on guest nodes natively."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Try it: Run <literal>crm_mon</literal> on the guest after pacemaker has integrated the guest node into the cluster. These tools just work. This means resource agents such as master/slave resources which need access to tools like <literal>crm_master</literal> work seamlessly on the guest nodes."
+msgid "Try it: Run <literal>crm_mon</literal> on the guest after pacemaker has integrated the guest node into the cluster. These tools just work. This means resource agents such as promotable resources (which need access to tools like <literal>crm_master</literal>) work seamlessly on the guest nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Higher-level command shells such as <literal>pcs</literal> may have partial support on guest nodes, but it is recommended to run them from a cluster node."
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Ch-Options.pot b/doc/Pacemaker_Remote/pot/Ch-Options.pot
index 77a04cde59..10dcbe1a9c 100644
--- a/doc/Pacemaker_Remote/pot/Ch-Options.pot
+++ b/doc/Pacemaker_Remote/pot/Ch-Options.pot
@@ -1,232 +1,232 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Configuration Explained"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The walk-through examples use some of these options, but don’t explain exactly what they mean or do. This section is meant to be the go-to resource for all the options available for configuring pacemaker_remote-based nodes. <indexterm> <primary>configuration</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Resource Meta-Attributes for Guest Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When configuring a virtual machine as a guest node, the virtual machine is created using one of the usual resource agents for that purpose (for example, ocf:heartbeat:VirtualDomain or ocf:heartbeat:Xen), with additional metadata parameters."
msgstr ""
#. Tag: para
#, no-c-format
msgid "No restrictions are enforced on what agents may be used to create a guest node, but obviously the agent must create a distinct environment capable of running the pacemaker_remote daemon and cluster resources. An additional requirement is that fencing the host running the guest node resource must be sufficient for ensuring the guest node is stopped. This means, for example, that not all hypervisors supported by VirtualDomain may be used to create guest nodes; if the guest can survive the hypervisor being fenced, it may not be used as a guest node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Below are the metadata options available to enable a resource as a guest node and define its connection parameters."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Meta-attributes for configuring VM resources as guest nodes"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Option"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>none</emphasis>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The node name of the guest node this resource defines. This both enables the resource as a guest node and defines the unique name used to identify the guest node. If no other parameters are set, this value will also be assumed as the hostname to use when connecting to pacemaker_remote on the VM. This value <emphasis role=\"strong\">must not</emphasis> overlap with any resource or node IDs."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-port</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "3121"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The port on the virtual machine that the cluster will use to connect to pacemaker_remote."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-addr</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis>value of</emphasis> <literal>remote-node</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The IP address or hostname to use when connecting to pacemaker_remote on the VM."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>remote-connect-timeout</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "60s"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How long before a pending guest connection will time out."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Connection Resources for Remote Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A remote node is defined by a connection resource. That connection resource has instance attributes that define where the remote node is located on the network and how to communicate with it."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Descriptions of these instance attributes can be retrieved using the following <literal>pcs</literal> command:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource describe remote\n"
"ocf:pacemaker:remote - remote resource agent\n"
"\n"
"Resource options:\n"
" server: Server location to connect to. This can be an ip address or hostname.\n"
" port: tcp port to connect to.\n"
" reconnect_interval: Interval in seconds at which Pacemaker will attempt to\n"
" reconnect to a remote node after an active connection to\n"
" the remote node has been severed. When this value is\n"
" nonzero, Pacemaker will retry the connection\n"
" indefinitely, at the specified interval. As with any\n"
" time-based actions, this is not guaranteed to be checked\n"
" more frequently than the value of the\n"
" cluster-recheck-interval cluster option."
msgstr ""
#. Tag: para
#, no-c-format
msgid "When defining a remote node’s connection resource, it is common and recommended to name the connection resource the same as the remote node’s hostname. By default, if no <emphasis role=\"strong\">server</emphasis> option is provided, the cluster will attempt to contact the remote node using the resource name as the hostname."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Example defining a remote node with the hostname <emphasis role=\"strong\">remote1</emphasis>:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create remote1 remote"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Example defining a remote node to connect to a specific IP address and port:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# pcs resource create remote1 remote server=192.168.122.200 port=8938"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Environment Variables for Daemon Start-up"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Authentication and encryption of the connection between cluster nodes and nodes running pacemaker_remote is achieved using with <ulink url=\"https://en.wikipedia.org/wiki/TLS-PSK\">TLS-PSK</ulink> encryption/authentication over TCP (port 3121 by default). This means that both the cluster node and remote node must share the same private key. By default, this key is placed at <literal>/etc/pacemaker/authkey</literal> on each node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "You can change the default port and/or key location for Pacemaker and pacemaker_remote via environment variables. How these variables are set varies by OS, but usually they are set in the <literal>/etc/sysconfig/pacemaker</literal> or <literal>/etc/default/pacemaker</literal> file."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "#==#==# Pacemaker Remote\n"
"# Use a custom directory for finding the authkey.\n"
"PCMK_authkey_location=/etc/pacemaker/authkey\n"
"#\n"
"# Specify a custom port for Pacemaker Remote connections\n"
"PCMK_remote_port=3121"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Removing Remote Nodes and Guest Nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "If the resource creating a guest node, or the <emphasis role=\"strong\">ocf:pacemaker:remote</emphasis> resource creating a connection to a remote node, is removed from the configuration, the affected node will continue to show up in output as an offline node."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you want to get rid of that output, run (replacing $NODE_NAME appropriately):"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "# crm_node --force --remove $NODE_NAME"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Be absolutely sure that there are no references to the node’s resource in the configuration before running the above command."
msgstr ""
diff --git a/doc/Pacemaker_Remote/pot/Revision_History.pot b/doc/Pacemaker_Remote/pot/Revision_History.pot
index e5aef3b9b2..84dcd5b59e 100644
--- a/doc/Pacemaker_Remote/pot/Revision_History.pot
+++ b/doc/Pacemaker_Remote/pot/Revision_History.pot
@@ -1,74 +1,79 @@
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2017-10-06 19:59-0500\n"
-"PO-Revision-Date: 2017-10-06 19:59-0500\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 "Revision History"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "David"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Vossel"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Import from Pages.app"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Added Future Features Section"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Added Baremetal remote-node feature documentation"
msgstr ""
#. Tag: firstname
#, no-c-format
msgid "Ken"
msgstr ""
#. Tag: surname
#, no-c-format
msgid "Gaillot"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Targeted CentOS 7.1 and Pacemaker 1.1.12+, updated for current terminology and practice"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for Pacemaker 1.1.14"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for Pacemaker 1.1.15"
msgstr ""
#. Tag: member
#, no-c-format
msgid "Updated for Pacemaker 1.1.16"
msgstr ""
+#. Tag: member
+#, no-c-format
+msgid "Update banner for Pacemaker 2.0 and content for CentOS 7.4 with Pacemaker 1.1.16"
+msgstr ""
+
diff --git a/include/crm/common/internal.h b/include/crm/common/internal.h
index d33f041a5d..c9ee488755 100644
--- a/include/crm/common/internal.h
+++ b/include/crm/common/internal.h
@@ -1,146 +1,151 @@
/*
* Copyright 2015-2018 Andrew Beekhof <andrew@beekhof.net>
*
* This source code is licensed under the GNU Lesser General Public License
* version 2.1 or later (LGPLv2.1+) WITHOUT ANY WARRANTY.
*/
#ifndef CRM_COMMON_INTERNAL__H
#define CRM_COMMON_INTERNAL__H
#include <glib.h> /* for gboolean */
#include <dirent.h> /* for struct dirent */
#include <unistd.h> /* for getpid() */
#include <sys/types.h> /* for uid_t and gid_t */
#include <crm/common/logging.h>
/* internal I/O utilities (from io.c) */
char *generate_series_filename(const char *directory, const char *series, int sequence,
gboolean bzip);
int get_last_sequence(const char *directory, const char *series);
void write_last_sequence(const char *directory, const char *series, int sequence, int max);
int crm_chown_last_sequence(const char *directory, const char *series, uid_t uid, gid_t gid);
bool pcmk__daemon_can_write(const char *dir, const char *file);
void crm_sync_directory(const char *name);
char *crm_read_contents(const char *filename);
int crm_write_sync(int fd, const char *contents);
int crm_set_nonblocking(int fd);
const char *crm_get_tmpdir(void);
/* internal procfs utilities (from procfs.c) */
int crm_procfs_process_info(struct dirent *entry, char *name, int *pid);
int crm_procfs_pid_of(const char *name);
unsigned int crm_procfs_num_cores(void);
/* internal XML schema functions (from xml.c) */
void crm_schema_init(void);
void crm_schema_cleanup(void);
/* internal functions related to process IDs (from pid.c) */
int crm_pid_active(long pid, const char *daemon);
long crm_pidfile_inuse(const char *filename, long mypid, const char *daemon);
long crm_read_pidfile(const char *filename);
int crm_lock_pidfile(const char *filename, const char *name);
/* interal functions related to resource operations (from operations.c) */
char *generate_op_key(const char *rsc_id, const char *op_type,
guint interval_ms);
char *generate_notify_key(const char *rsc_id, const char *notify_type,
const char *op_type);
char *generate_transition_magic(const char *transition_key, int op_status,
int op_rc);
char *generate_transition_key(int action, int transition_id, int target_rc,
const char *node);
void filter_action_parameters(xmlNode *param_set, const char *version);
xmlNode *create_operation_update(xmlNode *parent, lrmd_event_data_t *event,
const char *caller_version, int target_rc,
const char *node, const char *origin,
int level);
+// miscellaneous utilities (from utils.c)
+
+const char *pcmk_message_name(const char *name);
+
+
/* internal generic string functions (from strings.c) */
long long crm_int_helper(const char *text, char **end_text);
guint crm_parse_ms(const char *text);
bool crm_starts_with(const char *str, const char *prefix);
gboolean crm_ends_with(const char *s, const char *match);
gboolean crm_ends_with_ext(const char *s, const char *match);
char *add_list_element(char *list, const char *value);
bool crm_compress_string(const char *data, int length, int max, char **result,
unsigned int *result_len);
gint crm_alpha_sort(gconstpointer a, gconstpointer b);
static inline char *
crm_concat(const char *prefix, const char *suffix, char join)
{
CRM_ASSERT(prefix && suffix);
return crm_strdup_printf("%s%c%s", prefix, join, suffix);
}
static inline int
crm_strlen_zero(const char *s)
{
return !s || *s == '\0';
}
static inline char *
crm_getpid_s()
{
return crm_strdup_printf("%lu", (unsigned long) getpid());
}
/* convenience functions for failure-related node attributes */
#define CRM_FAIL_COUNT_PREFIX "fail-count"
#define CRM_LAST_FAILURE_PREFIX "last-failure"
/*!
* \internal
* \brief Generate a failure-related node attribute name for a resource
*
* \param[in] prefix Start of attribute name
* \param[in] rsc_id Resource name
* \param[in] op Operation name
* \param[in] interval_ms Operation interval
*
* \return Newly allocated string with attribute name
*
* \note Failure attributes are named like PREFIX-RSC#OP_INTERVAL (for example,
* "fail-count-myrsc#monitor_30000"). The '#' is used because it is not
* a valid character in a resource ID, to reliably distinguish where the
* operation name begins. The '_' is used simply to be more comparable to
* action labels like "myrsc_monitor_30000".
*/
static inline char *
crm_fail_attr_name(const char *prefix, const char *rsc_id, const char *op,
guint interval_ms)
{
CRM_CHECK(prefix && rsc_id && op, return NULL);
return crm_strdup_printf("%s-%s#%s_%u", prefix, rsc_id, op, interval_ms);
}
static inline char *
crm_failcount_name(const char *rsc_id, const char *op, guint interval_ms)
{
return crm_fail_attr_name(CRM_FAIL_COUNT_PREFIX, rsc_id, op, interval_ms);
}
static inline char *
crm_lastfailure_name(const char *rsc_id, const char *op, guint interval_ms)
{
return crm_fail_attr_name(CRM_LAST_FAILURE_PREFIX, rsc_id, op, interval_ms);
}
#endif /* CRM_COMMON_INTERNAL__H */
diff --git a/lib/cluster/cpg.c b/lib/cluster/cpg.c
index 1e33a42610..c1a36353c5 100644
--- a/lib/cluster/cpg.c
+++ b/lib/cluster/cpg.c
@@ -1,659 +1,649 @@
/*
- * Copyright (C) 2004 Andrew Beekhof <andrew@beekhof.net>
+ * Copyright 2004-2018 Andrew Beekhof <andrew@beekhof.net>
*
- * This library is free software; you can redistribute it and/or
- * modify it under the terms of the GNU Lesser General Public
- * License as published by the Free Software Foundation; either
- * version 2.1 of the License, or (at your option) any later version.
- *
- * This library is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- * Lesser General Public License for more details.
- *
- * You should have received a copy of the GNU Lesser General Public
- * License along with this library; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ * This source code is licensed under the GNU Lesser General Public License
+ * version 2.1 or later (LGPLv2.1+) WITHOUT ANY WARRANTY.
*/
#include <crm_internal.h>
#include <bzlib.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
#include <netdb.h>
#include <crm/common/ipc.h>
#include <crm/cluster/internal.h>
#include <crm/common/mainloop.h>
#include <sys/utsname.h>
#include <qb/qbipcc.h>
#include <qb/qbutil.h>
#include <corosync/corodefs.h>
#include <corosync/corotypes.h>
#include <corosync/hdb.h>
#include <corosync/cpg.h>
#include <crm/msg_xml.h>
cpg_handle_t pcmk_cpg_handle = 0; /* TODO: Remove, use cluster.cpg_handle */
static bool cpg_evicted = FALSE;
gboolean(*pcmk_cpg_dispatch_fn) (int kind, const char *from, const char *data) = NULL;
#define cs_repeat(counter, max, code) do { \
code; \
if(rc == CS_ERR_TRY_AGAIN || rc == CS_ERR_QUEUE_FULL) { \
counter++; \
crm_debug("Retrying operation after %ds", counter); \
sleep(counter); \
} else { \
break; \
} \
} while(counter < max)
void
cluster_disconnect_cpg(crm_cluster_t *cluster)
{
pcmk_cpg_handle = 0;
if (cluster->cpg_handle) {
crm_trace("Disconnecting CPG");
cpg_leave(cluster->cpg_handle, &cluster->group);
cpg_finalize(cluster->cpg_handle);
cluster->cpg_handle = 0;
} else {
crm_info("No CPG connection");
}
}
uint32_t get_local_nodeid(cpg_handle_t handle)
{
int rc = CS_OK;
int retries = 0;
static uint32_t local_nodeid = 0;
cpg_handle_t local_handle = handle;
cpg_callbacks_t cb = { };
if(local_nodeid != 0) {
return local_nodeid;
}
if(handle == 0) {
crm_trace("Creating connection");
cs_repeat(retries, 5, rc = cpg_initialize(&local_handle, &cb));
}
if (rc == CS_OK) {
retries = 0;
crm_trace("Performing lookup");
cs_repeat(retries, 5, rc = cpg_local_get(local_handle, &local_nodeid));
}
if (rc != CS_OK) {
crm_err("Could not get local node id from the CPG API: %s (%d)", ais_error2text(rc), rc);
}
if(handle == 0) {
crm_trace("Closing connection");
cpg_finalize(local_handle);
}
crm_debug("Local nodeid is %u", local_nodeid);
return local_nodeid;
}
GListPtr cs_message_queue = NULL;
int cs_message_timer = 0;
static ssize_t crm_cs_flush(gpointer data);
static gboolean
crm_cs_flush_cb(gpointer data)
{
cs_message_timer = 0;
crm_cs_flush(data);
return FALSE;
}
#define CS_SEND_MAX 200
static ssize_t
crm_cs_flush(gpointer data)
{
int sent = 0;
ssize_t rc = 0;
int queue_len = 0;
static unsigned int last_sent = 0;
cpg_handle_t *handle = (cpg_handle_t *)data;
if (*handle == 0) {
crm_trace("Connection is dead");
return pcmk_ok;
}
queue_len = g_list_length(cs_message_queue);
if ((queue_len % 1000) == 0 && queue_len > 1) {
crm_err("CPG queue has grown to %d", queue_len);
} else if (queue_len == CS_SEND_MAX) {
crm_warn("CPG queue has grown to %d", queue_len);
}
if (cs_message_timer) {
/* There is already a timer, wait until it goes off */
crm_trace("Timer active %d", cs_message_timer);
return pcmk_ok;
}
while (cs_message_queue && sent < CS_SEND_MAX) {
struct iovec *iov = cs_message_queue->data;
errno = 0;
rc = cpg_mcast_joined(*handle, CPG_TYPE_AGREED, iov, 1);
if (rc != CS_OK) {
break;
}
sent++;
last_sent++;
crm_trace("CPG message sent, size=%llu",
(unsigned long long) iov->iov_len);
cs_message_queue = g_list_remove(cs_message_queue, iov);
free(iov->iov_base);
free(iov);
}
queue_len -= sent;
if (sent > 1 || cs_message_queue) {
crm_info("Sent %d CPG messages (%d remaining, last=%u): %s (%lld)",
sent, queue_len, last_sent, ais_error2text(rc),
(long long) rc);
} else {
crm_trace("Sent %d CPG messages (%d remaining, last=%u): %s (%lld)",
sent, queue_len, last_sent, ais_error2text(rc),
(long long) rc);
}
if (cs_message_queue) {
uint32_t delay_ms = 100;
if(rc != CS_OK) {
/* Proportionally more if sending failed but cap at 1s */
delay_ms = QB_MIN(1000, CS_SEND_MAX + (10 * queue_len));
}
cs_message_timer = g_timeout_add(delay_ms, crm_cs_flush_cb, data);
}
return rc;
}
gboolean
send_cpg_iov(struct iovec * iov)
{
static unsigned int queued = 0;
queued++;
crm_trace("Queueing CPG message %u (%llu bytes)",
queued, (unsigned long long) iov->iov_len);
cs_message_queue = g_list_append(cs_message_queue, iov);
crm_cs_flush(&pcmk_cpg_handle);
return TRUE;
}
static int
pcmk_cpg_dispatch(gpointer user_data)
{
int rc = 0;
crm_cluster_t *cluster = (crm_cluster_t*) user_data;
rc = cpg_dispatch(cluster->cpg_handle, CS_DISPATCH_ONE);
if (rc != CS_OK) {
crm_err("Connection to the CPG API failed: %s (%d)", ais_error2text(rc), rc);
cluster->cpg_handle = 0;
return -1;
} else if(cpg_evicted) {
crm_err("Evicted from CPG membership");
return -1;
}
return 0;
}
char *
pcmk_message_common_cs(cpg_handle_t handle, uint32_t nodeid, uint32_t pid, void *content,
uint32_t *kind, const char **from)
{
char *data = NULL;
AIS_Message *msg = (AIS_Message *) content;
if(handle) {
// Do filtering and field massaging
uint32_t local_nodeid = get_local_nodeid(handle);
const char *local_name = get_local_node_name();
if (msg->sender.id > 0 && msg->sender.id != nodeid) {
crm_err("Nodeid mismatch from %d.%d: claimed nodeid=%u", nodeid, pid, msg->sender.id);
return NULL;
} else if (msg->host.id != 0 && (local_nodeid != msg->host.id)) {
/* Not for us */
crm_trace("Not for us: %u != %u", msg->host.id, local_nodeid);
return NULL;
} else if (msg->host.size != 0 && safe_str_neq(msg->host.uname, local_name)) {
/* Not for us */
crm_trace("Not for us: %s != %s", msg->host.uname, local_name);
return NULL;
}
msg->sender.id = nodeid;
if (msg->sender.size == 0) {
crm_node_t *peer = crm_get_peer(nodeid, NULL);
if (peer == NULL) {
crm_err("Peer with nodeid=%u is unknown", nodeid);
} else if (peer->uname == NULL) {
crm_err("No uname for peer with nodeid=%u", nodeid);
} else {
crm_notice("Fixing uname for peer with nodeid=%u", nodeid);
msg->sender.size = strlen(peer->uname);
memset(msg->sender.uname, 0, MAX_NAME);
memcpy(msg->sender.uname, peer->uname, msg->sender.size);
}
}
}
crm_trace("Got new%s message (size=%d, %d, %d)",
msg->is_compressed ? " compressed" : "",
ais_data_len(msg), msg->size, msg->compressed_size);
if (kind != NULL) {
*kind = msg->header.id;
}
if (from != NULL) {
*from = msg->sender.uname;
}
if (msg->is_compressed && msg->size > 0) {
int rc = BZ_OK;
char *uncompressed = NULL;
unsigned int new_size = msg->size + 1;
if (check_message_sanity(msg, NULL) == FALSE) {
goto badmsg;
}
crm_trace("Decompressing message data");
uncompressed = calloc(1, new_size);
rc = BZ2_bzBuffToBuffDecompress(uncompressed, &new_size, msg->data, msg->compressed_size, 1, 0);
if (rc != BZ_OK) {
crm_err("Decompression failed: %s " CRM_XS " bzerror=%d",
bz2_strerror(rc), rc);
free(uncompressed);
goto badmsg;
}
CRM_ASSERT(rc == BZ_OK);
CRM_ASSERT(new_size == msg->size);
data = uncompressed;
} else if (check_message_sanity(msg, data) == FALSE) {
goto badmsg;
} else if (safe_str_eq("identify", data)) {
char *pid_s = crm_getpid_s();
send_cluster_text(crm_class_cluster, pid_s, TRUE, NULL, crm_msg_ais);
free(pid_s);
return NULL;
} else {
data = strdup(msg->data);
}
// Is this necessary?
crm_get_peer(msg->sender.id, msg->sender.uname);
crm_trace("Payload: %.200s", data);
return data;
badmsg:
crm_err("Invalid message (id=%d, dest=%s:%s, from=%s:%s.%d):"
" min=%d, total=%d, size=%d, bz2_size=%d",
msg->id, ais_dest(&(msg->host)), msg_type2text(msg->host.type),
ais_dest(&(msg->sender)), msg_type2text(msg->sender.type),
msg->sender.pid, (int)sizeof(AIS_Message),
msg->header.size, msg->size, msg->compressed_size);
free(data);
return NULL;
}
void
pcmk_cpg_membership(cpg_handle_t handle,
const struct cpg_name *groupName,
const struct cpg_address *member_list, size_t member_list_entries,
const struct cpg_address *left_list, size_t left_list_entries,
const struct cpg_address *joined_list, size_t joined_list_entries)
{
int i;
gboolean found = FALSE;
static int counter = 0;
uint32_t local_nodeid = get_local_nodeid(handle);
for (i = 0; i < left_list_entries; i++) {
crm_node_t *peer = crm_find_peer(left_list[i].nodeid, NULL);
crm_info("Node %u left group %s (peer=%s, counter=%d.%d)",
left_list[i].nodeid, groupName->value,
(peer? peer->uname : "<none>"), counter, i);
if (peer) {
crm_update_peer_proc(__FUNCTION__, peer, crm_proc_cpg, OFFLINESTATUS);
}
}
for (i = 0; i < joined_list_entries; i++) {
crm_info("Node %u joined group %s (counter=%d.%d)",
joined_list[i].nodeid, groupName->value, counter, i);
}
for (i = 0; i < member_list_entries; i++) {
crm_node_t *peer = crm_get_peer(member_list[i].nodeid, NULL);
crm_info("Node %u still member of group %s (peer=%s, counter=%d.%d)",
member_list[i].nodeid, groupName->value,
(peer? peer->uname : "<none>"), counter, i);
/* Anyone that is sending us CPG messages must also be a _CPG_ member.
* But it's _not_ safe to assume it's in the quorum membership.
* We may have just found out it's dead and are processing the last couple of messages it sent
*/
peer = crm_update_peer_proc(__FUNCTION__, peer, crm_proc_cpg, ONLINESTATUS);
if(peer && peer->state && crm_is_peer_active(peer) == FALSE) {
time_t now = time(NULL);
/* Co-opt the otherwise unused votes field */
if(peer->votes == 0) {
peer->votes = now;
} else if(now > (60 + peer->votes)) {
/* On the other hand, if we're still getting messages, at a
* certain point we need to acknowledge our internal cache is
* probably wrong. Use 1 minute.
*/
crm_err("Node %s[%u] appears to be online even though we think it is dead", peer->uname, peer->id);
if (crm_update_peer_state(__FUNCTION__, peer, CRM_NODE_MEMBER, 0)) {
peer->votes = 0;
}
}
}
if (local_nodeid == member_list[i].nodeid) {
found = TRUE;
}
}
if (!found) {
crm_err("We're not part of CPG group '%s' anymore!", groupName->value);
cpg_evicted = TRUE;
}
counter++;
}
gboolean
cluster_connect_cpg(crm_cluster_t *cluster)
{
int rc = -1;
int fd = 0;
int retries = 0;
uint32_t id = 0;
crm_node_t *peer = NULL;
cpg_handle_t handle = 0;
+ const char *message_name = pcmk_message_name(crm_system_name);
struct mainloop_fd_callbacks cpg_fd_callbacks = {
.dispatch = pcmk_cpg_dispatch,
.destroy = cluster->destroy,
};
cpg_callbacks_t cpg_callbacks = {
.cpg_deliver_fn = cluster->cpg.cpg_deliver_fn,
.cpg_confchg_fn = cluster->cpg.cpg_confchg_fn,
/* .cpg_deliver_fn = pcmk_cpg_deliver, */
/* .cpg_confchg_fn = pcmk_cpg_membership, */
};
cpg_evicted = FALSE;
cluster->group.length = 0;
cluster->group.value[0] = 0;
/* group.value is char[128] */
- strncpy(cluster->group.value, crm_system_name?crm_system_name:"unknown", 127);
+ strncpy(cluster->group.value, message_name, 127);
cluster->group.value[127] = 0;
cluster->group.length = 1 + QB_MIN(127, strlen(cluster->group.value));
cs_repeat(retries, 30, rc = cpg_initialize(&handle, &cpg_callbacks));
if (rc != CS_OK) {
crm_err("Could not connect to the Cluster Process Group API: %d", rc);
goto bail;
}
id = get_local_nodeid(handle);
if (id == 0) {
crm_err("Could not get local node id from the CPG API");
goto bail;
}
cluster->nodeid = id;
retries = 0;
cs_repeat(retries, 30, rc = cpg_join(handle, &cluster->group));
if (rc != CS_OK) {
- crm_err("Could not join the CPG group '%s': %d", crm_system_name, rc);
+ crm_err("Could not join the CPG group '%s': %d", message_name, rc);
goto bail;
}
rc = cpg_fd_get(handle, &fd);
if (rc != CS_OK) {
crm_err("Could not obtain the CPG API connection: %d", rc);
goto bail;
}
pcmk_cpg_handle = handle;
cluster->cpg_handle = handle;
mainloop_add_fd("corosync-cpg", G_PRIORITY_MEDIUM, fd, cluster, &cpg_fd_callbacks);
bail:
if (rc != CS_OK) {
cpg_finalize(handle);
return FALSE;
}
peer = crm_get_peer(id, NULL);
crm_update_peer_proc(__FUNCTION__, peer, crm_proc_cpg, ONLINESTATUS);
return TRUE;
}
gboolean
send_cluster_message_cs(xmlNode * msg, gboolean local, crm_node_t * node, enum crm_ais_msg_types dest)
{
gboolean rc = TRUE;
char *data = NULL;
data = dump_xml_unformatted(msg);
rc = send_cluster_text(crm_class_cluster, data, local, node, dest);
free(data);
return rc;
}
gboolean
send_cluster_text(enum crm_ais_msg_class msg_class, const char *data,
gboolean local, crm_node_t *node, enum crm_ais_msg_types dest)
{
static int msg_id = 0;
static int local_pid = 0;
static int local_name_len = 0;
static const char *local_name = NULL;
char *target = NULL;
struct iovec *iov;
AIS_Message *msg = NULL;
enum crm_ais_msg_types sender = text2msg_type(crm_system_name);
switch (msg_class) {
case crm_class_cluster:
break;
default:
crm_err("Invalid message class: %d", msg_class);
return FALSE;
}
CRM_CHECK(dest != crm_msg_ais, return FALSE);
if(local_name == NULL) {
local_name = get_local_node_name();
}
if(local_name_len == 0 && local_name) {
local_name_len = strlen(local_name);
}
if (data == NULL) {
data = "";
}
if (local_pid == 0) {
local_pid = getpid();
}
if (sender == crm_msg_none) {
sender = local_pid;
}
msg = calloc(1, sizeof(AIS_Message));
msg_id++;
msg->id = msg_id;
msg->header.id = msg_class;
msg->header.error = CS_OK;
msg->host.type = dest;
msg->host.local = local;
if (node) {
if (node->uname) {
target = strdup(node->uname);
msg->host.size = strlen(node->uname);
memset(msg->host.uname, 0, MAX_NAME);
memcpy(msg->host.uname, node->uname, msg->host.size);
} else {
target = crm_strdup_printf("%u", node->id);
}
msg->host.id = node->id;
} else {
target = strdup("all");
}
msg->sender.id = 0;
msg->sender.type = sender;
msg->sender.pid = local_pid;
msg->sender.size = local_name_len;
memset(msg->sender.uname, 0, MAX_NAME);
if(local_name && msg->sender.size) {
memcpy(msg->sender.uname, local_name, msg->sender.size);
}
msg->size = 1 + strlen(data);
msg->header.size = sizeof(AIS_Message) + msg->size;
if (msg->size < CRM_BZ2_THRESHOLD) {
msg = realloc_safe(msg, msg->header.size);
memcpy(msg->data, data, msg->size);
} else {
char *compressed = NULL;
unsigned int new_size = 0;
char *uncompressed = strdup(data);
if (crm_compress_string(uncompressed, msg->size, 0, &compressed, &new_size)) {
msg->header.size = sizeof(AIS_Message) + new_size;
msg = realloc_safe(msg, msg->header.size);
memcpy(msg->data, compressed, new_size);
msg->is_compressed = TRUE;
msg->compressed_size = new_size;
} else {
msg = realloc_safe(msg, msg->header.size);
memcpy(msg->data, data, msg->size);
}
free(uncompressed);
free(compressed);
}
iov = calloc(1, sizeof(struct iovec));
iov->iov_base = msg;
iov->iov_len = msg->header.size;
if (msg->compressed_size) {
crm_trace("Queueing CPG message %u to %s (%llu bytes, %d bytes compressed payload): %.200s",
msg->id, target, (unsigned long long) iov->iov_len,
msg->compressed_size, data);
} else {
crm_trace("Queueing CPG message %u to %s (%llu bytes, %d bytes payload): %.200s",
msg->id, target, (unsigned long long) iov->iov_len,
msg->size, data);
}
free(target);
send_cpg_iov(iov);
return TRUE;
}
enum crm_ais_msg_types
text2msg_type(const char *text)
{
int type = crm_msg_none;
CRM_CHECK(text != NULL, return type);
+ text = pcmk_message_name(text);
if (safe_str_eq(text, "ais")) {
type = crm_msg_ais;
} else if (safe_str_eq(text, CRM_SYSTEM_CIB)) {
type = crm_msg_cib;
- } else if (safe_str_eq(text, CRM_SYSTEM_CRMD)) {
- type = crm_msg_crmd;
- } else if (safe_str_eq(text, CRM_SYSTEM_DC)) {
+ } else if (safe_str_eq(text, CRM_SYSTEM_CRMD)
+ || safe_str_eq(text, CRM_SYSTEM_DC)) {
type = crm_msg_crmd;
} else if (safe_str_eq(text, CRM_SYSTEM_TENGINE)) {
type = crm_msg_te;
} else if (safe_str_eq(text, CRM_SYSTEM_PENGINE)) {
type = crm_msg_pe;
} else if (safe_str_eq(text, CRM_SYSTEM_LRMD)) {
type = crm_msg_lrmd;
} else if (safe_str_eq(text, CRM_SYSTEM_STONITHD)) {
type = crm_msg_stonithd;
} else if (safe_str_eq(text, "stonith-ng")) {
type = crm_msg_stonith_ng;
} else if (safe_str_eq(text, "attrd")) {
type = crm_msg_attrd;
} else {
/* This will normally be a transient client rather than
* a cluster daemon. Set the type to the pid of the client
*/
int scan_rc = sscanf(text, "%d", &type);
if (scan_rc != 1 || type <= crm_msg_stonith_ng) {
/* Ensure it's sane */
type = crm_msg_none;
}
}
return type;
}
diff --git a/lib/common/utils.c b/lib/common/utils.c
index 61c8bef9ac..a67e58a262 100644
--- a/lib/common/utils.c
+++ b/lib/common/utils.c
@@ -1,1353 +1,1394 @@
/*
* Copyright 2004-2018 Andrew Beekhof <andrew@beekhof.net>
*
* This source code is licensed under the GNU Lesser General Public License
* version 2.1 or later (LGPLv2.1+) WITHOUT ANY WARRANTY.
*/
#include <crm_internal.h>
#include <dlfcn.h>
#ifndef _GNU_SOURCE
# define _GNU_SOURCE
#endif
#include <sys/types.h>
#include <sys/wait.h>
#include <sys/stat.h>
#include <sys/utsname.h>
#include <stdio.h>
#include <unistd.h>
#include <string.h>
#include <stdlib.h>
#include <limits.h>
#include <pwd.h>
#include <time.h>
#include <libgen.h>
#include <signal.h>
#include <qb/qbdefs.h>
#include <crm/crm.h>
#include <crm/services.h>
#include <crm/msg_xml.h>
#include <crm/cib/internal.h>
#include <crm/common/xml.h>
#include <crm/common/util.h>
#include <crm/common/ipc.h>
#include <crm/common/iso8601.h>
#include <crm/common/mainloop.h>
#include <libxml2/libxml/relaxng.h>
#ifndef MAXLINE
# define MAXLINE 512
#endif
#ifdef HAVE_GETOPT_H
# include <getopt.h>
#endif
#ifndef PW_BUFFER_LEN
# define PW_BUFFER_LEN 500
#endif
CRM_TRACE_INIT_DATA(common);
gboolean crm_config_error = FALSE;
gboolean crm_config_warning = FALSE;
char *crm_system_name = NULL;
int node_score_red = 0;
int node_score_green = 0;
int node_score_yellow = 0;
static struct crm_option *crm_long_options = NULL;
static const char *crm_app_description = NULL;
static char *crm_short_options = NULL;
static const char *crm_app_usage = NULL;
gboolean
check_time(const char *value)
{
if (crm_get_msec(value) < 5000) {
return FALSE;
}
return TRUE;
}
gboolean
check_timer(const char *value)
{
if (crm_get_msec(value) < 0) {
return FALSE;
}
return TRUE;
}
gboolean
check_boolean(const char *value)
{
int tmp = FALSE;
if (crm_str_to_boolean(value, &tmp) != 1) {
return FALSE;
}
return TRUE;
}
gboolean
check_number(const char *value)
{
errno = 0;
if (value == NULL) {
return FALSE;
} else if (safe_str_eq(value, CRM_MINUS_INFINITY_S)) {
} else if (safe_str_eq(value, CRM_INFINITY_S)) {
} else {
crm_int_helper(value, NULL);
}
if (errno != 0) {
return FALSE;
}
return TRUE;
}
gboolean
check_positive_number(const char* value)
{
if (safe_str_eq(value, CRM_INFINITY_S) || (crm_int_helper(value, NULL))) {
return TRUE;
}
return FALSE;
}
gboolean
check_quorum(const char *value)
{
if (safe_str_eq(value, "stop")) {
return TRUE;
} else if (safe_str_eq(value, "freeze")) {
return TRUE;
} else if (safe_str_eq(value, "ignore")) {
return TRUE;
} else if (safe_str_eq(value, "suicide")) {
return TRUE;
}
return FALSE;
}
gboolean
check_script(const char *value)
{
struct stat st;
if(safe_str_eq(value, "/dev/null")) {
return TRUE;
}
if(stat(value, &st) != 0) {
crm_err("Script %s does not exist", value);
return FALSE;
}
if(S_ISREG(st.st_mode) == 0) {
crm_err("Script %s is not a regular file", value);
return FALSE;
}
if( (st.st_mode & (S_IXUSR | S_IXGRP )) == 0) {
crm_err("Script %s is not executable", value);
return FALSE;
}
return TRUE;
}
gboolean
check_utilization(const char *value)
{
char *end = NULL;
long number = strtol(value, &end, 10);
if(end && end[0] != '%') {
return FALSE;
} else if(number < 0) {
return FALSE;
}
return TRUE;
}
void
crm_args_fini()
{
free(crm_short_options);
crm_short_options = NULL;
}
int
char2score(const char *score)
{
int score_f = 0;
if (score == NULL) {
} else if (safe_str_eq(score, CRM_MINUS_INFINITY_S)) {
score_f = -CRM_SCORE_INFINITY;
} else if (safe_str_eq(score, CRM_INFINITY_S)) {
score_f = CRM_SCORE_INFINITY;
} else if (safe_str_eq(score, CRM_PLUS_INFINITY_S)) {
score_f = CRM_SCORE_INFINITY;
} else if (safe_str_eq(score, "red")) {
score_f = node_score_red;
} else if (safe_str_eq(score, "yellow")) {
score_f = node_score_yellow;
} else if (safe_str_eq(score, "green")) {
score_f = node_score_green;
} else {
score_f = crm_parse_int(score, NULL);
if (score_f > 0 && score_f > CRM_SCORE_INFINITY) {
score_f = CRM_SCORE_INFINITY;
} else if (score_f < 0 && score_f < -CRM_SCORE_INFINITY) {
score_f = -CRM_SCORE_INFINITY;
}
}
return score_f;
}
char *
score2char_stack(int score, char *buf, size_t len)
{
if (score >= CRM_SCORE_INFINITY) {
strncpy(buf, CRM_INFINITY_S, 9);
} else if (score <= -CRM_SCORE_INFINITY) {
strncpy(buf, CRM_MINUS_INFINITY_S , 10);
} else {
return crm_itoa_stack(score, buf, len);
}
return buf;
}
char *
score2char(int score)
{
if (score >= CRM_SCORE_INFINITY) {
return strdup(CRM_INFINITY_S);
} else if (score <= -CRM_SCORE_INFINITY) {
return strdup(CRM_MINUS_INFINITY_S);
}
return crm_itoa(score);
}
const char *
cluster_option(GHashTable * options, gboolean(*validate) (const char *),
const char *name, const char *old_name, const char *def_value)
{
const char *value = NULL;
char *new_value = NULL;
CRM_ASSERT(name != NULL);
if (options) {
value = g_hash_table_lookup(options, name);
if ((value == NULL) && old_name) {
value = g_hash_table_lookup(options, old_name);
if (value != NULL) {
crm_config_warn("Support for legacy name '%s' for cluster option '%s'"
" is deprecated and will be removed in a future release",
old_name, name);
// Inserting copy with current name ensures we only warn once
new_value = strdup(value);
g_hash_table_insert(options, strdup(name), new_value);
value = new_value;
}
}
if (value && validate && (validate(value) == FALSE)) {
crm_config_err("Resetting cluster option '%s' to default: value '%s' is invalid",
name, value);
value = NULL;
}
if (value) {
return value;
}
}
// No value found, use default
value = def_value;
if (value == NULL) {
crm_trace("No value or default provided for cluster option '%s'",
name);
return NULL;
}
if (validate) {
CRM_CHECK(validate(value) != FALSE,
crm_err("Bug: default value for cluster option '%s' is invalid", name);
return NULL);
}
crm_trace("Using default value '%s' for cluster option '%s'",
value, name);
if (options) {
new_value = strdup(value);
g_hash_table_insert(options, strdup(name), new_value);
value = new_value;
}
return value;
}
const char *
get_cluster_pref(GHashTable * options, pe_cluster_option * option_list, int len, const char *name)
{
const char *value = NULL;
for (int lpc = 0; lpc < len; lpc++) {
if (safe_str_eq(name, option_list[lpc].name)) {
value = cluster_option(options,
option_list[lpc].is_valid,
option_list[lpc].name,
option_list[lpc].alt_name,
option_list[lpc].default_value);
return value;
}
}
CRM_CHECK(FALSE, crm_err("Bug: looking for unknown option '%s'", name));
return NULL;
}
void
config_metadata(const char *name, const char *version, const char *desc_short,
const char *desc_long, pe_cluster_option * option_list, int len)
{
int lpc = 0;
fprintf(stdout, "<?xml version=\"1.0\"?>"
"<!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\">\n"
"<resource-agent name=\"%s\">\n"
" <version>%s</version>\n"
" <longdesc lang=\"en\">%s</longdesc>\n"
" <shortdesc lang=\"en\">%s</shortdesc>\n"
" <parameters>\n", name, version, desc_long, desc_short);
for (lpc = 0; lpc < len; lpc++) {
if (option_list[lpc].description_long == NULL && option_list[lpc].description_short == NULL) {
continue;
}
fprintf(stdout, " <parameter name=\"%s\" unique=\"0\">\n"
" <shortdesc lang=\"en\">%s</shortdesc>\n"
" <content type=\"%s\" default=\"%s\"/>\n"
" <longdesc lang=\"en\">%s%s%s</longdesc>\n"
" </parameter>\n",
option_list[lpc].name,
option_list[lpc].description_short,
option_list[lpc].type,
option_list[lpc].default_value,
option_list[lpc].description_long ? option_list[lpc].
description_long : option_list[lpc].description_short,
option_list[lpc].values ? " Allowed values: " : "",
option_list[lpc].values ? option_list[lpc].values : "");
}
fprintf(stdout, " </parameters>\n</resource-agent>\n");
}
void
verify_all_options(GHashTable * options, pe_cluster_option * option_list, int len)
{
int lpc = 0;
for (lpc = 0; lpc < len; lpc++) {
cluster_option(options,
option_list[lpc].is_valid,
option_list[lpc].name,
option_list[lpc].alt_name, option_list[lpc].default_value);
}
}
char *
generate_hash_key(const char *crm_msg_reference, const char *sys)
{
char *hash_key = crm_concat(sys ? sys : "none", crm_msg_reference, '_');
crm_trace("created hash key: (%s)", hash_key);
return hash_key;
}
int
crm_user_lookup(const char *name, uid_t * uid, gid_t * gid)
{
int rc = pcmk_ok;
char *buffer = NULL;
struct passwd pwd;
struct passwd *pwentry = NULL;
buffer = calloc(1, PW_BUFFER_LEN);
rc = getpwnam_r(name, &pwd, buffer, PW_BUFFER_LEN, &pwentry);
if (pwentry) {
if (uid) {
*uid = pwentry->pw_uid;
}
if (gid) {
*gid = pwentry->pw_gid;
}
crm_trace("User %s has uid=%d gid=%d", name, pwentry->pw_uid, pwentry->pw_gid);
} else {
rc = rc? -rc : -EINVAL;
crm_info("User %s lookup: %s", name, pcmk_strerror(rc));
}
free(buffer);
return rc;
}
static int
crm_version_helper(const char *text, char **end_text)
{
int atoi_result = -1;
CRM_ASSERT(end_text != NULL);
errno = 0;
if (text != NULL && text[0] != 0) {
atoi_result = (int)strtol(text, end_text, 10);
if (errno == EINVAL) {
crm_err("Conversion of '%s' %c failed", text, text[0]);
atoi_result = -1;
}
}
return atoi_result;
}
/*
* version1 < version2 : -1
* version1 = version2 : 0
* version1 > version2 : 1
*/
int
compare_version(const char *version1, const char *version2)
{
int rc = 0;
int lpc = 0;
char *ver1_copy = NULL, *ver2_copy = NULL;
char *rest1 = NULL, *rest2 = NULL;
if (version1 == NULL && version2 == NULL) {
return 0;
} else if (version1 == NULL) {
return -1;
} else if (version2 == NULL) {
return 1;
}
ver1_copy = strdup(version1);
ver2_copy = strdup(version2);
rest1 = ver1_copy;
rest2 = ver2_copy;
while (1) {
int digit1 = 0;
int digit2 = 0;
lpc++;
if (rest1 == rest2) {
break;
}
if (rest1 != NULL) {
digit1 = crm_version_helper(rest1, &rest1);
}
if (rest2 != NULL) {
digit2 = crm_version_helper(rest2, &rest2);
}
if (digit1 < digit2) {
rc = -1;
break;
} else if (digit1 > digit2) {
rc = 1;
break;
}
if (rest1 != NULL && rest1[0] == '.') {
rest1++;
}
if (rest1 != NULL && rest1[0] == 0) {
rest1 = NULL;
}
if (rest2 != NULL && rest2[0] == '.') {
rest2++;
}
if (rest2 != NULL && rest2[0] == 0) {
rest2 = NULL;
}
}
free(ver1_copy);
free(ver2_copy);
if (rc == 0) {
crm_trace("%s == %s (%d)", version1, version2, lpc);
} else if (rc < 0) {
crm_trace("%s < %s (%d)", version1, version2, lpc);
} else if (rc > 0) {
crm_trace("%s > %s (%d)", version1, version2, lpc);
}
return rc;
}
gboolean do_stderr = FALSE;
#ifndef NUMCHARS
# define NUMCHARS "0123456789."
#endif
#ifndef WHITESPACE
# define WHITESPACE " \t\n\r\f"
#endif
guint
crm_parse_interval_spec(const char *input)
{
long long msec = 0;
if (input == NULL) {
return 0;
} else if (input[0] != 'P') {
long long tmp = crm_get_msec(input);
if(tmp > 0) {
msec = tmp;
}
} else {
crm_time_t *period_s = crm_time_parse_duration(input);
msec = 1000 * crm_time_get_seconds(period_s);
crm_time_free(period_s);
}
return (msec <= 0)? 0 : ((msec >= G_MAXUINT)? G_MAXUINT : (guint) msec);
}
long long
crm_get_msec(const char *input)
{
const char *cp = input;
const char *units;
long long multiplier = 1000;
long long divisor = 1;
long long msec = -1;
char *end_text = NULL;
/* double dret; */
if (input == NULL) {
return msec;
}
cp += strspn(cp, WHITESPACE);
units = cp + strspn(cp, NUMCHARS);
units += strspn(units, WHITESPACE);
if (strchr(NUMCHARS, *cp) == NULL) {
return msec;
}
if (strncasecmp(units, "ms", 2) == 0 || strncasecmp(units, "msec", 4) == 0) {
multiplier = 1;
divisor = 1;
} else if (strncasecmp(units, "us", 2) == 0 || strncasecmp(units, "usec", 4) == 0) {
multiplier = 1;
divisor = 1000;
} else if (strncasecmp(units, "s", 1) == 0 || strncasecmp(units, "sec", 3) == 0) {
multiplier = 1000;
divisor = 1;
} else if (strncasecmp(units, "m", 1) == 0 || strncasecmp(units, "min", 3) == 0) {
multiplier = 60 * 1000;
divisor = 1;
} else if (strncasecmp(units, "h", 1) == 0 || strncasecmp(units, "hr", 2) == 0) {
multiplier = 60 * 60 * 1000;
divisor = 1;
} else if (*units != EOS && *units != '\n' && *units != '\r') {
return msec;
}
msec = crm_int_helper(cp, &end_text);
if (msec > LLONG_MAX/multiplier) {
/* arithmetics overflow while multiplier/divisor mutually exclusive */
return LLONG_MAX;
}
msec *= multiplier;
msec /= divisor;
/* dret += 0.5; */
/* msec = (long long)dret; */
return msec;
}
extern bool crm_is_daemon;
/* coverity[+kill] */
void
crm_abort(const char *file, const char *function, int line,
const char *assert_condition, gboolean do_core, gboolean do_fork)
{
int rc = 0;
int pid = 0;
int status = 0;
/* Implied by the parent's error logging below */
/* crm_write_blackbox(0); */
if(crm_is_daemon == FALSE) {
/* This is a command line tool - do not fork */
/* crm_add_logfile(NULL); * Record it to a file? */
crm_enable_stderr(TRUE); /* Make sure stderr is enabled so we can tell the caller */
do_fork = FALSE; /* Just crash if needed */
}
if (do_core == FALSE) {
crm_err("%s: Triggered assert at %s:%d : %s", function, file, line, assert_condition);
return;
} else if (do_fork) {
pid = fork();
} else {
crm_err("%s: Triggered fatal assert at %s:%d : %s", function, file, line, assert_condition);
}
if (pid == -1) {
crm_crit("%s: Cannot create core for non-fatal assert at %s:%d : %s",
function, file, line, assert_condition);
return;
} else if(pid == 0) {
/* Child process */
abort();
return;
}
/* Parent process */
crm_err("%s: Forked child %d to record non-fatal assert at %s:%d : %s",
function, pid, file, line, assert_condition);
crm_write_blackbox(SIGTRAP, NULL);
do {
rc = waitpid(pid, &status, 0);
if(rc == pid) {
return; /* Job done */
}
} while(errno == EINTR);
if (errno == ECHILD) {
/* crm_mon does this */
crm_trace("Cannot wait on forked child %d - SIGCHLD is probably set to SIG_IGN", pid);
return;
}
crm_perror(LOG_ERR, "Cannot wait on forked child %d", pid);
}
void
crm_make_daemon(const char *name, gboolean daemonize, const char *pidfile)
{
int rc;
long pid;
const char *devnull = "/dev/null";
if (daemonize == FALSE) {
return;
}
/* Check before we even try... */
rc = crm_pidfile_inuse(pidfile, 1, name);
if(rc < pcmk_ok && rc != -ENOENT) {
pid = crm_read_pidfile(pidfile);
crm_err("%s: already running [pid %ld in %s]", name, pid, pidfile);
printf("%s: already running [pid %ld in %s]\n", name, pid, pidfile);
crm_exit(CRM_EX_ERROR);
}
pid = fork();
if (pid < 0) {
fprintf(stderr, "%s: could not start daemon\n", name);
crm_perror(LOG_ERR, "fork");
crm_exit(CRM_EX_OSERR);
} else if (pid > 0) {
crm_exit(CRM_EX_OK);
}
rc = crm_lock_pidfile(pidfile, name);
if(rc < pcmk_ok) {
crm_err("Could not lock '%s' for %s: %s (%d)", pidfile, name, pcmk_strerror(rc), rc);
printf("Could not lock '%s' for %s: %s (%d)\n", pidfile, name, pcmk_strerror(rc), rc);
crm_exit(CRM_EX_ERROR);
}
umask(S_IWGRP | S_IWOTH | S_IROTH);
close(STDIN_FILENO);
(void)open(devnull, O_RDONLY); /* Stdin: fd 0 */
close(STDOUT_FILENO);
(void)open(devnull, O_WRONLY); /* Stdout: fd 1 */
close(STDERR_FILENO);
(void)open(devnull, O_WRONLY); /* Stderr: fd 2 */
}
char *
crm_meta_name(const char *field)
{
int lpc = 0;
int max = 0;
char *crm_name = NULL;
CRM_CHECK(field != NULL, return NULL);
crm_name = crm_concat(CRM_META, field, '_');
/* Massage the names so they can be used as shell variables */
max = strlen(crm_name);
for (; lpc < max; lpc++) {
switch (crm_name[lpc]) {
case '-':
crm_name[lpc] = '_';
break;
}
}
return crm_name;
}
const char *
crm_meta_value(GHashTable * hash, const char *field)
{
char *key = NULL;
const char *value = NULL;
key = crm_meta_name(field);
if (key) {
value = g_hash_table_lookup(hash, key);
free(key);
}
return value;
}
static struct option *
crm_create_long_opts(struct crm_option *long_options)
{
struct option *long_opts = NULL;
#ifdef HAVE_GETOPT_H
int index = 0, lpc = 0;
/*
* A previous, possibly poor, choice of '?' as the short form of --help
* means that getopt_long() returns '?' for both --help and for "unknown option"
*
* This dummy entry allows us to differentiate between the two in crm_get_option()
* and exit with the correct error code
*/
long_opts = realloc_safe(long_opts, (index + 1) * sizeof(struct option));
long_opts[index].name = "__dummmy__";
long_opts[index].has_arg = 0;
long_opts[index].flag = 0;
long_opts[index].val = '_';
index++;
for (lpc = 0; long_options[lpc].name != NULL; lpc++) {
if (long_options[lpc].name[0] == '-') {
continue;
}
long_opts = realloc_safe(long_opts, (index + 1) * sizeof(struct option));
/*fprintf(stderr, "Creating %d %s = %c\n", index,
* long_options[lpc].name, long_options[lpc].val); */
long_opts[index].name = long_options[lpc].name;
long_opts[index].has_arg = long_options[lpc].has_arg;
long_opts[index].flag = long_options[lpc].flag;
long_opts[index].val = long_options[lpc].val;
index++;
}
/* Now create the list terminator */
long_opts = realloc_safe(long_opts, (index + 1) * sizeof(struct option));
long_opts[index].name = NULL;
long_opts[index].has_arg = 0;
long_opts[index].flag = 0;
long_opts[index].val = 0;
#endif
return long_opts;
}
void
crm_set_options(const char *short_options, const char *app_usage, struct crm_option *long_options,
const char *app_desc)
{
if (short_options) {
crm_short_options = strdup(short_options);
} else if (long_options) {
int lpc = 0;
int opt_string_len = 0;
char *local_short_options = NULL;
for (lpc = 0; long_options[lpc].name != NULL; lpc++) {
if (long_options[lpc].val && long_options[lpc].val != '-' && long_options[lpc].val < UCHAR_MAX) {
local_short_options = realloc_safe(local_short_options, opt_string_len + 4);
local_short_options[opt_string_len++] = long_options[lpc].val;
/* getopt(3) says: Two colons mean an option takes an optional arg; */
if (long_options[lpc].has_arg == optional_argument) {
local_short_options[opt_string_len++] = ':';
}
if (long_options[lpc].has_arg >= required_argument) {
local_short_options[opt_string_len++] = ':';
}
local_short_options[opt_string_len] = 0;
}
}
crm_short_options = local_short_options;
crm_trace("Generated short option string: '%s'", local_short_options);
}
if (long_options) {
crm_long_options = long_options;
}
if (app_desc) {
crm_app_description = app_desc;
}
if (app_usage) {
crm_app_usage = app_usage;
}
}
int
crm_get_option(int argc, char **argv, int *index)
{
return crm_get_option_long(argc, argv, index, NULL);
}
int
crm_get_option_long(int argc, char **argv, int *index, const char **longname)
{
#ifdef HAVE_GETOPT_H
static struct option *long_opts = NULL;
if (long_opts == NULL && crm_long_options) {
long_opts = crm_create_long_opts(crm_long_options);
}
*index = 0;
if (long_opts) {
int flag = getopt_long(argc, argv, crm_short_options, long_opts, index);
switch (flag) {
case 0:
if (long_opts[*index].val) {
return long_opts[*index].val;
} else if (longname) {
*longname = long_opts[*index].name;
} else {
crm_notice("Unhandled option --%s", long_opts[*index].name);
return flag;
}
case -1: /* End of option processing */
break;
case ':':
crm_trace("Missing argument");
crm_help('?', CRM_EX_USAGE);
break;
case '?':
crm_help('?', (*index? CRM_EX_OK : CRM_EX_USAGE));
break;
}
return flag;
}
#endif
if (crm_short_options) {
return getopt(argc, argv, crm_short_options);
}
return -1;
}
crm_exit_t
crm_help(char cmd, crm_exit_t exit_code)
{
int i = 0;
FILE *stream = (exit_code ? stderr : stdout);
if (cmd == 'v' || cmd == '$') {
fprintf(stream, "Pacemaker %s\n", PACEMAKER_VERSION);
fprintf(stream, "Written by Andrew Beekhof\n");
goto out;
}
if (cmd == '!') {
fprintf(stream, "Pacemaker %s (Build: %s): %s\n", PACEMAKER_VERSION, BUILD_VERSION, CRM_FEATURES);
goto out;
}
fprintf(stream, "%s - %s\n", crm_system_name, crm_app_description);
if (crm_app_usage) {
fprintf(stream, "Usage: %s %s\n", crm_system_name, crm_app_usage);
}
if (crm_long_options) {
fprintf(stream, "Options:\n");
for (i = 0; crm_long_options[i].name != NULL; i++) {
if (crm_long_options[i].flags & pcmk_option_hidden) {
} else if (crm_long_options[i].flags & pcmk_option_paragraph) {
fprintf(stream, "%s\n\n", crm_long_options[i].desc);
} else if (crm_long_options[i].flags & pcmk_option_example) {
fprintf(stream, "\t#%s\n\n", crm_long_options[i].desc);
} else if (crm_long_options[i].val == '-' && crm_long_options[i].desc) {
fprintf(stream, "%s\n", crm_long_options[i].desc);
} else {
/* is val printable as char ? */
if (crm_long_options[i].val && crm_long_options[i].val <= UCHAR_MAX) {
fprintf(stream, " -%c,", crm_long_options[i].val);
} else {
fputs(" ", stream);
}
fprintf(stream, " --%s%s\t%s\n", crm_long_options[i].name,
crm_long_options[i].has_arg == optional_argument ? "[=value]" :
crm_long_options[i].has_arg == required_argument ? "=value" : "",
crm_long_options[i].desc ? crm_long_options[i].desc : "");
}
}
} else if (crm_short_options) {
fprintf(stream, "Usage: %s - %s\n", crm_system_name, crm_app_description);
for (i = 0; crm_short_options[i] != 0; i++) {
int has_arg = no_argument /* 0 */;
if (crm_short_options[i + 1] == ':') {
if (crm_short_options[i + 2] == ':')
has_arg = optional_argument /* 2 */;
else
has_arg = required_argument /* 1 */;
}
fprintf(stream, " -%c %s\n", crm_short_options[i],
has_arg == optional_argument ? "[value]" :
has_arg == required_argument ? "{value}" : "");
i += has_arg;
}
}
fprintf(stream, "\nReport bugs to %s\n", PACKAGE_BUGREPORT);
out:
return crm_exit(exit_code);
}
void cib_ipc_servers_init(qb_ipcs_service_t **ipcs_ro,
qb_ipcs_service_t **ipcs_rw,
qb_ipcs_service_t **ipcs_shm,
struct qb_ipcs_service_handlers *ro_cb,
struct qb_ipcs_service_handlers *rw_cb)
{
*ipcs_ro = mainloop_add_ipc_server(cib_channel_ro, QB_IPC_NATIVE, ro_cb);
*ipcs_rw = mainloop_add_ipc_server(cib_channel_rw, QB_IPC_NATIVE, rw_cb);
*ipcs_shm = mainloop_add_ipc_server(cib_channel_shm, QB_IPC_SHM, rw_cb);
if (*ipcs_ro == NULL || *ipcs_rw == NULL || *ipcs_shm == NULL) {
crm_err("Failed to create the CIB manager: exiting and inhibiting respawn");
crm_warn("Verify pacemaker and pacemaker_remote are not both enabled");
crm_exit(CRM_EX_FATAL);
}
}
void cib_ipc_servers_destroy(qb_ipcs_service_t *ipcs_ro,
qb_ipcs_service_t *ipcs_rw,
qb_ipcs_service_t *ipcs_shm)
{
qb_ipcs_destroy(ipcs_ro);
qb_ipcs_destroy(ipcs_rw);
qb_ipcs_destroy(ipcs_shm);
}
qb_ipcs_service_t *
crmd_ipc_server_init(struct qb_ipcs_service_handlers *cb)
{
return mainloop_add_ipc_server(CRM_SYSTEM_CRMD, QB_IPC_NATIVE, cb);
}
void
attrd_ipc_server_init(qb_ipcs_service_t **ipcs, struct qb_ipcs_service_handlers *cb)
{
*ipcs = mainloop_add_ipc_server(T_ATTRD, QB_IPC_NATIVE, cb);
if (*ipcs == NULL) {
crm_err("Failed to create pacemaker-attrd server: exiting and inhibiting respawn");
crm_warn("Verify pacemaker and pacemaker_remote are not both enabled.");
crm_exit(CRM_EX_FATAL);
}
}
void
stonith_ipc_server_init(qb_ipcs_service_t **ipcs, struct qb_ipcs_service_handlers *cb)
{
*ipcs = mainloop_add_ipc_server("stonith-ng", QB_IPC_NATIVE, cb);
if (*ipcs == NULL) {
crm_err("Failed to create fencer: exiting and inhibiting respawn.");
crm_warn("Verify pacemaker and pacemaker_remote are not both enabled.");
crm_exit(CRM_EX_FATAL);
}
}
bool
pcmk_acl_required(const char *user)
{
#if ENABLE_ACL
if(user == NULL || strlen(user) == 0) {
crm_trace("no user set");
return FALSE;
} else if (strcmp(user, CRM_DAEMON_USER) == 0) {
return FALSE;
} else if (strcmp(user, "root") == 0) {
return FALSE;
}
crm_trace("acls required for %s", user);
return TRUE;
#else
crm_trace("acls not supported");
return FALSE;
#endif
}
#if ENABLE_ACL
char *
uid2username(uid_t uid)
{
struct passwd *pwent = getpwuid(uid);
if (pwent == NULL) {
crm_perror(LOG_ERR, "Cannot get password entry of uid: %d", uid);
return NULL;
} else {
return strdup(pwent->pw_name);
}
}
const char *
crm_acl_get_set_user(xmlNode * request, const char *field, const char *peer_user)
{
/* field is only checked for backwards compatibility */
static const char *effective_user = NULL;
const char *requested_user = NULL;
const char *user = NULL;
if(effective_user == NULL) {
effective_user = uid2username(geteuid());
}
requested_user = crm_element_value(request, XML_ACL_TAG_USER);
if(requested_user == NULL) {
requested_user = crm_element_value(request, field);
}
if (is_privileged(effective_user) == FALSE) {
/* We're not running as a privileged user, set or overwrite any existing value for $XML_ACL_TAG_USER */
user = effective_user;
} else if(peer_user == NULL && requested_user == NULL) {
/* No user known or requested, use 'effective_user' and make sure one is set for the request */
user = effective_user;
} else if(peer_user == NULL) {
/* No user known, trusting 'requested_user' */
user = requested_user;
} else if (is_privileged(peer_user) == FALSE) {
/* The peer is not a privileged user, set or overwrite any existing value for $XML_ACL_TAG_USER */
user = peer_user;
} else if (requested_user == NULL) {
/* Even if we're privileged, make sure there is always a value set */
user = peer_user;
} else {
/* Legal delegation to 'requested_user' */
user = requested_user;
}
// This requires pointer comparison, not string comparison
if(user != crm_element_value(request, XML_ACL_TAG_USER)) {
crm_xml_add(request, XML_ACL_TAG_USER, user);
}
if(field != NULL && user != crm_element_value(request, field)) {
crm_xml_add(request, field, user);
}
return requested_user;
}
void
determine_request_user(const char *user, xmlNode * request, const char *field)
{
/* Get our internal validation out of the way first */
CRM_CHECK(user != NULL && request != NULL && field != NULL, return);
/* If our peer is a privileged user, we might be doing something on behalf of someone else */
if (is_privileged(user) == FALSE) {
/* We're not a privileged user, set or overwrite any existing value for $field */
crm_xml_replace(request, field, user);
} else if (crm_element_value(request, field) == NULL) {
/* Even if we're privileged, make sure there is always a value set */
crm_xml_replace(request, field, user);
/* } else { Legal delegation */
}
crm_trace("Processing msg as user '%s'", crm_element_value(request, field));
}
#endif
void *
find_library_function(void **handle, const char *lib, const char *fn, gboolean fatal)
{
char *error;
void *a_function;
if (*handle == NULL) {
*handle = dlopen(lib, RTLD_LAZY);
}
if (!(*handle)) {
crm_err("%sCould not open %s: %s", fatal ? "Fatal: " : "", lib, dlerror());
if (fatal) {
crm_exit(CRM_EX_FATAL);
}
return NULL;
}
a_function = dlsym(*handle, fn);
if (a_function == NULL) {
error = dlerror();
crm_err("%sCould not find %s in %s: %s", fatal ? "Fatal: " : "", fn, lib, error);
if (fatal) {
crm_exit(CRM_EX_FATAL);
}
}
return a_function;
}
void *
convert_const_pointer(const void *ptr)
{
/* Worst function ever */
return (void *)ptr;
}
#ifdef HAVE_UUID_UUID_H
# include <uuid/uuid.h>
#endif
char *
crm_generate_uuid(void)
{
unsigned char uuid[16];
char *buffer = malloc(37); /* Including NUL byte */
uuid_generate(uuid);
uuid_unparse(uuid, buffer);
return buffer;
}
+/*!
+ * \brief Get name to be used as identifier for cluster messages
+ *
+ * \param[in] name Actual system name to check
+ *
+ * \return Non-NULL cluster message identifier corresponding to name
+ *
+ * \note The Pacemaker daemons were renamed in version 2.0.0, but the old names
+ * must continue to be used as the identifier for cluster messages, so
+ * that mixed-version clusters are possible during a rolling upgrade.
+ */
+const char *
+pcmk_message_name(const char *name)
+{
+ if (name == NULL) {
+ return "unknown";
+
+ } else if (!strcmp(name, "pacemaker-attrd")) {
+ return "attrd";
+
+ } else if (!strcmp(name, "pacemaker-based")) {
+ return CRM_SYSTEM_CIB;
+
+ } else if (!strcmp(name, "pacemaker-controld")) {
+ return CRM_SYSTEM_CRMD;
+
+ } else if (!strcmp(name, "pacemaker-execd")) {
+ return CRM_SYSTEM_LRMD;
+
+ } else if (!strcmp(name, "pacemaker-fenced")) {
+ return "stonith-ng";
+
+ } else if (!strcmp(name, "pacemaker-schedulerd")) {
+ return CRM_SYSTEM_PENGINE;
+
+ } else {
+ return name;
+ }
+}
+
/*!
* \brief Check whether a string represents a cluster daemon name
*
* \param[in] name String to check
*
* \return TRUE if name is standard client name used by daemons, FALSE otherwise
*/
bool
crm_is_daemon_name(const char *name)
{
- return (name &&
- (!strcmp(name, CRM_SYSTEM_CRMD)
+ name = pcmk_message_name(name);
+ return (!strcmp(name, CRM_SYSTEM_CRMD)
|| !strcmp(name, CRM_SYSTEM_STONITHD)
- || !strcmp(name, T_ATTRD)
+ || !strcmp(name, "stonith-ng")
+ || !strcmp(name, "attrd")
|| !strcmp(name, CRM_SYSTEM_CIB)
|| !strcmp(name, CRM_SYSTEM_MCP)
|| !strcmp(name, CRM_SYSTEM_DC)
|| !strcmp(name, CRM_SYSTEM_TENGINE)
- || !strcmp(name, CRM_SYSTEM_LRMD)));
+ || !strcmp(name, CRM_SYSTEM_LRMD));
}
#include <md5.h>
char *
crm_md5sum(const char *buffer)
{
int lpc = 0, len = 0;
char *digest = NULL;
unsigned char raw_digest[MD5_DIGEST_SIZE];
if (buffer == NULL) {
buffer = "";
}
len = strlen(buffer);
crm_trace("Beginning digest of %d bytes", len);
digest = malloc(2 * MD5_DIGEST_SIZE + 1);
if(digest) {
md5_buffer(buffer, len, raw_digest);
for (lpc = 0; lpc < MD5_DIGEST_SIZE; lpc++) {
sprintf(digest + (2 * lpc), "%02x", raw_digest[lpc]);
}
digest[(2 * MD5_DIGEST_SIZE)] = 0;
crm_trace("Digest %s.", digest);
} else {
crm_err("Could not create digest");
}
return digest;
}
#ifdef HAVE_GNUTLS_GNUTLS_H
void
crm_gnutls_global_init(void)
{
signal(SIGPIPE, SIG_IGN);
gnutls_global_init();
}
#endif
char *
crm_generate_ra_key(const char *standard, const char *provider, const char *type)
{
if (!standard && !provider && !type) {
return NULL;
}
return crm_strdup_printf("%s%s%s:%s",
(standard? standard : ""),
(provider? ":" : ""), (provider? provider : ""),
(type? type : ""));
}
/*!
* \brief Check whether a resource standard requires a provider to be specified
*
* \param[in] standard Standard name
*
* \return TRUE if standard requires a provider, FALSE otherwise
*/
bool
crm_provider_required(const char *standard)
{
CRM_CHECK(standard != NULL, return FALSE);
/* @TODO
* - this should probably be case-sensitive, but isn't,
* for backward compatibility
* - it might be nice to keep standards' capabilities (supports provider,
* can be promotable, etc.) as structured data somewhere
*/
if (!strcasecmp(standard, PCMK_RESOURCE_CLASS_OCF)) {
return TRUE;
}
return FALSE;
}
/*!
* \brief Parse a "standard[:provider]:type" agent specification
*
* \param[in] spec Agent specification
* \param[out] standard Newly allocated memory containing agent standard (or NULL)
* \param[out] provider Newly allocated memory containing agent provider (or NULL)
* \param[put] type Newly allocated memory containing agent type (or NULL)
*
* \return pcmk_ok if the string could be parsed, -EINVAL otherwise
*
* \note It is acceptable for the type to contain a ':' if the standard supports
* that. For example, systemd supports the form "systemd:UNIT@A:B".
* \note It is the caller's responsibility to free the returned values.
*/
int
crm_parse_agent_spec(const char *spec, char **standard, char **provider,
char **type)
{
char *colon;
CRM_CHECK(spec && standard && provider && type, return -EINVAL);
*standard = NULL;
*provider = NULL;
*type = NULL;
colon = strchr(spec, ':');
if ((colon == NULL) || (colon == spec)) {
return -EINVAL;
}
*standard = strndup(spec, colon - spec);
spec = colon + 1;
if (crm_provider_required(*standard)) {
colon = strchr(spec, ':');
if ((colon == NULL) || (colon == spec)) {
free(*standard);
return -EINVAL;
}
*provider = strndup(spec, colon - spec);
spec = colon + 1;
}
if (*spec == '\0') {
free(*standard);
free(*provider);
return -EINVAL;
}
*type = strdup(spec);
return pcmk_ok;
}
diff --git a/lib/lrmd/proxy_common.c b/lib/lrmd/proxy_common.c
index 41c0cce9fd..cd3bb26301 100644
--- a/lib/lrmd/proxy_common.c
+++ b/lib/lrmd/proxy_common.c
@@ -1,308 +1,308 @@
/*
* Copyright 2015-2018 David Vossel <davidvossel@gmail.com>
*
* This source code is licensed under the GNU Lesser General Public License
* version 2.1 or later (LGPLv2.1+) WITHOUT ANY WARRANTY.
*/
#include <crm_internal.h>
#include <glib.h>
#include <unistd.h>
#include <crm/crm.h>
#include <crm/msg_xml.h>
#include <crm/services.h>
#include <crm/common/mainloop.h>
#include <crm/pengine/status.h>
#include <crm/cib.h>
#include <crm/lrmd.h>
int lrmd_internal_proxy_send(lrmd_t * lrmd, xmlNode *msg);
GHashTable *proxy_table = NULL;
static void
remote_proxy_notify_destroy(lrmd_t *lrmd, const char *session_id)
{
/* sending to the remote node that an ipc connection has been destroyed */
xmlNode *msg = create_xml_node(NULL, T_LRMD_IPC_PROXY);
crm_xml_add(msg, F_LRMD_IPC_OP, LRMD_IPC_OP_DESTROY);
crm_xml_add(msg, F_LRMD_IPC_SESSION, session_id);
lrmd_internal_proxy_send(lrmd, msg);
free_xml(msg);
}
/*!
* \brief Send an acknowledgment of a remote proxy shutdown request.
*
* \param[in] lrmd Connection to proxy
*/
void
remote_proxy_ack_shutdown(lrmd_t *lrmd)
{
xmlNode *msg = create_xml_node(NULL, T_LRMD_IPC_PROXY);
crm_xml_add(msg, F_LRMD_IPC_OP, LRMD_IPC_OP_SHUTDOWN_ACK);
lrmd_internal_proxy_send(lrmd, msg);
free_xml(msg);
}
/*!
* \brief We're not going to shutdown as response to
* a remote proxy shutdown request.
*
* \param[in] lrmd Connection to proxy
*/
void
remote_proxy_nack_shutdown(lrmd_t *lrmd)
{
xmlNode *msg = create_xml_node(NULL, T_LRMD_IPC_PROXY);
crm_xml_add(msg, F_LRMD_IPC_OP, LRMD_IPC_OP_SHUTDOWN_NACK);
lrmd_internal_proxy_send(lrmd, msg);
free_xml(msg);
}
void
remote_proxy_relay_event(remote_proxy_t *proxy, xmlNode *msg)
{
/* sending to the remote node an event msg. */
xmlNode *event = create_xml_node(NULL, T_LRMD_IPC_PROXY);
crm_xml_add(event, F_LRMD_IPC_OP, LRMD_IPC_OP_EVENT);
crm_xml_add(event, F_LRMD_IPC_SESSION, proxy->session_id);
add_message_xml(event, F_LRMD_IPC_MSG, msg);
crm_log_xml_explicit(event, "EventForProxy");
lrmd_internal_proxy_send(proxy->lrm, event);
free_xml(event);
}
void
remote_proxy_relay_response(remote_proxy_t *proxy, xmlNode *msg, int msg_id)
{
/* sending to the remote node a response msg. */
xmlNode *response = create_xml_node(NULL, T_LRMD_IPC_PROXY);
crm_xml_add(response, F_LRMD_IPC_OP, LRMD_IPC_OP_RESPONSE);
crm_xml_add(response, F_LRMD_IPC_SESSION, proxy->session_id);
crm_xml_add_int(response, F_LRMD_IPC_MSG_ID, msg_id);
add_message_xml(response, F_LRMD_IPC_MSG, msg);
lrmd_internal_proxy_send(proxy->lrm, response);
free_xml(response);
}
static void
remote_proxy_end_session(remote_proxy_t *proxy)
{
if (proxy == NULL) {
return;
}
crm_trace("ending session ID %s", proxy->session_id);
if (proxy->source) {
mainloop_del_ipc_client(proxy->source);
}
}
void
remote_proxy_free(gpointer data)
{
remote_proxy_t *proxy = data;
crm_trace("freed proxy session ID %s", proxy->session_id);
free(proxy->node_name);
free(proxy->session_id);
free(proxy);
}
int
remote_proxy_dispatch(const char *buffer, ssize_t length, gpointer userdata)
{
// Async responses from cib and friends to clients via pacemaker-remoted
xmlNode *xml = NULL;
uint32_t flags = 0;
remote_proxy_t *proxy = userdata;
xml = string2xml(buffer);
if (xml == NULL) {
crm_warn("Received a NULL msg from IPC service.");
return 1;
}
flags = crm_ipc_buffer_flags(proxy->ipc);
if (flags & crm_ipc_proxied_relay_response) {
crm_trace("Passing response back to %.8s on %s: %.200s - request id: %d", proxy->session_id, proxy->node_name, buffer, proxy->last_request_id);
remote_proxy_relay_response(proxy, xml, proxy->last_request_id);
proxy->last_request_id = 0;
} else {
crm_trace("Passing event back to %.8s on %s: %.200s", proxy->session_id, proxy->node_name, buffer);
remote_proxy_relay_event(proxy, xml);
}
free_xml(xml);
return 1;
}
void
remote_proxy_disconnected(gpointer userdata)
{
remote_proxy_t *proxy = userdata;
crm_trace("destroying %p", proxy);
proxy->source = NULL;
proxy->ipc = NULL;
if(proxy->lrm) {
remote_proxy_notify_destroy(proxy->lrm, proxy->session_id);
proxy->lrm = NULL;
}
g_hash_table_remove(proxy_table, proxy->session_id);
}
remote_proxy_t *
remote_proxy_new(lrmd_t *lrmd, struct ipc_client_callbacks *proxy_callbacks,
const char *node_name, const char *session_id, const char *channel)
{
remote_proxy_t *proxy = NULL;
if(channel == NULL) {
crm_err("No channel specified to proxy");
remote_proxy_notify_destroy(lrmd, session_id);
return NULL;
}
proxy = calloc(1, sizeof(remote_proxy_t));
proxy->node_name = strdup(node_name);
proxy->session_id = strdup(session_id);
proxy->lrm = lrmd;
- if (safe_str_eq(crm_system_name, CRM_SYSTEM_CRMD)
- && safe_str_eq(channel, CRM_SYSTEM_CRMD)) {
+ if (!strcmp(pcmk_message_name(crm_system_name), CRM_SYSTEM_CRMD)
+ && !strcmp(pcmk_message_name(channel), CRM_SYSTEM_CRMD)) {
// The controller doesn't need to connect to itself
proxy->is_local = TRUE;
} else {
proxy->source = mainloop_add_ipc_client(channel, G_PRIORITY_LOW, 0, proxy, proxy_callbacks);
proxy->ipc = mainloop_get_ipc_client(proxy->source);
if (proxy->source == NULL) {
remote_proxy_free(proxy);
remote_proxy_notify_destroy(lrmd, session_id);
return NULL;
}
}
crm_trace("new remote proxy client established to %s on %s, session id %s",
channel, node_name, session_id);
g_hash_table_insert(proxy_table, proxy->session_id, proxy);
return proxy;
}
void
remote_proxy_cb(lrmd_t *lrmd, const char *node_name, xmlNode *msg)
{
const char *op = crm_element_value(msg, F_LRMD_IPC_OP);
const char *session = crm_element_value(msg, F_LRMD_IPC_SESSION);
remote_proxy_t *proxy = g_hash_table_lookup(proxy_table, session);
int msg_id = 0;
/* sessions are raw ipc connections to IPC,
* all we do is proxy requests/responses exactly
* like they are given to us at the ipc level. */
CRM_CHECK(op != NULL, return);
CRM_CHECK(session != NULL, return);
crm_element_value_int(msg, F_LRMD_IPC_MSG_ID, &msg_id);
/* This is msg from remote ipc client going to real ipc server */
if (safe_str_eq(op, LRMD_IPC_OP_DESTROY)) {
remote_proxy_end_session(proxy);
} else if (safe_str_eq(op, LRMD_IPC_OP_REQUEST)) {
int flags = 0;
xmlNode *request = get_message_xml(msg, F_LRMD_IPC_MSG);
const char *name = crm_element_value(msg, F_LRMD_IPC_CLIENT);
CRM_CHECK(request != NULL, return);
if (proxy == NULL) {
/* proxy connection no longer exists */
remote_proxy_notify_destroy(lrmd, session);
return;
}
// Controller requests MUST be handled by the controller, not us
CRM_CHECK(proxy->is_local == FALSE,
remote_proxy_end_session(proxy); return);
if (crm_ipc_connected(proxy->ipc) == FALSE) {
remote_proxy_end_session(proxy);
return;
}
proxy->last_request_id = 0;
crm_element_value_int(msg, F_LRMD_IPC_MSG_FLAGS, &flags);
crm_xml_add(request, XML_ACL_TAG_ROLE, "pacemaker-remote");
#if ENABLE_ACL
CRM_ASSERT(node_name);
crm_acl_get_set_user(request, F_LRMD_IPC_USER, node_name);
#endif
if(is_set(flags, crm_ipc_proxied)) {
const char *type = crm_element_value(request, F_TYPE);
int rc = 0;
if (safe_str_eq(type, T_ATTRD)
&& crm_element_value(request, F_ATTRD_HOST) == NULL) {
crm_xml_add(request, F_ATTRD_HOST, proxy->node_name);
}
rc = crm_ipc_send(proxy->ipc, request, flags, 5000, NULL);
if(rc < 0) {
xmlNode *op_reply = create_xml_node(NULL, "nack");
crm_err("Could not relay %s request %d from %s to %s for %s: %s (%d)",
op, msg_id, proxy->node_name, crm_ipc_name(proxy->ipc), name, pcmk_strerror(rc), rc);
/* Send a n'ack so the caller doesn't block */
crm_xml_add(op_reply, "function", __FUNCTION__);
crm_xml_add_int(op_reply, "line", __LINE__);
crm_xml_add_int(op_reply, "rc", rc);
remote_proxy_relay_response(proxy, op_reply, msg_id);
free_xml(op_reply);
} else {
crm_trace("Relayed %s request %d from %s to %s for %s",
op, msg_id, proxy->node_name, crm_ipc_name(proxy->ipc), name);
proxy->last_request_id = msg_id;
}
} else {
int rc = pcmk_ok;
xmlNode *op_reply = NULL;
// @COMPAT pacemaker_remoted <= 1.1.10
crm_trace("Relaying %s request %d from %s to %s for %s",
op, msg_id, proxy->node_name, crm_ipc_name(proxy->ipc), name);
rc = crm_ipc_send(proxy->ipc, request, flags, 10000, &op_reply);
if(rc < 0) {
crm_err("Could not relay %s request %d from %s to %s for %s: %s (%d)",
op, msg_id, proxy->node_name, crm_ipc_name(proxy->ipc), name, pcmk_strerror(rc), rc);
} else {
crm_trace("Relayed %s request %d from %s to %s for %s",
op, msg_id, proxy->node_name, crm_ipc_name(proxy->ipc), name);
}
if(op_reply) {
remote_proxy_relay_response(proxy, op_reply, msg_id);
free_xml(op_reply);
}
}
} else {
crm_err("Unknown proxy operation: %s", op);
}
}

File Metadata

Mime Type
text/x-diff
Expires
Sat, Nov 23, 3:18 PM (16 h, 17 s)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
1018843
Default Alt Text
(1 MB)

Event Timeline