#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2018-05-14 18:03-0500\n"
"PO-Revision-Date: 2018-05-14 18:03-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#, no-c-format
msgid "Pacemaker Tools"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Simplify administration using a cluster shell"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the dark past, configuring Pacemaker required the administrator to read and write XML. In true UNIX style, there were also a number of different commands that specialized in different aspects of querying and updating the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "All of that has been greatly simplified with the creation of unified command-line shells (and GUIs) that hide all the messy XML scaffolding."
msgstr ""
#. Tag: para
#, no-c-format
msgid "These shells take all the individual aspects required for managing and configuring a cluster, and pack them into one simple-to-use command line tool."
msgstr ""
#. Tag: para
#, no-c-format
msgid "They even allow you to queue up several changes at once and commit them all at once."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Two popular command-line shells are <literal>pcs</literal> and <literal>crmsh</literal>. This edition of Clusters from Scratch is based on <literal>pcs</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The two shells share many concepts but the scope, layout and syntax does differ, so make sure you read the version of this guide that corresponds to the software installed on your system."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Explore pcs"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Start by taking some time to familiarize yourself with what <literal>pcs</literal> can do."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs\n"
"\n"
"Usage: pcs [-f file] [-h] [commands]...\n"
"Control and configure pacemaker and corosync.\n"
"\n"
"Options:\n"
" -h, --help Display usage and exit.\n"
" -f file Perform actions on file instead of active CIB.\n"
" --debug Print all network traffic and external commands run.\n"
" --version Print pcs version information.\n"
" --request-timeout Timeout for each outgoing request to another node in\n"
" seconds. Default is 60s.\n"
"\n"
"Commands:\n"
" cluster Configure cluster options and nodes.\n"
" resource Manage cluster resources.\n"
" stonith Manage fence devices.\n"
" constraint Manage resource constraints.\n"
" property Manage pacemaker properties.\n"
" acl Manage pacemaker access control lists.\n"
" qdevice Manage quorum device provider on the local host.\n"
" quorum Manage cluster quorum settings.\n"
" booth Manage booth (cluster ticket manager).\n"
" status View cluster status.\n"
" config View and manage cluster configuration.\n"
" pcsd Manage pcs daemon.\n"
" node Manage cluster nodes.\n"
" alert Manage pacemaker alerts."
msgstr ""
#. Tag: para
#, no-c-format
msgid "As you can see, the different aspects of cluster management are separated into categories. To discover the functionality available in each of these categories, one can issue the command <literal>pcs <replaceable>category</replaceable> help</literal>. Below is an example of all the options available under the status category."
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pcs status help\n"
"\n"
"Usage: pcs status [commands]...\n"
"View current cluster and resource status\n"
"Commands:\n"
" [status] [--full | --hide-inactive]\n"
" View all information about the cluster and resources (--full provides\n"
" more details, --hide-inactive hides inactive resources).\n"
"\n"
" resources [<resource id> | --full | --groups | --hide-inactive]\n"
" Show all currently configured resources or if a resource is specified\n"
" show the options for the configured resource. If --full is specified,\n"
" all configured resource options will be displayed. If --groups is\n"
" specified, only show groups (and their resources). If --hide-inactive\n"
" is specified, only show active resources.\n"
"\n"
" groups\n"
" View currently configured groups and their resources.\n"
"\n"
" cluster\n"
" View current cluster status.\n"
"\n"
" corosync\n"
" View current membership information as seen by corosync.\n"
"\n"
" quorum\n"
" View current quorum status.\n"
"\n"
" qdevice <device model> [--full] [<cluster name>]\n"
" Show runtime status of specified model of quorum device provider. Using\n"
" --full will give more detailed output. If <cluster name> is specified,\n"
" only information about the specified cluster will be displayed.\n"
"\n"
" nodes [corosync | both | config]\n"
" View current status of nodes from pacemaker. If 'corosync' is\n"
" specified, view current status of nodes from corosync instead. If\n"
" 'both' is specified, view current status of nodes from both corosync &\n"
" pacemaker. If 'config' is specified, print nodes from corosync &\n"
" pacemaker configuration.\n"
"\n"
" pcsd [<node>]...\n"
" Show current status of pcsd on nodes specified, or on all nodes\n"
" configured in the local cluster if no nodes are specified.\n"
"\n"
" xml\n"
" View xml version of status (output from crm_mon -r -1 -X)."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Additionally, if you are interested in the version and supported cluster stack(s) available with your Pacemaker installation, run:"
msgstr ""
#. Tag: screen
#, no-c-format
msgid "[root@pcmk-1 ~]# pacemakerd --features\n"
"Pacemaker 1.1.16-12.el7_4.5 (Build: 94ff4df)\n"
" Supporting v3.0.12: generated-manpages agent-manpages ncurses libqb-logging libqb-ipc systemd nagios corosync-native atomic-attrd acls"
msgstr ""