#

# AUTHOR <EMAIL@ADDRESS>, YEAR.

#

msgid ""

msgstr ""

"Project-Id-Version: 0\n"

"POT-Creation-Date: 2012-10-17T05:19:03\n"

"PO-Revision-Date: 2010-12-15 23:43+0800\n"

"Last-Translator: Charlie Chen <laneovcc@gmail.com>\n"

"Language-Team: None\n"

"Language: \n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

#. Tag: title

#, fuzzy, no-c-format

msgid "Pacemaker Tools"

msgstr "使用Pacemaker工具"

#. Tag: title

#, no-c-format

msgid "Using Pacemaker Tools"

msgstr "使用Pacemaker工具"

#. 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 "在万恶的旧社会，配置Pacemaker需要管理员具备读写XML的能力。 根据UNIX精神，也有许多不同的查询和配置集群的命令。"

#. Tag: para

#, no-c-format

msgid "All of that has been greatly simplified with the creation of unified command-line shells (and GUIs) that hide all the messy XML scaffolding."

msgstr ""

#. Tag: para

#, no-c-format

msgid "These shells take all the individual aspects required for managing and configuring a cluster, and packs them into one simple to use command line tool."

msgstr ""

#. Tag: para

#, no-c-format

msgid "They even allow you to queue up several changes at once and commit them atomically."

msgstr ""

#. Tag: para

#, no-c-format

msgid "There are currently two command-line shells that people use, <literal>pcs</literal> and <literal>crmsh</literal>. This edition of Clusters from Scratch is based on <literal>pcs</literal>. Start by taking some time to familiarize yourself with what it can do."

msgstr ""

#. Tag: para

#, no-c-format

msgid "The two shells share many concepts but the scope, layout and syntax does differ, so make sure you read the version of this guide that corresponds to the software installed on your system."

msgstr ""

#. Tag: para

#, no-c-format

msgid "Since <literal>pcs</literal> has the ability to manage all aspects of the cluster (both corosync and pacemaker), it requires a specific cluster stack to be in use, (corosync 2.0 with votequorum + Pacemaker version >= 1.8)."

msgstr ""

#. Tag: programlisting

#, no-c-format

msgid "# pcs"

msgstr ""

#. Tag: literallayout

#, no-c-format

msgid ""

"Control and configure pacemaker and corosync.\n"

"\n"

"Options:\n"

"    -h          Display usage and exit\n"

"    -f file     Perform actions on file instead of active CIB\n"

"\n"

"Commands:\n"

"    resource    Manage cluster resources\n"

"    cluster     Configure cluster options and nodes\n"

"    stonith     Configure fence devices\n"

"    property    Set pacemaker properties\n"

"    constraint  Set resource constraints\n"

"    status      View cluster status"

msgstr ""

#. Tag: para

#, no-c-format

msgid "As you can see, the different aspects of cluster management are broken up into categories: resource, cluster, stonith, property, constraint, and status. To discover the functionality available in each of these categories, one can issue the command <emphasis>pcs <category> help</emphasis>. Below is an example of all the options available under the status category."

msgstr ""

#. Tag: programlisting

#, no-c-format

msgid "# pcs status help"

msgstr ""

#. Tag: literallayout

#, no-c-format

msgid ""

"Usage: pcs status [commands]...\n"

"View current cluster and resource status\n"

"Commands:\n"

"    status\n"

"        View all information about the cluster and resources\n"

"\n"

"    status resources\n"

"        View current status of cluster resources\n"

"\n"

"    status groups\n"

"        View currently configured groups and their resources\n"

"\n"

"    status cluster\n"

"        View current cluster status\n"

"\n"

"    status corosync\n"

"        View current corosync status\n"

"\n"

"    status nodes [corosync]\n"

"        View current status of nodes from pacemaker, or if corosync is\n"

"        specified, print nodes currently configured in corosync\n"

"\n"

"    status actions\n"

"        View failed actions\n"

"\n"

"    status pcsd <node> ...\n"

"        Show the current status of pcsd on the specified nodes\n"

"\n"

"    status xml\n"

"        View xml version of status (output from crm_mon -r -1 -X)"

msgstr ""

#. Tag: para

#, fuzzy, no-c-format

msgid "Additionally, if you are interested in the Pacemaker version and supported cluster stack(s) available with your current Pacemaker installation, the pacemakerd --features option is available to you."

msgstr "此外，Pacemaker的版本和支持的stack(本文中是corosync)可以通过 --version选项看到"

#. Tag: programlisting

