diff --git a/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot b/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot index 8e23e0d150..12fc354d9e 100644 --- a/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot +++ b/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot @@ -1,427 +1,536 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource\n" +msgid "[root@pcmk-1 ~]# pcs resource\n" " Master/Slave Set: WebDataClone [WebData]\n" -" Masters: [ pcmk-2 pcmk-1 ]\n" +" Masters: [ pcmk-1 pcmk-2 ]\n" " Clone Set: dlm-clone [dlm]\n" -" Started: [ pcmk-2 pcmk-1 ]\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" +" 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 ]\n" -"# pcs resource rsc defaults\n" -"resource-stickiness: 100\n" -"# pcs resource op defaults\n" -"timeout: 240s\n" -"# pcs stonith\n" -" impi-fencing (stonith:fence_ipmilan) Started\n" -"# pcs property\n" -"dc-version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"cluster-infrastructure: corosync\n" -"no-quorum-policy: ignore\n" -"stonith-enabled: true\n" -"# pcs constraint\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" -" ClusterIP-clone then WebSite-clone\n" -" WebDataClone then WebSite-clone\n" -" WebFS-clone then WebSite-clone\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\n" -" WebFS-clone with WebDataClone (with-rsc-role:Master)\n" -" WebSite-clone with WebFS-clone\n" -"#\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 13:45:34 2012\n" -"Last change: Fri Sep 14 13:43:13 2012 via cibadmin on pcmk-1\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)" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"11 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"11 Resources configured\n" +"\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-2 pcmk-1 ]\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-1\n" -" ClusterIP:1 (ocf::heartbeat:IPaddr2): Started pcmk-2\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" -" impi-fencing (stonith:fence_ipmilan): Started" +"\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 +#. Tag: screen #, no-c-format -msgid "In xml it should look similar to this." +msgid "[root@pcmk-1 ~]# pcs cluster cib" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<cib admin_epoch=\"0\" cib-last-written=\"Fri Sep 14 13:43:13 2012\" crm_feature_set=\"3.0.6\" dc-uuid=\"1\" epoch=\"47\" have-quorum=\"1\" num_updates=\"50\" update-client=\"cibadmin\" update-origin=\"pcmk-1\" validate-with=\"pacemaker-1.2\">\n" -" <configuration>\n" +msgid "<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\">\n" " <crm_config>\n" " <cluster_property_set id=\"cib-bootstrap-options\">\n" -" <nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\"/>\n" +" <nvpair id=\"cib-bootstrap-options-have-watchdog\" name=\"have-watchdog\" value=\"false\"/>\n" +" <nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.12-a14efad\"/>\n" " <nvpair id=\"cib-bootstrap-options-cluster-infrastructure\" name=\"cluster-infrastructure\" value=\"corosync\"/>\n" -" <nvpair id=\"cib-bootstrap-options-no-quorum-policy\" name=\"no-quorum-policy\" value=\"ignore\"/>\n" +" <nvpair id=\"cib-bootstrap-options-cluster-name\" name=\"cluster-name\" value=\"mycluster\"/>\n" +" <nvpair id=\"cib-bootstrap-options-last-lrm-refresh\" name=\"last-lrm-refresh\" value=\"1419129162\"/>\n" " <nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"true\"/>\n" " </cluster_property_set>\n" " </crm_config>\n" " <nodes>\n" -" <node id=\"1\" type=\"normal\" uname=\"pcmk-1\"/>\n" -" <node id=\"2\" type=\"normal\" uname=\"pcmk-2\"/>\n" +" <node id=\"1\" uname=\"pcmk-1\">\n" +" <instance_attributes id=\"nodes-1\"/>\n" +" </node>\n" +" <node id=\"2\" uname=\"pcmk-2\">\n" +" <instance_attributes id=\"nodes-2\"/>\n" +" </node>\n" " </nodes>\n" " <resources>\n" +" <primitive class=\"stonith\" id=\"impi-fencing\" type=\"fence_ipmilan\">\n" +" <instance_attributes id=\"impi-fencing-instance_attributes\">\n" +" <nvpair id=\"impi-fencing-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"pcmk-1 pcmk-2\"/>\n" +" <nvpair id=\"impi-fencing-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"10.0.0.1\"/>\n" +" <nvpair id=\"impi-fencing-instance_attributes-login\" name=\"login\" value=\"testuser\"/>\n" +" <nvpair id=\"impi-fencing-instance_attributes-passwd\" name=\"passwd\" value=\"acd123\"/>\n" +" </instance_attributes>\n" +" <operations>\n" +" <op id=\"impi-fencing-interval-60s\" interval=\"60s\" name=\"monitor\"/>\n" +" </operations>\n" +" </primitive>\n" " <master id=\"WebDataClone\">\n" " <primitive class=\"ocf\" id=\"WebData\" provider=\"linbit\" type=\"drbd\">\n" " <instance_attributes id=\"WebData-instance_attributes\">\n" " <nvpair id=\"WebData-instance_attributes-drbd_resource\" name=\"drbd_resource\" value=\"wwwdata\"/>\n" " </instance_attributes>\n" " <operations>\n" -" <op id=\"WebData-interval-60s\" interval=\"60s\" name=\"monitor\"/>\n" +" <op id=\"WebData-start-timeout-240\" interval=\"0s\" name=\"start\" timeout=\"240\"/>\n" +" <op id=\"WebData-promote-timeout-90\" interval=\"0s\" name=\"promote\" timeout=\"90\"/>\n" +" <op id=\"WebData-demote-timeout-90\" interval=\"0s\" name=\"demote\" timeout=\"90\"/>\n" +" <op id=\"WebData-stop-timeout-100\" interval=\"0s\" name=\"stop\" timeout=\"100\"/>\n" +" <op id=\"WebData-monitor-interval-60s\" interval=\"60s\" name=\"monitor\"/>\n" " </operations>\n" " </primitive>\n" " <meta_attributes id=\"WebDataClone-meta_attributes\">\n" +" <nvpair id=\"WebDataClone-meta_attributes-master-max\" name=\"master-max\" value=\"2\"/>\n" " <nvpair id=\"WebDataClone-meta_attributes-master-node-max\" name=\"master-node-max\" value=\"1\"/>\n" " <nvpair id=\"WebDataClone-meta_attributes-clone-max\" name=\"clone-max\" value=\"2\"/>\n" " <nvpair id=\"WebDataClone-meta_attributes-clone-node-max\" name=\"clone-node-max\" value=\"1\"/>\n" " <nvpair id=\"WebDataClone-meta_attributes-notify\" name=\"notify\" value=\"true\"/>\n" -" <nvpair id=\"WebDataClone-meta_attributes-master-max\" name=\"master-max\" value=\"2\"/>\n" " </meta_attributes>\n" " </master>\n" " <clone id=\"dlm-clone\">\n" " <primitive class=\"ocf\" id=\"dlm\" provider=\"pacemaker\" type=\"controld\">\n" " <instance_attributes id=\"dlm-instance_attributes\"/>\n" " <operations>\n" -" <op id=\"dlm-interval-60s\" interval=\"60s\" name=\"monitor\"/>\n" +" <op id=\"dlm-start-timeout-90\" interval=\"0s\" name=\"start\" timeout=\"90\"/>\n" +" <op id=\"dlm-stop-timeout-100\" interval=\"0s\" name=\"stop\" timeout=\"100\"/>\n" +" <op id=\"dlm-monitor-interval-60s\" interval=\"60s\" name=\"monitor\"/>\n" " </operations>\n" " </primitive>\n" " <meta_attributes id=\"dlm-clone-meta\">\n" " <nvpair id=\"dlm-clone-max\" name=\"clone-max\" value=\"2\"/>\n" " <nvpair id=\"dlm-clone-node-max\" name=\"clone-node-max\" value=\"1\"/>\n" " </meta_attributes>\n" " </clone>\n" " <clone id=\"ClusterIP-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterIP\" provider=\"heartbeat\" type=\"IPaddr2\">\n" " <instance_attributes id=\"ClusterIP-instance_attributes\">\n" -" <nvpair id=\"ClusterIP-instance_attributes-ip\" name=\"ip\" value=\"192.168.0.120\"/>\n" +" <nvpair id=\"ClusterIP-instance_attributes-ip\" name=\"ip\" value=\"192.168.122.120\"/>\n" " <nvpair id=\"ClusterIP-instance_attributes-cidr_netmask\" name=\"cidr_netmask\" value=\"32\"/>\n" " <nvpair id=\"ClusterIP-instance_attributes-clusterip_hash\" name=\"clusterip_hash\" value=\"sourceip\"/>\n" " </instance_attributes>\n" " <operations>\n" -" <op id=\"ClusterIP-interval-30s\" interval=\"30s\" name=\"monitor\"/>\n" +" <op id=\"ClusterIP-start-timeout-20s\" interval=\"0s\" name=\"start\" timeout=\"20s\"/>\n" +" <op id=\"ClusterIP-stop-timeout-20s\" interval=\"0s\" name=\"stop\" timeout=\"20s\"/>\n" +" <op id=\"ClusterIP-monitor-interval-30s\" interval=\"30s\" name=\"monitor\"/>\n" " </operations>\n" +" <meta_attributes id=\"ClusterIP-meta_attributes\"/>\n" " </primitive>\n" " <meta_attributes id=\"ClusterIP-clone-meta\">\n" -" <nvpair id=\"ClusterIP-globally-unique\" name=\"globally-unique\" value=\"true\"/>\n" " <nvpair id=\"ClusterIP-clone-max\" name=\"clone-max\" value=\"2\"/>\n" " <nvpair id=\"ClusterIP-clone-node-max\" name=\"clone-node-max\" value=\"2\"/>\n" +" <nvpair id=\"ClusterIP-globally-unique\" name=\"globally-unique\" value=\"true\"/>\n" " </meta_attributes>\n" " </clone>\n" " <clone id=\"WebFS-clone\">\n" " <primitive class=\"ocf\" id=\"WebFS\" provider=\"heartbeat\" type=\"Filesystem\">\n" " <instance_attributes id=\"WebFS-instance_attributes\">\n" -" <nvpair id=\"WebFS-instance_attributes-device\" name=\"device\" value=\"/dev/drbd/by-res/wwwdata\"/>\n" +" <nvpair id=\"WebFS-instance_attributes-device\" name=\"device\" value=\"/dev/drbd1\"/>\n" " <nvpair id=\"WebFS-instance_attributes-directory\" name=\"directory\" value=\"/var/www/html\"/>\n" " <nvpair id=\"WebFS-instance_attributes-fstype\" name=\"fstype\" value=\"gfs2\"/>\n" " </instance_attributes>\n" +" <operations>\n" +" <op id=\"WebFS-start-timeout-60\" interval=\"0s\" name=\"start\" timeout=\"60\"/>\n" +" <op id=\"WebFS-stop-timeout-60\" interval=\"0s\" name=\"stop\" timeout=\"60\"/>\n" +" <op id=\"WebFS-monitor-interval-20\" interval=\"20\" name=\"monitor\" timeout=\"40\"/>\n" +" </operations>\n" " <meta_attributes id=\"WebFS-meta_attributes\"/>\n" " </primitive>\n" " <meta_attributes id=\"WebFS-clone-meta\"/>\n" " </clone>\n" " <clone id=\"WebSite-clone\">\n" " <primitive class=\"ocf\" id=\"WebSite\" provider=\"heartbeat\" type=\"apache\">\n" " <instance_attributes id=\"WebSite-instance_attributes\">\n" " <nvpair id=\"WebSite-instance_attributes-configfile\" name=\"configfile\" value=\"/etc/httpd/conf/httpd.conf\"/>\n" " <nvpair id=\"WebSite-instance_attributes-statusurl\" name=\"statusurl\" value=\"http://localhost/server-status\"/>\n" " </instance_attributes>\n" " <operations>\n" -" <op id=\"WebSite-interval-1min\" interval=\"1min\" name=\"monitor\"/>\n" +" <op id=\"WebSite-start-timeout-40s\" interval=\"0s\" name=\"start\" timeout=\"40s\"/>\n" +" <op id=\"WebSite-stop-timeout-60s\" interval=\"0s\" name=\"stop\" timeout=\"60s\"/>\n" +" <op id=\"WebSite-monitor-interval-1min\" interval=\"1min\" name=\"monitor\"/>\n" " </operations>\n" " </primitive>\n" " <meta_attributes id=\"WebSite-clone-meta\"/>\n" " </clone>\n" -" <primitive class=\"stonith\" id=\"impi-fencing\" type=\"fence_ipmilan\">\n" -" <instance_attributes id=\"impi-fencing-instance_attributes\">\n" -" <nvpair id=\"impi-fencing-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"pcmk-1 pcmk-2\"/>\n" -" <nvpair id=\"impi-fencing-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"10.0.0.1\"/>\n" -" <nvpair id=\"impi-fencing-instance_attributes-login\" name=\"login\" value=\"testuser\"/>\n" -" <nvpair id=\"impi-fencing-instance_attributes-passwd\" name=\"passwd\" value=\"acd123\"/>\n" -" </instance_attributes>\n" -" <operations>\n" -" <op id=\"impi-fencing-interval-60s\" interval=\"60s\" name=\"monitor\"/>\n" -" </operations>\n" -" </primitive>\n" " </resources>\n" " <constraints>\n" " <rsc_colocation id=\"colocation-WebSite-ClusterIP-INFINITY\" rsc=\"WebSite-clone\" score=\"INFINITY\" with-rsc=\"ClusterIP-clone\"/>\n" " <rsc_order first=\"ClusterIP-clone\" first-action=\"start\" id=\"order-ClusterIP-WebSite-mandatory\" then=\"WebSite-clone\" then-action=\"start\"/>\n" " <rsc_colocation id=\"colocation-WebFS-WebDataClone-INFINITY\" rsc=\"WebFS-clone\" score=\"INFINITY\" with-rsc=\"WebDataClone\" with-rsc-role=\"Master\"/>\n" -" <rsc_colocation id=\"colocation-WebSite-WebFS-INFINITY\" rsc=\"WebSite-clone\" score=\"INFINITY\" with-rsc=\"WebFS-clone\"/>\n" -" <rsc_order first=\"WebFS-clone\" id=\"order-WebFS-WebSite-mandatory\" then=\"WebSite-clone\"/>\n" " <rsc_order first=\"WebDataClone\" first-action=\"promote\" id=\"order-WebDataClone-WebFS-mandatory\" then=\"WebFS-clone\" then-action=\"start\"/>\n" +" <rsc_colocation id=\"colocation-WebSite-WebFS-INFINITY\" rsc=\"WebSite-clone\" score=\"INFINITY\" with-rsc=\"WebFS-clone\"/>\n" +" <rsc_order first=\"WebFS-clone\" first-action=\"start\" id=\"order-WebFS-WebSite-mandatory\" then=\"WebSite-clone\" then-action=\"start\"/>\n" +" <rsc_colocation id=\"colocation-WebFS-clone-dlm-clone-INFINITY\" rsc=\"WebFS-clone\" score=\"INFINITY\" with-rsc=\"dlm-clone\"/>\n" +" <rsc_order first=\"dlm-clone\" first-action=\"start\" id=\"order-dlm-clone-WebFS-clone-mandatory\" then=\"WebFS-clone\" then-action=\"start\"/>\n" " </constraints>\n" " <rsc_defaults>\n" " <meta_attributes id=\"rsc_defaults-options\">\n" " <nvpair id=\"rsc_defaults-options-resource-stickiness\" name=\"resource-stickiness\" value=\"100\"/>\n" " </meta_attributes>\n" " </rsc_defaults>\n" " <op_defaults>\n" " <meta_attributes id=\"op_defaults-options\">\n" " <nvpair id=\"op_defaults-options-timeout\" name=\"timeout\" value=\"240s\"/>\n" " </meta_attributes>\n" " </op_defaults>\n" " </configuration>\n" +" <status>\n" +" <node_state id=\"1\" uname=\"pcmk-1\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_update_resource\" join=\"member\" expected=\"member\">\n" +" <lrm id=\"1\">\n" +" <lrm_resources>\n" +" <lrm_resource id=\"WebData\" type=\"drbd\" class=\"ocf\" provider=\"linbit\">\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"dlm\" type=\"controld\" class=\"ocf\" provider=\"pacemaker\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"ClusterIP:0\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"ClusterIP:1\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"WebFS\" type=\"Filesystem\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"WebSite\" type=\"apache\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" </lrm_resources>\n" +" </lrm>\n" +" <transient_attributes id=\"1\">\n" +" <instance_attributes id=\"status-1\">\n" +" <nvpair id=\"status-1-shutdown\" name=\"shutdown\" value=\"0\"/>\n" +" <nvpair id=\"status-1-probe_complete\" name=\"probe_complete\" value=\"true\"/>\n" +" <nvpair id=\"status-1-master-WebData\" name=\"master-WebData\" value=\"10000\"/>\n" +" </instance_attributes>\n" +" </transient_attributes>\n" +" </node_state>\n" +" <node_state id=\"2\" uname=\"pcmk-2\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_update_resource\" join=\"member\" expected=\"member\">\n" +" <transient_attributes id=\"2\">\n" +" <instance_attributes id=\"status-2\">\n" +" <nvpair id=\"status-2-shutdown\" name=\"shutdown\" value=\"0\"/>\n" +" <nvpair id=\"status-2-probe_complete\" name=\"probe_complete\" value=\"true\"/>\n" +" <nvpair id=\"status-2-master-WebData\" name=\"master-WebData\" value=\"10000\"/>\n" +" </instance_attributes>\n" +" </transient_attributes>\n" +" <lrm id=\"2\">\n" +" <lrm_resources>\n" +" <lrm_resource id=\"WebData\" type=\"drbd\" class=\"ocf\" provider=\"linbit\">\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"dlm\" type=\"controld\" class=\"ocf\" provider=\"pacemaker\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"ClusterIP:0\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"ClusterIP:1\" type=\"IPaddr2\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"WebFS\" type=\"Filesystem\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" <lrm_resource id=\"WebSite\" type=\"apache\" class=\"ocf\" provider=\"heartbeat\">\n" +" <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\"/>\n" +" <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\"/>\n" +" </lrm_resource>\n" +" </lrm_resources>\n" +" </lrm>\n" +" </node_state>\n" +" </status>\n" "</cib>" msgstr "" #. Tag: title #, no-c-format msgid "Node List" msgstr "" -#. Tag: para -#, no-c-format -msgid "The list of cluster nodes is automatically populated by the cluster." -msgstr "" - -#. Tag: literallayout +#. Tag: screen #, no-c-format -msgid "Pacemaker Nodes:\n" -" Online: [ pcmk-1 pcmk-2 ]" +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: para +#. Tag: screen #, no-c-format -msgid "This is where the cluster automatically stores some information about the cluster" +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" +" have-watchdog: false\n" +" last-lrm-refresh: 1439569053\n" +" stonith-enabled: true" msgstr "" #. Tag: para #, no-c-format -msgid "dc-version - the version (including upstream source-code hash) of Pacemaker used on the DC" +msgid "The output shows state information automatically obtained about the cluster, including:" msgstr "" #. Tag: para #, no-c-format -msgid "cluster-infrastructure - the cluster infrastructure being used (heartbeat or openais)" +msgid "cluster-infrastructure - the cluster communications layer in use (heartbeat or corosync)" msgstr "" #. Tag: para #, no-c-format -msgid "expected-quorum-votes - the maximum number of nodes expected to be part of the cluster" +msgid "cluster-name - the cluster name chosen by the administrator when the cluster was created" msgstr "" #. Tag: para #, no-c-format -msgid "and where the admin can set options that control the way the cluster operates" +msgid "dc-version - the version (including upstream source-code hash) of Pacemaker used on the Designated Controller" msgstr "" #. Tag: para #, no-c-format -msgid "stonith-enabled=true - Make use of STONITH" +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 "no-quorum-policy=ignore - Ignore loss of quorum and continue to host resources." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# pcs property\n" -"dc-version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"cluster-infrastructure: corosync\n" -"no-quorum-policy: ignore\n" -"stonith-enabled: true" +msgid "stonith-enabled=true - 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: para +#. Tag: screen #, no-c-format -msgid "Here we configure cluster options that apply to every resource." +msgid "[root@pcmk-1 ~]# pcs resource defaults\n" +"resource-stickiness: 100" msgstr "" #. Tag: para #, no-c-format -msgid "resource-stickiness - Specify the aversion to moving resources to other machines" +msgid "This shows cluster option defaults that apply to every resource that does not explicitly set the option itself. Above:" msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs resource rsc defaults\n" -"resource-stickiness: 100" +msgid "resource-stickiness - Specify the aversion to moving healthy resources to other machines" msgstr "" #. Tag: title #, no-c-format msgid "Fencing" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs stonith show\n" -" impi-fencing (stonith:fence_ipmilan) Started\n" -"# pcs stonith show impi-fencing\n" -"Resource: impi-fencing\n" -" pcmk_host_list: pcmk-1 pcmk-2\n" -" ipaddr: 10.0.0.1\n" -" login: testuser\n" -" passwd: acd123" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource show ClusterIP-clone\n" -"Resource: ClusterIP-clone\n" -" ip: 192.168.0.120\n" -" cidr_netmask: 32\n" -" clusterip_hash: sourceip\n" -" globally-unique: true\n" -" clone-max: 2\n" -" clone-node-max: 2\n" -" op monitor interval=30s" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "TODO: The RA should check for globally-unique=true when cloned" +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 drbd.conf) 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 by specifying master-max=2. We also set the notify option so that the cluster will tell DRBD agent when it’s 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 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." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource show WebDataClone\n" -"Resource: WebDataClone\n" -" drbd_resource: wwwdata\n" -" master-node-max: 1\n" -" clone-max: 2\n" -" clone-node-max: 1\n" -" notify: true\n" -" master-max: 2\n" -" op monitor interval=60s\n" -"# pcs constraint ref WebDataClone\n" +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 gfs-control and drbd instances." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource show WebFS-clone\n" -"Resource: WebFS-clone\n" -" device: /dev/drbd/by-res/wwwdata\n" -" directory: /var/www/html\n" -" fstype: gfs2\n" -"# pcs constraint ref WebFS-clone\n" +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-WebDataClone-WebFS-mandatory" +" 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 it’s main configuration file and restrict it to running on nodes that have the required filesystem mounted and the IP address active." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource show WebSite-clone\n" -"Resource: WebSite-clone\n" -" configfile: /etc/httpd/conf/httpd.conf\n" -" statusurl: http://localhost/server-status\n" -" master-max: 2\n" -" op monitor interval=1min\n" -"# pcs constraint ref WebSite-clone\n" +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 38f140ffed..b26a496c0d 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 , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 corosync.conf for two-node cluster using a node list." +msgid "Sample corosync.conf for two-node cluster created by pcs." msgstr "" #. Tag: literallayout #, no-c-format -msgid "# Please read the corosync.conf.5 manual page\n" -"totem {\n" +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" +" }\n" " node {\n" " ring0_addr: pcmk-2\n" " nodeid: 2\n" -" }\n" +" }\n" "}\n" "\n" "quorum {\n" -" provider: corosync_votequorum\n" +"provider: corosync_votequorum\n" +"two_node: 1\n" "}\n" "\n" "logging {\n" -" to_syslog: yes\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 41a3c035db..793acf98ba 100644 --- a/doc/Clusters_from_Scratch/pot/Ap-Reading.pot +++ b/doc/Clusters_from_Scratch/pot/Ap-Reading.pot @@ -1,34 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 http://www.clusterlabs.org" +msgid "Project Website http://www.clusterlabs.org/" msgstr "" #. Tag: para #, no-c-format -msgid "Cluster Commands A comprehensive guide to cluster commands has been written by SuSE and can be found at: http://www.suse.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/book_sleha.html" +msgid "SuSE has a comprehensive guide to cluster commands (though using the crmsh command-line shell rather than pcs) at: https://www.suse.com/documentation/sle_ha/book_sleha/data/book_sleha.html" msgstr "" #. Tag: para #, no-c-format -msgid "Corosync http://www.corosync.org" +msgid "Corosync http://www.corosync.org/" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Author_Group.pot b/doc/Clusters_from_Scratch/pot/Author_Group.pot index b1c4aeeadc..e1dac4cb14 100644 --- a/doc/Clusters_from_Scratch/pot/Author_Group.pot +++ b/doc/Clusters_from_Scratch/pot/Author_Group.pot @@ -1,64 +1,64 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 6de2f8111f..3ced027eed 100644 --- a/doc/Clusters_from_Scratch/pot/Book_Info.pot +++ b/doc/Clusters_from_Scratch/pot/Book_Info.pot @@ -1,69 +1,69 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Creating Active/Passive and Active/Active Clusters on Fedora" +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." 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," 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 Fedora 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." +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 bd3a559e11..5dd6e355ee 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot @@ -1,416 +1,489 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Conversion to Active/Active" +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 "Requirements" +msgid "Install Cluster Filesystem Software" 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, however since DRBD supports multiple Primaries, we can also use that." +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 "The only hitch is that we need to use a cluster-aware filesystem. The one we used earlier with DRBD, ext4, is not one of those. Both OCFS2 and GFS2 are supported, however here we will use GFS2 which comes with Fedora 17." +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 "Installing the required Software" +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 ocf:pacemaker:controld resource script), and clone it:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# yum install -y gfs2-utils dlm kernel-modules-extra" +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: literallayout +#. Tag: para #, no-c-format -msgid "Loaded plugins: langpacks, presto, refresh-packagekit\n" -"Resolving Dependencies\n" -"--> Running transaction check\n" -"---> Package dlm.x86_64 0:3.99.4-1.fc17 will be installed\n" -"---> Package gfs2-utils.x86_64 0:3.1.4-3.fc17 will be installed\n" -"---> Package kernel-modules-extra.x86_64 0:3.4.4-3.fc17 will be installed\n" -"--> Finished Dependency Resolution\n" +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" "\n" -"Dependencies Resolved\n" "\n" -"================================================================================\n" -" Package Arch Version Repository Size\n" -"================================================================================\n" -"Installing:\n" -" dlm x86_64 3.99.4-1.fc17 updates 83 k\n" -" gfs2-utils x86_64 3.1.4-3.fc17 fedora 214 k\n" -" kernel-modules-extra x86_64 3.4.4-3.fc17 updates 1.7 M\n" +"Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"Transaction Summary\n" -"================================================================================\n" -"Install 3 Packages\n" +"Full list of resources:\n" "\n" -"Total download size: 1.9 M\n" -"Installed size: 7.7 M\n" -"Downloading Packages:\n" -"(1/3): dlm-3.99.4-1.fc17.x86_64.rpm | 83 kB 00:00\n" -"(2/3): gfs2-utils-3.1.4-3.fc17.x86_64.rpm | 214 kB 00:00\n" -"(3/3): kernel-modules-extra-3.4.4-3.fc17.x86_64.rpm | 1.7 MB 00:01\n" -"--------------------------------------------------------------------------------\n" -"Total 615 kB/s | 1.9 MB 00:03\n" -"Running Transaction Check\n" -"Running Transaction Test\n" -"Transaction Test Succeeded\n" -"Running Transaction\n" -" Installing : kernel-modules-extra-3.4.4-3.fc17.x86_64 1/3\n" -" Installing : gfs2-utils-3.1.4-3.fc17.x86_64 2/3\n" -" Installing : dlm-3.99.4-1.fc17.x86_64 3/3\n" -" Verifying : dlm-3.99.4-1.fc17.x86_64 1/3\n" -" Verifying : gfs2-utils-3.1.4-3.fc17.x86_64 2/3\n" -" Verifying : kernel-modules-extra-3.4.4-3.fc17.x86_64 3/3\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" -"Installed:\n" -" dlm.x86_64 0:3.99.4-1.fc17\n" -" gfs2-utils.x86_64 0:3.1.4-3.fc17\n" -" kernel-modules-extra.x86_64 0:3.4.4-3.fc17\n" +"PCSD Status:\n" +" pcmk-1: Online\n" +" pcmk-2: Online\n" "\n" -"Complete!" +"Daemon Status:\n" +" corosync: active/disabled\n" +" pacemaker: active/disabled\n" +" pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format -msgid "Create a GFS2 Filesystem" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Preparation" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource stop WebFS\n" -"# pcs resource\n" -" ClusterIP (ocf::heartbeat:IPaddr2) Started\n" -" WebSite (ocf::heartbeat:apache) Stopped\n" +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" +" WebFS (ocf::heartbeat:Filesystem): Stopped\n" +" Clone Set: dlm-clone [dlm]\n" +" Started: [ pcmk-1 pcmk-2 ]" msgstr "" #. Tag: para #, no-c-format -msgid "Note that both Apache and WebFS have been stopped." -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Create and Populate an GFS2 Partition" +msgid "You can see that both Apache and WebFS have been stopped, and that pcmk-2 is the current master for the DRBD device." msgstr "" #. Tag: para #, no-c-format -msgid "Now that the cluster stack and integration pieces are running smoothly, we can create an GFS2 partition." +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 "We need to specify a number of additional parameters when creating a GFS2 partition." +msgid "Run the next command on whichever node has the DRBD Primary role. Otherwise, you will receive the message:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "First we must use the -p option to specify that we want to use the the Kernel’s DLM. Next we use -j to indicate that it should reserve enough space for two journals (one per node accessing the filesystem)." +msgid "/dev/drbd1: Read-only file system" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Lastly, we use -t to specify the lock table name. The format for this field is clustername:fsname. For the fsname, we need to use the same value as specified in corosync.conf for cluster_name. If you setup corosync with the same cluster name we used in this tutorial, cluster name will be mycluster. If you are unsure what your cluster name is, open up /etc/corosync/corosync.conf, or execute the command pcs cluster corosync pcmk-1 to view the corosync config. The cluster name will be in the totem block." +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 "We must run the next command on whichever node last had /dev/drbd mounted. Otherwise you will receive the message:" +msgid "The mkfs.gfs2 command required a number of additional parameters:" msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "/dev/drbd1: Read-only file system" +msgid "-p lock_dlm specifies that we want to use the kernel’s DLM." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# ssh pcmk-2 -- mkfs.gfs2 -p lock_dlm -j 2 -t mycluster:web /dev/drbd1\n" -"This will destroy any data on /dev/drbd1.\n" -"It appears to contain: Linux rev 1.0 ext4 filesystem data, UUID=dc45fff3-c47a-4db2-96f7-a8049a323fe4 (extents) (large files) (huge files)\n" -"Are you sure you want to proceed? [y/n]y\n" -"Device: /dev/drbd1\n" -"Blocksize: 4096\n" -"Device Size 0.97 GB (253935 blocks)\n" -"Filesystem Size: 0.97 GB (253932 blocks)\n" -"Journals: 2\n" -"Resource Groups: 4\n" -"Locking Protocol: \"lock_dlm\"\n" -"Lock Table: \"mycluster\"\n" -"UUID: ed293a02-9eee-3fa3-ed1c-435ef1fd0116" +msgid "-j 2 indicates that the filesystem should reserve enough space for two journals (one for each node that will access the filesystem)." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs cluster cib dlm_cfg\n" -"# pcs -f dlm_cfg resource create dlm ocf:pacemaker:controld op monitor interval=60s\n" -"# pcs -f dlm_cfg resource clone dlm clone-max=2 clone-node-max=1\n" -"# pcs -f dlm_cfg resource show\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" -" Stopped: [ dlm:0 dlm:1 ]\n" -"# pcs cluster push cib dlm_cfg\n" -"CIB updated\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 12:54:50 2012\n" -"Last change: Fri Sep 14 12:54:43 2012 via cibadmin on pcmk-1\n" -"Stack: corosync\n" -"Current DC: pcmk-1 (1) - partition with quorum\n" -"Version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"7 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): 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 ]" +msgid "-t mycluster:web specifies the lock table name. The format for this field is clustername:fsname. For clustername, we need to use the same value we specified originally with pcs cluster setup --name (which is also the value of cluster_name in /etc/corosync/corosync.conf). If you are unsure what your cluster name is, you can look in /etc/corosync/corosync.conf or execute the command pcs cluster corosync pcmk-1 | grep cluster_name." msgstr "" #. Tag: para #, no-c-format -msgid "Then (re)populate the new filesystem with data (web pages). For now we’ll create another variation on our home page." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# mount /dev/drbd1 /mnt/\n" -"# cat <<-END >/mnt/index.html\n" +msgid "[root@pcmk-2 ~]# mount /dev/drbd1 /mnt\n" +"[root@pcmk-2 ~]# cat <<-END >/mnt/index.html\n" "<html>\n" "<body>My Test Site - GFS2</body>\n" "</html>\n" "END\n" -"# umount /dev/drbd1\n" -"# drbdadm verify wwwdata#" +"[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, lets update the configuration." +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 gfs2 instead of xfs." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource show WebFS\n" -"Resource: WebFS\n" -" device: /dev/drbd/by-res/wwwdata\n" -" directory: /var/www/html\n" -" fstype: ext4\n" -" target-role: Stopped" +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 "The fstype option needs to be updated to gfs2 instead of ext4." +msgid "GFS2 requires that DLM be running, so we also need to set up new colocation and ordering constraints for it:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource update WebFS fstype=gfs2\n" -"# pcs resource show WebFS\n" -"Resource: WebFS\n" -" device: /dev/drbd/by-res/wwwdata\n" -" directory: /var/www/html\n" -" fstype: gfs2\n" -" target-role: Stopped\n" -"CIB updated" +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 "Reconfigure Pacemaker for Active/Active" +msgid "Clone the IP address" msgstr "" #. Tag: para #, no-c-format -msgid "Almost everything is in place. Recent versions of DRBD are capable of operating in Primary/Primary mode and the filesystem we’re using is cluster aware. All we need to do now is reconfigure the cluster to take advantage of this." +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 "This will involve a number of changes, so we’ll want work with a local cib file." +msgid "The IPaddr2 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 iptables clusterip 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: programlisting +#. Tag: para #, no-c-format -msgid "# pcs cluster cib active_cfg" +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 "There’s no point making the services active on both locations if we can’t reach them, so lets first clone the IP address. Cloned IPaddr2 resources use an iptables rule to ensure that each request only gets processed by one of the two clone instances. The additional meta options tell the cluster how many instances of the clone we want (one \"request bucket\" for each node) and that if all other nodes fail, then the remaining node should hold all of them. Otherwise the requests would be simply discarded." +msgid "clone-max=2 tells the resource agent to split packets this many ways. This should equal the number of nodes that can host the IP." msgstr "" -#. Tag: screen +#. Tag: para +#, no-c-format +msgid "clone-node-max=2 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 "# pcs -f active_cfg resource clone ClusterIP \\\n" -" globally-unique=true clone-max=2 clone-node-max=2" +msgid "globally-unique=true tells the cluster that one clone isn’t identical to another (each handles a different \"bucket\"). This also tells the resource agent to insert iptables rules so each host only processes packets in its bucket(s)." msgstr "" #. Tag: para #, no-c-format -msgid "Notice when the ClusterIP becomes a clone, the constraints referencing ClusterIP now reference the clone. This is done automatically by pcs." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f active_cfg constraint\n" +msgid "[root@pcmk-1 ~]# pcs -f loadbalance_cfg constraint\n" "Location Constraints:\n" "Ordering Constraints:\n" -" start ClusterIP-clone then start WebSite\n" -" WebFS then WebSite\n" -" promote WebDataClone then start WebFS\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\n" -" WebFS with WebDataClone (with-rsc-role:Master)\n" -" WebSite with WebFS" +" 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)" msgstr "" #. Tag: para #, no-c-format -msgid "Now we must tell the ClusterIP how to decide which requests are processed by which hosts. To do this we must specify the clusterip_hash parameter." +msgid "Now we must tell the resource how to decide which requests are processed by which hosts. To do this, we specify the clusterip_hash parameter. The value of sourceip means that the source IP address of incoming packets will be hashed; each node will process a certain range of hashes." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f active_cfg resource update ClusterIP clusterip_hash=sourceip" +msgid "[root@pcmk-1 ~]# pcs -f loadbalance_cfg resource update ClusterIP clusterip_hash=sourceip" msgstr "" #. Tag: para #, no-c-format -msgid "Next we need to convert the filesystem and Apache resources into clones." +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" +"\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 arping 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 "Notice how pcs automatically updates the relevant constraints again." +msgid "Clone the filesystem and Apache resources in a new configuration. Notice how pcs automatically updates the relevant constraints again." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f active_cfg resource clone WebFS\n" -"# pcs -f active_cfg resource clone WebSite\n" -"# pcs -f active_cfg constraint\n" +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\n" -" WebFS-clone then WebSite-clone\n" -" promote WebDataClone then start WebFS-clone\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\n" -" WebFS-clone with WebDataClone (with-rsc-role:Master)\n" -" WebSite-clone with WebFS-clone" +" 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)" msgstr "" #. Tag: para #, no-c-format -msgid "The last step is to tell the cluster that it is now allowed to promote both instances to be Primary (aka. Master)." +msgid "Tell the cluster that it is now allowed to promote both instances to be DRBD Primary (aka. master)." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f active_cfg resource update WebDataClone master-max=2" +msgid "[root@pcmk-1 ~]# pcs -f active_cfg resource update WebDataClone master-max=2" msgstr "" #. Tag: para #, no-c-format -msgid "Review the configuration before uploading it to the cluster, quitting the shell and watching the cluster’s response" +msgid "Finally, load our configuration to the cluster, and re-enable the WebFS resource (which we disabled earlier)." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster push cib active_cfg\n" -"# pcs resource start WebFS" +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." +msgid "After all the processes are started, the status should look similar to this." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource\n" +msgid "[root@pcmk-1 ~]# pcs resource\n" " Master/Slave Set: WebDataClone [WebData]\n" -" Masters: [ pcmk-2 pcmk-1 ]\n" +" Masters: [ pcmk-1 pcmk-2 ]\n" " Clone Set: dlm-clone [dlm]\n" -" Started: [ pcmk-2 pcmk-1 ]\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" +" 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 "Testing Recovery" +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 pcs status to confirm that its ClusterIP clone was moved to the other node, and use arping to verify that packets are not being lost from any source host." msgstr "" #. Tag: para #, no-c-format -msgid "TODO: Put one node into standby to demonstrate failover" +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 06fe5ff7ae..2adb086b7e 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot @@ -1,437 +1,508 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Creating an Active/Passive Cluster" +msgid "Create an Active/Passive Cluster" msgstr "" #. Tag: title #, no-c-format -msgid "Exploring the Existing Configuration" +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." +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 "This is what the base configuration should look like." +msgid "The first few lines of output should look like this:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs status\n" -"Last updated: Fri Sep 14 10:12:01 2012\n" -"Last change: Fri Sep 14 09:51:55 2012 via crmd on pcmk-2\n" +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-1 (1) - partition with quorum\n" -"Version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"0 Resources configured.\n" +"Current DC: pcmk-2 (2) - partition with quorum\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"0 Resources configured\n" "\n" -"Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"Full list of resources:" +"Online: [ pcmk-1 pcmk-2 ]" msgstr "" #. Tag: para #, no-c-format -msgid "For those that are not of afraid of XML, you can see the raw cluster configuration and status by using the pcs cluster cib command." +msgid "For those who are not of afraid of XML, you can see the raw cluster configuration and status by using the pcs cluster cib command." msgstr "" #. Tag: title #, no-c-format msgid "The last XML you’ll see in this document" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster cib" +msgid "[root@pcmk-1 ~]# pcs cluster cib" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<cib epoch=\"4\" num_updates=\"19\" admin_epoch=\"0\" validate-with=\"pacemaker-1.2\" crm_feature_set=\"3.0.6\" update-origin=\"pcmk-1\" update-client=\"crmd\" cib-last-written=\"Wed Aug 1 16:08:52 2012\" have-quorum=\"1\" dc-uuid=\"1\">\n" +msgid "<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\">\n" " <configuration>\n" " <crm_config>\n" " <cluster_property_set id=\"cib-bootstrap-options\">\n" -" <nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\"/>\n" +" <nvpair id=\"cib-bootstrap-options-have-watchdog\" name=\"have-watchdog\" value=\"false\"/>\n" +" <nvpair id=\"cib-bootstrap-options-dc-version\" name=\"dc-version\" value=\"1.1.12-a14efad\"/>\n" " <nvpair id=\"cib-bootstrap-options-cluster-infrastructure\" name=\"cluster-infrastructure\" value=\"corosync\"/>\n" +" <nvpair id=\"cib-bootstrap-options-cluster-name\" name=\"cluster-name\" value=\"mycluster\"/>\n" " </cluster_property_set>\n" " </crm_config>\n" " <nodes>\n" -" <node id=\"1\" uname=\"pcmk-1\" type=\"normal\"/>\n" -" <node id=\"2\" uname=\"pcmk-2\" type=\"normal\"/>\n" +" <node id=\"1\" uname=\"pcmk-1\"/>\n" +" <node id=\"2\" uname=\"pcmk-2\"/>\n" " </nodes>\n" " <resources/>\n" " <constraints/>\n" " </configuration>\n" " <status>\n" -" <node_state id=\"2\" uname=\"pcmk-2\" ha=\"active\" in_ccm=\"true\" crmd=\"online\" join=\"member\" expected=\"member\" crm-debug-origin=\"do_state_transition\" shutdown=\"0\">\n" +" <node_state id=\"2\" uname=\"pcmk-2\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_state_transition\" join=\"member\" expected=\"member\">\n" " <lrm id=\"2\">\n" " <lrm_resources/>\n" " </lrm>\n" " <transient_attributes id=\"2\">\n" " <instance_attributes id=\"status-2\">\n" +" <nvpair id=\"status-2-shutdown\" name=\"shutdown\" value=\"0\"/>\n" " <nvpair id=\"status-2-probe_complete\" name=\"probe_complete\" value=\"true\"/>\n" " </instance_attributes>\n" " </transient_attributes>\n" " </node_state>\n" -" <node_state id=\"1\" uname=\"pcmk-1\" ha=\"active\" in_ccm=\"true\" crmd=\"online\" join=\"member\" expected=\"member\" crm-debug-origin=\"do_state_transition\" shutdown=\"0\">\n" +" <node_state id=\"1\" uname=\"pcmk-1\" in_ccm=\"true\" crmd=\"online\" crm-debug-origin=\"do_state_transition\" join=\"member\" expected=\"member\">\n" " <lrm id=\"1\">\n" " <lrm_resources/>\n" " </lrm>\n" " <transient_attributes id=\"1\">\n" " <instance_attributes id=\"status-1\">\n" +" <nvpair id=\"status-1-shutdown\" name=\"shutdown\" value=\"0\"/>\n" " <nvpair id=\"status-1-probe_complete\" name=\"probe_complete\" value=\"true\"/>\n" " </instance_attributes>\n" " </transient_attributes>\n" " </node_state>\n" " </status>\n" "</cib>" msgstr "" #. Tag: para #, no-c-format -msgid "Before we make any changes, its a good idea to check the validity of the configuration." +msgid "Before we make any changes, it’s a good idea to check the validity of the configuration." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_verify -L -V\n" +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\n" -" -V may provide more details" +"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 If the data is corrupt, there is little point in continuing to make it available , the default for STONITH A common node fencing mechanism. Used to ensure data integrity by powering off \"bad\" nodes in Pacemaker is enabled. 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)." +msgid "In order to guarantee the safety of your data, If the data is corrupt, there is little point in continuing to make it available the default for STONITH A common node fencing mechanism. Used to ensure data integrity by powering off \"bad\" nodes in Pacemaker is enabled. 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 "For now, we will disable this feature and configure it later in the Configuring STONITH section. It is important to note that the use of STONITH is highly encouraged, turning it off tells the cluster to simply pretend that failed nodes are safely powered off. Some vendors will even refuse to support clusters that have it disabled." +msgid "We will disable this feature for now and configure it later." msgstr "" #. Tag: para #, no-c-format -msgid "To disable STONITH, we set the stonith-enabled cluster option to false." +msgid "To disable STONITH, set the stonith-enabled cluster option to false:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs property set stonith-enabled=false\n" -"# crm_verify -L" +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 stonith-enabled=false is completely inappropriate for a production cluster. We use it here to defer the discussion of its configuration which can differ widely from one installation to the next. See for information on why STONITH is important and details on how to configure it." +msgid "The use of stonith-enabled=false 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 for information on why STONITH is important and details on how to configure it." msgstr "" #. Tag: title #, no-c-format -msgid "Adding a Resource" +msgid "Add a Resource" msgstr "" #. Tag: para #, no-c-format -msgid "The first thing we should do is configure an IP address. Regardless of where the cluster service(s) are running, we need a consistent address to contact them on. Here I will choose and add 192.168.122.120 as the floating address, give it the imaginative name ClusterIP and tell the cluster to check that its running every 30 seconds." +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 be one already associated with a physical node" +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 "# pcs resource create ClusterIP ocf:heartbeat:IPaddr2 \\\n" -" ip=192.168.0.120 cidr_netmask=32 op monitor interval=30s" +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 "The other important piece of information here is ocf:heartbeat:IPaddr2." +msgid "Another important piece of information here is ocf:heartbeat:IPaddr2. This tells Pacemaker three things about the resource you want to add:" msgstr "" #. Tag: para #, no-c-format -msgid "This tells Pacemaker three things about the resource you want to add. The first field, ocf, is the standard to which the resource script conforms to and where to find it. The second field is specific to OCF resources and tells the cluster which namespace to find the resource script in, in this case heartbeat. The last field indicates the name of the resource script." +msgid "The first field (ocf in this case) is the standard to which the resource script conforms and where to find it." msgstr "" #. Tag: para #, no-c-format -msgid "To obtain a list of the available resource standards (the ocf part of ocf:heartbeat:IPaddr2), run" +msgid "The second field (heartbeat in this case) is standard-specific; for OCF resources, it tells the cluster which OCF namespace the resource script is in." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs resource standards\n" +msgid "The third field (IPaddr2 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 ocf part of ocf:heartbeat:IPaddr2), run:" +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "[root@pcmk-1 ~]# pcs resource standards\n" "ocf\n" "lsb\n" "service\n" "systemd\n" "stonith" msgstr "" #. Tag: para #, no-c-format -msgid "To obtain a list of the available ocf resource providers (the heartbeat part of ocf:heartbeat:IPaddr2), run" +msgid "To obtain a list of the available OCF resource providers (the heartbeat part of ocf:heartbeat:IPaddr2), run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource providers\n" +msgid "[root@pcmk-1 ~]# pcs resource providers\n" "heartbeat\n" -"linbit\n" -"pacemaker\n" -"redhat" +"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 IPaddr2 part of ocf:heartbeat:IPaddr2), run" +msgid "Finally, if you want to see all the resource agents available for a specific OCF provider (the IPaddr2 part of ocf:heartbeat:IPaddr2), run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource agents ocf:heartbeat\n" -"AoEtarget\n" -"AudibleAlarm\n" +msgid "[root@pcmk-1 ~]# pcs resource agents ocf:heartbeat\n" "CTDB\n" -"ClusterMon\n" "Delay\n" "Dummy\n" -".\n" -". (skipping lots of resources to save space)\n" -".\n" +"Filesystem\n" +"IPaddr\n" "IPaddr2\n" ".\n" +". (skipping lots of resources to save space)\n" ".\n" -".\n" +"rsyncd\n" +"slapd\n" "symlink\n" -"syslog-ng\n" -"tomcat\n" -"vmware" +"tomcat" 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." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs status\n" -"\n" -"Last updated: Fri Sep 14 10:17:00 2012\n" -"Last change: Fri Sep 14 10:15:48 2012 via cibadmin on pcmk-1\n" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"1 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"1 Resources configured\n" +"\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" "Full list of resources:\n" "\n" -" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1" +" 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 "Being a high-availability cluster, we should test failover of our new resource before moving on." +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" +"\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 "Shut down Pacemaker and Corosync on that machine." +msgid "You can see that the status of the ClusterIP resource is Started on a particular node (in this example, pcmk-1). Shut down Pacemaker and Corosync on that machine to trigger a failover." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "#pcs cluster stop pcmk-1\n" +msgid "[root@pcmk-1 ~]# pcs cluster stop pcmk-1\n" "Stopping Cluster..." msgstr "" #. Tag: para #, no-c-format -msgid "Once Corosync is no longer running, go to the other node and check the cluster status." +msgid "A cluster command such as pcs cluster stop nodename can be run from any node in the cluster, not just the affected node." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs status\n" -"\n" -"Last updated: Fri Sep 14 10:31:01 2012\n" -"Last change: Fri Sep 14 10:15:48 2012 via cibadmin on pcmk-1\n" +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 WITHOUT quorum\n" -"Version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"1 Resources configured.\n" +"Current DC: pcmk-2 (2) - partition with quorum\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"1 Resources configured\n" +"\n" "\n" "Online: [ pcmk-2 ]\n" "OFFLINE: [ pcmk-1 ]\n" "\n" "Full list of resources:\n" "\n" -" ClusterIP (ocf::heartbeat:IPaddr2): Stopped" +" 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 "There are three things to notice about the cluster’s current state. The first is that, as expected, pcmk-1 is now offline. However we can also see that ClusterIP isn’t running anywhere!" +msgid "Notice that pcmk-1 is OFFLINE for cluster purposes (its PCSD is still Online, allowing it to receive pcs commands, but it is not participating in the cluster)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Also notice that ClusterIP is now running on pcmk-2 — failover happened automatically, and no errors are reported." msgstr "" #. Tag: title #, no-c-format -msgid "Quorum and Two-Node Clusters" +msgid "Quorum" msgstr "" #. Tag: para #, no-c-format -msgid "This is because the cluster no longer has quorum, as can be seen by the text \"partition WITHOUT quorum\" in the status output. In order to reduce the possibility of data corruption, Pacemaker’s default behavior is to stop all resources if the cluster does not have quorum." +msgid "If a cluster splits into two (or more) groups of nodes that can no longer communicate with each other (aka. partitions), quorum 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 is said to have quorum when more than half the known or expected nodes are online, or for the mathematically inclined, whenever the following equation is true:" +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 < 2 * active_nodes" msgstr "" #. Tag: para #, no-c-format -msgid "Therefore a two-node cluster only has quorum when both nodes are running, which is no longer the case for our cluster. This would normally make the creation of a two-node cluster pointless Actually some would argue that two-node clusters are always pointless, but that is an argument for another time , however it is possible to control how Pacemaker behaves when quorum is lost. In particular, we can tell the cluster to simply ignore quorum altogether." +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: programlisting +#. Tag: para #, no-c-format -msgid "# pcs property set no-quorum-policy=ignore\n" -"# pcs property\n" -"dc-version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"cluster-infrastructure: corosync\n" -"stonith-enabled: false\n" -"no-quorum-policy: ignore" +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, Some would argue that two-node clusters are always pointless, but that is an argument for another time 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 "After a few moments, the cluster will start the IP address on the remaining node. Note that the cluster still does not have quorum." +msgid "The pcs cluster setup command will automatically configure two_node: 1 in corosync.conf, so a two-node cluster will \"just work\"." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs status\n" -"Last updated: Fri Sep 14 10:38:11 2012\n" -"Last change: Fri Sep 14 10:37:53 2012 via cibadmin on pcmk-2\n" -"Stack: corosync\n" -"Current DC: pcmk-2 (2) - partition WITHOUT quorum\n" -"Version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\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" +msgid "If you are using a different cluster shell, you will have to configure corosync.conf appropriately yourself. If you are using older versions of corosync, you will have to ignore quorum at the pacemaker level, using pcs property set no-quorum-policy=ignore (or the equivalent command if you are using a different cluster shell)." msgstr "" #. Tag: para #, no-c-format -msgid "Now simulate node recovery by restarting the cluster stack on pcmk-1 and check the cluster’s status. Note, if you get an authentication error with the pcs cluster start pcmk-1 command, you must authenticate on the node using the pcs cluster auth pcmk pcmk-1 pcmk-2 command discussed earlier." +msgid "Now, simulate node recovery by restarting the cluster stack on pcmk-1, 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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster start pcmk-1\n" -"Starting Cluster...\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 10:42:56 2012\n" -"Last change: Fri Sep 14 10:37:53 2012 via cibadmin on pcmk-2\n" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"1 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"1 Resources configured\n" +"\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" "Full list of resources:\n" "\n" -" ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2" +" 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 "In the dark days, the cluster may have moved the IP back to its original location (pcmk-1). Usually this is no longer the case." +msgid "With older versions of pacemaker, the cluster might move the IP back to its original location (pcmk-1). 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 like Oracle databases, this period can be quite long." +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 stickiness which controls how much 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\" It should be noted that 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 resource placement. We can specify a different stickiness for every resource, but it is often sufficient to change the default." +msgid "To address this, Pacemaker has the concept of resource stickiness, 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\" 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. resource placement. We can specify a different stickiness for every resource, but it is often sufficient to change the default." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource rsc defaults resource-stickiness=100\n" -"# pcs resource rsc defaults\n" +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 pcs required that rsc be added after resource 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 55cf7ee1d2..966ef24efe 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Apache.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Apache.pot @@ -1,493 +1,490 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Apache - Adding More Services" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Forward" +msgid "Add Apache as a Cluster Service" 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 because its a feature of many clusters and relatively simple to configure." +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 because it is a feature of many clusters and relatively simple to configure." msgstr "" #. Tag: title #, no-c-format -msgid "Installation" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# yum install -y httpd wget" +msgid "# yum install -y httpd wget\n" +"# firewall-cmd --permanent --add-service=http\n" +"# firewall-cmd --reload" msgstr "" -#. Tag: literallayout +#. Tag: para #, no-c-format -msgid "Loaded plugins: langpacks, presto, refresh-packagekit\n" -"fedora/metalink | 2.6 kB 00:00\n" -"updates/metalink | 3.2 kB 00:00\n" -"updates-testing/metalink | 41 kB 00:00\n" -"Resolving Dependencies\n" -"--> Running transaction check\n" -"---> Package httpd.x86_64 0:2.2.22-3.fc17 will be installed\n" -"--> Processing Dependency: httpd-tools = 2.2.22-3.fc17 for package: httpd-2.2.22-3.fc17.x86_64\n" -"--> Processing Dependency: apr-util-ldap for package: httpd-2.2.22-3.fc17.x86_64\n" -"--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.2.22-3.fc17.x86_64\n" -"--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.2.22-3.fc17.x86_64\n" -"--> Running transaction check\n" -"---> Package apr.x86_64 0:1.4.6-1.fc17 will be installed\n" -"---> Package apr-util.x86_64 0:1.4.1-2.fc17 will be installed\n" -"---> Package apr-util-ldap.x86_64 0:1.4.1-2.fc17 will be installed\n" -"---> Package httpd-tools.x86_64 0:2.2.22-3.fc17 will be installed\n" -"--> Finished Dependency Resolution\n" -"\n" -"Dependencies Resolved\n" -"\n" -"=====================================================================================\n" -" Package Arch Version Repository Size\n" -"=====================================================================================\n" -"Installing:\n" -" httpd x86_64 2.2.22-3.fc17 updates-testing 823 k\n" -" wget x86_64 1.13.4-2.fc17 fedora 495 k\n" -"Installing for dependencies:\n" -" apr x86_64 1.4.6-1.fc17 fedora 99 k\n" -" apr-util x86_64 1.4.1-2.fc17 fedora 78 k\n" -" apr-util-ldap x86_64 1.4.1-2.fc17 fedora 17 k\n" -" httpd-tools x86_64 2.2.22-3.fc17 updates-testing 74 k\n" -"\n" -"Transaction Summary\n" -"=====================================================================================\n" -"Install 1 Package (+4 Dependent packages)\n" -"\n" -"Total download size: 1.1 M\n" -"Installed size: 3.5 M\n" -"Downloading Packages:\n" -"(1/6): apr-1.4.6-1.fc17.x86_64.rpm | 99 kB 00:00\n" -"(2/6): apr-util-1.4.1-2.fc17.x86_64.rpm | 78 kB 00:00\n" -"(3/6): apr-util-ldap-1.4.1-2.fc17.x86_64.rpm | 17 kB 00:00\n" -"(4/6): httpd-2.2.22-3.fc17.x86_64.rpm | 823 kB 00:01\n" -"(5/6): httpd-tools-2.2.22-3.fc17.x86_64.rpm | 74 kB 00:00\n" -"(6/6): wget-1.13.4-2.fc17.x86_64.rpm | 495 kB 00:01\n" -"-------------------------------------------------------------------------------------\n" -"Total 238 kB/s | 1.1 MB 00:04\n" -"Running Transaction Check\n" -"Running Transaction Test\n" -"Transaction Test Succeeded\n" -"Running Transaction\n" -" Installing : apr-1.4.6-1.fc17.x86_64 1/6\n" -" Installing : apr-util-1.4.1-2.fc17.x86_64 2/6\n" -" Installing : apr-util-ldap-1.4.1-2.fc17.x86_64 3/6\n" -" Installing : httpd-tools-2.2.22-3.fc17.x86_64 4/6\n" -" Installing : httpd-2.2.22-3.fc17.x86_64 5/6\n" -" Installing : wget-1.13.4-2.fc17.x86_64 6/6\n" -" Verifying : apr-util-ldap-1.4.1-2.fc17.x86_64 1/6\n" -" Verifying : httpd-tools-2.2.22-3.fc17.x86_64 2/6\n" -" Verifying : apr-util-1.4.1-2.fc17.x86_64 3/6\n" -" Verifying : apr-1.4.6-1.fc17.x86_64 4/6\n" -" Verifying : httpd-2.2.22-3.fc17.x86_64 5/6\n" -" Verifying : wget-1.13.4-2.fc17.x86_64 6/6\n" -"\n" -"Installed:\n" -" httpd.x86_64 0:2.2.22-3.fc17 wget.x86_64 0:1.13.4-2.fc17\n" -"\n" -"Dependency Installed:\n" -" apr.x86_64 0:1.4.6-1.fc17 apr-util.x86_64 0:1.4.1-2.fc17\n" -" apr-util-ldap.x86_64 0:1.4.1-2.fc17 httpd-tools.x86_64 0:2.2.22-3.fc17\n" -"\n" -"Complete!" +msgid "Do not 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 "Preparation" +msgid "Create Website Documents" msgstr "" #. Tag: para #, no-c-format -msgid "First we need to create a page for Apache to serve up. On Fedora the default Apache docroot is /var/www/html, so we’ll create an index file there." +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: programlisting +#. Tag: screen #, no-c-format msgid "# cat <<-END >/var/www/html/index.html\n" " <html>\n" -" <body>My Test Site - pcmk-1</body>\n" +" <body>My Test Site - $(hostname)</body>\n" " </html>\n" "END" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "For the moment, we will simplify things by serving up only a static site and manually sync the data between the two nodes. So run the command again on pcmk-2." +msgid "Enable the Apache status URL" msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "[root@pcmk-2 ~]# cat <<-END >/var/www/html/index.html <html>\n" -" <body>My Test Site - pcmk-2</body>\n" -" </html>\n" -" END" +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: title +#. Tag: screen #, no-c-format -msgid "Enable the Apache status URL" +msgid "# cat <<-END >/etc/httpd/conf.d/status.conf\n" +" <Location /server-status>\n" +" SetHandler server-status\n" +" Order deny,allow\n" +" Deny from all\n" +" Allow from 127.0.0.1\n" +" </Location>\n" +"END" 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. Look for the following in /etc/httpd/conf/httpd.conf and make sure it is not disabled or commented out:" -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "<Location /server-status>\n" -" SetHandler server-status\n" -" Order deny,allow\n" -" Deny from all\n" -" Allow from 127.0.0.1\n" -"</Location>" +msgid "If you are using a different operating system, server-status may already be enabled or may be configurable in a different location." msgstr "" #. Tag: title #, no-c-format -msgid "Update the Configuration" +msgid "Configure the Cluster" msgstr "" #. Tag: para #, no-c-format -msgid "At this point, Apache is ready to go, all that needs to be done is to add it to the cluster. Lets call the resource WebSite. We need to use an OCF script called apache in the heartbeat namespace Compare the key used here ocf:heartbeat:apache with the one we used earlier for the IP address: ocf:heartbeat:IPaddr2 , the 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." +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. Compare the key used here, ocf:heartbeat:apache, with the one we used earlier for the IP address, ocf:heartbeat:IPaddr2 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 "pcs resource create WebSite ocf:heartbeat:apache \\\n" +msgid "[root@pcmk-1 ~]# pcs resource create WebSite ocf:heartbeat:apache \\\n" " configfile=/etc/httpd/conf/httpd.conf \\\n" -" statusurl=\"http://localhost/server-status\" op monitor interval=1min" +" statusurl=\"http://localhost/server-status\" \\\n" +" op monitor interval=1min" msgstr "" #. Tag: para #, no-c-format -msgid "By default, the operation timeout for all resource’s start, stop, and monitor operations is 20 seconds. In many cases this timeout period is less than the advised timeout period. For the purposes of this tutorial, we will adjust the global operation timeout default to 240 seconds." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs resource op defaults timeout=240s\n" -"# pcs resource op defaults\n" +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 "After a short delay, we should see the cluster start apache" +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: programlisting +#. Tag: para #, no-c-format -msgid "# pcs status\n" -"\n" -"Last updated: Fri Sep 14 10:51:27 2012\n" -"Last change: Fri Sep 14 10:50:46 2012 via crm_attribute on pcmk-1\n" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"2 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"2 Resources configured\n" +"\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" +" 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 pcs status output, you see the WebSite resource has failed to start, then you’ve likely not enabled the status URL correctly. You can check if this is the problem by running:" +msgid "If, in the pcs status 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 http://127.0.0.1/server-status" +msgid "wget -O - http://127.0.0.1/server-status" msgstr "" #. Tag: para #, no-c-format -msgid "If you see Connection refused in the output, then this is indeed the problem. Check to ensure that Allow from 127.0.0.1 is present for the <Location /server-status> block." +msgid "If you see Connection refused in the output, then this is likely the problem. Ensure that Allow from 127.0.0.1 is present for the <Location /server-status> block." msgstr "" #. Tag: title #, no-c-format -msgid "Ensuring Resources Run on the Same Host" +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." +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 colocation constraint 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." +msgid "To achieve this, we use a colocation constraint 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 WebSite needs to be placed on the same machine as ClusterIP, this implies that we must know the location of ClusterIP before choosing a location for WebSite." +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 WebSite needs to be placed on the same machine as ClusterIP, which implies that the cluster must know the location of ClusterIP before choosing a location for WebSite." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs constraint colocation add WebSite ClusterIP INFINITY\n" -"# pcs constraint\n" +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\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 11:00:44 2012\n" -"Last change: Fri Sep 14 11:00:25 2012 via cibadmin on pcmk-1\n" +" WebSite with ClusterIP (score:INFINITY)\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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"2 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"2 Resources configured\n" +"\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" +" 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 "Controlling Resource Start/Stop Ordering" +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 "When Apache starts, it binds to the available IP addresses. It doesn’t know about any addresses we add afterwards, so not only do they need to run on the same node, but we need to make sure ClusterIP is already active before we start WebSite. We do this by adding an ordering constraint." +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 "By default all order constraints are mandatory constraints unless otherwise configured. This means that the recovery of ClusterIP will also trigger the recovery of WebSite." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs constraint order ClusterIP then WebSite\n" +msgid "[root@pcmk-1 ~]# pcs constraint order ClusterIP then WebSite\n" "Adding ClusterIP WebSite (kind: Mandatory) (Options: first-action=start then-action=start)\n" -"# pcs constraint\n" +"[root@pcmk-1 ~]# pcs constraint\n" "Location Constraints:\n" "Ordering Constraints:\n" -" start ClusterIP then start WebSite\n" +" start ClusterIP then start WebSite (kind:Mandatory)\n" "Colocation Constraints:\n" -" WebSite with ClusterIP" +" WebSite with ClusterIP (score:INFINITY)" msgstr "" #. Tag: title #, no-c-format -msgid "Specifying a Preferred Location" +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 there if it is available. To do this we create a location constraint." +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. The score here indicates how badly we’d like the resource to run somewhere." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs constraint location WebSite prefers pcmk-1=50\n" -"# pcs constraint\n" +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\n" +" start ClusterIP then start WebSite (kind:Mandatory)\n" "Colocation Constraints:\n" -" WebSite with ClusterIP\n" -"# pcs status\n" -"Last updated: Fri Sep 14 11:06:37 2012\n" -"Last change: Fri Sep 14 11:06:26 2012 via cibadmin on pcmk-1\n" +" WebSite with ClusterIP (score:INFINITY)\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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"2 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"2 Resources configured\n" +"\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" +" 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 we now prefer pcmk-1 over pcmk-2, that preference is (intentionally) less than the resource stickiness (how much we preferred not to have unnecessary downtime)." +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" +msgid "To see the current placement scores, you can use a tool called crm_simulate." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_simulate -sL\n" +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" +" 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 "Manually Moving Resources Around the Cluster" +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. By updating our previous location constraint with a score of INFINITY, WebSite will be forced to move to pcmk-1." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs constraint location WebSite prefers pcmk-1=INFINITY\n" -"# pcs constraint all\n" +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) (id:location-WebSite-pcmk-1-INFINITY)\n" +" Enabled on: pcmk-1 (score:INFINITY)\n" "Ordering Constraints:\n" -" start ClusterIP then start WebSite (Mandatory) (id:order-ClusterIP-WebSite-mandatory)\n" +" start ClusterIP then start WebSite (kind:Mandatory)\n" "Colocation Constraints:\n" -" WebSite with ClusterIP (INFINITY) (id:colocation-WebSite-ClusterIP-INFINITY)\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 11:16:26 2012\n" -"Last change: Fri Sep 14 11:16:18 2012 via cibadmin on pcmk-1\n" +" WebSite with ClusterIP (score:INFINITY)\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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"2 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"2 Resources configured\n" +"\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" +" 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: title +#. Tag: para #, no-c-format -msgid "Giving Control Back to the Cluster" +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 "Once we’ve finished whatever activity that required us to move the resources to pcmk-1, in our case nothing, we can then allow the cluster to resume normal operation with the unmove command. Since we previously configured a default stickiness, the resources will remain on pcmk-1." +msgid "First, use the --full option to get the constraint’s ID:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs constraint all\n" +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 (Mandatory) (id:order-ClusterIP-WebSite-mandatory)\n" +" start ClusterIP then start WebSite (kind:Mandatory) (id:order-ClusterIP-WebSite-mandatory)\n" "Colocation Constraints:\n" -" WebSite with ClusterIP (INFINITY) (id:colocation-WebSite-ClusterIP-INFINITY)\n" -"# pcs constraint rm location-WebSite-pcmk-1-INFINITY\n" -"# pcs constraint\n" +" WebSite with ClusterIP (score:INFINITY) (id:colocation-WebSite-ClusterIP-INFINITY)" +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\n" +" start ClusterIP then start WebSite (kind:Mandatory)\n" "Colocation Constraints:\n" -" WebSite with ClusterIP" +" WebSite with ClusterIP (score:INFINITY)" msgstr "" #. Tag: para #, no-c-format -msgid "Note that the 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." +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: programlisting +#. Tag: screen #, no-c-format msgid "# pcs status\n" -"\n" -"Last updated: Fri Sep 14 11:57:12 2012\n" -"Last change: Fri Sep 14 11:57:03 2012 via cibadmin on pcmk-1\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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"2 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"2 Resources configured\n" +"\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" +" 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 d66ca3d684..396fb7042c 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Installation.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Installation.pot @@ -1,1170 +1,712 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "OS Installation" +msgid "Install &DISTRO; &DISTRO_VERSION;" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "Detailed instructions for installing Fedora are available at http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ in a number of languages. The abbreviated version is as follows…" +msgid "Boot the Install Image" msgstr "" #. Tag: para #, no-c-format -msgid "Point your browser to http://fedoraproject.org/en/get-fedora-all, locate the Install Media section and download the install DVD that matches your hardware." +msgid "Download the 4GB &DISTRO; &DISTRO_VERSION; DVD ISO. 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 "Burn the disk image to a DVD http://docs.fedoraproject.org/en-US/Fedora/16/html/Burning_ISO_images_to_disc/index.html and boot from it, or use the image to boot a virtual machine." +msgid "After starting the installation, select your language and keyboard layout at the welcome screen." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "After clicking through the welcome screen, select your language, keyboard layout http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/sn-keyboard-x86.html and storage type http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/Storage_Devices-x86.html" +msgid "&DISTRO; &DISTRO_VERSION; Installation Welcome Screen" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "Assign your machine a host name. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/sn-Netconfig-x86.html I happen to control the clusterlabs.org domain name, so I will use that here." +msgid "Installation Options" msgstr "" #. Tag: para #, no-c-format -msgid "Do not accept the default network settings. Cluster machines should never obtain an IP address via DHCP." +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 "When you are presented with the Configure Network advanced option, select that option before continuing with the installation process to specify a fixed IPv4 address for System eth0. Be sure to also enter the Routes section and add an entry for your default gateway." +msgid "Ignore the SOFTWARE SELECTION section (try saying that 10 times quickly). The Infrastructure Server environment does have add-ons with much of the software we need, but we will leave it as a Minimal Install here, so that we can see exactly what software is required later." msgstr "" -#. Tag: phrase +#. Tag: title #, no-c-format -msgid "Custom network settings" +msgid "Configure Network" msgstr "" #. Tag: para #, no-c-format -msgid "If you miss this step, this can easily be configured after installation. You will have to navigate to system settings and select network. From there you can select what device to configure." +msgid "In the NETWORK & HOSTNAME section:" msgstr "" #. Tag: para #, no-c-format -msgid "You will then be prompted to indicate the machine’s physical location http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-timezone-x86.html and to supply a root password. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/sn-account_configuration-x86.html" +msgid "Edit Host Name: as desired. For this example, we will use pcmk-1.localdomain." msgstr "" #. Tag: para #, no-c-format -msgid "Now select where you want Fedora installed. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-diskpartsetup-x86.html As I don’t care about any existing data, I will accept the default and allow Fedora to use the complete drive." +msgid "Select your network device, press Configure…, and manually assign a fixed IP address. For this example, we’ll use 192.168.122.101 under IPv4 Settings (with an appropriate netmask, gateway and DNS server)." msgstr "" #. Tag: para #, no-c-format -msgid "By default Fedora uses LVM for partitioning which allows us to dynamically change the amount of space allocated to a given partition." +msgid "Flip the switch to turn your network device on." msgstr "" #. Tag: para #, no-c-format -msgid "However, by default it also allocates all free space to the / (aka. root) partition which cannot be dynamically reduced in size (dynamic increases are fine by-the-way)." +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 "So if you plan on following the DRBD or GFS2 portions of this guide, you should reserve at least 1Gb of space on each machine from which to create a shared volume. To do so select the Review and modify partitioning layout checkbox before clicking Next. You will then be given an opportunity to reduce the size of the root partition." +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 / (aka. root) partition, which cannot be reduced in size later (dynamic increases are fine)." msgstr "" #. Tag: para #, no-c-format -msgid "Next choose which software should be installed. http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-pkgselection-x86.html Change the selection to Minimal so that we see everything that gets installed. Don’t enable updates yet, we’ll do that (and install any extra software we need) later. After you click next, Fedora will begin installing." +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 "Go grab something to drink, this may take a while." +msgid "Enter the INSTALLATION DESTINATION section, ensure the hard drive you want to install to is selected, select I will configure partitioning, and press Done." msgstr "" #. Tag: para #, no-c-format -msgid "Once the node reboots, you’ll see a (possibly mangled) login prompt on the console. Login using root and the password you created earlier." +msgid "In the MANUAL PARTITIONING screen that comes next, click the option to create mountpoints automatically. Select the / mountpoint, and reduce the desired capacity by 1GiB or so. Select Modify… by the volume group name, and change the Size policy: to As large as possible, to make the reclaimed space available inside the LVM volume group. We’ll add the additional volume later." msgstr "" -#. Tag: phrase +#. Tag: title #, no-c-format -msgid "Initial Console" +msgid "Configure Time Synchronization" msgstr "" #. Tag: para #, no-c-format -msgid "From here on in we’re going to be working exclusively from the terminal." +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 TIME & DATE section." msgstr "" #. Tag: title #, no-c-format -msgid "Post Installation Tasks" +msgid "Finish Install" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Select Begin Installation. 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 root and the password you created earlier." msgstr "" #. Tag: title #, no-c-format -msgid "Networking" +msgid "&DISTRO; &DISTRO_VERSION; Console Prompt" msgstr "" #. Tag: para #, no-c-format -msgid "Bring up the network and ensure it starts at boot" +msgid "From here on, we’re going to be working exclusively from the terminal." msgstr "" -#. Tag: programlisting +#. Tag: title #, no-c-format -msgid "# service network start\n" -"# chkconfig network on" +msgid "Configure the OS" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Verify Networking" msgstr "" #. Tag: para #, no-c-format -msgid "Check the machine has the static IP address you configured earlier" +msgid "Ensure that the machine has the static IP address you configured earlier." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# ip addr\n" -"1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN\n" +msgid "[root@pcmk-1 ~]# ip addr\n" +"1: lo: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 "Now check the default route setting:" +msgid "If you ever need to change the node’s IP address from the command line, follow" msgstr "" -#. Tag: programlisting +#. 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 NetworkManager 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\n" -"192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.101" +"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 default via, then you may need to add a line such as" +msgid "If there is no line beginning with default via, then you may need to add a line such as" msgstr "" #. Tag: programlisting #, no-c-format -msgid "GATEWAY=192.168.122.1" +msgid "GATEWAY=\"192.168.122.1\"" msgstr "" #. Tag: para #, no-c-format -msgid "to /etc/sysconfig/network and restart the network." +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 if we can read the gateway we configured." +msgid "Now, check for connectivity to the outside world. Start small by testing whether we can reach the gateway we configured." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# ping -c 1 192.168.122.1\n" +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" +" --- 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 will be available." +msgid "Now try something external; choose a location you know should be available." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# ping -c 1 www.google.com\n" +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" +" --- 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 "Leaving the Console" +msgid "Login Remotely" msgstr "" #. Tag: para #, no-c-format -msgid "The console isn’t a very friendly place to work from, we will now switch to accessing the machine remotely via SSH where we can use copy&paste etc." +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 "First we check we can see the newly installed at all:" +msgid "From another host, check whether we can see the new host at all:" msgstr "" -#. Tag: programlisting +#. 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 we login via SSH" +msgid "Next, login as root via SSH." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "beekhof@f16 ~ # ssh -l root 192.168.122.11\n" -"root@192.168.122.11's password:\n" -"Last login: Fri Mar 30 19:41:19 2012 from 192.168.122.1\n" +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 "Security Shortcuts" +msgid "Apply Updates" msgstr "" #. Tag: para #, no-c-format -msgid "To simplify this guide and focus on the aspects directly connected to clustering, we will now disable the machine’s firewall and SELinux installation." +msgid "Apply any package updates released since your installation image was created:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Both of these actions create significant security issues and should not be performed on machines that will be exposed to the outside world." -msgstr "" - -#. Tag: literallayout -#, no-c-format -msgid "TODO: Create an Appendix that deals with (at least) re-enabling the firewall." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# setenforce 0\n" -"# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" -"# systemctl disable iptables.service\n" -"# rm '/etc/systemd/system/basic.target.wants/iptables.service'\n" -"# systemctl stop iptables.service" +msgid "[root@pcmk-1 ~]# yum update" msgstr "" #. Tag: title #, no-c-format -msgid "Short Node Names" +msgid "Use Short Node Names" msgstr "" #. Tag: para #, no-c-format -msgid "During installation, we filled in the machine’s fully qualifier 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: Nodesshort name short name " +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: Nodesshort name short name " msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# uname -n\n" -"pcmk-1.clusterlabs.org\n" -"# dnsdomainname\n" -"clusterlabs.org" +msgid "[root@pcmk-1 ~]# uname -n\n" +"pcmk-1.localdomain" msgstr "" #. Tag: para #, no-c-format msgid " NodesDomain name (Query) Domain name (Query) " msgstr "" #. Tag: para #, no-c-format -msgid "The output from the second command is fine, but we really don’t need the domain name included in the basic host details. To address this, we need to update /etc/sysconfig/network. This is what it should look like before we start." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# cat /etc/sysconfig/network\n" -"NETWORKING=yes\n" -"HOSTNAME=pcmk-1.clusterlabs.org\n" -"GATEWAY=192.168.122.1" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "All we need to do now is strip off the domain name portion, which is stored elsewhere anyway." +msgid "We can use the hostnamectl tool to strip off the domain name:" msgstr "" -#. Tag: programlisting -#, no-c-format -msgid " # sed -i.sed 's/\\.[a-z].*//g' /etc/sysconfig/network" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Now confirm the change was successful. The revised file contents should look something like this." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# cat /etc/sysconfig/network\n" -"NETWORKING=yes\n" -"HOSTNAME=pcmk-1\n" -"GATEWAY=192.168.122.1" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "However we’re not finished. The machine wont normally see the shortened host name until about it reboots, but we can force it to update." -msgstr "" - -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# source /etc/sysconfig/network\n" -"# hostname $HOSTNAME" +msgid "[root@pcmk-1 ~]# hostnamectl set-hostname $(uname -n | sed s/\\\\..*//)" msgstr "" #. Tag: para #, no-c-format msgid " NodesDomain name (Remove from host name) Domain name (Remove from host name) " msgstr "" #. Tag: para #, no-c-format -msgid "Now check the machine is using the correct names" +msgid "Now, check that the machine is using the correct name:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# uname -n\n" -"pcmk-1\n" -"# dnsdomainname\n" -"clusterlabs.org" +msgid "[root@pcmk-1 ~]# uname -n\n" +"pcmk-1" msgstr "" #. Tag: title #, no-c-format -msgid "NTP" +msgid "Repeat for Second Node" 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. http://docs.fedoraproject.org/en-US/Fedora/17/html-single/System_Administrators_Guide/index.html#ch-Configuring_the_Date_and_Time" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Before You Continue" +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 "Repeat the Installation steps so far, so that you have two Fedora nodes ready to have the cluster software installed." +msgid "For the purposes of this document, the additional node is called pcmk-2 with address 192.168.122.102." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "For the purposes of this document, the additional node is called pcmk-2 with address 192.168.122.102." +msgid "Configure Communication Between Nodes" msgstr "" #. Tag: title #, no-c-format -msgid "Finalize Networking" +msgid "Configure Host Name Resolution" msgstr "" #. Tag: para #, no-c-format msgid "Confirm that you can communicate between the two new nodes:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# ping -c 3 192.168.122.102\n" +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 /etc/hosts . Below are the entries for my cluster nodes:" +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 /etc/hosts on both nodes. Below are the entries for my cluster nodes:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# grep pcmk /etc/hosts\n" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# ping -c 3 pcmk-2\n" +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 " SSH " 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." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# ssh-keygen -t dsa -f ~/.ssh/id_dsa -N \"\"\n" +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" -"\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" -"\n" -"# cp .ssh/id_dsa.pub .ssh/authorized_keys" +"[root@pcmk-1 ~]# cp ~/.ssh/id_dsa.pub ~/.ssh/authorized_keys" msgstr "" #. Tag: para #, no-c-format msgid " Creating and Activating a new SSH Key " msgstr "" #. Tag: para #, no-c-format -msgid "Install the key on the other nodes and test that you can now run commands remotely, without being prompted" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Installing the SSH Key on Another Host" +msgid "Install the key on the other node:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# scp -r .ssh pcmk-2:\n" +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" -"RSA key fingerprint is b1:2b:55:93:f1:d9:52:2b:0f:f2:8a:4e:ae:c6:7c:9a.\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' (RSA) to the list of known hosts.root@pcmk-2's password:\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\n" -"# ssh pcmk-2 -- uname -n\n" -"pcmk-2\n" -"#" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Cluster Software Installation" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Install the Cluster Software" +"authorized_keys 100% 616 0.6KB/s 00:00" msgstr "" #. Tag: para #, no-c-format -msgid "Since version 12, Fedora comes with recent versions of everything you need, so simply fire up the shell and run:" +msgid "Test that you can now run commands remotely, without being prompted:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# yum install -y pacemaker corosync" +msgid "[root@pcmk-1 ~]# ssh pcmk-2 -- uname -n\n" +"pcmk-2" msgstr "" -#. Tag: literallayout +#. Tag: title #, no-c-format -msgid "fedora/metalink | 38 kB 00:00\n" -"fedora | 4.2 kB 00:00\n" -"fedora/primary_db | 14 MB 00:21\n" -"updates/metalink | 2.7 kB 00:00\n" -"updates | 2.6 kB 00:00\n" -"updates/primary_db | 1.2 kB 00:00\n" -"updates-testing/metalink | 28 kB 00:00\n" -"updates-testing | 4.5 kB 00:00\n" -"updates-testing/primary_db | 4.5 MB 00:12\n" -"Setting up Install Process\n" -"Resolving Dependencies\n" -"--> Running transaction check\n" -"---> Package corosync.x86_64 0:1.99.9-1.fc17 will be installed\n" -"--> Processing Dependency: corosynclib = 1.99.9-1.fc17 for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libxslt for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libvotequorum.so.5(COROSYNC_VOTEQUORUM_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libquorum.so.5(COROSYNC_QUORUM_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcpg.so.4(COROSYNC_CPG_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcmap.so.4(COROSYNC_CMAP_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcfg.so.6(COROSYNC_CFG_0.82)(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libvotequorum.so.5()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libtotem_pg.so.5()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libquorum.so.5()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libqb.so.0()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libnetsnmp.so.30()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcpg.so.4()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcorosync_common.so.4()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcmap.so.4()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libcfg.so.6()(64bit) for package: corosync-1.99.9-1.fc17.x86_64\n" -"---> Package pacemaker.x86_64 0:1.1.7-2.fc17 will be installed\n" -"--> Processing Dependency: pacemaker-libs = 1.1.7-2.fc17 for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: pacemaker-cluster-libs = 1.1.7-2.fc17 for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: pacemaker-cli = 1.1.7-2.fc17 for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: resource-agents for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: perl(Getopt::Long) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: cluster-glue for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: /usr/bin/perl for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libtransitioner.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libstonithd.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libstonith.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libplumb.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libpils.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libpengine.so.3()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libpe_status.so.3()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libpe_rules.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libltdl.so.7()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: liblrm.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libgnutls.so.26()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libcrmcommon.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libcrmcluster.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Processing Dependency: libcib.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64\n" -"--> Running transaction check\n" -"---> Package cluster-glue.x86_64 0:1.0.6-9.fc17.1 will be installed\n" -"--> Processing Dependency: perl-TimeDate for package: cluster-glue-1.0.6-9.fc17.1.x86_64\n" -"--> Processing Dependency: libOpenIPMIutils.so.0()(64bit) for package: cluster-glue-1.0.6-9.fc17.1.x86_64\n" -"--> Processing Dependency: libOpenIPMIposix.so.0()(64bit) for package: cluster-glue-1.0.6-9.fc17.1.x86_64\n" -"--> Processing Dependency: libOpenIPMI.so.0()(64bit) for package: cluster-glue-1.0.6-9.fc17.1.x86_64\n" -"---> Package cluster-glue-libs.x86_64 0:1.0.6-9.fc17.1 will be installed\n" -"---> Package corosynclib.x86_64 0:1.99.9-1.fc17 will be installed\n" -"--> Processing Dependency: librdmacm.so.1(RDMACM_1.0)(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libibverbs.so.1(IBVERBS_1.1)(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libibverbs.so.1(IBVERBS_1.0)(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: librdmacm.so.1()(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64\n" -"--> Processing Dependency: libibverbs.so.1()(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64\n" -"---> Package gnutls.x86_64 0:2.12.17-1.fc17 will be installed\n" -"--> Processing Dependency: libtasn1.so.3(LIBTASN1_0_3)(64bit) for package: gnutls-2.12.17-1.fc17.x86_64\n" -"--> Processing Dependency: libtasn1.so.3()(64bit) for package: gnutls-2.12.17-1.fc17.x86_64\n" -"--> Processing Dependency: libp11-kit.so.0()(64bit) for package: gnutls-2.12.17-1.fc17.x86_64\n" -"---> Package libqb.x86_64 0:0.11.1-1.fc17 will be installed\n" -"---> Package libtool-ltdl.x86_64 0:2.4.2-3.fc17 will be installed\n" -"---> Package libxslt.x86_64 0:1.1.26-9.fc17 will be installed\n" -"---> Package net-snmp-libs.x86_64 1:5.7.1-4.fc17 will be installed\n" -"---> Package pacemaker-cli.x86_64 0:1.1.7-2.fc17 will be installed\n" -"---> Package pacemaker-cluster-libs.x86_64 0:1.1.7-2.fc17 will be installed\n" -"---> Package pacemaker-libs.x86_64 0:1.1.7-2.fc17 will be installed\n" -"---> Package perl.x86_64 4:5.14.2-211.fc17 will be installed\n" -"--> Processing Dependency: perl-libs = 4:5.14.2-211.fc17 for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(threads::shared) >= 1.21 for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Socket) >= 1.3 for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Scalar::Util) >= 1.10 for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(File::Spec) >= 0.8 for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl-macros for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl-libs for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(threads::shared) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(threads) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Socket) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Scalar::Util) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Pod::Simple) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Module::Pluggable) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(List::Util) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(File::Spec::Unix) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(File::Spec::Functions) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(File::Spec) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Cwd) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: perl(Carp) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"--> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.14.2-211.fc17.x86_64\n" -"---> Package resource-agents.x86_64 0:3.9.2-2.fc17.1 will be installed\n" -"--> Processing Dependency: /usr/sbin/rpc.nfsd for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /usr/sbin/rpc.mountd for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /usr/sbin/ethtool for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/rpc.statd for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/quotaon for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/quotacheck for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/mount.nfs4 for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/mount.nfs for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/mount.cifs for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: /sbin/fsck.xfs for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Processing Dependency: libnet.so.1()(64bit) for package: resource-agents-3.9.2-2.fc17.1.x86_64\n" -"--> Running transaction check\n" -"---> Package OpenIPMI-libs.x86_64 0:2.0.18-13.fc17 will be installed\n" -"---> Package cifs-utils.x86_64 0:5.3-2.fc17 will be installed\n" -"--> Processing Dependency: libtalloc.so.2(TALLOC_2.0.2)(64bit) for package: cifs-utils-5.3-2.fc17.x86_64\n" -"--> Processing Dependency: keyutils for package: cifs-utils-5.3-2.fc17.x86_64\n" -"--> Processing Dependency: libwbclient.so.0()(64bit) for package: cifs-utils-5.3-2.fc17.x86_64\n" -"--> Processing Dependency: libtalloc.so.2()(64bit) for package: cifs-utils-5.3-2.fc17.x86_64\n" -"---> Package ethtool.x86_64 2:3.2-2.fc17 will be installed\n" -"---> Package libibverbs.x86_64 0:1.1.6-2.fc17 will be installed\n" -"---> Package libnet.x86_64 0:1.1.5-3.fc17 will be installed\n" -"---> Package librdmacm.x86_64 0:1.0.15-1.fc17 will be installed\n" -"---> Package libtasn1.x86_64 0:2.12-1.fc17 will be installed\n" -"---> Package nfs-utils.x86_64 1:1.2.5-12.fc17 will be installed\n" -"--> Processing Dependency: rpcbind for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libtirpc for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libnfsidmap for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libgssglue.so.1(libgssapi_CITI_2)(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libgssglue for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libevent for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libtirpc.so.1()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libnfsidmap.so.0()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libgssglue.so.1()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"--> Processing Dependency: libevent-2.0.so.5()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64\n" -"---> Package p11-kit.x86_64 0:0.12-1.fc17 will be installed\n" -"---> Package perl-Carp.noarch 0:1.22-2.fc17 will be installed\n" -"---> Package perl-Module-Pluggable.noarch 1:3.90-211.fc17 will be installed\n" -"---> Package perl-PathTools.x86_64 0:3.33-211.fc17 will be installed\n" -"---> Package perl-Pod-Simple.noarch 1:3.16-211.fc17 will be installed\n" -"--> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.16-211.fc17.noarch\n" -"---> Package perl-Scalar-List-Utils.x86_64 0:1.25-1.fc17 will be installed\n" -"---> Package perl-Socket.x86_64 0:2.001-1.fc17 will be installed\n" -"---> Package perl-TimeDate.noarch 1:1.20-6.fc17 will be installed\n" -"---> Package perl-libs.x86_64 4:5.14.2-211.fc17 will be installed\n" -"---> Package perl-macros.x86_64 4:5.14.2-211.fc17 will be installed\n" -"---> Package perl-threads.x86_64 0:1.86-2.fc17 will be installed\n" -"---> Package perl-threads-shared.x86_64 0:1.40-2.fc17 will be installed\n" -"---> Package quota.x86_64 1:4.00-3.fc17 will be installed\n" -"--> Processing Dependency: quota-nls = 1:4.00-3.fc17 for package: 1:quota-4.00-3.fc17.x86_64\n" -"--> Processing Dependency: tcp_wrappers for package: 1:quota-4.00-3.fc17.x86_64\n" -"---> Package xfsprogs.x86_64 0:3.1.8-1.fc17 will be installed\n" -"--> Running transaction check\n" -"---> Package keyutils.x86_64 0:1.5.5-2.fc17 will be installed\n" -"---> Package libevent.x86_64 0:2.0.14-2.fc17 will be installed\n" -"---> Package libgssglue.x86_64 0:0.3-1.fc17 will be installed\n" -"---> Package libnfsidmap.x86_64 0:0.25-1.fc17 will be installed\n" -"---> Package libtalloc.x86_64 0:2.0.7-4.fc17 will be installed\n" -"---> Package libtirpc.x86_64 0:0.2.2-2.1.fc17 will be installed\n" -"---> Package libwbclient.x86_64 1:3.6.3-81.fc17.1 will be installed\n" -"---> Package perl-Pod-Escapes.noarch 1:1.04-211.fc17 will be installed\n" -"---> Package quota-nls.noarch 1:4.00-3.fc17 will be installed\n" -"---> Package rpcbind.x86_64 0:0.2.0-16.fc17 will be installed\n" -"---> Package tcp_wrappers.x86_64 0:7.6-69.fc17 will be installed\n" -"--> Finished Dependency Resolution\n" -"\n" -"Dependencies Resolved\n" -"\n" -"=====================================================================================\n" -" Package Arch Version Repository Size\n" -"=====================================================================================\n" -"Installing:\n" -" corosync x86_64 1.99.9-1.fc17 updates-testing 159 k\n" -" pacemaker x86_64 1.1.7-2.fc17 updates-testing 362 k\n" -"Installing for dependencies:\n" -" OpenIPMI-libs x86_64 2.0.18-13.fc17 fedora 466 k\n" -" cifs-utils x86_64 5.3-2.fc17 updates-testing 66 k\n" -" cluster-glue x86_64 1.0.6-9.fc17.1 fedora 229 k\n" -" cluster-glue-libs x86_64 1.0.6-9.fc17.1 fedora 121 k\n" -" corosynclib x86_64 1.99.9-1.fc17 updates-testing 96 k\n" -" ethtool x86_64 2:3.2-2.fc17 fedora 94 k\n" -" gnutls x86_64 2.12.17-1.fc17 fedora 385 k\n" -" keyutils x86_64 1.5.5-2.fc17 fedora 49 k\n" -" libevent x86_64 2.0.14-2.fc17 fedora 160 k\n" -" libgssglue x86_64 0.3-1.fc17 fedora 24 k\n" -" libibverbs x86_64 1.1.6-2.fc17 fedora 44 k\n" -" libnet x86_64 1.1.5-3.fc17 fedora 54 k\n" -" libnfsidmap x86_64 0.25-1.fc17 fedora 34 k\n" -" libqb x86_64 0.11.1-1.fc17 updates-testing 68 k\n" -" librdmacm x86_64 1.0.15-1.fc17 fedora 27 k\n" -" libtalloc x86_64 2.0.7-4.fc17 fedora 22 k\n" -" libtasn1 x86_64 2.12-1.fc17 updates-testing 319 k\n" -" libtirpc x86_64 0.2.2-2.1.fc17 fedora 78 k\n" -" libtool-ltdl x86_64 2.4.2-3.fc17 fedora 45 k\n" -" libwbclient x86_64 1:3.6.3-81.fc17.1 updates-testing 68 k\n" -" libxslt x86_64 1.1.26-9.fc17 fedora 416 k\n" -" net-snmp-libs x86_64 1:5.7.1-4.fc17 fedora 713 k\n" -" nfs-utils x86_64 1:1.2.5-12.fc17 fedora 311 k\n" -" p11-kit x86_64 0.12-1.fc17 updates-testing 36 k\n" -" pacemaker-cli x86_64 1.1.7-2.fc17 updates-testing 368 k\n" -" pacemaker-cluster-libs x86_64 1.1.7-2.fc17 updates-testing 77 k\n" -" pacemaker-libs x86_64 1.1.7-2.fc17 updates-testing 322 k\n" -" perl x86_64 4:5.14.2-211.fc17 fedora 10 M\n" -" perl-Carp noarch 1.22-2.fc17 fedora 17 k\n" -" perl-Module-Pluggable noarch 1:3.90-211.fc17 fedora 47 k\n" -" perl-PathTools x86_64 3.33-211.fc17 fedora 105 k\n" -" perl-Pod-Escapes noarch 1:1.04-211.fc17 fedora 40 k\n" -" perl-Pod-Simple noarch 1:3.16-211.fc17 fedora 223 k\n" -" perl-Scalar-List-Utils x86_64 1.25-1.fc17 updates-testing 33 k\n" -" perl-Socket x86_64 2.001-1.fc17 updates-testing 44 k\n" -" perl-TimeDate noarch 1:1.20-6.fc17 fedora 43 k\n" -" perl-libs x86_64 4:5.14.2-211.fc17 fedora 628 k\n" -" perl-macros x86_64 4:5.14.2-211.fc17 fedora 32 k\n" -" perl-threads x86_64 1.86-2.fc17 fedora 47 k\n" -" perl-threads-shared x86_64 1.40-2.fc17 fedora 36 k\n" -" quota x86_64 1:4.00-3.fc17 fedora 160 k\n" -" quota-nls noarch 1:4.00-3.fc17 fedora 74 k\n" -" resource-agents x86_64 3.9.2-2.fc17.1 fedora 466 k\n" -" rpcbind x86_64 0.2.0-16.fc17 fedora 52 k\n" -" tcp_wrappers x86_64 7.6-69.fc17 fedora 72 k\n" -" xfsprogs x86_64 3.1.8-1.fc17 updates-testing 715 k\n" -"\n" -"Transaction Summary\n" -"=====================================================================================\n" -"Install 2 Packages (+46 Dependent packages)\n" -"\n" -"Total download size: 18 M\n" -"Installed size: 59 M\n" -"Downloading Packages:\n" -"(1/48): OpenIPMI-libs-2.0.18-13.fc17.x86_64.rpm | 466 kB 00:00\n" -"warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 1aca3465: NOKEY\n" -"Public key for OpenIPMI-libs-2.0.18-13.fc17.x86_64.rpm is not installed\n" -"(2/48): cifs-utils-5.3-2.fc17.x86_64.rpm | 66 kB 00:01\n" -"Public key for cifs-utils-5.3-2.fc17.x86_64.rpm is not installed\n" -"(3/48): cluster-glue-1.0.6-9.fc17.1.x86_64.rpm | 229 kB 00:00\n" -"(4/48): cluster-glue-libs-1.0.6-9.fc17.1.x86_64.rpm | 121 kB 00:00\n" -"(5/48): corosync-1.99.9-1.fc17.x86_64.rpm | 159 kB 00:01\n" -"(6/48): corosynclib-1.99.9-1.fc17.x86_64.rpm | 96 kB 00:00\n" -"(7/48): ethtool-3.2-2.fc17.x86_64.rpm | 94 kB 00:00\n" -"(8/48): gnutls-2.12.17-1.fc17.x86_64.rpm | 385 kB 00:00\n" -"(9/48): keyutils-1.5.5-2.fc17.x86_64.rpm | 49 kB 00:00\n" -"(10/48): libevent-2.0.14-2.fc17.x86_64.rpm | 160 kB 00:00\n" -"(11/48): libgssglue-0.3-1.fc17.x86_64.rpm | 24 kB 00:00\n" -"(12/48): libibverbs-1.1.6-2.fc17.x86_64.rpm | 44 kB 00:00\n" -"(13/48): libnet-1.1.5-3.fc17.x86_64.rpm | 54 kB 00:00\n" -"(14/48): libnfsidmap-0.25-1.fc17.x86_64.rpm | 34 kB 00:00\n" -"(15/48): libqb-0.11.1-1.fc17.x86_64.rpm | 68 kB 00:01\n" -"(16/48): librdmacm-1.0.15-1.fc17.x86_64.rpm | 27 kB 00:00\n" -"(17/48): libtalloc-2.0.7-4.fc17.x86_64.rpm | 22 kB 00:00\n" -"(18/48): libtasn1-2.12-1.fc17.x86_64.rpm | 319 kB 00:02\n" -"(19/48): libtirpc-0.2.2-2.1.fc17.x86_64.rpm | 78 kB 00:00\n" -"(20/48): libtool-ltdl-2.4.2-3.fc17.x86_64.rpm | 45 kB 00:00\n" -"(21/48): libwbclient-3.6.3-81.fc17.1.x86_64.rpm | 68 kB 00:00\n" -"(22/48): libxslt-1.1.26-9.fc17.x86_64.rpm | 416 kB 00:00\n" -"(23/48): net-snmp-libs-5.7.1-4.fc17.x86_64.rpm | 713 kB 00:01\n" -"(24/48): nfs-utils-1.2.5-12.fc17.x86_64.rpm | 311 kB 00:00\n" -"(25/48): p11-kit-0.12-1.fc17.x86_64.rpm | 36 kB 00:01\n" -"(26/48): pacemaker-1.1.7-2.fc17.x86_64.rpm | 362 kB 00:02\n" -"(27/48): pacemaker-cli-1.1.7-2.fc17.x86_64.rpm | 368 kB 00:02\n" -"(28/48): pacemaker-cluster-libs-1.1.7-2.fc17.x86_64.rpm | 77 kB 00:00\n" -"(29/48): pacemaker-libs-1.1.7-2.fc17.x86_64.rpm | 322 kB 00:01\n" -"(30/48): perl-5.14.2-211.fc17.x86_64.rpm | 10 MB 00:15\n" -"(31/48): perl-Carp-1.22-2.fc17.noarch.rpm | 17 kB 00:00\n" -"(32/48): perl-Module-Pluggable-3.90-211.fc17.noarch.rpm | 47 kB 00:00\n" -"(33/48): perl-PathTools-3.33-211.fc17.x86_64.rpm | 105 kB 00:00\n" -"(34/48): perl-Pod-Escapes-1.04-211.fc17.noarch.rpm | 40 kB 00:00\n" -"(35/48): perl-Pod-Simple-3.16-211.fc17.noarch.rpm | 223 kB 00:00\n" -"(36/48): perl-Scalar-List-Utils-1.25-1.fc17.x86_64.rpm | 33 kB 00:01\n" -"(37/48): perl-Socket-2.001-1.fc17.x86_64.rpm | 44 kB 00:00\n" -"(38/48): perl-TimeDate-1.20-6.fc17.noarch.rpm | 43 kB 00:00\n" -"(39/48): perl-libs-5.14.2-211.fc17.x86_64.rpm | 628 kB 00:00\n" -"(40/48): perl-macros-5.14.2-211.fc17.x86_64.rpm | 32 kB 00:00\n" -"(41/48): perl-threads-1.86-2.fc17.x86_64.rpm | 47 kB 00:00\n" -"(42/48): perl-threads-shared-1.40-2.fc17.x86_64.rpm | 36 kB 00:00\n" -"(43/48): quota-4.00-3.fc17.x86_64.rpm | 160 kB 00:00\n" -"(44/48): quota-nls-4.00-3.fc17.noarch.rpm | 74 kB 00:00\n" -"(45/48): resource-agents-3.9.2-2.fc17.1.x86_64.rpm | 466 kB 00:00\n" -"(46/48): rpcbind-0.2.0-16.fc17.x86_64.rpm | 52 kB 00:00\n" -"(47/48): tcp_wrappers-7.6-69.fc17.x86_64.rpm | 72 kB 00:00\n" -"(48/48): xfsprogs-3.1.8-1.fc17.x86_64.rpm | 715 kB 00:03\n" -"----------------------------------------------------------------------------------------\n" -"Total 333 kB/s | 18 MB 00:55\n" -"Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64\n" -"Importing GPG key 0x1ACA3465:\n" -" Userid : \"Fedora (17) <fedora@fedoraproject.org>\"\n" -" Fingerprint: cac4 3fb7 74a4 a673 d81c 5de7 50e9 4c99 1aca 3465\n" -" Package : fedora-release-17-0.8.noarch (@anaconda-0)\n" -" From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64\n" -"Running Transaction Check\n" -"Running Transaction Test\n" -"Transaction Test Succeeded\n" -"Running Transaction\n" -" Installing : libqb-0.11.1-1.fc17.x86_64 1/48\n" -" Installing : libtool-ltdl-2.4.2-3.fc17.x86_64 2/48\n" -" Installing : cluster-glue-libs-1.0.6-9.fc17.1.x86_64 3/48\n" -" Installing : libxslt-1.1.26-9.fc17.x86_64 4/48\n" -" Installing : 1:perl-Pod-Escapes-1.04-211.fc17.noarch 5/48\n" -" Installing : perl-threads-1.86-2.fc17.x86_64 6/48\n" -" Installing : 4:perl-macros-5.14.2-211.fc17.x86_64 7/48\n" -" Installing : 1:perl-Pod-Simple-3.16-211.fc17.noarch 8/48\n" -" Installing : perl-Socket-2.001-1.fc17.x86_64 9/48\n" -" Installing : perl-Carp-1.22-2.fc17.noarch 10/48\n" -" Installing : 4:perl-libs-5.14.2-211.fc17.x86_64 11/48\n" -" Installing : perl-threads-shared-1.40-2.fc17.x86_64 12/48\n" -" Installing : perl-Scalar-List-Utils-1.25-1.fc17.x86_64 13/48\n" -" Installing : 1:perl-Module-Pluggable-3.90-211.fc17.noarch 14/48\n" -" Installing : perl-PathTools-3.33-211.fc17.x86_64 15/48\n" -" Installing : 4:perl-5.14.2-211.fc17.x86_64 16/48\n" -" Installing : libibverbs-1.1.6-2.fc17.x86_64 17/48\n" -" Installing : keyutils-1.5.5-2.fc17.x86_64 18/48\n" -" Installing : libgssglue-0.3-1.fc17.x86_64 19/48\n" -" Installing : libtirpc-0.2.2-2.1.fc17.x86_64 20/48\n" -" Installing : 1:net-snmp-libs-5.7.1-4.fc17.x86_64 21/48\n" -" Installing : rpcbind-0.2.0-16.fc17.x86_64 22/48\n" -" Installing : librdmacm-1.0.15-1.fc17.x86_64 23/48\n" -" Installing : corosynclib-1.99.9-1.fc17.x86_64 24/48\n" -" Installing : corosync-1.99.9-1.fc17.x86_64 25/48\n" -"error reading information on service corosync: No such file or directory\n" -" Installing : 1:perl-TimeDate-1.20-6.fc17.noarch 26/48\n" -" Installing : 1:quota-nls-4.00-3.fc17.noarch 27/48\n" -" Installing : tcp_wrappers-7.6-69.fc17.x86_64 28/48\n" -" Installing : 1:quota-4.00-3.fc17.x86_64 29/48\n" -" Installing : libnfsidmap-0.25-1.fc17.x86_64 30/48\n" -" Installing : 1:libwbclient-3.6.3-81.fc17.1.x86_64 31/48\n" -" Installing : libnet-1.1.5-3.fc17.x86_64 32/48\n" -" Installing : 2:ethtool-3.2-2.fc17.x86_64 33/48\n" -" Installing : libevent-2.0.14-2.fc17.x86_64 34/48\n" -" Installing : 1:nfs-utils-1.2.5-12.fc17.x86_64 35/48\n" -" Installing : libtalloc-2.0.7-4.fc17.x86_64 36/48\n" -" Installing : cifs-utils-5.3-2.fc17.x86_64 37/48\n" -" Installing : libtasn1-2.12-1.fc17.x86_64 38/48\n" -" Installing : OpenIPMI-libs-2.0.18-13.fc17.x86_64 39/48\n" -" Installing : cluster-glue-1.0.6-9.fc17.1.x86_64 40/48\n" -" Installing : p11-kit-0.12-1.fc17.x86_64 41/48\n" -" Installing : gnutls-2.12.17-1.fc17.x86_64 42/48\n" -" Installing : pacemaker-libs-1.1.7-2.fc17.x86_64 43/48\n" -" Installing : pacemaker-cluster-libs-1.1.7-2.fc17.x86_64 44/48\n" -" Installing : pacemaker-cli-1.1.7-2.fc17.x86_64 45/48\n" -" Installing : xfsprogs-3.1.8-1.fc17.x86_64 46/48\n" -" Installing : resource-agents-3.9.2-2.fc17.1.x86_64 47/48\n" -" Installing : pacemaker-1.1.7-2.fc17.x86_64 48/48\n" -" Verifying : xfsprogs-3.1.8-1.fc17.x86_64 1/48\n" -" Verifying : 1:net-snmp-libs-5.7.1-4.fc17.x86_64 2/48\n" -" Verifying : corosync-1.99.9-1.fc17.x86_64 3/48\n" -" Verifying : cluster-glue-1.0.6-9.fc17.1.x86_64 4/48\n" -" Verifying : perl-PathTools-3.33-211.fc17.x86_64 5/48\n" -" Verifying : p11-kit-0.12-1.fc17.x86_64 6/48\n" -" Verifying : 1:perl-Pod-Simple-3.16-211.fc17.noarch 7/48\n" -" Verifying : OpenIPMI-libs-2.0.18-13.fc17.x86_64 8/48\n" -" Verifying : libtasn1-2.12-1.fc17.x86_64 9/48\n" -" Verifying : perl-threads-1.86-2.fc17.x86_64 10/48\n" -" Verifying : 1:perl-Pod-Escapes-1.04-211.fc17.noarch 11/48\n" -" Verifying : pacemaker-1.1.7-2.fc17.x86_64 12/48\n" -" Verifying : 4:perl-5.14.2-211.fc17.x86_64 13/48\n" -" Verifying : gnutls-2.12.17-1.fc17.x86_64 14/48\n" -" Verifying : perl-threads-shared-1.40-2.fc17.x86_64 15/48\n" -" Verifying : 4:perl-macros-5.14.2-211.fc17.x86_64 16/48\n" -" Verifying : 1:perl-Module-Pluggable-3.90-211.fc17.noarch 17/48\n" -" Verifying : 1:nfs-utils-1.2.5-12.fc17.x86_64 18/48\n" -" Verifying : cluster-glue-libs-1.0.6-9.fc17.1.x86_64 19/48\n" -" Verifying : pacemaker-libs-1.1.7-2.fc17.x86_64 20/48\n" -" Verifying : libtalloc-2.0.7-4.fc17.x86_64 21/48\n" -" Verifying : libevent-2.0.14-2.fc17.x86_64 22/48\n" -" Verifying : perl-Socket-2.001-1.fc17.x86_64 23/48\n" -" Verifying : libgssglue-0.3-1.fc17.x86_64 24/48\n" -" Verifying : perl-Carp-1.22-2.fc17.noarch 25/48\n" -" Verifying : libtirpc-0.2.2-2.1.fc17.x86_64 26/48\n" -" Verifying : 2:ethtool-3.2-2.fc17.x86_64 27/48\n" -" Verifying : 4:perl-libs-5.14.2-211.fc17.x86_64 28/48\n" -" Verifying : libxslt-1.1.26-9.fc17.x86_64 29/48\n" -" Verifying : rpcbind-0.2.0-16.fc17.x86_64 30/48\n" -" Verifying : librdmacm-1.0.15-1.fc17.x86_64 31/48\n" -" Verifying : resource-agents-3.9.2-2.fc17.1.x86_64 32/48\n" -" Verifying : 1:quota-4.00-3.fc17.x86_64 33/48\n" -" Verifying : 1:perl-TimeDate-1.20-6.fc17.noarch 34/48\n" -" Verifying : perl-Scalar-List-Utils-1.25-1.fc17.x86_64 35/48\n" -" Verifying : libtool-ltdl-2.4.2-3.fc17.x86_64 36/48\n" -" Verifying : pacemaker-cluster-libs-1.1.7-2.fc17.x86_64 37/48\n" -" Verifying : cifs-utils-5.3-2.fc17.x86_64 38/48\n" -" Verifying : libnet-1.1.5-3.fc17.x86_64 39/48\n" -" Verifying : corosynclib-1.99.9-1.fc17.x86_64 40/48\n" -" Verifying : libqb-0.11.1-1.fc17.x86_64 41/48\n" -" Verifying : 1:libwbclient-3.6.3-81.fc17.1.x86_64 42/48\n" -" Verifying : libnfsidmap-0.25-1.fc17.x86_64 43/48\n" -" Verifying : tcp_wrappers-7.6-69.fc17.x86_64 44/48\n" -" Verifying : keyutils-1.5.5-2.fc17.x86_64 45/48\n" -" Verifying : libibverbs-1.1.6-2.fc17.x86_64 46/48\n" -" Verifying : 1:quota-nls-4.00-3.fc17.noarch 47/48\n" -" Verifying : pacemaker-cli-1.1.7-2.fc17.x86_64 48/48\n" -"\n" -"Installed:\n" -" corosync.x86_64 0:1.99.9-1.fc17 pacemaker.x86_64 0:1.1.7-2.fc17\n" -"\n" -"Dependency Installed:\n" -" OpenIPMI-libs.x86_64 0:2.0.18-13.fc17 cifs-utils.x86_64 0:5.3-2.fc17\n" -" cluster-glue.x86_64 0:1.0.6-9.fc17.1 cluster-glue-libs.x86_64 0:1.0.6-9.fc17.1\n" -" corosynclib.x86_64 0:1.99.9-1.fc17 ethtool.x86_64 2:3.2-2.fc17\n" -" gnutls.x86_64 0:2.12.17-1.fc17 keyutils.x86_64 0:1.5.5-2.fc17\n" -" libevent.x86_64 0:2.0.14-2.fc17 libgssglue.x86_64 0:0.3-1.fc17\n" -" libibverbs.x86_64 0:1.1.6-2.fc17 libnet.x86_64 0:1.1.5-3.fc17\n" -" libnfsidmap.x86_64 0:0.25-1.fc17 libqb.x86_64 0:0.11.1-1.fc17\n" -" librdmacm.x86_64 0:1.0.15-1.fc17 libtalloc.x86_64 0:2.0.7-4.fc17\n" -" libtasn1.x86_64 0:2.12-1.fc17 libtirpc.x86_64 0:0.2.2-2.1.fc17\n" -" libtool-ltdl.x86_64 0:2.4.2-3.fc17 libwbclient.x86_64 1:3.6.3-81.fc17.1\n" -" libxslt.x86_64 0:1.1.26-9.fc17 net-snmp-libs.x86_64 1:5.7.1-4.fc17\n" -" nfs-utils.x86_64 1:1.2.5-12.fc17 p11-kit.x86_64 0:0.12-1.fc17\n" -" pacemaker-cli.x86_64 0:1.1.7-2.fc17 pacemaker-cluster-libs.x86_64 0:1.1.7-2.fc17\n" -" pacemaker-libs.x86_64 0:1.1.7-2.fc17 perl.x86_64 4:5.14.2-211.fc17\n" -" perl-Carp.noarch 0:1.22-2.fc17 perl-Module-Pluggable.noarch 1:3.90-211.fc17\n" -" perl-PathTools.x86_64 0:3.33-211.fc17 perl-Pod-Escapes.noarch 1:1.04-211.fc17\n" -" perl-Pod-Simple.noarch 1:3.16-211.fc17 perl-Scalar-List-Utils.x86_64 0:1.25-1.fc17\n" -" perl-Socket.x86_64 0:2.001-1.fc17 perl-TimeDate.noarch 1:1.20-6.fc17\n" -" perl-libs.x86_64 4:5.14.2-211.fc17 perl-macros.x86_64 4:5.14.2-211.fc17\n" -" perl-threads.x86_64 0:1.86-2.fc17 perl-threads-shared.x86_64 0:1.40-2.fc17\n" -" quota.x86_64 1:4.00-3.fc17 quota-nls.noarch 1:4.00-3.fc17\n" -" resource-agents.x86_64 0:3.9.2-2.fc17.1 rpcbind.x86_64 0:0.2.0-16.fc17\n" -" tcp_wrappers.x86_64 0:7.6-69.fc17 xfsprogs.x86_64 0:3.1.8-1.fc17\n" -"\n" -"Complete!\n" -"[root@pcmk-1 ~]#" +msgid "Install the Cluster Software" msgstr "" #. Tag: para #, no-c-format -msgid "Now install the cluster software on the second node." +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: title +#. Tag: screen #, no-c-format -msgid "Install the Cluster Management Software" +msgid "# yum install -y pacemaker pcs psmisc policycoreutils-python" msgstr "" #. Tag: para #, no-c-format -msgid "The pcs cli command coupled with the pcs daemon creates a cluster management system capable of managing all aspects of the cluster stack across all nodes from a single location." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# yum install -y pcs" +msgid "This document will show commands that need to be executed on both nodes with a simple # prompt. Be sure to run them on each node individually." msgstr "" #. Tag: para #, no-c-format -msgid "Make sure to install the pcs packages on both nodes." +msgid "This document uses pcs for cluster management. Other alternatives, such as crmsh, are available, but their syntax will differ from the examples used here." msgstr "" #. Tag: title #, no-c-format -msgid "Setup" +msgid "Configure the Cluster Software" msgstr "" #. Tag: title #, no-c-format -msgid "Enable pcs Daemon" +msgid "Allow cluster services through firewall" msgstr "" #. Tag: para #, no-c-format -msgid "Before the cluster can be configured, the pcs daemon must be started and enabled to boot on startup on each node. This daemon works with the pcs cli command to manage syncing the corosync configuration across all the nodes in the cluster." +msgid "On each node, allow cluster-related services through the local firewall:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Start and enable the daemon by issuing the following commands on each node." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# systemctl start pcsd.service\n" -"# systemctl enable pcsd.service" +msgid "# firewall-cmd --permanent --add-service=high-availability\n" +"success\n" +"# firewall-cmd --reload\n" +"success" msgstr "" #. Tag: para #, no-c-format -msgid "Now we need a way for pcs to talk to itself on other nodes in the cluster. This is necessary in order to perform tasks such as syncing the corosync config, or starting/stopping the cluster on remote nodes" +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 "While pcs can be used locally without setting up these user accounts, this tutorial will make use of these remote access commands, so we will set a password for the hacluster user. Its probably best if password is consistent across all the nodes." +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 "As root, run:" +msgid "To disable security measures:" msgstr "" -#. Tag: programlisting -#, no-c-format -msgid "# passwd hacluster\n" -"password:" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Alternatively, to script this process or set the password on a different machine to the one you’re logged into, you can use the --stdin option for passwd:" -msgstr "" - -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# ssh pcmk-2 -- 'echo redhat1 | passwd --stdin hacluster'" +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 disable firewalld.service\n" +"[root@pcmk-1 ~]# systemctl stop firewalld.service\n" +"[root@pcmk-1 ~]# iptables --flush" msgstr "" #. Tag: title #, no-c-format -msgid "Notes on Multicast Address Assignment" +msgid "Enable pcs Daemon" msgstr "" #. Tag: para #, no-c-format -msgid "There are several subtle points that often deserve consideration when choosing/assigning multicast addresses. This information is borrowed from, the now defunct, http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html" +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 "Avoid 224.0.0.x" +msgid "Start and enable the daemon by issuing the following commands on each node:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Traffic to addresses of the form 224.0.0.x is often flooded to all switch ports. This address range is reserved for link-local uses. Many routing protocols assume that all traffic within this range will be received by all routers on the network. Hence (at least all Cisco) switches flood traffic within this range. The flooding behavior overrides the normal selective forwarding behavior of a multicast-aware switch (e.g. IGMP snooping, CGMP, etc.)." +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 "Watch for 32:1 overlap" +msgid "The installed packages will create a hacluster user with a disabled password. While this is fine for running pcs 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 "32 non-contiguous IP multicast addresses are mapped onto each Ethernet multicast address. A receiver that joins a single IP multicast group implicitly joins 31 others due to this overlap. Of course, filtering in the operating system discards undesired multicast traffic from applications, but NIC bandwidth and CPU resources are nonetheless consumed discarding it. The overlap occurs in the 5 high-order bits, so it’s best to use the 23 low-order bits to make distinct multicast streams unique. For example, IP multicast addresses in the range 239.0.0.0 to 239.127.255.255 all map to unique Ethernet multicast addresses. However, IP multicast address 239.128.0.0 maps to the same Ethernet multicast address as 239.0.0.0, 239.128.0.1 maps to the same Ethernet multicast address as 239.0.0.1, etc." +msgid "This tutorial will make use of such commands, so now we will set a password for the hacluster user, using the same password on both nodes:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Avoid x.0.0.y and x.128.0.y" +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 "Combining the above two considerations, it’s best to avoid using IP multicast addresses of the form x.0.0.y and x.128.0.y since they all map onto the range of Ethernet multicast addresses that are flooded to all switch ports." +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 --stdin option for passwd:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Watch for address assignment conflicts" +msgid "[root@pcmk-1 ~]# ssh pcmk-2 -- 'echo redhat1 | passwd --stdin hacluster'" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "IANA administers Internet multicast addresses. Potential conflicts with Internet multicast address assignments can be avoided by using GLOP addressing (AS required) or administratively scoped addresses. Such addresses can be safely used on a network connected to the Internet without fear of conflict with multicast sources originating on the Internet. Administratively scoped addresses are roughly analogous to the unicast address space for private internets. Site-local multicast addresses are of the form 239.255.x.y, but can grow down to 239.252.x.y if needed. Organization-local multicast addresses are of the form 239.192-251.x.y, but can grow down to 239.x.y.z if needed." +msgid "Configure Corosync" msgstr "" #. Tag: para #, no-c-format -msgid "For a more detailed treatment (57 pages!), see Cisco’s Guidelines for Enterprise IP Multicast Address Allocation paper." +msgid "On either node, use pcs cluster auth to authenticate as the hacluster user:" msgstr "" -#. Tag: title +#. Tag: screen #, no-c-format -msgid "Configuring Corosync" +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 "In the past, at this point in the tutorial an explanation of how to configure and propagate corosync’s /etc/corosync.conf file would be necessary. Using pcs with the pcs daemon greatly simplifies this process by generating corosync.conf across all the nodes in the cluster with a single command. The only thing required to achieve this is to authenticate as the pcs user hacluster on one of the nodes in the cluster, and then issue the pcs cluster setup command with a list of all the node names in the cluster." +msgid "Next, use pcs cluster setup on the same node to generate and synchronize the corosync configuration:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster auth pcmk-1 pcmk-2\n" -"Username: hacluster\n" -"Password:\n" -"pcmk-1: Authorized\n" -"pcmk-2: Authorized\n" -"\n" -"# pcs cluster setup mycluster pcmk-1 pcmk-2\n" +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 "That’s it. Corosync is configured across the cluster. If you received an authorization error for either of those commands, make sure you setup the hacluster user account and password on every node in the cluster with the same password." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "The final /etc/corosync.conf configuration on each node should look something like the sample in Appendix B, Sample Corosync Configuration." +msgid "If you received an authorization error for either of those commands, make sure you configured the hacluster user account on each node with the same password." msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker used to obtain membership and quorum from a custom Corosync plugin. This plugin also had the capability to start Pacemaker automatically when Corosync was started." +msgid "Early versions of pcs required that --name be omitted from the above command." msgstr "" #. Tag: para #, no-c-format -msgid "Neither behavior is possible with Corosync 2.0 and beyond as support for plugins was removed." +msgid "If you are not using pcs 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 "Instead, Pacemaker must be started as a separate job/initscript. Also, since Pacemaker made use of the plugin for message routing, a node using the plugin (Corosync prior to 2.0) cannot talk to one that isn’t (Corosync 2.0+)." +msgid "The pcs command will configure corosync to use UDP unicast transport; if you choose to use multicast instead, choose a multicast address carefully. For some subtle issues, see the now-defunct http://web.archive.org/web/20101211210054/http://29west.com/docs/THPM/multicast-address-assignment.html or the more detailed treatment in Cisco’s Guidelines for Enterprise IP Multicast Address Allocation paper." msgstr "" #. Tag: para #, no-c-format -msgid "Rolling upgrades between these versions are therefor not possible and an alternate strategy http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ap-upgrade.html must be used." +msgid "The final /etc/corosync.conf configuration on each node should look something like the sample in ." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot b/doc/Clusters_from_Scratch/pot/Ch-Intro.pot index 3936a578b3..686edc3126 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Intro.pot @@ -1,279 +1,289 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 Fedora distribution, version 17." +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 Pacemaker Explained manual." msgstr "" #. Tag: title #, no-c-format -msgid "What Is Pacemaker?" +msgid "What Is Pacemaker?" msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker is a cluster resource manager. It achieves maximum availability for your cluster services (aka. resources) 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 Corosync or Heartbeat)." +msgid "Pacemaker is a cluster resource manager, 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. nodes) and driven by prescribed rules." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "It achieves maximum availability for your cluster services (a.k.a. resources) 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 Corosync or Heartbeat), and possibly by utilizing other parts of the overall cluster stack." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "For the goal of minimal downtime a term high availability was coined and together with its acronym, HA, is well-established in the sector. To differentiate this sort of clusters from high performance computing (HPC) ones, should a context require it (apparently, not the case in this document), using HA cluster is an option." msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker’s key features include:" msgstr "" #. Tag: para #, no-c-format msgid "Detection and recovery of node and service-level failures" msgstr "" #. Tag: para #, no-c-format msgid "Storage agnostic, no requirement for shared storage" msgstr "" #. Tag: para #, no-c-format msgid "Resource agnostic, anything that can be scripted can be clustered" msgstr "" #. Tag: para #, no-c-format -msgid "Supports STONITH for ensuring data integrity" +msgid "Supports fencing (also referred to as the STONITH acronym, deciphered later on) for ensuring data integrity" msgstr "" #. Tag: para #, no-c-format msgid "Supports large and small clusters" msgstr "" #. Tag: para #, no-c-format -msgid "Supports both quorate and resource driven clusters" +msgid "Supports both quorate and resource-driven clusters" msgstr "" #. Tag: para #, no-c-format msgid "Supports practically any redundancy configuration" 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 service ordering, colocation and anti-colocation" msgstr "" #. Tag: para #, no-c-format msgid "Support for advanced service types" msgstr "" #. Tag: para #, no-c-format msgid "Clones: for services which need to be active on multiple nodes" msgstr "" #. Tag: para #, no-c-format -msgid "Multi-state: for services with multiple modes (eg. master/slave, primary/secondary)" +msgid "Multi-state: for services with multiple modes (e.g. master/slave, primary/secondary)" msgstr "" #. Tag: para #, no-c-format -msgid "Unified, scriptable, cluster management tools." +msgid "Unified, scriptable cluster management tools" 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:" msgstr "" #. Tag: para #, no-c-format -msgid "Non-cluster aware components (illustrated in green). These pieces include the resources themselves, scripts that start, stop and monitor them, and also a local daemon that masks the differences between the different standards these scripts implement." +msgid "Non-cluster-aware components. 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." msgstr "" #. Tag: para #, no-c-format -msgid "Resource management Pacemaker provides the brain (illustrated in blue) that processes and reacts to events regarding the cluster. These events include nodes joining or leaving the cluster; resource events caused by failures, maintenance, 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 "Resource management. 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." msgstr "" #. Tag: para #, no-c-format -msgid "Low level infrastructure Corosync provides reliable messaging, membership and quorum information about the cluster (illustrated in red)." +msgid "Low-level infrastructure. Projects like Corosync, CMAN and Heartbeat provide reliable messaging, membership and quorum information about the cluster." msgstr "" -#. Tag: title -#, no-c-format -msgid "Conceptual Stack Overview" -msgstr "" - -#. Tag: phrase +#. Tag: para #, no-c-format -msgid "Conceptual overview of the cluster stack" +msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems. 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. " msgstr "" #. Tag: para #, no-c-format -msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems. 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, however there seems little interest in this." +msgid "Due to past standardization within the cluster filesystem community, cluster filesystems make use of a common distributed lock manager, which makes use of Corosync for its messaging and membership capabilities (which nodes are up/down) and Pacemaker for fencing services." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "Due to recent standardization within the cluster filesystem community, they make use of a common distributed lock manager which makes use of Corosync for its messaging capabilities and Pacemaker for its membership (which nodes are up/down) and fencing services." +msgid "The Pacemaker Stack" msgstr "" #. Tag: title #, no-c-format -msgid "The Pacemaker Stack" +msgid "Internal Components" msgstr "" -#. Tag: phrase +#. Tag: para #, no-c-format -msgid "The Pacemaker StackThe Pacemaker stack when running on Corosync" +msgid "Pacemaker itself is composed of five key components:" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Internal Components" +msgid "Cluster Information Base (CIB)" msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker itself is composed of four key components (illustrated below in the same color scheme as the previous diagram):" +msgid "Cluster Resource Management daemon (CRMd)" msgstr "" #. Tag: para #, no-c-format -msgid "CIB (aka. Cluster Information Base)" +msgid "Local Resource Management daemon (LRMd)" msgstr "" #. Tag: para #, no-c-format -msgid "CRMd (aka. Cluster Resource Management daemon)" +msgid "Policy Engine (PEngine or PE)" msgstr "" #. Tag: para #, no-c-format -msgid "PEngine (aka. PE or Policy Engine)" +msgid "Fencing daemon (STONITHd)" msgstr "" #. Tag: para #, no-c-format -msgid "STONITHd" +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." msgstr "" -#. Tag: phrase +#. Tag: para #, no-c-format -msgid "Subsystems of a Pacemaker cluster running on Corosync" +msgid "This list of instructions is then fed to the Designated Controller (DC). 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." 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 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)." msgstr "" #. Tag: para #, no-c-format -msgid "This list of instructions is then fed to the DC (Designated Co-ordinator). 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 "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." 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 LRMd (Local Resource Management daemon) or CRMd peers on other nodes via the cluster messaging infrastructure (which in turn passes them on to their LRMd process)." +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." 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 "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head, a recommended practice that misbehaving node is best to be promptly fenced (shut off, cut from shared resources or otherwise immobilized), and is usually implemented with a remote power switch." 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. STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and is usually implemented with a remote power switch. 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 "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." msgstr "" #. Tag: title #, no-c-format msgid "Types of Pacemaker Clusters" msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker makes no assumptions about your environment, this allows it to support practically any redundancy configuration including Active/Active, Active/Passive, N+1, N+M, N-to-1 and N-to-N." +msgid "Pacemaker makes no assumptions about your environment. This allows it to support practically any redundancy configuration including Active/Active, Active/Passive, N+1, N+M, N-to-1 and N-to-N." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Active/Passive Redundancy" msgstr "" #. Tag: para #, no-c-format -msgid "In this document we will focus on the setup of a highly available Apache web server with an Active/Passive cluster using DRBD and Ext4 to store data. Then, we will upgrade this cluster to Active/Active using GFS2." +msgid "Two-node Active/Passive clusters using Pacemaker and DRBD are a cost-effective solution for many High Availability situations." msgstr "" #. Tag: title #, no-c-format -msgid "Active/Passive Redundancy" +msgid "Shared Failover" msgstr "" -#. Tag: phrase +#. Tag: para #, no-c-format -msgid "Two-node Active/Passive clusters using Pacemaker and DRBD are a cost-effective solution for many High Availability situations" +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." msgstr "" #. Tag: title #, no-c-format msgid "N to N Redundancy" msgstr "" -#. Tag: phrase +#. 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" +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 "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot b/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot index b4265053d4..520b1a2ac7 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot @@ -1,604 +1,695 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Replicated Storage with DRBD" +msgid "Replicate Storage Using DRBD" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Background" +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 "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. Enter DRBD which can be thought of as network based RAID-1. See http://www.drbd.org/ for more details." +msgid "Enter DRBD, which can be thought of as network-based RAID-1. See http://www.drbd.org/ for details." msgstr "" #. Tag: title #, no-c-format msgid "Install the DRBD Packages" msgstr "" #. Tag: para #, no-c-format -msgid "Since its inclusion in the upstream 2.6.33 kernel, everything needed to use DRBD has shiped with Fedora since version 13. All you need to do is install it:" +msgid "DRBD itself is included in the upstream kernel,Since version 2.6.33 but we do need some utilities to use it effectively." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# yum install -y drbd-pacemaker drbd-udev" +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 LINBIT, but here we’ll use the free ELRepo repository." msgstr "" -#. Tag: literallayout +#. Tag: para #, no-c-format -msgid "Loaded plugins: langpacks, presto, refresh-packagekit\n" -"Resolving Dependencies\n" -"--> Running transaction check\n" -"---> Package drbd-pacemaker.x86_64 0:8.3.11-5.fc17 will be installed\n" -"--> Processing Dependency: drbd-utils = 8.3.11-5.fc17 for package: drbd-pacemaker-8.3.11-5.fc17.x86_64\n" -"---> Package drbd-udev.x86_64 0:8.3.11-5.fc17 will be installed\n" -"--> Running transaction check\n" -"---> Package drbd-utils.x86_64 0:8.3.11-5.fc17 will be installed\n" -"--> Finished Dependency Resolution\n" -"\n" -"Dependencies Resolved\n" -"\n" -"======================================================================================\n" -" Package Arch Version Repository Size\n" -"======================================================================================\n" -"Installing:\n" -" drbd-pacemaker x86_64 8.3.11-5.fc17 updates-testing 22 k\n" -" drbd-udev x86_64 8.3.11-5.fc17 updates-testing 6.4 k\n" -"Installing for dependencies:\n" -" drbd-utils x86_64 8.3.11-5.fc17 updates-testing 183 k\n" -"\n" -"Transaction Summary\n" -"======================================================================================\n" -"Install 2 Packages (+1 Dependent package)\n" -"\n" -"Total download size: 212 k\n" -"Installed size: 473 k\n" -"Downloading Packages:\n" -"(1/3): drbd-pacemaker-8.3.11-5.fc17.x86_64.rpm | 22 kB 00:00\n" -"(2/3): drbd-udev-8.3.11-5.fc17.x86_64.rpm | 6.4 kB 00:00\n" -"(3/3): drbd-utils-8.3.11-5.fc17.x86_64.rpm | 183 kB 00:00\n" -"--------------------------------------------------------------------------------------\n" -"Total 293 kB/s | 212 kB 00:00\n" -"Running Transaction Check\n" -"Running Transaction Test\n" -"Transaction Test Succeeded\n" -"Running Transaction\n" -" Installing : drbd-utils-8.3.11-5.fc17.x86_64 1/3\n" -" Installing : drbd-pacemaker-8.3.11-5.fc17.x86_64 2/3\n" -" Installing : drbd-udev-8.3.11-5.fc17.x86_64 3/3\n" -" Verifying : drbd-pacemaker-8.3.11-5.fc17.x86_64 1/3\n" -" Verifying : drbd-udev-8.3.11-5.fc17.x86_64 2/3\n" -" Verifying : drbd-utils-8.3.11-5.fc17.x86_64 3/3\n" -"\n" -"Installed:\n" -" drbd-pacemaker.x86_64 0:8.3.11-5.fc17 drbd-udev.x86_64 0:8.3.11-5.fc17\n" -"\n" -"Dependency Installed:\n" -" drbd-utils.x86_64 0:8.3.11-5.fc17\n" -"\n" -"Complete!" +msgid "On both nodes, import the ELRepo package signing key, and enable the repository:" msgstr "" -#. Tag: title +#. Tag: screen #, no-c-format -msgid "Configure DRBD" +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" msgstr "" #. Tag: para #, no-c-format -msgid "Before we configure DRBD, we need to set aside some disk for it to use." +msgid "Now, we can install the DRBD kernel module and utilities:" msgstr "" -#. Tag: title +#. Tag: screen #, no-c-format -msgid "Create A Partition for DRBD" +msgid "# yum install -y kmod-drbd84 drbd84-utils" msgstr "" #. Tag: para #, no-c-format -msgid "If you have more than 1Gb free, feel free to use it. For this guide however, 1Gb is plenty of space for a single html file and sufficient for later holding the GFS2 metadata." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# vgdisplay | grep -e Name - e Free\n" -" VG Name vg_pcmk1\n" -" Free PE / Size 31 / 992.00 MiB\n" -"# lvs\n" -" LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert\n" -" lv_root vg_pcmk1 -wi-ao-- 8.56g\n" -" lv_swap vg_pcmk1 -wi-ao-- 960.00m\n" -"# lvcreate -n drbd-demo -L 1G vg_pcmk1\n" -"Logical volume \"drbd-demo\" created\n" -"# lvs\n" -" LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert\n" -" drbd-demo vg_pcmk1 -wi-a--- 1.00G\n" -" lv_root vg_pcmk1 -wi-ao-- 8.56g\n" -" lv_swap vg_pcmk1 -wi-ao-- 960.00m" +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 "Repeat this on the second node, be sure to use the same size partition." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# ssh pcmk-2 -- lvs\n" -"LV VG Attr LSize Origin Snap% Move Log Copy% Convert\n" -" lv_root vg_pcmk1 -wi-ao-- 8.56g\n" -" lv_swap vg_pcmk1 -wi-ao-- 960.00m\n" -"# ssh pcmk-2 -- lvcreate -n drbd-demo -L 1G vg_pcmk1\n" -"Logical volume \"drbd-demo\" created\n" -"# ssh pcmk-2 -- lvs\n" -"LV VG Attr LSize Origin Snap% Move Log Copy% Convert\n" -" drbd-demo vg_pcmk1 -wi-a--- 1.00G\n" -" lv_root vg_pcmk1 -wi-ao-- 8.56g\n" -" lv_swap vg_pcmk1 -wi-ao-- 960.00m" +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 "Write the DRBD Config" +msgid "Allocate a Disk Volume for DRBD" msgstr "" #. Tag: para #, no-c-format -msgid "There is no series of commands for building a DRBD configuration, so simply copy the configuration below to /etc/drbd.conf" +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 "Detailed information on the directives used in this configuration (and other alternatives) is available from http://www.drbd.org/users-guide/ch-configure.html" +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 "Be sure to use the names and addresses of your nodes if they differ from the ones used in this guide." +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: literallayout +#. Tag: screen #, no-c-format -msgid "global {\n" -" usage-count yes;\n" -"}\n" -"common {\n" -" protocol C;\n" -"}\n" +msgid "# cat <<END >/etc/drbd.d/wwwdata.res\n" "resource wwwdata {\n" +" protocol C;\n" " meta-disk internal;\n" -" device /dev/drbd1;\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/vg_pcmk1/drbd-demo;\n" +" disk /dev/centos_pcmk-1/drbd-demo;\n" " address 192.168.122.101:7789;\n" " }\n" " on pcmk-2 {\n" -" disk /dev/vg_pcmk1/drbd-demo;\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 http://www.drbd.org/users-guide/ch-configure.html" msgstr "" #. Tag: para #, no-c-format -msgid "TODO: Explain the reason for the allow-two-primaries option" +msgid "The allow-two-primaries 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 and Load DRBD" +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 "With the configuration in place, we can now perform the DRBD initialization" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# drbdadm create-md wwwdata\n" -"Writing meta data...\n" +msgid "[root@pcmk-1 ~]# drbdadm create-md wwwdata\n" "initializing activity log\n" -"NOT initialized bitmap\n" +"NOT initializing bitmap\n" +"Writing meta data...\n" "New drbd meta data block successfully created.\n" -"success" +"[root@pcmk-1 ~]# modprobe drbd\n" +"[root@pcmk-1 ~]# drbdadm up wwwdata" msgstr "" #. Tag: para #, no-c-format -msgid "Now load the DRBD kernel module and confirm that everything is sane" +msgid "We can confirm DRBD’s status on this node:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# modprobe drbd\n" -"# drbdadm up wwwdata\n" -"# cat /proc/drbd\n" -"version: 8.3.11 (api:88/proto:86-96)\n" -"srcversion: 0D2B62DEDB020A425130935\n" +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: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:1015740" +" 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 "Repeat on the second node" +msgid "Because we have not yet initialized the data, this node’s data is marked as Inconsistent. Because we have not yet initialized the second node, the local state is WFConnection (waiting for connection), and the partner node’s status is marked as Unknown." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# ssh pcmk-2 -- drbdadm --force create-md wwwdata\n" -"Writing meta data...\n" -"initializing activity log\n" -"NOT initialized bitmap\n" -"New drbd meta data block successfully created.\n" -"success\n" -"# ssh pcmk-2 -- modprobe drbd\n" -"WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.\n" -"# ssh pcmk-2 -- drbdadm up wwwdata\n" -"# ssh pcmk-2 -- cat /proc/drbd\n" -"version: 8.3.11 (api:88/proto:86-96)\n" -"srcversion: 0D2B62DEDB020A425130935\n" +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:1015740" +" 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 Connected, meaning the two DRBD nodes are communicating properly, and both nodes are in Secondary role with Inconsistent 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 "Now we need to tell DRBD which set of data to use. Since both sides contain garbage, we can run the following on pcmk-1:" +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." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# drbdadm -- --overwrite-data-of-peer primary wwwdata\n" -"# cat /proc/drbd\n" -"version: 8.3.11 (api:88/proto:86-96)\n" -"srcversion: 0D2B62DEDB020A425130935\n" +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:8064 nr:0 dw:0 dr:8728 al:0 bm:0 lo:0 pe:1 ua:0 ap:0 ep:1 wo:f oos:1007804\n" -" [>....................] sync'ed: 0.9% (1007804/1015740)K\n" -" finish: 0:12:35 speed: 1,320 (1,320) K/sec" +" 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" +" [>....................] 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 "After a while, the sync should finish and you’ll see:" +msgid "We can see that this node has the Primary role, the partner node has the Secondary role, this node’s data is now considered UpToDate, the partner node’s data is still Inconsistent, and a progress bar shows how far along the partner node is in synchronizing the data." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# cat /proc/drbd\n" -"version: 8.3.11 (api:88/proto:86-96)\n" -"srcversion: 0D2B62DEDB020A425130935\n" +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:1015740 nr:0 dw:0 dr:1016404 al:0 bm:62 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0" +" 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 "pcmk-1 is now in the Primary state which allows it to be written to. Which means it’s a good point at which to create a filesystem and populate it with some data to serve up via our WebSite resource." +msgid "Both sets of data are now UpToDate, and we can proceed to creating and populating a filesystem for our WebSite resource’s documents." msgstr "" #. Tag: title #, no-c-format -msgid "Populate DRBD with Data" -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# mkfs.ext4 /dev/drbd1\n" -"mke2fs 1.42 (29-Nov-2011)\n" -"Filesystem label=\n" -"OS type: Linux\n" -"Block size=4096 (log=2)\n" -"Fragment size=4096 (log=2)\n" -"Stride=0 blocks, Stripe width=0 blocks\n" -"63488 inodes, 253935 blocks\n" -"12696 blocks (5.00%) reserved for the super user\n" -"First data block=0\n" -"Maximum filesystem blocks=260046848\n" -"8 block groups\n" -"32768 blocks per group, 32768 fragments per group\n" -"7936 inodes per group\n" -"Superblock backups stored on blocks:\n" -" 32768, 98304, 163840, 229376\n" -"\n" -"Allocating group tables: done\n" -"Writing inode tables: done\n" -"Creating journal (4096 blocks): done\n" -"Writing superblocks and filesystem accounting information: done" +msgid "Populate the DRBD Disk" msgstr "" #. Tag: para #, no-c-format -msgid "Now mount the newly created filesystem so we can create our index file" +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: programlisting +#. Tag: para #, no-c-format -msgid "# mount /dev/drbd1 /mnt/\n" -"# cat <<-END >/mnt/index.html\n" +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 <<-END >/mnt/index.html\n" " <html>\n" -" <body>My Test Site - drbd</body>\n" +" <body>My Test Site - DRBD</body>\n" " </html>\n" "END\n" -"# umount /dev/drbd1" +"[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 DRBD" +msgid "Configure the Cluster for the DRBD device" msgstr "" #. Tag: para #, no-c-format -msgid "One handy feature pcs 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. This can be done using the following command." +msgid "One handy feature pcs 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." +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "[root@pcmk-1 ~]# pcs cluster cib drbd_cfg" msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs cluster cib drbd_cfg" +msgid "Using the pcs -f option, make changes to the configuration saved in the drbd_cfg file. These changes will not be seen by the cluster until the drbd_cfg file is pushed into the live cluster’s CIB later." msgstr "" #. Tag: para #, no-c-format -msgid "Now using the pcs -f option, make changes to the configuration saved in the drbd_cfg file. These changes will not be seen by the cluster until the drbd_cfg file is pushed into the live cluster’s cib later on." +msgid "Here, we create a cluster resource for the DRBD device, and an additional clone resource to allow the resource to run on both nodes at the same time." msgstr "" #. Tag: screen #, no-c-format -msgid "# pcs -f drbd_cfg resource create WebData ocf:linbit:drbd \\\n" +msgid "[root@pcmk-1 ~]# pcs -f drbd_cfg resource create WebData ocf:linbit:drbd \\\n" " drbd_resource=wwwdata op monitor interval=60s\n" -"# pcs -f drbd_cfg resource master WebDataClone WebData \\\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" +" 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: programlisting +#. Tag: screen #, no-c-format -msgid "# 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: [ WebData:0 WebData:1 ]" +msgid "[root@pcmk-1 ~]# pcs cluster cib-push drbd_cfg\n" +"CIB updated" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Early versions of pcs required push cib in place of cib-push above." msgstr "" #. Tag: para #, no-c-format -msgid "After you are satisfied with all the changes, you can commit all the changes at once by pushing the drbd_cfg file into the live cib." +msgid "Let’s see what the cluster did with the new configuration:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster push cib drbd_cfg\n" -"CIB updated\n" -"\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 12:19:49 2012\n" -"Last change: Fri Sep 14 12:19:13 2012 via cibadmin on pcmk-1\n" +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-2 (2) - partition with quorum\n" -"Version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"4 Resources configured.\n" +"Current DC: pcmk-1 (1) - partition with quorum\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"4 Resources configured\n" +"\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 ]" +" 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 WebDataClone (our DRBD device) is running as master (DRBD’s primary role) on pcmk-1 and slave (DRBD’s secondary role) on pcmk-2." msgstr "" #. Tag: para #, no-c-format -msgid "TODO: Include details on adding a second DRBD resource" +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 >/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 DRBD is functioning we can configure a Filesystem resource to use it. In addition to the filesystem’s definition, 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)." +msgid "Now that we have a working DRBD device, we need to mount its filesystem." msgstr "" #. Tag: para #, no-c-format -msgid "We are going to take a shortcut when creating the resource this time though. Instead of explicitly saying we want the ocf:heartbeat:Filesystem script, we are only going to ask for Filesystem. We can do this because we know there is only one resource script named Filesystem available to pacemaker, and that pcs is smart enough to fill in the ocf:heartbeat portion for us correctly in the configuration. If there were multiple Filesystem scripts from different ocf providers, we would need to specify the exact one we wanted to use." +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 "Once again we will queue up our changes to a file and then push the new configuration to the cluster as the final step." +msgid "We are going to take a shortcut when creating the resource this time. Instead of explicitly saying we want the ocf:heartbeat:Filesystem script, we are only going to ask for Filesystem. We can do this because we know there is only one resource script named Filesystem available to pacemaker, and that pcs is smart enough to fill in the ocf:heartbeat: portion for us correctly in the configuration. If there were multiple Filesystem scripts from different OCF providers, we would need to specify the exact one we wanted." msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "# pcs cluster cib fs_cfg\n" -"# pcs -f fs_cfg resource create WebFS Filesystem \\\n" -" device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" \\\n" -" fstype=\"ext4\"" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f fs_cfg constraint colocation add WebFS WebDataClone INFINITY with-rsc-role=Master\n" -"# pcs -f fs_cfg constraint order promote WebDataClone then start WebFS\n" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f fs_cfg constraint colocation add WebSite WebFS INFINITY\n" -"# pcs -f fs_cfg constraint order WebFS then WebSite" +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 "Now review the updated configuration." +msgid "Review the updated configuration." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs -f fs_cfg constraint\n" +msgid "[root@pcmk-1 ~]# pcs -f fs_cfg constraint\n" "Location Constraints:\n" "Ordering Constraints:\n" -" start ClusterIP then start WebSite\n" -" WebFS then WebSite\n" -" promote WebDataClone then start WebFS\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\n" -" WebFS with WebDataClone (with-rsc-role:Master)\n" -" WebSite with WebFS\n" -"\n" -"# pcs -f fs_cfg resource show\n" -" ClusterIP (ocf::heartbeat:IPaddr2) Started\n" -" WebSite (ocf::heartbeat:apache) Started\n" +" WebSite with ClusterIP (score:INFINITY)\n" +" WebFS with WebDataClone (score:INFINITY) (with-rsc-role:Master)\n" +" WebSite with WebFS (score:INFINITY)" +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" +" WebFS (ocf::heartbeat:Filesystem): Stopped" msgstr "" #. Tag: para #, no-c-format -msgid "After reviewing the new configuration, we again upload it and watch the cluster put it into effect." +msgid "After reviewing the new configuration, upload it and watch the cluster put it into effect." msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster push cib fs_cfg\n" -"CIB updated\n" -"# pcs status\n" -" Last updated: Fri Aug 10 12:47:01 2012\n" +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" +"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" "\n" -" Last change: Fri Aug 10 12:46:55 2012 via cibadmin on pcmk-1\n" -" Stack: corosync\n" -" Current DC: pcmk-1 (1) - partition with quorum\n" -" Version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -" 2 Nodes configured, unknown expected votes\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" +" 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 "Testing Migration" +msgid "Test Cluster Failover" msgstr "" #. Tag: para #, no-c-format -msgid "We could shut down the active node again, but another way to safely simulate recovery is to put the node into what is called \"standby mode\". Nodes in this state tell the cluster that they are not allowed to run resources. Any resources found active there will be moved elsewhere. This feature can be particularly useful when updating the resources' packages." +msgid "Previously, we used pcs cluster stop pcmk-1 to stop all cluster services on pcmk-1, failing over the cluster resources, but there is another way to safely simulate node failure." msgstr "" #. Tag: para #, no-c-format -msgid "Put the local node into standby mode and observe the cluster move all the resources to the other node. Note also that the node’s status will change to indicate that it can no longer host resources." +msgid "We can put the node into standby mode. 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: programlisting +#. Tag: para #, no-c-format -msgid "# pcs cluster standby pcmk-1\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 12:41:12 2012\n" -"Last change: Fri Sep 14 12:41:08 2012 via crm_attribute on pcmk-1\n" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"5 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"5 Resources configured\n" +"\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" +" 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: [ WebData:1 ]\n" -"WebFS (ocf::heartbeat:Filesystem): Started pcmk-2" +" 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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster unstandby pcmk-1\n" -"# pcs status\n" -"\n" -"Last updated: Fri Sep 14 12:43:02 2012\n" -"Last change: Fri Sep 14 12:42:57 2012 via crm_attribute on pcmk-1\n" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"5 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"5 Resources configured\n" +"\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" +" 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 our resource stickiness settings prevent the services from migrating back to pcmk-1." +msgid "Notice that pcmk-1 is back to the Online 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 a294603536..94738db0f8 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot @@ -1,198 +1,252 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +msgid "What is STONITH?" msgstr "" #. Tag: para #, no-c-format -msgid "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access." +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, 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." +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 "What STONITH Device Should You Use" +msgid "Choose a STONITH Device" 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." +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 "The biggest mistake people make in choosing a STONITH device is to use remote power switch (such as many on-board IMPI 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." +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\" used during testing) are inappropriate." +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 "Configuring STONITH" +msgid "Configure the Cluster for STONITH" msgstr "" #. Tag: para #, no-c-format -msgid "Find the correct driver: pcs stonith list" +msgid "Install the STONITH agent(s). To see what packages are available, run yum search fence-. Be sure to install the package(s) on all cluster nodes." msgstr "" #. Tag: para #, no-c-format -msgid "Find the parameters associated with the device: pcs stonith describe <agent name>" +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 "Create a local config to make changes to pcs cluster cib stonith_cfg" +msgid "Find the correct STONITH agent script: pcs stonith list" msgstr "" #. Tag: para #, no-c-format -msgid "Create the fencing resource using pcs -f stonith_cfg stonith create <stonith_id> <stonith device type> [stonith device options]" +msgid "Find the parameters associated with the device: pcs stonith describe agent_name" msgstr "" #. Tag: para #, no-c-format -msgid "Set stonith-enable to true. pcs -f stonith_cfg property set stonith-enabled=true" +msgid "Create a local copy of the CIB: pcs cluster cib stonith_cfg" 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 pcmk_host_map parameter. See man stonithd for details." +msgid "Create the fencing resource: pcs -f stonith_cfg stonith create stonith_id stonith_device_type [stonith_device_options]" msgstr "" #. Tag: para #, no-c-format -msgid "If the device does not support the list command, you may also need to set the special pcmk_host_list and/or pcmk_host_check parameters. See man stonithd for details." +msgid "Any flags that do not take arguments, such as --ssl, should be passed as ssl=1." msgstr "" #. Tag: para #, no-c-format -msgid "If the device does not expect the victim to be specified with the port parameter, you may also need to set the special pcmk_host_argument parameter. See man stonithd for details." +msgid "Enable STONITH in the cluster: pcs -f stonith_cfg property set stonith-enabled=true" msgstr "" #. Tag: para #, no-c-format -msgid "Commit the new configuration. pcs cluster push cib stonith_cfg" +msgid "If the device does not know how to fence nodes based on their uname, you may also need to set the special pcmk_host_map parameter. See man stonithd for details." msgstr "" #. Tag: para #, no-c-format -msgid "Once the stonith resource is running, you can test it by executing: stonith_admin --reboot nodename. Although you might want to stop the cluster on that machine first." +msgid "If the device does not support the list command, you may also need to set the special pcmk_host_list and/or pcmk_host_check parameters. See man stonithd for details." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If the device does not expect the victim to be specified with the port parameter, you may also need to set the special pcmk_host_argument parameter. See man stonithd for details." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Commit the new configuration: pcs cluster cib-push stonith_cfg" +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): stonith_admin --reboot nodename" msgstr "" #. Tag: title #, no-c-format msgid "Example" msgstr "" #. Tag: para #, no-c-format -msgid "Assuming we have an chassis containing four nodes and an IPMI device active on 10.0.0.1, then we would chose the fence_ipmilan driver in step 2 and obtain the following list of parameters" +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: title +#. Tag: para +#, no-c-format +msgid "Step 1: Install the fence-agents-ipmilan 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 fence_ipmilan STONITH agent." +msgstr "" + +#. Tag: para #, no-c-format -msgid "Obtaining a list of STONITH Parameters" +msgid "Step 4: Obtain the agent’s possible parameters:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs stonith describe fence_ipmilan\n" +msgid "[root@pcmk-1 ~]# pcs stonith describe fence_ipmilan\n" "Stonith options for: fence_ipmilan\n" -" auth: IPMI Lan Auth type (md5, password, or none)\n" -" ipaddr: IPMI Lan IP to talk to\n" -" passwd: Password (if required) to control power on IPMI device\n" -" passwd_script: Script to retrieve password (if required)\n" -" lanplus: Use Lanplus\n" -" login: Username/Login (if required) to control power on IPMI device\n" -" action: Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata\n" -" timeout: Timeout (sec) for IPMI operation\n" +" ipport: TCP/UDP port to use for connection with device\n" +" inet6_only: Forces agent to use IPv6 addresses only\n" +" ipaddr (required): 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" " cipher: Ciphersuite to use (same as ipmitool -C parameter)\n" -" method: Method to fence (onoff or cycle)\n" -" power_wait: Wait X seconds after on/off operation\n" -" delay: Wait X seconds before fencing is started\n" " privlvl: Privilege level on IPMI device\n" -" verbose: Verbose mode" +" action (required): Fencing Action\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" +" ipmitool_path: Path to ipmitool binary\n" +" shell_timeout: Wait X seconds for cmd prompt after issuing command\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_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." msgstr "" #. Tag: para #, no-c-format -msgid "from which we would create a STONITH resource fragment that might look like this" +msgid "Step 5: pcs cluster cib stonith_cfg" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Sample STONITH Resource" +msgid "Step 6: Here are example parameters for creating our STONITH resource:" msgstr "" #. Tag: screen #, no-c-format -msgid "# pcs cluster cib stonith_cfg\n" -"# pcs -f stonith_cfg stonith create impi-fencing fence_ipmilan \\\n" +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" +" passwd=acd123 op monitor interval=60s\n" +"[root@pcmk-1 ~]# pcs -f stonith_cfg stonith\n" +" ipmi-fencing (stonith:fence_ipmilan): Stopped" msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs -f stonith_cfg stonith\n" -" impi-fencing (stonith:fence_ipmilan) Stopped" +msgid "Steps 7-10: Enable STONITH in the cluster:" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "And finally, since we disabled it earlier, we need to re-enable STONITH. At this point we should have the following configuration." +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" +" have-watchdog: false\n" +" stonith-enabled: true" msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# pcs -f stonith_cfg property set stonith-enabled=true\n" -"# pcs -f stonith_cfg property\n" -"dc-version: 1.1.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"cluster-infrastructure: corosync\n" -"no-quorum-policy: ignore\n" -"stonith-enabled: true" +msgid "Step 11: pcs cluster cib-push stonith_cfg" msgstr "" #. Tag: para #, no-c-format -msgid "Now push the configuration into the cluster." +msgid "Step 12: Test:" msgstr "" -#. Tag: programlisting +#. 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 "# pcs cluster push cib stonith_cfg" +msgid "After a successful test, login to any rebooted nodes, and start the cluster (with pcs cluster start)." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Tools.pot b/doc/Clusters_from_Scratch/pot/Ch-Tools.pot index 1cb3f9efff..27d8cf17ca 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Tools.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Tools.pot @@ -1,146 +1,149 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Using Pacemaker Tools" +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 packs them into one simple to use command line tool." +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." msgstr "" #. Tag: para #, no-c-format -msgid "There are currently two command-line shells that people use, pcs and crmsh. This edition of Clusters from Scratch is based on pcs. Start by taking some time to familiarize yourself with what it can do." +msgid "Two popular command-line shells are pcs and crmsh. This edition of Clusters from Scratch is based on pcs." 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: para #, no-c-format -msgid "Since pcs has the ability to manage all aspects of the cluster (both corosync and pacemaker), it requires a specific cluster stack to be in use, (corosync 2.0 with votequorum + Pacemaker version >= 1.8)." +msgid "Since pcs has the ability to manage all aspects of the cluster (both corosync and pacemaker), it requires a specific cluster stack to be in use: corosync 2.0 or later with votequorum plus Pacemaker 1.1.8 or later." msgstr "" -#. Tag: programlisting +#. Tag: title #, no-c-format -msgid "# pcs" +msgid "Explore pcs" msgstr "" -#. Tag: literallayout +#. Tag: para #, no-c-format -msgid "Control and configure pacemaker and corosync.\n" +msgid "Start by taking some time to familiarize yourself with what pcs can do." +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "[root@pcmk-1 ~]# pcs\n" +"Usage: pcs [-f file] [-h] [commands]...\n" +"Control and configure pacemaker and corosync.\n" "\n" "Options:\n" -" -h Display usage and exit\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" "\n" "Commands:\n" -" resource Manage cluster resources\n" " cluster Configure cluster options and nodes\n" +" resource Manage cluster resources\n" " stonith Configure fence devices\n" -" property Set pacemaker properties\n" " constraint Set resource constraints\n" -" status View cluster status" +" property Set pacemaker properties\n" +" acl Set pacemaker access control lists\n" +" status View cluster status\n" +" config View and manage cluster configuration" msgstr "" #. Tag: para #, no-c-format -msgid "As you can see, the different aspects of cluster management are broken up into categories: resource, cluster, stonith, property, constraint, and status. To discover the functionality available in each of these categories, one can issue the command pcs <category> help. 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: resource, cluster, stonith, property, constraint, and status. To discover the functionality available in each of these categories, one can issue the command pcs category help. Below is an example of all the options available under the status category." msgstr "" -#. Tag: programlisting -#, no-c-format -msgid "# pcs status help" -msgstr "" - -#. Tag: literallayout +#. Tag: screen #, no-c-format -msgid "Usage: pcs status [commands]...\n" +msgid "[root@pcmk-1 ~]# pcs status help\n" +"Usage: pcs status [commands]...\n" "View current cluster and resource status\n" "Commands:\n" -" status\n" -" View all information about the cluster and resources\n" +" [status] [--full]\n" +" View all information about the cluster and resources (--full provides\n" +" more details)\n" "\n" -" status resources\n" +" resources\n" " View current status of cluster resources\n" "\n" -" status groups\n" +" groups\n" " View currently configured groups and their resources\n" "\n" -" status cluster\n" +" cluster\n" " View current cluster status\n" "\n" -" status corosync\n" -" View current corosync status\n" +" corosync\n" +" View current membership information as seen by corosync\n" "\n" -" status nodes [corosync]\n" -" View current status of nodes from pacemaker, or if corosync is\n" -" specified, print nodes currently configured in corosync\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 & pacemaker. If 'config'\n" +" is specified, print nodes from corosync & pacemaker configuration.\n" "\n" -" status actions\n" -" View failed actions\n" -"\n" -" status pcsd <node> ...\n" +" pcsd <node> ...\n" " Show the current status of pcsd on the specified nodes\n" "\n" -" status xml\n" +" xml\n" " 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 Pacemaker version and supported cluster stack(s) available with your current Pacemaker installation, the pacemakerd --features option is available to you." -msgstr "" - -#. Tag: programlisting -#, no-c-format -msgid "# pacemakerd --features" +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 "Pacemaker 1.1.8 (Build: 434edfa)\n" -" Supporting: generated-manpages agent-manpages ascii-docs publican-docs ncurses gcov libqb-logging libqb-ipc lha-fencing upstart systemd heartbeat corosync-native snmp" +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." +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." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Verification.pot b/doc/Clusters_from_Scratch/pot/Ch-Verification.pot index 08ab1f4ec1..6ad0af650c 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Verification.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Verification.pot @@ -1,183 +1,203 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Verify Cluster Installation" +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 pcs cluster auth command on earlier, you must authenticate on current node you are logged into before you will be allowed to start the cluster." +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 pcs cluster auth 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: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs cluster start --all\n" +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 pcs cluster startall command is to issue either of the below commands on each node in the cluster by hand." +msgid "An alternative to using the pcs cluster start --all command is to issue either of the below command sequences on each node in the cluster separately:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# pcs cluster start\n" "Starting Cluster..." msgstr "" #. Tag: para #, no-c-format msgid "or" msgstr "" -#. Tag: programlisting +#. 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 pcs cluster start nodename (or --all) 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 "The first thing to check is if cluster communication is happy, for that we use corosync-cfgtool." +msgid "First, use corosync-cfgtool to check whether cluster communication is happy:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# corosync-cfgtool -s\n" +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 id and no faults for the status." +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 id, and no faults 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 we check the membership and quorum APIs:" +msgid "Next, check the membership and quorum APIs:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# corosync-cmapctl | grep members\n" +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) = 1\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" -"# pcs status corosync\n" +"[root@pcmk-1 ~]# pcs status corosync\n" "Membership information\n" " --------------------------\n" " Nodeid Votes Name\n" -" 1 1 pcmk-1\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: para -#, no-c-format -msgid "All good!" -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." +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: programlisting +#. Tag: screen #, no-c-format -msgid "# ps axf\n" +msgid "[root@pcmk-1 ~]# ps axf\n" " PID TTY STAT TIME COMMAND\n" " 2 ? S 0:00 [kthreadd]\n" "...lots of processes...\n" -"28019 ? Ssl 0:03 /usr/sbin/corosync\n" -"28047 ? Ss 0:00 /usr/sbin/pacemakerd -f\n" -"28048 ? Ss 0:00 \\_ /usr/libexec/pacemaker/cib\n" -"28049 ? Ss 0:00 \\_ /usr/libexec/pacemaker/stonithd\n" -"28050 ? Ss 0:00 \\_ /usr/lib64/heartbeat/lrmd\n" -"28051 ? Ss 0:00 \\_ /usr/libexec/pacemaker/attrd\n" -"28052 ? Ss 0:00 \\_ /usr/libexec/pacemaker/pengine\n" -"28053 ? Ss 0:00 \\_ /usr/libexec/pacemaker/crmd" +" 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" msgstr "" #. Tag: para #, no-c-format -msgid "If that looks ok, check the pcs status output." +msgid "If that looks OK, check the pcs status output:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# pcs status\n" -"Last updated: Fri Sep 14 09:52:25 2012\n" -"Last change: Fri Sep 14 09:51:55 2012 via crmd on pcmk-2\n" +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.8-1.el7-60a19ed12fdb4d5c6a6b6767f52e5391e447fec0\n" -"2 Nodes configured, unknown expected votes\n" -"0 Resources configured.\n" +"Version: 1.1.12-a14efad\n" +"2 Nodes configured\n" +"0 Resources configured\n" +"\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"Full list of resources:" +"Full list of resources:\n" +"\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 "Next, check for any ERRORs during startup - there shouldn’t be any." +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: programlisting +#. Tag: screen +#, no-c-format +msgid "[root@pcmk-1 ~]# journalctl | grep -i error" +msgstr "" + +#. Tag: para #, no-c-format -msgid "# grep -i error /var/log/messages" +msgid "Other operating systems may report startup errors in other locations, for example /var/log/messages." 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/Clusters_from_Scratch.pot b/doc/Clusters_from_Scratch/pot/Clusters_from_Scratch.pot deleted file mode 100644 index 18734a24c0..0000000000 --- a/doc/Clusters_from_Scratch/pot/Clusters_from_Scratch.pot +++ /dev/null @@ -1,14 +0,0 @@ -# -# AUTHOR , YEAR. -# -msgid "" -msgstr "" -"Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\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" - diff --git a/doc/Clusters_from_Scratch/pot/Preface.pot b/doc/Clusters_from_Scratch/pot/Preface.pot index 2a5075c291..01aa1cc95d 100644 --- a/doc/Clusters_from_Scratch/pot/Preface.pot +++ b/doc/Clusters_from_Scratch/pot/Preface.pot @@ -1,19 +1,19 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 b4f86a7373..6552a88957 100644 --- a/doc/Clusters_from_Scratch/pot/Revision_History.pot +++ b/doc/Clusters_from_Scratch/pot/Revision_History.pot @@ -1,84 +1,109 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "" + diff --git a/doc/Pacemaker_Explained/en-US/Book_Info.xml b/doc/Pacemaker_Explained/en-US/Book_Info.xml index bce0089524..c189d07a6c 100644 --- a/doc/Pacemaker_Explained/en-US/Book_Info.xml +++ b/doc/Pacemaker_Explained/en-US/Book_Info.xml @@ -1,35 +1,35 @@ Configuration Explained An A-Z guide to Pacemaker's Configuration Options Pacemaker 1.1 - 6 + 7 0 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). diff --git a/doc/Pacemaker_Explained/en-US/Ch-Options.txt b/doc/Pacemaker_Explained/en-US/Ch-Options.txt index 0c1a2e7620..a2fbfe2473 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Options.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Options.txt @@ -1,404 +1,409 @@ = Cluster-Wide Configuration = == CIB Properties == Certain settings are defined by CIB properties (that is, attributes of the +cib+ tag) rather than with the rest of the cluster configuration in the +configuration+ section. 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. .CIB Properties [width="95%",cols="2m,5<",options="header",align="center"] |========================================================= |Field |Description | admin_epoch | indexterm:[Configuration Version,Cluster] indexterm:[Cluster,Option,Configuration Version] indexterm:[admin_epoch,Cluster Option] indexterm:[Cluster,Option,admin_epoch] 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 (+admin_epoch+, +epoch+, +num_updates+) tuple to replace the configuration on all the nodes -- which makes setting them, and setting them correctly, very important. +admin_epoch+ is never modified by the cluster; you can use this to make the configurations on any inactive nodes obsolete. _Never set this value to zero_. In such cases, the cluster cannot tell the difference between your configuration and the "empty" one used when nothing is found on disk. | epoch | indexterm:[epoch,Cluster Option] indexterm:[Cluster,Option,epoch] The cluster increments this every time the configuration is updated (usually by the administrator). | num_updates | indexterm:[num_updates,Cluster Option] indexterm:[Cluster,Option,num_updates] The cluster increments this every time the configuration or status is updated (usually by the cluster) and resets it to 0 when epoch changes. | validate-with | indexterm:[validate-with,Cluster Option] indexterm:[Cluster,Option,validate-with] Determines the type of XML validation that will be done on the configuration. If set to +none+, 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. |cib-last-written | indexterm:[cib-last-written,Cluster Property] indexterm:[Cluster,Property,cib-last-written] Indicates when the configuration was last written to disk. Maintained by the cluster; for informational purposes only. |have-quorum | indexterm:[have-quorum,Cluster Property] indexterm:[Cluster,Property,have-quorum] Indicates if the cluster has quorum. If false, this may mean that the cluster cannot start resources or fence other nodes (see +no-quorum-policy+ below). Maintained by the cluster. |dc-uuid | indexterm:[dc-uuid,Cluster Property] indexterm:[Cluster,Property,dc-uuid] 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. |========================================================= === Working with CIB Properties === 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. To change the ones that can be specified by the user, for example +admin_epoch+, one should use: ---- # cibadmin --modify --crm_xml '' ---- A complete set of CIB properties will look something like this: .Attributes set for a cib object ====== [source,XML] ------- ------- ====== == Cluster Options == Cluster options, as you might expect, control how the cluster behaves when confronted with certain situations. They are grouped into sets within the +crm_config+ section, and, in advanced configurations, there may be more than one set. (This will be described later in the section on <> 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. You can obtain an up-to-date list of cluster options, including their default values, by running the `man pengine` and `man crmd` commands. .Cluster Options [width="95%",cols="5m,2,11>). | enable-startup-probes | TRUE | indexterm:[enable-startup-probes,Cluster Option] indexterm:[Cluster,Option,enable-startup-probes] Should the cluster check for active resources during startup? | maintenance-mode | FALSE | indexterm:[maintenance-mode,Cluster Option] indexterm:[Cluster,Option,maintenance-mode] Should the cluster refrain from monitoring, starting and stopping resources? | stonith-enabled | TRUE | indexterm:[stonith-enabled,Cluster Option] indexterm:[Cluster,Option,stonith-enabled] 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. 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 _data loss_ if the unresponsive node still accesses shared storage, for example). See also the +requires+ meta-attribute in <>. | stonith-action | reboot | indexterm:[stonith-action,Cluster Option] indexterm:[Cluster,Option,stonith-action] Action to send to STONITH device. Allowed values are +reboot+ and +off+. The value +poweroff+ is also allowed, but is only used for legacy devices. | stonith-timeout | 60s | indexterm:[stonith-timeout,Cluster Option] indexterm:[Cluster,Option,stonith-timeout] How long to wait for STONITH actions (reboot, on, off) to complete +| concurrent-fencing | FALSE | +indexterm:[concurrent-fencing,Cluster Option] +indexterm:[Cluster,Option,concurrent-fencing] +Is the cluster allowed to initiate multiple fence actions concurrently? + | cluster-delay | 60s | indexterm:[cluster-delay,Cluster Option] indexterm:[Cluster,Option,cluster-delay] 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. | dc-deadtime | 20s | indexterm:[dc-deadtime,Cluster Option] indexterm:[Cluster,Option,dc-deadtime] How long to wait for a response from other nodes during startup. The "correct" value will depend on the speed/load of your network and the type of switches used. | cluster-recheck-interval | 15min | indexterm:[cluster-recheck-interval,Cluster Option] indexterm:[Cluster,Option,cluster-recheck-interval] Polling interval for time-based changes to options, resource parameters and constraints. 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). | pe-error-series-max | -1 | indexterm:[pe-error-series-max,Cluster Option] indexterm:[Cluster,Option,pe-error-series-max] The number of PE inputs resulting in ERRORs to save. Used when reporting problems. A value of -1 means unlimited (report all). | pe-warn-series-max | -1 | indexterm:[pe-warn-series-max,Cluster Option] indexterm:[Cluster,Option,pe-warn-series-max] The number of PE inputs resulting in WARNINGs to save. Used when reporting problems. A value of -1 means unlimited (report all). | pe-input-series-max | -1 | indexterm:[pe-input-series-max,Cluster Option] indexterm:[Cluster,Option,pe-input-series-max] The number of "normal" PE inputs to save. Used when reporting problems. A value of -1 means unlimited (report all). | remove-after-stop | FALSE | indexterm:[remove-after-stop,Cluster Option] indexterm:[Cluster,Option,remove-after-stop] _Advanced Use Only:_ 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. | startup-fencing | TRUE | indexterm:[startup-fencing,Cluster Option] indexterm:[Cluster,Option,startup-fencing] _Advanced Use Only:_ Should the cluster shoot unseen nodes? Not using the default is very unsafe! | election-timeout | 2min | indexterm:[election-timeout,Cluster Option] indexterm:[Cluster,Option,election-timeout] _Advanced Use Only:_ If you need to adjust this value, it probably indicates the presence of a bug. | shutdown-escalation | 20min | indexterm:[shutdown-escalation,Cluster Option] indexterm:[Cluster,Option,shutdown-escalation] _Advanced Use Only:_ If you need to adjust this value, it probably indicates the presence of a bug. | crmd-integration-timeout | 3min | indexterm:[crmd-integration-timeout,Cluster Option] indexterm:[Cluster,Option,crmd-integration-timeout] _Advanced Use Only:_ If you need to adjust this value, it probably indicates the presence of a bug. | crmd-finalization-timeout | 30min | indexterm:[crmd-finalization-timeout,Cluster Option] indexterm:[Cluster,Option,crmd-finalization-timeout] _Advanced Use Only:_ If you need to adjust this value, it probably indicates the presence of a bug. | crmd-transition-delay | 0s | indexterm:[crmd-transition-delay,Cluster Option] indexterm:[Cluster,Option,crmd-transition-delay] _Advanced Use Only:_ 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. |default-resource-stickiness | 0 | indexterm:[default-resource-stickiness,Cluster Option] indexterm:[Cluster,Option,default-resource-stickiness] _Deprecated:_ See <> instead | is-managed-default | TRUE | indexterm:[is-managed-default,Cluster Option] indexterm:[Cluster,Option,is-managed-default] _Deprecated:_ See <> instead | default-action-timeout | 20s | indexterm:[default-action-timeout,Cluster Option] indexterm:[Cluster,Option,default-action-timeout] _Deprecated:_ See <> instead |========================================================= === Querying and Setting Cluster Options === indexterm:[Querying,Cluster Option] indexterm:[Setting,Cluster Option] indexterm:[Cluster,Querying Options] indexterm:[Cluster,Setting Options] Cluster options can be queried and modified using the `crm_attribute` tool. To get the current value of +cluster-delay+, you can run: ---- # crm_attribute --query --name cluster-delay ---- which is more simply written as ---- # crm_attribute -G -n cluster-delay ---- If a value is found, you'll see a result like this: ---- # crm_attribute -G -n cluster-delay scope=crm_config name=cluster-delay value=60s ---- If no value is found, the tool will display an error: ---- # crm_attribute -G -n clusta-deway scope=crm_config name=clusta-deway value=(null) Error performing operation: No such device or address ---- To use a different value (for example, 30 seconds), simply run: ---- # crm_attribute --name cluster-delay --update 30s ---- To go back to the cluster's default value, you can delete the value, for example: ---- # crm_attribute --name cluster-delay --delete Deleted crm_config option: id=cib-bootstrap-options-cluster-delay name=cluster-delay ---- === When Options are Listed More Than Once === If you ever see something like the following, it means that the option you're modifying is present more than once. .Deleting an option that is listed twice ======= ------ # crm_attribute --name batch-limit --delete Multiple attributes match name=batch-limit in crm_config: Value: 50 (set=cib-bootstrap-options, id=cib-bootstrap-options-batch-limit) Value: 100 (set=custom, id=custom-batch-limit) Please choose from one of the matches above and supply the 'id' with --id ------- ======= 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 <>. diff --git a/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt b/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt index a5bcf0dcfa..d2880e0843 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt @@ -1,892 +1,901 @@ = STONITH = //// We prefer [[ch-stonith]], but older versions of asciidoc don't deal well with that construct for chapter headings //// anchor:ch-stonith[Chapter 13, STONITH] indexterm:[STONITH, Configuration] == What Is STONITH? == STONITH (an acronym for "Shoot The Other Node In The Head"), also called 'fencing', protects your data from being corrupted by rogue nodes or concurrent access. 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. 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. == What STONITH Device Should You Use? == It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one. 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. Likewise, any device that relies on the machine being active (such as SSH-based "devices" used during testing) are inappropriate. == Special Treatment of STONITH Resources == STONITH resources are somewhat special in Pacemaker. 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 'started' state in order to be used, thus allowing reliable use of STONITH devices in such a case. [NOTE] ==== 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. ==== All nodes have access to STONITH devices' definitions and instantiate them on-the-fly when needed, but preference is given to 'verified' instances, which are the ones that are 'started' according to the cluster's knowledge. 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. Fencing resources do work the same as regular resources in some respects: * +target-role+ can be used to enable or disable the resource * Location constraints can be used to prevent a specific node from using the resource [IMPORTANT] =========== 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. =========== See the table below or run `man stonithd` to see special instance attributes that may be set for any fencing resource, regardless of fence agent. .Properties of Fencing Resources [width="95%",cols="5m,2,3,10 ---- ==== Based on that, we would create a STONITH resource fragment that might look like this: .An IPMI-based STONITH Resource ==== [source,XML] ---- ---- ==== Finally, we need to enable STONITH: ---- # crm_attribute -t crm_config -n stonith-enabled -v true ---- == Advanced STONITH Configurations == Some people consider that having one fencing device is a single point of failure footnote:[Not true, since a node or resource must fail before fencing even has a chance to]; others prefer removing the node from the storage and network instead of turning it off. Whatever the reason, Pacemaker supports fencing nodes with multiple devices through a feature called 'fencing topologies'. Simply create the individual devices as you normally would, then define one or more +fencing-level+ entries in the +fencing-topology+ section of the configuration. * Each fencing level is attempted in order of ascending +index+. Allowed indexes are 0 to 9. * 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. * If the operation succeeds for all the listed devices in a level, the level is deemed to have passed. * The operation is finished when a level has passed (success), or all levels have been attempted (failed). * If the operation failed, the next step is determined by the Policy Engine and/or `crmd`. Some possible uses of topologies include: * Try poison-pill and fail back to power * Try disk and network, and fall back to power if either fails * Initiate a kdump and then poweroff the node .Properties of Fencing Levels [width="95%",cols="1m,3<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the level indexterm:[id,fencing-level] indexterm:[Fencing,fencing-level,id] |target |The name of a single node to which this level applies indexterm:[target,fencing-level] indexterm:[Fencing,fencing-level,target] |target-pattern |A regular expression matching the names of nodes to which this level applies '(since 1.1.14)' indexterm:[target-pattern,fencing-level] indexterm:[Fencing,fencing-level,target-pattern] |target-attribute |The name of a node attribute that is set for nodes to which this level applies '(since 1.1.14)' indexterm:[target-attribute,fencing-level] indexterm:[Fencing,fencing-level,target-attribute] |index |The order in which to attempt the levels. Levels are attempted in ascending order 'until one succeeds'. indexterm:[index,fencing-level] indexterm:[Fencing,fencing-level,index] |devices |A comma-separated list of devices that must all be tried for this level indexterm:[devices,fencing-level] indexterm:[Fencing,fencing-level,devices] |========================================================= .Fencing topology with different devices for different nodes ==== [source,XML] ---- ... ... ---- ==== === Example Dual-Layer, Dual-Device Fencing Topologies === The following example illustrates an advanced use of +fencing-topology+ in a cluster with the following properties: * 3 nodes (2 active prod-mysql nodes, 1 prod_mysql-rep in standby for quorum purposes) * the active nodes have an IPMI-controlled power board reached at 192.0.2.1 and 192.0.2.2 * 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) * the first fencing method uses the `fence_ipmi` agent * the second fencing method uses the `fence_apc_snmp` agent targetting 2 fencing devices (one per PSU, either port 10 or 11) * fencing is only implemented for the active nodes and has location constraints * fencing topology is set to try IPMI fencing first then default to a "sure-kill" dual PDU fencing In a normal failure scenario, STONITH will first select +fence_ipmi+ to try to kill the faulty node. Using a fencing topology, if that first method fails, STONITH will then move on to selecting +fence_apc_snmp+ twice: * once for the first PDU * again for the second PDU 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, +fence_ipmi+, and so on until the node is fenced or fencing action is cancelled. .First fencing method: single IPMI device Each cluster node has it own dedicated IPMI channel that can be called for fencing using the following primitives: [source,XML] ---- ---- .Second fencing method: dual PDU devices 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: - Node 1, PDU 1, PSU 1 @ port 10 - Node 1, PDU 2, PSU 2 @ port 10 - Node 2, PDU 1, PSU 1 @ port 11 - Node 2, PDU 2, PSU 2 @ port 11 The matching fencing agents are configured as follows: [source,XML] ---- ---- .Location Constraints 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: [source,XML] ---- ---- .Fencing topology 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. [source,XML] ---- ---- Please note, in +fencing-topology+, the lowest +index+ value determines the priority of the first fencing method. .Final configuration Put together, the configuration looks like this: [source,XML] ---- ... ... ---- == Remapping Reboots == When the cluster needs to reboot a node, whether because +stonith-action+ is +reboot+ or because a reboot was manually requested (such as by `stonith_admin --reboot`), it will remap that to other commands in two cases: . If the chosen fencing device does not support the +reboot+ command, the cluster will ask it to perform +off+ instead. . If a fencing topology level with multiple devices must be executed, the cluster will ask all the devices to perform +off+, then ask the devices to perform +on+. 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. In such a case, the fencing operation will be treated as successful as long as the +off+ commands succeed, because then it is safe for the cluster to recover any resources that were on the node. Timeouts and errors in the +on+ phase will be logged but ignored. When a reboot operation is remapped, any action-specific timeout for the remapped action will be used (for example, +pcmk_off_timeout+ will be used when executing the +off+ command, not +pcmk_reboot_timeout+). [NOTE] ==== 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. ==== diff --git a/doc/Pacemaker_Explained/en-US/Revision_History.xml b/doc/Pacemaker_Explained/en-US/Revision_History.xml index 33010d5c0e..4bd3485d26 100644 --- a/doc/Pacemaker_Explained/en-US/Revision_History.xml +++ b/doc/Pacemaker_Explained/en-US/Revision_History.xml @@ -1,72 +1,84 @@ Revision History 1-0 19 Oct 2009 AndrewBeekhofandrew@beekhof.net Import from Pages.app 2-0 26 Oct 2009 AndrewBeekhofandrew@beekhof.net Cleanup and reformatting of docbook xml complete 3-0 Tue Nov 12 2009 AndrewBeekhofandrew@beekhof.net Split book into chapters and pass validation Re-organize book for use with Publican 4-0 Mon Oct 8 2012 AndrewBeekhofandrew@beekhof.net Converted to asciidoc (which is converted to docbook for use with Publican) 5-0 Mon Feb 23 2015 KenGaillotkgaillot@redhat.com Update for clarity, stylistic consistency and current command-line syntax 6-0 Tue Dec 8 2015 KenGaillotkgaillot@redhat.com Update for Pacemaker 1.1.14 + + 7-0 + Tue May 3 2016 + KenGaillotkgaillot@redhat.com + + + + Update for Pacemaker 1.1.15 + + + + diff --git a/doc/Pacemaker_Explained/pot/Ap-Changes.pot b/doc/Pacemaker_Explained/pot/Ap-Changes.pot index 087fb6e5c5..271f0f097c 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Changes.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Changes.pot @@ -1,194 +1,194 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "What Changed in 1.0" msgstr "" #. Tag: title #, no-c-format msgid "New" msgstr "" #. Tag: para #, no-c-format msgid "Failure timeouts. See " msgstr "" #. Tag: para #, no-c-format msgid "New section for resource and operation defaults. See and " msgstr "" #. Tag: para #, no-c-format msgid "Tool for making offline configuration changes. See " msgstr "" #. Tag: para #, no-c-format msgid "Rules, instance_attributes, meta_attributes and sets of operations can be defined once and referenced in multiple places. See " msgstr "" #. Tag: para #, no-c-format msgid "The CIB now accepts XPath-based create/modify/delete operations. See the cibadmin help text." msgstr "" #. Tag: para #, no-c-format -msgid "Multi-dimensional colocation and ordering constraints. See and " +msgid "Multi-dimensional colocation and ordering constraints. See and " msgstr "" #. Tag: para #, no-c-format msgid "The ability to connect to the CIB from non-cluster machines. See " msgstr "" #. Tag: para #, no-c-format msgid "Allow recurring actions to be triggered at known times. See " 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 "master_slave was renamed to master" msgstr "" #. Tag: para #, no-c-format msgid "The attributes container tag was removed" msgstr "" #. Tag: para #, no-c-format msgid "The operation field pre-req has been renamed requires" msgstr "" #. Tag: para #, no-c-format msgid "All operations must have an interval, start/stop must have it set to zero" msgstr "" #. Tag: para #, no-c-format msgid "The stonith-enabled option now defaults to true." msgstr "" #. Tag: para #, no-c-format msgid "The cluster will refuse to start resources if stonith-enabled 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. See and " msgstr "" #. Tag: para #, no-c-format msgid "resource-failure-stickiness has been replaced by migration-threshold. See " 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 RelaxNG schema validation and libxml2 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 ha.cf." 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 crm_config. See and instead." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-Debug.pot b/doc/Pacemaker_Explained/pot/Ap-Debug.pot index d5c67ac12a..3da22721c0 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Debug.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Debug.pot @@ -1,189 +1,189 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Debugging Cluster Startup" msgstr "" #. Tag: title #, no-c-format msgid "Corosync" msgstr "" #. Tag: title #, no-c-format msgid "Prerequisites" msgstr "" #. Tag: title #, no-c-format msgid "Minimum logging configuration" msgstr "" #. Tag: programlisting #, no-c-format msgid "\n" " # /etc/init.d/openais start\n" " \n" " \n" " logging {\n" " to_syslog: yes\n" " syslog_facility: daemon\n" " }\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "Whatever other logging you have, these two lines are required for Pacemaker clusters" msgstr "" #. Tag: title #, no-c-format msgid "Confirm Corosync Started" msgstr "" #. Tag: title #, no-c-format msgid "Expected output when starting openais" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # /etc/init.d/openais start\n" " \n" " \n" " Starting Corosync daemon (aisexec): starting... rc=0: OK\n" " \n" " " msgstr "" #. Tag: title #, no-c-format msgid "Expected log messages - startup" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep -e \"openais.*network interface\" -e \"AIS Executive Service\" /var/log/messages\n" " \n" " \n" " Aug 27 16:23:37 test1 openais[26337]: [MAIN ] AIS Executive Service RELEASE 'subrev 1152 version 0.80'\n" " Aug 27 16:23:38 test1 openais[26337]: [MAIN ] AIS Executive Service: started and ready to provide service.\n" " Aug 27 16:23:38 test1 openais[26337]: [TOTEM] The network interface [192.168.9.41] is now up.\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "The versions may differ, but you should see Corosync indicate it started and sucessfully attached to the machine's network interface" msgstr "" #. Tag: title #, no-c-format msgid "Expected log messages - membership" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep CLM /var/log/messages\n" " \n" " \n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41)\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41)\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] got nodejoin message 192.168.9.41\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "The exact messages will differ, but you should see a new membership formed with the real IP address of your node" msgstr "" #. Tag: title #, no-c-format msgid "Checking Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Now that we have confirmed that Corosync is functional we can check the rest of the stack." msgstr "" #. Tag: title #, no-c-format msgid "Expected Pacemaker startup logging for Corosync" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep pcmk_plugin_init /var/log/messages\n" " \n" " \n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: CRM: Initialized\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] Logging: Initialized pcmk_plugin_init\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Service: 9\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Local hostname: test1\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "If you don't see these messages, or some like them, there is likely a problem finding or loading the pacemaker plugin." msgstr "" #. Tag: title #, no-c-format msgid "Expected process listing on a 64-bit machine" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # ps axf\n" " \n" " \n" " 3718 ? Ssl 0:05 /usr/sbin/aisexec\n" " 3723 ? SLs 0:00 \\_ /usr/lib64/heartbeat/stonithd\n" " 3724 ? S 0:05 \\_ /usr/lib64/heartbeat/cib\n" " 3725 ? S 0:21 \\_ /usr/lib64/heartbeat/lrmd\n" " 3726 ? S 0:01 \\_ /usr/lib64/heartbeat/attrd\n" " 3727 ? S 0:00 \\_ /usr/lib64/heartbeat/pengine\n" " 3728 ? S 0:01 \\_ /usr/lib64/heartbeat/crmd\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "On 32-bit systems the exact path may differ, but all the above processes should be listed." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-FAQ.pot b/doc/Pacemaker_Explained/pot/Ap-FAQ.pot index 8ec3c15447..47d40a5941 100644 --- a/doc/Pacemaker_Explained/pot/Ap-FAQ.pot +++ b/doc/Pacemaker_Explained/pot/Ap-FAQ.pot @@ -1,159 +1,124 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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: title -#, no-c-format -msgid "History" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Why is the Project Called PacemakernamingPacemaker?" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "First of all, the reason its not called the CRM is because of the abundance of terms that are commonly abbreviated to those three letters." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "The Pacemaker name came from Kham, a good friend of mine, and was originally used by a Java GUI that I was prototyping in early 2007. Alas other commitments have prevented the GUI from progressing much and, when it came time to choose a name for this project, Lars suggested it was an even better fit for an independent CRM." -msgstr "" - #. Tag: para #, no-c-format -msgid "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." +msgid "Why is the Project Called Pacemaker?" msgstr "" #. Tag: para #, no-c-format -msgid "There were a number of other names (and acronyms) tossed around, but suffice to say \"Pacemaker\" was the best" +msgid " Pacemaker First of all, the reason it’s not called the CRM is because of the abundance of terms http://en.wikipedia.org/wiki/CRM that are commonly abbreviated to those three letters. The Pacemaker name came from Kham, http://khamsouk.souvanlasy.com/ 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 "The decision was made to spin-off the CRM into its own project after the 2.1.3 Heartbeat release in order to:" msgstr "" #. Tag: para #, no-c-format msgid "support both the Corosync and Heartbeat cluster stacks equally" msgstr "" #. Tag: para #, no-c-format msgid "decouple the release cycles of two projects at very different stages of their life-cycles" msgstr "" #. Tag: para #, no-c-format -msgid "foster the clearer package boundaries, thus leading to" +msgid "foster clearer package boundaries, thus leading to better and more stable interfaces" msgstr "" #. Tag: para #, no-c-format -msgid "better and more stable interfaces" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Setup" +msgid "What Messaging Layers are Supported?" msgstr "" #. Tag: para #, no-c-format -msgid "What Messaging Layers Messaging Layers are Supported?" +msgid " Messaging Layers " msgstr "" #. Tag: para #, no-c-format -msgid "Corosync ()" +msgid "Corosync" msgstr "" #. Tag: para #, no-c-format -msgid "Heartbeat ()" +msgid "Heartbeat" msgstr "" #. Tag: para #, no-c-format -msgid "Can I Choose which Messaging Layer to use at Run Time?" +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 "Which Messaging Layer Should I Choose?" +msgid " Which Messaging Layer Should I Choose?" msgstr "" #. Tag: para #, no-c-format -msgid "This is discussed in ." +msgid " ClusterChoosing Between Heartbeat and Corosync Choosing Between Heartbeat and Corosync Cluster StackCorosync Corosync Corosync Cluster StackHeartbeat Heartbeat Heartbeat 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." msgstr "" #. Tag: para #, no-c-format msgid "Where Can I Get Pre-built Packages?" msgstr "" #. Tag: para #, no-c-format -msgid "Official packages for most major .rpm and based distributions are available from the ClusterLabs Website." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "For Debian packages, building from source and details on using the above repositories, see our installation page." +msgid "Most major Linux distributions have pacemaker packages in their standard package repositories. See the Install wiki page for details." msgstr "" #. Tag: para #, no-c-format msgid "What Versions of Pacemaker Are Supported?" msgstr "" #. Tag: para #, no-c-format -msgid "Please refer to the Releases page for an up-to-date list of versions supported directly by the project." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "When seeking assistance, please try to ensure you have one of these versions." +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 Releases wiki page 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-Install.pot b/doc/Pacemaker_Explained/pot/Ap-Install.pot index 9edfc629df..6148f76a9c 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Install.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Install.pot @@ -1,195 +1,268 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +msgid "Installing" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Installing the Software" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Most major Linux distributions have pacemaker packages in their standard package repositories, or the software can be built from source code. See the Install wiki page for details." msgstr "" #. Tag: para #, no-c-format -msgid "The following text may no longer be accurate in some places." +msgid "See Which Messaging Layer Should I Choose? for information about choosing a messaging layer." msgstr "" #. Tag: title #, no-c-format -msgid "Choosing a Cluster Stack" +msgid "Enabling Pacemaker" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid " ClusterChoosing Between Heartbeat and Corosync Choosing Between Heartbeat and Corosync Cluster StackCorosync Corosync Corosync Cluster StackHeartbeat Heartbeat Heartbeat " +msgid "Enabling Pacemaker For Corosync 2.x" msgstr "" #. Tag: para #, no-c-format -msgid "Ultimately the choice of cluster stack is a personal decision that must be made in the context of you or your company’s needs and strategic direction. Pacemaker currently functions equally well with both stacks." +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 "Here are some factors that may influence the decision:" +msgid "Corosync configuration is normally located in /etc/corosync/corosync.conf." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "SUSE/Novell, Red Hat and Oracle are all putting their collective weight behind the Corosync cluster stack." +msgid "Corosync 2.x configuration file for two nodes myhost1 and myhost2" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "Using Corosync gives your applications access to the following additional cluster services" +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: para +#. Tag: title #, no-c-format -msgid "distributed locking service" +msgid "Corosync 2.x configuration file for three nodes myhost1, myhost2 and myhost3" msgstr "" -#. Tag: para +#. Tag: screen #, no-c-format -msgid "extended virtual synchronization service" +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 "cluster closed process group service" +msgid "In the above examples, the totem section defines what protocol version and options (including encryption) to use, Please consult the Corosync website (http://www.corosync.org/) and documentation for details on enabling encryption and peer authentication for the cluster. and gives the cluster a unique name (mycluster in these examples)." msgstr "" #. Tag: para #, no-c-format -msgid "It is likely that Pacemaker, at some point in the future, will make use of some of these additional services not provided by Heartbeat" +msgid "The node section lists the nodes in this cluster. (See for how this affects pacemaker.)" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Enabling Pacemaker" +msgid "The quorum section defines how the cluster uses quorum. The important thing is that two-node clusters must be handled specially, so two_node: 1 must be defined for two-node clusters (and only for two-node clusters)." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "For Corosync" +msgid "The logging section should be self-explanatory." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "The Corosync configuration is normally located in /etc/corosync/corosync.conf and an example for a machine with an address of 1.2.3.4 in a cluster communicating on port 1234 (without peer authentication and message encryption) is shown below." +msgid "Enabling Pacemaker For Corosync 1.x" msgstr "" #. Tag: title #, no-c-format -msgid "An example Corosync configuration file" +msgid "Corosync 1.x configuration file for a cluster with all nodes on the 192.0.2.0/24 network" msgstr "" #. Tag: programlisting #, no-c-format msgid " totem {\n" " version: 2\n" " secauth: off\n" " threads: 0\n" " interface {\n" " ringnumber: 0\n" -" bindnetaddr: 1.2.3.4\n" +" bindnetaddr: 192.0.2.0\n" " mcastaddr: 239.255.1.1\n" " mcastport: 1234\n" " }\n" " }\n" " logging {\n" " fileline: off\n" " to_syslog: yes\n" " syslog_facility: daemon\n" " }\n" " amf {\n" " mode: disabled\n" " }" msgstr "" #. Tag: para #, no-c-format -msgid "The logging should be mostly obvious and the amf section refers to the Availability Management Framework and is not covered in this document." +msgid "With corosync 1.x, the totem section contains the protocol version and options as with 2.x. However, nodes are also listed here, in the interface section. The bindnetaddr option is usually the network address, thus allowing the same configuration file to be used on all nodes. IPv4 or IPv6 addresses can be used with corosync." msgstr "" #. Tag: para #, no-c-format -msgid "The interesting part of the configuration is the totem section. This is where we define how the node can communicate with the rest of the cluster and what protocol version and options (including encryption Please consult the Corosync website (http://www.corosync.org/) and documentation for details on enabling encryption and peer authentication for the cluster. ) it should use. Beginners are encouraged to use the values shown and modify the interface section based on their network." +msgid "The amf section refers to the Availability Management Framework and is not covered in this document." msgstr "" #. Tag: para #, no-c-format -msgid "It is also possible to configure Corosync for an IPv6 based environment. Simply configure bindnetaddr and mcastaddr with their IPv6 equivalents, eg." +msgid "The above corosync configuration is enough for corosync to operate by itself, but corosync 1.x additionally needs to be told when it is being used in conjunction with Pacemaker. This can be accomplished in one of two ways:" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Example options for an IPv6 environment" +msgid "Via the CMAN software provided with Red Hat Enterprise Linux 6 and its derivatives" msgstr "" -#. Tag: programlisting +#. Tag: para +#, no-c-format +msgid "Via the pacemaker corosync plugin" +msgstr "" + +#. Tag: para #, no-c-format -msgid " bindnetaddr: fec0::1:a800:4ff:fe00:20\n" -" mcastaddr: ff05::1" +msgid "To use CMAN, consult its documentation." msgstr "" #. Tag: para #, no-c-format -msgid "To tell Corosync to use the Pacemaker cluster manager, add the following fragment to a functional Corosync configuration and restart the cluster." +msgid "To use the pacemaker corosync plugin, add the following fragment to the corosync configuration and restart the cluster." msgstr "" #. Tag: title #, no-c-format -msgid "Configuration fragment for enabling Pacemaker under Corosync" +msgid "Corosync 1._x_configuration fragment to enable Pacemaker plugin" msgstr "" #. Tag: programlisting #, no-c-format msgid "aisexec {\n" " user: root\n" " group: root\n" "}\n" "service {\n" " name: pacemaker\n" " ver: 0\n" "}" msgstr "" #. Tag: para #, no-c-format msgid "The cluster needs to be run as root so that its child processes (the lrmd in particular) have sufficient privileges to perform the actions requested of it. After all, a cluster manager that can’t add an IP address or start apache is of little use." msgstr "" #. Tag: para #, no-c-format msgid "The second directive is the one that actually instructs the cluster to run Pacemaker." msgstr "" #. Tag: title #, no-c-format -msgid "For Heartbeat" +msgid "Enabling Pacemaker For Heartbeat" msgstr "" #. Tag: para #, no-c-format -msgid "Add the following to a functional ha.cf configuration file and restart Heartbeat:" +msgid "See the heartbeat documentation for how to set up a ha.cf configuration file." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To enable the use of pacemaker with heartbeat, add the following to a functional ha.cf configuration file and restart Heartbeat:" msgstr "" #. Tag: title #, no-c-format -msgid "Configuration fragment for enabling Pacemaker under Heartbeat" +msgid "Heartbeat configuration fragment to enable Pacemaker" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "crm respawn" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-LSB.pot b/doc/Pacemaker_Explained/pot/Ap-LSB.pot index ed87bf50cf..a09d77916c 100644 --- a/doc/Pacemaker_Explained/pot/Ap-LSB.pot +++ b/doc/Pacemaker_Explained/pot/Ap-LSB.pot @@ -1,139 +1,139 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "init-Script LSB Compliance" +msgid "Init Script LSB Compliance" msgstr "" #. Tag: para #, no-c-format -msgid "The relevant part of LSB spec includes a description of all the return codes listed here." +msgid "The relevant part of the LSB specifications includes a description of all the return codes listed here." msgstr "" #. Tag: para #, no-c-format -msgid "Assuming some_service is configured correctly and currently not active, the following sequence will help you determine if it is LSB compatible:" +msgid "Assuming some_service 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: programlisting +#. 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 result: 0 (in addition to the regular output)?" +msgid "Did the command print result: 0 (in addition to its usual output)?" msgstr "" #. Tag: para #, no-c-format msgid "Status (running):" msgstr "" -#. Tag: programlisting +#. 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: programlisting +#. 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 result: 3 (in addition to the regular output)?" +msgid "Did the command print result: 3 (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." +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_Explained/pot/Ap-OCF.pot b/doc/Pacemaker_Explained/pot/Ap-OCF.pot index eb5b72cdc4..34e1c3032d 100644 --- a/doc/Pacemaker_Explained/pot/Ap-OCF.pot +++ b/doc/Pacemaker_Explained/pot/Ap-OCF.pot @@ -1,529 +1,514 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "More About OCF Resource Agents" msgstr "" #. Tag: title #, no-c-format msgid "Location of Custom Scripts" msgstr "" #. Tag: para #, no-c-format -msgid " OCF Resource Agents OCF Resource Agents are found in /usr/lib/ocf/resource.d/provider." +msgid " OCF Resource Agents OCF Resource Agents are found in /usr/lib/ocf/resource.d/provider" msgstr "" #. Tag: para #, no-c-format -msgid "When creating your own agents, you are encouraged to create a new directory under /usr/lib/ocf/resource.d/ so that they are not confused with (or overwritten by) the agents shipped with Heartbeat." +msgid "When creating your own agents, you are encouraged to create a new directory under /usr/lib/ocf/resource.d/ 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 chose the provider name of bigCorp and wanted a new resource named bigApp, you would create a script called /usr/lib/ocf/resource.d/bigCorp/bigApp and define a resource:" +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 /usr/lib/ocf/resource.d/bigCorp/bigApp and define a resource:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"custom-app\" class=\"ocf\" provider=\"bigCorp\" type=\"bigApp\"/>" 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" +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 "start" 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. startOCF Action OCF Action OCFActionstart Actionstart start " msgstr "" #. Tag: para #, no-c-format msgid "stop" 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. stopOCF Action OCF Action OCFActionstop Actionstop stop " msgstr "" #. Tag: para #, no-c-format msgid "monitor" 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. monitorOCF Action OCF Action OCFActionmonitor Actionmonitor monitor " 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 "meta-data" 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. meta-dataOCF Action OCF Action OCFActionmeta-data Actionmeta-data meta-data " msgstr "" #. Tag: para #, no-c-format -msgid "NOTE: This is not performed as root." +msgid "NOTE: This is not performed as root." msgstr "" #. Tag: para #, no-c-format msgid "validate-all" msgstr "" #. Tag: para #, no-c-format msgid "Verify the supplied parameters" msgstr "" #. Tag: para #, no-c-format -msgid "Exit with 0 if parameters are valid, 2 if not valid, 6 if resource is not configured. validate-allOCF Action OCF Action OCFActionvalidate-all Actionvalidate-all validate-all " +msgid "Return 0 if parameters are valid, 2 if not valid, and 6 if resource is not configured. validate-allOCF Action OCF Action OCFActionvalidate-all Actionvalidate-all validate-all " msgstr "" #. Tag: para #, no-c-format -msgid "Additional requirements (not part of the OCF specs) are placed on agents that will be used for advanced concepts like clones and multi-state resources." +msgid "Additional requirements (not part of the OCF specification) are placed on agents that will be used for advanced concepts such as clones and multi-state resources." msgstr "" #. Tag: title #, no-c-format -msgid "Optional Actions for OCF Agents" +msgid "Optional Actions for OCF Resource Agents" msgstr "" #. Tag: para #, no-c-format msgid "promote" msgstr "" #. Tag: para #, no-c-format -msgid "Promote the local instance of a multi-state resource to the master/primary state." +msgid "Promote the local instance of a multi-state resource to the master (primary) state." msgstr "" #. Tag: para #, no-c-format msgid "Return 0 on success promoteOCF Action OCF Action OCFActionpromote Actionpromote promote " msgstr "" #. Tag: para #, no-c-format msgid "demote" msgstr "" #. Tag: para #, no-c-format -msgid "Demote the local instance of a multi-state resource to the slave/secondary state." +msgid "Demote the local instance of a multi-state resource to the slave (secondary) state." msgstr "" #. Tag: para #, no-c-format msgid "Return 0 on success demoteOCF Action OCF Action OCFActiondemote Actiondemote demote " msgstr "" #. Tag: para #, no-c-format msgid "notify" 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." +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 notifyOCF Action OCF Action OCFActionnotify Actionnotify notify " msgstr "" #. Tag: para #, no-c-format -msgid "One action specified in the OCF specs is not currently used by the cluster:" +msgid "One action specified in the OCF specs, recover, is not currently used by the cluster. It is intended to be a variant of the start action that tries to recover a resource locally." msgstr "" #. Tag: para #, no-c-format -msgid "recover - a variant of the start action, this should try to recover a resource locally." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Remember to use ocf-tester ocf-tester to verify that your new agent complies with the OCF standard properly." +msgid "If you create a new OCF resource agent, use ocf-tester ocf-tester 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." +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 "soft" 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 softOCF error OCF error OCFerrorsoft errorsoft soft " msgstr "" #. Tag: para #, no-c-format msgid "hard" 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 hardOCF error OCF error OCFerrorhard errorhard hard " msgstr "" #. Tag: para #, no-c-format msgid "fatal" msgstr "" #. Tag: para #, no-c-format -msgid "A non-transient error that will be common to all cluster nodes (eg. a bad configuration was specified)" +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 fatalOCF error OCF error OCFerrorfatal errorfatal fatal " msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "Assuming an action is considered to have failed, the following table outlines the different OCF return codes and the type of recovery the cluster will initiate when it is received." +msgid "OCF Return Codes" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "OCF Return Codes" +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. OCF_SUCCESS) 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 "0" msgstr "" #. Tag: para #, no-c-format msgid "OCF_SUCCESS" 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. Return CodeOCF_SUCCESS OCF_SUCCESS Return Code0OCF_SUCCESS 0OCF_SUCCESS OCF_SUCCESS " msgstr "" #. Tag: para #, no-c-format msgid "1" msgstr "" #. Tag: para #, no-c-format msgid "OCF_ERR_GENERIC" msgstr "" #. Tag: para #, no-c-format msgid "Generic \"there was a problem\" error code. Return CodeOCF_ERR_GENERIC OCF_ERR_GENERIC Return Code1OCF_ERR_GENERIC 1OCF_ERR_GENERIC OCF_ERR_GENERIC " msgstr "" #. Tag: para #, no-c-format msgid "2" msgstr "" #. Tag: para #, no-c-format msgid "OCF_ERR_ARGS" msgstr "" #. Tag: para #, no-c-format -msgid "The resource’s configuration is not valid on this machine. Eg. refers to a location/tool not found on the node. Return CodeOCF_ERR_ARGS OCF_ERR_ARGS Return Code2OCF_ERR_ARGS 2OCF_ERR_ARGS OCF_ERR_ARGS " +msgid "The resource’s configuration is not valid on this machine. E.g. it refers to a location not found on the node. Return CodeOCF_ERR_ARGS OCF_ERR_ARGS Return Code2OCF_ERR_ARGS 2OCF_ERR_ARGS OCF_ERR_ARGS " msgstr "" #. Tag: para #, no-c-format msgid "3" msgstr "" #. Tag: para #, no-c-format msgid "OCF_ERR_UNIMPLEMENTED" msgstr "" #. Tag: para #, no-c-format msgid "The requested action is not implemented. Return CodeOCF_ERR_UNIMPLEMENTED OCF_ERR_UNIMPLEMENTED Return Code3OCF_ERR_UNIMPLEMENTED 3OCF_ERR_UNIMPLEMENTED OCF_ERR_UNIMPLEMENTED " msgstr "" #. Tag: para #, no-c-format msgid "4" msgstr "" #. Tag: para #, no-c-format msgid "OCF_ERR_PERM" msgstr "" #. Tag: para #, no-c-format msgid "The resource agent does not have sufficient privileges to complete the task. Return CodeOCF_ERR_PERM OCF_ERR_PERM Return Code4OCF_ERR_PERM 4OCF_ERR_PERM OCF_ERR_PERM " msgstr "" #. Tag: para #, no-c-format msgid "5" msgstr "" #. Tag: para #, no-c-format msgid "OCF_ERR_INSTALLED" msgstr "" #. Tag: para #, no-c-format msgid "The tools required by the resource are not installed on this machine. Return CodeOCF_ERR_INSTALLED OCF_ERR_INSTALLED Return Code5OCF_ERR_INSTALLED 5OCF_ERR_INSTALLED OCF_ERR_INSTALLED " msgstr "" #. Tag: para #, no-c-format msgid "6" msgstr "" #. Tag: para #, no-c-format msgid "OCF_ERR_CONFIGURED" msgstr "" #. Tag: para #, no-c-format -msgid "The resource’s configuration is invalid. Eg. required parameters are missing. Return CodeOCF_ERR_CONFIGURED OCF_ERR_CONFIGURED Return Code6OCF_ERR_CONFIGURED 6OCF_ERR_CONFIGURED OCF_ERR_CONFIGURED " +msgid "The resource’s configuration is invalid. E.g. required parameters are missing. Return CodeOCF_ERR_CONFIGURED OCF_ERR_CONFIGURED Return Code6OCF_ERR_CONFIGURED 6OCF_ERR_CONFIGURED OCF_ERR_CONFIGURED " msgstr "" #. Tag: para #, no-c-format msgid "7" msgstr "" #. Tag: para #, no-c-format msgid "OCF_NOT_RUNNING" 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. Return CodeOCF_NOT_RUNNING OCF_NOT_RUNNING Return Code7OCF_NOT_RUNNING 7OCF_NOT_RUNNING OCF_NOT_RUNNING " msgstr "" #. Tag: para #, no-c-format msgid "N/A" msgstr "" #. Tag: para #, no-c-format msgid "8" msgstr "" #. Tag: para #, no-c-format msgid "OCF_RUNNING_MASTER" msgstr "" #. Tag: para #, no-c-format -msgid "The resource is running in Master mode. Return CodeOCF_RUNNING_MASTER OCF_RUNNING_MASTER Return Code8OCF_RUNNING_MASTER 8OCF_RUNNING_MASTER OCF_RUNNING_MASTER " +msgid "The resource is running in master mode. Return CodeOCF_RUNNING_MASTER OCF_RUNNING_MASTER Return Code8OCF_RUNNING_MASTER 8OCF_RUNNING_MASTER OCF_RUNNING_MASTER " msgstr "" #. Tag: para #, no-c-format msgid "9" msgstr "" #. Tag: para #, no-c-format msgid "OCF_FAILED_MASTER" 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. Return CodeOCF_FAILED_MASTER OCF_FAILED_MASTER Return Code9OCF_FAILED_MASTER 9OCF_FAILED_MASTER OCF_FAILED_MASTER " +msgid "The resource is in master mode but has failed. The resource will be demoted, stopped and then started (and possibly promoted) again. Return CodeOCF_FAILED_MASTER OCF_FAILED_MASTER Return Code9OCF_FAILED_MASTER 9OCF_FAILED_MASTER OCF_FAILED_MASTER " msgstr "" #. Tag: para #, no-c-format msgid "other" msgstr "" -#. Tag: para -#, no-c-format -msgid "NA" -msgstr "" - #. Tag: para #, no-c-format msgid "Custom error code. Return Codeother other " msgstr "" #. Tag: para #, no-c-format -msgid "Although counterintuitive, even actions that return 0 (aka. OCF_SUCCESS) can be considered to have failed." -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Exceptions" +msgid "Exceptions to the recovery handling described above:" msgstr "" #. Tag: para #, no-c-format -msgid "Non-recurring monitor actions (probes) that find a resource active (or in Master mode) will not result in recovery action unless it is also found active elsewhere" +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 multiple-active property of the resource" +msgid "The recovery action taken when a resource is found active more than once is determined by the resource’s multiple-active property (see )." msgstr "" #. Tag: para #, no-c-format -msgid "Recurring actions that return OCF_ERR_UNIMPLEMENTED do not cause any type of recovery" +msgid "Recurring actions that return OCF_ERR_UNIMPLEMENTED do not cause any type of recovery." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-Samples.pot b/doc/Pacemaker_Explained/pot/Ap-Samples.pot index 63f6983420..e6aac2e68a 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Samples.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Samples.pot @@ -1,173 +1,184 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "<cib admin_epoch=\"0\" epoch=\"0\" num_updates=\"0\" have-quorum=\"false\">\n" +msgid "<cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\">\n" " <configuration>\n" " <crm_config/>\n" " <nodes/>\n" " <resources/>\n" " <constraints/>\n" " </configuration>\n" " <status/>\n" "</cib>" msgstr "" #. Tag: title #, no-c-format msgid "Simple" msgstr "" #. Tag: title #, no-c-format -msgid "Simple Configuration - 2 nodes, some cluster options and a resource" +msgid "A simple configuration with two nodes, some cluster options and a resource" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<cib admin_epoch=\"0\" epoch=\"1\" num_updates=\"0\" have-quorum=\"false\"\n" -" validate-with=\"pacemaker-1.0\">\n" +msgid "<cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\">\n" " <configuration>\n" " <crm_config>\n" -" <nvpair id=\"option-1\" name=\"symmetric-cluster\" value=\"true\"/>\n" -" <nvpair id=\"option-2\" name=\"no-quorum-policy\" value=\"stop\"/>\n" +" <cluster_property_set id=\"cib-bootstrap-options\">\n" +" <nvpair id=\"option-1\" name=\"symmetric-cluster\" value=\"true\"/>\n" +" <nvpair id=\"option-2\" name=\"no-quorum-policy\" value=\"stop\"/>\n" +" <nvpair id=\"option-3\" name=\"stonith-enabled\" value=\"0\"/>\n" +" </cluster_property_set>\n" " </crm_config>\n" -" <op_defaults>\n" -" <nvpair id=\"op-default-1\" name=\"timeout\" value=\"30s\"/>\n" -" </op_defaults>\n" -" <rsc_defaults>\n" -" <nvpair id=\"rsc-default-1\" name=\"resource-stickiness\" value=\"100\"/>\n" -" <nvpair id=\"rsc-default-2\" name=\"migration-threshold\" value=\"10\"/>\n" -" </rsc_defaults>\n" " <nodes>\n" " <node id=\"xxx\" uname=\"c001n01\" type=\"normal\"/>\n" " <node id=\"yyy\" uname=\"c001n02\" type=\"normal\"/>\n" " </nodes>\n" " <resources>\n" " <primitive id=\"myAddr\" class=\"ocf\" provider=\"heartbeat\" type=\"IPaddr\">\n" " <operations>\n" " <op id=\"myAddr-monitor\" name=\"monitor\" interval=\"300s\"/>\n" " </operations>\n" -" <instance_attributes>\n" -" <nvpair name=\"ip\" value=\"10.0.200.30\"/>\n" +" <instance_attributes id=\"myAddr-params\">\n" +" <nvpair id=\"myAddr-ip\" name=\"ip\" value=\"192.0.2.10\"/>\n" " </instance_attributes>\n" " </primitive>\n" " </resources>\n" " <constraints>\n" " <rsc_location id=\"myAddr-prefer\" rsc=\"myAddr\" node=\"c001n01\" score=\"INFINITY\"/>\n" " </constraints>\n" +" <rsc_defaults>\n" +" <meta_attributes id=\"rsc_defaults-options\">\n" +" <nvpair id=\"rsc-default-1\" name=\"resource-stickiness\" value=\"100\"/>\n" +" <nvpair id=\"rsc-default-2\" name=\"migration-threshold\" value=\"10\"/>\n" +" </meta_attributes>\n" +" </rsc_defaults>\n" +" <op_defaults>\n" +" <meta_attributes id=\"op_defaults-options\">\n" +" <nvpair id=\"op-default-1\" name=\"timeout\" value=\"30s\"/>\n" +" </meta_attributes>\n" +" </op_defaults>\n" " </configuration>\n" " <status/>\n" "</cib>" msgstr "" #. Tag: para #, no-c-format -msgid "In this example, we have one resource (an IP address) that we check every five minutes and will run on host c001n01 until either the resource fails 10 times or the host shuts down." +msgid "In the above example, we have one resource (an IP address) that we check every five minutes and will run on host c001n01 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 "Advanced configuration - groups and clones with stonith" +msgid "An advanced configuration with groups, clones and STONITH" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<cib admin_epoch=\"0\" epoch=\"1\" num_updates=\"0\" have-quorum=\"false\"\n" -" validate-with=\"pacemaker-1.0\">\n" +msgid "<cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\">\n" " <configuration>\n" " <crm_config>\n" -" <nvpair id=\"option-1\" name=\"symmetric-cluster\" value=\"true\"/>\n" -" <nvpair id=\"option-2\" name=\"no-quorum-policy\" value=\"stop\"/>\n" -" <nvpair id=\"option-3\" name=\"stonith-enabled\" value=\"true\"/>\n" +" <cluster_property_set id=\"cib-bootstrap-options\">\n" +" <nvpair id=\"option-1\" name=\"symmetric-cluster\" value=\"true\"/>\n" +" <nvpair id=\"option-2\" name=\"no-quorum-policy\" value=\"stop\"/>\n" +" <nvpair id=\"option-3\" name=\"stonith-enabled\" value=\"true\"/>\n" +" </cluster_property_set>\n" " </crm_config>\n" -" <op_defaults>\n" -" <nvpair id=\"op-default-1\" name=\"timeout\" value=\"30s\"/>\n" -" </op_defaults>\n" -" <rsc_defaults>\n" -" <nvpair id=\"rsc-default-1\" name=\"resource-stickiness\" value=\"100\"/>\n" -" <nvpair id=\"rsc-default-2\" name=\"migration-threshold\" value=\"10\"/>\n" -" </rsc_defaults>\n" " <nodes>\n" " <node id=\"xxx\" uname=\"c001n01\" type=\"normal\"/>\n" " <node id=\"yyy\" uname=\"c001n02\" type=\"normal\"/>\n" " <node id=\"zzz\" uname=\"c001n03\" type=\"normal\"/>\n" " </nodes>\n" " <resources>\n" " <primitive id=\"myAddr\" class=\"ocf\" provider=\"heartbeat\" type=\"IPaddr\">\n" " <operations>\n" " <op id=\"myAddr-monitor\" name=\"monitor\" interval=\"300s\"/>\n" " </operations>\n" -" <instance_attributes>\n" -" <nvpair name=\"ip\" value=\"10.0.200.30\"/>\n" +" <instance_attributes id=\"myAddr-attrs\">\n" +" <nvpair id=\"myAddr-attr-1\" name=\"ip\" value=\"192.0.2.10\"/>\n" " </instance_attributes>\n" " </primitive>\n" " <group id=\"myGroup\">\n" " <primitive id=\"database\" class=\"lsb\" type=\"oracle\">\n" " <operations>\n" " <op id=\"database-monitor\" name=\"monitor\" interval=\"300s\"/>\n" " </operations>\n" " </primitive>\n" " <primitive id=\"webserver\" class=\"lsb\" type=\"apache\">\n" " <operations>\n" " <op id=\"webserver-monitor\" name=\"monitor\" interval=\"300s\"/>\n" " </operations>\n" " </primitive>\n" " </group>\n" " <clone id=\"STONITH\">\n" " <meta_attributes id=\"stonith-options\">\n" " <nvpair id=\"stonith-option-1\" name=\"globally-unique\" value=\"false\"/>\n" " </meta_attributes>\n" " <primitive id=\"stonithclone\" class=\"stonith\" type=\"external/ssh\">\n" " <operations>\n" " <op id=\"stonith-op-mon\" name=\"monitor\" interval=\"5s\"/>\n" " </operations>\n" " <instance_attributes id=\"stonith-attrs\">\n" " <nvpair id=\"stonith-attr-1\" name=\"hostlist\" value=\"c001n01,c001n02\"/>\n" " </instance_attributes>\n" " </primitive>\n" " </clone>\n" " </resources>\n" " <constraints>\n" " <rsc_location id=\"myAddr-prefer\" rsc=\"myAddr\" node=\"c001n01\"\n" " score=\"INFINITY\"/>\n" " <rsc_colocation id=\"group-with-ip\" rsc=\"myGroup\" with-rsc=\"myAddr\"\n" " score=\"INFINITY\"/>\n" " </constraints>\n" +" <op_defaults>\n" +" <meta_attributes id=\"op_defaults-options\">\n" +" <nvpair id=\"op-default-1\" name=\"timeout\" value=\"30s\"/>\n" +" </meta_attributes>\n" +" </op_defaults>\n" +" <rsc_defaults>\n" +" <meta_attributes id=\"rsc_defaults-options\">\n" +" <nvpair id=\"rsc-default-1\" name=\"resource-stickiness\" value=\"100\"/>\n" +" <nvpair id=\"rsc-default-2\" name=\"migration-threshold\" value=\"10\"/>\n" +" </meta_attributes>\n" +" </rsc_defaults>\n" " </configuration>\n" " <status/>\n" "</cib>" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-Upgrade-Config.pot b/doc/Pacemaker_Explained/pot/Ap-Upgrade-Config.pot index 03b7b3dad8..3e979ecf8e 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Upgrade-Config.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Upgrade-Config.pot @@ -1,245 +1,230 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 the Configuration from 0.6" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Preparation" -msgstr "" - -#. Tag: para -#, no-c-format -msgid " Upgrading the Configuration ConfigurationUpgrading Upgrading " +msgid "Upgrading the Configuration" msgstr "" #. Tag: para #, no-c-format -msgid " DownloadDTD DTD DTDDownload Download " +msgid "This process was originally written for the upgrade from 0.6.x to 1.y, but the concepts should apply for any upgrade involving a change in the XML schema version." msgstr "" #. Tag: para #, no-c-format -msgid "Download the latest DTD and ensure your configuration validates." +msgid " Upgrading the Configuration ConfigurationUpgrading Upgrading " msgstr "" #. Tag: title #, no-c-format msgid "Perform the upgrade" msgstr "" #. Tag: title #, no-c-format msgid "Upgrade the software" msgstr "" #. Tag: para #, no-c-format msgid "Refer to the appendix: " msgstr "" #. Tag: title #, no-c-format msgid "Upgrade the Configuration" msgstr "" #. Tag: para #, no-c-format -msgid "As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new 1.0 syntax." +msgid "As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new XML syntax." msgstr "" #. Tag: para #, no-c-format -msgid "In order to support such environments, it is actually possible to continue using the old 0.6 syntax." +msgid "In order to support such environments, it is actually possible to continue using the old XML syntax." msgstr "" #. Tag: para #, no-c-format msgid "The downside is, however, that not all the new features will be available 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 advisable to follow the upgrade procedure to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally)." +msgid "Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure (except for the last step) to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally)." msgstr "" #. Tag: para #, no-c-format msgid "Create a shadow copy to work with" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_shadow --create upgrade06" msgstr "" #. Tag: para #, no-c-format msgid "Verify the configuration is valid ConfigurationVerify Verify VerifyConfiguration Configuration " msgstr "" -#. Tag: programlisting +#. 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: programlisting +#. 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 - go back to step 2" msgstr "" #. Tag: para #, no-c-format msgid "The transformation failed - report a bug or email the project" msgstr "" #. Tag: para #, no-c-format msgid "The transformation was successful but produced an invalid result The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation. " 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 http://clusterlabs.org/wiki/Validation_FAQ and/or try the procedure described below under " +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 Validation FAQ wiki page and/or try the procedure described below under " msgstr "" #. Tag: para #, no-c-format msgid "Check the changes" msgstr "" -#. Tag: programlisting +#. 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. Since the shadow configuration is not in use by the cluster, it is safe to edit the file manually:" msgstr "" -#. Tag: programlisting +#. 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 $EDITOR environment variable)" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Preview how the cluster will react" +msgid "This will open the configuration in your favorite editor (whichever is specified by the standard $EDITOR environment variable)" msgstr "" #. Tag: para #, no-c-format -msgid "Test what the cluster will do when you upload the new configuration" +msgid "Preview how the cluster will react:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_simulate --live-check --save-dotfile upgrade06.dot -S\n" "# graphviz upgrade06.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 for further details on how to interpret the output of crm_simulate" +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 for further details on how to interpret the output of crm_simulate and graphviz." msgstr "" #. Tag: para #, no-c-format msgid "Upload the changes" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_shadow --commit upgrade06 --force" msgstr "" #. Tag: para #, no-c-format -msgid "If this step fails, something really strange has occurred. You should report a bug." +msgid "In the unlikely event this step fails, please report a bug." msgstr "" #. Tag: title #, no-c-format msgid "Manually Upgrading the Configuration" msgstr "" #. Tag: para #, no-c-format -msgid " ConfigurationUpgrade manually Upgrade manually It is also possible to perform the configuration upgrade steps manually. To do this" +msgid " ConfigurationUpgrade manually Upgrade manually It is also possible to perform the configuration upgrade steps manually:" msgstr "" #. Tag: para #, no-c-format -msgid "Locate the upgrade06.xsl conversion script or download the latest version from Git" +msgid "Locate the upgrade06.xsl conversion script provided with the source code (the latest version is available via git)." msgstr "" #. Tag: para #, no-c-format msgid "Convert the XML blob: XMLConvert Convert " msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# xsltproc /path/to/upgrade06.xsl config06.xml > config10.xml" msgstr "" #. Tag: para #, no-c-format -msgid "Locate the pacemaker.rng script." +msgid "Locate the pacemaker.rng script." msgstr "" #. Tag: para #, no-c-format msgid "Check the XML validity: Validate Configuration ConfigurationValidate XML Validate XML " msgstr "" -#. Tag: programlisting +#. 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 should be more informative (despite being generated by the same library!) since they include line numbers." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-Upgrade.pot b/doc/Pacemaker_Explained/pot/Ap-Upgrade.pot index 449d249285..e9f15efe06 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Upgrade.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Upgrade.pot @@ -1,379 +1,329 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 Cluster Software" msgstr "" -#. Tag: title -#, no-c-format -msgid "Version Compatibility" -msgstr "" - #. Tag: para #, no-c-format -msgid "When releasing newer versions we take care to make sure we are backwards compatible with older versions. While you will always be able to upgrade from version x to x+1, in order to continue to produce high quality software it may occasionally be necessary to drop compatibility with older versions." +msgid "There will always be an upgrade path from any pacemaker 1.x release to any other 1.y release." msgstr "" #. Tag: para #, no-c-format -msgid "There will always be an upgrade path from any series-2 release to any other series-2 release." +msgid "Consult the documentation for your messaging layer (Heartbeat or Corosync) to see whether upgrading them to a newer version is also supported." msgstr "" #. Tag: para #, no-c-format msgid "There are three approaches to upgrading your cluster software:" msgstr "" #. Tag: para #, no-c-format msgid "Complete Cluster Shutdown" msgstr "" #. Tag: para #, no-c-format msgid "Rolling (node by node)" msgstr "" #. Tag: para #, no-c-format msgid "Disconnect and Reattach" msgstr "" #. Tag: para #, no-c-format -msgid "Each method has advantages and disadvantages, some of which are listed in the table below, and you should chose the one most appropriate to your needs." +msgid "Each method has advantages and disadvantages, some of which are listed in the table below, and you should choose the one most appropriate to your needs." msgstr "" #. Tag: title #, no-c-format -msgid "Summary of Upgrade Methodologies" +msgid "Upgrade Methods" msgstr "" #. Tag: entry #, no-c-format msgid "Type" msgstr "" #. Tag: entry #, no-c-format msgid "Available between all software versions" 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/Configuration" msgstr "" #. Tag: entry #, no-c-format -msgid "Allows change of cluster stack type ClusterSwitching between Stacks Switching between Stacks Changing Cluster Stack For example, switching from Heartbeat to Corosync. Consult the Heartbeat or Corosync documentation to see if upgrading them to a newer version is also supported. " +msgid "Allows change of cluster stack type ClusterSwitching between Stacks Switching between Stacks Changing Cluster Stack For example, switching from Heartbeat to Corosync." msgstr "" #. Tag: para #, no-c-format msgid "Shutdown UpgradeShutdown Shutdown Shutdown Upgrade " 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 "Rolling UpgradeRolling Rolling Rolling Upgrade " msgstr "" #. Tag: para #, no-c-format msgid "Reattach UpgradeReattach Reattach Reattach Upgrade " msgstr "" #. Tag: para #, no-c-format msgid "only due to failure" msgstr "" #. Tag: para #, no-c-format -msgid "In this scenario one shuts down all cluster nodes and resources and upgrades all the nodes before restarting the cluster." +msgid "In this scenario, one shuts down all cluster nodes and resources, then upgrades all the nodes before restarting the cluster." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Procedure" +msgid "On each node:" msgstr "" #. Tag: para #, no-c-format -msgid "On each node:" +msgid "Shutdown the cluster software (pacemaker and the messaging layer)." msgstr "" #. Tag: para #, no-c-format -msgid "Shutdown the cluster stack (Heartbeat or Corosync)" +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 "Upgrade the Pacemaker software. This may also include upgrading the cluster stack and/or the underlying operating system." +msgid "Check the configuration manually or with the crm_verify tool if available." msgstr "" #. Tag: para #, no-c-format -msgid "Check the configuration manually or with the crm_verify tool if available." +msgid "Start the cluster software. The messaging layer can be either Corosync or Heartbeat and does not need to be the same one before the upgrade." msgstr "" #. Tag: para #, no-c-format -msgid "Start the cluster stack. This can be either Corosync or Heartbeat and does not need to be the same as the previous cluster stack." +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 "In this scenario each node is removed from the cluster, upgraded and then brought back online until all nodes are running the newest version." +msgid "Rolling upgrades should always be possible for pacemaker versions 1.0.0 and later." msgstr "" #. Tag: para #, no-c-format -msgid "This method is currently broken between Pacemaker 0.6.x and 1.0.x." +msgid "Put the node into standby mode, and wait for any active resources to be moved cleanly to another node." msgstr "" #. Tag: para #, no-c-format -msgid "Measures have been put into place to ensure rolling upgrades always work for versions after 1.0.0. Please try one of the other upgrade strategies. Detach/Reattach is a particularly good option for most people." +msgid "Shutdown the cluster software (pacemaker and the messaging layer) on the node." msgstr "" #. Tag: para #, no-c-format -msgid "On each node: . Shutdown the cluster stack (Heartbeat or Corosync) . Upgrade the Pacemaker software. This may also include upgrading the cluster stack and/or the underlying operating system. .. On the first node, check the configuration manually or with the crm_verify tool if available. .. Start the cluster stack." +msgid "If this is the first node to be upgraded, check the configuration manually or with the crm_verify tool if available." msgstr "" #. Tag: para #, no-c-format -msgid "+ This must be the same type of cluster stack (Corosync or Heartbeat) that the rest of the cluster is using. Upgrading Corosync/Heartbeat may also be possible, please consult the documentation for those projects to see if the two versions will be compatible." +msgid "Start the messaging layer. This must be the same messaging layer (Corosync or Heartbeat) that the rest of the cluster is using. Upgrading the messaging layer may also be possible; consult the documentation for those projects to see whether the two versions will be compatible." msgstr "" #. Tag: para #, no-c-format -msgid "+ .. Repeat for each node in the cluster." +msgid "Rolling upgrades were not always possible with older heartbeat and pacemaker versions. The table below shows which versions were compatible during rolling upgrades. Rolling upgrades that cross compatibility boundaries must be performed in multiple steps (for example, upgrading heartbeat 2.0.6 to heartbeat 2.1.3, and then upgrading again to pacemaker 0.6.6). Rolling upgrades from pacemaker 0.x to 1.y are not possible." 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 1.0.x" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker 1.0.0" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker 0.7.x" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker 0.6 or Heartbeat 2.1.3" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker 0.6.x" msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat 2.0.8" msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat 2.1.3 (or less)" msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat 2.0.4" msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat 2.0.4 (or less)" msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat 2.0.0" msgstr "" #. Tag: para #, no-c-format msgid "None. Use an alternate upgrade strategy." msgstr "" -#. Tag: title -#, no-c-format -msgid "Crossing Compatibility Boundaries" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Rolling upgrades that cross compatibility boundaries must be preformed in multiple steps. For example, to perform a rolling update from Heartbeat 2.0.1 to Pacemaker 0.6.6 one must:" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Perform a rolling upgrade from Heartbeat 2.0.1 to Heartbeat 2.0.4" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Perform a rolling upgrade from Heartbeat 2.0.4 to Heartbeat 2.1.3" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Perform a rolling upgrade from Heartbeat 2.1.3 to Pacemaker 0.6.6" -msgstr "" - #. Tag: para #, no-c-format -msgid "A variant of a complete cluster shutdown, but the resources are left active and get re-detected when the cluster is restarted." +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 "Tell the cluster to stop managing services." +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: para -#, no-c-format -msgid "This is required to allow the services to remain active after the cluster shuts down." -msgstr "" - -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_attribute -t crm_config -n is-managed-default -v false" msgstr "" #. Tag: para #, no-c-format -msgid "For any resource that has a value for is-managed, make sure it is set to false (so that the cluster will not stop it)" +msgid "For any resource that has a value for is-managed, make sure it is set to false so that the cluster will not stop it (replacing $rsc_id appropriately):" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_resource -t primitive -r $rsc_id -p is-managed -v false" msgstr "" #. Tag: para #, no-c-format -msgid "Upgrade the cluster stack program - This may also include upgrading the underlying operating system." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Start the cluster stack." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "This can be either Corosync or Heartbeat and does not need to be the same as the previous cluster stack." +msgid "Start the cluster software. The messaging layer can be either Corosync or Heartbeat and does not need to be the same one as 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: programlisting +#. Tag: screen #, no-c-format msgid "# crm_attribute -t crm_config -n is-managed-default -v true" msgstr "" #. Tag: para #, no-c-format -msgid "For any resource that has a value for is-managed reset it to true (so the cluster can recover the service if it fails) if desired:" +msgid "For any resource that has a value for is-managed, reset it to true (so the cluster can recover the service if it fails) if desired:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_resource -t primitive -r $rsc_id -p is-managed -v true" msgstr "" -#. Tag: title -#, no-c-format -msgid "Notes" -msgstr "" - #. Tag: para #, no-c-format -msgid "Always check your existing configuration is still compatible with the version you are installing before starting the cluster." +msgid "The oldest version of the CRM to support this upgrade type was in Heartbeat 2.0.4." msgstr "" #. Tag: para #, no-c-format -msgid "The oldest version of the CRM to support this upgrade type was in Heartbeat 2.0.4" +msgid "Always check your existing configuration is still compatible with the version you are installing before starting the cluster." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Author_Group.pot b/doc/Pacemaker_Explained/pot/Author_Group.pot index 9ef7225c64..ae3aa135e6 100644 --- a/doc/Pacemaker_Explained/pot/Author_Group.pot +++ b/doc/Pacemaker_Explained/pot/Author_Group.pot @@ -1,139 +1,139 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 a03fcdcded..3ad9435c46 100644 --- a/doc/Pacemaker_Explained/pot/Book_Info.pot +++ b/doc/Pacemaker_Explained/pot/Book_Info.pot @@ -1,44 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 the CIB." -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 I hope, however, that the concepts explained here make the functionality of these tools more easily understood. , precisely because they hide the XML." -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. Although such guides exist, 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. Try the Clusters from Scratch document instead." +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 80ecc8a136..5975f6b785 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot @@ -1,877 +1,948 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 " ClusterRemote connection Remote connection ClusterRemote administration Remote administration " 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 "CIB_user" msgstr "" #. Tag: para #, no-c-format -msgid "The user to connect as. Needs to be part of the hacluster group on the target host. Defaults to $USER. Environment VariableCIB_user CIB_user " +msgid "$USER" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The user to connect as. Needs to be part of the hacluster group on the target host. Environment VariableCIB_user CIB_user " msgstr "" #. Tag: para #, no-c-format msgid "CIB_passwd" msgstr "" #. Tag: para #, no-c-format msgid "The user’s password. Read from the command line if unset. Environment VariableCIB_passwd CIB_passwd " msgstr "" #. Tag: para #, no-c-format msgid "CIB_server" msgstr "" #. Tag: para #, no-c-format -msgid "The host to contact. Defaults to localhost. Environment VariableCIB_server CIB_server " +msgid "localhost" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The host to contact Environment VariableCIB_server CIB_server " msgstr "" #. Tag: para #, no-c-format msgid "CIB_port" msgstr "" #. Tag: para #, no-c-format msgid "The port on which to contact the server; required. Environment VariableCIB_port CIB_port " msgstr "" #. Tag: para #, no-c-format msgid "CIB_encrypted" msgstr "" #. Tag: para #, no-c-format -msgid "Encrypt network traffic; defaults to true. Environment VariableCIB_encrypted CIB_encrypted " +msgid "TRUE" msgstr "" #. Tag: para #, no-c-format -msgid "So, if c001n01 is an active cluster node and is listening on 1234 for connections, and someguy is a member of the hacluster group, then the following would prompt for someguy's password and return the cluster’s current configuration:" +msgid "Whether to encrypt network traffic Environment VariableCIB_encrypted CIB_encrypted " msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someguy;\n" +msgid "So, if c001n01 is an active cluster node and is listening on port 1234 for connections, and someuser is a member of the hacluster group, then the following would prompt for someuser'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 remote-tls-port (encrypted) or remote-clear-port (unencrypted) top-level options (ie., those kept in the cib tag, like num_updates and epoch)." +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 remote-tls-port (encrypted) or remote-clear-port (unencrypted) CIB properties (i.e., those kept in the cib tag, like num_updates and epoch)." msgstr "" #. Tag: title #, no-c-format -msgid "Extra top-level CIB options for remote access" +msgid "Extra top-level CIB properties for remote access" msgstr "" #. Tag: entry #, no-c-format msgid "Field" msgstr "" #. Tag: para #, no-c-format msgid "remote-tls-port" msgstr "" #. Tag: para #, no-c-format -msgid "Listen for encrypted remote connections on this port. Default: none remote-tls-portRemote Connection Option Remote Connection Option Remote ConnectionOptionremote-tls-port Optionremote-tls-port remote-tls-port " +msgid "none" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Listen for encrypted remote connections on this port. remote-tls-portRemote Connection Option Remote Connection Option Remote ConnectionOptionremote-tls-port Optionremote-tls-port remote-tls-port " msgstr "" #. Tag: para #, no-c-format msgid "remote-clear-port" msgstr "" #. Tag: para #, no-c-format -msgid "Listen for plaintext remote connections on this port. Default: none remote-clear-portRemote Connection Option Remote Connection Option Remote ConnectionOptionremote-clear-port Optionremote-clear-port remote-clear-port " +msgid "Listen for plaintext remote connections on this port. remote-clear-portRemote Connection Option Remote Connection Option Remote ConnectionOptionremote-clear-port Optionremote-clear-port remote-clear-port " 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 at in the middle of the business day - hardly desirable." +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/time that the operation should be relative to, set the operation’s interval-origin. The cluster uses this point to calculate the correct start-delay such that the operation will occur at origin + (interval * N)." +msgid "To specify a date and time that the operation should be relative to, set the operation’s interval-origin. The cluster uses this point to calculate the correct start-delay such that the operation will occur at origin + (interval * N)." msgstr "" #. Tag: para #, no-c-format -msgid "So, if the operation’s interval is 24h, it’s 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 of course cancelled." +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 interval and interval-origin can be any date/time conforming to the ISO8601 standard. 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:" +msgid "The value specified for interval and interval-origin can be any date/time conforming to the ISO8601 standard. 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 "<op id=\"my-weekly-action\" name=\"custom-action\" interval=\"P7D\" interval-origin=\"2009-W01-1\"/>" msgstr "" #. Tag: title #, no-c-format msgid "Moving Resources" msgstr "" #. Tag: para #, no-c-format msgid " MovingResources Resources ResourceMoving Moving " msgstr "" #. Tag: title #, no-c-format -msgid "Manual Intervention" +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 it’s current location: when the whole node is under maintenance, and when a single resource needs to be moved." +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 the configuration can seem convoluted at times, not even we would require this of administrators." +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 crm_standby. To check the standby status of the current machine, simply run:" +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 crm_standby. To check the standby status of the current machine, run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_standby --get-value" +msgid "# crm_standby -G" msgstr "" #. Tag: para #, no-c-format -msgid "A value of true indicates that the node is NOT able to host any resources, while a value of false says that it CAN." +msgid "A value of on indicates that the node is not able to host any resources, while a value of off says that it can." msgstr "" #. Tag: para #, no-c-format -msgid "You can also check the status of other nodes in the cluster by specifying the --node-uname option:" +msgid "You can also check the status of other nodes in the cluster by specifying the --node option:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_standby --get-value --node-uname sles-2" +msgid "# crm_standby -G --node sles-2" msgstr "" #. Tag: para #, no-c-format -msgid "To change the current node’s standby status, use --attr-value instead of --get-value." +msgid "To change the current node’s standby status, use -v instead of -G:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_standby --attr-value" +msgid "# crm_standby -v on" msgstr "" #. Tag: para #, no-c-format -msgid "Again, you can change another host’s value by supplying a host name with --node-uname." +msgid "Again, you can change another host’s value by supplying a hostname with --node." +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 do this by creating location constraints. However, once again we provide a user friendly shortcut as part of the crm_resource command, which creates and modifies the extra constraints for you. If Email was running on sles-1 and you wanted it moved to a specific location, the command would look something like:" +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 crm_resource command, which creates and modifies the extra constraints for you. If Email were running on sles-1 and you wanted it moved to a specific location, the command would look something like:" msgstr "" -#. Tag: programlisting +#. 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 "<rsc_location rsc=\"Email\" node=\"sles-2\" score=\"INFINITY\"/>" msgstr "" #. Tag: para #, no-c-format msgid "It is important to note that subsequent invocations of crm_resource -M are not cumulative. So, if you ran these commands" msgstr "" -#. Tag: programlisting +#. 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: programlisting +#. Tag: screen #, no-c-format msgid "# crm_resource -U -r Email" msgstr "" #. Tag: para #, no-c-format msgid "Note the use of the word allow. The resource can move back to its original location but, depending on resource-stickiness, it might stay where it is. To be absolutely certain that it moves back to sles-1, move it there before issuing the call to crm_resource -U:" msgstr "" -#. Tag: programlisting +#. 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" +msgid "Alternatively, if you only care that the resource should be moved from its current location, try:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_resource -M -r Email`" +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 "<rsc_location rsc=\"Email\" node=\"sles-1\" score=\"-INFINITY\"/>" 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 -INFINITY constraint will prevent the resource from running on that node until crm_resource -U 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 resource-stickiness is set to INFINITY, it is possible that you will end up with the problem described in . The tool can detect some of these cases and deals with them by also creating both a positive and negative constraint. Eg." +msgid "In some cases, such as when resource-stickiness is set to INFINITY, it is possible that you will end up with the problem described in . 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 "Email prefers sles-1 with a score of -INFINITY" msgstr "" #. Tag: para #, no-c-format msgid "Email prefers sles-2 with a score of INFINITY" 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 Failure" msgstr "" #. Tag: para #, no-c-format -msgid "New in 1.0 is the concept of a migration threshold. The naming of this option was perhaps unfortunate as it is easily confused with true 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. " +msgid "Normally, if a running resource fails, pacemaker will try to start it again on the same node. 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." msgstr "" #. Tag: para #, no-c-format -msgid "Simply define migration-threshold=N for a resource and it will migrate to a new node after N failures. There is no threshold defined by default. To determine the resource’s current failure status and limits, use crm_mon --failcounts." +msgid " migration-threshold failure-timeout start-failure-is-fatal " msgstr "" #. Tag: para #, no-c-format -msgid "By default, once the threshold has been reached, this node will no longer be allowed to run the failed resource until the administrator manually resets the resource’s failcount using crm_failcount (after hopefully first fixing the failure’s cause). However it is possible to expire them by setting the resource’s failure-timeout option." +msgid "Pacemaker allows you to set your preference via the migration-threshold resource option. 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. " msgstr "" #. Tag: para #, no-c-format -msgid "So a setting of migration-threshold=2 and failure-timeout=60s would cause the resource to move to a new node after 2 failures, and allow it to move back (depending on the stickiness and constraint scores) after one minute." +msgid "Simply define migration-threshold=N for a resource and it will migrate to a new node after N failures. There is no threshold defined by default. To determine the resource’s current failure status and limits, run crm_mon --failcounts." msgstr "" #. Tag: para #, no-c-format -msgid "There are two exceptions to the migration threshold concept; they occur when a resource either fails to start or fails to stop. Start failures cause the failcount to be set to INFINITY and thus always cause the resource to move immediately." +msgid "By default, once the threshold has been reached, the troublesome node will no longer be allowed to run the failed resource until the administrator manually resets the resource’s failcount using crm_failcount (after hopefully first fixing the failure’s cause). Alternatively, it is possible to expire them by setting the failure-timeout option for the resource." 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." +msgid "For example, a setting of migration-threshold=2 and failure-timeout=60s 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 "Please read before enabling this option." +msgid "There are two exceptions to the migration threshold concept: when a resource either fails to start or fails to stop." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Moving Resources Due to Connectivity Changes" +msgid "If the cluster property start-failure-is-fatal is set to true (which is the default), start failures cause the failcount to be set to INFINITY 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 "Setting up the cluster to move resources when external connectivity is lost is a two-step process." +msgid "Please read to understand how timeouts work before configuring a failure-timeout." msgstr "" #. Tag: title #, no-c-format -msgid "Tell Pacemaker to monitor connectivity" +msgid "Moving Resources Due to Connectivity Changes" msgstr "" #. Tag: para #, no-c-format -msgid "To do this, you need to add a ping resource to the cluster. The ping resource uses the system utility of the same name to a test if list of machines (specified by DNS hostname or IPv4/IPv6 address) are reachable and uses the results to maintain a node attribute normally called pingd. The attribute name is customizable; that allows multiple ping groups to be defined. " +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 "Older versions of Heartbeat required users to add ping nodes to ha.cf - this is no longer required." +msgid "First, add an ocf:pacemaker:ping resource to the cluster. The ping 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 pingd by default. The attribute name is customizable, in order to allow multiple ping groups to be defined. " msgstr "" #. Tag: para #, no-c-format -msgid "Older versions of Pacemaker used a custom binary called pingd for this functionality; this is now deprecated in favor of ping." +msgid "Older versions of Heartbeat required users to add ping nodes to ha.cf, but this is no longer required." msgstr "" #. Tag: para #, no-c-format -msgid "If your version of Pacemaker does not contain the ping agent, you can download the latest version from https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping" +msgid "Older versions of Pacemaker used a different agent ocf:pacemaker:pingd which is now deprecated in favor of ping. If your version of Pacemaker does not contain the ping resource agent, download the latest version from https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping" msgstr "" #. Tag: para #, no-c-format -msgid "Normally the resource will 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." +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 ping Resource" msgstr "" #. Tag: para #, no-c-format msgid "dampen" 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. dampenPing Resource Option Ping Resource Option Ping ResourceOptiondampen Optiondampen dampen " msgstr "" #. Tag: para #, no-c-format msgid "multiplier" 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. multiplierPing Resource Option Ping Resource Option Ping ResourceOptionmultiplier Optionmultiplier multiplier " msgstr "" #. Tag: para #, no-c-format msgid "host_list" 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. host_listPing Resource Option Ping Resource Option Ping ResourceOptionhost_list Optionhost_list host_list " 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 "<clone id=\"Connected\">\n" " <primitive id=\"ping\" provider=\"pacemaker\" class=\"ocf\" type=\"ping\">\n" " <instance_attributes id=\"ping-attrs\">\n" " <nvpair id=\"pingd-dampen\" name=\"dampen\" value=\"5s\"/>\n" " <nvpair id=\"pingd-multiplier\" name=\"multiplier\" value=\"1000\"/>\n" " <nvpair id=\"pingd-hosts\" name=\"host_list\" value=\"my.gateway.com www.bigcorp.com\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"ping-monitor-60s\" interval=\"60s\" name=\"monitor\"/>\n" " </operations>\n" " </primitive>\n" "</clone>" 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 ocf:pacemaker:ping is recording." msgstr "" #. Tag: title #, no-c-format -msgid "Tell Pacemaker how to interpret the connectivity data" +msgid "Tell Pacemaker How to Interpret the Connectivity Data" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Before attempting the following, make sure you understand ." msgstr "" #. Tag: para #, no-c-format -msgid "Before reading the following, please make sure you have read and understood above." +msgid "There are a number of ways to use the connectivity data." msgstr "" #. Tag: para #, no-c-format -msgid "There are a number of ways to use the connectivity data provided by Heartbeat. The most common setup is for people to have a single ping node, to prevent the cluster from running a resource on any unconnected node." +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 on unconnected nodes" +msgid "Don’t run a resource on unconnected nodes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_location id=\"WebServer-no-connectivity\" rsc=\"Webserver\">\n" " <rule id=\"ping-exclude-rule\" score=\"-INFINITY\" >\n" " <expression id=\"ping-exclude\" attribute=\"pingd\" operation=\"not_defined\"/>\n" " </rule>\n" "</rsc_location>" msgstr "" #. Tag: para #, no-c-format -msgid "A more complex setup is to have a number of ping nodes configured. You can require the cluster to only run resources on nodes that can connect to all (or a minimum subset) of them." +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 nodes; this assumes multiplier is set to 1000:" +msgid "Run only on nodes connected to three or more ping targets." msgstr "" #. Tag: programlisting #, no-c-format -msgid "<rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\">\n" +msgid "<primitive id=\"ping\" provider=\"pacemaker\" class=\"ocf\" type=\"ping\">\n" +"... <!-- omitting some configuration to highlight important parts -->\n" +" <nvpair id=\"pingd-multiplier\" name=\"multiplier\" value=\"1000\"/>\n" +"...\n" +"</primitive>\n" +"...\n" +"<rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\">\n" " <rule id=\"ping-prefer-rule\" score=\"-INFINITY\" >\n" -" <expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/>\n" +" <expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/>\n" " </rule>\n" "</rsc_location>" msgstr "" #. Tag: para #, no-c-format -msgid "Instead you can tell the cluster only to prefer nodes with the best connectivity. Just be sure to set multiplier to a value higher than that of resource-stickiness (and don’t set either of them to INFINITY)." +msgid "Alternatively, you can tell the cluster only to prefer nodes with the best connectivity. Just be sure to set multiplier to a value higher than that of resource-stickiness (and don’t set either of them to INFINITY)." msgstr "" #. Tag: title #, no-c-format msgid "Prefer the node with the most connected ping nodes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\">\n" " <rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" >\n" " <expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/>\n" " </rule>\n" "</rsc_location>" 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 sles-1 is connected to all 5 ping nodes but sles-2 is only connected to 2, then it would be as if you instead had the following constraints in your configuration:" +msgid "It is perhaps easier to think of this in terms of the simple constraints that the cluster translates it into. For example, if sles-1 is connected to all five ping nodes but sles-2 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 pingd constraint" +msgid "How the cluster translates the above location constraint" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_location id=\"ping-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"5000\"/>\n" "<rsc_location id=\"ping-2\" rsc=\"Webserver\" node=\"sles-2\" score=\"2000\"/>" 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 multiplier 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 "<rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\">\n" " <rule id=\"ping-exclude-rule\" score=\"-INFINITY\" >\n" " <expression id=\"ping-exclude\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/>\n" " </rule>\n" " <rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" >\n" " <expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/>\n" " </rule>\n" "</rsc_location>" msgstr "" #. Tag: title #, no-c-format -msgid "Resource Migration" +msgid "Migrating Resources" msgstr "" #. Tag: para #, no-c-format -msgid "Some resources, such as Xen virtual guests, are able to move to another location without loss of state. We call this resource migration; this is different from the normal practice of stopping the resource on the first machine and starting it elsewhere." +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 "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:" +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 "the resource must be active and healthy at the old location" +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 "everything required for the resource to run must be available on both the old and new locations" +msgid "The resource must be active and healthy at the old location; and" msgstr "" #. Tag: para #, no-c-format -msgid "The cluster is able to accommodate both push and pull migration models by requiring the resource agent to support two new actions: migrate_to (performed on the current location) and migrate_from (performed on the destination)." +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 push and pull migration models by requiring the resource agent to support two special actions: migrate_to (performed on the current location) and migrate_from (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 migrate_to action and, if anything, the activation would occur during migrate_from." msgstr "" #. Tag: para #, no-c-format msgid "Conversely for pull, the migrate_to action is practically empty and migrate_from 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 to implement migration for your service, as long as it works." +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 must not, directly or indirectly, depend on any primitive or group resources." +msgid "The resource agent must support migrate_to and migrate_from actions, and advertise them in its metadata." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The resource must have the allow-migrate meta-attribute set to true (which is not the default)." msgstr "" #. Tag: para #, no-c-format -msgid "The resource must support two new actions: migrate_to and migrate_from, and advertise them in its metadata." +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 "The resource must have the allow-migrate meta-attribute set to true (which is not the default)." +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." +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 any primitive or group resources." msgstr "" #. Tag: para #, no-c-format -msgid "If the resource depends on a clone, and at the time the resource needs to be move, the clone has instances that are stopping and instances that are starting, then the resource will be moved in the traditional manner. The Policy Engine is not yet able to model this situation correctly and so takes the safe (yet less optimal) path." +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." 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 id-ref 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 "<rsc_location id=\"WebDB-connectivity\" rsc=\"WebDB\">\n" " <rule id-ref=\"ping-prefer-rule\"/>\n" "</rsc_location>" msgstr "" #. Tag: para #, no-c-format msgid "The cluster will insist that the rule exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a rule that is referenced elsewhere." msgstr "" #. Tag: para #, no-c-format msgid "The same principle applies for meta_attributes and instance_attributes 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 "<primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\">\n" " <instance_attributes id=\"mySpecialRsc-attrs\" score=\"1\" >\n" " <nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/>\n" " <nvpair id=\"default-port\" name=\"port\" value=\"9999\"/>\n" " </instance_attributes>\n" " <meta_attributes id=\"mySpecialRsc-options\">\n" " <nvpair id=\"failure-timeout\" name=\"failure-timeout\" value=\"5m\"/>\n" " <nvpair id=\"migration-threshold\" name=\"migration-threshold\" value=\"1\"/>\n" " <nvpair id=\"stickiness\" name=\"resource-stickiness\" value=\"0\"/>\n" " </meta_attributes>\n" " <operations id=\"health-checks\">\n" " <op id=\"health-check\" name=\"monitor\" interval=\"60s\"/>\n" " <op id=\"health-check\" name=\"monitor\" interval=\"30min\"/>\n" " </operations>\n" "</primitive>\n" "<primitive id=\"myOtherlRsc\" class=\"ocf\" type=\"Other\" provider=\"me\">\n" " <instance_attributes id-ref=\"mySpecialRsc-attrs\"/>\n" " <meta_attributes id-ref=\"mySpecialRsc-options\"/>\n" " <operations id-ref=\"health-checks\"/>\n" "</primitive>" 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. However, 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." +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, your resource agent must:" +msgid "To take advantage of this capability, the resource agent must:" msgstr "" #. Tag: para #, no-c-format -msgid "Accept the reload operation and perform any required actions. The steps required here depend completely on your application!" +msgid "Accept the reload operation and perform any required actions. The actions here depend completely on your application!" msgstr "" #. Tag: title #, no-c-format -msgid "The DRBD Agent’s Control logic for Supporting the reload Operation" +msgid "The DRBD agent’s logic for supporting reload" 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 reload operation in the actions section of its metadata" msgstr "" #. Tag: title #, no-c-format msgid "The DRBD Agent Advertising Support for the reload Operation" msgstr "" #. Tag: programlisting #, no-c-format msgid "<?xml version=\"1.0\"?>\n" " <!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\">\n" " <resource-agent name=\"drbd\">\n" " <version>1.1</version>\n" "\n" " <longdesc>\n" " Master/Slave OCF Resource Agent for DRBD\n" " </longdesc>\n" "\n" " ...\n" "\n" " <actions>\n" " <action name=\"start\" timeout=\"240\" />\n" " <action name=\"reload\" timeout=\"240\" />\n" " <action name=\"promote\" timeout=\"90\" />\n" " <action name=\"demote\" timeout=\"90\" />\n" " <action name=\"notify\" timeout=\"90\" />\n" " <action name=\"stop\" timeout=\"100\" />\n" " <action name=\"meta-data\" timeout=\"5\" />\n" " <action name=\"validate-all\" timeout=\"30\" />\n" " </actions>\n" " </resource-agent>" msgstr "" #. Tag: para #, no-c-format msgid "Advertise one or more parameters that can take effect using reload." msgstr "" #. Tag: para #, no-c-format msgid "Any parameter with the unique 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 "<parameter name=\"drbdconf\" unique=\"0\">\n" " <longdesc>Full path to the drbd.conf file.</longdesc>\n" " <shortdesc>Path to drbd.conf</shortdesc>\n" " <content type=\"string\" default=\"${OCF_RESKEY_drbdconf_default}\"/>\n" "</parameter>" 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 fields changes." +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 "The metadata is re-read when the resource is started. This may mean that the resource will be restarted the first time, even though you changed a parameter with unique=0" +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 unique=0." 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 869339f6b3..5af5a9f04d 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot @@ -1,1288 +1,1425 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:01\n" -"PO-Revision-Date: 2012-10-17T05:19:01\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 " Group Resources ResourcesGroups Groups " 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." +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 "An example group" +msgid "A group of two primitive resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<group id=\"shortcut\">\n" " <primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" " <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" " </primitive>\n" " <primitive id=\"Email\" class=\"lsb\" type=\"exim\"/>\n" -" </group>" +"</group>" 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 (Public-IP first, then Email)" msgstr "" #. Tag: para #, no-c-format msgid "Resources are stopped in the reverse order to which they appear in (Email first, then Public-IP)" 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 Public-IP can’t run anywhere, neither can Email;" msgstr "" #. Tag: para #, no-c-format msgid "but if Email can’t run anywhere, this does not affect Public-IP 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 "<configuration>\n" " <resources>\n" " <primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" " <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" " </primitive>\n" " <primitive id=\"Email\" class=\"lsb\" type=\"exim\"/>\n" " </resources>\n" " <constraints>\n" " <rsc_colocation id=\"xxx\" rsc=\"Email\" with-rsc=\"Public-IP\" score=\"INFINITY\"/>\n" " <rsc_order id=\"yyy\" first=\"Public-IP\" then=\"Email\"/>\n" " </constraints>\n" "</configuration>" 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 "id" msgstr "" #. Tag: para #, no-c-format -msgid "Your name for the group idGroup Resource Property Group Resource Property ResourceGroup Propertyid Group Propertyid id " +msgid "A unique name for the group idGroup Resource Property Group Resource Property ResourceGroup Propertyid Group Propertyid id " msgstr "" #. Tag: title #, no-c-format msgid "Group Options" msgstr "" #. Tag: para #, no-c-format -msgid "Options inherited from primitive resources: priority, target-role, is-managed" +msgid "Groups inherit the priority, target-role, and is-managed properties from primitive resources. See 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 here will be inherited by the group’s children." +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. To refer to the child of a group resource, just use the child’s id instead of the group’s." +msgid "Groups may only contain a collection of cluster resources (see ). To refer to a child of a group resource, just use the child’s id 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 the group’s children in constraints, it is usually preferable to use the group’s name instead." +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 "Example constraints involving groups" +msgid "Some constraints involving groups" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_location id=\"group-prefers-node1\" rsc=\"shortcut\" node=\"node1\" score=\"500\"/>\n" " <rsc_colocation id=\"webserver-with-group\" rsc=\"Webserver\" with-rsc=\"shortcut\"/>\n" " <rsc_order id=\"start-group-then-webserver\" first=\"Webserver\" then=\"shortcut\"/>\n" "</constraints>" msgstr "" #. Tag: title #, no-c-format msgid "Group Stickiness" msgstr "" #. Tag: para #, no-c-format msgid " resource-stickinessGroups Groups " 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 resource-stickiness 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" msgstr "" #. Tag: para #, no-c-format msgid " Clone Resources ResourcesClones Clones " msgstr "" #. Tag: para #, no-c-format -msgid "Clones were initially conceived as a convenient way to start N instances of an IP 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 Red Hat’s DLM, the fencing subsystem, and OCFS2." +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." msgstr "" #. Tag: para #, no-c-format msgid "You can clone any resource, provided the resource agent supports it." msgstr "" #. Tag: para #, no-c-format msgid "Three types of cloned resources exist:" msgstr "" #. Tag: para #, no-c-format msgid "Anonymous" msgstr "" #. Tag: para #, no-c-format -msgid "Globally Unique" +msgid "Globally unique" msgstr "" #. Tag: para #, no-c-format msgid "Stateful" msgstr "" #. Tag: para #, no-c-format -msgid "Anonymous clones are the simplest type. These resources behave completely identically everywhere they are running. Because of this, there can only be one copy of an anonymous clone active per machine." +msgid "Anonymous 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." msgstr "" #. Tag: para #, no-c-format -msgid "Globally unique 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 "Globally unique 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." msgstr "" #. Tag: para #, no-c-format -msgid "Stateful clones are covered later in ." +msgid "Stateful clones are covered later in ." msgstr "" #. Tag: title #, no-c-format -msgid "An example clone" +msgid "A clone of an LSB resource" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"apache-clone\">\n" " <meta_attributes id=\"apache-clone-meta\">\n" " <nvpair id=\"apache-unique\" name=\"globally-unique\" value=\"false\"/>\n" " </meta_attributes>\n" " <primitive id=\"apache\" class=\"lsb\" type=\"apache\"/>\n" "</clone>" 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 "Your name for the clone idClone Property Clone Property ClonePropertyid Propertyid id " +msgid "A unique name for the clone idClone Property Clone Property ClonePropertyid Propertyid id " msgstr "" #. Tag: title #, no-c-format msgid "Clone Options" msgstr "" +#. Tag: para +#, no-c-format +msgid "Options inherited from primitive resources: priority, target-role, is-managed" +msgstr "" + #. Tag: title #, no-c-format -msgid "Clone specific configuration options" +msgid "Clone-specific configuration options" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Default" msgstr "" #. Tag: para #, no-c-format msgid "clone-max" msgstr "" #. Tag: para #, no-c-format -msgid "How many copies of the resource to start. Defaults to the number of nodes in the cluster. clone-maxClone Option Clone Option CloneOptionclone-max Optionclone-max clone-max " +msgid "number of nodes in cluster" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "How many copies of the resource to start clone-maxClone Option Clone Option CloneOptionclone-max Optionclone-max clone-max " msgstr "" #. Tag: para #, no-c-format msgid "clone-node-max" msgstr "" #. Tag: para #, no-c-format -msgid "How many copies of the resource can be started on a single node; default 1. clone-node-maxClone Option Clone Option CloneOptionclone-node-max Optionclone-node-max clone-node-max " +msgid "1" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "How many copies of the resource can be started on a single node clone-node-maxClone Option Clone Option CloneOptionclone-node-max Optionclone-node-max clone-node-max " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "clone-min" +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 (since 1.1.14) clone-minClone Option Clone Option CloneOptionclone-min Optionclone-min clone-min " msgstr "" #. Tag: para #, no-c-format msgid "notify" msgstr "" #. Tag: para #, no-c-format -msgid "When stopping or starting a copy of the clone, tell all the other copies beforehand and when the action was successful. Allowed values: false, true notifyClone Option Clone Option CloneOptionnotify Optionnotify notify " +msgid "true" +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: false, true notifyClone Option Clone Option CloneOptionnotify Optionnotify notify " msgstr "" #. Tag: para #, no-c-format msgid "globally-unique" msgstr "" #. Tag: para #, no-c-format -msgid "Does each copy of the clone perform a different function? Allowed values: false, true globally-uniqueClone Option Clone Option CloneOptionglobally-unique Optionglobally-unique globally-unique " +msgid "false" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Does each copy of the clone perform a different function? Allowed values: false, true globally-uniqueClone Option Clone Option CloneOptionglobally-unique Optionglobally-unique globally-unique " msgstr "" #. Tag: para #, no-c-format msgid "ordered" msgstr "" #. Tag: para #, no-c-format -msgid "Should the copies be started in series (instead of in parallel). Allowed values: false, true orderedClone Option Clone Option CloneOptionordered Optionordered ordered " +msgid "Should the copies be started in series (instead of in parallel)? Allowed values: false, true orderedClone Option Clone Option CloneOptionordered Optionordered ordered " msgstr "" #. Tag: para #, no-c-format msgid "interleave" msgstr "" #. Tag: para #, no-c-format -msgid "Changes the behavior of ordering constraints (between clones/masters) so that instances can start/stop as soon as their peer instance has (rather than waiting for every instance of the other clone has). Allowed values: false, true interleaveClone Option Clone Option CloneOptioninterleave Optioninterleave interleave " +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: false, true interleaveClone Option Clone Option CloneOptioninterleave Optioninterleave interleave " msgstr "" #. Tag: title #, no-c-format msgid "Clone Instance Attributes" 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" msgstr "" #. Tag: para #, no-c-format -msgid "Clones must contain exactly one group or one regular resource." +msgid "Clones must contain exactly one primitive or group resource." 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" 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 to those for regular resources except that the clone’s id is used." +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 id is used." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "Ordering constraints behave slightly differently for clones. In the example below, apache-stats will wait until all copies of the clone that need to be started have done so before being started itself. Only if no copies can be started apache-stats will be prevented from being active. Additionally, the clone will wait for apache-stats to be stopped before stopping the clone." +msgid "Some constraints involving clones" msgstr "" -#. Tag: para +#. Tag: programlisting #, no-c-format -msgid "Colocation of a regular (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 "<constraints>\n" +" <rsc_location id=\"clone-prefers-node1\" rsc=\"apache-clone\" node=\"node1\" score=\"500\"/>\n" +" <rsc_colocation id=\"stats-with-clone\" rsc=\"apache-stats\" with=\"apache-clone\"/>\n" +" <rsc_order id=\"start-clone-then-stats\" first=\"apache-clone\" then=\"apache-stats\"/>\n" +"</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "Colocation between clones is also possible. In such cases, the set of allowed locations for the clone is limited to nodes on which the clone is (or will be) active. Allocation is then performed as normally." +msgid "Ordering constraints behave slightly differently for clones. In the example above, apache-stats will wait until all copies of apache-clone that need to be started have done so before being started itself. Only if no copies can be started will apache-stats be prevented from being active. Additionally, the clone will wait for apache-stats to be stopped before stopping itself." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Example constraints involving clones" +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." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "<constraints>\n" -" <rsc_location id=\"clone-prefers-node1\" rsc=\"apache-clone\" node=\"node1\" score=\"500\"/>\n" -" <rsc_colocation id=\"stats-with-clone\" rsc=\"apache-stats\" with=\"apache-clone\"/>\n" -" <rsc_order id=\"start-clone-then-stats\" first=\"apache-clone\" then=\"apache-stats\"/>\n" -"</constraints>" +msgid "Colocation between clones is also possible. If one clone A is colocated with another clone B, the set of allowed locations for A is limited to nodes on which B is (or will be) active. Placement is then performed normally." msgstr "" #. Tag: title #, no-c-format msgid "Clone Stickiness" msgstr "" #. Tag: para #, no-c-format msgid " resource-stickinessClones Clones " msgstr "" #. Tag: para #, no-c-format msgid "To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for resource-stickiness 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 "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 resource-stickiness 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: title #, no-c-format msgid "Clone Resource Agent Requirements" 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 #, no-c-format -msgid "Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with other probes for instances of the clone should result in they should return one of the other OCF error codes." +msgid "Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with ${OCF_SUCCESS} if the node has that exact instance active. All other probes for instances of the clone should result in ${OCF_NOT_RUNNING} (or one of the other OCF error codes if they are failed)." msgstr "" #. Tag: para #, no-c-format -msgid "Copies of a clone are identified by appending a colon and a numerical offset, eg. apache:2." +msgid "Individual instances of a clone are identified by appending a colon and a numerical offset, e.g. apache:2." msgstr "" #. Tag: para #, no-c-format msgid "Resource agents can find out how many copies there are by examining the OCF_RESKEY_CRM_meta_clone_max environment variable and which copy it is by examining OCF_RESKEY_CRM_meta_clone." msgstr "" #. Tag: para #, no-c-format -msgid "You should not make any assumptions (based on OCF_RESKEY_CRM_meta_clone) about which copies are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0." +msgid "The resource agent must not make any assumptions (based on OCF_RESKEY_CRM_meta_clone) 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 "Clone Notifications" msgstr "" #. Tag: para #, no-c-format -msgid "Supporting notifications requires the notify action to be implemented. Once 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 "Supporting notifications requires the notify 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." msgstr "" #. Tag: title #, no-c-format msgid "Environment variables supplied with Clone notify actions" msgstr "" #. Tag: entry #, no-c-format msgid "Variable" msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_type" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: pre, post Environment VariableOCF_RESKEY_CRM_meta_notify_type OCF_RESKEY_CRM_meta_notify_type type typeNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_operation" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: start, stop Environment VariableOCF_RESKEY_CRM_meta_notify_operation OCF_RESKEY_CRM_meta_notify_operation operation operationNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_start_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be started Environment VariableOCF_RESKEY_CRM_meta_notify_start_resource OCF_RESKEY_CRM_meta_notify_start_resource start_resource start_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_stop_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be stopped Environment VariableOCF_RESKEY_CRM_meta_notify_stop_resource OCF_RESKEY_CRM_meta_notify_stop_resource stop_resource stop_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_active_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that are running Environment VariableOCF_RESKEY_CRM_meta_notify_active_resource OCF_RESKEY_CRM_meta_notify_active_resource active_resource active_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_inactive_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that are not running Environment VariableOCF_RESKEY_CRM_meta_notify_inactive_resource OCF_RESKEY_CRM_meta_notify_inactive_resource inactive_resource inactive_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_start_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources will be started Environment VariableOCF_RESKEY_CRM_meta_notify_start_uname OCF_RESKEY_CRM_meta_notify_start_uname start_uname start_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_stop_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources will be stopped Environment VariableOCF_RESKEY_CRM_meta_notify_stop_uname OCF_RESKEY_CRM_meta_notify_stop_uname stop_uname stop_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_active_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources are running Environment VariableOCF_RESKEY_CRM_meta_notify_active_uname OCF_RESKEY_CRM_meta_notify_active_uname active_uname active_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_inactive_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources are not running Environment VariableOCF_RESKEY_CRM_meta_notify_inactive_uname OCF_RESKEY_CRM_meta_notify_inactive_uname inactive_uname inactive_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format -msgid "The variables come in pairs, such as OCF_RESKEY_CRM_meta_notify_start_resource and OCF_RESKEY_CRM_meta_notify_start_uname and should be treated as an array of whitespace separated elements." +msgid "The variables come in pairs, such as OCF_RESKEY_CRM_meta_notify_start_resource and OCF_RESKEY_CRM_meta_notify_start_uname and should be treated as an array of whitespace-separated elements." msgstr "" #. Tag: para #, no-c-format msgid "Thus in order to indicate that clone:0 will be started on sles-1, clone:2 will be started on sles-3, and clone:3 will be started on sles-2, the cluster would set" msgstr "" #. Tag: title #, no-c-format -msgid "Example notification variables" +msgid "Notification variables" 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\"" msgstr "" #. Tag: title #, no-c-format msgid "Proper Interpretation of Notification Environment Variables" msgstr "" #. Tag: title #, no-c-format msgid "Pre-notification (stop):" msgstr "" #. Tag: para #, no-c-format msgid "Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource" msgstr "" #. Tag: para #, no-c-format msgid "Inactive resources: $OCF_RESKEY_CRM_meta_notify_inactive_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be started: $OCF_RESKEY_CRM_meta_notify_start_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource" msgstr "" #. Tag: title #, no-c-format msgid "Post-notification (stop) / Pre-notification (start):" msgstr "" #. Tag: para #, no-c-format msgid "Active resources" msgstr "" #. Tag: para #, no-c-format msgid "$OCF_RESKEY_CRM_meta_notify_active_resource" msgstr "" #. Tag: para #, no-c-format msgid "minus $OCF_RESKEY_CRM_meta_notify_stop_resource" msgstr "" #. Tag: para #, no-c-format msgid "Inactive resources" msgstr "" #. Tag: para #, no-c-format msgid "$OCF_RESKEY_CRM_meta_notify_inactive_resource" msgstr "" #. Tag: para #, no-c-format msgid "plus $OCF_RESKEY_CRM_meta_notify_stop_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that were started: $OCF_RESKEY_CRM_meta_notify_start_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that were stopped: $OCF_RESKEY_CRM_meta_notify_stop_resource" msgstr "" #. Tag: title #, no-c-format msgid "Post-notification (start):" msgstr "" #. Tag: para #, no-c-format msgid "Active resources:" msgstr "" #. Tag: para #, no-c-format msgid "plus $OCF_RESKEY_CRM_meta_notify_start_resource" msgstr "" #. Tag: para #, no-c-format msgid "Inactive resources:" msgstr "" #. Tag: para #, no-c-format msgid "minus $OCF_RESKEY_CRM_meta_notify_start_resource" msgstr "" #. Tag: title #, no-c-format msgid "Multi-state - Resources That Have Multiple Modes" msgstr "" #. Tag: para #, no-c-format msgid " Multi-state Resources ResourcesMulti-state Multi-state " msgstr "" #. Tag: para #, no-c-format -msgid "Multi-state resources are a specialization of Clone resources; please ensure you understand the section on clones before continuing! They allow the instances to be in one of two operating modes; these are called Master and Slave, 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 state." +msgid "Multi-state resources are a specialization of clone resources; please ensure you understand before continuing!" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Multi-state resources allow the instances to be in one of two operating modes (called roles). The roles are called master and slave, 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." msgstr "" #. Tag: title #, no-c-format msgid "Multi-state Properties" msgstr "" #. Tag: title #, no-c-format msgid "Properties of a Multi-State Resource" msgstr "" #. Tag: para #, no-c-format msgid "Your name for the multi-state resource idMulti-State Property Multi-State Property Multi-StatePropertyid Propertyid id " msgstr "" #. Tag: title #, no-c-format msgid "Multi-state Options" msgstr "" #. Tag: para #, no-c-format msgid "Options inherited from primitive resources: priority, target-role, is-managed" msgstr "" #. Tag: para #, no-c-format msgid "Options inherited from clone resources: clone-max, clone-node-max, notify, globally-unique, ordered, interleave" msgstr "" #. Tag: title #, no-c-format -msgid "Multi-state specific resource configuration options" +msgid "Multi-state-specific resource configuration options" msgstr "" #. Tag: para #, no-c-format msgid "master-max" msgstr "" #. Tag: para #, no-c-format -msgid "How many copies of the resource can be promoted to master status; default 1. master-maxMulti-State Option Multi-State Option Multi-StateOptionmaster-max Optionmaster-max master-max " +msgid "How many copies of the resource can be promoted to the master role master-maxMulti-State Option Multi-State Option Multi-StateOptionmaster-max Optionmaster-max master-max " msgstr "" #. Tag: para #, no-c-format msgid "master-node-max" msgstr "" #. Tag: para #, no-c-format -msgid "How many copies of the resource can be promoted to master status on a single node; default 1. master-node-maxMulti-State Option Multi-State Option Multi-StateOptionmaster-node-max Optionmaster-node-max master-node-max " +msgid "How many copies of the resource can be promoted to the master role on a single node master-node-maxMulti-State Option Multi-State Option Multi-StateOptionmaster-node-max Optionmaster-node-max master-node-max " msgstr "" #. Tag: title #, no-c-format msgid "Multi-state Instance Attributes" msgstr "" #. Tag: para #, no-c-format -msgid "Multi-state resources have no instance attributes; however, any that are set here will be inherited by master’s children." +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" msgstr "" #. Tag: para #, no-c-format -msgid "Masters must contain exactly one group or one regular resource." +msgid "Masters must contain exactly one primitive or group resource." 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." msgstr "" #. Tag: title #, no-c-format msgid "Monitoring Multi-State Resources" msgstr "" #. Tag: para #, no-c-format -msgid "The normal type of monitor actions are not sufficient to monitor a multi-state resource in the Master state. To detect failures of the Master instance, you need to define an additional monitor action with role=\"Master\"." +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." msgstr "" #. Tag: para #, no-c-format -msgid "It is crucial that every monitor operation has a different interval!" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "This is because Pacemaker currently differentiates between operations only by resource and interval; so if eg. a master/slave resource has 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." +msgid "Define two monitoring actions: the usual one will cover the slave role, and an additional one with role=\"master\" will cover the master role." msgstr "" #. Tag: title #, no-c-format msgid "Monitoring both states of a multi-state resource" msgstr "" #. Tag: programlisting #, no-c-format msgid "<master id=\"myMasterRsc\">\n" " <primitive id=\"myRsc\" class=\"ocf\" type=\"myApp\" provider=\"myCorp\">\n" " <operations>\n" " <op id=\"public-ip-slave-check\" name=\"monitor\" interval=\"60\"/>\n" " <op id=\"public-ip-master-check\" name=\"monitor\" interval=\"61\" role=\"Master\"/>\n" " </operations>\n" " </primitive>\n" "</master>" msgstr "" +#. Tag: para +#, no-c-format +msgid "It is crucial that every 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" msgstr "" #. Tag: para #, no-c-format -msgid "In most cases, a 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 to those for regular resources except that the master’s id is used." +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 id is used." 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 when the rsc-role and/or with-rsc-role fields (for colocation constraints) and first-action and/or then-action fields (for ordering constraints) are used." +msgid "When considering multi-state resources in constraints, for most purposes it is sufficient to treat them as clones. The exception is that the first-action and/or then-action fields for ordering constraints may be set to promote or demote to constrain the master role, and colocation constraints may contain rsc-role and/or with-rsc-role fields." msgstr "" #. Tag: title #, no-c-format -msgid "Additional constraint options relevant to multi-state resources" +msgid "Additional colocation constraint options for multi-state resources" msgstr "" #. Tag: para #, no-c-format msgid "rsc-role" msgstr "" #. Tag: para #, no-c-format -msgid "An additional attribute of colocation constraints that specifies the role that rsc must be in. Allowed values: Started, Master, Slave. rsc-roleOrdering Constraints Ordering Constraints ConstraintsOrderingrsc-role Orderingrsc-role rsc-role " +msgid "started" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "An additional attribute of colocation constraints that specifies the role that rsc must be in. Allowed values: started, master, slave. rsc-roleOrdering Constraints Ordering Constraints ConstraintsOrderingrsc-role Orderingrsc-role rsc-role " msgstr "" #. Tag: para #, no-c-format msgid "with-rsc-role" msgstr "" #. Tag: para #, no-c-format -msgid "An additional attribute of colocation constraints that specifies the role that with-rsc must be in. Allowed values: Started, Master, Slave. with-rsc-roleOrdering Constraints Ordering Constraints ConstraintsOrderingwith-rsc-role Orderingwith-rsc-role with-rsc-role " +msgid "An additional attribute of colocation constraints that specifies the role that with-rsc must be in. Allowed values: started, master, slave. with-rsc-roleOrdering Constraints Ordering Constraints ConstraintsOrderingwith-rsc-role Orderingwith-rsc-role with-rsc-role " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Constraints involving multi-state resources" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<constraints>\n" +" <rsc_location id=\"db-prefers-node1\" rsc=\"database\" node=\"node1\" score=\"500\"/>\n" +" <rsc_colocation id=\"backup-with-db-slave\" rsc=\"backup\"\n" +" with-rsc=\"database\" with-rsc-role=\"Slave\"/>\n" +" <rsc_colocation id=\"myapp-with-db-master\" rsc=\"myApp\"\n" +" with-rsc=\"database\" with-rsc-role=\"Master\"/>\n" +" <rsc_order id=\"start-db-before-backup\" first=\"database\" then=\"backup\"/>\n" +" <rsc_order id=\"promote-db-then-app\" first=\"database\" first-action=\"promote\"\n" +" then=\"myApp\" then-action=\"start\"/>\n" +"</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "first-action" +msgid "In the example above, myApp 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 myApp be prevented from being active. Additionally, the cluster will wait for myApp to be stopped before demoting the database." msgstr "" #. Tag: para #, no-c-format -msgid "An additional attribute of ordering constraints that specifies the action that the first resource must complete before executing the specified action for the then resource. Allowed values: start, stop, promote, demote. first-actionOrdering Constraints Ordering Constraints ConstraintsOrderingfirst-action Orderingfirst-action first-action " +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 (master or slave). In the example above, the cluster will choose a location based on where database is running as a master, and if there are multiple master instances it will also factor in myApp's own location preferences when deciding which location to choose." msgstr "" #. Tag: para #, no-c-format -msgid "then-action" +msgid "Colocation with regular clones and other multi-state resources is also possible. In such cases, the set of allowed locations for the rsc clone is (after role filtering) limited to nodes on which the with-rsc 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "role" msgstr "" #. Tag: para #, no-c-format -msgid "An additional attribute of ordering constraints that specifies the action that the then resource can only execute after the first-action on the first resource has completed. Allowed values: start, stop, promote, demote. Defaults to the value (specified or implied) of first-action. then-actionOrdering Constraints Ordering Constraints ConstraintsOrderingthen-action Orderingthen-action then-action " +msgid "The role that all members of the set must be in. Allowed values: started, master, slave. roleOrdering Constraints Ordering Constraints ConstraintsOrderingrole Orderingrole role " msgstr "" #. Tag: para #, no-c-format -msgid "In the example below, myApp will wait until one of the database copies has been started and promoted to master before being started itself. Only if no copies can be promoted will apache-stats be prevented from being active. Additionally, the database will wait for myApp to be stopped before it is demoted." +msgid "In the following example B's master must be located on the same node as A's master. Additionally resources C and D must be located on the same node as A's and B's masters." msgstr "" #. Tag: title #, no-c-format -msgid "Example constraints involving multi-state resources" +msgid "Colocate C and D with A’s and B’s master instances" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" -" <rsc_location id=\"db-prefers-node1\" rsc=\"database\" node=\"node1\" score=\"500\"/>\n" -" <rsc_colocation id=\"backup-with-db-slave\" rsc=\"backup\"\n" -" with-rsc=\"database\" with-rsc-role=\"Slave\"/>\n" -" <rsc_colocation id=\"myapp-with-db-master\" rsc=\"myApp\"\n" -" with-rsc=\"database\" with-rsc-role=\"Master\"/>\n" -" <rsc_order id=\"start-db-before-backup\" first=\"database\" then=\"backup\"/>\n" -" <rsc_order id=\"promote-db-then-app\" first=\"database\" first-action=\"promote\"\n" -" then=\"myApp\" then-action=\"start\"/>\n" +" <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n" +" <resource_set id=\"colocated-set-example-1\" sequential=\"true\" role=\"Master\">\n" +" <resource_ref id=\"A\"/>\n" +" <resource_ref id=\"B\"/>\n" +" </resource_set>\n" +" <resource_set id=\"colocated-set-example-2\" sequential=\"true\">\n" +" <resource_ref id=\"C\"/>\n" +" <resource_ref id=\"D\"/>\n" +" </resource_set>\n" +" </rsc_colocation>\n" "</constraints>" 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" +msgstr "" + #. Tag: para #, no-c-format -msgid "Colocation of a regular (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 is in the specified state (Master or Slave). In the example, the cluster will choose a location based on where database is running as a Master, and if there are multiple Master instances it will also factor in myApp's own location preferences when deciding which location to choose." +msgid "action" 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 rsc clone is (after role filtering) limited to nodes on which the with-rsc multi-state resource is (or will be) in the specified role. Allocation is then performed as-per-normal." +msgid "value of first-action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "An additional attribute of ordering constraint sets that specifies the action that applies to all members of the set. Allowed values: start, stop, promote, demote. actionOrdering Constraints Ordering Constraints ConstraintsOrderingaction Orderingaction action " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Start C and D after first promoting A and B" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<constraints>\n" +" <rsc_order id=\"order-1\" score=\"INFINITY\" >\n" +" <resource_set id=\"ordered-set-1\" sequential=\"true\" action=\"promote\">\n" +" <resource_ref id=\"A\"/>\n" +" <resource_ref id=\"B\"/>\n" +" </resource_set>\n" +" <resource_set id=\"ordered-set-2\" sequential=\"true\" action=\"start\">\n" +" <resource_ref id=\"C\"/>\n" +" <resource_ref id=\"D\"/>\n" +" </resource_set>\n" +" </rsc_order>\n" +"</constraints>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the above example, B cannot be promoted to a master role until A has been promoted. Additionally, resources C and D must wait until A and B have been promoted before they can start." msgstr "" #. Tag: title #, no-c-format msgid "Multi-state Stickiness" msgstr "" #. Tag: para #, no-c-format -msgid " resource-stickinessMulti-State Multi-State To achieve a stable allocation pattern, multi-state resources are slightly sticky by default. If no value for resource-stickiness is provided, the multi-state resource 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 " resource-stickinessMulti-State Multi-State As with regular clones, multi-state resources are slightly sticky by default. See for details." msgstr "" #. Tag: title #, no-c-format msgid "Which Resource Instance is Promoted" msgstr "" #. Tag: para #, no-c-format -msgid "During the start operation, most Resource Agent scripts should call the crm_master utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, master-max, and master-node-max, the instance(s) with the highest preference will be promoted." +msgid "During the start operation, most resource agents should call the crm_master utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, master-max, and master-node-max, the instance(s) with the highest preference will be promoted." msgstr "" #. Tag: para #, no-c-format -msgid "The other alternative is to create a location constraint that indicates which nodes are most preferred as masters." +msgid "An alternative is to create a location constraint that indicates which nodes are most preferred as masters." msgstr "" #. Tag: title #, no-c-format -msgid "Manually specifying which node should be promoted" +msgid "Explicitly preferring node1 to be promoted to master" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_location id=\"master-location\" rsc=\"myMasterRsc\">\n" " <rule id=\"master-rule\" score=\"100\" role=\"Master\">\n" " <expression id=\"master-exp\" attribute=\"#uname\" operation=\"eq\" value=\"node1\"/>\n" " </rule>\n" "</rsc_location>" msgstr "" #. Tag: title #, no-c-format -msgid "Multi-state Resource Agent Requirements" +msgid "Requirements for Multi-state Resource Agents" +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." msgstr "" #. Tag: para #, no-c-format -msgid "Since multi-state resources are an extension of cloned resources, all the requirements of Clones are also requirements of multi-state resources. Additionally, multi-state resources require two extra actions: demote and promote; these actions are responsible for changing the state of the resource. Like start and stop, they should return OCF_SUCCESS if they completed successfully or a relevant error code if they did not." +msgid "Additionally, multi-state resources require two extra actions, demote and promote, which are responsible for changing the state of the resource. Like start and stop, they should return ${OCF_SUCCESS} if they completed successfully or a relevant error code if they did not." 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 Slave. From there the cluster will then decide which instances to promote to Master." +msgid "The states can mean whatever you wish, but when the resource is started, it must come up in the mode called slave. From there the cluster will decide which instances to promote to master." msgstr "" #. Tag: para #, no-c-format -msgid "In addition to the Clone requirements for monitor actions, agents must also accurately 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 "In addition to the clone requirements for monitor actions, agents must also accurately 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 "Role implications of OCF return codes" msgstr "" #. Tag: entry #, no-c-format msgid "Monitor Return Code" msgstr "" #. Tag: para #, no-c-format msgid "OCF_NOT_RUNNING" msgstr "" #. Tag: para #, no-c-format msgid "Stopped Return CodeOCF_NOT_RUNNING OCF_NOT_RUNNING " msgstr "" #. Tag: para #, no-c-format msgid "OCF_SUCCESS" msgstr "" #. Tag: para #, no-c-format msgid "Running (Slave) Return CodeOCF_SUCCESS OCF_SUCCESS " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RUNNING_MASTER" msgstr "" #. Tag: para #, no-c-format msgid "Running (Master) Return CodeOCF_RUNNING_MASTER OCF_RUNNING_MASTER " msgstr "" #. Tag: para #, no-c-format msgid "OCF_FAILED_MASTER" msgstr "" #. Tag: para #, no-c-format msgid "Failed (Master) Return CodeOCF_FAILED_MASTER OCF_FAILED_MASTER " msgstr "" #. Tag: para #, no-c-format msgid "Other" msgstr "" #. Tag: para #, no-c-format msgid "Failed (Slave)" msgstr "" #. Tag: title #, no-c-format msgid "Multi-state Notifications" msgstr "" #. Tag: para #, no-c-format -msgid "Like clones, supporting notifications requires the notify action to be implemented. Once 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 "Like clones, supporting notifications requires the notify 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." msgstr "" #. Tag: title #, no-c-format -msgid "Environment variables supplied with Master notify actions Emphasized variables are specific to Master resources and all behave in the same manner as described for Clone resources." +msgid "Environment variables supplied with multi-state notify actions Emphasized variables are specific to Master resources, and all behave in the same manner as described for Clone resources." msgstr "" #. Tag: para #, no-c-format msgid "Resources the that are running Environment VariableOCF_RESKEY_CRM_meta_notify_active_resource OCF_RESKEY_CRM_meta_notify_active_resource active_resource active_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "Resources the that are not running Environment VariableOCF_RESKEY_CRM_meta_notify_inactive_resource OCF_RESKEY_CRM_meta_notify_inactive_resource inactive_resource inactive_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_master_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that are running in Master mode Environment VariableOCF_RESKEY_CRM_meta_notify_master_resource OCF_RESKEY_CRM_meta_notify_master_resource master_resource master_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_slave_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that are running in Slave mode Environment VariableOCF_RESKEY_CRM_meta_notify_slave_resource OCF_RESKEY_CRM_meta_notify_slave_resource slave_resource slave_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid " Environment VariableOCF_RESKEY_CRM_meta_notify_stop_resource OCF_RESKEY_CRM_meta_notify_stop_resource stop_resource stop_resourceNotification Environment Variable Notification Environment Variable OCF_RESKEY_CRM_meta_notify_stop_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be stopped" msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_promote_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be promoted Environment VariableOCF_RESKEY_CRM_meta_notify_promote_resource OCF_RESKEY_CRM_meta_notify_promote_resource promote_resource promote_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_demote_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be demoted Environment VariableOCF_RESKEY_CRM_meta_notify_demote_resource OCF_RESKEY_CRM_meta_notify_demote_resource demote_resource demote_resourceNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_promote_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources will be promote Environment VariableOCF_RESKEY_CRM_meta_notify_promote_uname OCF_RESKEY_CRM_meta_notify_promote_uname promote_uname promote_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_demote_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources will be demoted Environment VariableOCF_RESKEY_CRM_meta_notify_demote_uname OCF_RESKEY_CRM_meta_notify_demote_uname demote_uname demote_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_master_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources are running in Master mode Environment VariableOCF_RESKEY_CRM_meta_notify_master_uname OCF_RESKEY_CRM_meta_notify_master_uname master_uname master_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: para #, no-c-format msgid "OCF_RESKEY_CRM_meta_notify_slave_uname" msgstr "" #. Tag: para #, no-c-format msgid "Nodes on which resources are running in Slave mode Environment VariableOCF_RESKEY_CRM_meta_notify_slave_uname OCF_RESKEY_CRM_meta_notify_slave_uname slave_uname slave_unameNotification Environment Variable Notification Environment Variable " msgstr "" #. Tag: title #, no-c-format -msgid "Multi-state - Proper Interpretation of Notification Environment Variables" +msgid "Proper Interpretation of Multi-state Notification Environment Variables" msgstr "" #. Tag: title #, no-c-format msgid "Pre-notification (demote):" msgstr "" #. Tag: para #, no-c-format msgid "Active resources: $OCF_RESKEY_CRM_meta_notify_active_resource" msgstr "" #. Tag: para #, no-c-format msgid "Master resources: $OCF_RESKEY_CRM_meta_notify_master_resource" msgstr "" #. Tag: para #, no-c-format msgid "Slave resources: $OCF_RESKEY_CRM_meta_notify_slave_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources to be demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource" msgstr "" #. Tag: title #, no-c-format msgid "Post-notification (demote) / Pre-notification (stop):" msgstr "" #. Tag: para #, no-c-format msgid "Master resources:" msgstr "" #. Tag: para #, no-c-format msgid "$OCF_RESKEY_CRM_meta_notify_master_resource" msgstr "" #. Tag: para #, no-c-format msgid "minus $OCF_RESKEY_CRM_meta_notify_demote_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that were demoted: $OCF_RESKEY_CRM_meta_notify_demote_resource" msgstr "" #. Tag: title #, no-c-format msgid "Post-notification (stop) / Pre-notification (start)" msgstr "" #. Tag: para #, no-c-format msgid "Active resources:" msgstr "" #. Tag: para #, no-c-format msgid "Slave resources:" msgstr "" #. Tag: para #, no-c-format msgid "$OCF_RESKEY_CRM_meta_notify_slave_resource" 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 $OCF_RESKEY_CRM_meta_notify_promote_resource" msgstr "" #. Tag: para #, no-c-format msgid "minus $OCF_RESKEY_CRM_meta_notify_promote_resource" msgstr "" #. Tag: para #, no-c-format msgid "Resources that were promoted: $OCF_RESKEY_CRM_meta_notify_promote_resource" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Basics.pot b/doc/Pacemaker_Explained/pot/Ch-Basics.pot index 7e199edae9..8e852ee568 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Basics.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Basics.pot @@ -1,547 +1,563 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Configuration Basics" msgstr "" #. Tag: title #, no-c-format msgid "Configuration Layout" msgstr "" #. Tag: para #, no-c-format -msgid "The cluster is written using XML notation and divided into two main sections: configuration and status." +msgid "The cluster is defined by the Cluster Information Base (CIB), which uses XML notation. The simplest CIB, an empty one, looks like this:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An empty configuration" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<cib crm_feature_set=\"3.0.7\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\">\n" +" <configuration>\n" +" <crm_config/>\n" +" <nodes/>\n" +" <resources/>\n" +" <constraints/>\n" +" </configuration>\n" +" <status/>\n" +"</cib>" msgstr "" #. Tag: para #, no-c-format -msgid "The status section contains the history of each resource on each node and based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for the status section is the local resource manager (lrmd) process on each cluster node and the cluster will occasionally repopulate the entire section. For this reason it is never written to disk and administrators are advised against modifying it in any way." +msgid "The empty configuration above contains the major sections that make up a CIB:" msgstr "" #. Tag: para #, no-c-format -msgid "The configuration section contains the more traditional information like cluster options, lists of resources and indications of where they should be placed. The configuration section is the primary focus of this document." +msgid "cib: The entire CIB is enclosed with a cib tag. Certain fundamental settings are defined as attributes of this tag." msgstr "" #. Tag: para #, no-c-format -msgid "The configuration section itself is divided into four parts:" +msgid "configuration: 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 "Configuration options (called crm_config)" +msgid "crm_config: cluster-wide configuration options" msgstr "" #. Tag: para #, no-c-format -msgid "Nodes" +msgid "nodes: the machines that host the cluster" msgstr "" #. Tag: para #, no-c-format -msgid "Resources" +msgid "resources: the services run by the cluster" msgstr "" #. Tag: para #, no-c-format -msgid "Resource relationships (called constraints)" +msgid "constraints: indications of how resources should be placed" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "An empty configuration" +msgid "status: This section contains the history of each resource on each node. Based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for this section is the local resource manager (lrmd process) on each cluster node, and the cluster will occasionally repopulate the entire section. For this reason, it is never written to disk, and administrators are advised against modifying it in any way." msgstr "" -#. Tag: programlisting +#. Tag: para +#, no-c-format +msgid "In this document, configuration settings will be described as properties or options based on how they are defined in the CIB:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Properties are XML attributes of an XML element." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Options are name-value pairs expressed as nvpair child elements of an XML element." +msgstr "" + +#. Tag: para #, no-c-format -msgid " <cib admin_epoch=\"0\" epoch=\"0\" num_updates=\"0\" have-quorum=\"false\">\n" -" <configuration>\n" -" <crm_config/>\n" -" <nodes/>\n" -" <resources/>\n" -" <constraints/>\n" -" </configuration>\n" -" <status/>\n" -" </cib>" +msgid "Normally you will use command-line tools that abstract the XML, so the distinction will be unimportant; both properties and options are cluster settings you can tweak." msgstr "" #. Tag: title #, no-c-format msgid "The Current State of the Cluster" msgstr "" #. Tag: para #, no-c-format -msgid "Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the crm_mon utility that will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures." +msgid "Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the crm_mon utility, which will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures." msgstr "" #. Tag: para #, no-c-format msgid "Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures." msgstr "" #. Tag: para #, no-c-format msgid "Details on all the available options can be obtained using the crm_mon --help command." msgstr "" #. Tag: title #, no-c-format msgid "Sample output from crm_mon" msgstr "" #. Tag: screen #, no-c-format msgid " ============\n" " Last updated: Fri Nov 23 15:26:13 2007\n" " Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n" " 3 Nodes configured.\n" " 5 Resources configured.\n" " ============\n" "\n" " Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n" " 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n" " 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n" " 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n" " rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n" " child_DoFencing:2 (stonith:external/vmware): Started sles-1\n" " Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n" " Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n" " rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n" " rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n" " child_DoFencing:0 (stonith:external/vmware): Started sles-3" msgstr "" #. Tag: title #, no-c-format msgid "Sample output from crm_mon -n" msgstr "" #. Tag: screen #, no-c-format msgid " ============\n" " Last updated: Fri Nov 23 15:26:13 2007\n" " Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec)\n" " 3 Nodes configured.\n" " 5 Resources configured.\n" " ============\n" "\n" " Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online\n" " Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby\n" " Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online\n" "\n" " Resource Group: group-1\n" " 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1\n" " 192.168.100.182 (heartbeat:IPaddr): Started sles-1\n" " 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1\n" " rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1\n" " rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3\n" " rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3\n" " Clone Set: DoFencing\n" " child_DoFencing:0 (stonith:external/vmware): Started sles-3\n" " child_DoFencing:1 (stonith:external/vmware): Stopped\n" " child_DoFencing:2 (stonith:external/vmware): Started sles-1" msgstr "" #. Tag: para #, no-c-format -msgid "The DC (Designated Controller) node is where all the decisions are made and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting." +msgid "The DC (Designated Controller) node is where all the decisions are made, and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting." msgstr "" #. Tag: title #, no-c-format msgid "How Should the Configuration be Updated?" msgstr "" #. Tag: para #, no-c-format msgid "There are three basic rules for updating the cluster configuration:" msgstr "" #. Tag: para #, no-c-format -msgid "Rule 1 - Never edit the cib.xml file manually. Ever. I’m not making this up." +msgid "Rule 1 - Never edit the cib.xml file manually. Ever. I’m not making this up." msgstr "" #. Tag: para #, no-c-format msgid "Rule 2 - Read Rule 1 again." msgstr "" #. Tag: para #, no-c-format msgid "Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration." msgstr "" #. Tag: para #, no-c-format -msgid "Now that it is clear how NOT to update the configuration, we can begin to explain how you should." +msgid "Now that it is clear how not to update the configuration, we can begin to explain how you should." +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 cibadmin command which talks to a running cluster. With cibadmin, the user 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." +msgid "The most powerful tool for modifying the configuration is the cibadmin command. With cibadmin, 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 cibadmin 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." +msgid "The simplest way of using cibadmin 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. 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." msgstr "" #. Tag: title #, no-c-format msgid "Safely using an editor to modify the cluster configuration" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# cibadmin --query > tmp.xml\n" "# vi tmp.xml\n" "# cibadmin --replace --xml-file tmp.xml" msgstr "" #. Tag: para #, no-c-format -msgid "Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing the configuration can normally be found in /usr/lib/heartbeat/pacemaker.rng on most systems." +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 pacemaker.rng, which may be deployed in a location such as /usr/share/pacemaker or /usr/lib/heartbeat depending on your operating system and how you installed the software." msgstr "" #. Tag: para #, no-c-format -msgid "If you only wanted to modify the resources section, you could instead do" +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 a subsection of the cluster configuration" +msgid "Safely using an editor to modify only the resources section" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# cibadmin --query --obj_type resources > tmp.xml\n" +msgid "# cibadmin --query --scope resources > tmp.xml\n" "# vi tmp.xml\n" -"# cibadmin --replace --obj_type resources --xml-file tmp.xml" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "to avoid modifying any other part of the configuration." +"# 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. Eg. run" +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: programlisting -#, no-c-format -msgid "# cibadmin -Q | grep stonith" +msgid "Searching for STONITH-related configuration items" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid " <nvpair id=\"cib-bootstrap-options-stonith-action\" name=\"stonith-action\" value=\"reboot\"/>\n" +msgid "# cibadmin -Q | grep stonith\n" +" <nvpair id=\"cib-bootstrap-options-stonith-action\" name=\"stonith-action\" value=\"reboot\"/>\n" " <nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"1\"/>\n" " <primitive id=\"child_DoFencing\" class=\"stonith\" type=\"external/vmware\">\n" " <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n" " <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n" " <lrm_resource id=\"child_DoFencing:1\" type=\"external/vmware\" class=\"stonith\">\n" " <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n" " <lrm_resource id=\"child_DoFencing:2\" type=\"external/vmware\" class=\"stonith\">\n" " <lrm_resource id=\"child_DoFencing:0\" type=\"external/vmware\" class=\"stonith\">\n" " <lrm_resource id=\"child_DoFencing:3\" type=\"external/vmware\" class=\"stonith\">" msgstr "" #. Tag: para #, no-c-format -msgid "Next identify the resource’s tag name and id (in this case we’ll choose primitive and child_DoFencing). Then simply execute:" +msgid "If you wanted to delete the primitive tag with id child_DoFencing, you would run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# cibadmin --delete --crm_xml '<primitive id=\"child_DoFencing\"/>'" msgstr "" #. Tag: title #, no-c-format msgid "Updating the Configuration Without Using XML" msgstr "" #. Tag: para #, no-c-format -msgid "Some common tasks can also be performed with one of the higher level tools that avoid the need to read or edit XML." +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:" +msgid "To enable STONITH for example, one could run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name stonith-enabled --attr-value true" +msgid "# crm_attribute --name stonith-enabled --update 1" msgstr "" #. Tag: para #, no-c-format -msgid "Or, to see if somenode is allowed to run resources, there is:" +msgid "Or, to check whether somenode is allowed to run resources, there is:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_standby --get-value --node-uname somenode" +msgid "# crm_standby --get-value --node somenode" msgstr "" #. Tag: para #, no-c-format -msgid "Or, to find the current location of my-test-rsc, one can use:" +msgid "Or, to find the current location of my-test-rsc, one can use:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid "# crm_resource --locate --resource my-test-rsc" msgstr "" +#. Tag: para +#, no-c-format +msgid "Examples of using these tools for specific cases will be given throughout this document where appropriate." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Old versions of pacemaker (1.0.3 and earlier) had different command-line tool syntax. If you are using an older version, check your installed manual pages for the proper syntax to use." +msgstr "" + #. Tag: title #, no-c-format msgid "Making Configuration Changes in a Sandbox" msgstr "" #. Tag: para #, no-c-format msgid "Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created crm_shadow 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 crm_shadow and give it the name of a configuration to create Shadow copies are identified with a name, making it possible to have more than one. ; be sure to follow the simple on-screen instructions." +msgid "To begin, simply invoke crm_shadow --create with the name of a configuration to create Shadow copies are identified with a name, making it possible to have more than one., and follow the simple on-screen instructions." msgstr "" #. Tag: para #, no-c-format -msgid "Read the above carefully, failure to do so could result in you destroying the cluster’s active configuration!" +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: programlisting +#. 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" +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 commit the changes, or discard them as shown below. Again, be sure to follow the on-screen instructions carefully." +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 --commit option, or discard them using the --delete option. Again, be sure to follow the on-screen instructions carefully!" msgstr "" #. Tag: para #, no-c-format -msgid "For a full list of crm_shadow options and commands, invoke it with the <parameter>--help</parameter> option." +msgid "For a full list of crm_shadow options and commands, invoke it with the --help option." msgstr "" #. Tag: title #, no-c-format -msgid "Using a sandbox to make multiple changes atomically" +msgid "Using a sandbox to make multiple changes atomically, discard them and verify the real configuration is untouched" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format msgid " shadow[test] # crm_failcount -G -r rsc_c001n01\n" " name=fail-count-rsc_c001n01 value=0\n" -" shadow[test] # crm_standby -v on -n c001n02\n" -" shadow[test] # crm_standby -G -n c001n02\n" +" shadow[test] # crm_standby -v on -N c001n02\n" +" shadow[test] # crm_standby -G -N c001n02\n" " name=c001n02 scope=nodes value=on\n" " shadow[test] # cibadmin --erase --force\n" " shadow[test] # cibadmin --query\n" " <cib cib_feature_revision=\"1\" validate-with=\"pacemaker-1.0\" admin_epoch=\"0\" crm_feature_set=\"3.0\" have-quorum=\"1\" epoch=\"112\"\n" " dc-uuid=\"c001n01\" num_updates=\"1\" cib-last-written=\"Fri Jun 27 12:17:10 2008\">\n" " <configuration>\n" " <crm_config/>\n" " <nodes/>\n" " <resources/>\n" " <constraints/>\n" " </configuration>\n" " <status/>\n" " </cib>\n" " shadow[test] # crm_shadow --delete test --force\n" " Now type Ctrl-D to exit the crm_shadow shell\n" " shadow[test] # exit\n" " # crm_shadow --which\n" -" No shadow instance provided\n" +" No active shadow configuration defined\n" " # cibadmin -Q\n" " <cib cib_feature_revision=\"1\" validate-with=\"pacemaker-1.0\" admin_epoch=\"0\" crm_feature_set=\"3.0\" have-quorum=\"1\" epoch=\"110\"\n" " dc-uuid=\"c001n01\" num_updates=\"551\">\n" " <configuration>\n" " <crm_config>\n" " <cluster_property_set id=\"cib-bootstrap-options\">\n" " <nvpair id=\"cib-bootstrap-1\" name=\"stonith-enabled\" value=\"1\"/>\n" " <nvpair id=\"cib-bootstrap-2\" name=\"pe-input-series-max\" value=\"30000\"/>" msgstr "" -#. Tag: para -#, no-c-format -msgid "Making changes in a sandbox and verifying the real configuration is untouched" -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 (eg. crm_shadow --commit mytest --force), it is often advisable to simulate the effect of the changes with crm_simulate, eg." +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. crm_shadow --commit mytest --force), it is often advisable to simulate the effect of the changes with crm_simulate. For example:" msgstr "" -#. Tag: programlisting +#. 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 "The tool uses the same library as the live cluster to show what it would have done given the supplied input. It’s output, in addition to a significant amount of logging, is stored in two files tmp.graph and tmp.dot, both are representations of the same thing — the cluster’s response to your changes." +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 tmp.graph and tmp.dot. 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 Graph visualization software. See http://www.graphviz.org/ for details. dot-file representing the same information." msgstr "" #. Tag: para #, no-c-format -msgid "In the graph file is stored the complete transition, 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 dot-file representing the same information." +msgid "For information on the options supported by crm_simulate, use its --help 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" +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 rsc_action_interval node" 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 really bad. Please report them to the development team." msgstr "" #. Tag: title #, no-c-format msgid "Small Cluster Transition" msgstr "" -#. Tag: phrase -#, no-c-format -msgid "An example transition graph as represented by Graphviz" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "In the above example, it appears that a new node, node2, has come online and that the cluster is checking to make sure rsc1, rsc2 and rsc3 are not already running there (Indicated by the *_monitor_0 entries). Once it did that, and assuming the resources were not active there, it would have liked to stop rsc1 and rsc2 on node1 and move them to node2. 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 rsc3 anywhere." -msgstr "" - #. Tag: para #, no-c-format -msgid "For information on the options supported by crm_simulate, use the --help option." +msgid "In the above example, it appears that a new node, pcmk-2, has come online and that the cluster is checking to make sure rsc1, rsc2 and rsc3 are not already running there (Indicated by the rscN_monitor_0 entries). Once it did that, and assuming the resources were not active there, it would have liked to stop rsc1 and rsc2 on pcmk-1 and move them to pcmk-2. 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 rsc3 anywhere." msgstr "" #. Tag: title #, no-c-format msgid "Complex Cluster Transition" msgstr "" -#. Tag: phrase -#, no-c-format -msgid "Another, slightly more complex, transition graph that you're not expected to be able to read" -msgstr "" - #. Tag: title #, no-c-format -msgid "Do I Need to Update the Configuration on all Cluster Nodes?" +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 "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Constraints.pot b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot index 8abc38fffe..44d103e956 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Constraints.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot @@ -1,822 +1,1046 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 " ResourceConstraints Constraints " 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 on a per-resource basis and any node with a negative score for a resource can’t run that resource. After calculating the scores for a resource, the cluster then chooses the node with the highest one." +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 "INFINITY is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules:" +msgid "Pacemaker implements INFINITY (or equivalently, +INFINITY) 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 + INFINITY = INFINITY" msgstr "" #. Tag: para #, no-c-format -msgid "Any value - INFINITY = -INFINITY" +msgid "Any value - INFINITY = -INFINITY" msgstr "" #. Tag: para #, no-c-format -msgid "INFINITY - INFINITY = -INFINITY" +msgid "INFINITY - INFINITY = -INFINITY" +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 " Location Constraints ResourceConstraintsLocation ConstraintsLocation Location There are two alternative strategies for specifying which nodes a resources can run on. One way is to say that by default they can run anywhere and then create location constraints for nodes that are not allowed. The other option is to have nodes \"opt-in\"… to start with nothing able to run anywhere and selectively enable allowed nodes." +msgid " Location Constraints ResourceConstraintsLocation ConstraintsLocation Location Location constraints 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 opt-out cluster). The other way is to start with nothing able to run anywhere, and use location constraints to selectively enable allowed nodes (an opt-in 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 "Options" +msgid "Location Properties" msgstr "" #. Tag: title #, no-c-format -msgid "Options for Simple Location Constraints" +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 "id" msgstr "" #. Tag: para #, no-c-format msgid "A unique name for the constraint idLocation Constraints Location Constraints ConstraintsLocationid Locationid id " msgstr "" #. Tag: para #, no-c-format msgid "rsc" msgstr "" #. Tag: para #, no-c-format msgid "A resource name rscLocation Constraints Location Constraints ConstraintsLocationrsc Locationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "node" msgstr "" #. Tag: para #, no-c-format msgid "A node’s name nodeLocation Constraints Location Constraints ConstraintsLocationnode Locationnode node " msgstr "" #. Tag: para #, no-c-format msgid "score" msgstr "" #. Tag: para #, no-c-format -msgid "Positive values indicate the resource should run on this node. Negative values indicate the resource should not run on this node." +msgid "Positive values indicate the resource should run on this node. Negative values indicate the resource should not run on this node. Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\". scoreLocation Constraints Location Constraints ConstraintsLocationscore Locationscore score " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "resource-discovery" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "always" msgstr "" #. Tag: para #, no-c-format -msgid "Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\". scoreLocation Constraints Location Constraints ConstraintsLocationscore Locationscore score " +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 "always: Always perform resource discovery for the specified resource on this node." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "never: 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 "exclusive: Perform resource discovery for the specified resource only on this node (and other nodes similarly marked as exclusive). Multiple location constraints using exclusive discovery for the same resource across different nodes creates a subset of nodes resource-discovery is exclusive to. If a resource is marked for exclusive 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 " Resource DiscoveryLocation Constraints Location Constraints ConstraintsLocationResource Discovery LocationResource Discovery Resource Discovery " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Setting resource-discovery to never or exclusive 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 never 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 " Asymmetrical Opt-In Clusters Cluster TypeAsymmetrical Opt-In Asymmetrical Opt-In " msgstr "" #. Tag: para #, no-c-format msgid "To create an opt-in cluster, start by preventing resources from running anywhere by default:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name symmetric-cluster --attr-value false" +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 sles-1, the database prefers sles-2 and both can fail over to sles-3 if their most preferred node fails." +msgid "Then start enabling nodes. The following fragment says that the web server prefers sles-1, the database prefers sles-2 and both can fail over to sles-3 if their most preferred node fails." msgstr "" #. Tag: title #, no-c-format -msgid "Example set of opt-in location constraints" +msgid "Opt-in location constraints for two resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"200\"/>\n" " <rsc_location id=\"loc-2\" rsc=\"Webserver\" node=\"sles-3\" score=\"0\"/>\n" " <rsc_location id=\"loc-3\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/>\n" " <rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-3\" score=\"0\"/>\n" "</constraints>" msgstr "" #. Tag: title #, no-c-format msgid "Symmetrical \"Opt-Out\" Clusters" msgstr "" #. Tag: para #, no-c-format msgid " Symmetrical Opt-Out Clusters Cluster TypeSymmetrical Opt-Out Symmetrical Opt-Out " msgstr "" #. Tag: para #, no-c-format msgid "To create an opt-out cluster, start by allowing resources to run anywhere by default:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name symmetric-cluster --attr-value true" +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 "Example set of opt-out location constraints" +msgid "Opt-out location constraints for two resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"200\"/>\n" " <rsc_location id=\"loc-2-dont-run\" rsc=\"Webserver\" node=\"sles-2\" score=\"-INFINITY\"/>\n" " <rsc_location id=\"loc-3-dont-run\" rsc=\"Database\" node=\"sles-1\" score=\"-INFINITY\"/>\n" " <rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/>\n" "</constraints>" msgstr "" -#. Tag: para -#, no-c-format -msgid "Whether you should choose opt-in or opt-out depends both 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 "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 "Example of two resources that prefer two nodes equally" +msgid "Constraints where a resource prefers two nodes equally" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_location id=\"loc-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"INFINITY\"/>\n" " <rsc_location id=\"loc-2\" rsc=\"Webserver\" node=\"sles-2\" score=\"INFINITY\"/>\n" " <rsc_location id=\"loc-3\" rsc=\"Database\" node=\"sles-1\" score=\"500\"/>\n" " <rsc_location id=\"loc-4\" rsc=\"Database\" node=\"sles-2\" score=\"300\"/>\n" " <rsc_location id=\"loc-5\" rsc=\"Database\" node=\"sles-2\" score=\"200\"/>\n" "</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node’s uname and Database based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations." +msgid "In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node’s uname and Database 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 in which Order Resources Should Start/Stop" +msgid "Specifying the Order in which Resources Should Start/Stop" msgstr "" #. Tag: para #, no-c-format -msgid " ResourceConstraintsOrdering ConstraintsOrdering Ordering ResourceStart Order Start Order Ordering Constraints The way to specify the order in which resources should start is by creating rsc_order constraints." +msgid " ResourceConstraintsOrdering ConstraintsOrdering Ordering ResourceStart Order Start Order Ordering Constraints " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Ordering constraints tell the cluster the order in which resources should start." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Ordering constraints affect only the ordering of resources; they do not require that the resources be placed on the same node. If you want resources to be started on the same node and in a specific order, you need both an ordering constraint and a colocation constraint (see ), or alternatively, a group (see )." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Ordering Properties" msgstr "" #. Tag: title #, no-c-format -msgid "Properties of an Ordering Constraint" +msgid "Properties of a rsc_order Constraint" msgstr "" #. Tag: para #, no-c-format msgid "A unique name for the constraint idOrdering Constraints Ordering Constraints ConstraintsOrderingid Orderingid id " msgstr "" #. Tag: para #, no-c-format msgid "first" msgstr "" #. Tag: para #, no-c-format -msgid "The name of a resource that must be started before the then resource is allowed to. firstOrdering Constraints Ordering Constraints ConstraintsOrderingfirst Orderingfirst first " +msgid "Name of the resource that the then resource depends on firstOrdering Constraints Ordering Constraints ConstraintsOrderingfirst Orderingfirst first " msgstr "" #. Tag: para #, no-c-format msgid "then" msgstr "" #. Tag: para #, no-c-format -msgid "The name of a resource. This resource will start after the first resource. thenOrdering Constraints Ordering Constraints ConstraintsOrderingthen Orderingthen then " +msgid "Name of the dependent resource thenOrdering Constraints Ordering Constraints ConstraintsOrderingthen Orderingthen then " msgstr "" #. Tag: para #, no-c-format -msgid "kind" +msgid "first-action" msgstr "" #. Tag: para #, no-c-format -msgid "How to enforce the constraint. (Since 1.1.2)" +msgid "start" msgstr "" #. Tag: para #, no-c-format -msgid "* Optional - Just a suggestion. Only applies if both resources are starting/stopping." +msgid "The action that the first resource must complete before then-action can be initiated for the then resource. Allowed values: start, stop, promote, demote. first-actionOrdering Constraints Ordering Constraints ConstraintsOrderingfirst-action Orderingfirst-action first-action " msgstr "" #. Tag: para #, no-c-format -msgid "* Mandatory - Always. If first is stopping or cannot be started, then must be stopped." +msgid "then-action" msgstr "" #. Tag: para #, no-c-format -msgid "* Serialize - Ensure that no two stop/start actions occur concurrently for a set of resources." +msgid "value of first-action" msgstr "" #. Tag: para #, no-c-format -msgid " kindOrdering Constraints Ordering Constraints ConstraintsOrderingkind Orderingkind kind " +msgid "The action that the then resource can execute only after the first-action on the first resource has completed. Allowed values: start, stop, promote, demote. then-actionOrdering Constraints Ordering Constraints ConstraintsOrderingthen-action Orderingthen-action then-action " msgstr "" #. Tag: para #, no-c-format -msgid "symmetrical" +msgid "kind" msgstr "" #. Tag: para #, no-c-format -msgid "If true, which is the default, stop the resources in the reverse order. Default value: true symmetricalOrdering Constraints Ordering Constraints Ordering Constraintssymmetrical symmetrical " +msgid "How to enforce the constraint. Allowed values:" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Mandatory Ordering" +msgid "Optional: Just a suggestion. Only applies if both resources are executing the specified actions. Any change in state by the first resource will have no effect on the then resource." msgstr "" #. Tag: para #, no-c-format -msgid "When the then resource cannot run without the first resource being active, one should use mandatory constraints. To specify a constraint is mandatory, use scores greater than zero. This will ensure that the then resource will react when the first resource changes state." +msgid "Mandatory: Always. If first does not perform first-action, then will not be allowed to performed then-action. If first is restarted, then (if running) will be stopped beforehand and started afterward." msgstr "" #. Tag: para #, no-c-format -msgid "If the first resource was running and is stopped, the then resource will also be stopped (if it is running)." +msgid "Serialize: Ensure that no two stop/start actions occur concurrently for the resources. First and then 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 "If the first resource was not running and cannot be started, the then resource will be stopped (if it is running)." +msgid " kindOrdering Constraints Ordering Constraints ConstraintsOrderingkind Orderingkind kind " msgstr "" #. Tag: para #, no-c-format -msgid "If the first resource is (re)started while the then resource is running, the then resource will be stopped and restarted." +msgid "symmetrical" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "TRUE" +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). symmetricalOrdering Constraints Ordering Constraints Ordering Constraintssymmetrical symmetrical " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Promote and demote apply to the master role of multi-state resources." msgstr "" #. Tag: title #, no-c-format -msgid "Advisory Ordering" +msgid "Optional and mandatory ordering" msgstr "" #. Tag: para #, no-c-format -msgid "On the other hand, when score=\"0\" is specified for a constraint, the constraint is considered optional and only has an effect when both resources are stopping and/or starting. Any change in state by the first resource will have no effect on the then resource." +msgid "Here is an example of ordering constraints where Database must start before Webserver, and IP should start before Webserver if they both need to be started:" msgstr "" #. Tag: title #, no-c-format -msgid "Example of an optional and mandatory ordering constraint" +msgid "Optional and mandatory ordering constraints" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" -" <rsc_order id=\"order-1\" first=\"Database\" then=\"Webserver\" />\n" -" <rsc_order id=\"order-2\" first=\"IP\" then=\"Webserver\" score=\"0\"/>\n" +"<rsc_order id=\"order-1\" first=\"IP\" then=\"Webserver\" kind=\"Optional\"/>\n" +"<rsc_order id=\"order-2\" first=\"Database\" then=\"Webserver\" kind=\"Mandatory\" />\n" "</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "Some additional information on ordering constraints can be found in the document Ordering Explained." +msgid "Because the above example lets symmetrical default to TRUE, Webserver must be stopped before Database can be stopped, and Webserver should be stopped before IP 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 " ResourceConstraintsColocation ConstraintsColocation Colocation ResourceLocation Relative to other Resources Location Relative to other Resources When the location of one resource depends on the location of another one, we call this colocation." +msgid " ResourceConstraintsColocation ConstraintsColocation Colocation ResourceLocation Relative to other Resources Location Relative to other Resources Colocation constraints 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. 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. " msgstr "" #. Tag: para #, no-c-format -msgid "There is an important side-effect of creating a colocation constraint between two resources: it affects the order in which resources are assigned to a node. If you think about it, it’s somewhat obvious. You can’t place A relative to B unless you know where B is. 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. " +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 "So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A." +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 "Another thing to keep in mind is that, assuming A is collocated with B, the cluster will also take into account A’s preferences when deciding which node to choose for B." +msgid "For a detailed look at exactly how this occurs, see Colocation Explained." msgstr "" #. Tag: para #, no-c-format -msgid "For a detailed look at exactly how this occurs, see the Colocation Explained document." +msgid "Colocation constraints affect only the placement of resources; they do not require that the resources be started in a particular order. If you want resources to be started on the same node and in a specific order, you need both an ordering constraint (see ) and a colocation constraint, or alternatively, a group (see )." msgstr "" #. Tag: title #, no-c-format -msgid "Properties of a Collocation Constraint" +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. idColocation Constraints Colocation Constraints ConstraintsColocationid Colocationid id " msgstr "" #. Tag: para #, no-c-format -msgid "The colocation source. If the constraint cannot be satisfied, the cluster may decide not to allow the resource to run at all. rscColocation Constraints Colocation Constraints ConstraintsColocationrsc Colocationrsc rsc " +msgid "The name of a resource that should be located relative to with-rsc. rscColocation Constraints Colocation Constraints ConstraintsColocationrsc Colocationrsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "with-rsc" msgstr "" #. Tag: para #, no-c-format -msgid "The colocation target. The cluster will decide where to put this resource first and then decide where to put the resource in the rsc field. with-rscColocation Constraints Colocation Constraints ConstraintsColocationwith-rsc Colocationwith-rsc with-rsc " +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 rsc. with-rscColocation Constraints Colocation Constraints ConstraintsColocationwith-rsc Colocationwith-rsc with-rsc " msgstr "" #. Tag: para #, no-c-format -msgid "Positive values indicate the resource should run on the same node. Negative values indicate the resources should not run on the same node. Values of +/- INFINITY change \"should\" to \"must\". scoreColocation Constraints Colocation Constraints ConstraintsColocationscore Colocationscore score " +msgid "Positive values indicate the resources should run on the same node. Negative values indicate the resources should run on different nodes. Values of +/- INFINITY change \"should\" to \"must\". scoreColocation Constraints Colocation Constraints ConstraintsColocationscore Colocationscore score " msgstr "" #. Tag: title #, no-c-format msgid "Mandatory Placement" msgstr "" #. Tag: para #, no-c-format -msgid "Mandatory placement occurs any time the constraint’s score is +INFINITY or -INFINITY. In such cases, if the constraint can’t be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active." +msgid "Mandatory placement occurs when the constraint’s score is +INFINITY or -INFINITY. In such cases, if the constraint can’t be satisfied, then the rsc resource is not permitted to run. For score=INFINITY, this includes cases where the with-rsc resource is not active." msgstr "" #. Tag: para #, no-c-format -msgid "If you need resource1 to always run on the same machine as resource2, you would add the following constraint:" +msgid "If you need resource A to always run on the same machine as resource B, you would add the following constraint:" msgstr "" #. Tag: title #, no-c-format -msgid "An example colocation constraint" +msgid "Mandatory colocation constraint for two resources" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>" +msgid "<rsc_colocation id=\"colocate\" rsc=\"A\" with-rsc=\"B\" score=\"INFINITY\"/>" msgstr "" #. Tag: para #, no-c-format -msgid "Remember, because INFINITY was used, if resource2 can’t run on any of the cluster nodes (for whatever reason) then resource1 will not be allowed to run." +msgid "Remember, because INFINITY was used, if B can’t run on any of the cluster nodes (for whatever reason) then A will not be allowed to run. Whether A is running or not has no effect on B." msgstr "" #. Tag: para #, no-c-format -msgid "Alternatively, you may want the opposite… that resource1 cannot run on the same machine as resource2. In this case use score=\"-INFINITY\"" +msgid "Alternatively, you may want the opposite — that A cannot run on the same machine as B. In this case, use score=\"-INFINITY\"." msgstr "" #. Tag: title #, no-c-format -msgid "An example anti-colocation constraint" +msgid "Mandatory anti-colocation constraint for two resources" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<rsc_colocation id=\"anti-colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/>" +msgid "<rsc_colocation id=\"anti-colocate\" rsc=\"A\" with-rsc=\"B\" score=\"-INFINITY\"/>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Again, by specifying -INFINITY, the constraint is binding. So if the only place left to run is where B already is, then A may not run anywhere." msgstr "" #. Tag: para #, no-c-format -msgid "Again, by specifying -INFINTY, the constraint is binding. So if the only place left to run is where resource2 already is, then resource1 may not run anywhere." +msgid "As with INFINITY, B can run even if A is stopped. However, in this case A also can run if B is stopped, because it still meets the constraint of A and B 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 -INFINITY and less than INFINITY, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources." +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 -INFINITY and less than INFINITY, 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 "Like 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." +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 "An example advisory-only colocation constraint" +msgid "Advisory colocation constraint for two resources" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>" +msgid "<rsc_colocation id=\"colocate-maybe\" rsc=\"A\" with-rsc=\"B\" score=\"500\"/>" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Resource Sets" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Resource sets 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 "<resource_set id=\"resource-set-example\">\n" +" <resource_ref id=\"A\"/>\n" +" <resource_ref id=\"B\"/>\n" +" <resource_ref id=\"C\"/>\n" +"</resource_set>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Resource sets are valid inside rsc_location, rsc_order (see ), rsc_colocation (see ), and rsc_ticket (see ) 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 idResource Sets Resource Sets ConstraintsResource Setsid Resource Setsid id " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "sequential" +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 rsc_order and rsc_colocation. sequentialResource Sets Resource Sets ConstraintsResource Setssequential Resource Setssequential sequential " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "require-all" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Whether all members of the set must be active before continuing. Meaningful within rsc_order. require-allResource Sets Resource Sets ConstraintsResource Setsrequire-all Resource Setsrequire-all require-all " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "role" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Limit the effect of the constraint to the specified role. Meaningful within rsc_location, rsc_colocation and rsc_ticket. roleResource Sets Resource Sets ConstraintsResource Setsrole Resource Setsrole role " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Limit the effect of the constraint to the specified action. Meaningful within rsc_order. actionResource Sets Resource Sets ConstraintsResource Setsaction Resource Setsaction action " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Use a specific score for this set within the constraint. scoreResource Sets Resource Sets ConstraintsResource Setsscore Resource Setsscore score " 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 "<constraints>\n" " <rsc_order id=\"order-1\" first=\"A\" then=\"B\" />\n" " <rsc_order id=\"order-2\" first=\"B\" then=\"C\" />\n" " <rsc_order id=\"order-3\" first=\"C\" then=\"D\" />\n" "</constraints>" msgstr "" -#. Tag: title -#, no-c-format -msgid "Ordered Set" -msgstr "" - #. Tag: title #, no-c-format msgid "Visual representation of the four resources' start order for the above constraints" msgstr "" -#. Tag: phrase +#. Tag: title #, no-c-format -msgid "Ordered set" +msgid "Ordered Set" msgstr "" #. Tag: para #, no-c-format -msgid "To simplify this situation, there is an alternate format for ordering constraints:" +msgid "To simplify this situation, resource sets (see ) 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 "<constraints>\n" " <rsc_order id=\"order-1\">\n" " <resource_set id=\"ordered-set-example\" sequential=\"true\">\n" " <resource_ref id=\"A\"/>\n" " <resource_ref id=\"B\"/>\n" " <resource_ref id=\"C\"/>\n" " <resource_ref id=\"D\"/>\n" " </resource_set>\n" " </rsc_order>\n" "</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "Resource sets have the same ordering semantics as groups." +msgid "While the set-based format is not less verbose, it is significantly easier to get right and maintain." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "A group resource with the equivalent ordering rules" +msgid "If you use a higher-level tool, pay attention to how it exposes this functionality. Depending on the tool, creating a set A B may be equivalent to A then B, or B then A." msgstr "" -#. Tag: programlisting +#. Tag: title #, no-c-format -msgid "<group id=\"dummy\">\n" -" <primitive id=\"A\" .../>\n" -" <primitive id=\"B\" .../>\n" -" <primitive id=\"C\" .../>\n" -" <primitive id=\"D\" .../>\n" -"</group>" +msgid "Ordering Multiple Sets" 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. It can also be expanded to allow ordered sets of (un)ordered resources. In the example below, rscA and rscB can both start in parallel, as can rscC and rscD, however rscC and rscD can only start once both rscA and rscB are active." +msgid "The syntax can be expanded to allow ordered sets of (un)ordered resources. In the example below, A and B can both start in parallel, as can C and D, however C and D can only start once both A and B are active." msgstr "" #. Tag: title #, no-c-format msgid "Ordered sets of unordered resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_order id=\"order-1\">\n" " <resource_set id=\"ordered-set-1\" sequential=\"false\">\n" " <resource_ref id=\"A\"/>\n" " <resource_ref id=\"B\"/>\n" " </resource_set>\n" " <resource_set id=\"ordered-set-2\" sequential=\"false\">\n" " <resource_ref id=\"C\"/>\n" " <resource_ref id=\"D\"/>\n" " </resource_set>\n" " </rsc_order>\n" " </constraints>" msgstr "" #. Tag: title #, no-c-format -msgid "Two Sets of Unordered Resources" +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 sequential=\"true\") 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 "<constraints>\n" +" <rsc_order id=\"order-1\">\n" +" <resource_set id=\"ordered-set-1\" sequential=\"false\">\n" +" <resource_ref id=\"A\"/>\n" +" <resource_ref id=\"B\"/>\n" +" </resource_set>\n" +" <resource_set id=\"ordered-set-2\" sequential=\"true\">\n" +" <resource_ref id=\"C\"/>\n" +" <resource_ref id=\"D\"/>\n" +" </resource_set>\n" +" <resource_set id=\"ordered-set-3\" sequential=\"false\">\n" +" <resource_ref id=\"E\"/>\n" +" <resource_ref id=\"F\"/>\n" +" </resource_set>\n" +" </rsc_order>\n" +"</constraints>" msgstr "" #. Tag: title #, no-c-format -msgid "Visual representation of the start order for two ordered sets of unordered resources" +msgid "Visual representation of the start order for the three sets defined above" msgstr "" -#. Tag: phrase +#. Tag: para +#, no-c-format +msgid "An ordered set with sequential=false makes sense only if there is another set in the constraint. Otherwise, the constraint has no effect." +msgstr "" + +#. Tag: title #, no-c-format -msgid "Two ordered sets" +msgid "Resource Set OR Logic" msgstr "" #. Tag: para #, no-c-format -msgid "Of course either set — or both sets — of resources can also be internally ordered (by setting sequential=\"true\") and there is no limit to the number of sets that can be specified." +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, (A and B) then (C) then (D) then (E and F)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Say for example we want to change the first set, (A and B), to use \"OR\" logic so the sets look like this: (A or B) then (C) then (D) then (E and F). This functionality can be achieved through the use of the require-all option. This option defaults to TRUE which is why the \"AND\" logic is used by default. Setting require-all=false 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 "Advanced use of set ordering - Three ordered sets, two of which are internally unordered" +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 "<constraints>\n" " <rsc_order id=\"order-1\">\n" -" <resource_set id=\"ordered-set-1\" sequential=\"false\">\n" +" <resource_set id=\"ordered-set-1\" sequential=\"false\" require-all=\"false\">\n" " <resource_ref id=\"A\"/>\n" " <resource_ref id=\"B\"/>\n" " </resource_set>\n" " <resource_set id=\"ordered-set-2\" sequential=\"true\">\n" " <resource_ref id=\"C\"/>\n" " <resource_ref id=\"D\"/>\n" " </resource_set>\n" " <resource_set id=\"ordered-set-3\" sequential=\"false\">\n" " <resource_ref id=\"E\"/>\n" " <resource_ref id=\"F\"/>\n" " </resource_set>\n" " </rsc_order>\n" "</constraints>" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Three Resources Sets" +msgid "An ordered set with require-all=false makes sense only in conjunction with sequential=false. Think of it like this: sequential=false modifies the set to be an unordered set using \"AND\" logic by default, and adding require-all=false flips the unordered set’s \"AND\" logic to \"OR\" logic." msgstr "" #. Tag: title #, no-c-format -msgid "Visual representation of the start order for the three sets defined above" +msgid "Colocating Sets of Resources" msgstr "" -#. Tag: phrase +#. Tag: para #, no-c-format -msgid "Three ordered sets" +msgid "Another common situation is for an administrator to create a set of colocated resources." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Collocating Sets of Resources" +msgid "One way to do this would be to define a resource group (see ), but that cannot always accurately express the desired state." msgstr "" #. Tag: para #, no-c-format -msgid "Another common situation is for an administrator to create a set of collocated resources. Previously this was possible either by defining a resource group (See ) which could not always accurately express the design; or by defining each relationship as an individual constraint, causing a constraint explosion as the number of resources and combinations grew." +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 "A chain of collocated resources" +msgid "Chain of colocated resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" -" <rsc_colocation id=\"coloc-1\" rsc=\"B\" with-rsc=\"A\" score=\"INFINITY\"/>\n" +" <rsc_colocation id=\"coloc-1\" rsc=\"D\" with-rsc=\"C\" score=\"INFINITY\"/>\n" " <rsc_colocation id=\"coloc-2\" rsc=\"C\" with-rsc=\"B\" score=\"INFINITY\"/>\n" -" <rsc_colocation id=\"coloc-3\" rsc=\"D\" with-rsc=\"C\" score=\"INFINITY\"/>\n" +" <rsc_colocation id=\"coloc-3\" rsc=\"B\" with-rsc=\"A\" score=\"INFINITY\"/>\n" "</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "To make things easier, we allow an alternate form of colocation constraints using resource_sets. Just like the expanded version, a resource that can’t be active also prevents any resource that must be collocated with it from being active. For example, if B was not able to run, then both C (+and by inference +D) must also remain stopped." +msgid "To make things easier, resource sets (see ) 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 B is not able to run, then both C and by inference D must also remain stopped. Here is an example resource_set:" msgstr "" #. Tag: title #, no-c-format -msgid "The equivalent colocation chain expressed using resource_sets" +msgid "Equivalent colocation chain expressed using resource_set" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n" -" <resource_set id=\"collocated-set-example\" sequential=\"true\">\n" +" <resource_set id=\"colocated-set-example\" sequential=\"true\">\n" " <resource_ref id=\"A\"/>\n" " <resource_ref id=\"B\"/>\n" " <resource_ref id=\"C\"/>\n" " <resource_ref id=\"D\"/>\n" " </resource_set>\n" " </rsc_colocation>\n" "</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "Resource sets have the same colocation semantics as groups." -msgstr "" - -#. Tag: title -#, no-c-format -msgid "A group resource with the equivalent colocation rules" +msgid "If you use a higher-level tool, pay attention to how it exposes this functionality. Depending on the tool, creating a set A B may be equivalent to A with B, or B with A." msgstr "" #. Tag: para #, no-c-format -msgid "This notation can also be used in this context to tell the cluster that a set of resources must all be located with a common peer, but have no dependencies on each other. In this scenario, unlike the previous, B would be allowed to remain active even if A or C (or both) were inactive." +msgid "This notation can also be used to tell the cluster that a set of resources must all be located with a common peer, but have no dependencies on each other. In this scenario, unlike the previous, B would be allowed to remain active even if A or C (or both) were inactive." msgstr "" #. Tag: title #, no-c-format -msgid "Using colocation sets to specify a common peer." +msgid "Using colocated sets to specify a common peer" msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n" -" <resource_set id=\"collocated-set-1\" sequential=\"false\">\n" +" <resource_set id=\"colocated-set-1\" sequential=\"false\">\n" " <resource_ref id=\"A\"/>\n" " <resource_ref id=\"B\"/>\n" " <resource_ref id=\"C\"/>\n" " </resource_set>\n" -" <resource_set id=\"collocated-set-2\" sequential=\"true\">\n" +" <resource_set id=\"colocated-set-2\" sequential=\"true\">\n" " <resource_ref id=\"D\"/>\n" " </resource_set>\n" " </rsc_colocation>\n" "</constraints>" msgstr "" #. Tag: para #, no-c-format -msgid "Of course there is no limit to the number and size of the sets used. The only thing that matters is that in order for any member of set N to be active, all the members of set N+1 must also be active (and naturally on the same node); and if a set has sequential=\"true\", then in order for member M to be active, member M+1 must also be active. You can even specify the role in which the members of a set must be in using the set’s role attribute." +msgid "A colocated set with sequential=false 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 sequential=\"true\", then in order for one member of that set to be active, all members listed after it must also be active. You can even specify the role in which the members of a set must be in using the set’s role attribute." msgstr "" #. Tag: title #, no-c-format -msgid "A colocation chain where the members of the middle set have no inter-dependencies and the last has master status." +msgid "A colocation chain where the members of the middle set have no interdependencies and the last has master status." msgstr "" #. Tag: programlisting #, no-c-format msgid "<constraints>\n" " <rsc_colocation id=\"coloc-1\" score=\"INFINITY\" >\n" -" <resource_set id=\"collocated-set-1\" sequential=\"true\">\n" +" <resource_set id=\"colocated-set-1\" sequential=\"true\">\n" " <resource_ref id=\"A\"/>\n" " <resource_ref id=\"B\"/>\n" " </resource_set>\n" -" <resource_set id=\"collocated-set-2\" sequential=\"false\">\n" +" <resource_set id=\"colocated-set-2\" sequential=\"false\">\n" " <resource_ref id=\"C\"/>\n" " <resource_ref id=\"D\"/>\n" " <resource_ref id=\"E\"/>\n" " </resource_set>\n" -" <resource_set id=\"collocated-set-2\" sequential=\"true\" role=\"Master\">\n" +" <resource_set id=\"colocated-set-3\" sequential=\"true\" role=\"Master\">\n" " <resource_ref id=\"F\"/>\n" " <resource_ref id=\"G\"/>\n" " </resource_set>\n" " </rsc_colocation>\n" "</constraints>" msgstr "" -#. Tag: title -#, no-c-format -msgid "Another Three Resources Sets" -msgstr "" - #. Tag: title #, no-c-format msgid "Visual representation of a colocation chain where the members of the middle set have no inter-dependencies" msgstr "" -#. Tag: phrase +#. Tag: para #, no-c-format -msgid "Colocation chain" +msgid "Unlike ordered sets, colocated sets do not use the require-all option." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Intro.pot b/doc/Pacemaker_Explained/pot/Ch-Intro.pot index 15dfa38504..9c36266561 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Intro.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Intro.pot @@ -1,299 +1,284 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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." 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 I hope, however, that the concepts explained here make the functionality of these tools more easily understood. , precisely because they hide the XML." 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." msgstr "" #. Tag: para #, no-c-format -msgid "Although such guides exist, 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 "Although such guides exist, For example, see the Clusters from Scratch guide. 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." msgstr "" #. Tag: title #, no-c-format -msgid "What Is Pacemaker?" +msgid "What Is Pacemaker?" msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker is a cluster resource manager." +msgid "Pacemaker is a cluster resource manager, 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. nodes) and driven by prescribed rules." msgstr "" #. Tag: para #, no-c-format -msgid "It achieves maximum availability for your cluster services (aka. resources) 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 Corosync or Heartbeat." +msgid "It achieves maximum availability for your cluster services (a.k.a. resources) 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 Corosync or Heartbeat), and possibly by utilizing other parts of the overall cluster stack." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "For the goal of minimal downtime a term high availability was coined and together with its acronym, HA, is well-established in the sector. To differentiate this sort of clusters from high performance computing (HPC) ones, should a context require it (apparently, not the case in this document), using HA cluster is an option." msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker’s key features include:" msgstr "" #. Tag: para #, no-c-format msgid "Detection and recovery of node and service-level failures" msgstr "" #. Tag: para #, no-c-format msgid "Storage agnostic, no requirement for shared storage" msgstr "" #. Tag: para #, no-c-format msgid "Resource agnostic, anything that can be scripted can be clustered" msgstr "" #. Tag: para #, no-c-format -msgid "Supports STONITH for ensuring data integrity" +msgid "Supports fencing (also referred to as the STONITH acronym, deciphered later on) for ensuring data integrity" msgstr "" #. Tag: para #, no-c-format msgid "Supports large and small clusters" msgstr "" #. Tag: para #, no-c-format -msgid "Supports both quorate and resource driven clusters" +msgid "Supports both quorate and resource-driven clusters" msgstr "" #. Tag: para #, no-c-format -msgid "Supports practically any redundancy configuration" +msgid "Supports practically any redundancy configuration" 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 service ordering, colocation and anti-colocation" msgstr "" #. Tag: para #, no-c-format -msgid "Support for advanced services type" +msgid "Support for advanced service types" msgstr "" #. Tag: para #, no-c-format msgid "Clones: for services which need to be active on multiple nodes" msgstr "" #. Tag: para #, no-c-format -msgid "Multi-state: for services with multiple modes (eg. master/slave, primary/secondary)" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Types of Pacemaker Clusters" +msgid "Multi-state: for services with multiple modes (e.g. master/slave, primary/secondary)" msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker makes no assumptions about your environment, this allows it to support practically any redundancy configuration including Active/Active, Active/Passive, N+1, N+M, N-to-1 and N-to-N." +msgid "Unified, scriptable cluster management tools" msgstr "" #. Tag: title #, no-c-format -msgid "Active/Passive Redundancy" +msgid "Pacemaker Architecture" msgstr "" #. Tag: para #, no-c-format -msgid "Two-node Active/Passive clusters using Pacemaker and DRBD are a cost-effective solution for many High Availability situations." -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Shared Failover" +msgid "At the highest level, the cluster is made up of three pieces:" 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" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "N to N Redundancy" +msgid "Non-cluster-aware components. 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." 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 "Pacemaker Architecture" +msgid "Resource management. 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." msgstr "" #. Tag: para #, no-c-format -msgid "At the highest level, the cluster is made up of three pieces:" +msgid "Low-level infrastructure. Projects like Corosync, CMAN and Heartbeat provide reliable messaging, membership and quorum information about the cluster." msgstr "" #. Tag: para #, no-c-format -msgid "Core cluster infrastructure providing messaging and membership functionality (illustrated in red)" +msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems. 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. " msgstr "" #. Tag: para #, no-c-format -msgid "Non-cluster aware components (illustrated in green)." +msgid "Due to past standardization within the cluster filesystem community, cluster filesystems make use of a common distributed lock manager, which makes use of Corosync for its messaging and membership capabilities (which nodes are up/down) and Pacemaker for fencing services." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "In a Pacemaker cluster, these pieces include not only the scripts that knows how to start, stop and monitor resources, but also a local daemon that masks the differences between the different standards these scripts implement." +msgid "The Pacemaker Stack" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "A brain (illustrated in blue)" +msgid "Internal Components" msgstr "" #. Tag: para #, no-c-format -msgid "This component processes and reacts to events from the cluster (nodes leaving or joining) and resources (eg. monitor failures) as well as configuration changes from the administrator. In response to all of these events, Pacemaker will compute the ideal state of the cluster and plot a path to achieve it. This may include moving resources, stopping nodes and even forcing nodes offline with remote power switches." +msgid "Pacemaker itself is composed of five key components:" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Conceptual Stack Overview" +msgid "Cluster Information Base (CIB)" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Conceptual overview of the cluster stack" +msgid "Cluster Resource Management daemon (CRMd)" msgstr "" #. Tag: para #, no-c-format -msgid "When combined with Corosync, Pacemaker also supports popular open source cluster filesystems. footnote:[ 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." +msgid "Local Resource Management daemon (LRMd)" msgstr "" #. Tag: para #, no-c-format -msgid "Technically it would be possible for them to support Heartbeat as well, however there seems little interest in this. ]" +msgid "Policy Engine (PEngine or PE)" msgstr "" #. Tag: para #, no-c-format -msgid "Due to recent standardization within the cluster filesystem community, they make use of a common distributed lock manager which makes use of Corosync for its messaging capabilities and Pacemaker for its membership (which nodes are up/down) and fencing services." +msgid "Fencing daemon (STONITHd)" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "The Pacemaker stack when running on Corosync" +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." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Internal Components" +msgid "This list of instructions is then fed to the Designated Controller (DC). 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." msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker itself is composed of four key components (illustrated below in the same color scheme as the previous diagram):" +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)." msgstr "" #. Tag: para #, no-c-format -msgid "CIB (aka. Cluster Information Base)" +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." msgstr "" #. Tag: para #, no-c-format -msgid "CRMd (aka. Cluster Resource Management daemon)" +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." msgstr "" #. Tag: para #, no-c-format -msgid "PEngine (aka. PE or Policy Engine)" +msgid "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head, a recommended practice that misbehaving node is best to be promptly fenced (shut off, cut from shared resources or otherwise immobilized), and is usually implemented with a remote power switch." msgstr "" #. Tag: para #, no-c-format -msgid "STONITHd" +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." msgstr "" #. Tag: title #, no-c-format -msgid "Subsystems of a Pacemaker cluster" +msgid "Types of Pacemaker Clusters" 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 "Pacemaker makes no assumptions about your environment. This allows it to support practically any redundancy configuration including Active/Active, Active/Passive, N+1, N+M, N-to-1 and N-to-N." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "This list of instructions is then fed to the DC (Designated Controller). 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 "Active/Passive Redundancy" msgstr "" #. Tag: para #, no-c-format -msgid "The DC carries out PEngine’s instructions in the required order by passing them to either the LRMd (Local Resource Management daemon) or CRMd peers on other nodes via the cluster messaging infrastructure (which in turn passes them on to their LRMd process)." +msgid "Two-node Active/Passive clusters using Pacemaker and DRBD are a cost-effective solution for many High Availability situations." msgstr "" -#. Tag: para +#. Tag: title #, 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 "Shared Failover" 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 "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." msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and is usually implemented with a remote power switch." +msgid "N to N Redundancy" 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 "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 "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot new file mode 100644 index 0000000000..d9adc6dfd9 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot @@ -0,0 +1,458 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 Cluster Ticket Registry (CTR)." +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 tickets 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 rsc_ticket 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 site quorum, i.e. the permission to manage/own resources associated with that site. (One can also think of the current have-quorum 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: true (the site has the ticket) or false (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 false." +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 Dead Man Dependency 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 loss-policy=\"fence\" in rsc_ticket 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 not 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 rsc_ticket constraint lets you specify the resources depending on a certain ticket. Together with the constraint, you can set a loss-policy that defines what should happen to the respective resources if the ticket is revoked." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The attribute loss-policy can have the following values:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "fence: Fence the nodes that are running the relevant resources." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "stop: Stop the relevant resources." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "freeze: Do nothing to the relevant resources." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "demote: Demote relevant resources that are running in master mode to slave mode." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Constraint that fences node if ticketA is revoked" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" ticket=\"ticketA\" loss-policy=\"fence\"/>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The example above creates a constraint with the ID rsc1-req-ticketA. It defines that the resource rsc1 depends on ticketA and that the node running the resource should be fenced if ticketA is revoked." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If resource rsc1 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 ticketA. With the following configuration, rsc1 will be demoted to slave mode if ticketA is revoked:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Constraint that demotes rsc1 if ticketA is revoked" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" rsc-role=\"Master\" ticket=\"ticketA\" loss-policy=\"demote\"/>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "You can create multiple rsc_ticket constraints to let multiple resources depend on the same ticket. However, rsc_ticket also supports resource sets (see ), so one can easily list all the resources in one rsc_ticket constraint instead." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Ticket constraint for multiple resources" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_ticket id=\"resources-dep-ticketA\" ticket=\"ticketA\" loss-policy=\"fence\">\n" +" <resource_set id=\"resources-dep-ticketA-0\" role=\"Started\">\n" +" <resource_ref id=\"rsc1\"/>\n" +" <resource_ref id=\"group1\"/>\n" +" <resource_ref id=\"clone1\"/>\n" +" </resource_set>\n" +" <resource_set id=\"resources-dep-ticketA-1\" role=\"Master\">\n" +" <resource_ref id=\"ms1\"/>\n" +" </resource_set>\n" +"</rsc_ticket>" +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 rsc_ticket 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 ticketA." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Referencing resource templates in rsc_ticket 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 rsc_ticket." +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 crm_ticket 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 crm_ticket 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 Booth here as an example of software that can be used with pacemaker as a Cluster Ticket Registry. Booth implements the Raft 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 arbitrators runs the Booth daemon boothd." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "An arbitrator 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 "Boothd 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 loss-policy you set within the rsc_ticket 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 booth command-line tool. After you have initially granted a ticket to a site, boothd will take over and manage the ticket automatically." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The booth command-line tool can be used to grant, list, or revoke tickets and can be run on any machine where boothd is running. If you are managing tickets via Booth, use only booth for manual intervention, not crm_ticket. 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 rsc_ticket 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 loss-policy=\"fence\", 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 standby 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 "SUSE’s Geo Clustering quick start" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Booth" +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Nodes.pot b/doc/Pacemaker_Explained/pot/Ch-Nodes.pot index c0128722fc..fc613d28f2 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Nodes.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Nodes.pot @@ -1,275 +1,384 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 cluster node entry" +msgid "Example Heartbeat cluster node entry" msgstr "" #. Tag: programlisting #, no-c-format msgid "<node id=\"1186dc9a-324d-425a-966e-d757e693dc86\" uname=\"pcmk-1\" type=\"normal\"/>" msgstr "" +#. Tag: title +#, no-c-format +msgid "Example Corosync cluster node entry" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<node id=\"101\" uname=\"pcmk-1\" type=\"normal\"/>" +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 crm_uuid tool to read an existing UUID or define a value before the cluster starts." +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 uname -n. This can be problematic for services that require the uname -n 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 "In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However one can use the crm_uuid tool to read an existing UUID or define a value before the cluster starts." +msgid "The value stored in corosync.conf under ring0_addr in the nodelist, if it does not contain an IP address; otherwise" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The value stored in corosync.conf under name in the nodelist; otherwise" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The value of uname -n" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Pacemaker provides the crm_node -n command which displays the name used by a running cluster." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If a Corosync nodelist is used, crm_node --name-for-id number is also available to display the name used by the node with the corosync nodeid of number, for example: crm_node --name-for-id 2." msgstr "" #. Tag: title #, no-c-format -msgid "Describing a Cluster Node" +msgid "Node Attributes" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " Nodeattribute attribute Node attributes are a special type of option (name-value pair) that applies to a node object." msgstr "" #. Tag: para #, no-c-format -msgid " Nodeattribute attribute Beyond the basic definition of a node the administrator can also 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 ." +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 ." msgstr "" #. Tag: para #, no-c-format msgid "Node attributes can be specified ahead of time or populated later, when the cluster is running, using crm_attribute." 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 "The result of using crm_attribute to specify which kernel pcmk-1 is running" +msgid "Result of using crm_attribute to specify which kernel pcmk-1 is running" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r`" +msgid "# crm_attribute --type nodes --node pcmk-1 --name kernel --update $(uname -r)" msgstr "" #. Tag: programlisting #, no-c-format -msgid "<node uname=\"pcmk-1\" type=\"normal\" id=\"1186dc9a-324d-425a-966e-d757e693dc86\">\n" -" <instance_attributes id=\"nodes-1186dc9a-324d-425a-966e-d757e693dc86\">\n" -" <nvpair id=\"kernel-1186dc9a-324d-425a-966e-d757e693dc86\" name=\"kernel\" value=\"2.6.16.46-0.4-default\"/>\n" +msgid "<node uname=\"pcmk-1\" type=\"normal\" id=\"101\">\n" +" <instance_attributes id=\"nodes-101\">\n" +" <nvpair id=\"nodes-101-kernel\" name=\"kernel\" value=\"3.10.0-123.13.2.el7.x86_64\"/>\n" " </instance_attributes>\n" "</node>" msgstr "" #. Tag: para #, no-c-format -msgid "A simpler way to determine the current value of an attribute is to use crm_attribute command again:" +msgid "Rather than having to read the XML, a simpler way to determine the current value of an attribute is to use crm_attribute again:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" +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 --type nodes 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 --type status." +msgid "By specifying --type nodes 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 --type status." msgstr "" #. Tag: title #, no-c-format -msgid "Adding a New Cluster Node" +msgid "Managing Nodes in a Corosync-Based Cluster" msgstr "" #. Tag: title #, no-c-format -msgid "Corosync" +msgid "Adding a New Corosync Node" msgstr "" #. Tag: para #, no-c-format -msgid " CorosyncAdd Cluster Node Add Cluster Node Add Cluster NodeCorosync Corosync Adding a new node is as simple as installing Corosync and Pacemaker, and copying /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node’s IP address." +msgid " CorosyncAdd Cluster Node Add Cluster Node Add Cluster NodeCorosync Corosync " msgstr "" #. Tag: para #, no-c-format -msgid "If a log message containing \"Invalid digest\" appears from Corosync, the keys are not consistent between the machines." +msgid "To add a new node:" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Heartbeat" +msgid "Install Corosync and Pacemaker on the new host." msgstr "" #. Tag: para #, no-c-format -msgid " HeartbeatAdd Cluster Node Add Cluster Node Add Cluster NodeHeartbeat Heartbeat Provided you specified autojoin any in ha.cf, adding a new node is as simple as installing heartbeat and copying ha.cf and authkeys from an existing node." +msgid "Copy /etc/corosync/corosync.conf and /etc/corosync/authkey (if it exists) from an existing node. You may need to modify the mcastaddr option to match the new node’s IP address." msgstr "" #. Tag: para #, no-c-format -msgid "If you don’t want to use autojoin, then after setting up ha.cf and authkeys, you must use the hb_addnode command before starting the new node." +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 Cluster Node" +msgid "Removing a Corosync Node" msgstr "" #. Tag: para #, no-c-format -msgid " CorosyncRemove Cluster Node Remove Cluster Node Remove Cluster NodeCorosync Corosync Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below)." +msgid " CorosyncRemove Cluster Node Remove Cluster Node Remove Cluster NodeCorosync Corosync " msgstr "" #. Tag: para #, no-c-format -msgid "On the host to be removed:" +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 (pcmk-1 in the example below)." msgstr "" #. Tag: para #, no-c-format -msgid "Find and record the node’s Corosync id: crm_node -i" +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, pcs cluster stop if you are using pcs for cluster management, or service corosync stop on a host using corosync 1.x with the pacemaker plugin." msgstr "" #. Tag: para #, no-c-format -msgid "Stop the cluster: /etc/init.d/corosync stop" +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 "Next, from one of the remaining active cluster nodes:" +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 "Tell the cluster to forget about the removed host:" +msgid " CorosyncReplace Cluster Node Replace Cluster Node Replace Cluster NodeCorosync Corosync " msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# crm_node -R $COROSYNC_ID" +msgid "To replace an existing cluster node:" msgstr "" #. Tag: para #, no-c-format -msgid "Only now is it safe to delete the node from the CIB with:" +msgid "Make sure the old node is completely stopped." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"_pcmk-1_\"/>'\n" -"# cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"_pcmk-1_\"/>'" +msgid "Give the new machine the same hostname and IP address as the old one." msgstr "" #. Tag: para #, no-c-format -msgid " HeartbeatRemove Cluster Node Remove Cluster Node Remove Cluster NodeHeartbeat Heartbeat Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution." +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 "First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below). To do this, shut down heartbeat on the node and then, from one of the remaining active cluster nodes, run:" +msgid " HeartbeatAdd Cluster Node Add Cluster Node Add Cluster NodeHeartbeat Heartbeat " msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# hb_delnode pcmk-1" +msgid "Install heartbeat and pacemaker on the new host." msgstr "" #. Tag: para #, no-c-format -msgid "Only then is it safe to delete the node from the CIB with:" +msgid "Copy ha.cf and authkeys from an existing node." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# cibadmin --delete --obj_type nodes --crm_xml '<node uname=\"pcmk-1\"/>'\n" -"# cibadmin --delete --obj_type status --crm_xml '<node_state uname=\"pcmk-1\"/>'" +msgid "If you do not use autojoin any in ha.cf, 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 "Replacing a Cluster Node" +msgid "Removing a Heartbeat Node" msgstr "" #. Tag: para #, no-c-format -msgid " CorosyncReplace Cluster Node Replace Cluster Node Replace Cluster NodeCorosync Corosync The five-step guide to replacing an existing cluster node:" +msgid " HeartbeatRemove Cluster Node Remove Cluster Node Remove Cluster NodeHeartbeat Heartbeat " msgstr "" #. Tag: para #, no-c-format -msgid "Make sure the old node is completely stopped" +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 "Give the new machine the same hostname and IP address as the old one" +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 "Install the cluster software :-)" +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 "Copy /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) to the new node" +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 "Start the new cluster node" +msgid " HeartbeatReplace Cluster Node Replace Cluster Node Replace Cluster NodeHeartbeat Heartbeat To replace an existing cluster node:" msgstr "" #. Tag: para #, no-c-format -msgid " HeartbeatReplace Cluster Node Replace Cluster Node Replace Cluster NodeHeartbeat Heartbeat The seven-step guide to replacing an existing cluster node:" +msgid "Give the new machine the same hostname as the old one." msgstr "" #. Tag: para #, no-c-format -msgid "Give the new machine the same hostname as the old one" +msgid "Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache." msgstr "" #. Tag: para #, no-c-format -msgid "Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache" +msgid "Install the cluster software." msgstr "" #. Tag: para #, no-c-format -msgid "Install the cluster software" +msgid "Copy ha.cf and authkeys to the new node." msgstr "" #. Tag: para #, no-c-format -msgid "Copy ha.cf and authkeys to the new node" +msgid "On the new node, populate its UUID using crm_uuid -w and the UUID obtained earlier." msgstr "" #. Tag: para #, no-c-format -msgid "On the new node, populate it’s UUID using crm_uuid -w and the UUID from step 2" +msgid "Start the new cluster node." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Notifications.pot b/doc/Pacemaker_Explained/pot/Ch-Notifications.pot new file mode 100644 index 0000000000..0e0fed996f --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Notifications.pot @@ -0,0 +1,233 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Receiving Notification for Cluster Events" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " ResourceNotification Notification " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A Pacemaker cluster is an event-driven system. In this context, an event might be a resource failure or a configuration change, among others." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The ocf:pacemaker:ClusterMon resource can monitor the cluster status and trigger alerts on each cluster event. This resource runs crm_mon in the background at regular (configurable) intervals and uses crm_mon capabilities to trigger emails (SMTP), SNMP traps or external programs (via the extra_options parameter)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Depending on your system settings and compilation settings, SNMP or email alerts might be unavailable. Check the output of crm_mon --help to see whether these options are available to you. In any case, executing an external agent will always be available, and you can use this agent to send emails, SNMP traps or whatever action you develop." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring SNMP Notifications" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " ResourceNotificationSNMP NotificationSNMP SNMP " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Requires an IP to send SNMP traps to, and an SNMP community string. The Pacemaker MIB is provided with the source, and is typically installed in /usr/share/snmp/mibs/PCMK-MIB.txt." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "This example uses snmphost.example.com as the SNMP IP and public as the community string:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring ClusterMon to send SNMP traps" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<clone id=\"ClusterMon-clone\">\n" +" <primitive class=\"ocf\" id=\"ClusterMon-SNMP\" provider=\"pacemaker\" type=\"ClusterMon\">\n" +" <instance_attributes id=\"ClusterMon-instance_attributes\">\n" +" <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" +" <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" +" <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-S snmphost.example.com -C public\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +"</clone>" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring Email Notifications" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " ResourceNotificationSMTP NotificationSMTP SMTP " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Requires the recipient e-mail address. You can also optionally configure the sender e-mail address, the hostname of the SMTP relay, and a prefix string for the subject line." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring ClusterMon to send email alerts" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<clone id=\"ClusterMon-clone\">\n" +" <primitive class=\"ocf\" id=\"ClusterMon-SMTP\" provider=\"pacemaker\" type=\"ClusterMon\">\n" +" <instance_attributes id=\"ClusterMon-instance_attributes\">\n" +" <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" +" <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" +" <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-T pacemaker@example.com -F pacemaker@node2.example.com -P PACEMAKER -H mail.example.com\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +"</clone>" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring Notifications via External-Agent" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Requires a program (external-agent) to run when resource operations take place, and an external-recipient (IP address, email address, URI). When triggered, the external-agent is fed with dynamically filled environment variables describing precisely the cluster event that occurred. By making smart usage of these variables in your external-agent code, you can trigger any action." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring ClusterMon to execute an external-agent" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<clone id=\"ClusterMon-clone\">\n" +" <primitive class=\"ocf\" id=\"ClusterMon\" provider=\"pacemaker\" type=\"ClusterMon\">\n" +" <instance_attributes id=\"ClusterMon-instance_attributes\">\n" +" <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" +" <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" +" <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-E /usr/local/bin/example.sh -e 192.168.12.1\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +"</clone>" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Environment Variables Passed to the External Agent" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment Variable" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_recipient" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The static external-recipient from the resource definition. Environment VariableCRM_notify_recipient CRM_notify_recipient " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The node on which the status change happened. Environment VariableCRM_notify_node CRM_notify_node " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_rsc" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The name of the resource that changed the status. Environment VariableCRM_notify_rsc CRM_notify_rsc " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_task" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The operation that caused the status change. Environment VariableCRM_notify_task CRM_notify_task " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_desc" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The textual output relevant error code of the operation (if any) that caused the status change. Environment VariableCRM_notify_desc CRM_notify_desc " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_rc" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The return code of the operation. Environment VariableCRM_notify_rc CRM_notify_rc " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_target_rc" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The expected return code of the operation. Environment VariableCRM_notify_target_rc CRM_notify_target_rc " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_notify_status" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The numerical representation of the status of the operation. Environment VariableCRM_notify_target_rc CRM_notify_target_rc " +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Options.pot b/doc/Pacemaker_Explained/pot/Ch-Options.pot index 93a5c84f28..0c64043489 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Options.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Options.pot @@ -1,504 +1,726 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 Options" +msgid "Cluster-Wide Configuration" msgstr "" #. Tag: title #, no-c-format -msgid "Special Options" +msgid "CIB Properties" msgstr "" #. Tag: para #, no-c-format -msgid "The reason for these fields to be placed at the top level instead of with the rest of cluster options 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 "Certain settings are defined by CIB properties (that is, attributes of the cib tag) rather than with the rest of the cluster configuration in the configuration section." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Configuration Version" +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 " Configuration VersionCluster Cluster ClusterOptionConfiguration Version OptionConfiguration Version Configuration Version " +msgid "admin_epoch" msgstr "" #. Tag: para #, no-c-format -msgid "When a node joins the cluster, the cluster will perform a check to see who has the best configuration based on the fields below. It then asks the node with the highest (admin_epoch, epoch, num_updates) tuple to replace the configuration on all the nodes - which makes setting them, and setting them correctly, very important." +msgid " Configuration VersionCluster Cluster ClusterOptionConfiguration Version OptionConfiguration Version Configuration Version admin_epochCluster Option Cluster Option ClusterOptionadmin_epoch Optionadmin_epoch admin_epoch 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 (admin_epoch, epoch, num_updates) tuple to replace the configuration on all the nodes — which makes setting them, and setting them correctly, very important. admin_epoch is never modified by the cluster; you can use this to make the configurations on any inactive nodes obsolete. Never set this value to zero. 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: title +#. Tag: para #, no-c-format -msgid "Configuration Version Properties" +msgid "epoch" msgstr "" -#. Tag: entry +#. Tag: para #, no-c-format -msgid "Field" +msgid " epochCluster Option Cluster Option ClusterOptionepoch Optionepoch epoch The cluster increments this every time the configuration is updated (usually by the administrator)." msgstr "" -#. Tag: entry +#. Tag: para #, no-c-format -msgid "Description" +msgid "num_updates" msgstr "" #. Tag: para #, no-c-format -msgid "admin_epoch" +msgid " num_updatesCluster Option Cluster Option ClusterOptionnum_updates Optionnum_updates num_updates 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: para #, no-c-format -msgid " admin_epochCluster Option Cluster Option ClusterOptionadmin_epoch Optionadmin_epoch admin_epoch Never modified by the cluster. Use this to make the configurations on any inactive nodes obsolete." +msgid "validate-with" msgstr "" #. Tag: para #, no-c-format -msgid "Never set this value to zero, in such cases the cluster cannot tell the difference between your configuration and the \"empty\" one used when nothing is found on disk." +msgid " validate-withCluster Option Cluster Option ClusterOptionvalidate-with Optionvalidate-with validate-with Determines the type of XML validation that will be done on the configuration. If set to none, 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: para #, no-c-format -msgid "epoch" +msgid "cib-last-written" msgstr "" #. Tag: para #, no-c-format -msgid " epochCluster Option Cluster Option ClusterOptionepoch Optionepoch epoch Incremented every time the configuration is updated (usually by the admin)" +msgid " cib-last-writtenCluster Property Cluster Property ClusterPropertycib-last-written Propertycib-last-written cib-last-written Indicates when the configuration was last written to disk. Maintained by the cluster; for informational purposes only." msgstr "" #. Tag: para #, no-c-format -msgid "num_updates" +msgid "have-quorum" msgstr "" #. Tag: para #, no-c-format -msgid " num_updatesCluster Option Cluster Option ClusterOptionnum_updates Optionnum_updates num_updates Incremented every time the configuration or status is updated (usually by the cluster)" +msgid " have-quorumCluster Property Cluster Property ClusterPropertyhave-quorum Propertyhave-quorum have-quorum Indicates if the cluster has quorum. If false, this may mean that the cluster cannot start resources or fence other nodes (see no-quorum-policy below). Maintained by the cluster." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Other Fields" +msgid "dc-uuid" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " dc-uuidCluster Property Cluster Property ClusterPropertydc-uuid Propertydc-uuid dc-uuid 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 "Properties Controlling Validation" +msgid "Working with CIB Properties" msgstr "" #. Tag: para #, no-c-format -msgid "validate-with" +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 admin_epoch, one should use:" +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "# cibadmin --modify --crm_xml '<cib admin_epoch=\"42\"/>'" msgstr "" #. Tag: para #, no-c-format -msgid " validate-withCluster Option Cluster Option ClusterOptionvalidate-with Optionvalidate-with validate-with Determines the type of validation being done on the configuration. If set to \"none\", 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 "A complete set of CIB properties will look something like this:" msgstr "" #. Tag: title #, no-c-format -msgid "Fields Maintained by the Cluster" +msgid "Attributes set for a cib object" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<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\">" msgstr "" #. Tag: title #, no-c-format -msgid "Properties Maintained by the Cluster" +msgid "Cluster Options" msgstr "" #. Tag: para #, no-c-format -msgid "cib-last-written" +msgid "Cluster options, as you might expect, control how the cluster behaves when confronted with certain situations." msgstr "" #. Tag: para #, no-c-format -msgid " cib-last-writtenCluster Property Cluster Property ClusterPropertycib-last-written Propertycib-last-written cib-last-written Indicates when the configuration was last written to disk. Informational purposes only." +msgid "They are grouped into sets within the crm_config section, and, in advanced configurations, there may be more than one set. (This will be described later in the section on 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 "dc-uuid" +msgid "You can obtain an up-to-date list of cluster options, including their default values, by running the man pengine and man crmd commands." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Option" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Default" msgstr "" #. Tag: para #, no-c-format -msgid " dc-uuidCluster Property Cluster Property ClusterPropertydc-uuid Propertydc-uuid dc-uuid Indicates which cluster node is the current leader. Used by the cluster when placing resources and determining the order of some events." +msgid "dc-version" msgstr "" #. Tag: para #, no-c-format -msgid "have-quorum" +msgid " dc-versionCluster Property Cluster Property ClusterPropertydc-version Propertydc-version dc-version 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 " have-quorumCluster Property Cluster Property ClusterPropertyhave-quorum Propertyhave-quorum have-quorum Indicates if the cluster has quorum. If false, this may mean that the cluster cannot start resources or fence other nodes. See no-quorum-policy below." +msgid "cluster-infrastructure" msgstr "" #. Tag: para #, no-c-format -msgid "Note that although these fields can be written to by the admin, in most cases the cluster will overwrite any values specified by the admin with the \"correct\" ones. To change the admin_epoch, for example, one would use:" +msgid " cluster-infrastructureCluster Property Cluster Property ClusterPropertycluster-infrastructure Propertycluster-infrastructure cluster-infrastructure The messaging stack on which Pacemaker is currently running. Determined automatically by the cluster. Used for informational and diagnostic purposes." msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "# cibadmin --modify --crm_xml '<cib admin_epoch=\"42\"/>'" +msgid "expected-quorum-votes" msgstr "" #. Tag: para #, no-c-format -msgid "A complete set of fields will look something like this:" +msgid " expected-quorum-votesCluster Property Cluster Property ClusterPropertyexpected-quorum-votes Propertyexpected-quorum-votes expected-quorum-votes 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: title +#. Tag: para #, no-c-format -msgid "An example of the fields set for a cib object" +msgid "no-quorum-policy" msgstr "" -#. Tag: programlisting +#. Tag: para #, no-c-format -msgid "<cib have-quorum=\"true\" validate-with=\"pacemaker-1.0\"\n" -" admin_epoch=\"1\" epoch=\"12\" num_updates=\"65\"\n" -" dc-uuid=\"ea7d39f4-3b94-4cfa-ba7a-952956daabee\">" +msgid "stop" msgstr "" #. Tag: para #, no-c-format -msgid "Cluster options, as you might expect, control how the cluster behaves when confronted with certain situations." +msgid " no-quorum-policyCluster Option Cluster Option ClusterOptionno-quorum-policy Optionno-quorum-policy no-quorum-policy What to do when the cluster does not have quorum. Allowed values:" msgstr "" #. Tag: para #, no-c-format -msgid "They are grouped into sets and, in advanced configurations, there may be more than one. This will be described later in the section on where we will show how to have the cluster use different sets of options during working hours (when downtime is usually to be avoided at all costs) than it does during the weekends (when resources can be moved to the their preferred hosts without bothering end users) For now we will describe the simple case where each option is present at most once." +msgid "ignore: continue all resource management" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Available Cluster Options" +msgid "freeze: continue resource management, but don’t recover resources from nodes not in the affected partition" msgstr "" -#. Tag: entry +#. Tag: para #, no-c-format -msgid "Option" +msgid "stop: stop all resources in the affected cluster partition" msgstr "" -#. Tag: entry +#. Tag: para #, no-c-format -msgid "Default" +msgid "suicide: fence all nodes in the affected cluster partition" msgstr "" #. Tag: para #, no-c-format msgid "batch-limit" msgstr "" #. Tag: para #, no-c-format msgid "30" msgstr "" #. Tag: para #, no-c-format -msgid " batch-limitCluster Option Cluster Option ClusterOptionbatch-limit Optionbatch-limit batch-limit The number of jobs that the TE is allowed to execute in parallel. The \"correct\" value will depend on the speed and load of your network and cluster nodes." +msgid " batch-limitCluster Option Cluster Option ClusterOptionbatch-limit Optionbatch-limit batch-limit 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." msgstr "" #. Tag: para #, no-c-format msgid "migration-limit" msgstr "" #. Tag: para #, no-c-format -msgid "-1 (unlimited)" +msgid "-1" msgstr "" #. Tag: para #, no-c-format -msgid " migration-limitCluster Option Cluster Option ClusterOptionmigration-limit Optionmigration-limit migration-limit The number of migration jobs that the TE is allowed to execute in parallel on a node." +msgid " migration-limitCluster Option Cluster Option ClusterOptionmigration-limit Optionmigration-limit migration-limit 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 "no-quorum-policy" +msgid "symmetric-cluster" msgstr "" #. Tag: para #, no-c-format -msgid "stop" +msgid "TRUE" msgstr "" #. Tag: para #, no-c-format -msgid " no-quorum-policyCluster Option Cluster Option ClusterOptionno-quorum-policy Optionno-quorum-policy no-quorum-policy What to do when the cluster does not have quorum. Allowed values:" +msgid " symmetric-clusterCluster Option Cluster Option ClusterOptionsymmetric-cluster Optionsymmetric-cluster symmetric-cluster Can all resources run on any node by default?" msgstr "" #. Tag: para #, no-c-format -msgid "* ignore - continue all resource management" +msgid "stop-all-resources" msgstr "" #. Tag: para #, no-c-format -msgid "* freeze - continue resource management, but don’t recover resources from nodes not in the affected partition" +msgid "FALSE" msgstr "" #. Tag: para #, no-c-format -msgid "* stop - stop all resources in the affected cluster partition" +msgid " stop-all-resourcesCluster Option Cluster Option ClusterOptionstop-all-resources Optionstop-all-resources stop-all-resources Should the cluster stop all resources?" msgstr "" #. Tag: para #, no-c-format -msgid "* suicide - fence all nodes in the affected cluster partition" +msgid "stop-orphan-resources" msgstr "" #. Tag: para #, no-c-format -msgid "symmetric-cluster" +msgid " stop-orphan-resourcesCluster Option Cluster Option ClusterOptionstop-orphan-resources Optionstop-orphan-resources stop-orphan-resources Should deleted resources be stopped?" msgstr "" #. Tag: para #, no-c-format -msgid "TRUE" +msgid "stop-orphan-actions" msgstr "" #. Tag: para #, no-c-format -msgid " symmetric-clusterCluster Option Cluster Option ClusterOptionsymmetric-cluster Optionsymmetric-cluster symmetric-cluster Can all resources run on any node by default?" +msgid " stop-orphan-actionsCluster Option Cluster Option ClusterOptionstop-orphan-actions Optionstop-orphan-actions stop-orphan-actions Should deleted actions be cancelled?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "start-failure-is-fatal" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " start-failure-is-fatalCluster Option Cluster Option ClusterOptionstart-failure-is-fatal Optionstart-failure-is-fatal start-failure-is-fatal 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 to try starting on the same node again based on the resource’s current failure count and migration-threshold (see )." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "enable-startup-probes" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " enable-startup-probesCluster Option Cluster Option ClusterOptionenable-startup-probes Optionenable-startup-probes enable-startup-probes Should the cluster check for active resources during startup?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "maintenance-mode" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " maintenance-modeCluster Option Cluster Option ClusterOptionmaintenance-mode Optionmaintenance-mode maintenance-mode Should the cluster refrain from monitoring, starting and stopping resources?" msgstr "" #. Tag: para #, no-c-format msgid "stonith-enabled" msgstr "" #. Tag: para #, no-c-format msgid " stonith-enabledCluster Option Cluster Option ClusterOptionstonith-enabled Optionstonith-enabled stonith-enabled 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 also." +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 data loss if the unresponsive node still accesses shared storage, for example). See also the requires meta-attribute in ." msgstr "" #. Tag: para #, no-c-format msgid "stonith-action" msgstr "" #. Tag: para #, no-c-format msgid "reboot" msgstr "" #. Tag: para #, no-c-format -msgid " stonith-actionCluster Option Cluster Option ClusterOptionstonith-action Optionstonith-action stonith-action Action to send to STONITH device. Allowed values: reboot, off. The value poweroff is also allowed, but is only used for legacy devices." +msgid " stonith-actionCluster Option Cluster Option ClusterOptionstonith-action Optionstonith-action stonith-action Action to send to STONITH device. Allowed values are reboot and off. The value poweroff is also allowed, but is only used for legacy devices." msgstr "" #. Tag: para #, no-c-format -msgid "cluster-delay" +msgid "stonith-timeout" msgstr "" #. Tag: para #, no-c-format msgid "60s" msgstr "" #. Tag: para #, no-c-format -msgid " cluster-delayCluster Option Cluster Option ClusterOptioncluster-delay Optioncluster-delay cluster-delay Round trip delay over the network (excluding action execution). The \"correct\" value will depend on the speed and load of your network and cluster nodes." +msgid " stonith-timeoutCluster Option Cluster Option ClusterOptionstonith-timeout Optionstonith-timeout stonith-timeout How long to wait for STONITH actions (reboot, on, off) to complete" msgstr "" #. Tag: para #, no-c-format -msgid "stop-orphan-resources" +msgid "concurrent-fencing" msgstr "" #. Tag: para #, no-c-format -msgid " stop-orphan-resourcesCluster Option Cluster Option ClusterOptionstop-orphan-resources Optionstop-orphan-resources stop-orphan-resources Should deleted resources be stopped?" +msgid " concurrent-fencingCluster Option Cluster Option ClusterOptionconcurrent-fencing Optionconcurrent-fencing concurrent-fencing Is the cluster allowed to initiate multiple fence actions concurrently?" msgstr "" #. Tag: para #, no-c-format -msgid "stop-orphan-actions" +msgid "cluster-delay" msgstr "" #. Tag: para #, no-c-format -msgid " stop-orphan-actionsCluster Option Cluster Option ClusterOptionstop-orphan-actions Optionstop-orphan-actions stop-orphan-actions Should deleted actions be cancelled?" +msgid " cluster-delayCluster Option Cluster Option ClusterOptioncluster-delay Optioncluster-delay cluster-delay 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 "start-failure-is-fatal" +msgid "dc-deadtime" msgstr "" #. Tag: para #, no-c-format -msgid " start-failure-is-fatalCluster Option Cluster Option ClusterOptionstart-failure-is-fatal Optionstart-failure-is-fatal start-failure-is-fatal When set to FALSE, the cluster will instead use the resource’s failcount and value for resource-failure-stickiness." +msgid "20s" msgstr "" #. Tag: para #, no-c-format -msgid "pe-error-series-max" +msgid " dc-deadtimeCluster Option Cluster Option ClusterOptiondc-deadtime Optiondc-deadtime dc-deadtime 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 "cluster-recheck-interval" msgstr "" #. Tag: para #, no-c-format -msgid "-1 (all)" +msgid "15min" msgstr "" #. Tag: para #, no-c-format -msgid " pe-error-series-maxCluster Option Cluster Option ClusterOptionpe-error-series-max Optionpe-error-series-max pe-error-series-max The number of PE inputs resulting in ERRORs to save. Used when reporting problems." +msgid " cluster-recheck-intervalCluster Option Cluster Option ClusterOptioncluster-recheck-interval Optioncluster-recheck-interval cluster-recheck-interval 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 "pe-error-series-max" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pe-error-series-maxCluster Option Cluster Option ClusterOptionpe-error-series-max Optionpe-error-series-max pe-error-series-max 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 "pe-warn-series-max" msgstr "" #. Tag: para #, no-c-format -msgid " pe-warn-series-maxCluster Option Cluster Option ClusterOptionpe-warn-series-max Optionpe-warn-series-max pe-warn-series-max The number of PE inputs resulting in WARNINGs to save. Used when reporting problems." +msgid " pe-warn-series-maxCluster Option Cluster Option ClusterOptionpe-warn-series-max Optionpe-warn-series-max pe-warn-series-max 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 "pe-input-series-max" msgstr "" #. Tag: para #, no-c-format -msgid " pe-input-series-maxCluster Option Cluster Option ClusterOptionpe-input-series-max Optionpe-input-series-max pe-input-series-max The number of \"normal\" PE inputs to save. Used when reporting problems." +msgid " pe-input-series-maxCluster Option Cluster Option ClusterOptionpe-input-series-max Optionpe-input-series-max pe-input-series-max 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 "remove-after-stop" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " remove-after-stopCluster Option Cluster Option ClusterOptionremove-after-stop Optionremove-after-stop remove-after-stop Advanced Use Only: 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 "You can always obtain an up-to-date list of cluster options, including their default values, by running the pengine metadata command." +msgid "startup-fencing" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " startup-fencingCluster Option Cluster Option ClusterOptionstartup-fencing Optionstartup-fencing startup-fencing Advanced Use Only: Should the cluster shoot unseen nodes? Not using the default is very unsafe!" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "election-timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "2min" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " election-timeoutCluster Option Cluster Option ClusterOptionelection-timeout Optionelection-timeout election-timeout Advanced Use Only: If you need to adjust this value, it probably indicates the presence of a bug." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "shutdown-escalation" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "20min" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " shutdown-escalationCluster Option Cluster Option ClusterOptionshutdown-escalation Optionshutdown-escalation shutdown-escalation Advanced Use Only: If you need to adjust this value, it probably indicates the presence of a bug." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crmd-integration-timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "3min" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " crmd-integration-timeoutCluster Option Cluster Option ClusterOptioncrmd-integration-timeout Optioncrmd-integration-timeout crmd-integration-timeout Advanced Use Only: If you need to adjust this value, it probably indicates the presence of a bug." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crmd-finalization-timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "30min" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " crmd-finalization-timeoutCluster Option Cluster Option ClusterOptioncrmd-finalization-timeout Optioncrmd-finalization-timeout crmd-finalization-timeout Advanced Use Only: If you need to adjust this value, it probably indicates the presence of a bug." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crmd-transition-delay" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "0s" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " crmd-transition-delayCluster Option Cluster Option ClusterOptioncrmd-transition-delay Optioncrmd-transition-delay crmd-transition-delay Advanced Use Only: 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 "default-resource-stickiness" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "0" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " default-resource-stickinessCluster Option Cluster Option ClusterOptiondefault-resource-stickiness Optiondefault-resource-stickiness default-resource-stickiness Deprecated: See instead" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "is-managed-default" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " is-managed-defaultCluster Option Cluster Option ClusterOptionis-managed-default Optionis-managed-default is-managed-default Deprecated: See instead" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "default-action-timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " default-action-timeoutCluster Option Cluster Option ClusterOptiondefault-action-timeout Optiondefault-action-timeout default-action-timeout Deprecated: See instead" msgstr "" #. Tag: title #, no-c-format msgid "Querying and Setting Cluster Options" msgstr "" #. Tag: para #, no-c-format msgid " QueryingCluster Option Cluster Option SettingCluster Option Cluster Option ClusterQuerying Options Querying Options ClusterSetting Options Setting Options " msgstr "" #. Tag: para #, no-c-format -msgid "Cluster options can be queried and modified using the crm_attribute tool. To get the current value of cluster-delay, simply use:" +msgid "Cluster options can be queried and modified using the crm_attribute tool. To get the current value of cluster-delay, you can run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name cluster-delay --get-value" +msgid "# crm_attribute --query --name cluster-delay" msgstr "" #. Tag: para #, no-c-format msgid "which is more simply written as" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --get-value -n cluster-delay" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --get-value -n cluster-delay\n" -" name=cluster-delay value=60s" +msgid "# crm_attribute -G -n cluster-delay\n" +"scope=crm_config name=cluster-delay value=60s" msgstr "" #. Tag: para #, no-c-format -msgid "However, if no value is found, the tool will display an error:" +msgid "If no value is found, the tool will display an error:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --get-value -n clusta-deway`\n" -"name=clusta-deway value=(null)\n" -"Error performing operation: The object/attribute does not exist" +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, eg. 30, simply run:" +msgid "To use a different value (for example, 30 seconds), simply run:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name cluster-delay --attr-value 30s" +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 with this command:" +msgid "To go back to the cluster’s default value, you can delete the value, for example:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name cluster-delay --delete-attr" +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: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name batch-limit --delete-attr\n" +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 --attr-id" +"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, please refer to ." +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 ." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot b/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot new file mode 100644 index 0000000000..96fc81ea81 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot @@ -0,0 +1,317 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 Templates" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If you want to create lots of resources with similar configurations, defining a resource template 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 "<template id=\"vm-template\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" +" <meta_attributes id=\"vm-template-meta_attributes\">\n" +" <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" +" </meta_attributes>\n" +" <utilization id=\"vm-template-utilization\">\n" +" <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" +" </utilization>\n" +" <operations>\n" +" <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" +" <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" +" </operations>\n" +"</template>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Once you define a resource template, you can use it in primitives by specifying the template property." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Xen primitive resource using a resource template" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<primitive id=\"vm1\" template=\"vm-template\">\n" +" <instance_attributes id=\"vm1-instance_attributes\">\n" +" <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" +" <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" +" </instance_attributes>\n" +"</primitive>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the example above, the new primitive vm1 will inherit everything from vm-template. 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 "<primitive id=\"vm1\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" +" <meta_attributes id=\"vm-template-meta_attributes\">\n" +" <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" +" </meta_attributes>\n" +" <utilization id=\"vm-template-utilization\">\n" +" <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" +" </utilization>\n" +" <operations>\n" +" <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" +" <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" +" </operations>\n" +" <instance_attributes id=\"vm1-instance_attributes\">\n" +" <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" +" <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" +" </instance_attributes>\n" +"</primitive>" +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 "<primitive id=\"vm2\" template=\"vm-template\">\n" +" <meta_attributes id=\"vm2-meta_attributes\">\n" +" <nvpair id=\"vm2-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"false\"/>\n" +" </meta_attributes>\n" +" <utilization id=\"vm2-utilization\">\n" +" <nvpair id=\"vm2-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" +" </utilization>\n" +" <instance_attributes id=\"vm2-instance_attributes\">\n" +" <nvpair id=\"vm2-instance_attributes-name\" name=\"name\" value=\"vm2\"/>\n" +" <nvpair id=\"vm2-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm2\"/>\n" +" </instance_attributes>\n" +" <operations>\n" +" <op id=\"vm2-monitor-30s\" interval=\"30s\" name=\"monitor\" timeout=\"120s\"/>\n" +" <op id=\"vm2-stop-0\" interval=\"0\" name=\"stop\" timeout=\"60s\"/>\n" +" </operations>\n" +"</primitive>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the example above, the new primitive vm2 has special attribute values. Its monitor operation has a longer timeout and interval, and the primitive has an additional stop 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 "Referencing 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 "order constraints (see )" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "colocation constraints (see )" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "rsc_ticket constraints (for multi-site clusters as described in )" +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 "<rsc_colocation id=\"vm-template-colo-base-rsc\" rsc=\"vm-template\" rsc-role=\"Started\" with-rsc=\"base-rsc\" score=\"INFINITY\"/>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "would colocate all VMs with base-rsc and is the equivalent of the following constraint configuration:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_colocation id=\"vm-colo-base-rsc\" score=\"INFINITY\">\n" +" <resource_set id=\"vm-colo-base-rsc-0\" sequential=\"false\" role=\"Started\">\n" +" <resource_ref id=\"vm1\"/>\n" +" <resource_ref id=\"vm2\"/>\n" +" </resource_set>\n" +" <resource_set id=\"vm-colo-base-rsc-1\">\n" +" <resource_ref id=\"base-rsc\"/>\n" +" </resource_set>\n" +"</rsc_colocation>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In a colocation constraint, only one template may be referenced from either rsc or with-rsc; the other reference must be a regular resource." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Referencing Resource Templates in Sequential 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:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" +" <resource_set id=\"order1-0\">\n" +" <resource_ref id=\"base-rsc\"/>\n" +" <resource_ref id=\"vm-template\"/>\n" +" <resource_ref id=\"top-rsc\"/>\n" +" </resource_set>\n" +"</rsc_order>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "is the equivalent of the following constraint configuration:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" +" <resource_set id=\"order1-0\">\n" +" <resource_ref id=\"base-rsc\"/>\n" +" <resource_ref id=\"vm1\"/>\n" +" <resource_ref id=\"vm2\"/>\n" +" <resource_ref id=\"top-rsc\"/>\n" +" </resource_set>\n" +"</rsc_order>" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Referencing Resource Templates in Parallel Resource Sets" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If the resources referencing the template can run in parallel:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" +" <resource_set id=\"order2-0\">\n" +" <resource_ref id=\"base-rsc\"/>\n" +" </resource_set>\n" +" <resource_set id=\"order2-1\" sequential=\"false\">\n" +" <resource_ref id=\"vm-template\"/>\n" +" </resource_set>\n" +" <resource_set id=\"order2-2\">\n" +" <resource_ref id=\"top-rsc\"/>\n" +" </resource_set>\n" +"</rsc_order>" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" +" <resource_set id=\"order2-0\">\n" +" <resource_ref id=\"base-rsc\"/>\n" +" </resource_set>\n" +" <resource_set id=\"order2-1\" sequential=\"false\">\n" +" <resource_ref id=\"vm1\"/>\n" +" <resource_ref id=\"vm2\"/>\n" +" </resource_set>\n" +" <resource_set id=\"order2-2\">\n" +" <resource_ref id=\"top-rsc\"/>\n" +" </resource_set>\n" +"</rsc_order>" +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Resources.pot b/doc/Pacemaker_Explained/pot/Ch-Resources.pot index 44627995e1..db8be236ab 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Resources.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Resources.pot @@ -1,1024 +1,1230 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +msgid "What is a Cluster Resource?" msgstr "" #. Tag: para #, no-c-format msgid " Resource " msgstr "" #. Tag: para #, no-c-format -msgid "The role of a resource agent is to abstract the service it provides and present a consistent view to the cluster, which allows the cluster to be agnostic about the resources it manages." +msgid "A resource is a service made highly available by a cluster. The simplest type of resource, a primitive 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 "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 start, stop or monitor command." +msgid "Every primitive resource has a resource agent. 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 "For this reason it is crucial that resource agents are well tested." +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 start, stop or monitor 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." +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 "Supported Resource Classes" +msgid "Resource Classes" msgstr "" #. Tag: para #, no-c-format msgid " Resourceclass class " msgstr "" #. Tag: para #, no-c-format -msgid "There are five classes of agents supported by Pacemaker:" +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 "Fencing" -msgstr "" - #. Tag: para #, no-c-format msgid "Service" msgstr "" #. Tag: para #, no-c-format -msgid " ResourceHeartbeat Heartbeat HeartbeatResources Resources " -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Version 1 of Heartbeat came with its own style of resource agents and it is highly likely that many people have written their own agents based on its conventions. See http://wiki.linux-ha.org/HeartbeatResourceAgent for more information " +msgid "Fencing" msgstr "" #. Tag: para #, no-c-format -msgid "Although deprecated with the release of Heartbeat v2, they were supported by Pacemaker up until the release of 1.1.8 to enable administrators to continue to use these agents." +msgid "Nagios Plugins" msgstr "" #. Tag: title #, no-c-format msgid "Open Cluster Framework" msgstr "" #. Tag: para #, no-c-format msgid " ResourceOCF OCF OCFResources Resources Open Cluster FrameworkResources Resources " msgstr "" #. Tag: para #, no-c-format -msgid "The OCF standard http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD - 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. is basically an extension of the Linux Standard Base conventions for init scripts to:" +msgid "The OCF standard See http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD  — 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. 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" +msgid "make them self-describing, and" msgstr "" #. Tag: para #, no-c-format -msgid "extensible" +msgid "make them extensible" msgstr "" #. Tag: para #, no-c-format -msgid "OCF specs have strict definitions of the exit codes that actions must return. Included with the cluster is the ocf-tester script, which can be useful in this regard. " +msgid "OCF specs have strict definitions of the exit codes that actions must return. The resource-agents source code includes the ocf-tester script, which can be useful in this regard. " 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 script as environment variables, with the special prefix OCF_RESKEY_. So, a parameter which the user thinks of as ip it will be passed to the script as OCF_RESKEY_ip. The number and purpose of the parameters is completely arbitrary, however your script should advertise any that it supports using the meta-data command." +msgid "Parameters are passed to the resource agent as environment variables, with the special prefix OCF_RESKEY_. So, a parameter which the user thinks of as ip will be passed to the resource agent as OCF_RESKEY_ip. The number and purpose of the parameters is left to the resource agent; however, the resource agent should use the meta-data command to advertise any that it supports." msgstr "" #. Tag: para #, no-c-format -msgid "The OCF class is the most preferred one as it is an industry standard, highly flexible (allowing parameters to be passed to agents in a non-positional manner) and self-describing." +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 reference and ." msgstr "" #. Tag: title #, no-c-format msgid "Linux Standard Base" msgstr "" #. Tag: para #, no-c-format msgid " ResourceLSB LSB LSBResources Resources Linux Standard BaseResources Resources " msgstr "" #. Tag: para #, no-c-format -msgid "LSB resource agents are those found in /etc/init.d." +msgid "LSB resource agents are those found in /etc/init.d." 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. See http://refspecs.linux-foundation.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html for the LSB Spec (as it relates to init scripts). " +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. See http://refspecs.linux-foundation.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html for the LSB Spec as it relates to init scripts. " msgstr "" #. Tag: para #, no-c-format -msgid "Many distributions claim LSB compliance but ship with broken init scripts. For details on how to check if your init script is LSB-compatible, see . The most common problems are:" +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 . 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 start/stop/status actions" +msgid "Not observing the correct exit status codes for start/stop/status actions" msgstr "" #. Tag: para #, no-c-format -msgid "Starting a started resource returns an error (this violates the LSB spec)" +msgid "Starting a started resource returns an error" msgstr "" #. Tag: para #, no-c-format -msgid "Stopping a stopped resource returns an error (this violates the LSB spec)" +msgid "Stopping a stopped resource returns an error" msgstr "" #. Tag: para #, no-c-format -msgid " ResourceSystemd Systemd SystemdResources Resources " +msgid "Remember to make sure the computer is not configured to start any services at boot time — that should be controlled by the cluster." msgstr "" #. Tag: para #, no-c-format -msgid "Some newer distributions have replaced the old SYS-V style of initialization daemons (and scripts) with an alternative called Systemd." +msgid " ResourceSystemd Systemd SystemdResources Resources " msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker is able to manage these services if they are present." +msgid "Some newer distributions have replaced the old \"SysV\" style of initialization daemons and scripts with an alternative called Systemd." msgstr "" #. Tag: para #, no-c-format -msgid "Instead of init scripts, systemd has unit files. Generally the services (or unit files) are provided by the OS/distribution but there are some instructions for converting from init scripts at: http://0pointer.de/blog/projects/systemd-for-admins-3.html" +msgid "Pacemaker is able to manage these services if they are present." msgstr "" #. Tag: para #, no-c-format -msgid "Remember to make sure the computer is not configured to start any services at boot time that should be controlled by the cluster." +msgid "Instead of init scripts, systemd has unit files. Generally, the services (unit files) are provided by the OS distribution, but there are online guides for converting from init scripts. For example, http://0pointer.de/blog/projects/systemd-for-admins-3.html" msgstr "" #. Tag: para #, no-c-format msgid " ResourceUpstart Upstart UpstartResources Resources " msgstr "" #. Tag: para #, no-c-format -msgid "Some newer distributions have replaced the old SYS-V style of initialization daemons (and scripts) with an alternative called Upstart." +msgid "Some newer distributions have replaced the old \"SysV\" style of initialization daemons (and scripts) with an alternative called Upstart." msgstr "" #. Tag: para #, no-c-format -msgid "Instead of init scripts, upstart has jobs. Generally the services (or jobs) are provided by the OS/distribution." +msgid "Instead of init scripts, upstart has jobs. 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 " ResourceSystem Services System Services System ServiceResources Resources " msgstr "" #. Tag: para #, no-c-format -msgid "Since there are now many \"common\" types of system services (systemd, upstart, and lsb), Pacemaker supports a special alias which intelligently figures out which one applies to a given cluster node." +msgid "Since there are various types of system services (systemd, upstart, and lsb), Pacemaker supports a special service 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 systemd, upstart, and lsb." 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 (SYS-V) init script" +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 " ResourceSTONITH STONITH STONITHResources Resources " msgstr "" #. Tag: para #, no-c-format -msgid "There is also an additional class, STONITH, which is used exclusively for fencing related resources. This is discussed later in ." +msgid "The STONITH class is used exclusively for fencing-related resources. This is discussed later in ." +msgstr "" + +#. Tag: para +#, no-c-format +msgid " ResourceNagios Plugins Nagios Plugins Nagios PluginsResources Resources " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Nagios Plugins The project has two independent forks, hosted at https://www.nagios-plugins.org/ and https://www.monitoring-plugins.org/. Output from both projects' plugins is similar, so plugins from either project can be used with pacemaker. 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 if they are present." +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 script to use for the resource, where to find that script and what standards it conforms to." +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 "id" msgstr "" #. Tag: para #, no-c-format msgid "Your name for the resource idResource Resource ResourcePropertyid Propertyid id " msgstr "" #. Tag: para #, no-c-format msgid "class" msgstr "" #. Tag: para #, no-c-format -msgid "The standard the script conforms to. Allowed values: ocf, service, upstart, systemd, lsb, stonith classResource Resource ResourcePropertyclass Propertyclass class " +msgid "The standard the resource agent conforms to. Allowed values: lsb, nagios, ocf, service, stonith, systemd, upstart classResource Resource ResourcePropertyclass Propertyclass class " msgstr "" #. Tag: para #, no-c-format msgid "type" msgstr "" #. Tag: para #, no-c-format -msgid "The name of the Resource Agent you wish to use. Eg. IPaddr or Filesystem typeResource Resource ResourcePropertytype Propertytype type " +msgid "The name of the Resource Agent you wish to use. E.g. IPaddr or Filesystem typeResource Resource ResourcePropertytype Propertytype type " msgstr "" #. Tag: para #, no-c-format msgid "provider" msgstr "" #. Tag: para #, no-c-format -msgid "The OCF spec allows multiple vendors to supply the same ResourceAgent. To use the OCF resource agents supplied with Heartbeat, you should specify heartbeat here. providerResource Resource ResourcePropertyprovider Propertyprovider provider " +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 heartbeat here. providerResource Resource ResourcePropertyprovider Propertyprovider provider " msgstr "" #. Tag: para #, no-c-format -msgid "Resource definitions can be queried with the crm_resource tool. For example" +msgid "The XML definition of a resource can be queried with the crm_resource tool. For example:" msgstr "" -#. Tag: programlisting +#. 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 "An example system resource" +msgid "A system resource definition" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"Email\" class=\"service\" type=\"exim\"/>" msgstr "" #. Tag: para #, no-c-format -msgid "One of the main drawbacks to system services (such as LSB, Systemd and Upstart) resources is that they do not allow any parameters!" +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 example OCF resource" +msgid "An OCF resource definition" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" -" <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <instance_attributes id=\"Public-IP-params\">\n" +" <nvpair id=\"Public-IP-ip\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: title #, no-c-format msgid "Resource Options" msgstr "" #. Tag: para #, no-c-format -msgid "Options are used by the cluster to decide how your resource should behave and can be easily set using the --meta option of the crm_resource command." +msgid "Resources have two types of options: meta-attributes and instance attributes. Meta-attributes apply to any type of resource, while instance attributes are specific to each resource agent." msgstr "" #. Tag: title #, no-c-format -msgid "Options for a Primitive Resource" +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 --meta option of the crm_resource 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 "priority" msgstr "" #. Tag: para #, no-c-format -msgid "0" +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. priorityResource Option Resource Option ResourceOptionpriority Optionpriority priority " msgstr "" #. Tag: para #, no-c-format msgid "target-role" msgstr "" #. Tag: para #, no-c-format -msgid "Started" +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 "* Stopped - Force the resource to be stopped" +msgid "stopped: Force the resource to be stopped" msgstr "" #. Tag: para #, no-c-format -msgid "* Started - Allow the resource to be started (In the case of multi-state resources, they will not promoted to master)" +msgid "started: Allow the resource to be started (In the case of multi-state resources, they will not be promoted to master)" msgstr "" #. Tag: para #, no-c-format -msgid "* Master - Allow the resource to be started and, if appropriate, promoted target-roleResource Option Resource Option ResourceOptiontarget-role Optiontarget-role target-role " +msgid "master: Allow the resource to be started and, if appropriate, promoted target-roleResource Option Resource Option ResourceOptiontarget-role Optiontarget-role target-role " msgstr "" #. Tag: para #, no-c-format msgid "is-managed" msgstr "" #. Tag: para #, no-c-format -msgid "TRUE" +msgid "TRUE" msgstr "" #. Tag: para #, no-c-format msgid "Is the cluster allowed to start and stop the resource? Allowed values: true, false is-managedResource Option Resource Option ResourceOptionis-managed Optionis-managed is-managed " msgstr "" #. Tag: para #, no-c-format msgid "resource-stickiness" msgstr "" #. Tag: para #, no-c-format -msgid "Calculated" +msgid "value of resource-stickiness in the rsc_defaults section" msgstr "" #. Tag: para #, no-c-format -msgid "How much does the resource prefer to stay where it is? Defaults to the value of resource-stickiness in the rsc_defaults section resource-stickinessResource Option Resource Option ResourceOptionresource-stickiness Optionresource-stickiness resource-stickiness " +msgid "How much does the resource prefer to stay where it is? resource-stickinessResource Option Resource Option ResourceOptionresource-stickiness Optionresource-stickiness resource-stickiness " msgstr "" #. Tag: para #, no-c-format msgid "requires" msgstr "" #. Tag: para #, no-c-format -msgid "Under what conditions can the resource be started. (Since 1.1.8)" +msgid "fencing (unless stonith-enabled is false or class is stonith, in which case it defaults to quorum)" msgstr "" #. Tag: para #, no-c-format -msgid "Defaults to fencing unless stonith-enabled is false or class is stonith - under those conditions the default is quorum. Possible values:" +msgid "Conditions under which the resource can be started (Since 1.1.8) Allowed values:" msgstr "" #. Tag: para #, no-c-format -msgid "* nothing - can always be started" +msgid "nothing: can always be started" msgstr "" #. Tag: para #, no-c-format -msgid "* quorum - The cluster can only start this resource if a majority of the configured nodes are active" +msgid "quorum: The cluster can only start this resource if a majority of the configured nodes are active" msgstr "" #. Tag: para #, no-c-format -msgid "* fencing - The cluster can only start this resource if a majority of the configured nodes are active and any failed or unknown nodes have been powered off." +msgid "fencing: The cluster can only start this resource if a majority of the configured nodes are active and any failed or unknown nodes have been powered off" msgstr "" #. Tag: para #, no-c-format -msgid "* unfencing - The cluster can only start this resource if a majority of the configured nodes are active and any failed or unknown nodes have been powered off and only on nodes that have been unfenced indexterm: Option[requires,Resource] ResourceOptionrequires Optionrequires requires " +msgid "unfencing: The cluster can only start this resource if a majority of the configured nodes are active and any failed or unknown nodes have been powered off and only on nodes that have been unfenced" msgstr "" #. Tag: para #, no-c-format -msgid "migration-threshold" +msgid " requiresResource Option Resource Option ResourceOptionrequires Optionrequires requires " msgstr "" #. Tag: para #, no-c-format -msgid "INFINITY (disabled)" +msgid "migration-threshold" 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. migration-thresholdResource Option Resource Option ResourceOptionmigration-threshold Optionmigration-threshold migration-threshold " +msgid "INFINITY" msgstr "" #. Tag: para #, no-c-format -msgid "failure-timeout" +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 INFINITY indicates that this feature is disabled. migration-thresholdResource Option Resource Option ResourceOptionmigration-threshold Optionmigration-threshold migration-threshold " msgstr "" #. Tag: para #, no-c-format -msgid "0 (disabled)" +msgid "failure-timeout" 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. failure-timeoutResource Option Resource Option ResourceOptionfailure-timeout Optionfailure-timeout failure-timeout " +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. failure-timeoutResource Option Resource Option ResourceOptionfailure-timeout Optionfailure-timeout failure-timeout " msgstr "" #. Tag: para #, no-c-format msgid "multiple-active" msgstr "" #. Tag: para #, no-c-format -msgid "stop_start" +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:" +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 "* block - mark the resource as unmanaged" +msgid "block: mark the resource as unmanaged" msgstr "" #. Tag: para #, no-c-format -msgid "* stop_only - stop all active instances and leave them that way" +msgid "stop_only: stop all active instances and leave them that way" msgstr "" #. Tag: para #, no-c-format -msgid "* stop_start - stop all active instances and start the resource in one location only" +msgid "stop_start: stop all active instances and start the resource in one location only" msgstr "" #. Tag: para #, no-c-format msgid " multiple-activeResource Option Resource Option ResourceOptionmultiple-active Optionmultiple-active multiple-active " msgstr "" #. Tag: para #, no-c-format -msgid "If you performed the following commands on the previous LSB Email resource" +msgid "remote-node" msgstr "" -#. Tag: programlisting +#. Tag: para +#, no-c-format +msgid "The name of the remote-node this resource defines. This both enables the resource as a remote-node and defines the unique name used to identify the remote-node. If no other parameters are set, this value will also be assumed as the hostname to connect to at the port specified by remote-port. WARNING: This value cannot overlap with any resource or node IDs. If not specified, this feature is disabled." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "remote-port" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "3121" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Port to use for the guest connection to pacemaker_remote" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "remote-addr" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "value of remote-node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The IP address or hostname to connect to if remote-node’s name is not the hostname of the guest." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "remote-connect-timeout" +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: para +#, no-c-format +msgid "Support for remote nodes was added in pacemaker 1.1.10. If you are using an earlier version, options related to remote nodes will not be available." +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 --property-value 100\n" -"# crm_resource --meta --resource Email --set-parameter multiple-active --property-value block" +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 would be" +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 "<primitive id=\"Email\" class=\"lsb\" type=\"exim\">\n" -" <meta_attributes id=\"meta-email\">\n" -" <nvpair id=\"email-priority\" name=\"priority\" value=\"100\"/>\n" -" <nvpair id=\"email-active\" name=\"multiple-active\" value=\"block\"/>\n" -" </meta_attributes>\n" +" <meta_attributes id=\"Email-meta_attributes\">\n" +" <nvpair id=\"Email-meta_attributes-priority\" name=\"priority\" value=\"100\"/>\n" +" <nvpair id=\"Email-meta_attributes-multiple-active\" name=\"multiple-active\" value=\"block\"/>\n" +" </meta_attributes>\n" "</primitive>" msgstr "" #. Tag: title #, no-c-format -msgid "Setting Global Defaults for Resource Options" +msgid "Setting Global Defaults for Resource Meta-Attributes" msgstr "" #. Tag: para #, no-c-format -msgid "To set a default value for a resource option, simply add it to the rsc_defaults section with crm_attribute. Thus," +msgid "To set a default value for a resource option, add it to the rsc_defaults section with crm_attribute. For example," msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --type rsc_defaults --attr-name is-managed --attr-value false" +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 and had is-managed set to true)." +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 is-managed set to true)." msgstr "" #. Tag: title #, no-c-format -msgid "Instance Attributes" +msgid "Resource Instance Attributes" msgstr "" #. Tag: para #, no-c-format -msgid "The scripts of some resource classes (LSB not being one of them) can be given parameters which determine how they behave and which instance of a service they control." +msgid "The resource agents of some resource classes (lsb, systemd and upstart not 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 crm_resource command. For instance" +msgid "If your resource agent supports parameters, you can add them with the crm_resource command. For example," msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_resource --resource Public-IP --set-parameter ip --property-value 1.2.3.4" +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 "<primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" +" <instance_attributes id=\"params-public-ip\">\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/>\n" +" </instance_attributes>\n" +"</primitive>" +msgstr "" + #. Tag: para #, no-c-format -msgid "For an OCF resource, the result would be an environment variable called OCF_RESKEY_ip with a value of 1.2.3.4." +msgid "For an OCF resource, the result would be an environment variable called OCF_RESKEY_ip with a value of 192.0.2.2." msgstr "" #. Tag: para #, no-c-format -msgid "The list of instance attributes supported by an OCF script can be found by calling the resource script with the meta-data command. The output contains an XML description of all the supported attributes, their purpose and default values." +msgid "The list of instance attributes supported by an OCF resource agent can be found by calling the resource agent with the meta-data 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: programlisting +#. 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 "<?xml version=\"1.0\"?>\n" -" <!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\">\n" -" <resource-agent name=\"Dummy\" version=\"0.9\">\n" -" <version>1.0</version>\n" +"<!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\">\n" +"<resource-agent name=\"Dummy\" version=\"1.0\">\n" +"<version>1.0</version>\n" "\n" -" <longdesc lang=\"en-US\">\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" -" </longdesc>\n" -" <shortdesc lang=\"en-US\">Dummy resource agent</shortdesc>\n" +"<longdesc>\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" -" <parameters>\n" -" <parameter name=\"state\" unique=\"1\">\n" -" <longdesc lang=\"en-US\">\n" -" Location to store the resource state in.\n" -" </longdesc>\n" -" <shortdesc lang=\"en-US\">State file</shortdesc>\n" -" <content type=\"string\" default=\"/var/run/Dummy-{OCF_RESOURCE_INSTANCE}.state\" />\n" -" </parameter>\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" +"</longdesc>\n" +"<shortdesc>Example stateless resource agent</shortdesc>\n" "\n" -" <parameter name=\"dummy\" unique=\"0\">\n" -" <longdesc lang=\"en-US\">\n" -" Dummy attribute that can be changed to cause a reload\n" -" </longdesc>\n" -" <shortdesc lang=\"en-US\">Dummy attribute that can be changed to cause a reload</shortdesc>\n" -" <content type=\"string\" default=\"blah\" />\n" -" </parameter>\n" -" </parameters>\n" +"<parameters>\n" +"<parameter name=\"state\" unique=\"1\">\n" +"<longdesc>\n" +"Location to store the resource state in.\n" +"</longdesc>\n" +"<shortdesc>State file</shortdesc>\n" +"<content type=\"string\" default=\"/var/run/Dummy-default.state\" />\n" +"</parameter>\n" "\n" -" <actions>\n" -" <action name=\"start\" timeout=\"90\" />\n" -" <action name=\"stop\" timeout=\"100\" />\n" -" <action name=\"monitor\" timeout=\"20\" interval=\"10\",height=\"0\" start-delay=\"0\" />\n" -" <action name=\"reload\" timeout=\"90\" />\n" -" <action name=\"migrate_to\" timeout=\"100\" />\n" -" <action name=\"migrate_from\" timeout=\"90\" />\n" -" <action name=\"meta-data\" timeout=\"5\" />\n" -" <action name=\"validate-all\" timeout=\"30\" />\n" -" </actions>\n" -" </resource-agent>" +"<parameter name=\"fake\" unique=\"0\">\n" +"<longdesc>\n" +"Fake attribute that can be changed to cause a reload\n" +"</longdesc>\n" +"<shortdesc>Fake attribute that can be changed to cause a reload</shortdesc>\n" +"<content type=\"string\" default=\"dummy\" />\n" +"</parameter>\n" +"\n" +"<parameter name=\"op_sleep\" unique=\"1\">\n" +"<longdesc>\n" +"Number of seconds to sleep during operations. This can be used to test how\n" +"the cluster reacts to operation timeouts.\n" +"</longdesc>\n" +"<shortdesc>Operation sleep duration in seconds.</shortdesc>\n" +"<content type=\"string\" default=\"0\" />\n" +"</parameter>\n" +"\n" +"</parameters>\n" +"\n" +"<actions>\n" +"<action name=\"start\" timeout=\"20\" />\n" +"<action name=\"stop\" timeout=\"20\" />\n" +"<action name=\"monitor\" timeout=\"20\" interval=\"10\" depth=\"0\"/>\n" +"<action name=\"reload\" timeout=\"20\" />\n" +"<action name=\"migrate_to\" timeout=\"20\" />\n" +"<action name=\"migrate_from\" timeout=\"20\" />\n" +"<action name=\"validate-all\" timeout=\"20\" />\n" +"<action name=\"meta-data\" timeout=\"5\" />\n" +"</actions>\n" +"</resource-agent>" msgstr "" #. Tag: title #, no-c-format msgid "Resource Operations" msgstr "" #. Tag: para #, no-c-format msgid " ResourceAction Action " msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Monitoring Resources for Failure" +msgid "Operations 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 "By default, the cluster will not ensure your resources are still healthy. To instruct the cluster to do this, you need to add a monitor operation to the resource’s definition." +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 not ensure your resources stay healthy once they are started. Currently, anyway. Automatic monitoring operations may be added in a future version of Pacemaker. To instruct the cluster to do this, you need to add a monitor 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 "<primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" " <operations>\n" " <op id=\"public-ip-check\" name=\"monitor\" interval=\"60s\"/>\n" " </operations>\n" " <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: title #, no-c-format msgid "Properties of an Operation" msgstr "" #. Tag: para #, no-c-format -msgid "Your name for the action. Must be unique. idAction Property Action Property ActionPropertyid Propertyid id " +msgid "A unique name for the operation. idAction Property Action Property ActionPropertyid Propertyid id " msgstr "" #. Tag: para #, no-c-format msgid "name" msgstr "" #. Tag: para #, no-c-format -msgid "The action to perform. Common values: monitor, start, stop nameAction Property Action Property ActionPropertyname Propertyname name " +msgid "The action to perform. This can be any action supported by the agent; common values include monitor, start, and stop. nameAction Property Action Property ActionPropertyname Propertyname name " msgstr "" #. Tag: para #, no-c-format msgid "interval" msgstr "" #. Tag: para #, no-c-format -msgid "How frequently (in seconds) to perform the operation. Default value: 0, meaning never. intervalAction Property Action Property ActionPropertyinterval Propertyinterval interval " +msgid "How frequently (in seconds) to perform the operation. A value of 0 means never. A positive value defines a recurring action, which is typically used with monitor. intervalAction Property Action Property ActionPropertyinterval Propertyinterval interval " msgstr "" #. Tag: para #, no-c-format msgid "timeout" msgstr "" #. Tag: para #, no-c-format -msgid "How long to wait before declaring the action has failed. timeoutAction Property Action Property ActionPropertytimeout Propertytimeout timeout " +msgid "How long to wait before declaring the action has failed timeoutAction Property Action Property ActionPropertytimeout Propertytimeout timeout " msgstr "" #. Tag: para #, no-c-format msgid "on-fail" msgstr "" +#. Tag: para +#, no-c-format +msgid "restart (except for stop operations, which default to fence when STONITH is enabled and block otherwise)" +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 "* ignore - Pretend the resource did not fail" +msgid "ignore: Pretend the resource did not fail." msgstr "" #. Tag: para #, no-c-format -msgid "* block - Don’t perform any further operations on the resource" +msgid "block: Don’t perform any further operations on the resource." msgstr "" #. Tag: para #, no-c-format -msgid "* stop - Stop the resource and do not start it elsewhere" +msgid "stop: Stop the resource and do not start it elsewhere." msgstr "" #. Tag: para #, no-c-format -msgid "* restart - Stop the resource and start it again (possibly on a different node)" +msgid "restart: Stop the resource and start it again (possibly on a different node)." msgstr "" #. Tag: para #, no-c-format -msgid "* fence - STONITH the node on which the resource failed" +msgid "fence: STONITH the node on which the resource failed." msgstr "" #. Tag: para #, no-c-format -msgid "* standby - Move all resources away from the node on which the resource failed" +msgid "standby: Move all resources away from the node on which the resource failed." msgstr "" #. Tag: para #, no-c-format -msgid "The default for the stop operation is fence when STONITH is enabled and block otherwise. All other operations default to stop. on-failAction Property Action Property ActionPropertyon-fail Propertyon-fail on-fail " +msgid " on-failAction Property Action Property ActionPropertyon-fail Propertyon-fail on-fail " msgstr "" #. Tag: para #, no-c-format msgid "enabled" msgstr "" #. Tag: para #, no-c-format -msgid "If false, the operation is treated as if it does not exist. Allowed values: true, false enabledAction Property Action Property ActionPropertyenabled Propertyenabled enabled " +msgid "If false, 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 (is-managed=false), as this alone will not block any configured monitoring. Disabling the operation does not suppress all actions of the given type. Allowed values: true, false. enabledAction Property Action Property ActionPropertyenabled Propertyenabled enabled " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "record-pending" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If true, 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 operation default (see next section). Allowed values: true, false. enabledAction Property Action Property ActionPropertyenabled Propertyenabled enabled " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "role" +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: Stopped, Started, and in the case of multi-state resources, Slave and Master. roleAction Property Action Property ActionPropertyrole Propertyrole role " +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 probes) 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 resource-discovery 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 target-role property can be used for further checking." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "For example, if a resource has one monitor operation with interval=10 role=Started and a second monitor operation with interval=11 role=Stopped, the cluster will run the first monitor on any nodes it thinks should be running the resource, and the second monitor on any nodes that it thinks should not 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 is-managed=false): 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 target-role to be set to Stopped then Started 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 role=Stopped. Monitor operations with role=Stopped 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 role=Stopped. 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 "To set a default value for a operation option, simply add it to the op_defaults section with crm_attribute. Thus," +msgid "You can change the global default values for operation properties in a given cluster. These are defined in an op_defaults section of the CIB’s configuration section, and can be set with crm_attribute. For example," msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --type op_defaults --attr-name timeout --attr-value 20s" +msgid "# crm_attribute --type op_defaults --name timeout --update 20s" msgstr "" #. Tag: para #, no-c-format -msgid "would default each operation’s timeout to 20 seconds. If an operation’s definition also includes a value for timeout, then that value would be used instead (for that operation only)." +msgid "would default each operation’s timeout to 20 seconds. If an operation’s definition also includes a value for timeout, then that value would be used for that operation instead." msgstr "" #. Tag: title #, no-c-format -msgid "When Resources Take a Long Time to Start/Stop" +msgid "When Implicit Operations Take a Long Time" msgstr "" #. Tag: para #, no-c-format -msgid "There are a number of implicit operations that the cluster will always perform - start, stop and a non-recurring monitor operation (used at startup to check the resource isn’t already active). If one of these is taking too long, then you can create an entry for them and simply specify a new value." +msgid "The cluster will always perform a number of implicit operations: start, stop and a non-recurring monitor 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 "<primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" " <operations>\n" " <op id=\"public-ip-startup\" name=\"monitor\" interval=\"0\" timeout=\"90s\"/>\n" " <op id=\"public-ip-start\" name=\"start\" interval=\"0\" timeout=\"180s\"/>\n" " <op id=\"public-ip-stop\" name=\"stop\" interval=\"0\" timeout=\"15min\"/>\n" " </operations>\n" " <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" "</primitive>" 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." +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 OCF_CHECK_LEVEL for this purpose and dictates that it is \"made available to the resource agent without the normal OCF_RESKEY prefix\"." +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 OCF_CHECK_LEVEL for this purpose and dictates that it is \"made available to the resource agent without the normal OCF_RESKEY prefix\"." msgstr "" #. Tag: para #, no-c-format -msgid "Whatever name you choose, you can specify it by adding an instance_attributes block to the op tag. Note that it is up to each resource agent to look for the parameter and decide how to use it." +msgid "Whatever name you choose, you can specify it by adding an instance_attributes block to the op 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 OCF_CHECK_LEVEL." +msgid "An OCF resource with two recurring health checks, performing different levels of checks specified via OCF_CHECK_LEVEL." msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" " <operations>\n" " <op id=\"public-ip-health-60\" name=\"monitor\" interval=\"60\">\n" " <instance_attributes id=\"params-public-ip-depth-60\">\n" " <nvpair id=\"public-ip-depth-60\" name=\"OCF_CHECK_LEVEL\" value=\"10\"/>\n" " </instance_attributes>\n" " </op>\n" " <op id=\"public-ip-health-300\" name=\"monitor\" interval=\"300\">\n" " <instance_attributes id=\"params-public-ip-depth-300\">\n" " <nvpair id=\"public-ip-depth-300\" name=\"OCF_CHECK_LEVEL\" value=\"20\"/>\n" " </instance_attributes>\n" " </op>\n" " </operations>\n" " <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-level\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <nvpair id=\"public-ip-level\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" "</primitive>" 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 enabled=\"false\" 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 "<primitive id=\"Public-IP\" class=\"ocf\" type=\"IPaddr\" provider=\"heartbeat\">\n" " <operations>\n" " <op id=\"public-ip-check\" name=\"monitor\" interval=\"60s\" enabled=\"false\"/>\n" " </operations>\n" " <instance_attributes id=\"params-public-ip\">\n" -" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"192.0.2.2\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format -msgid "This can be achieved from the command-line by executing" +msgid "This can be achieved from the command line by executing:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# cibadmin -M -X '<op id=\"public-ip-check\" enabled=\"false\"/>'" +msgid "# cibadmin --modify --xml-text '<op id=\"public-ip-check\" enabled=\"false\"/>'" 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 '<op id=\"public-ip-check\" enabled=\"true\"/>'" +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Rules.pot b/doc/Pacemaker_Explained/pot/Ch-Rules.pot index b4fbd058af..f97eb12b36 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Rules.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Rules.pot @@ -1,762 +1,807 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 " ResourceConstraintRule ConstraintRule Rule " 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 resource-stickiness 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 boolean-op field to determine if the rule ultimately evaluates to true or false. 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 "role" msgstr "" #. Tag: para #, no-c-format -msgid "Limits the rule to apply only when the resource is in that role. Allowed values: Started, Slave, and Master. NOTE: A rule with role=\"Master\" can not determine the initial location of a clone instance. It will only affect which of the active instances will be promoted. roleConstraint Rule Constraint Rule ConstraintRulerole Rulerole role " +msgid "started" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Limits the rule to apply only when the resource is in the specified role. Allowed values are started, slave, and master. A rule with role=\"master\" cannot determine the initial location of a clone instance and will only affect which of the active instances will be promoted. roleConstraint Rule Constraint Rule ConstraintRulerole Rulerole role " msgstr "" #. Tag: para #, no-c-format msgid "score" msgstr "" #. Tag: para #, no-c-format msgid "The score to apply if the rule evaluates to true. Limited to use in rules that are part of location constraints. scoreConstraint Rule Constraint Rule ConstraintRulescore Rulescore score " msgstr "" #. Tag: para #, no-c-format msgid "score-attribute" msgstr "" #. Tag: para #, no-c-format msgid "The node attribute to look up and use as a score if the rule evaluates to true. Limited to use in rules that are part of location constraints. score-attributeConstraint Rule Constraint Rule ConstraintRulescore-attribute Rulescore-attribute score-attribute " msgstr "" #. Tag: para #, no-c-format msgid "boolean-op" msgstr "" #. Tag: para #, no-c-format -msgid "How to combine the result of multiple expression objects. Allowed values: and and or. boolean-opConstraint Rule Constraint Rule ConstraintRuleboolean-op Ruleboolean-op boolean-op " +msgid "and" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "How to combine the result of multiple expression objects. Allowed values are and and or. boolean-opConstraint Rule Constraint Rule ConstraintRuleboolean-op Ruleboolean-op boolean-op " msgstr "" #. Tag: title #, no-c-format msgid "Node Attribute Expressions" msgstr "" #. Tag: para #, no-c-format msgid " ResourceConstraintAttribute Expression ConstraintAttribute Expression Attribute Expression " 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. In addition to any attributes added by the administrator, each node has a built-in node attribute called #uname that can also be used." msgstr "" #. Tag: title #, no-c-format msgid "Properties of an Expression" msgstr "" #. Tag: para #, no-c-format msgid "value" msgstr "" #. Tag: para #, no-c-format -msgid "User supplied value for comparison valueConstraint Expression Constraint Expression ConstraintAttribute Expressionvalue Attribute Expressionvalue value " +msgid "User-supplied value for comparison valueConstraint Expression Constraint Expression ConstraintAttribute Expressionvalue Attribute Expressionvalue value " msgstr "" #. Tag: para #, no-c-format msgid "attribute" msgstr "" #. Tag: para #, no-c-format msgid "The node attribute to test attributeConstraint Expression Constraint Expression ConstraintAttribute Expressionattribute Attribute Expressionattribute attribute " msgstr "" #. Tag: para #, no-c-format msgid "type" msgstr "" #. Tag: para #, no-c-format -msgid "Determines how the value(s) should be tested. Allowed values: string, integer, version typeConstraint Expression Constraint Expression ConstraintAttribute Expressiontype Attribute Expressiontype type " +msgid "string" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Determines how the value(s) should be tested. Allowed values are string, integer, and version. typeConstraint Expression Constraint Expression ConstraintAttribute Expressiontype Attribute Expressiontype type " msgstr "" #. Tag: para #, no-c-format msgid "operation" msgstr "" #. Tag: para #, no-c-format msgid "The comparison to perform. Allowed values:" msgstr "" #. Tag: para #, no-c-format -msgid "* lt - True if the node attribute’s value is less than value" +msgid "lt: True if the value of the node’s attribute is less than value" msgstr "" #. Tag: para #, no-c-format -msgid "* gt - True if the node attribute’s value is greater than value" +msgid "gt: True if the value of the node’s attribute is greater than value" msgstr "" #. Tag: para #, no-c-format -msgid "* lte - True if the node attribute’s value is less than or equal to value" +msgid "lte: True if the value of the node’s attribute is less than or equal to value" msgstr "" #. Tag: para #, no-c-format -msgid "* gte - True if the node attribute’s value is greater than or equal to value" +msgid "gte: True if the value of the node’s attribute is greater than or equal to value" msgstr "" #. Tag: para #, no-c-format -msgid "* eq - True if the node attribute’s value is equal to value" +msgid "eq: True if the value of the node’s attribute is equal to value" msgstr "" #. Tag: para #, no-c-format -msgid "* ne - True if the node attribute’s value is not equal to value" +msgid "ne: True if the value of the node’s attribute is not equal to value" msgstr "" #. Tag: para #, no-c-format -msgid "* defined - True if the node has the named attribute" +msgid "defined: True if the node has the named attribute" msgstr "" #. Tag: para #, no-c-format -msgid "* not_defined - True if the node does not have the named attribute operationConstraint Expression Constraint Expression ConstraintAttribute Expressionoperation Attribute Expressionoperation operation " +msgid "not_defined: True if the node does not have the named attribute operationConstraint Expression Constraint Expression ConstraintAttribute Expressionoperation Attribute Expressionoperation operation " msgstr "" #. Tag: title #, no-c-format -msgid "Time/Date Based Expressions" +msgid "Time- and Date-Based Expressions" msgstr "" #. Tag: para #, no-c-format msgid " Time Based Expressions ResourceConstraintDate/Time Expression ConstraintDate/Time Expression Date/Time Expression " msgstr "" #. Tag: para #, no-c-format -msgid "As the name suggests, date_expressions are used to control a resource or cluster option based on the current date/time. They can contain an optional date_spec and/or duration object depending on the context." +msgid "As the name suggests, date_expressions are used to control a resource or cluster option based on the current date/time. They may contain an optional date_spec and/or duration object depending on the context." msgstr "" #. Tag: title #, no-c-format msgid "Properties of a Date Expression" msgstr "" #. Tag: para #, no-c-format msgid "start" msgstr "" #. Tag: para #, no-c-format -msgid "A date/time conforming to the ISO8601 specification. startConstraint Expression Constraint Expression ConstraintDate/Time Expressionstart Date/Time Expressionstart start " +msgid "A date/time conforming to the ISO8601 specification. startConstraint Expression Constraint Expression ConstraintDate/Time Expressionstart Date/Time Expressionstart start " msgstr "" #. Tag: para #, no-c-format msgid "end" msgstr "" #. Tag: para #, no-c-format -msgid "A date/time conforming to the ISO8601 specification. Can be inferred by supplying a value for start and a duration. endConstraint Expression Constraint Expression ConstraintDate/Time Expressionend Date/Time Expressionend end " +msgid "A date/time conforming to the ISO8601 specification. Can be inferred by supplying a value for start and a duration. endConstraint Expression Constraint Expression ConstraintDate/Time Expressionend Date/Time Expressionend end " 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 "* gt - True if the current date/time is after start" +msgid "gt: True if the current date/time is after start" msgstr "" #. Tag: para #, no-c-format -msgid "* lt - True if the current date/time is before end" +msgid "lt: True if the current date/time is before end" msgstr "" #. Tag: para #, no-c-format -msgid "* in-range - True if the current date/time is after start and before end" +msgid "in-range: True if the current date/time is after start and before end" msgstr "" #. Tag: para #, no-c-format -msgid "* date-spec - performs a cron-like comparison to the current date/time operationConstraint Expression Constraint Expression ConstraintDate/Time Expressionoperation Date/Time Expressionoperation operation " +msgid "date-spec: True if the current date/time matches a date_spec object (described below) operationConstraint Expression Constraint Expression ConstraintDate/Time Expressionoperation Date/Time Expressionoperation operation " msgstr "" #. Tag: para #, no-c-format msgid "As these comparisons (except for date_spec) include the time, the eq, neq, gte and lte 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 " Date Specification ResourceConstraintDate Specification ConstraintDate Specification Date Specification " msgstr "" #. Tag: para #, no-c-format msgid "date_spec 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, monthdays=\"1\" matches the first day of every month and hours=\"09-17\" matches the hours between 9am and 5pm (inclusive). However, at this time one cannot specify weekdays=\"1,2\" or weekdays=\"1-2,5-6\" since they contain multiple ranges. Depending on demand, this may be implemented in a future release." +msgid "For example, monthdays=\"1\" matches the first day of every month and hours=\"09-17\" matches the hours between 9am and 5pm (inclusive). At this time, multiple ranges (e.g. weekdays=\"1,2\" or weekdays=\"1-2,5-6\") 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 Spec" +msgid "Properties of a Date Specification" msgstr "" #. Tag: para #, no-c-format msgid "id" msgstr "" #. Tag: para #, no-c-format -msgid "A unique name for the date idDate Specification Date Specification ConstraintDate Specificationid Date Specificationid id " +msgid "A unique name for the object idDate Specification Date Specification ConstraintDate Specificationid Date Specificationid id " msgstr "" #. Tag: para #, no-c-format msgid "hours" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: 0-23 hoursDate Specification Date Specification ConstraintDate Specificationhours Date Specificationhours hours " msgstr "" #. Tag: para #, no-c-format msgid "monthdays" msgstr "" #. Tag: para #, no-c-format -msgid "Allowed values: 0-31 (depending on month and year) monthdaysDate Specification Date Specification ConstraintDate Specificationmonthdays Date Specificationmonthdays monthdays " +msgid "Allowed values: 1-31 (depending on month and year) monthdaysDate Specification Date Specification ConstraintDate Specificationmonthdays Date Specificationmonthdays monthdays " msgstr "" #. Tag: para #, no-c-format msgid "weekdays" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: 1-7 (1=Monday, 7=Sunday) weekdaysDate Specification Date Specification ConstraintDate Specificationweekdays Date Specificationweekdays weekdays " msgstr "" #. Tag: para #, no-c-format msgid "yeardays" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: 1-366 (depending on the year) yeardaysDate Specification Date Specification ConstraintDate Specificationyeardays Date Specificationyeardays yeardays " msgstr "" #. Tag: para #, no-c-format msgid "months" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: 1-12 monthsDate Specification Date Specification ConstraintDate Specificationmonths Date Specificationmonths months " msgstr "" #. Tag: para #, no-c-format msgid "weeks" msgstr "" #. Tag: para #, no-c-format msgid "Allowed values: 1-53 (depending on weekyear) weeksDate Specification Date Specification ConstraintDate Specificationweeks Date Specificationweeks weeks " msgstr "" #. Tag: para #, no-c-format msgid "years" msgstr "" #. Tag: para #, no-c-format -msgid "Year according the Gregorian calendar yearsDate Specification Date Specification ConstraintDate Specificationyears Date Specificationyears years " +msgid "Year according to the Gregorian calendar yearsDate Specification Date Specification ConstraintDate Specificationyears Date Specificationyears years " msgstr "" #. Tag: para #, no-c-format msgid "weekyears" msgstr "" #. Tag: para #, no-c-format -msgid "May differ from Gregorian years; Eg. 2005-001 Ordinal is also 2005-01-01 Gregorian is also 2004-W53-6 Weekly weekyearsDate Specification Date Specification ConstraintDate Specificationweekyears Date Specificationweekyears weekyears " +msgid "Year in which the week started; e.g. 1 January 2005 can be specified as 2005-001 Ordinal, 2005-01-01 Gregorian or 2004-W53-6 Weekly and thus would match years=\"2005\" or weekyears=\"2004\" weekyearsDate Specification Date Specification ConstraintDate Specificationweekyears Date Specificationweekyears weekyears " msgstr "" #. Tag: para #, no-c-format msgid "moon" msgstr "" #. Tag: para #, no-c-format -msgid "Allowed values: 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. moonDate Specification Date Specification ConstraintDate Specificationmoon Date Specificationmoon moon " +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. moonDate Specification Date Specification ConstraintDate Specificationmoon Date Specificationmoon moon " msgstr "" #. Tag: title #, no-c-format msgid "Durations" msgstr "" #. Tag: para #, no-c-format msgid " Duration ResourceConstraintDuration ConstraintDuration Duration " msgstr "" #. Tag: para #, no-c-format -msgid "Durations are used to calculate a value for end when one is not supplied to in_range operations. They contain the same fields as date_spec objects but without the limitations (ie. you can have a duration of 19 months). Like date_specs, any field not supplied is ignored." +msgid "Durations are used to calculate a value for end when one is not supplied to in-range operations. They contain the same fields as date_spec objects but without the limitations (e.g. you can have a duration of 19 months). As with date_specs, any field not supplied is ignored." msgstr "" #. Tag: title #, no-c-format -msgid "Sample Time Based Expressions" +msgid "Sample Time-Based Expressions" msgstr "" #. Tag: para #, no-c-format -msgid "A small sample of how time based expressions can be used." +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 "<rule id=\"rule1\">\n" " <date_expression id=\"date_expr1\" start=\"2005-001\" operation=\"in_range\">\n" " <duration years=\"1\"/>\n" " </date_expression>\n" "</rule>" msgstr "" #. Tag: title #, no-c-format msgid "Equivalent expression" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"rule2\">\n" " <date_expression id=\"date_expr2\" operation=\"date_spec\">\n" " <date_spec years=\"2005\"/>\n" " </date_expression>\n" "</rule>" msgstr "" #. Tag: title #, no-c-format -msgid "9am-5pm, Mon-Friday" +msgid "9am-5pm Monday-Friday" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"rule3\">\n" " <date_expression id=\"date_expr3\" operation=\"date_spec\">\n" " <date_spec hours=\"9-16\" days=\"1-5\"/>\n" " </date_expression>\n" "</rule>" msgstr "" #. Tag: para #, no-c-format msgid "Please note that the 16 matches up to 16:59:59, as the numeric value (hour) still matches!" msgstr "" #. Tag: title #, no-c-format -msgid "9am-6pm, Mon-Friday, or all day saturday" +msgid "9am-6pm Monday through Friday or anytime Saturday" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"rule4\" boolean_op=\"or\">\n" " <date_expression id=\"date_expr4-1\" operation=\"date_spec\">\n" " <date_spec hours=\"9-16\" days=\"1-5\"/>\n" " </date_expression>\n" " <date_expression id=\"date_expr4-2\" operation=\"date_spec\">\n" " <date_spec days=\"6\"/>\n" " </date_expression>\n" "</rule>" msgstr "" #. Tag: title #, no-c-format -msgid "9am-5pm or 9pm-12pm, Mon-Friday" +msgid "9am-5pm or 9pm-12am Monday through Friday" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"rule5\" boolean_op=\"and\">\n" " <rule id=\"rule5-nested1\" boolean_op=\"or\">\n" " <date_expression id=\"date_expr5-1\" operation=\"date_spec\">\n" " <date_spec hours=\"9-16\"/>\n" " </date_expression>\n" " <date_expression id=\"date_expr5-2\" operation=\"date_spec\">\n" " <date_spec hours=\"21-23\"/>\n" " </date_expression>\n" " </rule>\n" " <date_expression id=\"date_expr5-3\" operation=\"date_spec\">\n" " <date_spec days=\"1-5\"/>\n" " </date_expression>\n" " </rule>" msgstr "" #. Tag: title #, no-c-format msgid "Mondays in March 2005" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"rule6\" boolean_op=\"and\">\n" " <date_expression id=\"date_expr6-1\" operation=\"date_spec\">\n" " <date_spec weekdays=\"1\"/>\n" " </date_expression>\n" " <date_expression id=\"date_expr6-2\" operation=\"in_range\"\n" " start=\"2005-03-01\" end=\"2005-04-01\"/>\n" " </rule>" msgstr "" #. Tag: para #, no-c-format -msgid "Because no time is specified, 00:00:00 is implied." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "This means that the range includes all of 2005-03-01 but none of 2005-04-01. You may wish to write end=\"2005-03-31T23:59:59\" to avoid confusion." +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 end=\"2005-03-31T23:59:59\" to avoid confusion." msgstr "" #. Tag: title #, no-c-format msgid "A full moon on Friday the 13th" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"rule7\" boolean_op=\"and\">\n" " <date_expression id=\"date_expr7\" operation=\"date_spec\">\n" " <date_spec weekdays=\"5\" monthdays=\"13\" moon=\"4\"/>\n" " </date_expression>\n" "</rule>" msgstr "" #. Tag: title #, no-c-format msgid "Using Rules to Determine Resource Location" msgstr "" #. Tag: para #, no-c-format msgid " RuleDetermine Resource Location Determine Resource Location ResourceLocationDetermine by Rules LocationDetermine by Rules Determine by Rules " msgstr "" #. Tag: para #, no-c-format -msgid "If the constraint’s outer-most rule evaluates to false, the cluster treats the constraint as if it was not there. When the rule evaluates to true, the node’s preference for running the resource is updated with the score associated with the rule." +msgid "A location constraint may contain rules. When the constraint’s outermost rule evaluates to false, the cluster treats the constraint as if it were not there. When the rule evaluates to true, 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, its because you have been using a simplified syntax for location constraint rules already. Consider the following location constraint:" +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 "<rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\"\n" " score=\"-INFINITY\" node=\"c001n03\"/>" 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 "<rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\">\n" " <rule id=\"dont-run-apache-rule\" score=\"-INFINITY\">\n" " <expression id=\"dont-run-apache-expr\" attribute=\"#uname\"\n" " operation=\"eq\" value=\"c00n03\"/>\n" " </rule>\n" "</rsc_location>" 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 (this is discussed in subsequent sections)." +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 "It also 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:" +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 "<nodes>\n" " <node id=\"uuid1\" uname=\"c001n01\" type=\"normal\">\n" " <instance_attributes id=\"uuid1-custom_attrs\">\n" " <nvpair id=\"uuid1-cpu_mips\" name=\"cpu_mips\" value=\"1234\"/>\n" " </instance_attributes>\n" " </node>\n" " <node id=\"uuid2\" uname=\"c001n02\" type=\"normal\">\n" " <instance_attributes id=\"uuid2-custom_attrs\">\n" " <nvpair id=\"uuid2-cpu_mips\" name=\"cpu_mips\" value=\"5678\"/>\n" " </instance_attributes>\n" " </node>\n" "</nodes>" msgstr "" #. Tag: para #, no-c-format -msgid "then we could prevent resources from running on underpowered machines with the rule" +msgid "then we could prevent resources from running on underpowered machines with this rule:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rule id=\"need-more-power-rule\" score=\"-INFINITY\">\n" -" <expression id=\" need-more-power-expr\" attribute=\"cpu_mips\"\n" +" <expression id=\"need-more-power-expr\" attribute=\"cpu_mips\"\n" " operation=\"lt\" value=\"3000\"/>\n" "</rule>" msgstr "" #. Tag: title #, no-c-format msgid "Using score-attribute Instead of score" msgstr "" #. Tag: para #, no-c-format msgid "When using score-attribute instead of score, 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 score-attribute=\"cpu_mips\", c001n01 would have its preference to run the resource increased by 1234 whereas c001n02 would have its preference increased by 5678." 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 (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." +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 instance_attributes 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, mySpecialRsc will use eth1 and port 9999 when run on node1, eth2 and port 8888 on node2 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 "<primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\">\n" " <instance_attributes id=\"special-node1\" score=\"3\">\n" " <rule id=\"node1-special-case\" score=\"INFINITY\" >\n" " <expression id=\"node1-special-case-expr\" attribute=\"#uname\"\n" " operation=\"eq\" value=\"node1\"/>\n" " </rule>\n" " <nvpair id=\"node1-interface\" name=\"interface\" value=\"eth1\"/>\n" " </instance_attributes>\n" " <instance_attributes id=\"special-node2\" score=\"2\" >\n" " <rule id=\"node2-special-case\" score=\"INFINITY\">\n" " <expression id=\"node2-special-case-expr\" attribute=\"#uname\"\n" " operation=\"eq\" value=\"node2\"/>\n" " </rule>\n" " <nvpair id=\"node2-interface\" name=\"interface\" value=\"eth2\"/>\n" " <nvpair id=\"node2-port\" name=\"port\" value=\"8888\"/>\n" " </instance_attributes>\n" " <instance_attributes id=\"defaults\" score=\"1\" >\n" " <nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/>\n" " <nvpair id=\"default-port\" name=\"port\" value=\"9999\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format -msgid "The order in which instance_attributes 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 instance_attributes object does not have a rule or has a rule that evaluates to true, then for any parameter the resource does not yet have a value for, the resource will use the parameter values defined by the instance_attributes object." +msgid "The order in which instance_attributes 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 instance_attributes object has no rule or a rule that evaluates to true, then for any parameter the resource does not yet have a value for, the resource will use the parameter values defined by the instance_attributes." +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 "special-node1 has the highest score (3) and so is evaluated first; its rule evaluates to true, so interface is set to eth1." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "special-node2 is evaluated next with score 2, but its rule evaluates to false, so it is ignored." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "defaults is evaluated last with score 1, and has no rule, so its values are examined; interface is already defined, so the value here is not used, but port is not yet defined, so port is set to 9999." msgstr "" #. Tag: title #, no-c-format msgid "Using Rules to Control Cluster Options" msgstr "" #. Tag: para #, no-c-format msgid " RuleControlling Cluster Options Controlling Cluster Options ClusterSetting Options with Rules Setting Options with Rules " 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 resource-stickiness value during and outside of 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." +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 resource-stickiness 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 resource-stickiness during working hours" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_defaults>\n" " <meta_attributes id=\"core-hours\" score=\"2\">\n" " <rule id=\"core-hour-rule\" score=\"0\">\n" " <date_expression id=\"nine-to-five-Mon-to-Fri\" operation=\"date_spec\">\n" " <date_spec id=\"nine-to-five-Mon-to-Fri-spec\" hours=\"9-16\" weekdays=\"1-5\"/>\n" " </date_expression>\n" " </rule>\n" " <nvpair id=\"core-stickiness\" name=\"resource-stickiness\" value=\"INFINITY\"/>\n" " </meta_attributes>\n" " <meta_attributes id=\"after-hours\" score=\"1\" >\n" " <nvpair id=\"after-stickiness\" name=\"resource-stickiness\" value=\"0\"/>\n" " </meta_attributes>\n" "</rsc_defaults>" msgstr "" #. Tag: title #, no-c-format -msgid "Ensuring Time Based Rules Take Effect" +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 in 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." +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, it is essential that you set the cluster-recheck-interval option. This tells the cluster to periodically recalculate the ideal state of the cluster. For example, if you set cluster-recheck-interval=5m, then sometime between 9:00 and 9: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." +msgid "If you rely on time-based rules, the cluster-recheck-interval 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 "Note that the timing of the actual start and stop actions depends on what else needs to be performed first ." +msgid "For example, if you set cluster-recheck-interval=\"5m\", 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 e59239e3e3..8c4f651df1 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Status.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Status.pot @@ -1,642 +1,632 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +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 crm_mon." 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 " NodeStatus Status Status of a Node " 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 status section." +msgid "In addition to the cluster’s configuration, the CIB holds an up-to-date representation of each cluster node in the status section." msgstr "" #. Tag: title #, no-c-format -msgid "A bare-bones status entry for a healthy node called cl-virt-1" +msgid "A bare-bones status entry for a healthy node cl-virt-1" msgstr "" #. Tag: programlisting #, no-c-format msgid " <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\">\n" " <transient_attributes id=\"cl-virt-1\"/>\n" " <lrm id=\"cl-virt-1\"/>\n" " </node_state>" msgstr "" #. Tag: para #, no-c-format -msgid "Users are highly recommended not to modify any part of a node’s state directly. The cluster will periodically regenerate the entire section from authoritative sources. So any changes should be done with the tools for those subsystems." +msgid "Users are highly recommended not to modify any part of a node’s state directly. 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 "Dataset" +msgid "CIB Object" msgstr "" #. Tag: entry #, no-c-format msgid "Authoritative Source" msgstr "" #. Tag: para #, no-c-format -msgid "node_state fields" +msgid "node_state" msgstr "" #. Tag: para #, no-c-format msgid "crmd" msgstr "" #. Tag: para #, no-c-format -msgid "transient_attributes tag" +msgid "transient_attributes" msgstr "" #. Tag: para #, no-c-format msgid "attrd" msgstr "" #. Tag: para #, no-c-format -msgid "lrm tag" +msgid "lrm" msgstr "" #. Tag: para #, no-c-format msgid "lrmd" msgstr "" #. Tag: para #, no-c-format -msgid "The fields used in the node_state objects are named as they are largely for historical reasons and are rooted in Pacemaker’s origins as the Heartbeat resource manager." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "They have remained unchanged to preserve compatibility with older versions." +msgid "The fields used in the node_state 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." 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 "id" msgstr "" #. Tag: para #, no-c-format -msgid " idNode Status Node Status NodeStatusid Statusid id Unique identifier for the node. Corosync based clusters use the uname of the machine, Heartbeat clusters use a human-readable (but annoying) UUID." +msgid " idNode Status Node Status NodeStatusid Statusid id Unique identifier for the node. Corosync-based clusters use a numeric counter, while Heartbeat clusters use a (barely) human-readable UUID." msgstr "" #. Tag: para #, no-c-format msgid "uname" msgstr "" #. Tag: para #, no-c-format msgid " unameNode Status Node Status NodeStatusuname Statusuname uname The node’s machine name (output from uname -n)." msgstr "" #. Tag: para #, no-c-format msgid "ha" msgstr "" #. Tag: para #, no-c-format -msgid " haNode Status Node Status NodeStatusha Statusha ha Flag specifying whether the cluster software is active on the node. Allowed values: active, dead." +msgid " haNode Status Node Status NodeStatusha Statusha ha Is the cluster software active on this node? Allowed values: active, dead." msgstr "" #. Tag: para #, no-c-format msgid "in_ccm" msgstr "" #. Tag: para #, no-c-format -msgid " in_ccmNode Status Node Status NodeStatusin_ccm Statusin_ccm in_ccm Flag for cluster membership; allowed values: true, false." +msgid " in_ccmNode Status Node Status NodeStatusin_ccm Statusin_ccm in_ccm Is the node a member of the cluster? Allowed values: true, false." msgstr "" #. Tag: para #, no-c-format msgid "crmd" msgstr "" #. Tag: para #, no-c-format -msgid " crmdNode Status Node Status NodeStatuscrmd Statuscrmd crmd Flag: is the crmd process active on the node? One of online, offline." +msgid " crmdNode Status Node Status NodeStatuscrmd Statuscrmd crmd Is the crmd process active on the node? Allowed values: online, offline." msgstr "" #. Tag: para #, no-c-format msgid "join" msgstr "" #. Tag: para #, no-c-format -msgid " joinNode Status Node Status NodeStatusjoin Statusjoin join Flag saying whether the node participates in hosting resources. Possible values: down, pending, member, banned." +msgid " joinNode Status Node Status NodeStatusjoin Statusjoin join Does the node participate in hosting resources? Allowed values: down, pending, member, banned." msgstr "" #. Tag: para #, no-c-format msgid "expected" msgstr "" #. Tag: para #, no-c-format msgid " expectedNode Status Node Status NodeStatusexpected Statusexpected expected Expected value for join." msgstr "" #. Tag: para #, no-c-format msgid "crm-debug-origin" msgstr "" #. Tag: para #, no-c-format -msgid " crm-debug-originNode Status Node Status NodeStatuscrm-debug-origin Statuscrm-debug-origin crm-debug-origin Diagnostic indicator: the origin of the most recent change(s)." +msgid " crm-debug-originNode Status Node Status NodeStatuscrm-debug-origin Statuscrm-debug-origin crm-debug-origin 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 if, at the node level, the node is healthy or is in a failed state and needs to be fenced." +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 node attributes, the name/value pairs listed here also 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) until the next reboot." +msgid "Like regular node attributes, the name/value pairs listed in the transient_attributes 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 "Example set of transient node attributes for node \"cl-virt-1\"" +msgid "A set of transient node attributes for node cl-virt-1" msgstr "" #. Tag: programlisting #, no-c-format -msgid " <transient_attributes id=\"cl-virt-1\">\n" -" <instance_attributes id=\"status-cl-virt-1\">\n" -" <nvpair id=\"status-cl-virt-1-pingd\" name=\"pingd\" value=\"3\"/>\n" -" <nvpair id=\"status-cl-virt-1-probe_complete\" name=\"probe_complete\" value=\"true\"/>\n" -" <nvpair id=\"status-cl-virt-1-fail-count-pingd:0\" name=\"fail-count-pingd:0\" value=\"1\"/>\n" -" <nvpair id=\"status-cl-virt-1-last-failure-pingd:0\" name=\"last-failure-pingd:0\" value=\"1239009742\"/>\n" -" </instance_attributes>\n" -" </transient_attributes>" +msgid "<transient_attributes id=\"cl-virt-1\">\n" +" <instance_attributes id=\"status-cl-virt-1\">\n" +" <nvpair id=\"status-cl-virt-1-pingd\" name=\"pingd\" value=\"3\"/>\n" +" <nvpair id=\"status-cl-virt-1-probe_complete\" name=\"probe_complete\" value=\"true\"/>\n" +" <nvpair id=\"status-cl-virt-1-fail-count-pingd:0\" name=\"fail-count-pingd:0\" value=\"1\"/>\n" +" <nvpair id=\"status-cl-virt-1-last-failure-pingd:0\" name=\"last-failure-pingd:0\" value=\"1239009742\"/>\n" +" </instance_attributes>\n" +"</transient_attributes>" msgstr "" #. Tag: para #, no-c-format -msgid "In the above example, we can see that the pingd:0 resource has failed once, at Mon Apr 6 11:22:22 2009. You can use the standard date command to print a human readable of any seconds-since-epoch value: # date -d @<parameter>number</parameter> We also see that the node is connected to three \"pingd\" peers and that all known resources have been checked for on this machine (probe_complete)." +msgid "In the above example, we can see that the pingd:0 resource has failed once, at 09:22:22 UTC 6 April 2009. You can use the standard date command to print a human-readable version of any seconds-since-epoch value, for example date -d @1239009742. We also see that the node is connected to three pingd peers and that all known resources have been checked for on this machine (probe_complete)." msgstr "" #. Tag: title #, no-c-format msgid "Operation History" msgstr "" #. Tag: para #, no-c-format msgid " Operation History " msgstr "" #. Tag: para #, no-c-format -msgid "A node’s resource history is held in the lrm_resources tag (a child of the lrm tag). The information stored here includes enough information for the cluster to stop the resource safely if it is removed from the configuration section. Specifically the resource’s id, class, type and provider are stored." +msgid "A node’s resource history is held in the lrm_resources tag (a child of the lrm tag). The information stored here includes enough information for the cluster to stop the resource safely if it is removed from the configuration section. Specifically, the resource’s id, class, type and provider are stored." msgstr "" #. Tag: title #, no-c-format -msgid "A record of the apcstonith resource" +msgid "A record of the apcstonith resource" msgstr "" #. Tag: programlisting #, no-c-format msgid "<lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\"/>" msgstr "" #. Tag: para #, no-c-format -msgid "Additionally, we store the last job for every combination of resource, action and interval. The concatenation of the values in this tuple are used to create the id of the lrm_rsc_op object." +msgid "Additionally, we store the last job for every combination of resource, action and interval. The concatenation of the values in this tuple are used to create the id of the lrm_rsc_op object." msgstr "" #. Tag: title #, no-c-format msgid "Contents of an lrm_rsc_op job" msgstr "" #. Tag: para #, no-c-format msgid " idAction Status Action Status ActionStatusid Statusid id " msgstr "" #. Tag: para #, no-c-format msgid "Identifier for the job constructed from the resource’s id, operation and interval." msgstr "" #. Tag: para #, no-c-format msgid "call-id" msgstr "" #. Tag: para #, no-c-format msgid " call-idAction Status Action Status ActionStatuscall-id Statuscall-id call-id " 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 "operation" msgstr "" #. Tag: para #, no-c-format msgid " operationAction Status Action Status ActionStatusoperation Statusoperation operation " msgstr "" #. Tag: para #, no-c-format msgid "The action the resource agent was invoked with." msgstr "" #. Tag: para #, no-c-format msgid "interval" msgstr "" #. Tag: para #, no-c-format msgid " intervalAction Status Action Status ActionStatusinterval Statusinterval interval " 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 "op-status" msgstr "" #. Tag: para #, no-c-format msgid " op-statusAction Status Action Status ActionStatusop-status Statusop-status op-status " 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 rc-code." msgstr "" #. Tag: para #, no-c-format msgid "rc-code" msgstr "" #. Tag: para #, no-c-format msgid " rc-codeAction Status Action Status ActionStatusrc-code Statusrc-code rc-code " msgstr "" #. Tag: para #, no-c-format msgid "The job’s result. Refer to for details on what the values here mean and how they are interpreted." msgstr "" #. Tag: para #, no-c-format msgid "last-run" msgstr "" #. Tag: para #, no-c-format msgid " last-runAction Status Action Status ActionStatuslast-run Statuslast-run last-run " msgstr "" #. Tag: para #, no-c-format -msgid "Diagnostic indicator. Machine local date/time, in seconds since epoch, at which the job was executed." +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 "last-rc-change" msgstr "" #. Tag: para #, no-c-format msgid " last-rc-changeAction Status Action Status ActionStatuslast-rc-change Statuslast-rc-change last-rc-change " msgstr "" #. Tag: para #, no-c-format -msgid "Diagnostic indicator. Machine local date/time, in seconds since epoch, at which the job first returned the current value of rc-code." +msgid "Machine-local date/time, in seconds since epoch, at which the job first returned the current value of rc-code. For diagnostic purposes." msgstr "" #. Tag: para #, no-c-format msgid "exec-time" msgstr "" #. Tag: para #, no-c-format msgid " exec-timeAction Status Action Status ActionStatusexec-time Statusexec-time exec-time " msgstr "" #. Tag: para #, no-c-format -msgid "Diagnostic indicator. Time, in milliseconds, that the job was running for." +msgid "Time, in milliseconds, that the job was running for. For diagnostic purposes." msgstr "" #. Tag: para #, no-c-format msgid "queue-time" msgstr "" #. Tag: para #, no-c-format msgid " queue-timeAction Status Action Status ActionStatusqueue-time Statusqueue-time queue-time " msgstr "" #. Tag: para #, no-c-format -msgid "Diagnostic indicator. Time, in seconds, that the job was queued for in the LRMd." +msgid "Time, in seconds, that the job was queued for in the LRMd. For diagnostic purposes." msgstr "" #. Tag: para #, no-c-format msgid "crm_feature_set" msgstr "" #. Tag: para #, no-c-format msgid " crm_feature_setAction Status Action Status ActionStatuscrm_feature_set Statuscrm_feature_set crm_feature_set " msgstr "" #. Tag: para #, no-c-format msgid "The version which this job description conforms to. Used when processing op-digest." msgstr "" #. Tag: para #, no-c-format msgid "transition-key" msgstr "" #. Tag: para #, no-c-format msgid " transition-keyAction Status Action Status ActionStatustransition-key Statustransition-key transition-key " 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 transition-magic (below)." msgstr "" #. Tag: para #, no-c-format msgid "transition-magic" msgstr "" #. Tag: para #, no-c-format msgid " transition-magicAction Status Action Status ActionStatustransition-magic Statustransition-magic transition-magic " msgstr "" #. Tag: para #, no-c-format msgid "A concatenation of the job’s op-status, rc-code and transition-key. 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." msgstr "" #. Tag: para #, no-c-format msgid "op-digest" msgstr "" #. Tag: para #, no-c-format msgid " op-digestAction Status Action Status ActionStatusop-digest Statusop-digest op-digest " 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 " crm-debug-originAction Status Action Status ActionStatuscrm-debug-origin Statuscrm-debug-origin crm-debug-origin " msgstr "" #. Tag: para #, no-c-format -msgid "Diagnostic indicator. The origin of the current values." +msgid "The origin of the current values. For diagnostic purposes." msgstr "" #. Tag: title #, no-c-format -msgid "Simple Example" +msgid "Simple Operation History Example" msgstr "" #. Tag: title #, no-c-format -msgid "A monitor operation (determines current state of the apcstonith resource)" +msgid "A monitor operation (determines current state of the apcstonith resource)" msgstr "" #. Tag: programlisting #, no-c-format msgid "<lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\">\n" " <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\"/>\n" "</lrm_resource>" 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 apcstonith resource." msgstr "" #. Tag: para #, no-c-format -msgid "The cluster schedules probes for every configured resource on when a new node starts, in order to determine the resource’s current state before it takes any further action." +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 transition-key, 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)." msgstr "" #. Tag: para #, no-c-format -msgid "The third field of the transition-key contains a 7, this indicates that the job expects to find the resource inactive." -msgstr "" - -#. Tag: para -#, no-c-format -msgid "By looking at the rc-code property, we see that this was the case." +msgid "The third field of the transition-key contains a 7, which indicates that the job expects to find the resource inactive. By looking at the rc-code 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." +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 Resource History Example" +msgid "Complex Operation History Example" msgstr "" #. Tag: title #, no-c-format -msgid "Resource history of a pingd clone with multiple jobs" +msgid "Resource history of a pingd clone with multiple jobs" msgstr "" #. Tag: programlisting #, no-c-format msgid "<lrm_resource id=\"pingd:0\" type=\"pingd\" class=\"ocf\" provider=\"pacemaker\">\n" " <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\"/>\n" " <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\"/>\n" " <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\" />\n" " <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\"/>\n" " </lrm_resource>" msgstr "" #. Tag: para #, no-c-format msgid "When more than one job record exists, it is important to first sort them by call-id 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 call-id of 3" msgstr "" #. Tag: para #, no-c-format msgid "A stop operation returning 0 (success), with a call-id of 32" msgstr "" #. Tag: para #, no-c-format msgid "A start operation returning 0 (success), with a call-id of 33" msgstr "" #. Tag: para #, no-c-format msgid "A recurring monitor returning 0 (success), with a call-id 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." +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 stop operation with a lower call-id than that of the start 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 2668bbeb…. 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 7a178365ae..d3ef340bed 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Stonith.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Stonith.pot @@ -1,293 +1,1262 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +msgid "STONITH" msgstr "" #. Tag: para #, no-c-format msgid " STONITHConfiguration Configuration " msgstr "" #. Tag: title #, no-c-format -msgid "What Is STONITH" +msgid "What Is STONITH?" msgstr "" #. Tag: para #, no-c-format -msgid "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access." +msgid "STONITH (an acronym for \"Shoot The Other Node In The Head\"), also called fencing, 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" +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 remote power switch (such as many on-board IMPI 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." +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 started 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 verified instances, which are the ones that are started 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 "target-role 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 man stonithd 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" +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 "stonith-timeout" +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 pcmk_reboot_timeout and pcmk_off_timeout properties. stonith-timeoutFencing Fencing FencingPropertystonith-timeout Propertystonith-timeout stonith-timeout " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "priority" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "integer" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "0" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The priority of the STONITH resource. Devices are tried in order of highest priority to lowest. priorityFencing Fencing FencingPropertypriority Propertypriority priority " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_host_map" +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: node1:1;node2:2,3 tells the cluster to use port 1 for node1 and ports 2 and 3 for node2. pcmk_host_mapFencing Fencing FencingPropertypcmk_host_map Propertypcmk_host_map pcmk_host_map " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_host_list" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A list of machines controlled by this device (optional unless pcmk_host_check is static-list). pcmk_host_listFencing Fencing FencingPropertypcmk_host_list Propertypcmk_host_list pcmk_host_list " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_host_check" +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 "dynamic-list: query the device" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "static-list: check the pcmk_host_list attribute" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "none: assume every device can fence every machine" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pcmk_host_checkFencing Fencing FencingPropertypcmk_host_check Propertypcmk_host_check pcmk_host_check " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_delay_max" +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pcmk_delay_maxFencing Fencing FencingPropertypcmk_delay_max Propertypcmk_delay_max pcmk_delay_max " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_action_limit" +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 concurrent-fencing is true. -1 is unlimited." +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pcmk_action_limitFencing Fencing FencingPropertypcmk_action_limit Propertypcmk_action_limit pcmk_action_limit " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_host_argument" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "port" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Which parameter should be supplied to the resource agent to identify the node to be fenced. Some devices do not support the standard port parameter or may provide additional ones. Use this to specify an alternate, device-specific parameter. A value of none tells the cluster not to supply any additional parameters. pcmk_host_argumentFencing Fencing FencingPropertypcmk_host_argument Propertypcmk_host_argument pcmk_host_argument " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_reboot_action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "reboot" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. 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. pcmk_reboot_actionFencing Fencing FencingPropertypcmk_reboot_action Propertypcmk_reboot_action pcmk_reboot_action " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_reboot_timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "60s" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Specify an alternate timeout to use for reboot actions instead of the value of stonith-timeout. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. pcmk_reboot_timeoutFencing Fencing FencingPropertypcmk_reboot_timeout Propertypcmk_reboot_timeout pcmk_reboot_timeout stonith-timeoutFencing Fencing FencingPropertystonith-timeout Propertystonith-timeout stonith-timeout " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_reboot_retries" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "2" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. The maximum number of times to retry the reboot 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. pcmk_reboot_retriesFencing Fencing FencingPropertypcmk_reboot_retries Propertypcmk_reboot_retries pcmk_reboot_retries " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_off_action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "off" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. 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. pcmk_off_actionFencing Fencing FencingPropertypcmk_off_action Propertypcmk_off_action pcmk_off_action " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_off_timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Specify an alternate timeout to use for off actions instead of the value of stonith-timeout. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. pcmk_off_timeoutFencing Fencing FencingPropertypcmk_off_timeout Propertypcmk_off_timeout pcmk_off_timeout stonith-timeoutFencing Fencing FencingPropertystonith-timeout Propertystonith-timeout stonith-timeout " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_off_retries" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. The maximum number of times to retry the off 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. pcmk_off_retriesFencing Fencing FencingPropertypcmk_off_retries Propertypcmk_off_retries pcmk_off_retries " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_list_action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "list" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. 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. pcmk_list_actionFencing Fencing FencingPropertypcmk_list_action Propertypcmk_list_action pcmk_list_action " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_list_timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Specify an alternate timeout to use for list actions instead of the value of stonith-timeout. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. pcmk_list_timeoutFencing Fencing FencingPropertypcmk_list_timeout Propertypcmk_list_timeout pcmk_list_timeout " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_list_retries" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. The maximum number of times to retry the list 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. pcmk_list_retriesFencing Fencing FencingPropertypcmk_list_retries Propertypcmk_list_retries pcmk_list_retries " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_monitor_action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "monitor" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. 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. pcmk_monitor_actionFencing Fencing FencingPropertypcmk_monitor_action Propertypcmk_monitor_action pcmk_monitor_action " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_monitor_timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Specify an alternate timeout to use for monitor actions instead of the value of stonith-timeout. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. pcmk_monitor_timeoutFencing Fencing FencingPropertypcmk_monitor_timeout Propertypcmk_monitor_timeout pcmk_monitor_timeout " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_monitor_retries" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. The maximum number of times to retry the monitor 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. pcmk_monitor_retriesFencing Fencing FencingPropertypcmk_monitor_retries Propertypcmk_monitor_retries pcmk_monitor_retries " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_status_action" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "status" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. 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. pcmk_status_actionFencing Fencing FencingPropertypcmk_status_action Propertypcmk_status_action pcmk_status_action " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_status_timeout" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. Specify an alternate timeout to use for status actions instead of the value of stonith-timeout. Some devices need much more or less time to complete than normal. Use this to specify an alternate, device-specific timeout. pcmk_status_timeoutFencing Fencing FencingPropertypcmk_status_timeout Propertypcmk_status_timeout pcmk_status_timeout " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pcmk_status_retries" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Advanced use only. The maximum number of times to retry the status 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. pcmk_status_retriesFencing Fencing FencingPropertypcmk_status_retries Propertypcmk_status_retries pcmk_status_retries " +msgstr "" + #. Tag: title #, no-c-format msgid "Configuring STONITH" msgstr "" #. Tag: para #, no-c-format -msgid "Find the correct driver: stonith_admin --list-installed" +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 Clusters from Scratch 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 stonith.xml containing a primitive resource with a class of stonith, 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 pcmk_host_map parameter. See man stonithd for details." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If the device does not support the list command, you may also need to set the special pcmk_host_list and/or pcmk_host_check parameters. See man stonithd for details." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If the device does not expect the victim to be specified with the port parameter, you may also need to set the special pcmk_host_argument parameter. See man stonithd 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 stonith-enabled 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 "Since every device is different, the parameters needed to configure it will vary. To find out the parameters associated with the device, run: stonith_admin --metadata --agent type" +msgid "Assume we have an chassis containing four nodes and an IPMI device active on 192.0.2.1. We would choose the fence_ipmilan 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: literallayout +#. Tag: programlisting #, no-c-format -msgid "The output should be XML formatted text containing additional\n" -"parameter descriptions. We will endevor to make the output more\n" -"friendly in a later version." +msgid "<resource-agent name=\"fence_ipmilan\" shortdesc=\"Fence agent for IPMI over LAN\">\n" +" <symlink name=\"fence_ilo3\" shortdesc=\"Fence agent for HP iLO3\"/>\n" +" <symlink name=\"fence_ilo4\" shortdesc=\"Fence agent for HP iLO4\"/>\n" +" <symlink name=\"fence_idrac\" shortdesc=\"Fence agent for Dell iDRAC\"/>\n" +" <symlink name=\"fence_imm\" shortdesc=\"Fence agent for IBM Integrated Management Module\"/>\n" +" <longdesc>\n" +" </longdesc>\n" +" <vendor-url>\n" +" </vendor-url>\n" +" <parameters>\n" +" <parameter name=\"auth\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-A\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"ipaddr\" unique=\"0\" required=\"1\">\n" +" <getopt mixed=\"-a\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"passwd\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-p\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"passwd_script\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-S\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"lanplus\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-P\"/>\n" +" <content type=\"boolean\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"login\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-l\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"action\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-o\"/>\n" +" <content type=\"string\" default=\"reboot\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"timeout\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-t\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"cipher\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-C\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"method\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-M\"/>\n" +" <content type=\"string\" default=\"onoff\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"power_wait\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-T\"/>\n" +" <content type=\"string\" default=\"2\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"delay\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-f\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"privlvl\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-L\"/>\n" +" <content type=\"string\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" <parameter name=\"verbose\" unique=\"0\" required=\"0\">\n" +" <getopt mixed=\"-v\"/>\n" +" <content type=\"boolean\"/>\n" +" <shortdesc>\n" +" </shortdesc>\n" +" </parameter>\n" +" </parameters>\n" +" <actions>\n" +" <action name=\"on\"/>\n" +" <action name=\"off\"/>\n" +" <action name=\"reboot\"/>\n" +" <action name=\"status\"/>\n" +" <action name=\"diag\"/>\n" +" <action name=\"list\"/>\n" +" <action name=\"monitor\"/>\n" +" <action name=\"metadata\"/>\n" +" <action name=\"stop\" timeout=\"20s\"/>\n" +" <action name=\"start\" timeout=\"20s\"/>\n" +" </actions>\n" +"</resource-agent>" msgstr "" #. Tag: para #, no-c-format -msgid "Enter the shell crm Create an editable copy of the existing configuration cib new stonith Create a fencing resource containing a primitive resource with a class of stonith, a type of type and a parameter for each of the values returned in step 2: configure primitive …" +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 "<primitive id=\"Fencing\" class=\"stonith\" type=\"fence_ipmilan\" >\n" +" <instance_attributes id=\"Fencing-params\" >\n" +" <nvpair id=\"Fencing-passwd\" name=\"passwd\" value=\"testuser\" />\n" +" <nvpair id=\"Fencing-login\" name=\"login\" value=\"abc123\" />\n" +" <nvpair id=\"Fencing-ipaddr\" name=\"ipaddr\" value=\"192.0.2.1\" />\n" +" <nvpair id=\"Fencing-pcmk_host_list\" name=\"pcmk_host_list\" value=\"pcmk-1 pcmk-2\" />\n" +" </instance_attributes>\n" +" <operations >\n" +" <op id=\"Fencing-monitor-10m\" interval=\"10m\" name=\"monitor\" timeout=\"300s\" />\n" +" </operations>\n" +"</primitive>" 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 pcmk_host_map parameter. See man stonithd for details." +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 Not true, since a node or resource must fail before fencing even has a chance to; 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 fencing topologies." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Simply create the individual devices as you normally would, then define one or more fencing-level entries in the fencing-topology section of the configuration." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Each fencing level is attempted in order of ascending index. Allowed indexes are 0 to 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 crmd." msgstr "" #. Tag: para #, no-c-format -msgid "If the device does not support the list command, you may also need to set the special pcmk_host_list and/or pcmk_host_check parameters. See man stonithd for details." +msgid "Some possible uses of topologies include:" msgstr "" #. Tag: para #, no-c-format -msgid "If the device does not expect the victim to be specified with the port parameter, you may also need to set the special pcmk_host_argument parameter. See man stonithd for details." +msgid "Try poison-pill and fail back to power" msgstr "" #. Tag: para #, no-c-format -msgid "Upload it into the CIB from the shell: cib commit stonith" +msgid "Try disk and network, and fall back to power if either fails" msgstr "" #. Tag: para #, no-c-format -msgid "Once the stonith resource is running, you can test it by executing: stonith_admin --reboot nodename. Although you might want to stop the cluster on that machine first." +msgid "Initiate a kdump and then poweroff the node" msgstr "" #. Tag: title #, no-c-format -msgid "Example" +msgid "Properties of Fencing Levels" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "id" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A unique name for the level idfencing-level fencing-level Fencingfencing-levelid fencing-levelid id " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "target" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The name of a single node to which this level applies targetfencing-level fencing-level Fencingfencing-leveltarget fencing-leveltarget target " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "target-pattern" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A regular expression matching the names of nodes to which this level applies (since 1.1.14) target-patternfencing-level fencing-level Fencingfencing-leveltarget-pattern fencing-leveltarget-pattern target-pattern " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "target-attribute" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The name of a node attribute that is set for nodes to which this level applies (since 1.1.14) target-attributefencing-level fencing-level Fencingfencing-leveltarget-attribute fencing-leveltarget-attribute target-attribute " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "index" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The order in which to attempt the levels. Levels are attempted in ascending order until one succeeds. indexfencing-level fencing-level Fencingfencing-levelindex fencing-levelindex index " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "devices" msgstr "" #. Tag: para #, no-c-format -msgid "Assuming we have an chassis containing four nodes and an IPMI device active on 10.0.0.1, then we would chose the fence_ipmilan driver in step 2 and obtain the following list of parameters" +msgid "A comma-separated list of devices that must all be tried for this level devicesfencing-level fencing-level Fencingfencing-leveldevices fencing-leveldevices devices " msgstr "" #. Tag: title #, no-c-format -msgid "Obtaining a list of STONITH Parameters" +msgid "Fencing topology with different devices for different nodes" msgstr "" #. Tag: programlisting #, no-c-format -msgid "# stonith_admin --metadata -a fence_ipmilan" +msgid " <cib crm_feature_set=\"3.0.6\" validate-with=\"pacemaker-1.2\" admin_epoch=\"1\" epoch=\"0\" num_updates=\"0\">\n" +" <configuration>\n" +" ...\n" +" <fencing-topology>\n" +" <!-- For pcmk-1, try poison-pill and fail back to power -->\n" +" <fencing-level id=\"f-p1.1\" target=\"pcmk-1\" index=\"1\" devices=\"poison-pill\"/>\n" +" <fencing-level id=\"f-p1.2\" target=\"pcmk-1\" index=\"2\" devices=\"power\"/>\n" +"\n" +" <!-- For pcmk-2, try disk and network, and fail back to power -->\n" +" <fencing-level id=\"f-p2.1\" target=\"pcmk-2\" index=\"1\" devices=\"disk,network\"/>\n" +" <fencing-level id=\"f-p2.2\" target=\"pcmk-2\" index=\"2\" devices=\"power\"/>\n" +" </fencing-topology>\n" +" ...\n" +" <configuration>\n" +" <status/>\n" +"</cib>" +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 fencing-topology 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 fence_ipmi agent" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "the second fencing method uses the fence_apc_snmp 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 fence_ipmi to try to kill the faulty node. Using a fencing topology, if that first method fails, STONITH will then move on to selecting fence_apc_snmp 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, fence_ipmi, 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 "<?xml version=\"1.0\" ?>\n" -"<resource-agent name=\"fence_ipmilan\" shortdesc=\"Fence agent for IPMI over LAN\">\n" -"<longdesc>\n" -"fence_ipmilan is an I/O Fencing agent which can be used with machines controlled by IPMI. This agent calls support software using ipmitool (http://ipmitool.sf.net/).\n" -"\n" -"To use fence_ipmilan with HP iLO 3 you have to enable lanplus option (lanplus / -P) and increase wait after operation to 4 seconds (power_wait=4 / -T 4)</longdesc>\n" -"<parameters>\n" -" <parameter name=\"auth\" unique=\"1\">\n" -" <getopt mixed=\"-A\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>IPMI Lan Auth type (md5, password, or none)</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"ipaddr\" unique=\"1\">\n" -" <getopt mixed=\"-a\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>IPMI Lan IP to talk to</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"passwd\" unique=\"1\">\n" -" <getopt mixed=\"-p\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>Password (if required) to control power on IPMI device</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"passwd_script\" unique=\"1\">\n" -" <getopt mixed=\"-S\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>Script to retrieve password (if required)</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"lanplus\" unique=\"1\">\n" -" <getopt mixed=\"-P\" />\n" -" <content type=\"boolean\" />\n" -" <shortdesc>Use Lanplus</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"login\" unique=\"1\">\n" -" <getopt mixed=\"-l\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>Username/Login (if required) to control power on IPMI device</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"action\" unique=\"1\">\n" -" <getopt mixed=\"-o\" />\n" -" <content type=\"string\" default=\"reboot\"/>\n" -" <shortdesc>Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"timeout\" unique=\"1\">\n" -" <getopt mixed=\"-t\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>Timeout (sec) for IPMI operation</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"cipher\" unique=\"1\">\n" -" <getopt mixed=\"-C\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>Ciphersuite to use (same as ipmitool -C parameter)</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"method\" unique=\"1\">\n" -" <getopt mixed=\"-M\" />\n" -" <content type=\"string\" default=\"onoff\"/>\n" -" <shortdesc>Method to fence (onoff or cycle)</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"power_wait\" unique=\"1\">\n" -" <getopt mixed=\"-T\" />\n" -" <content type=\"string\" default=\"2\"/>\n" -" <shortdesc>Wait X seconds after on/off operation</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"delay\" unique=\"1\">\n" -" <getopt mixed=\"-f\" />\n" -" <content type=\"string\" />\n" -" <shortdesc>Wait X seconds before fencing is started</shortdesc>\n" -" </parameter>\n" -" <parameter name=\"verbose\" unique=\"1\">\n" -" <getopt mixed=\"-v\" />\n" -" <content type=\"boolean\" />\n" -" <shortdesc>Verbose mode</shortdesc>\n" -" </parameter>\n" -"</parameters>\n" -"<actions>\n" -" <action name=\"on\" />\n" -" <action name=\"off\" />\n" -" <action name=\"reboot\" />\n" -" <action name=\"status\" />\n" -" <action name=\"diag\" />\n" -" <action name=\"list\" />\n" -" <action name=\"monitor\" />\n" -" <action name=\"metadata\" />\n" -"</actions>\n" -"</resource-agent>" +msgid "<primitive class=\"stonith\" id=\"fence_prod-mysql1_ipmi\" type=\"fence_ipmilan\">\n" +" <instance_attributes id=\"fence_prod-mysql1_ipmi-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/>\n" +" </instance_attributes>\n" +"</primitive>\n" +"<primitive class=\"stonith\" id=\"fence_prod-mysql2_ipmi\" type=\"fence_ipmilan\">\n" +" <instance_attributes id=\"fence_prod-mysql2_ipmi-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.2\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/>\n" +" </instance_attributes>\n" +"</primitive>" +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 "from which we would create a STONITH resource fragment that might look like this" +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 "<primitive class=\"stonith\" id=\"fence_prod-mysql1_apc1\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql1_apc1-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-port\" name=\"port\" value=\"10\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/>\n" +" </instance_attributes>\n" +"</primitive>\n" +"<primitive class=\"stonith\" id=\"fence_prod-mysql1_apc2\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql1_apc2-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-port\" name=\"port\" value=\"10\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/>\n" +" </instance_attributes>\n" +"</primitive>\n" +"<primitive class=\"stonith\" id=\"fence_prod-mysql2_apc1\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql2_apc1-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-port\" name=\"port\" value=\"11\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/>\n" +" </instance_attributes>\n" +"</primitive>\n" +"<primitive class=\"stonith\" id=\"fence_prod-mysql2_apc2\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql2_apc2-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-port\" name=\"port\" value=\"11\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/>\n" +" </instance_attributes>\n" +"</primitive>" +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 "<constraints>\n" +" <rsc_location id=\"l_fence_prod-mysql1_ipmi\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_ipmi\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql2_ipmi\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_ipmi\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql1_apc2\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc2\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql1_apc1\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc1\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql2_apc1\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc1\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql2_apc2\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc2\" score=\"-INFINITY\"/>\n" +"</constraints>" msgstr "" #. Tag: title #, no-c-format -msgid "Sample STONITH Resource" +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 "# crm crm(live)# cib new stonith\n" -"INFO: stonith shadow CIB created\n" -"crm(stonith)# configure primitive impi-fencing stonith::fence_ipmilan \\\n" -" params pcmk_host_list=\"pcmk-1 pcmk-2\" ipaddr=10.0.0.1 login=testuser passwd=abc123 \\\n" -" op monitor interval=\"60s\"" +msgid "<fencing-topology>\n" +" <fencing-level devices=\"fence_prod-mysql1_ipmi\" id=\"fencing-2\" index=\"1\" target=\"prod-mysql1\"/>\n" +" <fencing-level devices=\"fence_prod-mysql1_apc1,fence_prod-mysql1_apc2\" id=\"fencing-3\" index=\"2\" target=\"prod-mysql1\"/>\n" +" <fencing-level devices=\"fence_prod-mysql2_ipmi\" id=\"fencing-0\" index=\"1\" target=\"prod-mysql2\"/>\n" +" <fencing-level devices=\"fence_prod-mysql2_apc1,fence_prod-mysql2_apc2\" id=\"fencing-1\" index=\"2\" target=\"prod-mysql2\"/>\n" +"</fencing-topology>" msgstr "" #. Tag: para #, no-c-format -msgid "And finally, since we disabled it earlier, we need to re-enable STONITH. At this point we should have the following configuration." +msgid "Please note, in fencing-topology, the lowest index 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 "Now push the configuration into the cluster." +msgid "Put together, the configuration looks like this:" msgstr "" #. Tag: programlisting #, no-c-format -msgid "crm(stonith)# configure property stonith-enabled=\"true\"\n" -"crm(stonith)# configure shownode pcmk-1\n" -"node pcmk-2\n" -"primitive WebData ocf:linbit:drbd \\\n" -" params drbd_resource=\"wwwdata\" \\\n" -" op monitor interval=\"60s\"\n" -"primitive WebFS ocf:heartbeat:Filesystem \\\n" -" params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=\"gfs2\"\n" -"primitive WebSite ocf:heartbeat:apache \\\n" -" params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -" op monitor interval=\"1min\"\n" -"primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" -" params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" -" op monitor interval=\"30s\"primitive ipmi-fencing stonith::fence_ipmilan \\ params pcmk_host_list=\"pcmk-1 pcmk-2\" ipaddr=10.0.0.1 login=testuser passwd=abc123 \\ op monitor interval=\"60s\"ms WebDataClone WebData \\\n" -" meta master-max=\"2\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone WebFSClone WebFS\n" -"clone WebIP ClusterIP \\\n" -" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"\n" -"clone WebSiteClone WebSite\n" -"colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone\n" -"colocation fs_on_drbd inf: WebFSClone WebDataClone:Master\n" -"colocation website-with-ip inf: WebSiteClone WebIP\n" -"order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start\n" -"order WebSite-after-WebFS inf: WebFSClone WebSiteClone\n" -"order apache-after-ip inf: WebIP WebSiteClone\n" -"property $id=\"cib-bootstrap-options\" \\\n" -" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" -" cluster-infrastructure=\"openais\" \\\n" -" expected-quorum-votes=\"2\" \\\n" -" stonith-enabled=\"true\" \\\n" -" no-quorum-policy=\"ignore\"\n" -"rsc_defaults $id=\"rsc-options\" \\\n" -" resource-stickiness=\"100\"\n" -"crm(stonith)# cib commit stonithINFO: commited 'stonith' shadow CIB to the cluster\n" -"crm(stonith)# quit\n" -"bye" +msgid "<cib admin_epoch=\"0\" crm_feature_set=\"3.0.7\" epoch=\"292\" have-quorum=\"1\" num_updates=\"29\" validate-with=\"pacemaker-1.2\">\n" +" <configuration>\n" +" <crm_config>\n" +" <cluster_property_set id=\"cib-bootstrap-options\">\n" +" <nvpair id=\"cib-bootstrap-options-stonith-enabled\" name=\"stonith-enabled\" value=\"true\"/>\n" +" <nvpair id=\"cib-bootstrap-options-stonith-action\" name=\"stonith-action\" value=\"off\"/>\n" +" <nvpair id=\"cib-bootstrap-options-expected-quorum-votes\" name=\"expected-quorum-votes\" value=\"3\"/>\n" +" ...\n" +" </cluster_property_set>\n" +" </crm_config>\n" +" <nodes>\n" +" <node id=\"prod-mysql1\" uname=\"prod-mysql1\">\n" +" <node id=\"prod-mysql2\" uname=\"prod-mysql2\"/>\n" +" <node id=\"prod-mysql-rep1\" uname=\"prod-mysql-rep1\"/>\n" +" <instance_attributes id=\"prod-mysql-rep1\">\n" +" <nvpair id=\"prod-mysql-rep1-standby\" name=\"standby\" value=\"on\"/>\n" +" </instance_attributes>\n" +" </node>\n" +" </nodes>\n" +" <resources>\n" +" <primitive class=\"stonith\" id=\"fence_prod-mysql1_ipmi\" type=\"fence_ipmilan\">\n" +" <instance_attributes id=\"fence_prod-mysql1_ipmi-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +" <primitive class=\"stonith\" id=\"fence_prod-mysql2_ipmi\" type=\"fence_ipmilan\">\n" +" <instance_attributes id=\"fence_prod-mysql2_ipmi-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"192.0.2.2\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-passwd\" name=\"passwd\" value=\"finishme\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-verbose\" name=\"verbose\" value=\"true\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/>\n" +" <nvpair id=\"fence_prod-mysql2_ipmi-instance_attributes-lanplus\" name=\"lanplus\" value=\"true\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +" <primitive class=\"stonith\" id=\"fence_prod-mysql1_apc1\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql1_apc1-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-port\" name=\"port\" value=\"10\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +" <primitive class=\"stonith\" id=\"fence_prod-mysql1_apc2\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql1_apc2-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-port\" name=\"port\" value=\"10\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql1_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql1\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +" <primitive class=\"stonith\" id=\"fence_prod-mysql2_apc1\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql2_apc1-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"198.51.100.1\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-port\" name=\"port\" value=\"11\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc1-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +" <primitive class=\"stonith\" id=\"fence_prod-mysql2_apc2\" type=\"fence_apc_snmp\">\n" +" <instance_attributes id=\"fence_prod-mysql2_apc2-instance_attributes\">\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-ipaddr\" name=\"ipaddr\" value=\"203.0.113.1\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-action\" name=\"action\" value=\"off\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-port\" name=\"port\" value=\"11\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-login\" name=\"login\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-passwd\" name=\"passwd\" value=\"fencing\"/>\n" +" <nvpair id=\"fence_prod-mysql2_apc2-instance_attributes-pcmk_host_list\" name=\"pcmk_host_list\" value=\"prod-mysql2\"/>\n" +" </instance_attributes>\n" +" </primitive>\n" +" </resources>\n" +" <constraints>\n" +" <rsc_location id=\"l_fence_prod-mysql1_ipmi\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_ipmi\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql2_ipmi\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_ipmi\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql1_apc2\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc2\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql1_apc1\" node=\"prod-mysql1\" rsc=\"fence_prod-mysql1_apc1\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql2_apc1\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc1\" score=\"-INFINITY\"/>\n" +" <rsc_location id=\"l_fence_prod-mysql2_apc2\" node=\"prod-mysql2\" rsc=\"fence_prod-mysql2_apc2\" score=\"-INFINITY\"/>\n" +" </constraints>\n" +" <fencing-topology>\n" +" <fencing-level devices=\"fence_prod-mysql1_ipmi\" id=\"fencing-2\" index=\"1\" target=\"prod-mysql1\"/>\n" +" <fencing-level devices=\"fence_prod-mysql1_apc1,fence_prod-mysql1_apc2\" id=\"fencing-3\" index=\"2\" target=\"prod-mysql1\"/>\n" +" <fencing-level devices=\"fence_prod-mysql2_ipmi\" id=\"fencing-0\" index=\"1\" target=\"prod-mysql2\"/>\n" +" <fencing-level devices=\"fence_prod-mysql2_apc1,fence_prod-mysql2_apc2\" id=\"fencing-1\" index=\"2\" target=\"prod-mysql2\"/>\n" +" </fencing-topology>\n" +" ...\n" +" </configuration>\n" +"</cib>" +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 stonith-action is reboot or because a reboot was manually requested (such as by stonith_admin --reboot), 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 reboot command, the cluster will ask it to perform off 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 off, then ask the devices to perform on." +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 off commands succeed, because then it is safe for the cluster to recover any resources that were on the node. Timeouts and errors in the on 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, pcmk_off_timeout will be used when executing the off command, not pcmk_reboot_timeout)." +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 7e93931e23..ba87400325 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot @@ -1,342 +1,362 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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: title +#. Tag: para #, no-c-format -msgid "Background" +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 "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. 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 cib will be chosen to run the resource." +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 "Though resources are different. They may consume different amounts of the capacities of the nodes. Actually, we cannot ideally balance the load 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." +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 into account, Pacemaker allows you to specify the following configurations:" +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." +msgid "The capacity a certain node provides." msgstr "" #. Tag: para #, no-c-format -msgid "The capacity a certain resource requires." +msgid "The capacity a certain resource requires." msgstr "" #. Tag: para #, no-c-format -msgid "An overall strategy for placement of resources." +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 a node provides and the resource’s requirements, use utilization attributes. You can name the utilization attributes according to your preferences and define as many name/value pairs as your configuration needs. However, the attribute’s values must be integers." +msgid "To configure the capacity that a node provides or a resource requires, you can use utilization attributes in node and resource 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: para +#. Tag: title #, no-c-format -msgid "First, specify the capacities the nodes provide:" +msgid "Specifying CPU and RAM capacities of two nodes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<node id=\"node1\" type=\"normal\" uname=\"node1\">\n" " <utilization id=\"node1-utilization\">\n" " <nvpair id=\"node1-utilization-cpu\" name=\"cpu\" value=\"2\"/>\n" " <nvpair id=\"node1-utilization-memory\" name=\"memory\" value=\"2048\"/>\n" " </utilization>\n" "</node>\n" "<node id=\"node2\" type=\"normal\" uname=\"node2\">\n" " <utilization id=\"node2-utilization\">\n" " <nvpair id=\"node2-utilization-cpu\" name=\"cpu\" value=\"4\"/>\n" " <nvpair id=\"node2-utilization-memory\" name=\"memory\" value=\"4096\"/>\n" " </utilization>\n" "</node>" msgstr "" -#. Tag: para +#. Tag: title #, no-c-format -msgid "Then, specify the capacities the resources require:" +msgid "Specifying CPU and RAM consumed by several resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"rsc-small\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-small-utilization\">\n" " <nvpair id=\"rsc-small-utilization-cpu\" name=\"cpu\" value=\"1\"/>\n" " <nvpair id=\"rsc-small-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" "</primitive>\n" "<primitive id=\"rsc-medium\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-medium-utilization\">\n" " <nvpair id=\"rsc-medium-utilization-cpu\" name=\"cpu\" value=\"2\"/>\n" " <nvpair id=\"rsc-medium-utilization-memory\" name=\"memory\" value=\"2048\"/>\n" " </utilization>\n" "</primitive>\n" "<primitive id=\"rsc-large\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-large-utilization\">\n" " <nvpair id=\"rsc-large-utilization-cpu\" name=\"cpu\" value=\"3\"/>\n" " <nvpair id=\"rsc-large-utilization-memory\" name=\"memory\" value=\"3072\"/>\n" " </utilization>\n" "</primitive>" 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 for Pacemaker, it just makes sure that all capacity requirements of a resource are satisfied before placing a resource to a node." +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 placement-strategy in the global cluster options, otherwise the capacity configurations have no effect." +msgid "After you have configured the capacities your nodes provide and the capacities your resources require, you need to set the placement-strategy in the global cluster options, otherwise the capacity configurations have no effect." msgstr "" #. Tag: para #, no-c-format msgid "Four values are available for the placement-strategy:" msgstr "" #. Tag: term #, no-c-format msgid "default" msgstr "" #. Tag: para #, no-c-format -msgid "Utilization values are not taken into account at all, per default. Resources are allocated according to allocation scores. If scores are equal, resources are evenly distributed across nodes." +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 "utilization" msgstr "" #. Tag: para #, no-c-format -msgid "Utilization values are taken into account when deciding whether a node is considered eligible if it has sufficient free capacity to satisfy the resource’s requirements. However, load-balancing is still done based on the number of resources allocated to a node." +msgid "Utilization values are taken into account only 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 "balanced" msgstr "" #. Tag: para #, no-c-format -msgid "Utilization values are taken into account when deciding whether a node is eligible to serve a resource; an attempt is made to spread the resources evenly, optimizing resource performance." +msgid "Utilization values are taken into account when deciding whether a node is eligible to serve a resource and 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 "minimal" msgstr "" #. Tag: para #, no-c-format -msgid "Utilization values are taken into account when deciding whether a node is eligible to serve a resource; an attempt is made to concentrate the resources on as few nodes as possible, thereby enabling possible power savings on the remaining nodes." +msgid "Utilization values are taken into account only 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 placement-strategy with crm_attribute:" msgstr "" -#. Tag: programlisting +#. Tag: screen #, no-c-format -msgid "# crm_attribute --attr-name placement-strategy --attr-value balanced" +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." +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 be chosen to get consumed first on allocating resources?" +msgid "Which node is preferred to get consumed first when allocating resources?" msgstr "" #. Tag: para #, no-c-format -msgid "The node that is most healthy (which has the highest node weight) gets consumed first." +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 their weights are equal:" +msgid "If multiple nodes have the same node weight:" msgstr "" #. Tag: para #, no-c-format -msgid "If placement-strategy=\"default|utilization\", the node that has the least number of allocated resources gets consumed first." +msgid "If placement-strategy is default or utilization, 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 cib gets consumed first." +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 placement-strategy=\"balanced\", the node that has more free capacity gets consumed first." +msgid "If placement-strategy is balanced, 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 placement-strategy=\"minimal\", the first eligible node listed in cib gets consumed first." +msgid "If placement-strategy is minimal, 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 "This will be quite clear if we only define one type of capacity. While if we define multiple types of capacity, for example:" +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 nodeA has more free cpus, nodeB has more free memory, their free capacities are equal." +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 nodeA has more free cpus, while nodeB has more free memory and storage, nodeB has more free capacity." +msgid "If nodeA has more free cpus, and nodeB has more free memory, then their free capacities are equal." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If nodeA has more free cpus, while nodeB has more free memory and storage, then nodeB has more free capacity." msgstr "" #. Tag: title #, no-c-format -msgid "Which resource is preferred to be chosen to get assigned first?" +msgid "Which resource is preferred to be assigned first?" msgstr "" #. Tag: para #, no-c-format -msgid "The resource that has the highest priority gets allocated first." +msgid "The resource that has the highest priority (see ) gets allocated first." msgstr "" #. Tag: para #, no-c-format -msgid "If their priorities are equal, check if 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)." +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 they are not running, the resource has the highest score on the preferred node gets allocated first." +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 cib gets allocated first." +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" +msgid "Limitations and Workarounds" msgstr "" #. Tag: para #, no-c-format -msgid "This type of problem Pacemaker is dealing with here is known as the knapsack problem and falls into the NP-complete category of computer science problems - which is fancy way of saying \"it takes a really long time to solve\"." +msgid "The type of problem Pacemaker is dealing with here is known as the knapsack problem and falls into the NP-complete 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 optional solution while services remain unavailable." msgstr "" #. Tag: para #, no-c-format msgid "So instead of trying to solve the problem completely, Pacemaker uses a best effort 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 above:" +msgid "In the contrived example at the start of this section:" msgstr "" #. Tag: para #, no-c-format msgid "rsc-small would be allocated to node1" msgstr "" #. Tag: para #, no-c-format msgid "rsc-medium would be allocated to node2" msgstr "" #. Tag: para #, no-c-format msgid "rsc-large would remain inactive" msgstr "" #. Tag: para #, no-c-format msgid "Which is not ideal." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Strategies for Dealing with the Limitations" +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 "Ensure you have sufficient physical capacity. It might sounds 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'." +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 "Build some buffer into the capabilities advertised by the nodes. Advertise slightly more resources than we physically have on the (usually valid) assumption that a resource will not use 100% of the configured number of cpu/memory/etc all the time. This practice is also known as over commit." +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 all the time. This practice is sometimes called overcommit." +msgstr "" + +#. Tag: term +#, no-c-format +msgid "Specify resource priorities." msgstr "" #. Tag: para #, no-c-format -msgid "Specify resource priorities. If the cluster is going to sacrifice services, it should be the ones you care (comparatively) about the least. Ensure that resource priorities are properly set so that your most important resources are scheduled first." +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 400f42de82..f715ca374e 100644 --- a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot +++ b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot @@ -1,59 +1,44 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "Receiving Notification for Cluster Events" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Configuring Email Notifications" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Configuring SNMP Notifications" -msgstr "" - #. Tag: title #, no-c-format msgid "Further Reading" msgstr "" #. Tag: para #, no-c-format -msgid "Project Website " +msgid "Project Website: " msgstr "" #. Tag: para #, no-c-format -msgid "Project Documentation " +msgid "Project Documentation: " msgstr "" #. Tag: para #, no-c-format -msgid "A comprehensive guide to cluster commands has been written by Novell" +msgid "SUSE High Availibility Guide: " msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat configuration: " msgstr "" #. Tag: para #, no-c-format msgid "Corosync Configuration: " msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Preface.pot b/doc/Pacemaker_Explained/pot/Preface.pot index bcd9cb577f..01aa1cc95d 100644 --- a/doc/Pacemaker_Explained/pot/Preface.pot +++ b/doc/Pacemaker_Explained/pot/Preface.pot @@ -1,19 +1,19 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 8b19d38ba8..886c776f17 100644 --- a/doc/Pacemaker_Explained/pot/Revision_History.pot +++ b/doc/Pacemaker_Explained/pot/Revision_History.pot @@ -1,54 +1,79 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:02\n" -"PO-Revision-Date: 2012-10-17T05:19:02\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 Publican" msgstr "" #. Tag: member #, no-c-format msgid "Converted to asciidoc (which is converted to docbook for use with Publican)" 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 "" + diff --git a/doc/Pacemaker_Remote/en-US/Book_Info.xml b/doc/Pacemaker_Remote/en-US/Book_Info.xml index 12e1ab891d..1e3675b9d1 100644 --- a/doc/Pacemaker_Remote/en-US/Book_Info.xml +++ b/doc/Pacemaker_Remote/en-US/Book_Info.xml @@ -1,75 +1,75 @@ %BOOK_ENTITIES; ]> Pacemaker Remote Scaling High Availablity Clusters - 5 + 6 0 The document exists as both a reference and deployment guide for the Pacemaker Remote service. The example commands in this document will use: &DISTRO; &DISTRO_VERSION; as the host operating system Pacemaker Remote to perform resource management within guest nodes and remote nodes KVM for virtualization libvirt to manage guest nodes Corosync to provide messaging and membership services on cluster nodes Pacemaker to perform resource management on cluster nodes pcs as the cluster configuration toolset The concepts are the same for other distributions, virtualization platforms, toolsets, and messaging layers, and should be easily adaptable. diff --git a/doc/Pacemaker_Remote/en-US/Ch-Alternatives.txt b/doc/Pacemaker_Remote/en-US/Ch-Alternatives.txt index d2fd9f42fd..7cf45ab423 100644 --- a/doc/Pacemaker_Remote/en-US/Ch-Alternatives.txt +++ b/doc/Pacemaker_Remote/en-US/Ch-Alternatives.txt @@ -1,77 +1,78 @@ = Alternative Configurations = 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. == Virtual Machines as Cluster Nodes == 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. 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. 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. 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. == Virtual Machines as Remote Nodes == Virtual machines may be configured following the process for remote nodes rather than guest nodes (i.e., using an *ocf:pacemaker:remote* resource rather than letting the cluster manage the VM directly). 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. == Containers as Guest Nodes == Containers,footnote:[https://en.wikipedia.org/wiki/Operating-system-level_virtualization] and in particular Linux containers (LXC) and Docker, have become a popular method of isolating services in a resource-efficient manner. The preferred means of integrating containers into Pacemaker is as a cluster resource, whether opaque or using Pacemaker's built-in resource isolation support.footnote:[Documentation for this support is planned but not yet available.] However, it is possible to run `pacemaker_remote` 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. The configuration process is very similar to that described for guest nodes using virtual machines. Key differences: * The underlying host must install the libvirt driver for the desired container technology -- for example, the +libvirt-daemon-lxc+ package to get the http://libvirt.org/drvlxc.html:[libvirt-lxc] driver for LXC containers. * Libvirt XML definitions must be generated for the containers. The - +pacemaker-cts+ package includes a helpful script for this purpose, + +pacemaker-cts+ package includes a script for this purpose, +/usr/share/pacemaker/tests/cts/lxc_autogen.sh+. Run it with the - `--help` option for details on how to use it. Of course, you can create - XML definitions manually, following the appropriate libvirt driver - documentation. + `--help` 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. * To share the authentication key, either share the host's +/etc/pacemaker+ directory with the container, or copy the key into the container's filesystem. * The *VirtualDomain* resource for a container will need *force_stop="true"* and an appropriate hypervisor option, for example *hypervisor="lxc:///"* for LXC containers. diff --git a/doc/Pacemaker_Remote/en-US/Ch-Baremetal-Tutorial.txt b/doc/Pacemaker_Remote/en-US/Ch-Baremetal-Tutorial.txt index c187b2536f..f866c9a944 100644 --- a/doc/Pacemaker_Remote/en-US/Ch-Baremetal-Tutorial.txt +++ b/doc/Pacemaker_Remote/en-US/Ch-Baremetal-Tutorial.txt @@ -1,306 +1,310 @@ = Remote Node Walk-through = *What this tutorial is:* 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. *What this tutorial is not:* A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of remote nodes as quickly as possible. This tutorial requires three machines: two to act as cluster nodes, and a third to act as the remote node. == Configure Remote Node == === Configure Firewall on Remote Node === Allow cluster-related services through the local firewall: ---- # firewall-cmd --permanent --add-service=high-availability success # firewall-cmd --reload success ---- [NOTE] ====== 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. 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. To disable security measures: ---- # setenforce 0 # sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config # systemctl disable firewalld.service # systemctl stop firewalld.service # iptables --flush ---- ====== === Configure pacemaker_remote on Remote Node === Install the pacemaker_remote daemon on the remote node. ---- # yum install -y pacemaker-remote resource-agents pcs ---- Create a location for the shared authentication key: ---- # mkdir -p --mode=0750 /etc/pacemaker # chgrp haclient /etc/pacemaker ---- 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: ---- # dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1 ---- Now start and enable the pacemaker_remote daemon on the remote node. ---- # systemctl enable pacemaker_remote.service # systemctl start pacemaker_remote.service ---- Verify the start is successful. ---- # systemctl status pacemaker_remote pacemaker_remote.service - Pacemaker Remote Service Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled) Active: active (running) since Fri 2015-08-21 15:21:20 CDT; 20s ago Main PID: 21273 (pacemaker_remot) CGroup: /system.slice/pacemaker_remote.service └─21273 /usr/sbin/pacemaker_remoted Aug 21 15:21:20 remote1 systemd[1]: Starting Pacemaker Remote Service... Aug 21 15:21:20 remote1 systemd[1]: Started Pacemaker Remote Service. Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121. Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: bind_and_listen: Listening on address :: ---- == Verify Connection to Remote Node == 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. First, add the remote node's hostname (we're using *remote1* in this tutorial) to the cluster nodes' +/etc/hosts+ 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. Execute the following on each cluster node, replacing the IP address with the actual IP address of the remote node. ---- # cat << END >> /etc/hosts 192.168.122.10 remote1 END ---- If running the ssh command on one of the cluster nodes results in this -output before disconnecting, the connection works. +output before disconnecting, the connection works: ---- # ssh -p 3121 remote1 ssh_exchange_identification: read: Connection reset by peer ---- -If you see this, the connection is not working. +If you see one of these, the connection is not working: ---- # ssh -p 3121 remote1 ssh: connect to host remote1 port 3121: No route to host ---- +---- +# ssh -p 3121 remote1 +ssh: connect to host remote1 port 3121: Connection refused +---- Once you can successfully connect to the remote node from the both cluster nodes, move on to setting up Pacemaker on the cluster nodes. == Configure Cluster Nodes == === Configure Firewall on Cluster Nodes === On each cluster node, allow cluster-related services through the local firewall, following the same procedure as in <<_configure_firewall_on_remote_node>>. === Install Pacemaker on Cluster Nodes === On the two cluster nodes, install the following packages. ---- # yum install -y pacemaker corosync pcs resource-agents ---- === Copy Authentication Key to Cluster Nodes === Create a location for the shared authentication key, and copy it from any existing node: ---- # mkdir -p --mode=0750 /etc/pacemaker # chgrp haclient /etc/pacemaker # scp remote1:/etc/pacemaker/authkey /etc/pacemaker/authkey ---- === Configure Corosync on Cluster Nodes === Corosync handles Pacemaker's cluster membership and messaging. The corosync config file is located in +/etc/corosync/corosync.conf+. That config file must be initialized with information about the two cluster nodes before pacemaker can start. To initialize the corosync config file, execute the following pcs command on both nodes, filling in the information in <> with your nodes' information. ---- # pcs cluster setup --force --local --name mycluster ---- === Start Pacemaker on Cluster Nodes === Start the cluster stack on both cluster nodes using the following command. ---- # pcs cluster start ---- Verify corosync membership .... # pcs status corosync Membership information ---------------------- Nodeid Votes Name 1 1 node1 (local) .... Verify Pacemaker status. At first, the `pcs cluster status` output will look like this. ---- # pcs status Cluster name: mycluster Last updated: Fri Aug 21 16:14:05 2015 Last change: Fri Aug 21 14:02:14 2015 Stack: corosync Current DC: NONE Version: 1.1.12-a14efad 1 Nodes configured, unknown expected votes 0 Resources configured ---- After about a minute, you should see your two cluster nodes come online. ---- # pcs status Cluster name: mycluster Last updated: Fri Aug 21 16:16:32 2015 Last change: Fri Aug 21 14:02:14 2015 Stack: corosync Current DC: node1 (1) - partition with quorum Version: 1.1.12-a14efad 2 Nodes configured 0 Resources configured Online: [ node1 node2 ] ---- For the sake of this tutorial, we are going to disable stonith to avoid having to cover fencing device configuration. ---- # pcs property set stonith-enabled=false ---- == Integrate Remote Node into Cluster == 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 +/usr/lib/ocf/resource.d/pacemaker/remote+ file that describes what options are available, but there is no actual *ocf:pacemaker:remote* resource agent script that performs any work. Define the remote node connection resource to our remote node, *remote1*, using the following command on any cluster node. ---- # pcs resource create remote1 ocf:pacemaker:remote ---- That's it. After a moment you should see the remote node come online. ---- Cluster name: mycluster Last updated: Fri Aug 21 17:13:09 2015 Last change: Fri Aug 21 17:02:02 2015 Stack: corosync Current DC: node1 (1) - partition with quorum Version: 1.1.12-a14efad 3 Nodes configured 1 Resources configured Online: [ node1 node2 ] RemoteOnline: [ remote1 ] Full list of resources: remote1 (ocf::pacemaker:remote): Started node1 PCSD Status: node1: Online node2: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- == Starting Resources on Remote Node == 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 http://clusterlabs.org/doc/['Clusters from Scratch'] document for examples of resource creation. [WARNING] ========= Never involve a remote node connection resource in a resource group, colocation constraint, or order constraint. ========= == Fencing Remote Nodes == 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. Note, however, that remote nodes can never 'initiate' a fencing action. Only cluster nodes are capable of actually executing a fencing operation against another node. == Accessing Cluster Tools from a Remote Node == 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 (`crm_resource`, `crm_mon`, `crm_attribute`, `crm_master`, etc.) to work on remote nodes natively. Try it: Run `crm_mon` 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 `crm_master` work seamlessly on the remote nodes. Higher-level command shells such as `pcs` may have partial support on remote nodes, but it is recommended to run them from a cluster node. diff --git a/doc/Pacemaker_Remote/en-US/Ch-Intro.txt b/doc/Pacemaker_Remote/en-US/Ch-Intro.txt index 9edf054a69..416c19d880 100644 --- a/doc/Pacemaker_Remote/en-US/Ch-Intro.txt +++ b/doc/Pacemaker_Remote/en-US/Ch-Intro.txt @@ -1,198 +1,204 @@ = Scaling a Pacemaker Cluster = == Overview == In a basic Pacemaker high-availability cluster,footnote:[See the http://www.clusterlabs.org/doc/[Pacemaker documentation], especially 'Clusters From Scratch' and 'Pacemaker Explained', for basic information about high-availability using Pacemaker] each node runs the full cluster stack of corosync and all Pacemaker components. This allows great flexibility but limits scalability to around 16 nodes. 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. == Terms == cluster node:: 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 (`crm_mon`, `crm_resource` and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster's Designated Controller (DC). (((cluster node))) (((node,cluster node))) pacemaker_remote:: 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). (((pacemaker_remote))) remote node:: 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 'baremetal' case. (((remote node))) (((node,remote node))) guest node:: 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. (((guest node))) (((node,guest node))) [NOTE] ====== 'Remote' 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. ====== [NOTE] ====== It is important to distinguish the various roles a virtual machine can serve in Pacemaker clusters: * 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. * 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 'opaque' to the cluster. * 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 'transparent' to the cluster. ====== == Support in Pacemaker Versions == 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: +.1.1.15 +* 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. +* Bug fixes + .1.1.14 * Resources that create guest nodes can be included in groups * reconnect_interval option for remote nodes * Bug fixes, including a memory leak .1.1.13 * Support for maintenance mode * Remote nodes can recover without being fenced when the cluster node hosting their connection fails * Running pacemaker_remote within LXC environments is deprecated due to newly added Pacemaker support for isolated resources * Bug fixes .1.1.12 * Support for permanent node attributes * Support for migration * Bug fixes .1.1.11 * Support for IPv6 * Support for remote nodes * Support for transient node attributes * Support for clusters with mixed endian architectures * Bug fixes .1.1.10 * Bug fixes .1.1.9 * Initial version to include pacemaker_remote * Limited to guest nodes in KVM/LXC environments using only IPv4; all nodes' architectures must have same endianness == Guest Nodes == (((guest node))) (((node,guest node))) *"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."* Without pacemaker_remote, the possibilities for implementing the above use case have significant limitations: * The cluster stack could be run on the physical hosts only, which loses the ability to monitor resources within the guests. * A separate cluster could be on the virtual guests, which quickly hits scalability issues. * 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. With pacemaker_remote: * The physical hosts are cluster nodes (running the full cluster stack). * The virtual machines are guest nodes (running the pacemaker_remote service). Nearly zero configuration is required on the virtual machine. * 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. 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. 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. 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 `crm_mon` output as nodes. 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: * 16 cluster nodes running the full corosync + pacemaker stack * 64 Pacemaker-managed virtual machine resources running pacemaker_remote configured as guest nodes * 64 Pacemaker-managed webserver and database resources configured to run on the 64 guest nodes 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. == Remote Nodes == (((remote node))) (((node,remote node))) *"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer."* 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. Like guest nodes, remote nodes will never become the DC, initiate fencing actions or participate in quorum voting. 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. == Expanding the Cluster Stack == With pacemaker_remote, the traditional view of the high-availability stack can be expanded to include a new layer: .Traditional HA Stack image::images/pcmk-ha-cluster-stack.png["Traditional Pacemaker+Corosync Stack",width="17cm",height="9cm",align="center"] .HA Stack With Guest Nodes image::images/pcmk-ha-remote-stack.png["Pacemaker+Corosync Stack With pacemaker_remote",width="20cm",height="10cm",align="center"] diff --git a/doc/Pacemaker_Remote/en-US/Ch-KVM-Tutorial.txt b/doc/Pacemaker_Remote/en-US/Ch-KVM-Tutorial.txt index 72a9076592..7f09598e31 100644 --- a/doc/Pacemaker_Remote/en-US/Ch-KVM-Tutorial.txt +++ b/doc/Pacemaker_Remote/en-US/Ch-KVM-Tutorial.txt @@ -1,583 +1,583 @@ = Guest Node Walk-through = *What this tutorial is:* 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. *What this tutorial is not:* A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of guest nodes as quickly as possible. == Configure the Physical Host == [NOTE] ====== For this example, we will use a single physical host named *example-host*. A production cluster would likely have multiple physical hosts, in which case you would run the commands here on each one, unless noted otherwise. ====== === Configure Firewall on Host === On the physical host, allow cluster-related services through the local firewall: ---- # firewall-cmd --permanent --add-service=high-availability success # firewall-cmd --reload success ---- [NOTE] ====== 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. 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. To disable security measures: ---- [root@pcmk-1 ~]# setenforce 0 [root@pcmk-1 ~]# sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config [root@pcmk-1 ~]# systemctl disable firewalld.service [root@pcmk-1 ~]# systemctl stop firewalld.service [root@pcmk-1 ~]# iptables --flush ---- ====== === Install Cluster Software === ---- # yum install -y pacemaker corosync pcs resource-agents ---- === Configure Corosync === Corosync handles pacemaker's cluster membership and messaging. The corosync config file is located in +/etc/corosync/corosync.conf+. That config file must be initialized with information about the cluster nodes before pacemaker can start. To initialize the corosync config file, execute the following `pcs` command, replacing the cluster name and hostname as desired: ---- # pcs cluster setup --force --local --name mycluster example-host ---- [NOTE] ====== 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. ====== === Configure Pacemaker for Remote Node Communication === Create a place to hold an authentication key for use with pacemaker_remote: ---- # mkdir -p --mode=0750 /etc/pacemaker # chgrp haclient /etc/pacemaker ---- Generate a key: ---- # dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1 ---- [NOTE] ====== 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. ====== === Verify Cluster Software === Start the cluster ---- # pcs cluster start ---- Verify corosync membership .... # pcs status corosync Membership information ---------------------- Nodeid Votes Name 1 1 example-host (local) .... Verify pacemaker status. At first, the output will look like this: ---- # pcs status Cluster name: mycluster WARNING: no stonith devices and stonith-enabled is not false 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 Stack: corosync Current DC: NONE 1 node and 0 resources configured Node example-host: UNCLEAN (offline) Full list of resources: PCSD Status: example-host: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- After a short amount of time, you should see your host as a single node in the cluster: ---- # pcs status Cluster name: mycluster WARNING: no stonith devices and stonith-enabled is not false 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 Stack: corosync Current DC: example-host (version 1.1.13-a14efad) - partition WITHOUT quorum 1 node and 0 resources configured Online: [ example-host ] Full list of resources: PCSD Status: example-host: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- === Disable STONITH and Quorum === 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. ---- # pcs property set stonith-enabled=false # pcs property set no-quorum-policy=ignore ---- [WARNING] ========= The use of `stonith-enabled=false` 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. ========= Now, the status output should look similar to this: ---- # pcs status Cluster name: mycluster 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 Stack: corosync Current DC: example-host (version 1.1.13-a14efad) - partition with quorum 1 node and 0 resources configured Online: [ example-host ] Full list of resources: PCSD Status: example-host: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- Go ahead and stop the cluster for now after verifying everything is in order. ---- # pcs cluster stop --force ---- === Install Virtualization Software === ---- # yum install -y kvm libvirt qemu-system qemu-kvm bridge-utils virt-manager # systemctl enable libvirtd.service ---- Reboot the host. [NOTE] ====== 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 *remote-node* meta-attribute, independent of the agent. ====== == Configure the KVM guest == === Create Guest === 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). === Configure Firewall on Guest === On each guest, allow cluster-related services through the local firewall, following the same procedure as in <<_configure_firewall_on_host>>. === Verify Connectivity === At this point, you should be able to ping and ssh into guests from hosts, and vice versa. === Configure pacemaker_remote === 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. ---- # yum install -y pacemaker pacemaker-remote resource-agents # systemctl enable pacemaker_remote.service ---- Copy the authentication key from a host: ---- # mkdir -p --mode=0750 /etc/pacemaker # chgrp haclient /etc/pacemaker # scp root@example-host:/etc/pacemaker/authkey /etc/pacemaker ---- Start pacemaker_remote, and verify the start was successful: ---- # systemctl start pacemaker_remote # systemctl status pacemaker_remote pacemaker_remote.service - Pacemaker Remote Service Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled) Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago Main PID: 1233 (pacemaker_remot) CGroup: name=systemd:/system/pacemaker_remote.service └─1233 /usr/sbin/pacemaker_remoted Mar 14 18:24:04 guest1 systemd[1]: Starting Pacemaker Remote Service... Mar 14 18:24:04 guest1 systemd[1]: Started Pacemaker Remote Service. Mar 14 18:24:04 guest1 pacemaker_remoted[1233]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121. ---- === Verify Host Connection to Guest === 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. First add guest1 to the host machine's +/etc/hosts+ file if you haven't already. This is required unless you have DNS setup in a way where guest1's address can be discovered. ---- # cat << END >> /etc/hosts 192.168.122.10 guest1 END ---- If running the ssh command on one of the cluster nodes results in this -output before disconnecting, the connection works. +output before disconnecting, the connection works: ---- # ssh -p 3121 guest1 ssh_exchange_identification: read: Connection reset by peer ---- -If you see one of these, the connection is not working. +If you see one of these, the connection is not working: ---- # ssh -p 3121 guest1 ssh: connect to host guest1 port 3121: No route to host ---- ---- # ssh -p 3121 guest1 ssh: connect to host guest1 port 3121: Connection refused ---- 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. == Integrate Guest into Cluster == Now the fun part, integrating the virtual machine you've just created into the cluster. It is incredibly simple. === Start the Cluster === On the host, start pacemaker. ---- # pcs cluster start ---- Wait for the host to become the DC. The output of `pcs status` should look as it did in <<_disable_stonith_and_quorum>>. === Integrate as Guest Node === 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 +/etc/hosts+ file so we can connect by hostname. For this example: ---- # cat << END >> /etc/hosts 192.168.122.10 guest1 END ---- We will use the *VirtualDomain* 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. .... # virsh list --all Id Name State ---------------------------------------------------- - guest1 shut off .... In my case I named it guest1. Dump the xml to a file somewhere on the host using the following command. ---- # virsh dumpxml guest1 > /etc/pacemaker/guest1.xml ---- Now just register the resource with pacemaker and you're set! ---- # pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system" \ config="/etc/pacemaker/guest1.xml" meta remote-node=guest1 ---- [NOTE] ====== 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 `setenforce 0`. If it works after that, see SELinux documentation for how to troubleshoot, if you wish to reenable SELinux. ====== [NOTE] ====== Pacemaker will automatically monitor pacemaker_remote connections for failure, so it is not necessary to create a recurring monitor on the VirtualDomain resource. ====== Once the *vm-guest1* resource is started you will see *guest1* appear in the `pcs status` output as a node. The final `pcs status` output should look something like this. ---- # pcs status Cluster name: mycluster 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 Stack: corosync Current DC: example-host (version 1.1.13-a14efad) - partition with quorum 2 nodes and 2 resources configured Online: [ example-host ] GuestOnline: [ guest1@example-host ] Full list of resources: vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host PCSD Status: example-host: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- === Starting Resources on KVM Guest === The commands below demonstrate how resources can be executed on both the guest node and the cluster node. 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. ---- # pcs resource create FAKE1 ocf:pacemaker:Dummy # pcs resource create FAKE2 ocf:pacemaker:Dummy # pcs resource create FAKE3 ocf:pacemaker:Dummy # pcs resource create FAKE4 ocf:pacemaker:Dummy # pcs resource create FAKE5 ocf:pacemaker:Dummy ---- Now check your `pcs status` 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. ---- Full list of resources: vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host FAKE1 (ocf::pacemaker:Dummy): Started guest1 FAKE2 (ocf::pacemaker:Dummy): Started guest1 FAKE3 (ocf::pacemaker:Dummy): Started example-host FAKE4 (ocf::pacemaker:Dummy): Started guest1 FAKE5 (ocf::pacemaker:Dummy): Started example-host ---- The guest node, *guest1*, 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 *guest1* in the exact same way we would any other node. ---- # pcs constraint location FAKE3 prefers guest1 ---- Now, looking at the bottom of the `pcs status` output you'll see FAKE3 is on *guest1*. ---- Full list of resources: vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host FAKE1 (ocf::pacemaker:Dummy): Started guest1 FAKE2 (ocf::pacemaker:Dummy): Started guest1 FAKE3 (ocf::pacemaker:Dummy): Started guest1 FAKE4 (ocf::pacemaker:Dummy): Started example-host FAKE5 (ocf::pacemaker:Dummy): Started example-host ---- === Testing Recovery and Fencing === 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. ssh into the guest and run this command. ---- # kill -9 `pidof pacemaker_remoted` ---- Within a few seconds, your `pcs status` output will show a monitor failure, and the *guest1* node will not be shown while it is being recovered. ---- # pcs status Cluster name: mycluster 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 Stack: corosync Current DC: example-host (version 1.1.13-a14efad) - partition with quorum 2 nodes and 7 resources configured Online: [ example-host ] Full list of resources: vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host FAKE1 (ocf::pacemaker:Dummy): Stopped FAKE2 (ocf::pacemaker:Dummy): Stopped FAKE3 (ocf::pacemaker:Dummy): Stopped FAKE4 (ocf::pacemaker:Dummy): Started example-host FAKE5 (ocf::pacemaker:Dummy): Started example-host Failed Actions: * guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none', last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms PCSD Status: example-host: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- [NOTE] ====== 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 *remote-node* 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 *guest1* and not *vm-guest1*. ====== Once recovery of the guest is complete, you'll see it automatically get re-integrated into the cluster. The final `pcs status` output should look something like this. ---- Cluster name: mycluster 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 Stack: corosync Current DC: example-host (version 1.1.13-a14efad) - partition with quorum 2 nodes and 7 resources configured Online: [ example-host ] GuestOnline: [ guest1@example-host ] Full list of resources: vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host FAKE1 (ocf::pacemaker:Dummy): Started guest1 FAKE2 (ocf::pacemaker:Dummy): Started guest1 FAKE3 (ocf::pacemaker:Dummy): Started guest1 FAKE4 (ocf::pacemaker:Dummy): Started example-host FAKE5 (ocf::pacemaker:Dummy): Started example-host Failed Actions: * guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none', last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms PCSD Status: example-host: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled ---- 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: ---- # pcs resource disable vm-guest1 --wait # pcs resource cleanup guest1 # pcs resource enable vm-guest1 ---- === Accessing Cluster Tools from Guest Node === 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 (`crm_resource`, `crm_mon`, `crm_attribute`, `crm_master`, etc.) to work on guest nodes natively. Try it: Run `crm_mon` 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 `crm_master` work seamlessly on the guest nodes. Higher-level command shells such as `pcs` may have partial support on guest nodes, but it is recommended to run them from a cluster node. diff --git a/doc/Pacemaker_Remote/en-US/Revision_History.xml b/doc/Pacemaker_Remote/en-US/Revision_History.xml index 1954f14d96..b3d1fd285d 100644 --- a/doc/Pacemaker_Remote/en-US/Revision_History.xml +++ b/doc/Pacemaker_Remote/en-US/Revision_History.xml @@ -1,42 +1,49 @@ %BOOK_ENTITIES; ]> + Revision History 1-0 Tue Mar 19 2013 DavidVosseldavidvossel@gmail.com Import from Pages.app 2-0 Tue May 13 2013 DavidVosseldavidvossel@gmail.com Added Future Features Section 3-0 Fri Oct 18 2013 DavidVosseldavidvossel@gmail.com Added Baremetal remote-node feature documentation 4-0 Tue Aug 25 2015 KenGaillotkgaillot@redhat.com Targeted CentOS 7.1 and Pacemaker 1.1.12+, updated for current terminology and practice 5-0 Tue Dec 8 2015 KenGaillotkgaillot@redhat.com Updated for Pacemaker 1.1.14 + + 6-0 + Tue May 3 2016 + KenGaillotkgaillot@redhat.com + Updated for Pacemaker 1.1.15 + diff --git a/doc/Pacemaker_Remote/pot/Author_Group.pot b/doc/Pacemaker_Remote/pot/Author_Group.pot new file mode 100644 index 0000000000..3b4203d1d1 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Author_Group.pot @@ -0,0 +1,34 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 new file mode 100644 index 0000000000..d2a6a8e310 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Book_Info.pot @@ -0,0 +1,74 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +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 new file mode 100644 index 0000000000..f79938fd9c --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot @@ -0,0 +1,109 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 ocf:pacemaker:remote 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,https://en.wikipedia.org/wiki/Operating-system-level_virtualization 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 built-in resource isolation support.Documentation for this support is planned but not yet available." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "However, it is possible to run pacemaker_remote 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 libvirt-daemon-lxc package to get the libvirt-lxc driver for LXC containers." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Libvirt XML definitions must be generated for the containers. The pacemaker-cts package includes a script for this purpose, /usr/share/pacemaker/tests/cts/lxc_autogen.sh. Run it with the --help 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 /etc/pacemaker directory with the container, or copy the key into the container’s filesystem." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The VirtualDomain resource for a container will need force_stop=\"true\" and an appropriate hypervisor option, for example hypervisor=\"lxc:///\" for LXC containers." +msgstr "" + diff --git a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot new file mode 100644 index 0000000000..1d1bc56c28 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot @@ -0,0 +1,458 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "What this tutorial is: 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 "What this tutorial is not: 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 disable 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" +" Main PID: 21273 (pacemaker_remot)\n" +" CGroup: /system.slice/pacemaker_remote.service\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 ::" +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 remote1 in this tutorial) to the cluster nodes' /etc/hosts 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 << END >> /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 ." +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 /etc/corosync/corosync.conf. 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 <> with your nodes' information." +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "# pcs cluster setup --force --local --name mycluster <node1 ip or hostname> <node2 ip or hostname>" +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 pcs cluster status 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" +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" +"\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 /usr/lib/ocf/resource.d/pacemaker/remote file that describes what options are available, but there is no actual ocf:pacemaker:remote resource agent script that performs any work." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Define the remote node connection resource to our remote node, remote1, 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" +"\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 Clusters from Scratch 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 initiate 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 (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on remote nodes natively." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Try it: Run crm_mon 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 crm_master work seamlessly on the remote nodes." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Higher-level command shells such as pcs 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 new file mode 100644 index 0000000000..869200d5a5 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Ch-Example.pot @@ -0,0 +1,174 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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. guest node nodeguest node guest node " +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 /etc/pacemaker/authkey 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 remote-node 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 " <primitive class=\"ocf\" id=\"vm-guest1\" provider=\"heartbeat\" type=\"VirtualDomain\">\n" +" <instance_attributes id=\"vm-guest-instance_attributes\">\n" +" <nvpair id=\"vm-guest1-instance_attributes-hypervisor\" name=\"hypervisor\" value=\"qemu:///system\"/>\n" +" <nvpair id=\"vm-guest1-instance_attributes-config\" name=\"config\" value=\"guest1.xml\"/>\n" +" </instance_attributes>\n" +" <operations>\n" +" <op id=\"vm-guest1-interval-30s\" interval=\"30s\" name=\"monitor\"/>\n" +" </operations>\n" +" <meta_attributes id=\"vm-guest1-meta_attributes\">\n" +" <nvpair id=\"vm-guest1-meta_attributes-remote-node\" name=\"remote-node\" value=\"guest1\"/>\n" +" </meta_attributes>\n" +" </primitive>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the example above, the meta-attribute remote-node=\"guest1\" tells Pacemaker that this resource is a guest node with the hostname guest1. The cluster will attempt to contact the virtual machine’s pacemaker_remote service at the hostname guest1 after it launches." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The ID of the resource creating the virtual machine (vm-guest1 in the above example) must be different from the virtual machine’s uname (guest1 in the above example). Pacemaker will create an implicit internal resource for the pacemaker_remote connection to the guest, named with the value of remote-node, 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 crm_mon output as normal:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example crm_mon output after guest1 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" +"\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 guest1:" +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" +"\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 guest1 is integrated into the cluster, nearly all the Pacemaker command-line tools immediately become available to the guest node. This means things like crm_mon, crm_resource, and crm_attribute 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 crm_master to set transient attributes." +msgstr "" + diff --git a/doc/Pacemaker_Remote/pot/Ch-Intro.pot b/doc/Pacemaker_Remote/pot/Ch-Intro.pot new file mode 100644 index 0000000000..4616770a77 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Ch-Intro.pot @@ -0,0 +1,374 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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,See the Pacemaker documentation, especially Clusters From Scratch and Pacemaker Explained, for basic information about high-availability using Pacemaker 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 (crm_mon, crm_resource and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster’s Designated Controller (DC). cluster node nodecluster node cluster node " +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). pacemaker_remote " +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 baremetal case. remote node noderemote node remote node " +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. guest node nodeguest node guest node " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Remote 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 opaque 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 transparent 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:" +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: para +#, no-c-format +msgid "Bug fixes" +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: para +#, no-c-format +msgid "Bug fixes, including a memory leak" +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 "Running pacemaker_remote within LXC environments is deprecated due to newly added Pacemaker support for isolated resources" +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: 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 " guest node nodeguest node guest node " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "\"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.\"" +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 crm_mon 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 " remote node noderemote node remote node " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "\"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer.\"" +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." +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 new file mode 100644 index 0000000000..ae9f3718b9 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot @@ -0,0 +1,767 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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 "What this tutorial is: 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 "What this tutorial is not: 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 example-host. 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 disable 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 /etc/corosync/corosync.conf. 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 pcs 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" +"\n" +"Node example-host: UNCLEAN (offline)\n" +"\n" +"Full list of resources:\n" +"\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: 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" +"\n" +"Full list of resources:\n" +"\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 "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 stonith-enabled=false 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" +"\n" +"Full list of resources:\n" +"\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: 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 remote-node 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 ." +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" +"\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." +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 /etc/hosts 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 << END >> /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 pcs status should look as it did in ." +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 /etc/hosts file so we can connect by hostname. For this example:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "We will use the VirtualDomain 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 > /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 setenforce 0. 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 vm-guest1 resource is started you will see guest1 appear in the pcs status output as a node. The final pcs status 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" +"\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 pcs status 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, guest1, 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 guest1 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 pcs status output you’ll see FAKE3 is on guest1." +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." +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`" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Within a few seconds, your pcs status output will show a monitor failure, and the guest1 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" +"\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" +"\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 remote-node 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 guest1 and not vm-guest1." +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 pcs status 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" +"\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" +"\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 (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on guest nodes natively." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Try it: Run crm_mon 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 crm_master work seamlessly on the guest nodes." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Higher-level command shells such as pcs 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 new file mode 100644 index 0000000000..a16b6653d3 --- /dev/null +++ b/doc/Pacemaker_Remote/pot/Ch-Options.pot @@ -0,0 +1,222 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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. configuration " +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 to use as a guest node, these are the metadata options available to enable the 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 "remote-node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "none" +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 must not overlap with any resource or node IDs." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "remote-port" +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 "remote-addr" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "value of remote-node" +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 "remote-connect-timeout" +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 pcs 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: Time in seconds to wait before attempting to reconnect to\n" +" a remote node after an active connection to the remote\n" +" node has been severed. This wait is recurring. If\n" +" reconnect fails after the wait period, a new reconnect\n" +" attempt will be made after observing the wait time. When\n" +" this option is in use, pacemaker will keep attempting to\n" +" reach out and connect to the remote node indefinitely\n" +" after each wait interval." +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 server 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 remote1:" +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 TLS-PSK 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 /etc/pacemaker/authkey 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. These environment variables can be enabled by placing them in the /etc/sysconfig/pacemaker 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 ocf:pacemaker:remote 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 the node’s resource has been deleted from the configuration first." +msgstr "" + diff --git a/doc/Clusters_from_Scratch/pot/Revision_History.pot b/doc/Pacemaker_Remote/pot/Revision_History.pot similarity index 62% copy from doc/Clusters_from_Scratch/pot/Revision_History.pot copy to doc/Pacemaker_Remote/pot/Revision_History.pot index b4f86a7373..707c7a7ee7 100644 --- a/doc/Clusters_from_Scratch/pot/Revision_History.pot +++ b/doc/Pacemaker_Remote/pot/Revision_History.pot @@ -1,84 +1,69 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2012-10-17T05:19:03\n" -"PO-Revision-Date: 2012-10-17T05:19:03\n" +"POT-Creation-Date: 2016-05-03 17:45-0500\n" +"PO-Revision-Date: 2016-05-03 17:45-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" +msgid "David" msgstr "" #. Tag: surname #, no-c-format -msgid "Beekhof" +msgid "Vossel" 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" +msgid "Added Future Features Section" msgstr "" #. Tag: member #, no-c-format -msgid "Updated for Fedora 13" +msgid "Added Baremetal remote-node feature documentation" msgstr "" -#. Tag: member +#. Tag: firstname #, no-c-format -msgid "Update the GFS2 section to use CMAN" +msgid "Ken" msgstr "" -#. Tag: member +#. Tag: surname #, no-c-format -msgid "Generate docbook content from asciidoc sources" +msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format -msgid "Updated for Fedora 17" +msgid "Targeted CentOS 7.1 and Pacemaker 1.1.12+, updated for current terminology and practice" msgstr "" -#. Tag: firstname -#, no-c-format -msgid "David" -msgstr "" - -#. Tag: surname +#. Tag: member #, no-c-format -msgid "Vossel" +msgid "Updated for Pacemaker 1.1.14" msgstr "" #. Tag: member #, no-c-format -msgid "Updated for pcs" +msgid "Updated for Pacemaker 1.1.15" msgstr ""