diff --git a/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot b/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot index 9000daba69..d2927808cb 100644 --- a/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot +++ b/doc/Clusters_from_Scratch/pot/Ap-Configuration.pot @@ -1,341 +1,261 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:26\n" -"PO-Revision-Date: 2010-12-21T11:01:26\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Configuration Recap" msgstr "" #. Tag: title #, no-c-format msgid "Final Cluster Configuration" msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebData ocf:linbit:drbd \\\n" -"        params drbd_resource=\"wwwdata\" \\\n" -"        op monitor interval=\"60s\"\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" +" 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" +" 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\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -"   params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -"        op monitor interval=\"120s\"\n" -"primitive rsa-fencing stonith::external/ibmrsa \\\n" -"        params hostname=”pcmk-1 pcmk-2\" ipaddr=192.168.122.31 userid=mgmt passwd=abc123 type=ibm \\\n" -"        op monitor interval=\"60s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" +" op monitor interval=\"30s\"\n" +"primitive ipmi-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\"\n" "ms WebDataClone WebData \\\n" -"        meta master-max=\"2\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone Fencing rsa-fencing \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 WebIP ClusterIP \\\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"\n" "clone WebSiteClone WebSite\n" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\"\n" -"clone gfs-clone gfs-control \\\n" -"        meta interleave=\"true\"\n" -"colocation WebFS-with-gfs-control inf: WebFSClone gfs-clone\n" "colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone\n" "colocation fs_on_drbd inf: WebFSClone WebDataClone:Master\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\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" -"order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=”true” \\\n" -"        no-quorum-policy=\"ignore\"\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" -"" +" resource-stickiness=\"100\"" 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: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"node pcmk-1\n" -"node pcmk-2\n" -"" +msgid "node pcmk-1\n" +"node pcmk-2" msgstr "" #. Tag: title #, no-c-format msgid "Cluster Options" msgstr "" #. Tag: para #, no-c-format msgid "This is where the cluster automatically stores some information about the cluster" msgstr "" #. Tag: para #, no-c-format msgid "dc-version - the version (including upstream source-code hash) of Pacemaker used on the DC" msgstr "" #. Tag: para #, no-c-format msgid "cluster-infrastructure - the cluster infrastructure being used (heartbeat or openais)" msgstr "" #. Tag: para #, no-c-format msgid "expected-quorum-votes - the maximum number of nodes expected to be part of the cluster" msgstr "" #. Tag: para #, no-c-format msgid "and where the admin can set options that control the way the cluster operates" msgstr "" #. Tag: para #, no-c-format msgid "stonith-enabled=true - Make use of STONITH" msgstr "" #. Tag: para #, no-c-format msgid "no-quorum-policy=ignore - Ignore loss of quorum and continue to host resources." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=”true” \\\n" -"        no-quorum-policy=\"ignore\"\n" -"" +msgid "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\"" msgstr "" #. Tag: title #, no-c-format msgid "Resources" msgstr "" #. Tag: title #, no-c-format msgid "Default Options" msgstr "" #. Tag: para #, no-c-format msgid "Here we configure cluster options that apply to every resource." msgstr "" #. Tag: para #, no-c-format msgid "resource-stickiness - Specify the aversion to moving resources to other machines" msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -"" +msgid "rsc_defaults $id=\"rsc-options\" \\\n" +" resource-stickiness=\"100\"" msgstr "" #. Tag: title #, no-c-format msgid "Fencing" msgstr "" #. Tag: para #, no-c-format msgid "TODO: Add text here" msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"primitive rsa-fencing stonith::external/ibmrsa \\\n" -"        params hostname=”pcmk-1 pcmk-2\" ipaddr=192.168.122.31 userid=mgmt passwd=abc123 type=ibm \\\n" -"        op monitor interval=\"60s\"\n" -"clone Fencing rsa-fencing\n" -"" +msgid "primitive ipmi-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\"\n" +"clone Fencing rsa-fencing" 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 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." +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 processed by one of the two clone instances. The additional meta options tell the cluster that we want two instances of the clone (one \"request bucket\" for each node) and that if one node fails, then the remaining node should hold both." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" -"        params ip=”192.168.122.101” cidr_netmask=”32” clusterip_hash=”sourceip” \\\n" -"        op monitor interval=\"30s\"\n" -"clone WebIP ClusterIP  \n" -"        meta globally-unique=”true” clone-max=”2” clone-node-max=”2”\n" -"" +msgid "primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" +" op monitor interval=\"30s\"\n" +"clone WebIP ClusterIP\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"" msgstr "" #. Tag: para #, no-c-format msgid "TODO: The RA should check for globally-unique=true when cloned" msgstr "" -#. Tag: title -#, no-c-format -msgid "Distributed lock manager" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Cluster filesystems like GFS2 require a lock manager. This service starts the daemon that provides user-space applications (such as the GFS2 daemon) with access to the in-kernel lock manager. Since we need it to be available on all nodes in the cluster, we have it cloned." -msgstr "" - -#. Tag: screen -#, no-c-format -msgid "\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\n" -"" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "TODO: Confirm interleave is no longer needed" -msgstr "" - -#. Tag: title -#, no-c-format -msgid "GFS control daemon" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "GFS2 also needs a user-space/kernel bridge that runs on every node. So here we have another clone, however this time we must also specify that it can only run on machines that are also running the DLM (colocation constraint) and that it can only be started after the DLM is running (order constraint). Additionally, the gfs-control clone should only care about the DLM instances it is paired with, so we need to set the interleave option." -msgstr "" - -#. Tag: screen -#, no-c-format -msgid "\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -"   params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -"        op monitor interval=\"120s\"\n" -"clone gfs-clone gfs-control \\\n" -"        meta interleave=\"true\"\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" -"" -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." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"primitive WebData ocf:linbit:drbd \\\n" -"        params drbd_resource=\"wwwdata\" \\\n" -"        op monitor interval=\"60s\"\n" +msgid "primitive WebData ocf:linbit:drbd \\\n" +" params drbd_resource=\"wwwdata\" \\\n" +" op monitor interval=\"60s\"\n" "ms WebDataClone WebData \\\n" -"        meta master-max=\"2\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"" +" meta master-max=\"2\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"" 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." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"primitive WebFS ocf:heartbeat:Filesystem \\\n" -"        params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=”gfs2”\n" +msgid "primitive WebFS ocf:heartbeat:Filesystem \\\n" +" params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=\"gfs2\"\n" "clone WebFSClone WebFS\n" "colocation WebFS-with-gfs-control inf: WebFSClone gfs-clone\n" "colocation fs_on_drbd inf: WebFSClone WebDataClone:Master\n" "order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start\n" -"order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone\n" -"" +"order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone" 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." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\n" +msgid "primitive WebSite ocf:heartbeat:apache \\\n" +" params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" +" op monitor interval=\"1min\"\n" "clone WebSiteClone WebSite\n" "colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone\n" "colocation website-with-ip inf: WebSiteClone WebIP\n" "order apache-after-ip inf: WebIP WebSiteClone\n" -"order WebSite-after-WebFS inf: WebFSClone WebSiteClone\n" -"" +"order WebSite-after-WebFS inf: WebFSClone WebSiteClone" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot b/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot index 01254bd911..b1782baa29 100644 --- a/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot +++ b/doc/Clusters_from_Scratch/pot/Ap-Corosync-Conf.pot @@ -1,101 +1,90 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:26\n" -"PO-Revision-Date: 2010-12-21T11:01:26\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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.conf" +msgid "Sample Corosync Configuration" msgstr "" -#. Tag: screen +#. Tag: title #, no-c-format -msgid "\n" -"# Please read the Corosync.conf.5 manual page\n" +msgid "Sample Corosync.conf for a two-node cluster" +msgstr "" + +#. Tag: literallayout +#, no-c-format +msgid "# Please read the Corosync.conf.5 manual page\n" "compatibility: whitetank\n" "\n" -"aisexec {\n" -"        # Run as root - this is necessary to be able to manage resources with Pacemaker\n" -"        user:        root\n" -"        group:        root\n" -"}\n" -"\n" -"service {\n" -"        # Load the Pacemaker Cluster Resource Manager\n" -"        ver:       0\n" -"        name:      pacemaker\n" -"        use_mgmtd: no\n" -"        use_logd:  no\n" -"}\n" -"\n" "totem {\n" -"        version: 2\n" +" version: 2\n" "\n" -"        # How long before declaring a token lost (ms)\n" -"        token:          5000\n" +" # How long before declaring a token lost (ms)\n" +" token: 5000\n" "\n" -"        # How many token retransmits before forming a new configuration\n" -"        token_retransmits_before_loss_const: 10\n" +" # How many token retransmits before forming a new configuration\n" +" token_retransmits_before_loss_const: 10\n" "\n" -"        # How long to wait for join messages in the membership protocol (ms)\n" -"        join:           1000\n" +" # How long to wait for join messages in the membership protocol (ms)\n" +" join: 1000\n" "\n" -"        # How long to wait for consensus to be achieved before starting a new\n" -"        # round of membership configuration (ms)\n" -"        consensus:      6000\n" +" # How long to wait for consensus to be achieved before starting a new\n" +" # round of membership configuration (ms)\n" +" consensus: 6000\n" "\n" -"        # Turn off the virtual synchrony filter\n" -"        vsftype:        none\n" +" # Turn off the virtual synchrony filter\n" +" vsftype: none\n" "\n" -"        # Number of messages that may be sent by one processor on receipt of the token\n" -"        max_messages:   20\n" +" # Number of messages that may be sent by one processor on receipt of the token\n" +" max_messages: 20\n" "\n" -"        # Stagger sending the node join messages by 1..send_join ms\n" -"        send_join: 45\n" +" # Stagger sending the node join messages by 1..send_join ms\n" +" send_join: 45\n" "\n" -"        # Limit generated nodeids to 31-bits (positive signed integers)\n" -"        clear_node_high_bit: yes\n" +" # Limit generated nodeids to 31-bits (positive signed integers)\n" +" clear_node_high_bit: yes\n" "\n" -"        # Disable encryption\n" -"        secauth:        off\n" +" # Disable encryption\n" +" secauth: off\n" "\n" -"        # How many threads to use for encryption/decryption\n" -"        threads:           0\n" +" # How many threads to use for encryption/decryption\n" +" threads: 0\n" "\n" -"        # Optionally assign a fixed node id (integer)\n" -"        # nodeid:         1234\n" +" # Optionally assign a fixed node id (integer)\n" +" # nodeid: 1234\n" "\n" -"        interface {\n" -"                ringnumber: 0\n" +" interface {\n" +" ringnumber: 0\n" "\n" -"                # The following values need to be set based on your environment\n" -"                bindnetaddr: 192.168.122.0\n" -"                mcastaddr: 226.94.1.1\n" -"                mcastport: 4000\n" -"        }\n" +" # The following values need to be set based on your environment\n" +" bindnetaddr: 192.168.122.0\n" +" mcastaddr: 226.94.1.1\n" +" mcastport: 4000\n" +" }\n" "}\n" "\n" "logging {\n" -"        debug: off\n" -"        fileline: off\n" -"        to_syslog: yes\n" -"        to_stderr: off\n" -"        syslog_facility: daemon\n" -"        timestamp: on\n" +" debug: off\n" +" fileline: off\n" +" to_syslog: yes\n" +" to_stderr: off\n" +" syslog_facility: daemon\n" +" timestamp: on\n" "}\n" "\n" "amf {\n" -"        mode: disabled\n" -"}\n" -"" +" mode: disabled\n" +"}" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ap-Reading.pot b/doc/Clusters_from_Scratch/pot/Ap-Reading.pot index 00f5286b94..8c3ffb976b 100644 --- a/doc/Clusters_from_Scratch/pot/Ap-Reading.pot +++ b/doc/Clusters_from_Scratch/pot/Ap-Reading.pot @@ -1,54 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:26\n" -"PO-Revision-Date: 2010-12-21T11:01:26\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" +msgid "Project Website http://www.clusterlabs.org" msgstr "" #. Tag: para #, no-c-format -msgid "http://www.clusterlabs.org" +msgid "Cluster Commands A comprehensive guide to cluster commands has been written by Novell and can be found at: http://www.novell.com/documentation/sles11/book_sleha/index.html?page=/documentation/sles11/book_sleha/data/book_sleha.html" msgstr "" #. Tag: para #, no-c-format -msgid "Cluster Commands" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "A comprehensive guide to cluster commands has been written by Novell and can be found at:" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "http://www.novell.com/documentation/sles11/book_sleha/index.html?page=/documentation/sles11/book_sleha/data/book_sleha.html" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "Corosync" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "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 716df800eb..f22b21612f 100644 --- a/doc/Clusters_from_Scratch/pot/Author_Group.pot +++ b/doc/Clusters_from_Scratch/pot/Author_Group.pot @@ -1,49 +1,49 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:26\n" -"PO-Revision-Date: 2010-12-21T11:01:26\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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 "" diff --git a/doc/Clusters_from_Scratch/pot/Book_Info.pot b/doc/Clusters_from_Scratch/pot/Book_Info.pot index 4af2b80f71..1e1965f07b 100644 --- a/doc/Clusters_from_Scratch/pot/Book_Info.pot +++ b/doc/Clusters_from_Scratch/pot/Book_Info.pot @@ -1,74 +1,74 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:26\n" -"PO-Revision-Date: 2010-12-21T11:01:26\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" 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" +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 "The crm shell for displaying the configuration and making changes" 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." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot b/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot index beb1d28039..4ce66415b4 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Active-Active.pot @@ -1,852 +1,927 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" msgstr "" #. Tag: title #, no-c-format msgid "Requirements" msgstr "" #. Tag: para #, no-c-format -msgid "The primary requirement for an Active/Active cluster is that the data required for your services are 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 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." msgstr "" #. Tag: para #, no-c-format -msgid "The only hitch is that we need to use a cluster-aware filesystem (and 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 &DISTRO; &DISTRO_VERSION; ." +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 13." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "We’ll also need to use CMAN for Cluster Membership and Quorum instead of our Corosync plugin." msgstr "" #. Tag: title #, no-c-format -msgid "Install a Cluster Filesystem - GFS2" +msgid "Adding CMAN Support" msgstr "" #. Tag: para #, no-c-format -msgid "The first thing to do is install gfs2-utils on each machine." +msgid "CMAN v3 is a Corsync plugin that monitors the names and number of active cluster nodes in order to deliver membership and quorum information to clients (such as the Pacemaker daemons)." msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# yum install -y gfs2-utils gfs-pcmk\n" +msgid "In a traditional Corosync-Pacemaker cluster, a Pacemaker plugin is loaded to provide membership and quorum information. The motivation for wanting to use CMAN for this instead, is to ensure all elements of the cluster stack are making decisions based on the same membership and quorum data. A failure to do this can lead to what is called internal split-brain - a situation where different parts of the stack disagree about whether some nodes are alive or dead - which quickly leads to unnecssary down-time and/or data corruption." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the case of GFS2, the key pieces are the dlm_controld and gfs_controld helpers which act as the glue between the filesystem and the cluster software. Supporting CMAN enables us to use the versions already being shipped by most distributions (since CMAN has been around longer than Pacemaker and is part of the Red Hat cluster stack)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Ensure Corosync and Pacemaker are stopped on all nodes before continuing" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Be sure to disable the Pacemaker plugin before continuing with this section. In most cases, this can be achieved by removing /etc/corosync/service.d/pcmk and stopping Corosync." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Installing the required Software" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# yum install -y cman gfs2-utils gfs2-cluster\n" +"Loaded plugins: auto-update-debuginfo\n" "Setting up Install Process\n" "Resolving Dependencies\n" "--> Running transaction check\n" -"---> Package gfs-pcmk.x86_64 0:3.0.5-2.fc12 set to be updated\n" -"--> Processing Dependency: libSaCkpt.so.3(OPENAIS_CKPT_B.01.01)(64bit) for package: gfs-pcmk-3.0.5-2.fc12.x86_64\n" -"--> Processing Dependency: dlm-pcmk for package: gfs-pcmk-3.0.5-2.fc12.x86_64\n" -"--> Processing Dependency: libccs.so.3()(64bit) for package: gfs-pcmk-3.0.5-2.fc12.x86_64\n" -"--> Processing Dependency: libdlmcontrol.so.3()(64bit) for package: gfs-pcmk-3.0.5-2.fc12.x86_64\n" -"--> Processing Dependency: liblogthread.so.3()(64bit) for package: gfs-pcmk-3.0.5-2.fc12.x86_64\n" -"--> Processing Dependency: libSaCkpt.so.3()(64bit) for package: gfs-pcmk-3.0.5-2.fc12.x86_64\n" -"---> Package gfs2-utils.x86_64 0:3.0.5-2.fc12 set to be updated\n" +"---> Package cman.x86_64 0:3.1.7-1.fc15 will be installed\n" +"--> Processing Dependency: modcluster >= 0.18.1-1 for package: cman-3.1.7-1.fc15.x86_64\n" +"--> Processing Dependency: fence-agents >= 3.1.5-1 for package: cman-3.1.7-1.fc15.x86_64\n" +"--> Processing Dependency: openais >= 1.1.4-1 for package: cman-3.1.7-1.fc15.x86_64\n" +"--> Processing Dependency: ricci >= 0.18.1-1 for package: cman-3.1.7-1.fc15.x86_64\n" +"--> Processing Dependency: libSaCkpt.so.3(OPENAIS_CKPT_B.01.01)(64bit) for package: cman-3.1.7-1.fc15.x86_64\n" +"--> Processing Dependency: libSaCkpt.so.3()(64bit) for package: cman-3.1.7-1.fc15.x86_64\n" +"---> Package gfs2-cluster.x86_64 0:3.1.1-2.fc15 will be installed\n" +"---> Package gfs2-utils.x86_64 0:3.1.1-2.fc15 will be installed\n" +"--> Running transaction check\n" +"---> Package fence-agents.x86_64 0:3.1.5-1.fc15 will be installed\n" +"--> Processing Dependency: /usr/bin/virsh for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: net-snmp-utils for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: sg3_utils for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: perl(Net::Telnet) for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: /usr/bin/ipmitool for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: perl-Net-Telnet for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: pexpect for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: pyOpenSSL for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"--> Processing Dependency: python-suds for package: fence-agents-3.1.5-1.fc15.x86_64\n" +"---> Package modcluster.x86_64 0:0.18.7-1.fc15 will be installed\n" +"--> Processing Dependency: oddjob for package: modcluster-0.18.7-1.fc15.x86_64\n" +"---> Package openais.x86_64 0:1.1.4-2.fc15 will be installed\n" +"---> Package openaislib.x86_64 0:1.1.4-2.fc15 will be installed\n" +"---> Package ricci.x86_64 0:0.18.7-1.fc15 will be installed\n" +"--> Processing Dependency: parted for package: ricci-0.18.7-1.fc15.x86_64\n" +"--> Processing Dependency: nss-tools for package: ricci-0.18.7-1.fc15.x86_64\n" +"--> Running transaction check\n" +"---> Package ipmitool.x86_64 0:1.8.11-6.fc15 will be installed\n" +"---> Package libvirt-client.x86_64 0:0.8.8-7.fc15 will be installed\n" +"--> Processing Dependency: libnetcf.so.1(NETCF_1.3.0)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: cyrus-sasl-md5 for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: gettext for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: nc for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnuma.so.1(libnuma_1.1)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnuma.so.1(libnuma_1.2)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnetcf.so.1(NETCF_1.2.0)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: gnutls-utils for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnetcf.so.1(NETCF_1.0.0)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libyajl.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnl.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnuma.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libaugeas.so.0()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"--> Processing Dependency: libnetcf.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64\n" +"---> Package net-snmp-utils.x86_64 1:5.6.1-7.fc15 will be installed\n" +"---> Package nss-tools.x86_64 0:3.12.10-6.fc15 will be installed\n" +"---> Package oddjob.x86_64 0:0.31-2.fc15 will be installed\n" +"---> Package parted.x86_64 0:2.3-10.fc15 will be installed\n" +"---> Package perl-Net-Telnet.noarch 0:3.03-12.fc15 will be installed\n" +"---> Package pexpect.noarch 0:2.3-6.fc15 will be installed\n" +"---> Package pyOpenSSL.x86_64 0:0.10-3.fc15 will be installed\n" +"---> Package python-suds.noarch 0:0.3.9-3.fc15 will be installed\n" +"---> Package sg3_utils.x86_64 0:1.29-3.fc15 will be installed\n" +"--> Processing Dependency: sg3_utils-libs = 1.29-3.fc15 for package: sg3_utils-1.29-3.fc15.x86_64\n" +"--> Processing Dependency: libsgutils2.so.2()(64bit) for package: sg3_utils-1.29-3.fc15.x86_64\n" "--> Running transaction check\n" -"---> Package clusterlib.x86_64 0:3.0.5-2.fc12 set to be updated\n" -"---> Package dlm-pcmk.x86_64 0:3.0.5-2.fc12 set to be updated\n" -"---> Package openaislib.x86_64 0:1.1.0-1.fc12 set to be updated\n" +"---> Package augeas-libs.x86_64 0:0.9.0-1.fc15 will be installed\n" +"---> Package cyrus-sasl-md5.x86_64 0:2.1.23-18.fc15 will be installed\n" +"---> Package gettext.x86_64 0:0.18.1.1-7.fc15 will be installed\n" +"--> Processing Dependency: libgomp.so.1(GOMP_1.0)(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64\n" +"--> Processing Dependency: libgettextlib-0.18.1.so()(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64\n" +"--> Processing Dependency: libgettextsrc-0.18.1.so()(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64\n" +"--> Processing Dependency: libgomp.so.1()(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64\n" +"---> Package gnutls-utils.x86_64 0:2.10.5-1.fc15 will be installed\n" +"---> Package libnl.x86_64 0:1.1-14.fc15 will be installed\n" +"---> Package nc.x86_64 0:1.100-3.fc15 will be installed\n" +"--> Processing Dependency: libbsd.so.0(LIBBSD_0.0)(64bit) for package: nc-1.100-3.fc15.x86_64\n" +"--> Processing Dependency: libbsd.so.0(LIBBSD_0.2)(64bit) for package: nc-1.100-3.fc15.x86_64\n" +"--> Processing Dependency: libbsd.so.0()(64bit) for package: nc-1.100-3.fc15.x86_64\n" +"---> Package netcf-libs.x86_64 0:0.1.9-1.fc15 will be installed\n" +"---> Package numactl.x86_64 0:2.0.7-1.fc15 will be installed\n" +"---> Package sg3_utils-libs.x86_64 0:1.29-3.fc15 will be installed\n" +"---> Package xen-libs.x86_64 0:4.1.1-3.fc15 will be installed\n" +"--> Processing Dependency: xen-licenses for package: xen-libs-4.1.1-3.fc15.x86_64\n" +"---> Package yajl.x86_64 0:1.0.11-1.fc15 will be installed\n" +"--> Running transaction check\n" +"---> Package gettext-libs.x86_64 0:0.18.1.1-7.fc15 will be installed\n" +"---> Package libbsd.x86_64 0:0.2.0-4.fc15 will be installed\n" +"---> Package libgomp.x86_64 0:4.6.1-9.fc15 will be installed\n" +"---> Package xen-licenses.x86_64 0:4.1.1-3.fc15 will be installed\n" "--> Finished Dependency Resolution\n" "\n" "Dependencies Resolved\n" "\n" -"===========================================================================================\n" -" Package                Arch               Version                   Repository        Size\n" -"===========================================================================================\n" +"=============================================================================\n" +" Package Arch Version Repository Size\n" +"=============================================================================\n" "Installing:\n" -" gfs-pcmk               x86_64             3.0.5-2.fc12              custom           101 k\n" -" gfs2-utils             x86_64             3.0.5-2.fc12              custom           208 k\n" +" cman x86_64 3.1.7-1.fc15 updates 366 k\n" +" gfs2-cluster x86_64 3.1.1-2.fc15 fedora 69 k\n" +" gfs2-utils x86_64 3.1.1-2.fc15 fedora 222 k\n" "Installing for dependencies:\n" -" clusterlib             x86_64             3.0.5-2.fc12              custom            65 k\n" -" dlm-pcmk               x86_64             3.0.5-2.fc12              custom            93 k\n" -" openaislib             x86_64             1.1.0-1.fc12              fedora            76 k\n" +" augeas-libs x86_64 0.9.0-1.fc15 updates 311 k\n" +" cyrus-sasl-md5 x86_64 2.1.23-18.fc15 updates 46 k\n" +" fence-agents x86_64 3.1.5-1.fc15 updates 186 k\n" +" gettext x86_64 0.18.1.1-7.fc15 fedora 1.0 M\n" +" gettext-libs x86_64 0.18.1.1-7.fc15 fedora 610 k\n" +" gnutls-utils x86_64 2.10.5-1.fc15 fedora 101 k\n" +" ipmitool x86_64 1.8.11-6.fc15 fedora 273 k\n" +" libbsd x86_64 0.2.0-4.fc15 fedora 37 k\n" +" libgomp x86_64 4.6.1-9.fc15 updates 95 k\n" +" libnl x86_64 1.1-14.fc15 fedora 118 k\n" +" libvirt-client x86_64 0.8.8-7.fc15 updates 2.4 M\n" +" modcluster x86_64 0.18.7-1.fc15 fedora 187 k\n" +" nc x86_64 1.100-3.fc15 updates 24 k\n" +" net-snmp-utils x86_64 1:5.6.1-7.fc15 fedora 180 k\n" +" netcf-libs x86_64 0.1.9-1.fc15 updates 50 k\n" +" nss-tools x86_64 3.12.10-6.fc15 updates 723 k\n" +" numactl x86_64 2.0.7-1.fc15 updates 54 k\n" +" oddjob x86_64 0.31-2.fc15 fedora 61 k\n" +" openais x86_64 1.1.4-2.fc15 fedora 190 k\n" +" openaislib x86_64 1.1.4-2.fc15 fedora 88 k\n" +" parted x86_64 2.3-10.fc15 updates 618 k\n" +" perl-Net-Telnet noarch 3.03-12.fc15 fedora 55 k\n" +" pexpect noarch 2.3-6.fc15 fedora 141 k\n" +" pyOpenSSL x86_64 0.10-3.fc15 fedora 198 k\n" +" python-suds noarch 0.3.9-3.fc15 fedora 195 k\n" +" ricci x86_64 0.18.7-1.fc15 fedora 584 k\n" +" sg3_utils x86_64 1.29-3.fc15 fedora 465 k\n" +" sg3_utils-libs x86_64 1.29-3.fc15 fedora 54 k\n" +" xen-libs x86_64 4.1.1-3.fc15 updates 310 k\n" +" xen-licenses x86_64 4.1.1-3.fc15 updates 64 k\n" +" yajl x86_64 1.0.11-1.fc15 fedora 27 k\n" "\n" "Transaction Summary\n" -"===========================================================================================\n" -"Install       5 Package(s)\n" -"Upgrade       0 Package(s)\n" +"=============================================================================\n" +"Install 34 Package(s)\n" "\n" -"Total download size: 541 k\n" +"Total download size: 10 M\n" +"Installed size: 38 M\n" "Downloading Packages:\n" -"(1/5): clusterlib-3.0.5-2.fc12.x86_64.rpm                                |  65 kB     00:00\n" -"(2/5): dlm-pcmk-3.0.5-2.fc12.x86_64.rpm                                  |  93 kB     00:00\n" -"(3/5): gfs-pcmk-3.0.5-2.fc12.x86_64.rpm                                  | 101 kB     00:00\n" -"(4/5): gfs2-utils-3.0.5-2.fc12.x86_64.rpm                                | 208 kB     00:00\n" -"(5/5): openaislib-1.1.0-1.fc12.x86_64.rpm                                |  76 kB     00:00\n" -"-------------------------------------------------------------------------------------------\n" -"Total                                                           992 kB/s | 541 kB     00:00\n" +"(1/34): augeas-libs-0.9.0-1.fc15.x86_64.rpm | 311 kB 00:00\n" +"(2/34): cman-3.1.7-1.fc15.x86_64.rpm | 366 kB 00:00\n" +"(3/34): cyrus-sasl-md5-2.1.23-18.fc15.x86_64.rpm | 46 kB 00:00\n" +"(4/34): fence-agents-3.1.5-1.fc15.x86_64.rpm | 186 kB 00:00\n" +"(5/34): gettext-0.18.1.1-7.fc15.x86_64.rpm | 1.0 MB 00:01\n" +"(6/34): gettext-libs-0.18.1.1-7.fc15.x86_64.rpm | 610 kB 00:00\n" +"(7/34): gfs2-cluster-3.1.1-2.fc15.x86_64.rpm | 69 kB 00:00\n" +"(8/34): gfs2-utils-3.1.1-2.fc15.x86_64.rpm | 222 kB 00:00\n" +"(9/34): gnutls-utils-2.10.5-1.fc15.x86_64.rpm | 101 kB 00:00\n" +"(10/34): ipmitool-1.8.11-6.fc15.x86_64.rpm | 273 kB 00:00\n" +"(11/34): libbsd-0.2.0-4.fc15.x86_64.rpm | 37 kB 00:00\n" +"(12/34): libgomp-4.6.1-9.fc15.x86_64.rpm | 95 kB 00:00\n" +"(13/34): libnl-1.1-14.fc15.x86_64.rpm | 118 kB 00:00\n" +"(14/34): libvirt-client-0.8.8-7.fc15.x86_64.rpm | 2.4 MB 00:01\n" +"(15/34): modcluster-0.18.7-1.fc15.x86_64.rpm | 187 kB 00:00\n" +"(16/34): nc-1.100-3.fc15.x86_64.rpm | 24 kB 00:00\n" +"(17/34): net-snmp-utils-5.6.1-7.fc15.x86_64.rpm | 180 kB 00:00\n" +"(18/34): netcf-libs-0.1.9-1.fc15.x86_64.rpm | 50 kB 00:00\n" +"(19/34): nss-tools-3.12.10-6.fc15.x86_64.rpm | 723 kB 00:00\n" +"(20/34): numactl-2.0.7-1.fc15.x86_64.rpm | 54 kB 00:00\n" +"(21/34): oddjob-0.31-2.fc15.x86_64.rpm | 61 kB 00:00\n" +"(22/34): openais-1.1.4-2.fc15.x86_64.rpm | 190 kB 00:00\n" +"(23/34): openaislib-1.1.4-2.fc15.x86_64.rpm | 88 kB 00:00\n" +"(24/34): parted-2.3-10.fc15.x86_64.rpm | 618 kB 00:00\n" +"(25/34): perl-Net-Telnet-3.03-12.fc15.noarch.rpm | 55 kB 00:00\n" +"(26/34): pexpect-2.3-6.fc15.noarch.rpm | 141 kB 00:00\n" +"(27/34): pyOpenSSL-0.10-3.fc15.x86_64.rpm | 198 kB 00:00\n" +"(28/34): python-suds-0.3.9-3.fc15.noarch.rpm | 195 kB 00:00\n" +"(29/34): ricci-0.18.7-1.fc15.x86_64.rpm | 584 kB 00:00\n" +"(30/34): sg3_utils-1.29-3.fc15.x86_64.rpm | 465 kB 00:00\n" +"(31/34): sg3_utils-libs-1.29-3.fc15.x86_64.rpm | 54 kB 00:00\n" +"(32/34): xen-libs-4.1.1-3.fc15.x86_64.rpm | 310 kB 00:00\n" +"(33/34): xen-licenses-4.1.1-3.fc15.x86_64.rpm | 64 kB 00:00\n" +"(34/34): yajl-1.0.11-1.fc15.x86_64.rpm | 27 kB 00:00\n" +" -----------------------------------------------------------------------------\n" +"Total 803 kB/s | 10 MB 00:12\n" "Running rpm_check_debug\n" "Running Transaction Test\n" -"Finished Transaction Test\n" "Transaction Test Succeeded\n" "Running Transaction\n" -"  Installing     : clusterlib-3.0.5-2.fc12.x86_64                                       1/5 \n" -"  Installing     : openaislib-1.1.0-1.fc12.x86_64                                       2/5 \n" -"  Installing     : dlm-pcmk-3.0.5-2.fc12.x86_64                                         3/5 \n" -"  Installing     : gfs-pcmk-3.0.5-2.fc12.x86_64                                         4/5 \n" -"  Installing     : gfs2-utils-3.0.5-2.fc12.x86_64                                       5/5 \n" +" Installing : openais-1.1.4-2.fc15.x86_64 1/34\n" +" Installing : openaislib-1.1.4-2.fc15.x86_64 2/34\n" +" Installing : libnl-1.1-14.fc15.x86_64 3/34\n" +" Installing : augeas-libs-0.9.0-1.fc15.x86_64 4/34\n" +" Installing : oddjob-0.31-2.fc15.x86_64 5/34\n" +" Installing : modcluster-0.18.7-1.fc15.x86_64 6/34\n" +" Installing : netcf-libs-0.1.9-1.fc15.x86_64 7/34\n" +" Installing : 1:net-snmp-utils-5.6.1-7.fc15.x86_64 8/34\n" +" Installing : sg3_utils-libs-1.29-3.fc15.x86_64 9/34\n" +" Installing : sg3_utils-1.29-3.fc15.x86_64 10/34\n" +" Installing : libgomp-4.6.1-9.fc15.x86_64 11/34\n" +" Installing : gnutls-utils-2.10.5-1.fc15.x86_64 12/34\n" +" Installing : pyOpenSSL-0.10-3.fc15.x86_64 13/34\n" +" Installing : parted-2.3-10.fc15.x86_64 14/34\n" +" Installing : cyrus-sasl-md5-2.1.23-18.fc15.x86_64 15/34\n" +" Installing : python-suds-0.3.9-3.fc15.noarch 16/34\n" +" Installing : ipmitool-1.8.11-6.fc15.x86_64 17/34\n" +" Installing : perl-Net-Telnet-3.03-12.fc15.noarch 18/34\n" +" Installing : numactl-2.0.7-1.fc15.x86_64 19/34\n" +" Installing : yajl-1.0.11-1.fc15.x86_64 20/34\n" +" Installing : gettext-libs-0.18.1.1-7.fc15.x86_64 21/34\n" +" Installing : gettext-0.18.1.1-7.fc15.x86_64 22/34\n" +" Installing : libbsd-0.2.0-4.fc15.x86_64 23/34\n" +" Installing : nc-1.100-3.fc15.x86_64 24/34\n" +" Installing : xen-licenses-4.1.1-3.fc15.x86_64 25/34\n" +" Installing : xen-libs-4.1.1-3.fc15.x86_64 26/34\n" +" Installing : libvirt-client-0.8.8-7.fc15.x86_64 27/34\n" +"\n" +"Note: This output shows SysV services only and does not include native\n" +" systemd services. SysV configuration data might be overridden by native\n" +" systemd configuration.\n" +"\n" +" Installing : nss-tools-3.12.10-6.fc15.x86_64 28/34\n" +" Installing : ricci-0.18.7-1.fc15.x86_64 29/34\n" +" Installing : pexpect-2.3-6.fc15.noarch 30/34\n" +" Installing : fence-agents-3.1.5-1.fc15.x86_64 31/34\n" +" Installing : cman-3.1.7-1.fc15.x86_64 32/34\n" +" Installing : gfs2-cluster-3.1.1-2.fc15.x86_64 33/34\n" +" Installing : gfs2-utils-3.1.1-2.fc15.x86_64 34/34\n" "\n" "Installed:\n" -"  gfs-pcmk.x86_64 0:3.0.5-2.fc12                    gfs2-utils.x86_64 0:3.0.5-2.fc12\n" +" cman.x86_64 0:3.1.7-1.fc15 gfs2-cluster.x86_64 0:3.1.1-2.fc15\n" +" gfs2-utils.x86_64 0:3.1.1-2.fc15\n" "\n" "Dependency Installed:\n" -"  clusterlib.x86_64 0:3.0.5-2.fc12   dlm-pcmk.x86_64 0:3.0.5-2.fc12 \n" -"  openaislib.x86_64 0:1.1.0-1.fc12  \n" +" augeas-libs.x86_64 0:0.9.0-1.fc15\n" +" cyrus-sasl-md5.x86_64 0:2.1.23-18.fc15\n" +" fence-agents.x86_64 0:3.1.5-1.fc15\n" +" gettext.x86_64 0:0.18.1.1-7.fc15\n" +" gettext-libs.x86_64 0:0.18.1.1-7.fc15\n" +" gnutls-utils.x86_64 0:2.10.5-1.fc15\n" +" ipmitool.x86_64 0:1.8.11-6.fc15\n" +" libbsd.x86_64 0:0.2.0-4.fc15\n" +" libgomp.x86_64 0:4.6.1-9.fc15\n" +" libnl.x86_64 0:1.1-14.fc15\n" +" libvirt-client.x86_64 0:0.8.8-7.fc15\n" +" modcluster.x86_64 0:0.18.7-1.fc15\n" +" nc.x86_64 0:1.100-3.fc15\n" +" net-snmp-utils.x86_64 1:5.6.1-7.fc15\n" +" netcf-libs.x86_64 0:0.1.9-1.fc15\n" +" nss-tools.x86_64 0:3.12.10-6.fc15\n" +" numactl.x86_64 0:2.0.7-1.fc15\n" +" oddjob.x86_64 0:0.31-2.fc15\n" +" openais.x86_64 0:1.1.4-2.fc15\n" +" openaislib.x86_64 0:1.1.4-2.fc15\n" +" parted.x86_64 0:2.3-10.fc15\n" +" perl-Net-Telnet.noarch 0:3.03-12.fc15\n" +" pexpect.noarch 0:2.3-6.fc15\n" +" pyOpenSSL.x86_64 0:0.10-3.fc15\n" +" python-suds.noarch 0:0.3.9-3.fc15\n" +" ricci.x86_64 0:0.18.7-1.fc15\n" +" sg3_utils.x86_64 0:1.29-3.fc15\n" +" sg3_utils-libs.x86_64 0:1.29-3.fc15\n" +" xen-libs.x86_64 0:4.1.1-3.fc15\n" +" xen-licenses.x86_64 0:4.1.1-3.fc15\n" +" yajl.x86_64 0:1.0.11-1.fc15\n" "\n" -"Complete!\n" -"[root@pcmk-1 x86_64]#\n" -"" +"Complete!" msgstr "" #. Tag: title #, no-c-format -msgid "Setup Pacemaker-GFS2 Integration" +msgid "Configuring CMAN" msgstr "" #. Tag: para #, no-c-format -msgid "GFS2 needs two services to be running, the first is the user-space interface to the kernel’s distributed lock manager (DLM). The DLM is used to co-ordinate which node(s) can access a given file (and when) and integrates with Pacemaker to obtain node membership The list of nodes the cluster considers to be available information and fencing capabilities." +msgid "The first thing we need to do, is tell CMAN complete starting up even without quorum. We can do this by changing the quorum timeout setting:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# sed -i.sed \"s/.*CMAN_QUORUM_TIMEOUT=.*/CMAN_QUORUM_TIMEOUT=0/g\" /etc/sysconfig/cman" msgstr "" #. Tag: para #, no-c-format -msgid "The second service is GFS2’s own control daemon which also integrates with Pacemaker to obtain node membership data." +msgid "Next we create a basic configuration file and place is in /etc/cluster/cluster.conf. The name used for each clusternode should correspond to that node’s uname -n, just as Pacemaker expects. The nodeid can be any positive mumber but nust be unique." +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<?xml version=\"1.0\"?>\n" +"<cluster config_version=\"1\" name=\"my_cluster_name\">\n" +" <logging debug=\"off\"/>\n" +" <clusternodes>\n" +" <clusternode name=\"pcmk-1\" nodeid=\"1\"/>\n" +" <clusternode name=\"pcmk-2\" nodeid=\"2\"/>\n" +" </clusternodes>\n" +"</cluster>" msgstr "" #. Tag: title #, no-c-format -msgid "Add the DLM service" +msgid "Configuring CMAN Fencing" msgstr "" #. Tag: para #, no-c-format -msgid "The DLM control daemon needs to run on all active cluster nodes, so we will use the shells interactive mode to create a cloned resource." +msgid "We configure the fence_pcmk agent (supplied with Pacemaker) to redirect any fencing requests from CMAN components (such as dlm_controld) to Pacemaker. Pacemaker’s fencing subsystem lets other parts of the stack know that a node has been successfully fenced, thus avoiding the need for it to be fenced again when other subsystems notice the node is gone." msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm\n" -"crm(live)# cib new stack-glue\n" -"INFO: stack-glue shadow CIB created\n" -"crm(stack-glue)# configure primitive dlm ocf:pacemaker:controld op monitor interval=120s\n" -"crm(stack-glue)# configure clone dlm-clone dlm meta interleave=true\n" -"crm(stack-glue)# configure show xml\n" -"crm(stack-glue)# configure show\n" -"node 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=\"ext4\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -" op monitor interval=\"120s\"\n" -"ms WebDataClone WebData \\\n" -"        meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone dlm-clone dlm \\\n" -" meta interleave=\"true\"\n" -"location prefer-pcmk-1 WebSite 50: pcmk-1\n" -"colocation WebSite-with-WebFS inf: WebSite WebFS\n" -"colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" -"colocation website-with-ip inf: WebSite ClusterIP\n" -"order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" -"order WebSite-after-WebFS inf: WebFS WebSite\n" -"order apache-after-ip inf: ClusterIP WebSite\n" -"property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" -"rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -"" +msgid "Warning Configuring real fencing devices in CMAN will result in nodes being fenced multiple times as different parts of the stack notice the node is missing or failed." msgstr "" #. Tag: para #, no-c-format -msgid "TODO: Explain the meaning of the interleave option" +msgid "The definition should be placed in the fencedevices section and contain:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " <fencedevice name=\"pcmk\" agent=\"fence_pcmk\"/>" 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 "Each clusternode must be configured to use this device by adding a fence method block that lists the node’s name as the port." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(stack-glue)# cib commit stack-glue\n" -"INFO: commited 'stack-glue' shadow CIB to the cluster\n" -"crm(stack-glue)# quit\n" -"bye\n" -"[root@pcmk-1 ~]# crm_mon\n" -"============\n" -"Last updated: Thu Sep  3 20:49:54 2009\n" -"Stack: openais\n" -"Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" -"2 Nodes configured, 2 expected votes\n" -"5 Resources configured.\n" -"============\n" -"\n" -"Online: [ pcmk-1 pcmk-2 ]\n" -"\n" -"WebSite (ocf::heartbeat:apache):        Started pcmk-2\n" -"Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-1 ]\n" -"        Slaves: [ pcmk-2 ]\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"Clone Set: dlm-clone\n" -" Started: [ pcmk-2 pcmk-1 ]\n" -"WebFS   (ocf::heartbeat:Filesystem):    Started pcmk-2\n" -"" +msgid " <fence>\n" +" <method name=\"pcmk-redirect\">\n" +" <device name=\"pcmk\" port=\"node_name_here\"/>\n" +" </method>\n" +" </fence>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Putting everything together, we have:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<?xml version=\"1.0\"?>\n" +"<cluster config_version=\"1\" name=\"mycluster\">\n" +" <logging debug=\"off\"/>\n" +" <clusternodes>\n" +" <clusternode name=\"pcmk-1\" nodeid=\"1\">\n" +" <fence>\n" +" <method name=\"pcmk-redirect\">\n" +" <device name=\"pcmk\" port=\"pcmk-1\"/>\n" +" </method>\n" +" </fence>\n" +" </clusternode>\n" +" <clusternode name=\"pcmk-2\" nodeid=\"2\">\n" +" <fence>\n" +" <method name=\"pcmk-redirect\">\n" +" <device name=\"pcmk\" port=\"pcmk-2\"/>\n" +" </method>\n" +" </fence>\n" +" </clusternode>\n" +" </clusternodes>\n" +" <fencedevices>\n" +" <fencedevice name=\"pcmk\" agent=\"fence_pcmk\"/>\n" +" </fencedevices>\n" +"</cluster>" msgstr "" #. Tag: title #, no-c-format -msgid "Add the GFS2 service" +msgid "Bringing the Cluster Online with CMAN" msgstr "" #. Tag: para #, no-c-format -msgid "Once the DLM is active, we can add the GFS2 control daemon." +msgid "The first thing to do is check that the configuration is valid" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# ccs_config_validate\n" +"Configuration validates" msgstr "" #. Tag: para #, no-c-format -msgid "Use the crm shell to create the gfs-control cluster resource:" +msgid "Now start CMAN" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm\n" -"crm(live)# cib new gfs-glue --force\n" -"INFO: gfs-glue shadow CIB created\n" -"crm(gfs-glue)# configure primitive gfs-control ocf:pacemaker:controld params daemon=gfs_controld.pcmk args=\"-g 0\" op monitor interval=120s\n" -"crm(gfs-glue)# configure clone gfs-clone gfs-control meta interleave=true\n" -"" +msgid "# service cman start\n" +"Starting cluster:\n" +" Checking Network Manager... [ OK ]\n" +" Global setup... [ OK ]\n" +" Loading kernel modules... [ OK ]\n" +" Mounting configfs... [ OK ]\n" +" Starting cman... [ OK ]\n" +" Waiting for quorum... [ OK ]\n" +" Starting fenced... [ OK ]\n" +" Starting dlm_controld... [ OK ]\n" +" Starting gfs_controld... [ OK ]\n" +" Unfencing self... [ OK ]\n" +" Joining fence domain... [ OK ]\n" +"# crm_mon -1" msgstr "" #. Tag: para #, no-c-format -msgid "Now ensure Pacemaker only starts the gfs-control service on nodes that also have a copy of the dlm service (created above) already running" +msgid "Once you have confirmed that the first node is happily online, start the second node." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(gfs-glue)# configure colocation gfs-with-dlm INFINITY: gfs-clone dlm-clone\n" -"crm(gfs-glue)# configure order start-gfs-after-dlm mandatory: dlm-clone gfs-clone\n" -"" +msgid "[root@pcmk-2 ~]# service cman startStarting cluster:\n" +" Checking Network Manager... [ OK ]\n" +" Global setup... [ OK ]\n" +" Loading kernel modules... [ OK ]\n" +" Mounting configfs... [ OK ]\n" +" Starting cman... [ OK ]\n" +" Waiting for quorum... [ OK ]\n" +" Starting fenced... [ OK ]\n" +" Starting dlm_controld... [ OK ]\n" +" Starting gfs_controld... [ OK ]\n" +" Unfencing self... [ OK ]\n" +" Joining fence domain... [ OK ]\n" +"# cman_tool nodes\n" +"Node Sts Inc Joined Name\n" +" 1 M 548 2011-09-28 10:52:21 pcmk-1\n" +" 2 M 548 2011-09-28 10:52:21 pcmk-2\n" +"# crm_mon -1" msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "\n" -"crm(gfs-glue)# configure show\n" -"node 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=\"ext4\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -" params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -" op monitor interval=\"120s\"\n" -"ms WebDataClone WebData \\\n" -"        meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\"\n" -"clone gfs-clone gfs-control \\\n" -" meta interleave=\"true\"\n" -"location prefer-pcmk-1 WebSite 50: pcmk-1\n" -"colocation WebSite-with-WebFS inf: WebSite WebFS\n" -"colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\n" -"colocation website-with-ip inf: WebSite ClusterIP\n" -"order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" -"order WebSite-after-WebFS inf: WebFS WebSite\n" -"order apache-after-ip inf: ClusterIP WebSite\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" -"property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" -"rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -"crm(gfs-glue)# cib commit gfs-glue\n" -"INFO: commited 'gfs-glue' shadow CIB to the cluster\n" -"crm(gfs-glue)# quit\n" -"bye\n" -"[root@pcmk-1 ~]# crm_mon\n" -"============\n" -"Last updated: Thu Sep  3 20:49:54 2009\n" -"Stack: openais\n" -"Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" -"2 Nodes configured, 2 expected votes\n" -"6 Resources configured.\n" -"============\n" -"\n" -"Online: [ pcmk-1 pcmk-2 ]\n" -"\n" -"WebSite (ocf::heartbeat:apache):        Started pcmk-2\n" -"Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-1 ]\n" -"        Slaves: [ pcmk-2 ]\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"Clone Set: dlm-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"Clone Set: gfs-clone\n" -" Started: [ pcmk-2 pcmk-1 ]\n" -"WebFS   (ocf::heartbeat:Filesystem):    Started pcmk-1\n" -"" +msgid "You should now see both nodes online and services started." msgstr "" #. Tag: title #, no-c-format msgid "Create a GFS2 Filesystem" msgstr "" #. Tag: title #, no-c-format msgid "Preparation" 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 tell the cluster to stop the WebFS resource. This will ensure that other resources (in our case, Apache) using WebFS are not only stopped, but stopped in the correct order." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm_resource --resource WebFS --set-parameter target-role --meta --parameter-value Stopped\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# crm_resource --resource WebFS --set-parameter target-role --meta --parameter-value Stopped\n" +"# crm_mon\n" "============\n" -"Last updated: Thu Sep  3 15:18:06 2009\n" +"Last updated: Thu Sep 3 15:18:06 2009\n" "Stack: openais\n" "Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "6 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" "Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-1 ]\n" -"        Slaves: [ pcmk-2 ]\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-1\n" -"Clone Set: dlm-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"Clone Set: gfs-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"" +" Masters: [ pcmk-1 ]\n" +" Slaves: [ pcmk-2 ]\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1" 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" msgstr "" #. Tag: para #, no-c-format msgid "Now that the cluster stack and integration pieces are running smoothly, we can create an GFS2 partition." 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." msgstr "" #. Tag: para #, 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)." msgstr "" #. Tag: para #, 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 just need to pick something unique and descriptive and since we haven’t specified a clustername yet, we will use the default (pcmk)." msgstr "" #. Tag: para #, no-c-format -msgid "To specify an alternate name for the cluster, locate the service section containing “name: pacemaker” in corosync.conf and insert the following line anywhere inside the block:" +msgid "To specify an alternate name for the cluster, locate the service section containing name: pacemaker in corosync.conf and insert the following line anywhere inside the block:" msgstr "" -#. Tag: para +#. Tag: literallayout #, no-c-format msgid "clustername: myname" msgstr "" #. Tag: para #, no-c-format msgid "Do this on each node in the cluster and be sure to restart them before continuing." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"mkfs.gfs2 -p lock_dlm -j 2 -t pcmk:web /dev/drbd1\n" -"[root@pcmk-1 ~]# mkfs.gfs2 -t pcmk:web -p lock_dlm -j 2 /dev/vdb \n" -"This will destroy any data on /dev/vdb.\n" +msgid "# mkfs.gfs2 -p lock_dlm -j 2 -t pcmk:web /dev/drbd1\n" +"This will destroy any data on /dev/drbd1.\n" "It appears to contain: data\n" "\n" "Are you sure you want to proceed? [y/n] y\n" "\n" -"Device:                    /dev/vdb\n" -"Blocksize:                 4096\n" -"Device Size                1.00 GB (131072 blocks)\n" -"Filesystem Size:           1.00 GB (131070 blocks)\n" -"Journals:                  2\n" -"Resource Groups:           2\n" -"Locking Protocol:          \"lock_dlm\"\n" -"Lock Table:                \"pcmk:web\"\n" -"UUID:                      6B776F46-177B-BAF8-2C2B-292C0E078613\n" -"\n" -"[root@pcmk-1 ~]#\n" -"" +"Device: /dev/drbd1\n" +"Blocksize: 4096\n" +"Device Size 1.00 GB (131072 blocks)\n" +"Filesystem Size: 1.00 GB (131070 blocks)\n" +"Journals: 2\n" +"Resource Groups: 2\n" +"Locking Protocol: \"lock_dlm\"\n" +"Lock Table: \"pcmk:web\"\n" +"UUID: 6B776F46-177B-BAF8-2C2B-292C0E078613" 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# mount /dev/drbd1 /mnt/\n" -"[root@pcmk-1 ~]# cat <<-END >/mnt/index.html\n" +msgid "# mount /dev/drbd1 /mnt/# cat <<-END >/mnt/index.html\n" "<html>\n" "<body>My Test Site - GFS2</body>\n" "</html>\n" "END\n" -"[root@pcmk-1 ~]# umount /dev/drbd1\n" -"[root@pcmk-1 ~]# drbdadm verify wwwdata\n" -"[root@pcmk-1 ~]#\n" -"" +"# umount /dev/drbd1\n" +"# drbdadm verify wwwdata#" msgstr "" #. Tag: title #, no-c-format msgid "Reconfigure the Cluster for GFS2" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm\n" -"crm(live)# cib new GFS2\n" +msgid "# crm\n" +"crm(live) # cib new GFS2\n" "INFO: GFS2 shadow CIB created\n" -"crm(GFS2)# configure delete WebFS\n" -"crm(GFS2)# configure primitive WebFS ocf:heartbeat:Filesystem params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=”gfs2”\n" -"" +"crm(GFS2) # configure delete WebFS\n" +"crm(GFS2) # configure primitive WebFS ocf:heartbeat:Filesystem params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=\"gfs2\"" msgstr "" #. Tag: para #, no-c-format msgid "Now that we’ve recreated the resource, we also need to recreate all the constraints that used it. This is because the shell will automatically remove any constraints that referenced WebFS." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(GFS2)# configure colocation WebSite-with-WebFS inf: WebSite WebFS\n" -"crm(GFS2)# configure colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" -"crm(GFS2)# configure order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" -"crm(GFS2)# configure order WebSite-after-WebFS inf: WebFS WebSite\n" -"crm(GFS2)# configure colocation WebFS-with-gfs-control INFINITY: WebFS gfs-clone\n" -"crm(GFS2)# configure order start-WebFS-after-gfs-control mandatory: gfs-clone WebFS\n" -"crm(GFS2)# configure show\n" +msgid "crm(GFS2) # configure colocation WebSite-with-WebFS inf: WebSite WebFS\n" +"crm(GFS2) # configure colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" +"crm(GFS2) # configure order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" +"crm(GFS2) # configure order WebSite-after-WebFS inf: WebFS WebSite\n" +"crm(GFS2) # configure show\n" "node 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" +" 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" +" 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\" \\\n" -"        op monitor interval=\"30s\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -"   params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -"        op monitor interval=\"120s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "ms WebDataClone WebData \\\n" -"        meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\"\n" -"clone gfs-clone gfs-control \\\n" -"        meta interleave=\"true\"\n" -"colocation WebFS-with-gfs-control inf: WebFS gfs-clone\n" +" meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" "colocation WebSite-with-WebFS inf: WebSite WebFS\n" "colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\n" "colocation website-with-ip inf: WebSite ClusterIP\n" "order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" "order WebSite-after-WebFS inf: WebFS WebSite\n" "order apache-after-ip inf: ClusterIP WebSite\n" -"order start-WebFS-after-gfs-control inf: gfs-clone WebFS\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -"" +" resource-stickiness=\"100\"" +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" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(GFS2)# cib commit GFS2\n" +msgid "crm(GFS2) # cib commit GFS2\n" "INFO: commited 'GFS2' shadow CIB to the cluster\n" -"crm(GFS2)# quit\n" +"crm(GFS2) # quit\n" "bye\n" -"[root@pcmk-1 ~]# crm_mon\n" +"# crm_mon\n" "============\n" -"Last updated: Thu Sep  3 20:49:54 2009\n" +"Last updated: Thu Sep 3 20:49:54 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "6 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"WebSite (ocf::heartbeat:apache):        Started pcmk-2\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-2\n" "Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-1 ]\n" -"        Slaves: [ pcmk-2 ]\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"Clone Set: dlm-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"Clone Set: gfs-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"WebFS (ocf::heartbeat:Filesystem): Started pcmk-1\n" -"" +" Masters: [ pcmk-1 ]\n" +" Slaves: [ pcmk-2 ]\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2WebFS (ocf::heartbeat:Filesystem): Started pcmk-1" msgstr "" #. Tag: title #, no-c-format msgid "Reconfigure Pacemaker for Active/Active" 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." msgstr "" #. Tag: para #, no-c-format msgid "This will involve a number of changes, so we’ll again use interactive mode." msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm\n" -"[root@pcmk-1 ~]# cib new active\n" -" " +msgid "# crm # cib new active" 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 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 "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 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# configure clone WebIP ClusterIP  \\\n" -"        meta globally-unique=”true” clone-max=”2” clone-node-max=”2”\n" -" " +msgid "# configure clone WebIP ClusterIP \\\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"" 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." msgstr "" #. Tag: para #, no-c-format msgid "Open the ClusterIP resource" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "[root@pcmk-1 ~]# configure edit  ClusterIP" +msgid "# configure edit ClusterIP" msgstr "" #. Tag: para #, no-c-format msgid "And add the following to the params line" msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format msgid "clusterip_hash=\"sourceip\"" msgstr "" #. Tag: para #, no-c-format msgid "So that the complete definition looks like:" msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"primitive ClusterIP ocf:heartbeat:IPaddr2 \\ \n" -"        params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" -"        op monitor interval=\"30s\"\n" -" " +msgid "primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" +" op monitor interval=\"30s\"" msgstr "" #. Tag: para #, no-c-format msgid "Here is the full transcript" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm \n" -"crm(live)# cib new active\n" +msgid "# crm crm(live)\n" +"# cib new active\n" "INFO: active shadow CIB created\n" -"crm(active)# configure clone WebIP ClusterIP  \\\n" -"        meta globally-unique=”true” clone-max=”2” clone-node-max=”2”\n" -"crm(active)# configure show\n" -"node pcmk-1\n" +"crm(active) # configure clone WebIP ClusterIP \\\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"\n" +"crm(active) # 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" +" 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" +" 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" +" 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\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -"   params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -"        op monitor interval=\"120s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" +" op monitor interval=\"30s\"\n" "ms WebDataClone WebData \\\n" -"        meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone WebIP ClusterIP \\\n" -" meta globally-unique=”true” clone-max=”2” clone-node-max=”2”\n" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\"\n" -"clone gfs-clone gfs-control \\\n" -"        meta interleave=\"true\"\n" -"colocation WebFS-with-gfs-control inf: WebFS gfs-clone\n" +" meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" +"clone WebIP ClusterIP \\\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"\n" "colocation WebSite-with-WebFS inf: WebSite WebFS\n" "colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\n" -"colocation website-with-ip inf: WebSite WebIP\n" -"order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" -"order WebSite-after-WebFS inf: WebFS WebSite\n" -"order apache-after-ip inf: WebIP WebSite\n" -"order start-WebFS-after-gfs-control inf: gfs-clone WebFS\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" +"colocation website-with-ip inf: WebSite WebIPorder WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" +"order WebSite-after-WebFS inf: WebFS WebSiteorder apache-after-ip inf: WebIP WebSite\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -" " +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "Notice how any constraints that referenced ClusterIP have been updated to use WebIP instead. This is an additional benefit of using the crm shell." msgstr "" #. Tag: para #, no-c-format msgid "Next we need to convert the filesystem and Apache resources into clones. Again, the shell will automatically update any relevant constraints." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(active)# configure clone WebFSClone WebFS\n" -"crm(active)# configure clone WebSiteClone WebSite\n" -" " +msgid "crm(active) # configure clone WebFSClone WebFS\n" +"crm(active) # configure clone WebSiteClone WebSite" 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)." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(active)# configure edit WebDataClone\n" -" " +msgid "crm(active) # configure edit WebDataClone" msgstr "" #. Tag: para #, no-c-format msgid "Change master-max to 2" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(active)# configure show\n" +msgid "crm(active) # configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebData ocf:linbit:drbd \\\n" -"        params drbd_resource=\"wwwdata\" \\\n" -"        op monitor interval=\"60s\"\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" +" 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" +" 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\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -"   params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -"        op monitor interval=\"120s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" clusterip_hash=\"sourceip\" \\\n" +" op monitor interval=\"30s\"\n" "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" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\"\n" -"clone gfs-clone gfs-control \\\n" -"        meta interleave=\"true\"\n" -"colocation WebFS-with-gfs-control inf: WebFSClone gfs-clone\n" -"colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone\n" -"colocation fs_on_drbd inf: WebFSClone WebDataClone:Master\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\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" -"order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" +" meta master-max=\"2\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" +"clone WebFSClone WebFSclone WebIP ClusterIP \\\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"\n" +"clone WebSiteClone WebSitecolocation 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.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -" " +" resource-stickiness=\"100\"" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(active)# cib commit active\n" +msgid "crm(active) # cib commit active\n" "INFO: commited 'active' shadow CIB to the cluster\n" -"crm(active)# quit\n" +"crm(active) # quit\n" "bye\n" -"[root@pcmk-1 ~]# crm_mon\n" +"# crm_mon\n" "============\n" -"Last updated: Thu Sep  3 21:37:27 2009\n" +"Last updated: Thu Sep 3 21:37:27 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "6 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" "Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-1 pcmk-2 ]\n" -"Clone Set: dlm-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"Clone Set: gfs-clone\n" -"        Started: [ pcmk-2 pcmk-1 ]\n" -"Clone Set: WebIP\n" -" Started: [ pcmk-1 pcmk-2 ]\n" -"Clone Set: WebFSClone\n" -" Started: [ pcmk-1 pcmk-2 ]\n" -"Clone Set: WebSiteClone\n" -" Started: [ pcmk-1 pcmk-2 ]\n" -" " +" Masters: [ pcmk-1 pcmk-2 ]\n" +"Clone Set: WebIP Started: [ pcmk-1 pcmk-2 ]\n" +"Clone Set: WebFSClone Started: [ pcmk-1 pcmk-2 ]\n" +"Clone Set: WebSiteClone Started: [ pcmk-1 pcmk-2 ]" msgstr "" #. Tag: title #, no-c-format msgid "Testing Recovery" msgstr "" #. Tag: para #, no-c-format msgid "TODO: Put one node into standby to demonstrate failover" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot b/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot index 6fe8efa690..76853e2dc7 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Active-Passive.pot @@ -1,502 +1,470 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" msgstr "" #. Tag: title #, no-c-format msgid "Exploring the Existing Configuration" msgstr "" #. Tag: para #, no-c-format msgid "When Pacemaker starts up, it automatically records the number and details of the nodes in the cluster as well as which stack is being used and the version of Pacemaker being used." msgstr "" #. Tag: para #, no-c-format msgid "This is what the base configuration should look like." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-2 ~]# crm configure show\n" +msgid "# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\"\n" -"" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\"" msgstr "" #. Tag: para #, no-c-format -msgid "For those that are not of afraid of XML, you can see the raw configuration by appending “xml” to the previous command." +msgid "For those that are not of afraid of XML, you can see the raw configuration by appending \"xml\" to the previous command." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-2 ~]# crm configure show xml\n" +msgid "# crm configure show xml\n" "<?xml version=\"1.0\" ?>\n" "<cib admin_epoch=\"0\" crm_feature_set=\"3.0.1\" dc-uuid=\"pcmk-1\" epoch=\"13\" have-quorum=\"1\" num_updates=\"7\" validate-with=\"pacemaker-1.0\">\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.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\"/>\n" -"        <nvpair id=\"cib-bootstrap-options-cluster-infrastructure\" name=\"cluster-infrastructure\" value=\"openais\"/>\n" -"        <nvpair id=\"cib-bootstrap-options-expected-quorum-votes\" name=\"expected-quorum-votes\" value=\"2\"/>\n" -"      </cluster_property_set>\n" -"    </crm_config>\n" -"    <rsc_defaults/>\n" -"    <op_defaults/>\n" -"    <nodes>\n" -"      <node id=\"pcmk-1\" type=\"normal\" uname=\"pcmk-1\"/>\n" -"      <node id=\"pcmk-2\" type=\"normal\" uname=\"pcmk-2\"/>\n" -"    </nodes>\n" -"    <resources/>\n" -"    <constraints/>\n" -"  </configuration>\n" -"</cib>\n" -"" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "The last XML you’ll see in this document" +" <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.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\"/>\n" +" <nvpair id=\"cib-bootstrap-options-cluster-infrastructure\" name=\"cluster-infrastructure\" value=\"openais\"/>\n" +" <nvpair id=\"cib-bootstrap-options-expected-quorum-votes\" name=\"expected-quorum-votes\" value=\"2\"/>\n" +" </cluster_property_set>\n" +" </crm_config>\n" +" <rsc_defaults/>\n" +" <op_defaults/>\n" +" <nodes>\n" +" <node id=\"pcmk-1\" type=\"normal\" uname=\"pcmk-1\"/>\n" +" <node id=\"pcmk-2\" type=\"normal\" uname=\"pcmk-2\"/>\n" +" </nodes>\n" +" <resources/>\n" +" <constraints/>\n" +" </configuration>\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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm_verify -L\n" -"crm_verify[2195]: 2009/08/27_16:57:12 ERROR: unpack_resources: Resource start-up disabled since no STONITH resources have been defined\n" +msgid "# crm_verify -L\n" +"crm_verify[2195]: 2009/08/27_16:57:12 ERROR: unpack_resources: Resource start-up disabled since no STONITH resources have been defined\n" "crm_verify[2195]: 2009/08/27_16:57:12 ERROR: unpack_resources: Either configure some or disable STONITH with the stonith-enabled option\n" "crm_verify[2195]: 2009/08/27_16:57:12 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\n" -"[root@pcmk-1 ~]#\n" -"" +"Errors found during check: config not valid -V may provide more details\n" +"#" 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 , Pacemaker ships with STONITH A common node fencing mechanism. Used to ensure data integrity by powering off “bad” nodes. 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 , Pacemaker ships with STONITH A common node fencing mechanism. Used to ensure data integrity by powering off \"bad\" nodes 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." msgstr "" #. Tag: para #, no-c-format msgid "To disable STONITH, we set the stonith-enabled cluster option to false." msgstr "" -#. Tag: para +#. Tag: programlisting #, no-c-format -msgid "crm configure property stonith-enabled=false" +msgid "# crm configure property stonith-enabled=false\n" +"# crm_verify -L" msgstr "" #. Tag: para #, no-c-format -msgid "crm_verify -L" +msgid "With the new cluster option set, the configuration is now valid." msgstr "" #. Tag: para #, no-c-format -msgid "With the new cluster option set, the configuration is now valid." +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." msgstr "" #. Tag: title #, no-c-format msgid "Adding 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.101 as the floating address, give it the imaginative name ClusterIP and tell the cluster to check that its running every 30 seconds." msgstr "" #. Tag: para #, no-c-format msgid "The chosen address must not be one already associated with a physical node" msgstr "" -#. Tag: screen +#. Tag: programlisting +#, no-c-format +msgid "# crm configure primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" +" params ip=192.168.122.101 cidr_netmask=32 \\\n" +" op monitor interval=30s" +msgstr "" + +#. Tag: para #, no-c-format -msgid "\n" -"crm configure primitive ClusterIP ocf:heartbeat:IPaddr2 \\ \n" -"        params ip=192.168.122.101 cidr_netmask=32 \\ \n" -"        op monitor interval=30s\n" -"" +msgid "The other important piece of information here is ocf:heartbeat:IPaddr2." msgstr "" #. Tag: para #, no-c-format -msgid "The other important piece of information here is ocf:heartbeat:IPaddr2. 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 "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." msgstr "" #. Tag: para #, no-c-format msgid "To obtain a list of the available resource classes, run" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm ra classes\n" -"heartbeat\n" -"lsb\n" -"ocf / heartbeat pacemaker\n" -"stonith\n" -"" +msgid "# crm ra classesheartbeat\n" +"lsb ocf / heartbeat pacemakerstonith" msgstr "" #. Tag: para #, no-c-format msgid "To then find all the OCF resource agents provided by Pacemaker and Heartbeat, run" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm ra list ocf pacemaker\n" -"ClusterMon     Dummy          Stateful       SysInfo        SystemHealth   controld\n" -"ping           pingd          \n" -"[root@pcmk-1 ~]# crm ra list ocf heartbeat\n" -"AoEtarget              AudibleAlarm           ClusterMon             Delay\n" -"Dummy                  EvmsSCC                Evmsd                  Filesystem\n" -"ICP                    IPaddr                 IPaddr2                IPsrcaddr\n" -"LVM                    LinuxSCSI              MailTo                 ManageRAID\n" -"ManageVE               Pure-FTPd              Raid1                  Route\n" -"SAPDatabase            SAPInstance            SendArp                ServeRAID\n" -"SphinxSearchDaemon     Squid                  Stateful               SysInfo\n" -"VIPArip                VirtualDomain          WAS                    WAS6\n" -"WinPopup               Xen                    Xinetd                 anything\n" -"apache                 db2                    drbd                   eDir88\n" -"iSCSILogicalUnit       iSCSITarget            ids                    iscsi\n" -"ldirectord             mysql                  mysql-proxy            nfsserver\n" -"oracle                 oralsnr                pgsql                  pingd\n" -"portblock              rsyncd                 scsi2reservation       sfex\n" -"tomcat                 vmware                 \n" -"[root@pcmk-1 ~]#\n" -"" +msgid "# crm ra list ocf pacemaker\n" +"ClusterMon Dummy Stateful SysInfo SystemHealth controld\n" +"ping pingd\n" +"# crm ra list ocf heartbeat\n" +"AoEtarget AudibleAlarm ClusterMon Delay\n" +"Dummy EvmsSCC Evmsd Filesystem\n" +"ICP IPaddr IPaddr2 IPsrcaddr\n" +"LVM LinuxSCSI MailTo ManageRAID\n" +"ManageVE Pure-FTPd Raid1 Route\n" +"SAPDatabase SAPInstance SendArp ServeRAID\n" +"SphinxSearchDaemon Squid Stateful SysInfo\n" +"VIPArip VirtualDomain WAS WAS6\n" +"WinPopup Xen Xinetd anything\n" +"apache db2 drbd eDir88\n" +"iSCSILogicalUnit iSCSITarget ids iscsi\n" +"ldirectord mysql mysql-proxy nfsserver\n" +"oracle oralsnr pgsql pingd\n" +"portblock rsyncd scsi2reservation sfex\n" +"tomcat vmware\n" +"#" msgstr "" #. Tag: para #, no-c-format msgid "Now verify that the IP resource has been added and display the cluster’s status to see that it is now active." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure show\n" -"node pcmk-1\n" -"node pcmk-2\n" -"primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" -" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" -" op monitor interval=\"30s\"\n" +msgid "# crm configure shownode pcmk-1\n" +"node pcmk-2primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"[root@pcmk-1 ~]# crm_mon\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +"# crm_mon\n" "============\n" "Last updated: Fri Aug 28 15:23:48 2009\n" "Stack: openais\n" "Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "1 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" -"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1\n" -"" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1" 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." msgstr "" #. Tag: para #, no-c-format msgid "First, find the node on which the IP address is running." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm resource status ClusterIP\n" +msgid "# crm resource status ClusterIP\n" "resource ClusterIP is running on: pcmk-1\n" -"[root@pcmk-1 ~]#\n" -"" +"#" msgstr "" #. Tag: para #, no-c-format -msgid "Shut down Corosync on that machine." +msgid "Shut down Pacemaker and Corosync on that machine." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# ssh pcmk-1 -- /etc/init.d/corosync stop\n" -"Stopping Corosync Cluster Engine (corosync): [ OK ]\n" -"Waiting for services to unload: [ OK ]\n" -"[root@pcmk-1 ~]#\n" -"" +msgid "# ssh pcmk-1 -- /etc/init.d/pacemaker stop\n" +"Signaling Pacemaker Cluster Manager to terminate: [ OK ]\n" +"Waiting for cluster services to unload:. [ OK ]\n" +"# ssh pcmk-1 -- /etc/init.d/corosync stop\n" +"Stopping Corosync Cluster Engine (corosync): [ OK ]\n" +"Waiting for services to unload: [ OK ]\n" +"#" msgstr "" #. Tag: para #, no-c-format msgid "Once Corosync is no longer running, go to the other node and check the cluster status with crm_mon." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-2 ~]# crm_mon\n" +msgid "# crm_mon\n" "============\n" "Last updated: Fri Aug 28 15:27:35 2009\n" "Stack: openais\n" -"Current DC: pcmk-2 - partition WITHOUT quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Current DC: pcmk-2 - partition WITHOUT quorum\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "1 Resources configured.\n" "============\n" "\n" -"Online: [ pcmk-2 ]\n" -"OFFLINE: [ pcmk-1 ]\n" -"" +"Online: [ pcmk-2 ]OFFLINE: [ pcmk-1 ]" 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!" msgstr "" #. Tag: title #, no-c-format msgid "Quorum and Two-Node Clusters" 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” (emphasised green) in the output above. 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 "This is because the cluster no longer has quorum, as can be seen by the text \"partition WITHOUT quorum\" (emphasised green) in the output above. 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." 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:" msgstr "" -#. Tag: para +#. Tag: literallayout #, no-c-format -msgid "total_nodes - 1 < 2 * active_nodes" +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 "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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure property no-quorum-policy=ignore\n" -"[root@pcmk-1 ~]# crm configure show \n" +msgid "# crm configure property no-quorum-policy=ignore\n" +"# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" -"        params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" -"        op monitor interval=\"30s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" -"" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"" 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-2 ~]# crm_mon\n" +msgid "# crm_mon\n" "============\n" "Last updated: Fri Aug 28 15:30:18 2009\n" "Stack: openais\n" -"Current DC: pcmk-2 - partition WITHOUT quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Current DC: pcmk-2 - partition WITHOUT quorum\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "1 Resources configured.\n" "============\n" "Online: [ pcmk-2 ]\n" -"OFFLINE: [ pcmk-1 ]\n" -"\n" -"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2\n" -"" +"OFFLINE: [ pcmk-1 ]\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2" 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# /etc/init.d/corosync start\n" -"Starting Corosync Cluster Engine (corosync): [ OK ] \n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# /etc/init.d/corosync start\n" +"Starting Corosync Cluster Engine (corosync): [ OK ]\n" +"# /etc/init.d/pacemaker start\n" +"Starting Pacemaker Cluster Manager: [ OK ]# crm_mon\n" "============\n" "Last updated: Fri Aug 28 15:32:13 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "1 Resources configured.\n" "============\n" -"Online: [ pcmk-1 pcmk-2 ]\n" +"Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-1\n" -"" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1" msgstr "" #. Tag: para #, no-c-format msgid "Here we see something that some may consider surprising, the IP is back running at its original location!" msgstr "" #. Tag: title #, no-c-format msgid "Prevent Resources from Moving after Recovery" msgstr "" #. Tag: para #, no-c-format -msgid "In some circumstances it is highly desirable to prevent healthy resources from being moved around the cluster. Move resources almost always requires a period of downtime and for complex services like Oracle databases, this period can be quite long." +msgid "In some 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." 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 create implicit preferences (required in order to create a stabile solution) in situations where the administrator had not explicitly specified some. ” 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 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm configure rsc_defaults resource-stickiness=100\n" -"[root@pcmk-2 ~]# crm configure show\n" +msgid "# crm configure rsc_defaults resource-stickiness=100\n" +"# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" -"        params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" -"        op monitor interval=\"30s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" -"rsc_defaults $id=\"rsc-options\" \\\n" -" resource-stickiness=\"100\"\n" -"" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"rsc_defaults $id=\"rsc-options\" \\\n" +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "If we now retry the failover test, we see that as expected ClusterIP still moves to pcmk-2 when pcmk-1 is taken offline." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# ssh pcmk-1 -- /etc/init.d/corosync stop\n" -"Stopping Corosync Cluster Engine (corosync):               [  OK  ]\n" -"Waiting for services to unload:                            [  OK  ]\n" -"[root@pcmk-1 ~]# ssh pcmk-2 -- crm_mon -1\n" +msgid "# ssh pcmk-1 -- /etc/init.d/pacemaker stop\n" +"Signaling Pacemaker Cluster Manager to terminate: [ OK ]\n" +"Waiting for cluster services to unload:. [ OK ]\n" +"# ssh pcmk-1 -- /etc/init.d/corosync stop\n" +"Stopping Corosync Cluster Engine (corosync): [ OK ]\n" +"Waiting for services to unload: [ OK ]\n" +"# ssh pcmk-2 -- crm_mon -1\n" "============\n" "Last updated: Fri Aug 28 15:39:38 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition WITHOUT quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "1 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-2 ]\n" -"OFFLINE: [ pcmk-1 ]\n" -"\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"" +"OFFLINE: [ pcmk-1 ]\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2" msgstr "" #. Tag: para #, no-c-format msgid "However when we bring pcmk-1 back online, ClusterIP now remains running on pcmk-2." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# /etc/init.d/corosync start\n" -"Starting Corosync Cluster Engine (corosync): [ OK ]\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# /etc/init.d/corosync start\n" +"Starting Corosync Cluster Engine (corosync): [ OK ]\n" +"# /etc/init.d/pacemaker start\n" +"Starting Pacemaker Cluster Manager: [ OK ]\n" +"# crm_mon\n" "============\n" "Last updated: Fri Aug 28 15:41:23 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "1 Resources configured.\n" "============\n" "\n" -"Online: [ pcmk-1 pcmk-2 ]\n" +"Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Apache.pot b/doc/Clusters_from_Scratch/pot/Ch-Apache.pot index 940736fd88..d8743a8e24 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Apache.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Apache.pot @@ -1,566 +1,542 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" +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." msgstr "" #. Tag: title #, no-c-format msgid "Installation" msgstr "" #. Tag: para #, no-c-format -msgid "Before continuing, we need to make sure Apache is installed on both hosts." +msgid "Before continuing, we need to make sure Apache is installed on both hosts." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@ppcmk-1 ~]# yum install -y httpd\n" -"Setting up Install Process\n" +msgid "# yum install -y httpdSetting up Install Process\n" "Resolving Dependencies\n" "--> Running transaction check\n" "---> Package httpd.x86_64 0:2.2.13-2.fc12 set to be updated\n" "--> Processing Dependency: httpd-tools = 2.2.13-2.fc12 for package: httpd-2.2.13-2.fc12.x86_64\n" "--> Processing Dependency: apr-util-ldap for package: httpd-2.2.13-2.fc12.x86_64\n" "--> Processing Dependency: /etc/mime.types for package: httpd-2.2.13-2.fc12.x86_64\n" "--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.2.13-2.fc12.x86_64\n" "--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.2.13-2.fc12.x86_64\n" "--> Running transaction check\n" "---> Package apr.x86_64 0:1.3.9-2.fc12 set to be updated\n" "---> Package apr-util.x86_64 0:1.3.9-2.fc12 set to be updated\n" "---> Package apr-util-ldap.x86_64 0:1.3.9-2.fc12 set to be updated\n" "---> Package httpd-tools.x86_64 0:2.2.13-2.fc12 set to be updated\n" "---> Package mailcap.noarch 0:2.1.30-1.fc12 set to be updated\n" "--> Finished Dependency Resolution\n" "\n" "Dependencies Resolved\n" "\n" "=======================================================================================\n" -" Package               Arch             Version                Repository         Size\n" +"Package Arch Version Repository Size\n" "=======================================================================================\n" "Installing:\n" -" httpd               x86_64           2.2.13-2.fc12            rawhide           735 k\n" +"httpd x86_64 2.2.13-2.fc12 rawhide 735 k\n" "Installing for dependencies:\n" -" apr                 x86_64           1.3.9-2.fc12             rawhide           117 k\n" -" apr-util            x86_64           1.3.9-2.fc12             rawhide            84 k\n" -" apr-util-ldap       x86_64           1.3.9-2.fc12             rawhide            15 k\n" -" httpd-tools         x86_64           2.2.13-2.fc12            rawhide            63 k\n" -" mailcap             noarch           2.1.30-1.fc12            rawhide            25 k\n" +"apr x86_64 1.3.9-2.fc12 rawhide 117 k\n" +"apr-util x86_64 1.3.9-2.fc12 rawhide 84 k\n" +"apr-util-ldap x86_64 1.3.9-2.fc12 rawhide 15 k\n" +"httpd-tools x86_64 2.2.13-2.fc12 rawhide 63 k\n" +"mailcap noarch 2.1.30-1.fc12 rawhide 25 k\n" "\n" "Transaction Summary\n" "=======================================================================================\n" -"Install       6 Package(s)\n" -"Upgrade       0 Package(s)\n" +"Install 6 Package(s)\n" +"Upgrade 0 Package(s)\n" "\n" "Total download size: 1.0 M\n" "Downloading Packages:\n" -"(1/6): apr-1.3.9-2.fc12.x86_64.rpm                                   | 117 kB     00:00     \n" -"(2/6): apr-util-1.3.9-2.fc12.x86_64.rpm                             |  84 kB     00:00     \n" -"(3/6): apr-util-ldap-1.3.9-2.fc12.x86_64.rpm                         |  15 kB     00:00     \n" -"(4/6): httpd-2.2.13-2.fc12.x86_64.rpm                               | 735 kB     00:00     \n" -"(5/6): httpd-tools-2.2.13-2.fc12.x86_64.rpm                         |  63 kB     00:00     \n" -"(6/6): mailcap-2.1.30-1.fc12.noarch.rpm                             |  25 kB     00:00     \n" -"----------------------------------------------------------------------------------------\n" -"Total                                                       875 kB/s | 1.0 MB     00:01     \n" +"(1/6): apr-1.3.9-2.fc12.x86_64.rpm | 117 kB 00:00\n" +"(2/6): apr-util-1.3.9-2.fc12.x86_64.rpm | 84 kB 00:00\n" +"(3/6): apr-util-ldap-1.3.9-2.fc12.x86_64.rpm | 15 kB 00:00\n" +"(4/6): httpd-2.2.13-2.fc12.x86_64.rpm | 735 kB 00:00\n" +"(5/6): httpd-tools-2.2.13-2.fc12.x86_64.rpm | 63 kB 00:00\n" +"(6/6): mailcap-2.1.30-1.fc12.noarch.rpm | 25 kB 00:00\n" +" ----------------------------------------------------------------------------------------\n" +"Total 875 kB/s | 1.0 MB 00:01\n" "Running rpm_check_debug\n" "Running Transaction Test\n" "Finished Transaction Test\n" "Transaction Test Succeeded\n" "Running Transaction\n" -"  Installing     : apr-1.3.9-2.fc12.x86_64                                         1/6 \n" -"  Installing     : apr-util-1.3.9-2.fc12.x86_64                                     2/6 \n" -"  Installing     : apr-util-ldap-1.3.9-2.fc12.x86_64                               3/6 \n" -"  Installing     : httpd-tools-2.2.13-2.fc12.x86_64                                 4/6 \n" -"  Installing     : mailcap-2.1.30-1.fc12.noarch                                     5/6 \n" -"  Installing     : httpd-2.2.13-2.fc12.x86_64                                       6/6 \n" +" Installing : apr-1.3.9-2.fc12.x86_64 1/6\n" +" Installing : apr-util-1.3.9-2.fc12.x86_64 2/6\n" +" Installing : apr-util-ldap-1.3.9-2.fc12.x86_64 3/6\n" +" Installing : httpd-tools-2.2.13-2.fc12.x86_64 4/6\n" +" Installing : mailcap-2.1.30-1.fc12.noarch 5/6\n" +" Installing : httpd-2.2.13-2.fc12.x86_64 6/6\n" "\n" "Installed:\n" -"  httpd.x86_64 0:2.2.13-2.fc12                                                         \n" +" httpd.x86_64 0:2.2.13-2.fc12\n" "\n" "Dependency Installed:\n" -"  apr.x86_64 0:1.3.9-2.fc12            apr-util.x86_64 0:1.3.9-2.fc12\n" -"  apr-util-ldap.x86_64 0:1.3.9-2.fc12  httpd-tools.x86_64 0:2.2.13-2.fc12\n" -"  mailcap.noarch 0:2.1.30-1.fc12  \n" +" apr.x86_64 0:1.3.9-2.fc12 apr-util.x86_64 0:1.3.9-2.fc12\n" +" apr-util-ldap.x86_64 0:1.3.9-2.fc12 httpd-tools.x86_64 0:2.2.13-2.fc12\n" +" mailcap.noarch 0:2.1.30-1.fc12\n" "\n" -"Complete!\n" -"[root@pcmk-1 ~]#\n" -"" +"Complete!" msgstr "" #. Tag: para #, no-c-format msgid "Also, we need the wget tool in order for the cluster to be able to check the status of the Apache server." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# yum install -y wget\n" -"Setting up Install Process\n" +msgid "# yum install -y wgetSetting up Install Process\n" "Resolving Dependencies\n" "--> Running transaction check\n" "---> Package wget.x86_64 0:1.11.4-5.fc12 set to be updated\n" "--> Finished Dependency Resolution\n" "\n" "Dependencies Resolved\n" "\n" "===========================================================================================\n" -" Package        Arch             Version                      Repository               Size\n" +"Package Arch Version Repository Size\n" "===========================================================================================\n" "Installing:\n" -" wget         x86_64          1.11.4-5.fc12                   rawhide                393 k\n" +"wget x86_64 1.11.4-5.fc12 rawhide 393 k\n" "\n" "Transaction Summary\n" "===========================================================================================\n" -"Install       1 Package(s)\n" -"Upgrade       0 Package(s)\n" +"Install 1 Package(s)\n" +"Upgrade 0 Package(s)\n" "\n" "Total download size: 393 k\n" "Downloading Packages:\n" -"wget-1.11.4-5.fc12.x86_64.rpm                                            | 393 kB     00:00     \n" +"wget-1.11.4-5.fc12.x86_64.rpm | 393 kB 00:00\n" "Running rpm_check_debug\n" "Running Transaction Test\n" "Finished Transaction Test\n" "Transaction Test Succeeded\n" "Running Transaction\n" -"  Installing     : wget-1.11.4-5.fc12.x86_64                                            1/1 \n" +" Installing : wget-1.11.4-5.fc12.x86_64 1/1\n" "\n" "Installed:\n" -"  wget.x86_64 0:1.11.4-5.fc12\n" +" wget.x86_64 0:1.11.4-5.fc12\n" "\n" -"Complete!\n" -"[root@pcmk-1 ~]#\n" -"" +"Complete!" msgstr "" #. Tag: title #, no-c-format msgid "Preparation" 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# cat <<-END >/var/www/html/index.html\n" -" <html>\n" +msgid "[root@pcmk-1 ~]# cat <<-END >/var/www/html/index.html <html>\n" " <body>My Test Site - pcmk-1</body>\n" " </html>\n" -" END\n" -"[root@pcmk-1 ~]#\n" -"" +" END" msgstr "" #. Tag: para #, 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-2 ~]# cat <<-END >/var/www/html/index.html\n" -" <html>\n" +msgid "[root@pcmk-2 ~]# cat <<-END >/var/www/html/index.html <html>\n" " <body>My Test Site - pcmk-2</body>\n" " </html>\n" -" END\n" -"[root@pcmk-2 ~]#\n" -"" +" END" msgstr "" #. Tag: title #, no-c-format msgid "Enable the Apache status URL" 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: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"<Location /server-status>\n" +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>\n" -" " +"</Location>" msgstr "" #. Tag: title #, no-c-format msgid "Update the Configuration" 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, 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure primitive WebSite ocf:heartbeat:apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=1min\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "# crm configure primitive WebSite ocf:heartbeat:apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=1min\n" +"# crm configure show\n" "node pcmk-1\n" -"node pcmk-2\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\" \\\n" -"        op monitor interval=\"30s\"\n" +"node pcmk-2primitive WebSite ocf:heartbeat:apache \\ params configfile=\"/etc/httpd/conf/httpd.conf\" \\ op monitor interval=\"1min\"primitive ClusterIP ocf:heartbeat:IPaddr2 \\\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=\"100\"\n" -"" +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "After a short delay, we should see the cluster start apache" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# crm_mon\n" "============\n" "Last updated: Fri Aug 28 16:12:49 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "2 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"WebSite        (ocf::heartbeat:apache):        Started pcmk-1\n" -"" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-1" 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: title #, no-c-format msgid "Ensuring 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. If ClusterIP is not active anywhere, WebSite will not be permitted to run anywhere." +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 "For the constraint, we need a name (choose something descriptive like website-with-ip), indicate that its mandatory (so that if ClusterIP is not active anywhere, WebSite will not be permitted to run anywhere either) by specifying a score of INFINITY and finally list the two resources." +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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure colocation website-with-ip INFINITY: WebSite ClusterIP\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "# crm configure colocation website-with-ip INFINITY: WebSite ClusterIP\n" +"# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" -"colocation website-with-ip inf: WebSite ClusterIP\n" -"property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"colocation website-with-ip inf: WebSite ClusterIPproperty $id=\"cib-bootstrap-options\" \\\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=\"100\"\n" -"[root@pcmk-1 ~]# crm_mon\n" +" resource-stickiness=\"100\"\n" +"# crm_mon\n" "============\n" "Last updated: Fri Aug 28 16:14:34 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "2 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"WebSite        (ocf::heartbeat:apache):        Started pcmk-2\n" -"" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-2" msgstr "" #. Tag: title #, no-c-format msgid "Controlling Resource Start/Stop Ordering" 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. We need to give it a name (chose something descriptive like apache-after-ip), indicate that its mandatory (so that any recovery for ClusterIP will also trigger recovery of WebSite) and list the two resources in the order we need them to start." +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. We need to give it a name (choose something descriptive like apache-after-ip), indicate that its mandatory (so that any recovery for ClusterIP will also trigger recovery of WebSite) and list the two resources in the order we need them to start." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure order apache-after-ip mandatory: ClusterIP WebSite\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "# crm configure order apache-after-ip mandatory: ClusterIP WebSite\n" +"# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" -"colocation website-with-ip inf: WebSite ClusterIP\n" -"order apache-after-ip inf: ClusterIP WebSite\n" -"property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" +"colocation website-with-ip inf: WebSite ClusterIPorder apache-after-ip inf: ClusterIP WebSiteproperty $id=\"cib-bootstrap-options\" \\\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=\"100\"\n" -"" +" resource-stickiness=\"100\"" msgstr "" #. Tag: title #, no-c-format msgid "Specifying a Preferred Location" 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. Again we give it a descriptive name (prefer-pcmk-1), specify the resource we want to run there (WebSite), how badly we’d like it to run there (we’ll use 50 for now, but in a two-node situation almost any value above 0 will do) and the host’s name." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure location prefer-pcmk-1 WebSite 50: pcmk-1\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "# crm configure location prefer-pcmk-1 WebSite 50: pcmk-1\n" +"# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" -"location prefer-pcmk-1 WebSite 50: pcmk-1\n" -"colocation website-with-ip inf: WebSite ClusterIP\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"location prefer-pcmk-1 WebSite 50: pcmk-1colocation website-with-ip inf: WebSite ClusterIP\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=\"100\"\n" -"[root@pcmk-1 ~]# crm_mon\n" +" resource-stickiness=\"100\"\n" +"# crm_mon\n" "============\n" "Last updated: Fri Aug 28 16:17:35 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "2 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"WebSite        (ocf::heartbeat:apache):        Started pcmk-2\n" -"" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2WebSite (ocf::heartbeat:apache): Started pcmk-2" 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)." msgstr "" #. Tag: para #, no-c-format msgid "To see the current placement scores, you can use a tool called ptest" msgstr "" -#. Tag: para +#. Tag: literallayout #, no-c-format msgid "ptest -sL" msgstr "" #. Tag: para #, no-c-format -msgid "Include output" -msgstr "" - -#. Tag: para -#, no-c-format -msgid "There is a way to force them to move though..." +msgid "Include output There is a way to force them to move though…" msgstr "" #. Tag: title #, no-c-format msgid "Manually Moving Resources Around the Cluster" 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. Underneath we use location constraints like the one we created above, happily you don’t need to care. Just provide the name of the resource and the intended location, we’ll do the rest." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm resource move WebSite pcmk-1\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# crm resource move WebSite pcmk-1\n" +"# crm_mon\n" "============\n" "Last updated: Fri Aug 28 16:19:24 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "2 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-1\n" -"WebSite        (ocf::heartbeat:apache):        Started pcmk-1\n" -"Notice how the colocation rule we created has ensured that ClusterIP was also moved to pcmk-1.\n" -"For the curious, we can see the effect of this command by examining the configuration\n" -"crm configure show\n" -"[root@pcmk-1 ~]# crm configure show\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-1" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Notice how the colocation rule we created has ensured that ClusterIP was also moved to pcmk-1. For the curious, we can see the effect of this command by examining the configuration" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" -"location cli-prefer-WebSite WebSite \\\n" -" rule $id=\"cli-prefer-rule-WebSite\" inf: #uname eq pcmk-1\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" +"location cli-prefer-WebSite WebSite \\\n" +" rule $id=\"cli-prefer-rule-WebSite\" inf: #uname eq pcmk-1\n" "location prefer-pcmk-1 WebSite 50: pcmk-1\n" "colocation website-with-ip inf: WebSite ClusterIP\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=\"100\"\n" -"" +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "Highlighted is the automated constraint used to move the resources to pcmk-1" msgstr "" #. Tag: title #, no-c-format msgid "Giving Control Back to the Cluster" 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm resource unmove WebSite\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "# crm resource unmove WebSite\n" +"# crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "location prefer-pcmk-1 WebSite 50: pcmk-1\n" "colocation website-with-ip inf: WebSite ClusterIP\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=\"2\" \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=\"100\"\n" -"" +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "Note that the automated constraint is now gone. If we check the cluster status, we can also see that as expected the resources are still active on pcmk-1." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# crm_mon\n" "============\n" "Last updated: Fri Aug 28 16:20:53 2009\n" "Stack: openais\n" "Current DC: pcmk-2 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "2 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -" ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-1\n" -" WebSite        (ocf::heartbeat:apache):        Started pcmk-1\n" -"" +" ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1\n" +" WebSite (ocf::heartbeat:apache): Started pcmk-1" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Installation.pot b/doc/Clusters_from_Scratch/pot/Ch-Installation.pot index d7ea09d8a2..b93fa404c3 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Installation.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Installation.pot @@ -1,986 +1,970 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" msgstr "" #. Tag: para #, no-c-format -msgid "Detailed instructions for installing Fedora are available at http://docs.fedoraproject.org/install-guide/f&DISTRO_VERSION;/ in a number of languages. The abbreviated version is as follows..." +msgid "Detailed instructions for installing Fedora are available at http://docs.fedoraproject.org/install-guide/f13/ in a number of languages. The abbreviated version is as follows…" 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 "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." msgstr "" #. Tag: para #, no-c-format -msgid "Burn the disk image to a DVD http://docs.fedoraproject.org/readme-burning-isos/en-US.html and boot from it. Or use the image to boot a virtual machine as I have done here. After clicking through the welcome screen, select your language and keyboard layout http://docs.fedoraproject.org/install-guide/f&DISTRO_VERSION;/en-US/html/s1-langselection-x86.html " +msgid "Burn the disk image to a DVD http://docs.fedoraproject.org/readme-burning-isos/en-US.html and boot from it. Or use the image to boot a virtual machine as I have done here. After clicking through the welcome screen, select your language and keyboard layout http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-langselection-x86.html" msgstr "" #. Tag: title #, no-c-format -msgid "Fedora Installation - Welcome" +msgid "Installation: Good choice" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Good choice" +msgid "Welcome" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Storage Devices" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Storage Devices" +msgid "Storage Devices" msgstr "" #. Tag: para #, no-c-format -msgid "Assign your machine a host name. http://docs.fedoraproject.org/install-guide/f&DISTRO_VERSION;/en-US/html/sn-networkconfig-fedora.html I happen to control the clusterlabs.org domain name, so I will use that here." +msgid "Assign your machine a host name. http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-networkconfig-fedora.html I happen to control the clusterlabs.org domain name, so I will use that here." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Hostname" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Choose a hostname" +msgid "Hostname" msgstr "" #. Tag: para #, no-c-format -msgid "You will then be prompted to indicate the machine’s physical location and to supply a root password. http://docs.fedoraproject.org/install-guide/f&DISTRO_VERSION;/en-US/html/sn-account_configuration.html " +msgid "You will then be prompted to indicate the machine’s physical location and to supply a root password. http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-account_configuration.html" msgstr "" #. Tag: para #, no-c-format -msgid "Now select where you want Fedora installed. http://docs.fedoraproject.org/install-guide/f13/en-US/html/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. However I want to reserve some space for DRBD, so I'll check the Review and modify partitioning layout box." +msgid "Now select where you want Fedora installed. http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-diskpartsetup-x86.html" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "As I don’t care about any existing data, I will accept the default and allow Fedora to use the complete drive. However I want to reserve some space for DRBD, so I’ll check the Review and modify partitioning layout box." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Installation Type" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Choose an installation type" +msgid "Choose Install Type" msgstr "" #. Tag: para #, no-c-format -msgid "By default, Fedora will give all the space to the / (aka. root) partition. Wel'll take some back so we can use DRBD." +msgid "By default, Fedora will give all the space to the / (aka. root) partition. Wel’ll take some back so we can use DRBD." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Default Partitioning" msgstr "" +#. Tag: phrase +#, no-c-format +msgid "Default Partitioning" +msgstr "" + #. Tag: para #, no-c-format msgid "The finalized partition layout should look something like the diagram below." msgstr "" #. Tag: para #, no-c-format -msgid "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." +msgid "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. Fedora Installation - Customize PartitioningFedora Installation: Create a partition to use (later) for website data" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Customize Partitioning" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Create a partition to use (later) for website data" +msgid "Customize Partitioning" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Bootloader" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Unless you have a strong reason not to, accept the default bootloader location" +msgid "Unless you have a strong reason not to, accept the default bootloader location" msgstr "" #. Tag: para #, no-c-format -msgid "Next choose which software should be installed. Change the selection to Web Server since we plan on using Apache. 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 "Next choose which software should be installed. Change the selection to Web Server since we plan on using Apache. 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." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Software" msgstr "" -#. Tag: caption +#. Tag: phrase +#, no-c-format +msgid "Software selection" +msgstr "" + +#. Tag: para #, no-c-format -msgid "Fedora Installation: Software selection" +msgid "Go grab something to drink, this may take a while" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Installing" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Go grab something to drink, this may take a while" +msgid "Installing" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Installation Complete" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Stage 1, completed" +msgid "Stage 1, completed" msgstr "" #. Tag: para #, no-c-format -msgid "Once the node reboots, follow the on screen instructions http://docs.fedoraproject.org/install-guide/f&DISTRO_VERSION;/en-US/html/ch-firstboot.html to create a system user and configure the time." +msgid "Once the node reboots, follow the on screen instructions http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-firstboot.html to create a system user and configure the time." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - First Boot" msgstr "" +#. Tag: phrase +#, no-c-format +msgid "First boot" +msgstr "" + #. Tag: title #, no-c-format msgid "Fedora Installation - Create Non-privileged User" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Creating a non-privileged user, take note of the password, you'll need it soon" +msgid "Creating a new user, take note of the password, you'll need it soon" 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." +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. Fedora Installation - Date and TimeFedora Installation: Enable NTP to keep the times on all your nodes consistent" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Date and Time" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Enable NTP to keep the times on all your nodes consistent" +msgid "Date and time" msgstr "" #. Tag: para #, no-c-format msgid "Click through the next screens until you reach the login window. Click on the user you created and supply the password you indicated earlier." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Customize Networking" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Click here to configure networking" +msgid "Click here to configure networking" msgstr "" #. Tag: para #, no-c-format -msgid "Do not accept the default network settings. Cluster machines should never obtain an ip address via DHCP. Here I will use the internal addresses for the clusterlab.org network." +msgid "Do not accept the default network settings. Cluster machines should never obtain an ip address via DHCP. Here I will use the internal addresses for the clusterlab.org network." msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Specify Network Preferences" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Specify network settings for your machine, never choose DHCP" +msgid "Specify network settings for your machine, never choose DHCP" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Activate Networking" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Click the big green button to activate your changes" +msgid "Click the big green button to activate your changes" msgstr "" #. Tag: title #, no-c-format msgid "Fedora Installation - Bring up the Terminal" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "Fedora Installation: Down to business, fire up the command line" +msgid "Down to business, fire up the command line" msgstr "" #. Tag: para #, no-c-format msgid "That was the last screenshot, from here on in we’re going to be working from the terminal." msgstr "" #. Tag: title #, no-c-format msgid "Cluster Software Installation" msgstr "" #. Tag: para #, no-c-format -msgid "Go to the terminal window you just opened and switch to the super user (aka. \"root\") account with the su command. You will need to supply the password you entered earlier during the installation process." +msgid "Go to the terminal window you just opened and switch to the super user (aka. \"root\") account with the su command. You will need to supply the password you entered earlier during the installation process." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[beekhof@pcmk-1 ~]$ su -\n" +msgid "[beekhof@pcmk-1 ~]$ su -\n" "Password:\n" -"[root@pcmk-1 ~]#\n" -" " +"[root@pcmk-1 ~]#" msgstr "" #. Tag: para #, no-c-format msgid "Note that the username (the text before the @ symbol) now indicates we’re running as the super user “root”." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# ip addr\n" -"1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN \n" +msgid "# ip addr\n" +"1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 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" +" 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 UNKNOWN qlen 1000\n" " link/ether 00:0c:29:6f:e1:58 brd ff:ff:ff:ff:ff:ff\n" " inet 192.168.9.41/24 brd 192.168.9.255 scope global eth0\n" -" inet6 ::20c:29ff:fe6f:e158/64 scope global dynamic \n" +" inet6 ::20c:29ff:fe6f:e158/64 scope global dynamic\n" " valid_lft 2591667sec preferred_lft 604467sec\n" -" inet6 2002:57ae:43fc:0:20c:29ff:fe6f:e158/64 scope global dynamic \n" +" inet6 2002:57ae:43fc:0:20c:29ff:fe6f:e158/64 scope global dynamic\n" " valid_lft 2591990sec preferred_lft 604790sec\n" -" inet6 fe80::20c:29ff:fe6f:e158/64 scope link \n" +" inet6 fe80::20c:29ff:fe6f:e158/64 scope link\n" " valid_lft forever preferred_lft forever\n" -"[root@pcmk-1 ~]# ping -c 1 www.google.com\n" +"# ping -c 1 www.google.com\n" "PING www.l.google.com (74.125.39.99) 56(84) bytes of data.\n" "64 bytes from fx-in-f99.1e100.net (74.125.39.99): icmp_seq=1 ttl=56 time=16.7 ms\n" "\n" "--- www.l.google.com ping statistics ---\n" "1 packets transmitted, 1 received, 0% packet loss, time 20ms\n" "rtt min/avg/max/mdev = 16.713/16.713/16.713/0.000 ms\n" -"[root@pcmk-1 ~]# /sbin/chkconfig network on\n" -"[root@pcmk-1 ~]# \n" -" " +"# /sbin/chkconfig network on\n" +"#" msgstr "" #. Tag: title #, no-c-format msgid "Security Shortcuts" 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. 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: para +#. Tag: literallayout #, no-c-format msgid "TODO: Create an Appendix that deals with (at least) re-enabling the firewall." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" -"[root@pcmk-1 ~]# /sbin/chkconfig --del iptables\n" -"[root@pcmk-1 ~]# service iptables stop\n" +msgid "# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" +"# /sbin/chkconfig --del iptables\n" +"# service iptables stop\n" "iptables: Flushing firewall rules: [ OK ]\n" "iptables: Setting chains to policy ACCEPT: filter [ OK ]\n" -"iptables: Unloading modules: [ OK ]\n" -" " +"iptables: Unloading modules: [ OK ]" msgstr "" #. Tag: para #, no-c-format msgid "You will need to reboot for the SELinux changes to take effect. Otherwise you will see something like this when you start corosync:" msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"May 4 19:30:54 pcmk-1 setroubleshoot: SELinux is preventing /usr/sbin/corosync \"getattr\" access on /. For complete SELinux messages. run sealert -l 6e0d4384-638e-4d55-9aaf-7dac011f29c1\n" -"May 4 19:30:54 pcmk-1 setroubleshoot: SELinux is preventing /usr/sbin/corosync \"getattr\" access on /. For complete SELinux messages. run sealert -l 6e0d4384-638e-4d55-9aaf-7dac011f29c1\n" -" " +msgid "May 4 19:30:54 pcmk-1 setroubleshoot: SELinux is preventing /usr/sbin/corosync \"getattr\" access on /. For complete SELinux messages. run sealert -l 6e0d4384-638e-4d55-9aaf-7dac011f29c1\n" +"May 4 19:30:54 pcmk-1 setroubleshoot: SELinux is preventing /usr/sbin/corosync \"getattr\" access on /. For complete SELinux messages. run sealert -l 6e0d4384-638e-4d55-9aaf-7dac011f29c1" msgstr "" #. Tag: title #, no-c-format msgid "Install the Cluster Software" 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:" msgstr "" -#. Tag: screen -#, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# sed -i.bak \"s/enabled=0/enabled=1/g\" /etc/yum.repos.d/fedora.repo\n" -"[root@pcmk-1 ~]# sed -i.bak \"s/enabled=0/enabled=1/g\" /etc/yum.repos.d/fedora-updates.repo\n" -"[root@pcmk-1 ~]# yum install -y pacemaker corosync\n" -"Loaded plugins: presto, refresh-packagekit\n" -"fedora/metalink | 22 kB 00:00 \n" -"fedora-debuginfo/metalink | 16 kB 00:00 \n" -"fedora-debuginfo | 3.2 kB 00:00 \n" -"fedora-debuginfo/primary_db | 1.4 MB 00:04 \n" -"fedora-source/metalink | 22 kB 00:00 \n" -"fedora-source | 3.2 kB 00:00 \n" -"fedora-source/primary_db | 3.0 MB 00:05 \n" -"updates/metalink | 26 kB 00:00 \n" -"updates | 2.6 kB 00:00 \n" -"updates/primary_db | 1.1 kB 00:00 \n" -"updates-debuginfo/metalink | 18 kB 00:00 \n" -"updates-debuginfo | 2.6 kB 00:00 \n" -"updates-debuginfo/primary_db | 1.1 kB 00:00 \n" -"updates-source/metalink | 25 kB 00:00 \n" -"updates-source | 2.6 kB 00:00 \n" -"updates-source/primary_db | 1.1 kB 00:00 \n" +#. Tag: literallayout +#, no-c-format +msgid "# sed -i.bak \"s/enabled=0/enabled=1/g\"\n" +"/etc/yum.repos.d/fedora.repo\n" +"# sed -i.bak \"s/enabled=0/enabled=1/g\"\n" +"/etc/yum.repos.d/fedora-updates.repo\n" +"# yum install -y pacemaker corosyncLoaded plugins: presto, refresh-packagekit\n" +"fedora/metalink | 22 kB 00:00\n" +"fedora-debuginfo/metalink | 16 kB 00:00\n" +"fedora-debuginfo | 3.2 kB 00:00\n" +"fedora-debuginfo/primary_db | 1.4 MB 00:04\n" +"fedora-source/metalink | 22 kB 00:00\n" +"fedora-source | 3.2 kB 00:00\n" +"fedora-source/primary_db | 3.0 MB 00:05\n" +"updates/metalink | 26 kB 00:00\n" +"updates | 2.6 kB 00:00\n" +"updates/primary_db | 1.1 kB 00:00\n" +"updates-debuginfo/metalink | 18 kB 00:00\n" +"updates-debuginfo | 2.6 kB 00:00\n" +"updates-debuginfo/primary_db | 1.1 kB 00:00\n" +"updates-source/metalink | 25 kB 00:00\n" +"updates-source | 2.6 kB 00:00\n" +"updates-source/primary_db | 1.1 kB 00:00\n" "Setting up Install Process\n" "Resolving Dependencies\n" "--> Running transaction check\n" "---> Package corosync.x86_64 0:1.2.1-1.fc13 set to be updated\n" "--> Processing Dependency: corosynclib = 1.2.1-1.fc13 for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libquorum.so.4(COROSYNC_QUORUM_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libvotequorum.so.4(COROSYNC_VOTEQUORUM_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libcpg.so.4(COROSYNC_CPG_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libconfdb.so.4(COROSYNC_CONFDB_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libcfg.so.4(COROSYNC_CFG_0.82)(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libpload.so.4(COROSYNC_PLOAD_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: liblogsys.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libconfdb.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libcoroipcc.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libcpg.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libquorum.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libcoroipcs.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libvotequorum.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libcfg.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libtotem_pg.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libpload.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64\n" -"---> Package pacemaker.x86_64 0:1.1.1-1.fc13 set to be updated\n" -"--> Processing Dependency: heartbeat >= 3.0.0 for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: net-snmp >= 5.4 for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: resource-agents for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: cluster-glue for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libnetsnmp.so.20()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libcrmcluster.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libpengine.so.3()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libnetsnmpagent.so.20()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libesmtp.so.5()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libstonithd.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libhbclient.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libpils.so.2()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libpe_status.so.2()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libnetsnmpmibs.so.20()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libnetsnmphelpers.so.20()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libcib.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libccmclient.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libstonith.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: liblrm.so.2()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libtransitioner.so.1()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libpe_rules.so.2()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libcrmcommon.so.2()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" -"--> Processing Dependency: libplumb.so.2()(64bit) for package: pacemaker-1.1.1-1.fc13.x86_64\n" +"---> Package pacemaker.x86_64 0:1.1.5-1.fc13 set to be updated\n" +"--> Processing Dependency: heartbeat >= 3.0.0 for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: net-snmp >= 5.4 for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: resource-agents for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: cluster-glue for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libnetsnmp.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libcrmcluster.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libpengine.so.3()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libnetsnmpagent.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libesmtp.so.5()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libstonithd.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libhbclient.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libpils.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libpe_status.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libnetsnmpmibs.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libnetsnmphelpers.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libcib.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libccmclient.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libstonith.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: liblrm.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libtransitioner.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libpe_rules.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libcrmcommon.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" +"--> Processing Dependency: libplumb.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64\n" "--> Running transaction check\n" "---> Package cluster-glue.x86_64 0:1.0.2-1.fc13 set to be updated\n" "--> Processing Dependency: perl-TimeDate for package: cluster-glue-1.0.2-1.fc13.x86_64\n" "--> Processing Dependency: libOpenIPMIutils.so.0()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64\n" "--> Processing Dependency: libOpenIPMIposix.so.0()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64\n" "--> Processing Dependency: libopenhpi.so.2()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64\n" "--> Processing Dependency: libOpenIPMI.so.0()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64\n" "---> Package cluster-glue-libs.x86_64 0:1.0.2-1.fc13 set to be updated\n" "---> Package corosynclib.x86_64 0:1.2.1-1.fc13 set to be updated\n" "--> Processing Dependency: librdmacm.so.1(RDMACM_1.0)(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libibverbs.so.1(IBVERBS_1.0)(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libibverbs.so.1(IBVERBS_1.1)(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: libibverbs.so.1()(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64\n" "--> Processing Dependency: librdmacm.so.1()(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64\n" "---> Package heartbeat.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13 set to be updated\n" "--> Processing Dependency: PyXML for package: heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64\n" "---> Package heartbeat-libs.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13 set to be updated\n" "---> Package libesmtp.x86_64 0:1.0.4-12.fc12 set to be updated\n" "---> Package net-snmp.x86_64 1:5.5-12.fc13 set to be updated\n" "--> Processing Dependency: libsensors.so.4()(64bit) for package: 1:net-snmp-5.5-12.fc13.x86_64\n" "---> Package net-snmp-libs.x86_64 1:5.5-12.fc13 set to be updated\n" -"---> Package pacemaker-libs.x86_64 0:1.1.1-1.fc13 set to be updated\n" +"---> Package pacemaker-libs.x86_64 0:1.1.5-1.fc13 set to be updated\n" "---> Package resource-agents.x86_64 0:3.0.10-1.fc13 set to be updated\n" "--> Processing Dependency: libnet.so.1()(64bit) for package: resource-agents-3.0.10-1.fc13.x86_64\n" "--> Running transaction check\n" "---> Package OpenIPMI-libs.x86_64 0:2.0.16-8.fc13 set to be updated\n" "---> Package PyXML.x86_64 0:0.8.4-17.fc13 set to be updated\n" "---> Package libibverbs.x86_64 0:1.1.3-4.fc13 set to be updated\n" "--> Processing Dependency: libibverbs-driver for package: libibverbs-1.1.3-4.fc13.x86_64\n" "---> Package libnet.x86_64 0:1.1.4-3.fc12 set to be updated\n" "---> Package librdmacm.x86_64 0:1.0.10-2.fc13 set to be updated\n" "---> Package lm_sensors-libs.x86_64 0:3.1.2-2.fc13 set to be updated\n" "---> Package openhpi-libs.x86_64 0:2.14.1-3.fc13 set to be updated\n" "---> Package perl-TimeDate.noarch 1:1.20-1.fc13 set to be updated\n" "--> Running transaction check\n" "---> Package libmlx4.x86_64 0:1.0.1-5.fc13 set to be updated\n" "--> Finished Dependency Resolution\n" "\n" "Dependencies Resolved\n" "\n" -" " -msgstr "" - -#. Tag: screen -#, no-c-format -msgid "\n" +"\n" "==========================================================================================\n" " Package Arch Version Repository Size\n" "==========================================================================================\n" "Installing:\n" " corosync x86_64 1.2.1-1.fc13 fedora 136 k\n" -" pacemaker x86_64 1.1.1-1.fc13 fedora 543 k\n" +" pacemaker x86_64 1.1.5-1.fc13 fedora 543 k\n" "Installing for dependencies:\n" " OpenIPMI-libs x86_64 2.0.16-8.fc13 fedora 474 k\n" " PyXML x86_64 0.8.4-17.fc13 fedora 906 k\n" " cluster-glue x86_64 1.0.2-1.fc13 fedora 230 k\n" " cluster-glue-libs x86_64 1.0.2-1.fc13 fedora 116 k\n" " corosynclib x86_64 1.2.1-1.fc13 fedora 145 k\n" " heartbeat x86_64 3.0.0-0.7.0daab7da36a8.hg.fc13 updates 172 k\n" " heartbeat-libs x86_64 3.0.0-0.7.0daab7da36a8.hg.fc13 updates 265 k\n" " libesmtp x86_64 1.0.4-12.fc12 fedora 54 k\n" " libibverbs x86_64 1.1.3-4.fc13 fedora 42 k\n" " libmlx4 x86_64 1.0.1-5.fc13 fedora 27 k\n" " libnet x86_64 1.1.4-3.fc12 fedora 49 k\n" " librdmacm x86_64 1.0.10-2.fc13 fedora 22 k\n" " lm_sensors-libs x86_64 3.1.2-2.fc13 fedora 37 k\n" " net-snmp x86_64 1:5.5-12.fc13 fedora 295 k\n" " net-snmp-libs x86_64 1:5.5-12.fc13 fedora 1.5 M\n" " openhpi-libs x86_64 2.14.1-3.fc13 fedora 135 k\n" -" pacemaker-libs x86_64 1.1.1-1.fc13 fedora 264 k\n" +" pacemaker-libs x86_64 1.1.5-1.fc13 fedora 264 k\n" " perl-TimeDate noarch 1:1.20-1.fc13 fedora 42 k\n" " resource-agents x86_64 3.0.10-1.fc13 fedora 357 k\n" "\n" "Transaction Summary\n" "=========================================================================================\n" "Install 21 Package(s)\n" "Upgrade 0 Package(s)\n" "\n" "Total download size: 5.7 M\n" "Installed size: 20 M\n" "Downloading Packages:\n" "Setting up and reading Presto delta metadata\n" -"updates-testing/prestodelta | 164 kB 00:00 \n" -"fedora/prestodelta | 150 B 00:00 \n" +"updates-testing/prestodelta | 164 kB 00:00\n" +"fedora/prestodelta | 150 B 00:00\n" "Processing delta metadata\n" "Package(s) data still to download: 5.7 M\n" -"(1/21): OpenIPMI-libs-2.0.16-8.fc13.x86_64.rpm | 474 kB 00:00 \n" -"(2/21): PyXML-0.8.4-17.fc13.x86_64.rpm | 906 kB 00:01 \n" -"(3/21): cluster-glue-1.0.2-1.fc13.x86_64.rpm | 230 kB 00:00 \n" -"(4/21): cluster-glue-libs-1.0.2-1.fc13.x86_64.rpm | 116 kB 00:00 \n" -"(5/21): corosync-1.2.1-1.fc13.x86_64.rpm | 136 kB 00:00 \n" -"(6/21): corosynclib-1.2.1-1.fc13.x86_64.rpm | 145 kB 00:00 \n" -"(7/21): heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64.rpm | 172 kB 00:00 \n" -"(8/21): heartbeat-libs-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64.rpm | 265 kB 00:00 \n" -"(9/21): libesmtp-1.0.4-12.fc12.x86_64.rpm | 54 kB 00:00 \n" -"(10/21): libibverbs-1.1.3-4.fc13.x86_64.rpm | 42 kB 00:00 \n" -"(11/21): libmlx4-1.0.1-5.fc13.x86_64.rpm | 27 kB 00:00 \n" -"(12/21): libnet-1.1.4-3.fc12.x86_64.rpm | 49 kB 00:00 \n" -"(13/21): librdmacm-1.0.10-2.fc13.x86_64.rpm | 22 kB 00:00 \n" -"(14/21): lm_sensors-libs-3.1.2-2.fc13.x86_64.rpm | 37 kB 00:00 \n" -"(15/21): net-snmp-5.5-12.fc13.x86_64.rpm | 295 kB 00:00 \n" -"(16/21): net-snmp-libs-5.5-12.fc13.x86_64.rpm | 1.5 MB 00:01 \n" -"(17/21): openhpi-libs-2.14.1-3.fc13.x86_64.rpm | 135 kB 00:00 \n" -"(18/21): pacemaker-1.1.1-1.fc13.x86_64.rpm | 543 kB 00:00 \n" -"(19/21): pacemaker-libs-1.1.1-1.fc13.x86_64.rpm | 264 kB 00:00 \n" -"(20/21): perl-TimeDate-1.20-1.fc13.noarch.rpm | 42 kB 00:00 \n" -"(21/21): resource-agents-3.0.10-1.fc13.x86_64.rpm | 357 kB 00:00 \n" -"----------------------------------------------------------------------------------------\n" -"Total 539 kB/s | 5.7 MB 00:10 \n" +"(1/21): OpenIPMI-libs-2.0.16-8.fc13.x86_64.rpm | 474 kB 00:00\n" +"(2/21): PyXML-0.8.4-17.fc13.x86_64.rpm | 906 kB 00:01\n" +"(3/21): cluster-glue-1.0.2-1.fc13.x86_64.rpm | 230 kB 00:00\n" +"(4/21): cluster-glue-libs-1.0.2-1.fc13.x86_64.rpm | 116 kB 00:00\n" +"(5/21): corosync-1.2.1-1.fc13.x86_64.rpm | 136 kB 00:00\n" +"(6/21): corosynclib-1.2.1-1.fc13.x86_64.rpm | 145 kB 00:00\n" +"(7/21): heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64.rpm | 172 kB 00:00\n" +"(8/21): heartbeat-libs-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64.rpm | 265 kB 00:00\n" +"(9/21): libesmtp-1.0.4-12.fc12.x86_64.rpm | 54 kB 00:00\n" +"(10/21): libibverbs-1.1.3-4.fc13.x86_64.rpm | 42 kB 00:00\n" +"(11/21): libmlx4-1.0.1-5.fc13.x86_64.rpm | 27 kB 00:00\n" +"(12/21): libnet-1.1.4-3.fc12.x86_64.rpm | 49 kB 00:00\n" +"(13/21): librdmacm-1.0.10-2.fc13.x86_64.rpm | 22 kB 00:00\n" +"(14/21): lm_sensors-libs-3.1.2-2.fc13.x86_64.rpm | 37 kB 00:00\n" +"(15/21): net-snmp-5.5-12.fc13.x86_64.rpm | 295 kB 00:00\n" +"(16/21): net-snmp-libs-5.5-12.fc13.x86_64.rpm | 1.5 MB 00:01\n" +"(17/21): openhpi-libs-2.14.1-3.fc13.x86_64.rpm | 135 kB 00:00\n" +"(18/21): pacemaker-1.1.5-1.fc13.x86_64.rpm | 543 kB 00:00\n" +"(19/21): pacemaker-libs-1.1.5-1.fc13.x86_64.rpm | 264 kB 00:00\n" +"(20/21): perl-TimeDate-1.20-1.fc13.noarch.rpm | 42 kB 00:00\n" +"(21/21): resource-agents-3.0.10-1.fc13.x86_64.rpm | 357 kB 00:00\n" +"\n" +"Total 539 kB/s | 5.7 MB 00:10\n" "warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID e8e40fde: NOKEY\n" -"fedora/gpgkey | 3.2 kB 00:00 ... \n" +"fedora/gpgkey | 3.2 kB 00:00 ...\n" "Importing GPG key 0xE8E40FDE \"Fedora (13) <fedora@fedoraproject.org%gt;\" from /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64\n" -" " -msgstr "" - -#. Tag: screen -#, no-c-format -msgid "\n" +"\n" "Running rpm_check_debug\n" "Running Transaction Test\n" "Transaction Test Succeeded\n" "Running Transaction\n" -" Installing : lm_sensors-libs-3.1.2-2.fc13.x86_64 1/21 \n" -" Installing : 1:net-snmp-libs-5.5-12.fc13.x86_64 2/21 \n" -" Installing : 1:net-snmp-5.5-12.fc13.x86_64 3/21 \n" -" Installing : openhpi-libs-2.14.1-3.fc13.x86_64 4/21 \n" -" Installing : libibverbs-1.1.3-4.fc13.x86_64 5/21 \n" -" Installing : libmlx4-1.0.1-5.fc13.x86_64 6/21 \n" -" Installing : librdmacm-1.0.10-2.fc13.x86_64 7/21 \n" -" Installing : corosync-1.2.1-1.fc13.x86_64 8/21 \n" -" Installing : corosynclib-1.2.1-1.fc13.x86_64 9/21 \n" -" Installing : libesmtp-1.0.4-12.fc12.x86_64 10/21 \n" -" Installing : OpenIPMI-libs-2.0.16-8.fc13.x86_64 11/21 \n" -" Installing : PyXML-0.8.4-17.fc13.x86_64 12/21 \n" -" Installing : libnet-1.1.4-3.fc12.x86_64 13/21 \n" -" Installing : 1:perl-TimeDate-1.20-1.fc13.noarch 14/21 \n" -" Installing : cluster-glue-1.0.2-1.fc13.x86_64 15/21 \n" -" Installing : cluster-glue-libs-1.0.2-1.fc13.x86_64 16/21 \n" -" Installing : resource-agents-3.0.10-1.fc13.x86_64 17/21 \n" -" Installing : heartbeat-libs-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64 18/21 \n" -" Installing : heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64 19/21 \n" -" Installing : pacemaker-1.1.1-1.fc13.x86_64 20/21 \n" -" Installing : pacemaker-libs-1.1.1-1.fc13.x86_64 21/21 \n" +" Installing : lm_sensors-libs-3.1.2-2.fc13.x86_64 1/21\n" +" Installing : 1:net-snmp-libs-5.5-12.fc13.x86_64 2/21\n" +" Installing : 1:net-snmp-5.5-12.fc13.x86_64 3/21\n" +" Installing : openhpi-libs-2.14.1-3.fc13.x86_64 4/21\n" +" Installing : libibverbs-1.1.3-4.fc13.x86_64 5/21\n" +" Installing : libmlx4-1.0.1-5.fc13.x86_64 6/21\n" +" Installing : librdmacm-1.0.10-2.fc13.x86_64 7/21\n" +" Installing : corosync-1.2.1-1.fc13.x86_64 8/21\n" +" Installing : corosynclib-1.2.1-1.fc13.x86_64 9/21\n" +" Installing : libesmtp-1.0.4-12.fc12.x86_64 10/21\n" +" Installing : OpenIPMI-libs-2.0.16-8.fc13.x86_64 11/21\n" +" Installing : PyXML-0.8.4-17.fc13.x86_64 12/21\n" +" Installing : libnet-1.1.4-3.fc12.x86_64 13/21\n" +" Installing : 1:perl-TimeDate-1.20-1.fc13.noarch 14/21\n" +" Installing : cluster-glue-1.0.2-1.fc13.x86_64 15/21\n" +" Installing : cluster-glue-libs-1.0.2-1.fc13.x86_64 16/21\n" +" Installing : resource-agents-3.0.10-1.fc13.x86_64 17/21\n" +" Installing : heartbeat-libs-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64 18/21\n" +" Installing : heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64 19/21\n" +" Installing : pacemaker-1.1.5-1.fc13.x86_64 20/21\n" +" Installing : pacemaker-libs-1.1.5-1.fc13.x86_64 21/21\n" "\n" "Installed:\n" -" corosync.x86_64 0:1.2.1-1.fc13 pacemaker.x86_64 0:1.1.1-1.fc13 \n" +" corosync.x86_64 0:1.2.1-1.fc13 pacemaker.x86_64 0:1.1.5-1.fc13\n" "\n" "Dependency Installed:\n" -" OpenIPMI-libs.x86_64 0:2.0.16-8.fc13 \n" -" PyXML.x86_64 0:0.8.4-17.fc13 \n" -" cluster-glue.x86_64 0:1.0.2-1.fc13 \n" -" cluster-glue-libs.x86_64 0:1.0.2-1.fc13 \n" -" corosynclib.x86_64 0:1.2.1-1.fc13 \n" -" heartbeat.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13 \n" -" heartbeat-libs.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13 \n" -" libesmtp.x86_64 0:1.0.4-12.fc12 \n" -" libibverbs.x86_64 0:1.1.3-4.fc13 \n" -" libmlx4.x86_64 0:1.0.1-5.fc13 \n" -" libnet.x86_64 0:1.1.4-3.fc12 \n" -" librdmacm.x86_64 0:1.0.10-2.fc13 \n" -" lm_sensors-libs.x86_64 0:3.1.2-2.fc13 \n" -" net-snmp.x86_64 1:5.5-12.fc13 \n" -" net-snmp-libs.x86_64 1:5.5-12.fc13 \n" -" openhpi-libs.x86_64 0:2.14.1-3.fc13 \n" -" pacemaker-libs.x86_64 0:1.1.1-1.fc13 \n" -" perl-TimeDate.noarch 1:1.20-1.fc13 \n" -" resource-agents.x86_64 0:3.0.10-1.fc13 \n" +" OpenIPMI-libs.x86_64 0:2.0.16-8.fc13\n" +" PyXML.x86_64 0:0.8.4-17.fc13\n" +" cluster-glue.x86_64 0:1.0.2-1.fc13\n" +" cluster-glue-libs.x86_64 0:1.0.2-1.fc13\n" +" corosynclib.x86_64 0:1.2.1-1.fc13\n" +" heartbeat.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13\n" +" heartbeat-libs.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13\n" +" libesmtp.x86_64 0:1.0.4-12.fc12\n" +" libibverbs.x86_64 0:1.1.3-4.fc13\n" +" libmlx4.x86_64 0:1.0.1-5.fc13\n" +" libnet.x86_64 0:1.1.4-3.fc12\n" +" librdmacm.x86_64 0:1.0.10-2.fc13\n" +" lm_sensors-libs.x86_64 0:3.1.2-2.fc13\n" +" net-snmp.x86_64 1:5.5-12.fc13\n" +" net-snmp-libs.x86_64 1:5.5-12.fc13\n" +" openhpi-libs.x86_64 0:2.14.1-3.fc13\n" +" pacemaker-libs.x86_64 0:1.1.5-1.fc13\n" +" perl-TimeDate.noarch 1:1.20-1.fc13\n" +" resource-agents.x86_64 0:3.0.10-1.fc13\n" "\n" "Complete!\n" -"[root@pcmk-1 ~]# \n" -" " +"#" msgstr "" #. Tag: title #, no-c-format msgid "Before You Continue" msgstr "" #. Tag: para #, no-c-format msgid "Repeat the Installation steps so that you have 2 Fedora nodes with the cluster software installed." msgstr "" #. Tag: para #, no-c-format -msgid "For the purposes of this document, the additional node is called pcmk-2 with address 192.168.122.42." +msgid "For the purposes of this document, the additional node is called pcmk-2 with address 192.168.122.102." msgstr "" #. Tag: title #, no-c-format msgid "Setup" msgstr "" #. Tag: title #, no-c-format msgid "Finalize Networking" msgstr "" #. Tag: para #, no-c-format msgid "Confirm that you can communicate with the two new nodes:" msgstr "" -#. Tag: title -#, no-c-format -msgid "Verify Connectivity by IP address" -msgstr "" - #. Tag: programlisting #, no-c-format -msgid "\n" -" ping -c 3 192.168.122.102\n" -"[root@pcmk-1 ~]# ping -c 3 192.168.122.102\n" +msgid "# 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\n" -" " +"--- 192.168.122.102 ping statistics ---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 three machines. Otherwise, you’ll need to add the machines to /etc/hosts . Below are the entries for my cluster nodes:" +msgid "Figure 2.18. Verify Connectivity by IP address" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Set up /etc/hosts entries" +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:" msgstr "" #. Tag: programlisting #, no-c-format -msgid "\n" -" grep pcmk /etc/hosts\n" -"[root@pcmk-1 ~]# grep pcmk /etc/hosts\n" +msgid "# 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\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:" +msgid "Figure 2.19. Set up /etc/hosts entries" msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Verify Connectivity by Hostname" +msgid "We can now verify the setup by again using ping:" msgstr "" #. Tag: programlisting #, no-c-format -msgid "\n" -" ping -c 3 pcmk-2\n" -"[root@pcmk-1 ~]# ping -c 3 pcmk-2\n" +msgid "# 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\n" -" " +"--- pcmk-2.clusterlabs.org ping statistics ---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: para +#, no-c-format +msgid "Figure 2.20. Verify Connectivity by Hostname" 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 "Unprotected SSH keys, those without a password, are not recommended for servers exposed to the outside world." +msgid " SSH " msgstr "" #. Tag: para #, no-c-format -msgid "Create a new key and allow anyone with that key to log in:" +msgid "Unprotected SSH keys, those without a password, are not recommended for servers exposed to the outside world." msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Creating and Activating a new SSH Key" +msgid "Create a new key and allow anyone with that key to log in:" msgstr "" #. Tag: programlisting #, no-c-format -msgid "\n" -"[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" +msgid "# 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" -"[root@pcmk-1 ~]# cp .ssh/id_dsa.pub .ssh/authorized_keys\n" -"[root@pcmk-1 ~]#\n" -" " +"\n" +"# cp .ssh/id_dsa.pub .ssh/authorized_keys" 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" +msgid " Creating and Activating a new SSH Key " msgstr "" -#. Tag: title +#. Tag: para #, no-c-format -msgid "Installing the SSH Key on Another Host" +msgid "Install the key on the other nodes and test that you can now run commands remotely, without being prompted" msgstr "" #. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# scp -r .ssh pcmk-2:\n" +msgid "# 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" "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.\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" -"[root@pcmk-1 ~]# ssh pcmk-2 -- uname -n\n" -"pcmk-2\n" -"[root@pcmk-1 ~]#\n" -" " +"Warning: Permanently added 'pcmk-2,192.168.122.102' (RSA) to the list of known hosts.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 -npcmk-2\n" +"#" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Figure 2.22. Installing the SSH Key on Another Host" msgstr "" #. Tag: title #, no-c-format msgid "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:" +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 " msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# uname -n\n" -"pcmk-1.clusterlabs.org\n" -"[root@pcmk-1 ~]# dnsdomainname \n" -"clusterlabs.org\n" -" " +msgid "# uname -n\n" +"pcmk-1.clusterlabs.org\n" +"# dnsdomainname clusterlabs.org" +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: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# cat /etc/sysconfig/network\n" +msgid "# cat /etc/sysconfig/network\n" "NETWORKING=yes\n" -"HOSTNAME=pcmk-1.clusterlabs.org\n" -"GATEWAY=192.168.122.1\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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "[root@pcmk-1 ~]# sed -i.bak 's/\\.[a-z].*//g' /etc/sysconfig/network" +msgid " # sed -i.bak '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: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# cat /etc/sysconfig/network\n" +msgid "# cat /etc/sysconfig/network\n" "NETWORKING=yes\n" -"HOSTNAME=pcmk-1\n" -"GATEWAY=192.168.122.1\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: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# source /etc/sysconfig/network\n" -"[root@pcmk-1 ~]# hostname $HOSTNAME\n" -" " +msgid "# source /etc/sysconfig/network\n" +"# hostname $HOSTNAME" +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" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# uname -n\n" -"pcmk-1\n" -"[root@pcmk-1 ~]# dnsdomainname \n" -"clusterlabs.org\n" -" " +msgid "# uname -npcmk-1\n" +"# dnsdomainname clusterlabs.org" msgstr "" #. Tag: para #, no-c-format msgid "Now repeat on pcmk-2." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Corosync" msgstr "" #. Tag: para #, no-c-format -msgid "Choose a port number and multi-cast http://en.wikipedia.org/wiki/Multicast address. http://en.wikipedia.org/wiki/Multicast_address " +msgid "Choose a port number and multi-cast http://en.wikipedia.org/wiki/Multicast address. http://en.wikipedia.org/wiki/Multicast_address Be sure that the values you chose do not conflict with any existing clusters you might have. For advice on choosing a multi-cast address, see http://www.29west.com/docs/THPM/multicast-address-assignment.html For this document, I have chosen port 4000 and used 226.94.1.1 as the multi-cast address." msgstr "" #. Tag: para #, no-c-format -msgid "Be sure that the values you chose do not conflict with any existing clusters you might have. For advice on choosing a multi-cast address, see http://www.29west.com/docs/THPM/multicast-address-assignment.html " +msgid "The instructions below only apply for a machine with a single NIC. If you have a more complicated setup, you should edit the configuration manually." msgstr "" -#. Tag: para -#, no-c-format -msgid "For this document, I have chosen port 4000 and used 226.94.1.1 as the multi-cast address." -msgstr "" - -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# export ais_port=4000\n" -"[root@pcmk-1 ~]# export ais_mcast=226.94.1.1\n" -" " +msgid "# export ais_port=4000\n" +"# export ais_mcast=226.94.1.1" msgstr "" #. Tag: para #, no-c-format msgid "Next we automatically determine the hosts address. By not using the full address, we make the configuration suitable to be copied to other nodes." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "[root@pcmk-1 ~]# export ais_addr=`ip addr | grep \"inet \" | tail -n 1 | awk '{print $4}' | sed s/255/0/`" +msgid "# export ais_addr=`ip addr | grep \"inet \" | tail -n 1 | awk '{print $4}' | sed s/255/0/`" msgstr "" #. Tag: para #, no-c-format msgid "Display and verify the configuration options" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# env | grep ais_\n" -"ais_mcast=226.94.1.1\n" +msgid "# env | grep ais_ais_mcast=226.94.1.1\n" "ais_port=4000\n" -"ais_addr=192.168.122.0\n" -" " +"ais_addr=192.168.122.0" msgstr "" #. Tag: para #, no-c-format msgid "Once you’re happy with the chosen values, update the Corosync configuration" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf\n" -"[root@pcmk-1 ~]# sed -i.bak \"s/.*mcastaddr:.*/mcastaddr:\\ $ais_mcast/g\" /etc/corosync/corosync.conf\n" -"[root@pcmk-1 ~]# sed -i.bak \"s/.*mcastport:.*/mcastport:\\ $ais_port/g\" /etc/corosync/corosync.conf\n" -"[root@pcmk-1 ~]# sed -i.bak \"s/.*bindnetaddr:.*/bindnetaddr:\\ $ais_addr/g\" /etc/corosync/corosync.conf\n" -" " +msgid "# cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf\n" +"# sed -i.bak \"s/.*mcastaddr:.*/mcastaddr:\\ $ais_mcast/g\" /etc/corosync/corosync.conf\n" +"# sed -i.bak \"s/.*mcastport:.*/mcastport:\\ $ais_port/g\" /etc/corosync/corosync.conf\n" +"# sed -i.bak \"s/.*bindnetaddr:.*/bindnetaddr:\\ $ais_addr/g\" /etc/corosync/corosync.conf" msgstr "" #. Tag: para #, no-c-format -msgid "Finally, tell Corosync to start Pacemaker" +msgid "Finally, tell Corosync to load the Pacemaker plugin." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# cat <<-END >>/etc/corosync/service.d/pcmk\n" -"service {\n" +msgid "# cat <<-END >>/etc/corosync/service.d/pcmkservice {\n" " # Load the Pacemaker Cluster Resource Manager\n" " name: pacemaker\n" -" ver: 0\n" +" ver: 1\n" "}\n" -"END\n" -" " +"END" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The final configuration should look something like the sample in Appendix B, Sample Corosync Configuration." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "When run in version 1 mode, the plugin does not start the Pacemaker daemons. Instead it just sets up the quorum and messaging interfaces needed by the rest of the stack. Starting the dameons occurs when the Pacemaker init script is invoked. This resolves two long standing issues:" msgstr "" #. Tag: para #, no-c-format -msgid "The final configuration should look something like the sample in the appendix." +msgid "Forking inside a multi-threaded process like Corosync causes all sorts of pain. This has been problematic for Pacemaker as it needs a number of daemons to be spawned." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Corosync was never designed for staggered shutdown - something previously needed in order to prevent the cluster from leaving before Pacemaker could stop all active resources." msgstr "" #. Tag: title #, no-c-format msgid "Propagate the Configuration" msgstr "" #. Tag: para #, no-c-format msgid "Now we need to copy the changes so far to the other node:" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# for f in /etc/corosync/corosync.conf /etc/corosync/service.d/pcmk /etc/hosts; do scp $f pcmk-2:$f ; done\n" +msgid "# for f in /etc/corosync/corosync.conf /etc/corosync/service.d/pcmk /etc/hosts; do scp $f pcmk-2:$f ; done\n" "corosync.conf 100% 1528 1.5KB/s 00:00\n" "hosts 100% 281 0.3KB/s 00:00\n" -"[root@pcmk-1 ~]#\n" -" " +"#" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot b/doc/Clusters_from_Scratch/pot/Ch-Intro.pot index 6507b25169..e5e729c828 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Intro.pot @@ -1,269 +1,279 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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 best, it will focus exclusively on the XML syntax used to configure the CIB." +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 "For those that are allergic to XML, Pacemaker comes with a cluster shell and a Python based GUI exists, however these tools will not be covered at all in this document It is hoped however, that having understood the concepts explained here, that the functionality of these tools will also be more readily understood. , precisely because they hide the XML." +msgid "This document will walk through the installation and setup of simple clusters using the Fedora distribution, version 14." 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." +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?" 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. 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)." msgstr "" #. Tag: para #, no-c-format -msgid "Pacemaker's key features include:" +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 STONITH 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: para #, no-c-format msgid "Unified, scriptable, cluster shell" 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." -msgstr "" - -#. Tag: title -#, no-c-format -msgid "Active/Passive Redundancy" -msgstr "" - -#. Tag: caption -#, 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" -msgstr "" - -#. Tag: caption -#, 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" -msgstr "" - -#. Tag: caption -#, 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" 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 "Core cluster infrastructure providing messaging and membership functionality (illustrated in red)" +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." msgstr "" #. Tag: para #, no-c-format -msgid "Non-cluster aware components (illustrated in blue). 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 "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." msgstr "" #. Tag: para #, no-c-format -msgid "A brain (illustrated in green) that 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 them offline with remote power switches." +msgid "Low level infrastructure Corosync provides reliable messaging, membership and quorum information about the cluster (illustrated in red)." msgstr "" #. Tag: title #, no-c-format msgid "Conceptual Stack Overview" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format msgid "Conceptual overview of the cluster stack" 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. 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 "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." +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." msgstr "" #. Tag: title #, no-c-format msgid "The Pacemaker Stack" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format -msgid "The Pacemaker stack when running on Corosync" +msgid "The Pacemaker StackThe Pacemaker stack when running on Corosync" msgstr "" #. Tag: title #, no-c-format msgid "Internal Components" 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):" msgstr "" #. Tag: para #, no-c-format msgid "CIB (aka. Cluster Information Base)" msgstr "" #. Tag: para #, no-c-format msgid "CRMd (aka. Cluster Resource Management daemon)" msgstr "" #. Tag: para #, no-c-format msgid "PEngine (aka. PE or Policy Engine)" msgstr "" #. Tag: para #, no-c-format msgid "STONITHd" msgstr "" -#. Tag: caption +#. Tag: phrase #, no-c-format msgid "Subsystems of a Pacemaker cluster running on Corosync" 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 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: 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 "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." 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 "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)." 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." 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." 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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Active/Passive Redundancy" +msgstr "" + +#. Tag: phrase +#, 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 "N to N Redundancy" +msgstr "" + +#. Tag: phrase +#, 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 "" + diff --git a/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot b/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot index d59501adff..213b9be059 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Shared-Storage.pot @@ -1,655 +1,599 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" msgstr "" +#. Tag: title +#, no-c-format +msgid "Background" +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, its 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 "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, its 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." 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 ships with &DISTRO; &DISTRO_VERSION;. All you need to do is install it:" +msgid "Since its inclusion in the upstream 2.6.33 kernel, everything needed to use DRBD ships with Fedora 13. All you need to do is install it:" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# yum install -y drbd-pacemaker\n" +msgid "# yum install -y drbd-pacemaker drbd-udev\n" "Loaded plugins: presto, refresh-packagekit\n" "Setting up Install Process\n" "Resolving Dependencies\n" "--> Running transaction check\n" "---> Package drbd-pacemaker.x86_64 0:8.3.7-2.fc13 set to be updated\n" "--> Processing Dependency: drbd-utils = 8.3.7-2.fc13 for package: drbd-pacemaker-8.3.7-2.fc13.x86_64\n" "--> Running transaction check\n" "---> Package drbd-utils.x86_64 0:8.3.7-2.fc13 set to be updated\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.7-2.fc13 fedora 19 k\n" "Installing for dependencies:\n" " drbd-utils x86_64 8.3.7-2.fc13 fedora 165 k\n" "\n" "Transaction Summary\n" "=================================================================================\n" "Install 2 Package(s)\n" "Upgrade 0 Package(s)\n" "\n" "Total download size: 184 k\n" "Installed size: 427 k\n" "Downloading Packages:\n" "Setting up and reading Presto delta metadata\n" -"fedora/prestodelta | 1.7 kB 00:00 \n" +"fedora/prestodelta | 1.7 kB 00:00\n" "Processing delta metadata\n" "Package(s) data still to download: 184 k\n" -"(1/2): drbd-pacemaker-8.3.7-2.fc13.x86_64.rpm | 19 kB 00:01 \n" -"(2/2): drbd-utils-8.3.7-2.fc13.x86_64.rpm | 165 kB 00:02 \n" -"---------------------------------------------------------------------------------\n" -"Total 45 kB/s | 184 kB 00:04 \n" +"(1/2): drbd-pacemaker-8.3.7-2.fc13.x86_64.rpm | 19 kB 00:01\n" +"(2/2): drbd-utils-8.3.7-2.fc13.x86_64.rpm | 165 kB 00:02\n" +" ---------------------------------------------------------------------------------\n" +"Total 45 kB/s | 184 kB 00:04\n" "Running rpm_check_debug\n" "Running Transaction Test\n" "Transaction Test Succeeded\n" "Running Transaction\n" -" Installing : drbd-utils-8.3.7-2.fc13.x86_64 1/2 \n" -" Installing : drbd-pacemaker-8.3.7-2.fc13.x86_64 2/2 \n" +" Installing : drbd-utils-8.3.7-2.fc13.x86_64 1/2\n" +" Installing : drbd-pacemaker-8.3.7-2.fc13.x86_64 2/2\n" "\n" "Installed:\n" -" drbd-pacemaker.x86_64 0:8.3.7-2.fc13 \n" +" drbd-pacemaker.x86_64 0:8.3.7-2.fc13\n" "\n" "Dependency Installed:\n" -" drbd-utils.x86_64 0:8.3.7-2.fc13 \n" +" drbd-utils.x86_64 0:8.3.7-2.fc13\n" "\n" -"Complete!\n" -"[root@pcmk-1 ~]#\n" -" " +"Complete!" msgstr "" #. Tag: title #, no-c-format msgid "Configure DRBD" msgstr "" #. Tag: para #, no-c-format msgid "Before we configure DRBD, we need to set aside some disk for it to use." msgstr "" #. Tag: title #, no-c-format msgid "Create A Partition for DRBD" 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# lvcreate -n drbd-demo -L 1G VolGroup\n" -"  Logical volume \"drbd-demo\" created\n" -"[root@pcmk-1 ~]# lvs\n" -"  LV        VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert\n" -"  drbd-demo VolGroup -wi-a- 1.00G                                      \n" -"  lv_root   VolGroup -wi-ao   7.30G                                      \n" -"  lv_swap   VolGroup -wi-ao 500.00M\n" -" " +msgid "# lvcreate -n drbd-demo -L 1G VolGroup\n" +"Logical volume \"drbd-demo\" created\n" +"# lvs\n" +"LV VG Attr LSize Origin Snap% Move Log Copy% Convert\n" +"drbd-demo VolGroup -wi-a- 1.00G\n" +"lv_root VolGroup -wi-ao 7.30G\n" +"lv_swap VolGroup -wi-ao 500.00M" msgstr "" #. Tag: para #, no-c-format msgid "Repeat this on the second node, be sure to use the same size partition." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-2 ~]# lvs\n" -"  LV      VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert\n" -"  lv_root VolGroup -wi-ao   7.30G                                      \n" -"  lv_swap VolGroup -wi-ao 500.00M                                      \n" -"[root@pcmk-2 ~]# lvcreate -n drbd-demo -L 1G VolGroup\n" -"  Logical volume \"drbd-demo\" created\n" -"[root@pcmk-2 ~]# lvs\n" -"  LV        VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert\n" -"  drbd-demo VolGroup -wi-a- 1.00G                                      \n" -"  lv_root   VolGroup -wi-ao   7.30G                                      \n" -"  lv_swap   VolGroup -wi-ao 500.00M\n" -" " +msgid "# ssh pcmk-2 -- lvs\n" +"LV VG Attr LSize Origin Snap% Move Log Copy% Convert\n" +"lv_root VolGroup -wi-ao 7.30G\n" +"lv_swap VolGroup -wi-ao 500.00M\n" +"# ssh pcmk-2 -- lvcreate -n drbd-demo -L 1G VolGroup\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 VolGroup -wi-a- 1.00G\n" +"lv_root VolGroup -wi-ao 7.30G\n" +"lv_swap VolGroup -wi-ao 500.00M" msgstr "" #. Tag: title #, no-c-format msgid "Write the DRBD Config" msgstr "" #. Tag: para #, no-c-format msgid "There is no series of commands for build a DRBD configuration, so simply copy the configuration below to /etc/drbd.conf" 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" 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 "Be sure to use the names and addresses of your nodes if they differ from the ones used in this guide." msgstr "" -#. Tag: screen +#. Tag: literallayout #, no-c-format -msgid "\n" -"global { \n" -"  usage-count yes; \n" +msgid "global {\n" +" usage-count yes;\n" "}\n" "common {\n" -"  protocol C;\n" +" protocol C;\n" "}\n" "resource wwwdata {\n" -"  meta-disk internal;\n" -"  device    /dev/drbd1;\n" -"  syncer {\n" -"    verify-alg sha1;\n" -"  }\n" -"  net { \n" -"    allow-two-primaries; \n" -"  }\n" -"  on pcmk-1 {\n" -"    disk      /dev/mapper/VolGroup-drbd--demo;\n" -"    address   192.168.122.101:7789; \n" -"  }\n" -"  on \n" -"pcmk-2 {\n" -"    disk      /dev/mapper/VolGroup-drbd--demo;\n" -"    address   192.168.122.102:7789; \n" -"  }\n" -"}\n" -" " +" meta-disk internal;\n" +" device /dev/drbd1;\n" +" syncer {\n" +" verify-alg sha1;\n" +" }\n" +" net {\n" +" allow-two-primaries;\n" +" }\n" +" on pcmk-1 {\n" +" disk /dev/mapper/VolGroup-drbd--demo;\n" +" address 192.168.122.101:7789;\n" +" }\n" +" on pcmk-2 {\n" +" disk /dev/mapper/VolGroup-drbd--demo;\n" +" address 192.168.122.102:7789;\n" +" }\n" +"}" msgstr "" #. Tag: para #, no-c-format msgid "TODO: Explain the reason for the allow-two-primaries option" msgstr "" #. Tag: title #, no-c-format msgid "Initialize and Load DRBD" msgstr "" #. Tag: para #, no-c-format msgid "With the configuration in place, we can now perform the DRBD initialization" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# drbdadm create-md wwwdata\n" +msgid "# drbdadm create-md wwwdata\n" "md_offset 12578816\n" "al_offset 12546048\n" "bm_offset 12541952\n" "\n" -"Found some data \n" -" ==> This might destroy existing data! <==\n" +"Found some data\n" +"==> This might destroy existing data! <==\n" "\n" "Do you want to proceed?\n" -"[need to type 'yes' to confirm] yes\n" -"\n" +"[need to type 'yes' to confirm] yes\n" "Writing meta data...\n" "initializing activity log\n" "NOT initialized bitmap\n" "New drbd meta data block successfully created.\n" -"success\n" -" " +"success" msgstr "" #. Tag: para #, no-c-format msgid "Now load the DRBD kernel module and confirm that everything is sane" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# modprobe drbd\n" -"[root@pcmk-1 ~]# drbdadm up wwwdata\n" -"[root@pcmk-1 ~]# cat /proc/drbd\n" -"version: 8.3.6 (api:88/proto:86-90)\n" +msgid "# modprobe drbd# drbdadm up wwwdata# cat /proc/drbdversion: 8.3.6 (api:88/proto:86-90)\n" "GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57\n" -"\n" -" 1: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown 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:b oos:12248\n" -"[root@pcmk-1 ~]# \n" -"\n" -"Repeat on the second node\n" -"drbdadm --force create-md wwwdata \n" -"modprobe drbd\n" -"drbdadm up wwwdata\n" -"cat /proc/drbd\n" -"[root@pcmk-2 ~]# drbdadm --force create-md wwwdata\n" +" 1: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown 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:b oos:12248" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Repeat on the second node" +msgstr "" + +#. Tag: programlisting +#, 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" -"[root@pcmk-2 ~]# modprobe drbd\n" +"# ssh pcmk-2 -- modprobe drbd\n" "WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.\n" -"[root@pcmk-2 ~]# drbdadm up wwwdata\n" -"[root@pcmk-2 ~]# cat /proc/drbd\n" +"# ssh pcmk-2 -- drbdadm up wwwdata\n" +"# ssh pcmk-2 -- cat /proc/drbd\n" "version: 8.3.6 (api:88/proto:86-90)\n" "GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57\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:b oos:12248\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:b oos:12248" 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:" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# drbdadm -- --overwrite-data-of-peer primary wwwdata\n" -"[root@pcmk-1 ~]# cat /proc/drbd\n" +msgid "# drbdadm -- --overwrite-data-of-peer primary wwwdata\n" +"# cat /proc/drbd\n" "version: 8.3.6 (api:88/proto:86-90)\n" "GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57\n" -" 1: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r----\n" -"    ns:2184 nr:0 dw:0 dr:2472 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:10064\n" -"        [=====>..............] sync'ed: 33.4% (10064/12248)K\n" -"        finish: 0:00:37 speed: 240 (240) K/sec\n" -"[root@pcmk-1 ~]# cat /proc/drbd\n" +"1: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r----\n" +" ns:2184 nr:0 dw:0 dr:2472 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:10064\n" +" [=====>..............] sync'ed: 33.4% (10064/12248)K\n" +" finish: 0:00:37 speed: 240 (240) K/sec\n" +"# cat /proc/drbd\n" "version: 8.3.6 (api:88/proto:86-90)\n" "GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57\n" -" 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----\n" -"    ns:12248 nr:0 dw:0 dr:12536 al:0 bm:1 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0\n" -" " +"1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----\n" +" ns:12248 nr:0 dw:0 dr:12536 al:0 bm:1 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b 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 its a good point at which to create a filesystem and populate it with some data to serve up via our WebSite resource." msgstr "" #. Tag: title #, no-c-format msgid "Populate DRBD with Data" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# mkfs.ext4 /dev/drbd1\n" +msgid "# mkfs.ext4 /dev/drbd1\n" "mke2fs 1.41.4 (27-Jan-2009)\n" "Filesystem label=\n" "OS type: Linux\n" "Block size=1024 (log=0)\n" "Fragment size=1024 (log=0)\n" "3072 inodes, 12248 blocks\n" "612 blocks (5.00%) reserved for the super user\n" "First data block=1\n" "Maximum filesystem blocks=12582912\n" "2 block groups\n" "8192 blocks per group, 8192 fragments per group\n" "1536 inodes per group\n" -"Superblock backups stored on blocks: \n" -"        8193\n" +"Superblock backups stored on blocks:\n" +" 8193\n" "\n" -"Writing inode tables: done                            \n" +"Writing inode tables: done\n" "Creating journal (1024 blocks): done\n" "Writing superblocks and filesystem accounting information: done\n" "\n" "This filesystem will be automatically checked every 26 mounts or\n" -"180 days, whichever comes first.  Use tune2fs -c or -i to override.\n" -"\n" -"Now mount the newly created filesystem so we can create our index file\n" -"mount /dev/drbd1 /mnt/\n" -"cat <<-END >/mnt/index.html\n" -"<html>\n" -"<body>My Test Site - drbd</body>\n" -"</html>\n" -"END\n" -"umount /dev/drbd1\n" -"[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" -"> </html>\n" -"> END\n" -"[root@pcmk-1 ~]# umount /dev/drbd1\n" -" " +"180 days, whichever comes first. Use tune2fs -c or -i to override." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Now mount the newly created filesystem so we can create our index file" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# mount /dev/drbd1 /mnt/\n" +"# cat <<-END >/mnt/index.html\n" +" <html>\n" +" <body>My Test Site - drbd</body>\n" +" </html>\n" +" END\n" +"# umount /dev/drbd1" msgstr "" #. Tag: title #, no-c-format msgid "Configure the Cluster for DRBD" msgstr "" #. Tag: para #, no-c-format msgid "One handy feature of the crm shell is that you can use it in interactive mode to make several changes atomically." msgstr "" #. Tag: para #, no-c-format msgid "First we launch the shell. The prompt will change to indicate you’re in interactive mode." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm\n" -"cib crm(live)#\n" -" " +msgid "# crm cib\n" +"crm(live) #" msgstr "" #. Tag: para #, no-c-format msgid "Next we must create a working copy or the current configuration. This is where all our changes will go. The cluster will not see any of them until we say its ok. Notice again how the prompt changes, this time to indicate that we’re no longer looking at the live cluster." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"cib crm(live)# cib new drbd\n" +msgid "cib crm(live) # cib new drbd\n" "INFO: drbd shadow CIB created\n" -"crm(drbd)#\n" -" " +"crm(drbd) #" msgstr "" #. Tag: para #, no-c-format msgid "Now we can create our DRBD clone and display the revised configuration." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(drbd)# configure primitive WebData ocf:linbit:drbd params drbd_resource=wwwdata \\\n" -"        op monitor interval=60s\n" -"crm(drbd)# configure ms WebDataClone WebData meta master-max=1 master-node-max=1 \\\n" -"        clone-max=2 clone-node-max=1 notify=true\n" -"crm(drbd)# configure show\n" -"node pcmk-1\n" -"node pcmk-2\n" -"primitive WebData ocf:linbit:drbd \\\n" -" params drbd_resource=\"wwwdata\" \\\n" -" op monitor interval=\"60s\"\n" -"primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\n" +msgid "crm(drbd) # configure primitive WebData ocf:linbit:drbd params drbd_resource=wwwdata \\\n" +" op monitor interval=60s\n" +"crm(drbd) # configure ms WebDataClone WebData meta master-max=1 master-node-max=1 \\\n" +" clone-max=2 clone-node-max=1 notify=truecrm(drbd) # configure shownode pcmk-1\n" +"node pcmk-2primitive WebData ocf:linbit:drbd \\\n" +" params drbd_resource=\"wwwdata\" \\\n" +" op monitor interval=\"60s\"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\" \\\n" -"        op monitor interval=\"30s\"\n" -"ms WebDataClone WebData \\\n" -" meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"ms WebDataClone WebData \\\n" +" meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" "location prefer-pcmk-1 WebSite 50: pcmk-1\n" "colocation website-with-ip inf: WebSite ClusterIP\n" "order apache-after-ip inf: ClusterIP WebSite\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -" " +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "Once we’re happy with the changes, we can tell the cluster to start using them and use crm_mon to check everything is functioning." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(drbd)# cib commit drbd\n" -"INFO: commited 'drbd' shadow CIB to the cluster\n" -"crm(drbd)# quit\n" -"bye\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "crm(drbd) # cib commit drbdINFO: commited 'drbd' shadow CIB to the cluster\n" +"crm(drbd) # quitbye\n" +"# crm_mon\n" "============\n" -"Last updated: Tue Sep  1 09:37:13 2009\n" +"Last updated: Tue Sep 1 09:37:13 2009\n" "Stack: openais\n" "Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "3 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-1\n" -"WebSite (ocf::heartbeat:apache):        Started pcmk-1\n" -"Master/Slave Set: WebDataClone\n" -" Masters: [ pcmk-2 ]\n" -" Slaves: [ pcmk-1 ]\n" -" " +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-1Master/Slave Set: WebDataClone Masters: [ pcmk-2 ] Slaves: [ pcmk-1 ]" msgstr "" #. Tag: para #, no-c-format msgid "Include details on adding a second DRBD resource" 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)." msgstr "" #. Tag: para #, no-c-format msgid "Once again we’ll use the shell’s interactive mode" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm\n" -"crm(live)# cib new fs\n" +msgid "# crm\n" +"crm(live) # cib new fs\n" "INFO: fs shadow CIB created\n" -"crm(fs)# configure primitive WebFS ocf:heartbeat:Filesystem \\\n" -"        params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=\"ext4\"\n" -"crm(fs)# configure colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" -"crm(fs)# configure order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" -" " -msgstr "" - -#. Tag: para -#, no-c-format -msgid "We also need to tell the cluster that Apache needs to run on the same machine as the filesystem and that it must be active before Apache can start." -msgstr "" - -#. Tag: screen -#, no-c-format -msgid "\n" -"crm(fs)# configure colocation WebSite-with-WebFS inf: WebSite WebFS\n" -"crm(fs)# configure order WebSite-after-WebFS inf: WebFS WebSite\n" -" " +"crm(fs) # configure primitive WebFS ocf:heartbeat:Filesystem \\\n" +" params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=\"ext4\"\n" +"crm(fs) # configure colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" +"crm(fs) # configure order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" +"\n" +"We also need to tell the cluster that Apache needs to run on the same\n" +"machine as the filesystem and that it must be active before Apache can\n" +"start.\n" +"\n" +"crm(fs) # configure colocation WebSite-with-WebFS inf: WebSite WebFS\n" +"crm(fs) # configure order WebSite-after-WebFS inf: WebFS WebSite" msgstr "" #. Tag: para #, no-c-format msgid "Time to review the updated configuration:" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm configure show\n" +msgid "crm(fs) # crm configure show\n" "node pcmk-1\n" "node pcmk-2\n" "primitive WebData ocf:linbit:drbd \\\n" -"        params drbd_resource=\"wwwdata\" \\\n" -"        op monitor interval=\"60s\"\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=\"ext4\"\n" +" params device=\"/dev/drbd/by-res/wwwdata\" directory=\"/var/www/html\" fstype=\"ext4\"\n" "primitive WebSite ocf:heartbeat:apache \\\n" -"        params configfile=\"/etc/httpd/conf/httpd.conf\" \\\n" -"        op monitor interval=\"1min\"\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\" \\\n" -"        op monitor interval=\"30s\"\n" +" params ip=\"192.168.122.101\" cidr_netmask=\"32\" \\\n" +" op monitor interval=\"30s\"\n" "ms WebDataClone WebData \\\n" -"        meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" +" meta master-max=\"1\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" "location prefer-pcmk-1 WebSite 50: pcmk-1\n" "colocation WebSite-with-WebFS inf: WebSite WebFS\n" "colocation fs_on_drbd inf: WebFS WebDataClone:Master\n" "colocation website-with-ip inf: WebSite ClusterIP\n" "order WebFS-after-WebData inf: WebDataClone:promote WebFS:start\n" "order WebSite-after-WebFS inf: WebFS WebSite\n" "order apache-after-ip inf: ClusterIP WebSite\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"false\" \\\n" -"        no-quorum-policy=\"ignore\"\n" +" dc-version=\"1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\" \\\n" +" cluster-infrastructure=\"openais\" \\\n" +" expected-quorum-votes=\"2\" \\\n" +" stonith-enabled=\"false\" \\\n" +" no-quorum-policy=\"ignore\"\n" "rsc_defaults $id=\"rsc-options\" \\\n" -"        resource-stickiness=”100”\n" -" " +" resource-stickiness=\"100\"" msgstr "" #. Tag: para #, no-c-format msgid "After reviewing the new configuration, we again upload it and watch the cluster put it into effect." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(fs)# cib commit fs\n" +msgid "crm(fs) # cib commit fs\n" "INFO: commited 'fs' shadow CIB to the cluster\n" -"crm(fs)# quit\n" +"crm(fs) # quit\n" "bye\n" -"[root@pcmk-1 ~]# crm_mon\n" +"# crm_mon\n" "============\n" -"Last updated: Tue Sep  1 10:08:44 2009\n" +"Last updated: Tue Sep 1 10:08:44 2009\n" "Stack: openais\n" "Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "4 Resources configured.\n" "============\n" "\n" "Online: [ pcmk-1 pcmk-2 ]\n" "\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-1\n" -"WebSite (ocf::heartbeat:apache): Started pcmk-1\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-1\n" "Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-1 ]\n" -"        Slaves: [ pcmk-2 ]\n" -"WebFS (ocf::heartbeat:Filesystem): Started pcmk-1\n" -" " +" Masters: [ pcmk-1 ]\n" +" Slaves: [ pcmk-2 ]\n" +"WebFS (ocf::heartbeat:Filesystem): Started pcmk-1" msgstr "" #. Tag: title #, no-c-format msgid "Testing Migration" 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 "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." 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm node standby\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# crm node standby\n" +"# crm_mon\n" "============\n" -"Last updated: Tue Sep  1 10:09:57 2009\n" +"Last updated: Tue Sep 1 10:09:57 2009\n" "Stack: openais\n" "Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "4 Resources configured.\n" "============\n" +"Node pcmk-1: standbyOnline: [ pcmk-2 ]\n" "\n" -"Node pcmk-1: standby\n" -"Online: [ pcmk-2 ]\n" -"\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"WebSite (ocf::heartbeat:apache):        Started pcmk-2\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-2\n" "Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-2 ]\n" -"        Stopped: [ WebData:1 ]\n" -"WebFS   (ocf::heartbeat:Filesystem):    Started pcmk-2\n" -" " +" Masters: [ pcmk-2 ] Stopped: [ WebData:1 ]\n" +"WebFS (ocf::heartbeat:Filesystem): Started pcmk-2" msgstr "" #. Tag: para #, no-c-format msgid "Once we’ve done everything we needed to on pcmk-1 (in this case nothing, we just wanted to see the resources move), we can allow the node to be a full cluster member again." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm node online\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# crm node online\n" +"# crm_mon\n" "============\n" -"Last updated: Tue Sep  1 10:13:25 2009\n" +"Last updated: Tue Sep 1 10:13:25 2009\n" "Stack: openais\n" "Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" "2 Nodes configured, 2 expected votes\n" "4 Resources configured.\n" "============\n" -"\n" -"Online: [ pcmk-1 pcmk-2 ]\n" -"\n" -"ClusterIP        (ocf::heartbeat:IPaddr):        Started pcmk-2\n" -"WebSite (ocf::heartbeat:apache):        Started pcmk-2\n" +"Online: [ pcmk-1 pcmk-2 ]\n" +"ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2\n" +"WebSite (ocf::heartbeat:apache): Started pcmk-2\n" "Master/Slave Set: WebDataClone\n" -"        Masters: [ pcmk-2 ]\n" -"        Slaves: [ pcmk-1 ]\n" -"WebFS   (ocf::heartbeat:Filesystem):    Started pcmk-2\n" -" " +" Masters: [ pcmk-2 ]\n" +" Slaves: [ pcmk-1 ]\n" +"WebFS (ocf::heartbeat:Filesystem): Started pcmk-2" msgstr "" #. Tag: para #, no-c-format msgid "Notice that our resource stickiness settings prevent the services from migrating back to pcmk-1." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot b/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot index 39c4d514c6..8ca4ab2edb 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Stonith.pot @@ -1,205 +1,272 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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 "Why You Need 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 rouge nodes or concurrent access." +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." msgstr "" #. Tag: para #, no-c-format msgid "Just because a node is unresponsive, this doesn’t mean it isn’t accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node." msgstr "" #. Tag: para #, no-c-format msgid "STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere." msgstr "" #. Tag: title #, no-c-format msgid "What STONITH Device Should You Use" msgstr "" #. Tag: para #, no-c-format msgid "It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one." msgstr "" #. Tag: para #, no-c-format -msgid "The biggest mistake people make in choosing a STONITH device is to use remote power switch (such as many onboard 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 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." 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\" used during testing) are inappropriate." msgstr "" #. Tag: title #, no-c-format msgid "Configuring STONITH" msgstr "" #. Tag: para #, no-c-format -msgid "Find the correct driver: stonith -L" +msgid "Find the correct driver: stonith_admin --list-installed" 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 required by the device: stonith -t {type} -n" +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" +msgstr "" + +#. Tag: literallayout +#, 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." msgstr "" #. Tag: para #, no-c-format -msgid "Hopefully the developers chose names that make sense, if not you can query for some additional information by finding an active cluster node and running:" +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 …" msgstr "" -#. Tag: screen +#. Tag: para #, no-c-format -msgid "lrmadmin -M stonith {type} pacemaker\n" -"" +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 "The output should be XML formatted text containing additional parameter descriptions" +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 "Create a file called stonith.xml 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" +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 "Create a clone from the primitive resource if the device can shoot more than one node and supports multiple simultaneous connections." +msgid "Upload it into the CIB from the shell: cib commit stonith" msgstr "" #. Tag: para #, no-c-format -msgid "Upload it into the CIB using cibadmin: cibadmin -C -o resources --xml-file stonith.xml" +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." msgstr "" #. Tag: title #, no-c-format msgid "Example" msgstr "" #. Tag: para #, no-c-format -msgid "Assuming we have an IBM BladeCenter containing our two nodes and the management interface is active on 192.168.122.31, then we would chose the external/ibmrsa driver in step 2 and obtain the following list of parameters" +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" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# stonith_admin --metadata -a fence_ipmilan" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"stonith -t external/ibmrsa -n\n" -"[root@pcmk-1 ~]# stonith -t external/ibmrsa -n\n" -"hostname  ipaddr  userid  passwd  type\n" -"" +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>" msgstr "" #. Tag: para #, no-c-format -msgid "Assuming we know the username and password for the management interface, we would create a STONITH resource with the shell" +msgid "from which we would create a STONITH resource fragment that might look like this" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm \n" -"crm(live)# cib new stonith\n" +msgid "# crm crm(live)# cib new stonith\n" "INFO: stonith shadow CIB created\n" -"crm(stonith)# configure primitive rsa-fencing stonith::external/ibmrsa \\\n" -"        params hostname=”pcmk-1 pcmk-2\" ipaddr=192.168.122.31 userid=mgmt passwd=abc123 type=ibm \\\n" -"        op monitor interval=\"60s\"\n" -"crm(stonith)# configure clone Fencing rsa-fencing\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\"" msgstr "" #. Tag: para #, no-c-format -msgid "And finally, since we disabled it earlier, we need to re-enable STONITH" +msgid "And finally, since we disabled it earlier, we need to re-enable STONITH. At this point we should have the following configuration.." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"crm(stonith)# configure property stonith-enabled=\"true\"\n" -"crm(stonith)# configure show\n" -"node pcmk-1\n" +msgid "crm(stonith)# configure property stonith-enabled=\"true\"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" +" 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" +" 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" +" 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\"\n" -"primitive dlm ocf:pacemaker:controld \\\n" -"        op monitor interval=\"120s\"\n" -"primitive gfs-control ocf:pacemaker:controld \\\n" -"   params daemon=”gfs_controld.pcmk” args=”-g 0” \\\n" -"        op monitor interval=\"120s\"\n" -"primitive rsa-fencing stonith::external/ibmrsa \\\n" -" params hostname=”pcmk-1 pcmk-2\" ipaddr=192.168.122.31 userid=mgmt passwd=abc123 type=ibm \\\n" -" op monitor interval=\"60s\"\n" -"ms WebDataClone WebData \\\n" -"        meta master-max=\"2\" master-node-max=\"1\" clone-max=\"2\" clone-node-max=\"1\" notify=\"true\"\n" -"clone Fencing rsa-fencing \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 WebIP ClusterIP \\\n" +" meta globally-unique=\"true\" clone-max=\"2\" clone-node-max=\"2\"\n" "clone WebSiteClone WebSite\n" -"clone dlm-clone dlm \\\n" -"        meta interleave=\"true\"\n" -"clone gfs-clone gfs-control \\\n" -"        meta interleave=\"true\"\n" -"colocation WebFS-with-gfs-control inf: WebFSClone gfs-clone\n" "colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone\n" "colocation fs_on_drbd inf: WebFSClone WebDataClone:Master\n" -"colocation gfs-with-dlm inf: gfs-clone dlm-clone\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" -"order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone\n" -"order start-gfs-after-dlm inf: dlm-clone gfs-clone\n" "property $id=\"cib-bootstrap-options\" \\\n" -"        dc-version=\"1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\" \\\n" -"        cluster-infrastructure=\"openais\" \\\n" -"        expected-quorum-votes=”2” \\\n" -"        stonith-enabled=\"true\" \\\n" -"        no-quorum-policy=\"ignore\"\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" -"" +" resource-stickiness=\"100\"\n" +"crm(stonith)# cib commit stonithINFO: commited 'stonith' shadow CIB to the cluster\n" +"crm(stonith)# quit\n" +"bye" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Tools.pot b/doc/Clusters_from_Scratch/pot/Ch-Tools.pot index 0d4784a236..d53ac5873a 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Tools.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Tools.pot @@ -1,148 +1,197 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" 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 "Since Pacemaker 1.0, this has all changed and we have an integrated, scriptable, cluster shell that hides all the messy XML scaffolding. It even allows you to queue up several changes at once and commit them atomically." msgstr "" #. Tag: para #, no-c-format msgid "Take some time to familiarize yourself with what it can do." msgstr "" +#. Tag: para +#, no-c-format +msgid "# crm --help" +msgstr "" + #. Tag: screen #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm --help\n" +msgid "usage:\n" +" crm [-D display_type] [-f file] [-hF] [args]\n" "\n" -"usage:\n" -"    crm [-D display_type]\n" -"    crm [-D display_type] args\n" -"    crm [-D display_type] [-f file]\n" +" Use crm without arguments for an interactive session.\n" +" Supply one or more arguments for a \"single-shot\" use.\n" +" Specify with -f a file which contains a script. Use '-' for\n" +" standard input or use pipe/redirection.\n" "\n" -"    Use crm without arguments for an interactive session.\n" -"    Supply one or more arguments for a \"single-shot\" use.\n" -"    Specify with -f a file which contains a script. Use '-' for\n" -"    standard input or use pipe/redirection.\n" +" crm displays cli format configurations using a color scheme\n" +" and/or in uppercase. Pick one of \"color\" or \"uppercase\", or\n" +" use \"-D color,uppercase\" if you want colorful uppercase.\n" +" Get plain output by \"-D plain\". The default may be set in\n" +" user preferences (options).\n" "\n" -"    crm displays cli format configurations using a color scheme\n" -"    and/or in uppercase. Pick one of \"color\" or \"uppercase\", or\n" -"    use \"-D color,uppercase\" if you want colorful uppercase.\n" -"    Get plain output by \"-D plain\". The default may be set in\n" -"    user preferences (options).\n" +" -F stands for force, if set all operations will behave as if\n" +" force was specified on the line (e.g. configure commit).\n" "\n" "Examples:\n" "\n" -"    # crm -f stopapp2.cli\n" -"    # crm < stopapp2.cli\n" -"    # crm resource stop global_www\n" -"    # crm status\n" -"" +" # crm -f stopapp2.cli\n" +" # crm < stopapp2.cli\n" +" # crm resource stop global_www\n" +" # crm status" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The primary tool for monitoring the status of the cluster is crm_mon (also available as crm status). It can be run in a variety of modes and has a number of output options. To find out about any of the tools that come with Pacemaker, simply invoke them with the --help option or consult the included man pages. Both sets of output are created from the tool, and so will always be in sync with each other and the tool itself." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Additionally, the Pacemaker version and supported cluster stack(s) is available via the --feature option to pacemakerd." msgstr "" #. Tag: para #, no-c-format -msgid "The primary tool for monitoring the status of the cluster is crm_mon (also available as crm status). It can be run in a variety of modes and has a number of output options. To find out about any of the tools that come with Pacemaker, simply invoke them with the --help option or consult the included man pages. Both sets of output are created from the tool, and so will always be in sync with each other and the tool itself." +msgid "# pacemakerd --features" +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "Pacemaker 1.1.6 (Build: 7249214)\n" +" Supporting: generated-manpages agent-manpages ascii-docs publican-docs ncurses trace-logging libqb heartbeat corosync-native libesmtp" msgstr "" #. Tag: para #, no-c-format -msgid "Additionally, the Pacemaker version and supported cluster stack(s) is available via the --version option." +msgid "# pacemakerd --help" msgstr "" #. Tag: screen #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# crm_mon --version\n" -"crm_mon 1.0.5 for OpenAIS and Heartbeat (Build: 462f1569a43740667daf7b0f6b521742e9eb8fa7)\n" +msgid "pacemakerd - Start/Stop Pacemaker\n" "\n" -"Written by Andrew Beekhof\n" -"[root@pcmk-1 ~]# crm_mon --help\n" -"crm_mon - Provides a summary of cluster's current state.\n" +"Usage: pacemakerd mode [options]\n" +"Options:\n" +" -?, --help This text\n" +" -$, --version Version information\n" +" -V, --verbose Increase debug output\n" +" -S, --shutdown Instruct Pacemaker to shutdown on this machine\n" +" -F, --features Display the full version and list of features Pacemaker was built with\n" +"\n" +"Additional Options:\n" +" -f, --foreground Run in the foreground instead of as a daemon\n" +" -p, --pid-file=value (Advanced) Daemon pid file location\n" +"\n" +"Report bugs to pacemaker@oss.clusterlabs.org" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "# crm_mon --help" +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "crm_mon - Provides a summary of cluster's current state.\n" "\n" "Outputs varying levels of detail in a number of different formats.\n" "\n" "Usage: crm_mon mode [options]\n" "Options:\n" -" -?, --help                 This text\n" -" -$, --version             Version information\n" -" -V, --verbose             Increase debug output\n" +" -?, --help This text\n" +" -$, --version Version information\n" +" -V, --verbose Increase debug output\n" +" -Q, --quiet Display only essential output\n" "\n" "Modes:\n" -" -h, --as-html=value        Write cluster status to the named file\n" -" -w, --web-cgi             Web mode with output suitable for cgi\n" -" -s, --simple-status       Display the cluster status once as a simple one line output (suitable for nagios)\n" -" -S, --snmp-traps=value    Send SNMP traps to this station\n" -" -T, --mail-to=value        Send Mail alerts to this user.  See also --mail-from, --mail-host, --mail-prefix\n" +" -h, --as-html=value Write cluster status to the named html file\n" +" -X, --as-xml=value Write cluster status to the named xml file\n" +" -w, --web-cgi Web mode with output suitable for cgi\n" +" -s, --simple-status Display the cluster status once as a simple one line output (suitable for nagios)\n" +" -T, --mail-to=value Send Mail alerts to this user. See also --mail-from, --mail-host, --mail-prefix\n" "\n" "Display Options:\n" -" -n, --group-by-node       Group resources by node\n" -" -r, --inactive             Display inactive resources\n" -" -f, --failcounts           Display resource fail counts\n" -" -o, --operations           Display resource operation history\n" -" -t, --timing-details       Display resource operation history with timing details\n" +" -n, --group-by-node Group resources by node\n" +" -r, --inactive Display inactive resources\n" +" -f, --failcounts Display resource fail counts\n" +" -o, --operations Display resource operation history\n" +" -t, --timing-details Display resource operation history with timing details\n" +" -A, --show-node-attributes Display node attributes\n" "\n" "\n" "Additional Options:\n" -" -i, --interval=value           Update frequency in seconds\n" -" -1, --one-shot                 Display the cluster status once on the console and exit\n" -" -N, --disable-ncurses          Disable the use of ncurses\n" -" -d, --daemonize                Run in the background as a daemon\n" -" -p, --pid-file=value           (Advanced) Daemon pid file location\n" -" -F, --mail-from=value          Mail alerts should come from the named user\n" -" -H, --mail-host=value          Mail alerts should be sent via the named host\n" -" -P, --mail-prefix=value        Subjects for mail alerts should start with this string\n" -" -E, --external-agent=value     A program to run when resource operations take place.\n" -" -e, --external-recipient=value A recipient for your program (assuming you want the program to send something to someone).\n" +" -i, --interval=value Update frequency in seconds\n" +" -1, --one-shot Display the cluster status once on the console and exit\n" +" -N, --disable-ncurses Disable the use of ncurses\n" +" -d, --daemonize Run in the background as a daemon\n" +" -p, --pid-file=value (Advanced) Daemon pid file location\n" +" -F, --mail-from=value Mail alerts should come from the named user\n" +" -H, --mail-host=value Mail alerts should be sent via the named host\n" +" -P, --mail-prefix=value Subjects for mail alerts should start with this string\n" +" -E, --external-agent=value A program to run when resource operations take place.\n" +" -e, --external-recipient=value A recipient for your program (assuming you want the program to send something to someone).\n" "\n" "Examples:\n" "\n" -"Display the cluster´s status on the console with updates as they occur:\n" -"        # crm_mon\n" +"Display the cluster status on the console with updates as they occur:\n" +"\n" +" # crm_mon\n" +"\n" +"Display the cluster status on the console just once then exit:\n" +"\n" +" # crm_mon -1\n" "\n" -"Display the cluster´s status on the console just once then exit:\n" -"        # crm_mon\n" +"Display your cluster status, group resources by node, and include inactive resources in the list:\n" "\n" -"Display your cluster´s status, group resources by node, and include inactive resources in the list:\n" -"        # crm_mon --group-by-node --inactive\n" +" # crm_mon --group-by-node --inactive\n" "\n" -"Start crm_mon as a background daemon and have it write the cluster´s status to an HTML file:\n" -"        # crm_mon --daemonize --as-html /path/to/docroot/filename.html\n" +"Start crm_mon as a background daemon and have it write the cluster status to an HTML file:\n" +"\n" +" # crm_mon --daemonize --as-html /path/to/docroot/filename.html\n" +"\n" +"Start crm_mon and export the current cluster status to an xml file, then exit.:\n" +"\n" +" # crm_mon --one-shot --as-xml /path/to/docroot/filename.xml\n" "\n" "Start crm_mon as a background daemon and have it send email alerts:\n" -"        # crm_mon --daemonize --mail-to user@example.com --mail-host mail.example.com\n" "\n" -"Start crm_mon as a background daemon and have it send SNMP alerts:\n" -"        # crm_mon --daemonize --snmp-traps snmptrapd.example.com\n" +" # crm_mon --daemonize --mail-to user@example.com --mail-host mail.example.com\n" +"\n" "\n" -"Report bugs to pacemaker@oss.clusterlabs.org\n" -"" +"Report bugs to pacemaker@oss.clusterlabs.org" 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." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Ch-Verification.pot b/doc/Clusters_from_Scratch/pot/Ch-Verification.pot index 1620d2a4db..0aa11ff14c 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Verification.pot +++ b/doc/Clusters_from_Scratch/pot/Ch-Verification.pot @@ -1,155 +1,169 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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" msgstr "" #. Tag: title #, no-c-format msgid "Verify Corosync Installation" msgstr "" #. Tag: para #, no-c-format msgid "Start Corosync on the first node" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# /etc/init.d/corosync start\n" -"Starting Corosync Cluster Engine (corosync): [ OK ]\n" -"" +msgid "# /etc/init.d/corosync start\n" +"Starting Corosync Cluster Engine (corosync): [ OK ]" msgstr "" #. Tag: para #, no-c-format msgid "Check the cluster started correctly and that an initial membership was able to form" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# grep -e \"corosync.*network interface\" -e \"Corosync Cluster Engine\" -e \"Successfully read main configuration file\" /var/log/messages\n" -"Aug 27 09:05:34 pcmk-1 corosync[1540]: [MAIN  ] Corosync Cluster Engine ('1.1.0'): started and ready to provide service.\n" -"Aug 27 09:05:34 pcmk-1 corosync[1540]: [MAIN  ] Successfully read main configuration file '/etc/corosync/corosync.conf'.\n" -"[root@pcmk-1 ~]# grep TOTEM /var/log/messages\n" +msgid "# grep -e \"corosync.*network interface\" -e \"Corosync Cluster Engine\" -e \"Successfully read main configuration file\" /var/log/messages\n" +"Aug 27 09:05:34 pcmk-1 corosync[1540]: [MAIN ] Corosync Cluster Engine ('1.1.0'): started and ready to provide service.\n" +"Aug 27 09:05:34 pcmk-1 corosync[1540]: [MAIN ] Successfully read main configuration file '/etc/corosync/corosync.conf'.\n" +"# grep TOTEM /var/log/messages\n" "Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transport (UDP/IP).\n" "Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] The network interface [192.168.122.101] is now up.\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed.\n" -"" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] The network interface [192.168.122.101] is now up.\n" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed." msgstr "" #. Tag: para #, no-c-format msgid "With one node functional, its now safe to start Corosync on the second node as well." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# ssh pcmk-2 -- /etc/init.d/corosync start\n" -"Starting Corosync Cluster Engine (corosync): [ OK ]\n" -"[root@pcmk-1 ~]#\n" -"" +msgid "# ssh pcmk-2 -- /etc/init.d/corosync start\n" +"Starting Corosync Cluster Engine (corosync): [ OK ]\n" +"#" msgstr "" #. Tag: para #, no-c-format msgid "Check the cluster formed correctly" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# grep TOTEM /var/log/messages\n" +msgid "# grep TOTEM /var/log/messages\n" "Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transport (UDP/IP).\n" "Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] The network interface [192.168.122.101] is now up.\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed.\n" -"Aug 27 09:12:11 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed.\n" -"" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] The network interface [192.168.122.101] is now up.\n" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed.\n" +"Aug 27 09:12:11 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed." 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." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# grep pcmk_startup /var/log/messages\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: CRM: Initialized\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] Logging: Initialized pcmk_startup\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: Maximum core file size is: 18446744073709551615\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: Service: 9\n" -"Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: Local hostname: pcmk-1\n" -"" +msgid "# grep pcmk_startup /var/log/messages\n" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: CRM: InitializedAug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] Logging: Initialized pcmk_startup\n" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: Maximum core file size is: 18446744073709551615\n" +"Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: Service: 9Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: Local hostname: pcmk-1" msgstr "" #. Tag: para #, no-c-format -msgid "Now verify the Pacemaker processes have been started" +msgid "Now try starting Pacemaker and check the necessary processes have been started" msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# ps axf\n" -"  PID TTY      STAT   TIME COMMAND\n" -"    2 ?        S<     0:00 [kthreadd]\n" -"    3 ?        S<     0:00  \\_ [migration/0]\n" +msgid "# /etc/init.d/pacemaker start\n" +"Starting Pacemaker Cluster Manager: [ OK ]\n" +"\n" +"# grep -e pacemakerd.*get_config_opt -e pacemakerd.*start_child -e \"Starting Pacemaker\" /var/log/messages\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'pacemaker' for option: name\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found '1' for option: ver\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Defaulting to 'no' for option: use_logd\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Defaulting to 'no' for option: use_mgmtd\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'on' for option: debug\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'yes' for option: to_logfile\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found '/var/log/corosync.log' for option: logfile\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'yes' for option: to_syslog\n" +"Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'daemon' for option: syslog_facility\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: main: Starting Pacemaker 1.1.5 (Build: 31f088949239+): docbook-manpages publican ncurses trace-logging cman cs-quorum heartbeat corosync snmp libesmtp\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14022 for process stonith-ng\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14023 for process cib\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14024 for process lrmd\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14025 for process attrd\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14026 for process pengine\n" +"Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14027 for process crmd\n" +"\n" +"# ps axf PID TTY STAT TIME COMMAND\n" +" 2 ? S< 0:00 [kthreadd]\n" +" 3 ? S< 0:00 \\_ [migration/0]\n" "... lots of processes ...\n" -" 2166 pts/0    SLl    0:01 /usr/sbin/corosync\n" -" 2172 ?        SLs    0:00  \\_ /usr/lib64/heartbeat/stonithd\n" -" 2173 pts/0    S      0:00  \\_ /usr/lib64/heartbeat/cib\n" -" 2174 pts/0    S      0:00  \\_ /usr/lib64/heartbeat/lrmd\n" -" 2175 pts/0    S      0:00  \\_ /usr/lib64/heartbeat/attrd\n" -" 2176 pts/0    S      0:00  \\_ /usr/lib64/heartbeat/pengine\n" -" 2177 pts/0    S      0:00  \\_ /usr/lib64/heartbeat/crmd\n" -"" +"13990 ? S 0:01 pacemakerd\n" +"14022 ? Sa 0:00 \\_ /usr/lib64/heartbeat/stonithd\n" +"14023 ? Sa 0:00 \\_ /usr/lib64/heartbeat/cib\n" +"14024 ? Sa 0:00 \\_ /usr/lib64/heartbeat/lrmd\n" +"14025 ? Sa 0:00 \\_ /usr/lib64/heartbeat/attrd\n" +"14026 ? Sa 0:00 \\_ /usr/lib64/heartbeat/pengine\n" +"14027 ? Sa 0:00 \\_ /usr/lib64/heartbeat/crmd" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Next, check for any ERRORs during startup - there shouldn’t be any." +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# grep ERROR: /var/log/messages | grep -v unpack_resources\n" +"#" msgstr "" #. Tag: para #, no-c-format -msgid "And finally, check for any ERRORs during startup, there shouldn’t be any, and display the cluster’s status." +msgid "Repeat on the other node and display the cluster’s status." msgstr "" -#. Tag: screen +#. Tag: programlisting #, no-c-format -msgid "\n" -"[root@pcmk-1 ~]# grep ERROR: /var/log/messages | grep -v unpack_resources\n" -"[root@pcmk-1 ~]# crm_mon\n" +msgid "# ssh pcmk-2 -- /etc/init.d/pacemaker start\n" +"Starting Pacemaker Cluster Manager: [ OK ]\n" +"# crm_mon\n" "============\n" -"Last updated: Thu Aug 27 16:54:55 2009\n" -"Stack: openais\n" -"Current DC: pcmk-1 - partition with quorum\n" -"Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7\n" -"2 Nodes configured, 2 expected votes\n" -"0 Resources configured.\n" +"Last updated: Thu Aug 27 16:54:55 2009Stack: openais\n" +"Current DC: pcmk-1 - partition with quorum\n" +"Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f\n" +"2 Nodes configured, 2 expected votes\n" +"0 Resources configured.\n" "============\n" -"\n" -"Online: [ pcmk-1 pcmk-2 ]\n" -"" +"Online: [ pcmk-1 pcmk-2 ]" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Clusters_from_Scratch.pot b/doc/Clusters_from_Scratch/pot/Clusters_from_Scratch.pot index f7e9bac288..e5f9d32636 100644 --- a/doc/Clusters_from_Scratch/pot/Clusters_from_Scratch.pot +++ b/doc/Clusters_from_Scratch/pot/Clusters_from_Scratch.pot @@ -1,14 +1,14 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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 edda6f88ed..aa90cb253f 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: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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 3bd4a37844..a4f16a6578 100644 --- a/doc/Clusters_from_Scratch/pot/Revision_History.pot +++ b/doc/Clusters_from_Scratch/pot/Revision_History.pot @@ -1,34 +1,64 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:57\n" +"PO-Revision-Date: 2012-02-27T09:17:57\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 "" + diff --git a/doc/Pacemaker_Explained/pot/Ap-Changes.pot b/doc/Pacemaker_Explained/pot/Ap-Changes.pot new file mode 100644 index 0000000000..3df63e0011 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-Changes.pot @@ -0,0 +1,179 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 " +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 RelaxNGRelaxNG schema validation and libxml2libxml2 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. 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. 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. 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 new file mode 100644 index 0000000000..8e2fe921a0 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-Debug.pot @@ -0,0 +1,189 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 new file mode 100644 index 0000000000..96899fdd6a --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-FAQ.pot @@ -0,0 +1,159 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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." +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" +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" +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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "better and more stable interfaces" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Setup" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "What Messaging Layers Messaging Layers are Supported?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Corosync ()" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Heartbeat ()" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Can I Choose which Messaging Layer to use at Run Time?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Yes. The CRM will automatically detect which started it and behave accordingly." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Can I Have a Mixed Heartbeat-Corosync Cluster?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "No." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Which Messaging Layer Should I Choose?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "This is discussed in ." +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." +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." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ap-Install.pot b/doc/Pacemaker_Explained/pot/Ap-Install.pot new file mode 100644 index 0000000000..2083b52ea2 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-Install.pot @@ -0,0 +1,204 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "Choosing a Cluster Stackchoosing oneCluster Stack" +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Here are some factors that may influence the decision:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "SUSE/Novell, Red Hat and Oracle are all putting their collective weight behind the Corosync cluster stack." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Cluster StackCorosync CorosyncCorosync is an OSI Certified implementation of an industry standard (the Service Availability Forum Application Interface Specification)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Using Corosync gives your applications access to the following additional cluster services" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "checkpoint service" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "distributed locking service" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "extended virtual synchronization service" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "cluster closed process group service" +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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To date, Pacemaker has received less real-world testing on Corosync than it has on Cluster StackHeartbeat HeartbeatHeartbeat." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Enabling Pacemaker" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "For Corosync" +msgstr "" + +#. Tag: para +#, 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example Corosync configuration file" +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" +" mcastaddr: 226.94.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" +" }\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." +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 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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example options for an IPv6 environment" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "bindnetaddr: fec0::1:a800:4ff:fe00:20 \n" +" mcastaddr: ff05::1\n" +" " +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuration fragment for enabling Pacemaker under Corosync" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "aisexec {\n" +" user: root\n" +" group: root\n" +"}\n" +"service {\n" +" name: pacemaker\n" +" ver: 0\n" +"}\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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm respawn\n" +" " +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ap-LSB.pot b/doc/Pacemaker_Explained/pot/Ap-LSB.pot new file mode 100644 index 0000000000..cc14731312 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-LSB.pot @@ -0,0 +1,144 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The relevant part of LSB init scriptsinit scriptscompatibilityLSB spec 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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Start (stopped):" +msgstr "" + +#. Tag: programlisting +#, 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)?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Status (running):" +msgstr "" + +#. Tag: programlisting +#, 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: programlisting +#, no-c-format +msgid " /etc/init.d/some_service start ; echo \"result: $?\" " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Is the service still running?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Stop (running):" +msgstr "" + +#. Tag: programlisting +#, 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)?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Stop (stopped):" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Is the service still stopped?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Status (failed):" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "This step is not readily testable and relies on manual inspection of the script." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The script can use one of the error codes (other than 3) listed in the LSB spec to indicate that it is active but failed. This tells the cluster that before moving the resource to another node, it needs to stop it on the existing one first." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If the answer to any of the above questions is no, then the script is not LSB compliant. Your options are then to either fix the script or write an OCF agent based on the existing script." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ap-OCF.pot b/doc/Pacemaker_Explained/pot/Ap-OCF.pot new file mode 100644 index 0000000000..a26a7998cc --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-OCF.pot @@ -0,0 +1,529 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 AgentsOCF 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. 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:" +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" +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: entry +#, no-c-format +msgid "start action actionstartstart" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Start the resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully active." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "stop action actionstopstop" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Stop the resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Return 0 on success and an appropriate error code otherwise. Must not report success until the resource is fully stopped." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "monitor action actionmonitormonitor" +msgstr "" + +#. Tag: entry +#, 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." +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: entry +#, no-c-format +msgid "meta-data action actionmeta-datameta-data" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "NOTE: This is not performed as root." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "validate-all action actionvalidate-allvalidate-all" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Verify the supplied parameters" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Exit with 0 if parameters are valid, 2 if not valid, 6 if resource is not configured." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Optional Actions for OCF Agents" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "promote action actionpromotepromote" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Promote the local instance of a multi-state resource to the master/primary state." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Return 0 on success." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "demote action actiondemotedemote" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Demote the local instance of a multi-state resource to the slave/secondary state." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "notify action actionnotifynotify" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Used by the cluster to send the agent pre and post notification events telling the resource what has happened and will happen." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Must not fail. Must exit with 0." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "One action specified in the OCF specs is not currently used by the cluster:" +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-testerocf-tester to verify that your new agent complies with the OCF standard properly." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "How are OCF Return Codes Interpreted?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The first thing the cluster does is to check the return code against the expected result. If the result does not match the expected value, then the operation is considered to have failed and recovery action is initiated." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "There are three types of failure recovery:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Types of recovery performed by the cluster" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Type" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Action Taken by the Cluster" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "soft error type error typesoftsoft" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A transient error occurred" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Restart the resource or move it to a new location" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "hard error type error typehardhard" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A non-transient error that may be specific to the current node occurred" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Move the resource elsewhere and prevent it from being retried on the current node" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "fatal error type error typefatalfatal" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A non-transient error that will be common to all cluster nodes (eg. a bad configuration was specified)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Stop the resource and prevent it from being started on any cluster node" +msgstr "" + +#. Tag: para +#, 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." +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: entry +#, no-c-format +msgid "return code00" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_SUCCESS Environment VariableOCF_SUCCESS return codeOCF_SUCCESSOCF_SUCCESS" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Success. The command completed successfully. This is the expected result for all start, stop, promote and demote commands." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "soft" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code11" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_ERR_GENERIC Environment VariableOCF_ERR_GENERIC return codeOCF_ERR_GENERIC OCF_ERR_GENERIC" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Generic \"there was a problem\" error code." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code22" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_ERR_ARGS Environment VariableOCF_ERR_ARGS return codeOCF_ERR_ARGSOCF_ERR_ARGS" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "hard" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code33" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_ERR_UNIMPLEMENTED Environment VariableOCF_ERR_UNIMPLEMENTED return codeOCF_ERR_UNIMPLEMENTEDOCF_ERR_UNIMPLEMENTED" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The requested action is not implemented." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code44" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_ERR_PERM Environment VariableOCF_ERR_PERM return codeOCF_ERR_PERMOCF_ERR_PERM" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The resource agent does not have sufficient privileges to complete the task." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code55" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_ERR_INSTALLED Environment VariableOCF_ERR_INSTALLED return codeOCF_ERR_INSTALLEDOCF_ERR_INSTALLED" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The tools required by the resource are not installed on this machine." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code66" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_ERR_CONFIGURED Environment VariableOCF_ERR_CONFIGURED return codeOCF_ERR_CONFIGUREDOCF_ERR_CONFIGURED" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The resource's configuration is invalid. Eg. required parameters are missing." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "fatal" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code77" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_NOT_RUNNING Environment VariableOCF_NOT_RUNNING return codeOCF_NOT_RUNNINGOCF_NOT_RUNNING" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The resource is safely stopped. The cluster will not attempt to stop a resource that returns this for any action." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "N/A" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code88" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_RUNNING_MASTER Environment VariableOCF_RUNNING_MASTER return codeOCF_RUNNING_MASTEROCF_RUNNING_MASTER" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The resource is running in Master mode." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return code99" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "OCF_FAILED_MASTER Environment VariableOCF_FAILED_MASTER return codeOCF_FAILED_MASTEROCF_FAILED_MASTER" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "other return codes return codeotherother" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "NA" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Custom error code." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Although counterintuitive, even actions that return 0 (aka. OCF_SUCCESS) can be considered to have failed. This can happen when a resource that is expected to be in the Master state is found running as a Slave, or when a resource is found active on multiple machines." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Exceptions" +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" +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" +msgstr "" + +#. Tag: para +#, no-c-format +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 new file mode 100644 index 0000000000..a07b54b537 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-Samples.pot @@ -0,0 +1,173 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "An Empty Configuration" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An Empty ConfigurationConfigurationEmptyempty configuration" +msgstr "" + +#. Tag: programlisting +#, 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> " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "A SimpleConfigurationConfigurationSimpleSimple Configuration" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "2 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" +" <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" +" </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>\n" +" </primitive>\n" +" </resources>\n" +" <constraints>\n" +" <rsc_location id=\"myAddr-prefer\" rsc=\"myAddr\" node=\"c001n01\" score=\"INFINITY\"/>\n" +" </constraints>\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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An AdvancedConfigurationConfigurationAdvancedAdvanced Configuration" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "groups and clones with 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" +" <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" +" </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>\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" +" </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 new file mode 100644 index 0000000000..8554645536 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-Upgrade-Config.pot @@ -0,0 +1,245 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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: indexterm +#, no-c-format +msgid "Upgrading the Configuration" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ConfigurationUpgrading" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "DownloadDTD DTDDownload Download the latest DTD and ensure your configuration validates." +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." +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." +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)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Create a shadow copyexample for upgradingshadow copy to work with" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_shadow --create upgrade06" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Verify the ConfigurationVerifyVerifyConfigurationconfiguration is valid" +msgstr "" + +#. Tag: programlisting +#, 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 +#, 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 and/or try the procedure described below under ." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Check the changes" +msgstr "" + +#. Tag: programlisting +#, 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 +#, 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Test what the cluster will do when you upload the new configuration" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# ptest -VVVVV --live-check --save-dotfile upgrade06.dot\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 ptest." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Upload the changes" +msgstr "" + +#. Tag: programlisting +#, 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Manually Upgrading the Configuration" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "It is also possible to perform the ConfigurationUpgrade manuallyconfiguration upgrade steps manually. To do this" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Locate the upgrade06.xsl conversion script or download the latest version from version control" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Convert the XMLConvertXML blob:" +msgstr "" + +#. Tag: programlisting +#, 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Check the ValidateXMLxmllintValidate XMLXML validity:" +msgstr "" + +#. Tag: programlisting +#, 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 new file mode 100644 index 0000000000..e12ea5b7ac --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ap-Upgrade.pot @@ -0,0 +1,364 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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." +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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Summary of Upgrade Methodologies" +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 Cluster Stackswitching between 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. " +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "UpgradeShutdown Shutdown Upgrade Shutdown" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "yes" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "always" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "N/A" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "no" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "UpgradeRolling Rolling Upgrade Rolling" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "UpgradeReattach Reattach Upgrade Reattach" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Procedure" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "On each node:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Shutdown the cluster stack (Heartbeat or Corosync)" +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Check the configuration manually or with the crm_verify tool if available." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In this scenario each node is removed from the cluster, upgraded and then brought back online until all nodes are running the newest version." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "This method is currently broken between Pacemaker 0.6.x and 1.0.x." +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. If there is sufficient demand, the work to repair 0.6 -> 1.0 compatibility will be carried out. Otherwise, please try one of the other upgrade strategies. Detach/Reattach is a particularly good option for most people." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "On the first node, check the configuration manually or with the crm_verify tool if available." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Start the cluster stack. 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Repeat for each node in the cluster." +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: entry +#, no-c-format +msgid "Pacemaker 1.0.x" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Pacemaker 1.0.0" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Pacemaker 0.7.x" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Pacemaker 0.6 or Heartbeat 2.1.3" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Pacemaker 0.6.x" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Heartbeat 2.0.8" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Heartbeat 2.1.3 (or less)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Heartbeat 2.0.4" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Heartbeat 2.0.4 (or less)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Heartbeat 2.0.0" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Tell the cluster to stop managing services. This is required to allow the services to remain active after the cluster shuts down." +msgstr "" + +#. Tag: programlisting +#, 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)" +msgstr "" + +#. Tag: programlisting +#, 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 "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 +#, 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:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_resource -t primitive -r <rsc_id> -p is-managed -v false" +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The oldest version of the CRM to support this upgrade type was in Heartbeat 2.0.4" +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Author_Group.pot b/doc/Pacemaker_Explained/pot/Author_Group.pot new file mode 100644 index 0000000000..527838eb97 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Author_Group.pot @@ -0,0 +1,124 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "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 "" + diff --git a/doc/Pacemaker_Explained/pot/Book_Info.pot b/doc/Pacemaker_Explained/pot/Book_Info.pot new file mode 100644 index 0000000000..70760e2cb8 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Book_Info.pot @@ -0,0 +1,44 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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, Pacemaker comes with a cluster shell; a Python based GUI exists, too, 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." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot new file mode 100644 index 0000000000..1940fe496a --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot @@ -0,0 +1,868 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 " Remote connect Remote administration 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 VariableRemote Administration Environment Variable" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "CIB_*, Env. Var. for Remote Conn.user Environment VariableCIB_user CIB_user" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The user to connect as. Needs to be part of the hacluster group on the target host. Defaults to $USER." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "CIB_*, Env. Var. for Remote Conn.passwd Environment VariableCIB_passwd CIB_passwd" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The user's password. Read from the command line if unset." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "CIB_*, Env. Var. for Remote Conn.server Environment VariableCIB_server CIB_server" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The host to contact. Defaults to localhost." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "CIB_*, Env. Var. for Remote Conn.port Environment VariableCIB_port CIB_port" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The port on which to contact the server; required." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "CIB_*, Env. Var. for Remote Conn.encrypted Environment VariableCIB_encrypted CIB_encrypted" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Encrypt network traffic; defaults to 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:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "\n" +" export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someguy;\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)." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Remoteconnect, CIB options Extra top-level CIB options for remote access" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Field" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "remote-tls-port remote-tls-port" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Listen for encrypted remote connections on this port. Default: none" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "remote-clear-port remote-clear-port" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Listen for plaintext remote connections on this port. Default: none" +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." +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)." +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." +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:" +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: indexterm +#, no-c-format +msgid "Moving Resources" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceMoving" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Manual Intervention" +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." +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." +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:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_standby --get-value" +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." +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:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_standby --get-value --node-uname sles-2" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To change the current node's standby status, use --attr-value instead of --get-value." +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_standby --attr-value" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Again, you can change another host's value by supplying a host name with --node-uname." +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:" +msgstr "" + +#. Tag: programlisting +#, 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 +#, 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 +#, 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 +#, no-c-format +msgid "crm_resource -M -r Email -H sles-1\n" +" crm_resource -U -r Email" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Alternatively, if you only care that the resource should be moved from its current location, try" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_resource -M -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." +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 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. . 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." +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." +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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Stop failures are slightly different and crucial. If a resource fails to stop and STONITH is enabled, then the cluster will fence the node in order to be able to start the resource elsewhere. If STONITH is not enabled, then the cluster has no way to continue and will not try to start the resource elsewhere, but will try to stop it again after the failure timeout." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Please read before enabling this option." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Moving Resources Due to Connectivity Changes" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Setting up the cluster to move resources when external connectivity is lost is a two-step process." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Tell Pacemaker to monitor connectivity" +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. ." +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." +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. If your version of Pacemaker does not contain the ping agent, you can download the latest version." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Common Options for a 'ping' Resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "dampenResource Option ResourceOptiondampen dampen" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "multiplierResource Option ResourceOptionmultiplier multiplier" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "host_listResource Option ResourceOptionhost_list host_list" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example ping cluster resource, 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "NOTE: Before reading the following, please make sure you have read and understood above." +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. TODO: is the idea that only nodes that can reach eg. the router should have active resources?" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Don't run 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." +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." +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " <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" +" </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)." +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:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "How the cluster translates the pingd 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" +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Not all resources are able to migrate, see the Migration Checklist below, and those that can, won't do so in all situations. Conceptually there are two requirements from which the other prerequisites follow:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "the resource must be active and healthy at the old location" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "everything required for the resource to run must be available on both the old and new locations" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The cluster is able to accommodate both 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)." +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." +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. TODO: how can a KVM with DRBD migrate?" +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." +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 "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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To take advantage of this capability, your 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!" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "The DRBD Agent's Control logic for Supporting the reload Operation" +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 lang=\"en\">\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 lang=\"en\">Full path to the drbd.conf file.</longdesc>\n" +" <shortdesc lang=\"en\">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." +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" +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 new file mode 100644 index 0000000000..2574d90de7 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Resources.pot @@ -0,0 +1,1330 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "Group Resources ResourcesGroups Groups - A Syntactic Shortcut" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "One of the most common elements of a cluster is a set of resources that need to be located together, start sequentially, and stop in the reverse order. To simplify this configuration we support the concept of groups." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example group" +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" +" </instance_attributes>\n" +" </primitive>\n" +" <primitive id=\"Email\" class=\"lsb\" type=\"exim\"/>\n" +" </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" +" </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 "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: entry +#, no-c-format +msgid "idGroup Resource Property Group Resource Propertiesid ResourceGroup Propertyid id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Your name for the group" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Options" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Options inherited from simple resources: priority, target-role, is-managed" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Contents" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Groups may only contain a collection of primitive cluster resources. To refer to the child of a group resource, just use the child's id instead of the group's." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example 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 "resource-stickinessof a Group Resource Stickiness" +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 "Clone Resources ResourcesClones Clones - Resources That Get Active on Multiple Hosts" +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." +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" +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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Stateful clones are covered later in ." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example clone" +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 "Properties of a Clone Resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "idClone Resource Property Clone Resource Propertiesid ResourceClone Propertyid id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Your name for the clone" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Options inherited from simple resources: priority, target-role, is-managed" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Clone specific configuration options" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "clone-max Clone Resource Property Clone Resource Propertiesclone-max ResourceClone Propertyclone-max clone-max" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How many copies of the resource to start. Defaults to the number of nodes in the cluster." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "clone-node-max Clone Resource Property Clone Resource Propertiesclone-node-max ResourceClone Propertyclone-node-max clone-node-max" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How many copies of the resource can be started on a single node; default 1." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "notify Clone Resource Property Clone Resource Propertiesnotify ResourceClone Propertynotify notify" +msgstr "" + +#. Tag: entry +#, 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" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "globally-unique Clone Resource Property Clone Resource Propertiesglobally-unique ResourceClone Propertyglobally-unique globally-unique" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Does each copy of the clone perform a different function? Allowed values: false, true" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "ordered Clone Resource Property Clone Resource Propertiesordered ResourceClone Propertyordered ordered" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Should the copies be started in series (instead of in parallel). Allowed values: false, true" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "interleave Clone Resource Property Clone Resource Propertiesinterleave ResourceClone Propertyinterleave interleave" +msgstr "" + +#. Tag: entry +#, 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" +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: para +#, no-c-format +msgid "Clones must contain exactly one group or one regular 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: 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." +msgstr "" + +#. Tag: para +#, 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." +msgstr "" + +#. Tag: para +#, 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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example constraints involving clones" +msgstr "" + +#. Tag: programlisting +#, 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> " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Stickiness" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "resource-stickinessof a Clone Resource 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: title +#, no-c-format +msgid "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 ${OCF_SUCCESS} if the node has that exact instance active. All other probes for instances of the clone should result in ${OCF_NOT_RUNNING}. Unless of course they are failed, in which case they should return one of the other OCF error codes." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Copies of a clone are identified by appending a colon and a numerical offset, eg. 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Environment variables supplied with Clone notify actions" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Variable" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_type OCF_RESKEY_CRM_meta_notify_type OCF_RESKEY_CRM_meta_notify_type" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: pre, post" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_operation OCF_RESKEY_CRM_meta_notify_operation OCF_RESKEY_CRM_meta_notify_operation" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: start, stop" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_start_resource OCF_RESKEY_CRM_meta_notify_start_resource OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources to be started" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_stop_resource OCF_RESKEY_CRM_meta_notify_stop_resource OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources to be stopped" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_active_resource OCF_RESKEY_CRM_meta_notify_active_resource OCF_RESKEY_CRM_meta_notify_active_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources that are running" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_inactive_resource OCF_RESKEY_CRM_meta_notify_inactive_resource OCF_RESKEY_CRM_meta_notify_inactive_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources that are not running" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_start_uname OCF_RESKEY_CRM_meta_notify_start_uname OCF_RESKEY_CRM_meta_notify_start_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources will be started" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_stop_uname OCF_RESKEY_CRM_meta_notify_stop_uname OCF_RESKEY_CRM_meta_notify_stop_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources will be stopped" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_active_uname OCF_RESKEY_CRM_meta_notify_active_uname OCF_RESKEY_CRM_meta_notify_active_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources are running" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM_meta_notify_inactive_uname OCF_RESKEY_CRM_meta_notify_inactive_uname OCF_RESKEY_CRM_meta_notify_inactive_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources are not running" +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." +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" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "\n" +" 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\"\n" +" " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Proper Interpretation of Notification Environment Variables" +msgstr "" + +#. Tag: para +#, 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: para +#, 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: para +#, 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 ResourcesMulti-state Multi-state - Resources That Have Multiple Modes" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties of a Multi-State Resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "idMulti-State Resource Property Multi-State Resource Propertiesid ResourceMulti-State Propertyid id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Your name for the multi-state resource" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Options inherited from simple 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" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "master-max Multi-State Resource Property Multi-State Resource Propertiesmaster-max ResourceMulti-State Propertymaster-max master-max" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How many copies of the resource can be promoted to master status; default 1." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "master-node-max Multi-State Resource Property Multi-State Resource Propertiesmaster-node-max ResourceMulti-State Propertymaster-node-max master-node-max" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How many copies of the resource can be promoted to master status on a single node; default 1." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Masters must contain exactly one group or one regular 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\"." +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." +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 "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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Additional constraint options relevant to multi-state resources" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "rsc-role Multi-State Resource Constraints Multi-State Resource Constraintsrsc-role ResourceMulti-State Constraintsrsc-role 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "with-rsc-role Multi-State Resource Constraints Multi-State Resource Constraintswith-rsc-role ResourceMulti-State Constraintswith-rsc-role 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "first-action Multi-State Resource Constraints Multi-State Resource Constraintsfirst-action ResourceMulti-State Constraintsfirst-action first-action" +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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "then-action Multi-State Resource Constraints Multi-State Resource Constraintsthen-action ResourceMulti-State Constraintsthen-action then-action" +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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example 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 "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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "resource-stickinessof a Multi-State Resource 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." +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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Manually specifying which node should be promoted" +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: 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." +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." +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." +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: entry +#, no-c-format +msgid "return codeOCF_NOT_RUNNING Environment VariableOCF_NOT_RUNNING OCF_NOT_RUNNING OCF_NOT_RUNNING" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Stopped" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return codeOCF_SUCCESS Environment VariableOCF_SUCCESS OCF_SUCCESS OCF_SUCCESS" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Running (Slave)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return codeOCF_RUNNING_MASTER Environment VariableOCF_RUNNING_MASTER OCF_RUNNING_MASTER OCF_RUNNING_MASTER" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Running (Master)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "return codeOCF_FAILED_MASTER Environment VariableOCF_FAILED_MASTER OCF_FAILED_MASTER OCF_FAILED_MASTER" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Failed (Master)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Other" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Failed (Slave)" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Environment variables supplied with Master notify actionsEmphasized variables are specific to Master resources and all behave in the same manner as described for Clone resources." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_type OCF_RESKEY_CRM_meta_notify_type OCF_RESKEY_CRM_meta_notify_type" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_operation OCF_RESKEY_CRM_meta_notify_operationOCF_RESKEY_CRM_meta_notify_operation" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_active_resource OCF_RESKEY_CRM_meta_notify_active_resource OCF_RESKEY_CRM_meta_notify_active_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources the that are running" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_inactive_resource OCF_RESKEY_CRM_meta_notify_inactive_resource OCF_RESKEY_CRM_meta_notify_inactive_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources the that are not running" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_master_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_master_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_master_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources that are running in Master mode" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_slave_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_slave_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_slave_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources that are running in Slave mode" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_start_resource OCF_RESKEY_CRM_meta_notify_start_resource OCF_RESKEY_CRM_meta_notify_start_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_stop_resource OCF_RESKEY_CRM_meta_notify_stop_resource OCF_RESKEY_CRM_meta_notify_stop_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_promote_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_promote_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources to be promoted" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_demote_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_demote_resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_demote_resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Resources to be demoted" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_start_uname OCF_RESKEY_CRM_meta_notify_start_uname OCF_RESKEY_CRM_meta_notify_start_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_stop_uname OCF_RESKEY_CRM_meta_notify_stop_uname OCF_RESKEY_CRM_meta_notify_stop_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_promote_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_promote_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_promote_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources will be promoted" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_demote_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_demote_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_demote_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources will be demoted" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_active_uname OCF_RESKEY_CRM_meta_notify_active_uname OCF_RESKEY_CRM_meta_notify_active_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_inactive_uname OCF_RESKEY_CRM_meta_notify_inactive_uname OCF_RESKEY_CRM_meta_notify_inactive_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_master_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_master_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_master_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources are running in Master mode" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid " OCF_RESKEY_CRM_meta_notify_slave_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Environment VariableOCF_RESKEY_CRM__meta_notify_slave_uname" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCF_RESKEY_CRM_meta_notify_slave_uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Nodes on which resources are running in Slave mode" +msgstr "" + +#. Tag: para +#, 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: para +#, 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: para +#, 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: para +#, no-c-format +msgid "Post-notification (start) / Pre-notification (promote)" +msgstr "" + +#. Tag: para +#, 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 new file mode 100644 index 0000000000..e5d9931dcc --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Basics.pot @@ -0,0 +1,513 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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." +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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The configuration section itself is divided into four parts:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Configuration options (called crm_config)" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Nodes" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Resources" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Resource relationships (called constraints)" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " <cib generated=\"true\" 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>" +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." +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." +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." +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." +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." +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." +msgstr "" + +#. Tag: programlisting +#, 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If you only wanted to modify the resources section, you could instead do" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# cibadmin --query --obj_type resources > tmp.xml\n" +"# vi tmp.xml</command>]\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." +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" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# cibadmin -Q | grep stonith</command>\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:" +msgstr "" + +#. Tag: para +#, 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To enable stonith for example, one could run:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_attribute --attr-name stonith-enabled --attr-value true" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Or, to see if somenode is allowed to run resources, there is:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_standby --get-value --node-uname somenode" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Or, to find the current location of my-test-rsc, one can use:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_resource --locate --resource my-test-rsc" +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." +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!</warning>" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " # crm_shadow --create test\n" +" Setting up shadow instance\n" +" Type Ctrl-D to exit the crm_shadow shell\n" +" shadow[test]:\n" +" shadow[test] # crm_shadow --which\n" +" test" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster’s active configuration. Once you have finished experimenting, you can either commit the changes, or discard them as shown below. 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." +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " shadow[test] # crm_failcount -G -r rsc_c001n01\n" +" name=fail-count-rsc_c001n01 value=0\n" +" shadow[test] # crm_standby -v on -n c001n02\n" +" shadow[test] # crm_standby -G -n c001n02\n" +" name=c001n02 scope=nodes value=on\n" +" shadow[test] # cibadmin --erase --force\n" +" shadow[test] # cibadmin --query\n" +" <cib cib_feature_revision=\"1\" validate-with=\"pacemaker-1.0\" admin_epoch=\"0\" crm_feature_set=\"3.0\" have-quorum=\"1\" epoch=\"112\"\n" +" dc-uuid=\"c001n01\" num_updates=\"1\" cib-last-written=\"Fri Jun 27 12:17:10 2008\">\n" +" <configuration>\n" +" <crm_config/>\n" +" <nodes/>\n" +" <resources/>\n" +" <constraints/>\n" +" </configuration>\n" +" <status/>\n" +" </cib>\n" +" shadow[test] # crm_shadow --delete test --force\n" +" Now type Ctrl-D to exit the crm_shadow shell\n" +" shadow[test] # exit\n" +" # crm_shadow --which\n" +" No shadow instance provided\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 ptest, eg." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "ptest --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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Interpreting the Graphviz output" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Arrows indicate ordering dependencies" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Dashed-arrows indicate dependencies that are not present in the transition graph" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Actions with a dashed border of any color do not form part of the transition graph" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Actions with a green border form part of the transition graph" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Actions with a red border are ones the cluster would like to execute but cannot run" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Actions with a blue border are ones the cluster does not feel need to be executed" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Actions with black text are sent to the LRM" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Resource actions have text of the form 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 ptest, use ptest --help." +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?" +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 new file mode 100644 index 0000000000..5380fd305e --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Constraints.pot @@ -0,0 +1,771 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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: title +#, no-c-format +msgid "Scores" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceConstraints" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Constraintsfor Resources" +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." +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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Any value + INFINITY = INFINITY" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Any value - INFINITY = -INFINITY" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "INFINITY - INFINITY = -INFINITY" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Deciding Which Nodes a Resource Can Run On" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Options" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Options for Simple Location Constraints" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Field" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "idConstraint Field Constraint Fieldid entry>id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A unique name for the constraint" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "rsc Constraint Field Constraint Fieldrsc rsc" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A resource name" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "NodeConstraint Field Constraint Fieldnode node" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A node's uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "scoreConstraint Field Constraint Fieldscore score" +msgstr "" + +#. Tag: entry +#, 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. Values of +/- INFINITY change \"should\"/\"should not\" to \"must\"/\"must not\"." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Asymmetrical Opt-In Clusters Cluster TypeAsymmetrical Opt-In Asymmetrical \"Opt-In\" Clusters" +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 +#, no-c-format +msgid "crm_attribute --attr-name symmetric-cluster --attr-value 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example set of opt-in location constraints" +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 Cluster TypeSymmetrical Opt-Out Symmetrical \"Opt-Out\" Clusters" +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 +#, no-c-format +msgid "crm_attribute --attr-name symmetric-cluster --attr-value 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" +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" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Specifying in which Order Resources Should Start/Stop" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The way to specify the order in which resources should start is by creating rsc_order constraints." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties of an Ordering Constraint" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "first" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The name of a resource that must be started before the then resource is allowed to." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "then" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The name of a resource. This resource will start after the first resource." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "score" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "If greater than zero, the constraint is mandatory. Otherwise it is only a suggestion. Default value: INFINITY" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "symmetrical" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "If true, which is the default, stop the resources in the reverse order. Default value: true" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Mandatory Ordering" +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." +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)." +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)." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Advisory 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Example of an optional and mandatory ordering constraint" +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" +" </constraints> " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Some additional information on ordering constraints can be found in the document Ordering Explained." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Placing Resources Relative to other Resources" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "When the location of one resource depends on the location of another one, we call this colocation." +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. . So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Another thing to keep in mind is that, assuming A is collocated with B, the cluster will also take into account A's preferences when deciding which node to choose for B. For a detailed look at exactly how this occurs, see the Colocation Explained document." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties of a Collocation Constraint" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A unique name for the constraint." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "rsc" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "with-rsc" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, 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\"." +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." +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:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example colocation constraint" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_colocation id=\"colocate\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"INFINITY\"/>\n" +" " +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." +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\"" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example anti-colocation constraint" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_colocation id=\"anti-colocate\"\n" +" rsc=\"resource1\" with-rsc=\"resource2\" score=\"-INFINITY\"/> \n" +" " +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." +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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example advisory-only colocation constraint" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_colocation id=\"colocate-maybe\" rsc=\"resource1\" with-rsc=\"resource2\" score=\"500\"/>\n" +" " +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: caption +#, no-c-format +msgid "Visual representation of the four resources' start order for the above constraints" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To simplify this situation, there is an alternate format for 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "A group resource with the equivalent ordering rules" +msgstr "" + +#. Tag: programlisting +#, 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> " +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." +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" +msgstr "" + +#. Tag: caption +#, no-c-format +msgid "Visual representation of the start order for two ordered sets of unordered resources" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Of course either set -- or both sets -- of resources can also be internally ordered (by setting 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 "Three Resources Sets" +msgstr "" + +#. Tag: caption +#, no-c-format +msgid "Visual representation of the start order for the three sets defined above" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Collocating Sets of Resources" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "A chain of collocated 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-2\" rsc=\"C\" with-rsc=\"B\" score=\"INFINITY\"/>\n" +" <rsc_colocation id=\"coloc-3\" rsc=\"D\" with-rsc=\"C\" 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "The equivalent colocation chain expressed using resource_sets" +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_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" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Using colocation 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_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_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." +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." +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_ref id=\"A\"/>\n" +" <resource_ref id=\"B\"/>\n" +" </resource_set>\n" +" <resource_set id=\"collocated-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_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: caption +#, no-c-format +msgid "Visual representation of a colocation chain where the members of the middle set have no inter-dependencies" +msgstr "" + diff --git a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot b/doc/Pacemaker_Explained/pot/Ch-Intro.pot similarity index 73% copy from doc/Clusters_from_Scratch/pot/Ch-Intro.pot copy to doc/Pacemaker_Explained/pot/Ch-Intro.pot index 6507b25169..fae561e5c9 100644 --- a/doc/Clusters_from_Scratch/pot/Ch-Intro.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Intro.pot @@ -1,269 +1,269 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 best, it will focus exclusively on the XML syntax used to configure the CIB." +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, Pacemaker comes with a cluster shell and a Python based GUI exists, however these tools will not be covered at all in this document It is hoped however, that having understood the concepts explained here, that the functionality of these tools will also be more readily understood. , precisely because they hide the XML." +msgid "For those that are allergic to XML, Pacemaker comes with a cluster shell; a Python based GUI exists, too, 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." msgstr "" #. Tag: title #, no-c-format 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. 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)." 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" 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 TODO: quorum-driven?" 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 services type" 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: para #, no-c-format msgid "Unified, scriptable, cluster shell" 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." msgstr "" #. Tag: title #, no-c-format msgid "Active/Passive Redundancy" msgstr "" #. Tag: caption #, 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" msgstr "" #. Tag: caption #, 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" msgstr "" #. Tag: caption #, 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" 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 "Core cluster infrastructure providing messaging and membership functionality (illustrated in red)" msgstr "" #. Tag: para #, no-c-format -msgid "Non-cluster aware components (illustrated in blue). 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 "Non-cluster aware components (illustrated in green). 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." msgstr "" #. Tag: para #, no-c-format -msgid "A brain (illustrated in green) that 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 them offline with remote power switches." +msgid "A brain (illustrated in blue) that 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." msgstr "" #. Tag: title #, no-c-format msgid "Conceptual Stack Overview" msgstr "" #. Tag: caption #, no-c-format msgid "Conceptual overview of the cluster stack" 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. 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 "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. . 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." msgstr "" #. Tag: title #, no-c-format msgid "The Pacemaker Stack" msgstr "" #. Tag: caption #, no-c-format msgid "The Pacemaker stack when running on Corosync" msgstr "" #. Tag: title #, no-c-format msgid "Internal Components" 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):" msgstr "" #. Tag: para #, no-c-format msgid "CIB (aka. Cluster Information Base)" msgstr "" #. Tag: para #, no-c-format msgid "CRMd (aka. Cluster Resource Management daemon)" msgstr "" #. Tag: para #, no-c-format msgid "PEngine (aka. PE or Policy Engine)" msgstr "" #. Tag: para #, no-c-format msgid "STONITHd" msgstr "" #. Tag: caption #, no-c-format -msgid "Subsystems of a Pacemaker cluster running on Corosync" +msgid "Subsystems of a Pacemaker cluster" 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." 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 "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." 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 "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)." 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 "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 "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." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Nodes.pot b/doc/Pacemaker_Explained/pot/Ch-Nodes.pot new file mode 100644 index 0000000000..98895c4a53 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Nodes.pot @@ -0,0 +1,263 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<node id=\"1186dc9a-324d-425a-966e-d757e693dc86\" uname=\"pcmk-1\" type=\"normal\"/>\n" +" " +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Describing a Cluster Node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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 the section on ." +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" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` \n" +"\n" +" <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" +" </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:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Adding a New Cluster Node" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Corosync" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Heartbeat" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Removing a Cluster Node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for heartbeat to forget about the node (pcmk-1 in the example below)." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "On the host to be removed:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Find and record the node's Corosync id: crm_node -i" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Stop the cluster: /etc/init.d/corosync stop" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Next, from one of the remaining active cluster nodes:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Tell the cluster to forget about the removed host: crm_node -R COROSYNC_ID" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Only now is it safe to delete the node from the CIB with:" +msgstr "" + +#. Tag: programlisting +#, 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\"/>'" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. 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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "hb_delnode pcmk-1" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Only then is it safe to delete the node from the CIB with:" +msgstr "" + +#. Tag: programlisting +#, 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\"/>'" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Replacing a Cluster Node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The five-step guide to replacing an existing cluster node:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Make sure the old node is completely stopped" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Give the new machine the same hostname and IP address as the old one" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Install the cluster software :-)" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Copy /etc/corosync/corosync.conf and /etc/ais/authkey (if it exists) to the new node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Start the new cluster node" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The seven-step guide to replacing an existing cluster node:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Give the new machine the same hostname as the old one" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Go to an active cluster node and look up the UUID for the old node in /var/lib/heartbeat/hostcache" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Install the cluster software" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Copy ha.cf and authkeys to the new node" +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" +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Options.pot b/doc/Pacemaker_Explained/pot/Ch-Options.pot new file mode 100644 index 0000000000..f05dfb2e8d --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Options.pot @@ -0,0 +1,495 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Special Options" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " Special Cluster Options Cluster OptionsSpecial Options Special Options " +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuration Version" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " Configuration VersionCluster Option Cluster Option Cluster OptionsConfiguration Version Configuration Version " +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuration Version Properties" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Field" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "admin_epoch" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " admin_epoch Cluster Option Cluster Optionsadmin_epoch admin_epoch Never modified by the cluster. Use this to make the configurations on any inactive nodes obsolete." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "epoch" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " epoch Cluster Option Cluster Optionsepoch epoch Incremented every time the configuration is updated (usually by the admin)" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "num_updates" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " num_updates Cluster Option Cluster Optionsnum_updates num_updates Incremented every time the configuration or status is updated (usually by the cluster)" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Other Fields" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties Controlling Validation" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "validate-with" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " validate-with Cluster Option Cluster Optionsvalidate-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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Fields Maintained by the Cluster" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties Maintained by the Cluster" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm-debug-origin" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " crm-debug-origin Cluster Fields Cluster Fieldscrm-debug-origin crm-debug-origin Indicates where the last update came from. Informational purposes only." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "cib-last-written" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " cib-last-written Cluster Fields Cluster Fieldscib-last-written cib-last-written Indicates when the configuration was last written to disk. Informational purposes only." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "dc-uuid" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " dc-uuid Cluster Fields Cluster Fieldsdc-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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "have-quorum" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " have-quorum Cluster Fields Cluster Fieldshave-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." +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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "cibadmin --modify --crm_xml ‘<cib admin_epoch=\"42\"/>'" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A complete set of fields will look something like this:" +msgstr "" + +#. Tag: programlisting +#, 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\">" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Cluster options, as you might expect, control how the cluster behaves when confronted with certain situations." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "They are grouped into sets and, in advanced configurations, there may be more than one. This will be described later in the section on <xref linkend=\"ch-rules\"/> where we will show how to have the cluster use different sets of options during working hours (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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Available Cluster Options" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Option" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Default" +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-limit Cluster Options Cluster Optionsbatch-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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "no-quorum-policy" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "stop" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " no-quorum-policy Cluster Options Cluster Optionsno-quorum-policy no-quorum-policy What to do when the cluster does not have quorum. Allowed values:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "* ignore - continue all resource management * freeze - continue resource management, but don’t recover resources from nodes not in the affected partition * stop - stop all resources in the affected cluster partition * suicide - fence all nodes in the affected cluster partition" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "symmetric-cluster" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "TRUE" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " symmetric-cluster Cluster Options Cluster Optionssymmetric-cluster symmetric-cluster Can all resources run on any node by default?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "stonith-enabled" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " stonith-enabled Cluster Options Cluster Optionsstonith-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." +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-action Cluster Options Cluster Optionsstonith-action stonith-action Action to send to STONITH device. Allowed values: reboot, poweroff." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "cluster-delay" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "60s" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " cluster-delay Cluster Options Cluster Optionscluster-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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "stop-orphan-resources" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " stop-orphan-resources Cluster Options Cluster Optionsstop-orphan-resources stop-orphan-resources Should deleted resources be stopped?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "stop-orphan-actions" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " stop-orphan-actions Cluster Options Cluster Optionsstop-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-fatal Cluster Options Cluster Optionsstart-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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pe-error-series-max" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "-1 (all)" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pe-error-series-max Cluster Options Cluster Optionspe-error-series-max pe-error-series-max The number of PE inputs resulting in ERRORs to save. Used when reporting problems." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pe-warn-series-max" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pe-warn-series-max Cluster Options Cluster Optionspe-warn-series-max pe-warn-series-max The number of PE inputs resulting in WARNINGs to save. Used when reporting problems." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "pe-input-series-max" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " pe-input-series-max Cluster Options Cluster Optionspe-input-series-max pe-input-series-max The number of \"normal\" PE inputs to save. Used when reporting problems." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Querying and Setting Cluster Options" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " Querying Cluster Options Setting Cluster Options Cluster OptionsQuerying Querying Cluster OptionsSetting Setting " +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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_attribute --attr-name cluster-delay --get-value" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "which is more simply written as" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_attribute --get-value -n cluster-delay" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If a value is found, you’ll see a result like this:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid " # crm_attribute --get-value -n cluster-delay" +msgstr "" + +#. Tag: literallayout +#, no-c-format +msgid "name=cluster-delay value=60s" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "However, if no value is found, the tool will display an error:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "# crm_attribute --get-value -n clusta-deway" +msgstr "" + +#. Tag: literallayout +#, no-c-format +msgid "name=clusta-deway value=(null)\n" +"Error performing operation: The object/attribute does not exist" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To use a different value, eg. 30, simply run:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_attribute --attr-name cluster-delay --attr-value 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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_attribute --attr-name cluster-delay --delete-attr" +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: para +#, no-c-format +msgid "# crm_attribute --attr-name batch-limit --delete-attr" +msgstr "" + +#. Tag: literallayout +#, no-c-format +msgid "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" +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 the section on <xref linkend=\"ch-rules\"/>." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Resources.pot b/doc/Pacemaker_Explained/pot/Ch-Resources.pot new file mode 100644 index 0000000000..55525a15ec --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Resources.pot @@ -0,0 +1,959 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\n" +"Last-Translator: Automatically generated\n" +"Language-Team: None\n" +"MIME-Version: 1.0\n" +"Content-Type: application/x-publican; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#, no-c-format +msgid "Cluster Resources" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "What is a Cluster Resource" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceDescription" +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. 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "For this reason it is crucial that resource agents are well tested." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Typically resource agents come in the form of shell scripts, however they can be written using any technology (such as C, Python or Perl) that the author is comfortable with." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Supported Resource Classes" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceClasses" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "There are three basic classes of agents supported by Pacemaker. In order of encouraged usage they are:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Open Cluster Framework" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceOCF" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "OCFResources" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Open Cluster FrameworkResources" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The OCF Spec - at least as it relates to resource agents.'Note: 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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. . 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." +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." +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: indexterm +#, no-c-format +msgid "ResourceLSB" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "LSBResources" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "Linus Standard BaseResources" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "LSB resource agents are those typically found in /etc/init.d. 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 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. To see if your init script is LSB-compatible, see the FAQ entry . The most common problems are:" +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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Starting a started resource returns an error (this violates the LSB spec)" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Stopping a stopped resource returns an error (this violates the LSB spec)" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Legacy Heartbeat" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceHeartbeat (legacy)" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "HeartbeatLegacy 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. To enable administrators to continue to use these agents, they are supported by the new cluster manager See for more information.." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "STONITH" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "ResourceSTONITH" +msgstr "" + +#. Tag: indexterm +#, no-c-format +msgid "STONITHResources" +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 ." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "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." +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: entry +#, no-c-format +msgid "id id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Your name for the resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "classResource Field ResourceFieldclass class" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The standard the script conforms to. Allowed values: heartbeat, lsb, ocf, stonith" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "typeResource Field ResourceFieldtype type" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The name of the Resource Agent you wish to use. Eg. IPaddr or Filesystem" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "providerResource Field ResourceFieldprovider provider" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Resource definitions can be queried with the crm_resource tool. For example" +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "crm_resource --resource Email --query-xml" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "might produce" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example LSB resource" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<primitive id=\"Email\" class=\"lsb\" type=\"exim\"/>\n" +" " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "One of the main drawbacks to LSB resources is that they do not allow any parameters!" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Example for an OCF resource:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example OCF resource" +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>\n" +" </primitive> " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Or, finally for the equivalent legacy Heartbeat resource:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "An example Heartbeat resource" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " <primitive id=\"Public-IP-legacy\" class=\"heartbeat\" type=\"IPaddr\">\n" +" <instance_attributes id=\"params-public-ip-legacy\">\n" +" <nvpair id=\"public-ip-addr-legacy\" name=\"1\" value=\"1.2.3.4\"/>\n" +" </instance_attributes>\n" +" </primitive> " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Heartbeat resources take only ordered and unnamed parameters. The supplied name therefore indicates the order in which they are passed to the script. Only single digit values are allowed." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Options for a Primitive Resource" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Default" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "priorityResource Option ResourceOptionpriority priority" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "0" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "target-roleResource Option ResourceOptiontarget-role target-role" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Started" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "What state should the cluster attempt to keep this resource in? Allowed values:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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)" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Master - Allow the resource to be started and, if appropriate, promoted" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "is-managedResource Option ResourceOptionis-managed is-managed" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "TRUE" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Is the cluster allowed to start and stop the resource? Allowed values: true, false" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "resource-stickinessResource Option ResourceOptionresource-stickiness resource-stickiness" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Inherited" +msgstr "" + +#. Tag: entry +#, 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" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "migration-thresholdResource Option ResourceOptionmigration-threshold migration-threshold" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "INFINITY (disabled)" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "failure-timeoutResource Option ResourceOptionfailure-timeout failure-timeout" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "0 (disabled)" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "multiple-activeResource Option ResourceOptionmultiple-active multiple-active" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "stop_start" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "What should the cluster do if it ever finds the resource active on more than one node. Allowed values:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "block - mark the resource as unmanaged" +msgstr "" + +#. Tag: para +#, no-c-format +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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If you performed the following commands on the previous 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\n" +" " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "the resulting resource definition would 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" +" </primitive> " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Setting Global Defaults for Resource Options" +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," +msgstr "" + +#. Tag: para +#, no-c-format +msgid "crm_attribute --type rsc_defaults --attr-name is-managed --attr-value 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)." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If your resource agent supports parameters, you can add them with the crm_resource command. For instance" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_resource --resource Public-IP --set-parameter ip --property-value 1.2.3.4" +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=\"1.2.3.4\"/>\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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Displaying the metadata for the Dummy resource agent template" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "export OCF_ROOT=/usr/lib/ocf; $OCF_ROOT/resource.d/pacemaker/Dummy meta-data\n" +" <?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" +" \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" +" \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" +" \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" +" \n" +" <actions>\n" +" <action name=\"start\" timeout=\"90\" />\n" +" <action name=\"stop\" timeout=\"100\" />\n" +" <action name=\"monitor\" timeout=\"20\" interval=\"10\" depth=\"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> " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Resource Operations" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Monitoring Resources for Failure" +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." +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" +" </instance_attributes>\n" +" </primitive> " +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties of an Operation" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Your name for the action. Must be unique." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "name" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The action to perform. Common values: monitor, start, stop" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "interval" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How frequently (in seconds) to perform the operation. Default value: 0, meaning never." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "timeout" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How long to wait before declaring the action has failed." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "requires" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "What conditions need to be satisfied before this action occurs. Allowed values:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "nothing - The cluster may start this resource at any time" +msgstr "" + +#. Tag: para +#, no-c-format +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "STONITH resources default to nothing, and all others default to fencing if STONITH is enabled and quorum otherwise." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "on-fail" +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" +msgstr "" + +#. Tag: para +#, no-c-format +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" +msgstr "" + +#. Tag: para +#, no-c-format +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" +msgstr "" + +#. Tag: para +#, no-c-format +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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "enabled" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "If false, the operation is treated as if it does not exist. Allowed values: true, false" +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," +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "crm_attribute --type op_defaults --attr-name timeout --attr-value 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)." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "When Resources Take a Long Time to Start/Stop" +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." +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" +" </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." +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\"." +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." +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." +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" +" </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 disabled=\"true\" 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\" disabled=\"true\"/>\n" +" </operations>\n" +" <instance_attributes id=\"params-public-ip\">\n" +" <nvpair id=\"public-ip-addr\" name=\"ip\" value=\"1.2.3.4\"/>\n" +" </instance_attributes>\n" +" </primitive> " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "This can be achieved from the command-line by executing" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "cibadmin -M -X ‘<op id=\"public-ip-check\" disabled=\"true\"/>'" +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: programlisting +#, no-c-format +msgid "cibadmin -M -X ‘<op id=\"public-ip-check\" disabled=\"false\"/>'" +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Rules.pot b/doc/Pacemaker_Explained/pot/Ch-Rules.pot new file mode 100644 index 0000000000..97c97ba3ab --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Rules.pot @@ -0,0 +1,732 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "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 "Properties of a Rule" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Field" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "role Rule Property RulePropertiesrole role" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "scoreRule Property RulePropertiesscore score" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "score-attribute Rule Property RulePropertiesscore-attribute score-attribute" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "boolean-op Rule Property RulePropertiesboolean-op boolean-op" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "How to combine the result of multiple expression objects. Allowed values: and and or." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "NodeAttribute ExpressionsNode Attribute Expressions" +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: entry +#, no-c-format +msgid "value Expression Property Expression Propertiesvalue value" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "User supplied value for comparison" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "attribute Expression Property Expression Propertiesattribute attribute" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The node attribute to test" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "typeExpression Property Expression Propertiestype type" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Determines how the value(s) should be tested. Allowed values: string, integer, version" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "operation Expression Property Expression Propertiesoperation 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "gt - True if the node attribute's value 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "gte - True if the node attribute's value 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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "ne - True if the node attribute's value is not equal to value" +msgstr "" + +#. Tag: para +#, no-c-format +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" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Time Based Expressions ExpressionTime/Date Based Time/Date Based Expressions" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties of a Date Expression" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "start" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A date/time conforming to the ISO8601 specification." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "end" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A date/time conforming to the ISO8601 specification. Can be inferred by supplying a value for start and a duration." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "operation" +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" +msgstr "" + +#. Tag: para +#, no-c-format +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" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "date-spec - performs a cron-like comparison to the current date/time" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Because the comparisons (except for date_spec) include the time, the eq, neq, gte and lte operators have not been implemented." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Date Specifications Date Specifications" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Properties of a Date Spec" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "idDate Spec Property Date Spec Propertiesid id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "A unique name for the date" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "hours Date Spec Property Date Spec Propertieshours hours" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: 0-23" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "monthdays Date Spec Property Date Spec Propertiesmonthdays monthdays" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: 0-31 (depending on month and year)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "weekdays Date Spec Property Date Spec Propertiesweekdays weekdays" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: 1-7 (1=Monday, 7=Sunday)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "yeardays Date Spec Property Date Spec Propertiesyeardays yeardays" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: 1-366 (depending on the year)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "months Date Spec Property Date Spec Propertiesmonths months" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: 1-12" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "weeks Date Spec Property Date Spec Propertiesweeks weeks" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Allowed values: 1-53 (depending on weekyear)" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "years Date Spec Property Date Spec Propertiesyears years" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Year according the Gregorian calendar" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "weekyears Date Spec Property Date Spec Propertiesweekyears 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" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "moon Date Spec Property Date Spec Propertiesmoon moon" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Durations Expressions ExpressionsDurations Durations" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Sample Time Based Expressions" +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" +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" +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" +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 "NOTE: 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "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 "RuleDetermine Resource Location ResourceLocation, Determine by Rules Using Rules to Determine Resource Location" +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." +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:" +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)." +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:" +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" +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" +" 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." +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "RuleControlling Cluster Options Cluster OptionsControlled by Rules Using Rules to Control Cluster Options" +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." +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" +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." +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." +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." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Status.pot b/doc/Pacemaker_Explained/pot/Ch-Status.pot new file mode 100644 index 0000000000..a6ca585eb6 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Status.pot @@ -0,0 +1,534 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\n" +"Last-Translator: Automatically generated\n" +"Language-Team: None\n" +"MIME-Version: 1.0\n" +"Content-Type: application/x-publican; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#, no-c-format +msgid "Status - Here be dragons" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Most users never need to understand the contents of the status section and can be happy with the output from crm_mon. However for those with a curious inclination, this section attempts to provide an overview of its contents." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "NodeStatus Status of a Node Node Status" +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "A bare-bones status entry for a healthy node called 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Authoritative Sources for State Information" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Dataset" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Authoritative Source" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "node_state fields" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "crmd" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "transient_attributes tag" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "attrd" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "lrm tag" +msgstr "" + +#. Tag: entry +#, 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. 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: entry +#, no-c-format +msgid "idNode Status Field NodeStatus Fieldid id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Unique identifier for the node. Corosync based clusters use the uname of the machine, Heartbeat clusters use a human-readable (but annoying) UUID." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "uname Node Status Field NodeStatus Fielduname uname" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The node's machine name (output from uname -n)." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "ha Node Status Field NodeStatus Fieldha ha" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Flag specifying whether the cluster software is active on the node. Allowed values: active, dead." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "in_ccm Node Status Field NodeStatus Fieldin_ccm in_ccm" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Flag for cluster membership; allowed values: true, false." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "crmd Node Status Field NodeStatus Fieldcrmd crmd" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Flag: is the crmd process active on the node? One of online, offline." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "join Node Status Field NodeStatus Fieldjoin join" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Flag saying whether the node participates in hosting resources. Possible values: down, pending, member, banned." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "expected Node Status Field NodeStatus Fieldexpected expected" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Expected value for join." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "crm-debug-origin Node Status Field NodeStatus Fieldcrm-debug-origin crm-debug-origin" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Diagnostic indicator: the origin of the most recent change(s)." +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." +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." +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\"" +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\"\n" +" 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 @number . 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 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "A record of the apcstonith resource" +msgstr "" + +#. Tag: screen +#, no-c-format +msgid "<lrm_resource id=\"apcstonith\" type=\"apcmastersnmp\" class=\"stonith\">\n" +" " +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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Contents of an lrm_rsc_op job." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "idJob Field Job Fieldid id" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Identifier for the job constructed from the resource's id, operation and interval." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "call-id Job Field Job Fieldcall-id call-id" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "operation Job Field Job Fieldoperation operation" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The action the resource agent was invoked with." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "interval Job Field Job Fieldinterval interval" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "op-status Job Field Job Fieldop-status op-status" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "rc-code Job Field Job Fieldrc-code rc-code" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "last-run Job Field Job Fieldlast-run last-run" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Diagnostic indicator. Machine local date/time, in seconds since epoch, at which the job was executed." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "last-rc-change Job Field Job Fieldlast-rc-change last-rc-change" +msgstr "" + +#. Tag: entry +#, 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." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "exec-time Job Field Job Fieldexec-time exec-time" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Diagnostic indicator. Time, in milliseconds, that the job was running for." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "queue-time Job Field Job Fieldqueue-time queue-time" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Diagnostic indicator. Time, in seconds, that the job was queued for in the LRMd." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "crm_feature_set Job Field Job Fieldcrm_feature_set crm_feature_set" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "The version which this job description conforms to. Used when processing op-digest." +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "transition-key Job Field Job Fieldtransition-key transition-key" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "transition-magic Job Field Job Fieldtransition-magic transition-magic" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "op-digest Job Field Job Fieldop-digest op-digest" +msgstr "" + +#. Tag: entry +#, 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: entry +#, no-c-format +msgid "crm-debug-origin Job Field Job Fieldcrm-debug-origin crm-debug-origin" +msgstr "" + +#. Tag: entry +#, no-c-format +msgid "Diagnostic indicator. The origin of the current values." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Simple Example" +msgstr "" + +#. Tag: title +#, no-c-format +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. 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." +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). The third field of the transition-key contains a 7, this 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." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Complex Resource History Example" +msgstr "" + +#. Tag: title +#, no-c-format +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. 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. 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 new file mode 100644 index 0000000000..683c3948f2 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Stonith.pot @@ -0,0 +1,223 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "Protecting Your Data - STONITH" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Why You Need STONITH" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "STONITH is an acronym for Shoot-The-Other-Node-In-The-Head; its purpose is to protect your data from being corrupted by rogue nodes or concurrent access." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "When a node is unresponsive it might still access your data. The only way to be 100% sure that your data is safe, is to use STONITH, so we can be certain that the node is truly offline, before allowing the data to be accessed from another node." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "What STONITH Device Should You Use" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "It is crucial that the STONITH device can allow the cluster to differentiate between a node and a network failure." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The biggest mistake people make in choosing a STONITH device is to use a remote power switch (such as many on-board IPMI controllers) that shares power with the node it controls. In such cases, the cluster cannot be sure if the node is really offline, or active and suffering from a network fault." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Likewise, any device that relies on the machine being active (such as SSH-based \"devices\" used during testing) are inappropriate." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring STONITH" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Find the correct driver: stonith_admin --list-installed" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Since every device is different, the parameters needed to configure it will vary. To find out which parameters the device supports resp. needs, run:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "stonith_admin --metadata --agent type\n" +" " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The output should be XML formatted text containing additional parameter descriptions. We will endeavour to make the output more friendly in a later version." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Create a file called stonith.xml 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." +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: cibadmin -C -o resources --xml-file stonith.xml" +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." +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:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Obtaining a list of STONITH Parameters" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# stonith_admin --metadata -a fence_ipmilan\n" +"<?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.\n" +"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\n" +"increase wait after operation to 4 seconds (power_wait=4 / -T 4)</longdesc>\n" +"<parameters>\n" +" <parameter name=\"auth\" unique=\"1\">\n" +" <shortdesc lang=\"en\">IPMI Lan Auth type (md5, password, or none)</shortdesc>\n" +" <getopt mixed=\"-A\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"ipaddr\" unique=\"1\">\n" +" <shortdesc lang=\"en\">IPMI Lan IP to talk to</shortdesc>\n" +" <getopt mixed=\"-a\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"passwd\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Password to control power on IPMI device</shortdesc>\n" +" <getopt mixed=\"-p\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"passwd_script\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Script to retrieve password (if required)</shortdesc>\n" +" <getopt mixed=\"-S\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"lanplus\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Use Lanplus</shortdesc>\n" +" <getopt mixed=\"-P\" /> <content type=\"boolean\" /> </parameter>\n" +" <parameter name=\"login\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Username/Login to control IPMI device</shortdesc>\n" +" <getopt mixed=\"-l\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"action\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Operation to perform. Valid operations:\n" +" on, off, reboot, status, list, diag, monitor or metadata</shortdesc>\n" +" <getopt mixed=\"-o\" /> <content type=\"string\" default=\"reboot\"/> </parameter>\n" +" <parameter name=\"timeout\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Timeout (sec) for IPMI operation</shortdesc>\n" +" <getopt mixed=\"-t\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"cipher\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Ciphersuite to use (same as ipmitool -C parameter)</shortdesc>\n" +" <getopt mixed=\"-C\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"method\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Method to fence (onoff or cycle)</shortdesc>\n" +" <getopt mixed=\"-M\" /> <content type=\"string\" default=\"onoff\"/> </parameter>\n" +" <parameter name=\"power_wait\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Wait X seconds after on/off operation</shortdesc>\n" +" <getopt mixed=\"-T\" /> <content type=\"string\" default=\"2\"/> </parameter>\n" +" <parameter name=\"delay\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Wait X seconds before fencing is started</shortdesc>\n" +" <getopt mixed=\"-f\" /> <content type=\"string\" /> </parameter>\n" +" <parameter name=\"verbose\" unique=\"1\">\n" +" <shortdesc lang=\"en\">Verbose mode</shortdesc>\n" +" <getopt mixed=\"-v\" /> <content type=\"boolean\" /> </parameter>\n" +"</parameters>\n" +"<actions>\n" +" <action name=\"on\" /> <action name=\"off\" /> \n" +" <action name=\"reboot\" /> <action name=\"status\" /> \n" +" <action name=\"diag\" /> <action name=\"list\" /> \n" +" <action name=\"monitor\" /> <action name=\"metadata\" />\n" +"</actions>\n" +"</resource-agent>\n" +" " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "From this list we would create a STONITH resource fragment that might look like this:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Sample STONITH Resource" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid " <primitive id=\"ipmi\" class=\"stonith\" type=\"fence_ipmilan\">\n" +" <operations>\n" +" <op id=\"ipmi-mon-1\" name=\"monitor\" interval=\"2h\"/>\n" +" </operations>\n" +" <instance_attributes id=\"ipmi-parameters\">\n" +" <nvpair id=\"ipmi-attr-1\" name=\"pcmk_host_list\" value=\"node1 node2 node3 node4\"/>\n" +" <nvpair id=\"ipmi-attr-1\" name=\"ipaddr\" value=\"10.0.0.1\"/>\n" +" <nvpair id=\"ipmi-attr-1\" name=\"login\" value=\"testuser\"/>\n" +" <nvpair id=\"ipmi-attr-1\" name=\"passwd\" value=\"abc123\"/>\n" +" </instance_attributes>\n" +" </primitive> " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The monitor interval of two hours is explained by bugs in some IPMI implementations; see Monitoring the fencing devices." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot new file mode 100644 index 0000000000..e04a3e59e6 --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot @@ -0,0 +1,342 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 +#, no-c-format +msgid "Background" +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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To take these into account, Pacemaker allows you to specify the following configurations:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The capacity a certain node provides." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The capacity a certain resource requires." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "An overall strategy for placement of resources." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Utilization attributes" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "To configure the capacity 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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "First, specify the capacities the nodes provide:" +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 +#, no-c-format +msgid "Then, specify the capacities the resources require:" +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." +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." +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." +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." +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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Set placement-strategy with crm_attribute:" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "# crm_attribute --attr-name placement-strategy --attr-value balanced" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Now Pacemaker will ensure the load from your resources will be distributed evenly throughout the cluster - without the need for convoluted sets of colocation constraints." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Allocation Details" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Which node is preferred to be chosen to get consumed first on allocating resources?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The node that is most healthy (which has the highest node weight) gets consumed first." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If their weights are equal:" +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." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If placement-strategy=\"balanced\", the node that has more 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." +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:" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If nodeA has more free cpus, nodeB has more free memory, 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, nodeB has more free capacity." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Which resource is preferred to be chosen to get assigned first?" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The resource that has the highest priority 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)." +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." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If the scores above are equal, the first runnable resource listed in cib gets allocated first." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Limitations" +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\"." +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:" +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 +#, no-c-format +msgid "Strategies for Dealing with the Limitations" +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'." +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." +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." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot new file mode 100644 index 0000000000..45c890aaff --- /dev/null +++ b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot @@ -0,0 +1,59 @@ +# +# AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Project Documentation " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A comprehensive guide to cluster commands has been written by Novell" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Heartbeat configuration: " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Corosync Configuration: " +msgstr "" + diff --git a/doc/Clusters_from_Scratch/pot/Preface.pot b/doc/Pacemaker_Explained/pot/Preface.pot similarity index 79% copy from doc/Clusters_from_Scratch/pot/Preface.pot copy to doc/Pacemaker_Explained/pot/Preface.pot index edda6f88ed..bfa2bf3df5 100644 --- a/doc/Clusters_from_Scratch/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: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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/Pacemaker_Explained/pot/Revision_History.pot similarity index 55% copy from doc/Clusters_from_Scratch/pot/Revision_History.pot copy to doc/Pacemaker_Explained/pot/Revision_History.pot index 3bd4a37844..9d6e0db619 100644 --- a/doc/Clusters_from_Scratch/pot/Revision_History.pot +++ b/doc/Pacemaker_Explained/pot/Revision_History.pot @@ -1,34 +1,49 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2010-12-21T11:01:27\n" -"PO-Revision-Date: 2010-12-21T11:01:27\n" +"POT-Creation-Date: 2012-02-27T09:17:56\n" +"PO-Revision-Date: 2012-02-27T09:17:56\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 "" +