#, no-c-format

msgid "# pacemakerd --features"

msgstr ""

#. Tag: screen

#, no-c-format

msgid ""

"Pacemaker 1.1.8 (Build: 434edfa)\n"

" Supporting:  generated-manpages agent-manpages ascii-docs publican-docs ncurses gcov libqb-logging libqb-ipc lha-fencing upstart systemd  heartbeat corosync-native snmp"

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 "如果SNMP或者email选项没有出现在选项中，说明pacemaker编译的时候没有打开对他们的支持，你需要联系提供这个发行版本的人，或者自己编译。"

#~ 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 "自从Pacemaker 1.0，这一切都改变了，我们有了一个集成的脚本化的集群控制shell,它把麻烦的XML配置隐藏了起来。它甚至允许你一次做出许多修改并自动提交(并检测是否合法)。"

#~ msgid "Take some time to familiarize yourself with what it can do."

#~ msgstr "让我们花点时间熟悉一下它能做什么。"

#~ msgid ""

#~ "\n"

#~ "[root@pcmk-1 ~]# <userinput>crm --help</userinput>\n"

#~ "\n"

#~ "usage:\n"

#~ "    crm [-D display_type]\n"

#~ "    crm [-D display_type] args\n"

#~ "    crm [-D display_type] [-f file]\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"

#~ "\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"

#~ "Examples:\n"

#~ "\n"

#~ "    # crm -f stopapp2.cli\n"

#~ "    # crm < stopapp2.cli\n"

#~ "    # crm resource stop global_www\n"

#~ "    # crm status\n"

#~ msgstr ""

#~ "\n"

#~ "[root@pcmk-1 ~]# <userinput>crm --help</userinput>\n"

#~ "\n"

#~ "usage:\n"

#~ "    crm [-D display_type]\n"

#~ "    crm [-D display_type] args\n"

#~ "    crm [-D display_type] [-f file]\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"

#~ "\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"

#~ "Examples:\n"

#~ "\n"

#~ "    # crm -f stopapp2.cli\n"

#~ "    # crm < stopapp2.cli\n"

#~ "    # crm resource stop global_www\n"

#~ "    # crm status\n"

#~ 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 <command>--help</command> 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 "监控集群状态的主要命令是 crm_mon(跟crm status是一样的效果)。它可以运行在很多模式下并且有许多输出选项。如果要查看Pacemaker相应的工具，可以通过--help或者man pages来查看。这些输出都是靠命令来生成的，所以它总是会在各个节点和工具之间同步。"

#~ msgid ""

#~ "\n"

#~ "[root@pcmk-1 ~]# <userinput>crm_mon --version</userinput>\n"

#~ "crm_mon 1.0.5 for OpenAIS and Heartbeat (Build: 462f1569a43740667daf7b0f6b521742e9eb8fa7)\n"

#~ "\n"

#~ "Written by Andrew Beekhof\n"

#~ "[root@pcmk-1 ~]# <userinput>crm_mon --help</userinput>\n"

#~ "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"

#~ "\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"

#~ "\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"

#~ "\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"

#~ "\n"

#~ "Examples:\n"

#~ "\n"

#~ "Display the cluster´s status on the console with updates as they occur:\n"

#~ "        # crm_mon\n"

#~ "\n"

#~ "Display the cluster´s status on the console just once then exit:\n"

#~ "        # crm_mon\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"

#~ "\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"

#~ "\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"

#~ "\n"

#~ "Report bugs to pacemaker@oss.clusterlabs.org\n"

#~ msgstr ""

#~ "\n"

#~ "[root@pcmk-1 ~]# <userinput>crm_mon --version</userinput>\n"

#~ "crm_mon 1.0.5 for OpenAIS and Heartbeat (Build: 462f1569a43740667daf7b0f6b521742e9eb8fa7)\n"

#~ "\n"

#~ "Written by Andrew Beekhof\n"

#~ "[root@pcmk-1 ~]# <userinput>crm_mon --help</userinput>\n"

#~ "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"

#~ "\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"

#~ "\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"

#~ "\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"

#~ "\n"

#~ "Examples:\n"

#~ "\n"

#~ "Display the cluster´s status on the console with updates as they occur:\n"

#~ "        # crm_mon\n"

#~ "\n"

#~ "Display the cluster´s status on the console just once then exit:\n"

#~ "        # crm_mon\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"

#~ "\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"

#~ "\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"

#~ "\n"

#~ "Report bugs to pacemaker@oss.clusterlabs.org\n"