diff --git a/doc/Clusters_from_Scratch/pot/Author_Group.pot b/doc/Clusters_from_Scratch/pot/Author_Group.pot index 078e45daed..82963b7dd2 100644 --- a/doc/Clusters_from_Scratch/pot/Author_Group.pot +++ b/doc/Clusters_from_Scratch/pot/Author_Group.pot @@ -1,64 +1,64 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Primary author" msgstr "" #. Tag: firstname #, no-c-format msgid "Raoul" msgstr "" #. Tag: surname #, no-c-format msgid "Scarazzini" msgstr "" #. Tag: contrib #, no-c-format msgid "Italian translation" msgstr "" #. Tag: firstname #, no-c-format msgid "Dan" msgstr "" #. Tag: surname #, no-c-format msgid "Frîncu" msgstr "" #. Tag: contrib #, no-c-format msgid "Romanian translation" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Book_Info.pot b/doc/Clusters_from_Scratch/pot/Book_Info.pot index 2e5b57f4f5..059d4534e9 100644 --- a/doc/Clusters_from_Scratch/pot/Book_Info.pot +++ b/doc/Clusters_from_Scratch/pot/Book_Info.pot @@ -1,69 +1,69 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Clusters from Scratch" msgstr "" #. Tag: subtitle #, no-c-format msgid "Step-by-Step Instructions for Building Your First High-Availability Cluster" msgstr "" #. Tag: productname #, no-c-format msgid "Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "The purpose of this document is to provide a start-to-finish guide to building an example active/passive cluster with Pacemaker and show how it can be converted to an active/active one." msgstr "" #. Tag: para #, no-c-format msgid "The example cluster will use:" msgstr "" #. Tag: para #, no-c-format msgid "&DISTRO; &DISTRO_VERSION; as the host operating system" msgstr "" #. Tag: para #, no-c-format msgid "Corosync to provide messaging and membership services," msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker to perform resource management," msgstr "" #. Tag: para #, no-c-format msgid "DRBD as a cost-effective alternative to shared storage," msgstr "" #. Tag: para #, no-c-format msgid "GFS2 as the cluster filesystem (in active/active mode)" msgstr "" #. Tag: para #, no-c-format msgid "Given the graphical nature of the 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/Preface.pot b/doc/Clusters_from_Scratch/pot/Preface.pot index eb70fb6c89..f84c72b747 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: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Preface" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Revision_History.pot b/doc/Clusters_from_Scratch/pot/Revision_History.pot index a3dc415ba8..7f577ac31b 100644 --- a/doc/Clusters_from_Scratch/pot/Revision_History.pot +++ b/doc/Clusters_from_Scratch/pot/Revision_History.pot @@ -1,109 +1,109 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: member #, no-c-format msgid "Import from Pages.app" msgstr "" #. Tag: firstname #, no-c-format msgid "Raoul" msgstr "" #. Tag: surname #, no-c-format msgid "Scarazzini" msgstr "" #. Tag: member #, no-c-format msgid "Italian translation" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Fedora 13" msgstr "" #. Tag: member #, no-c-format msgid "Update the GFS2 section to use CMAN" msgstr "" #. Tag: member #, no-c-format msgid "Generate docbook content from asciidoc sources" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Fedora 17" msgstr "" #. Tag: firstname #, no-c-format msgid "David" msgstr "" #. Tag: surname #, no-c-format msgid "Vossel" msgstr "" #. Tag: member #, no-c-format msgid "Updated for pcs" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Fedora 21" msgstr "" #. Tag: member #, no-c-format msgid "Minor corrections, plus use include file for intro" msgstr "" #. Tag: member #, no-c-format msgid "Update for CentOS 7.1 and leaving firewalld/SELinux enabled" msgstr "" diff --git a/doc/Pacemaker_Development/pot/Author_Group.pot b/doc/Pacemaker_Development/pot/Author_Group.pot index 5ed5c168d1..4c66589225 100644 --- a/doc/Pacemaker_Development/pot/Author_Group.pot +++ b/doc/Pacemaker_Development/pot/Author_Group.pot @@ -1,44 +1,44 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Co-author" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" diff --git a/doc/Pacemaker_Development/pot/Book_Info.pot b/doc/Pacemaker_Development/pot/Book_Info.pot index d508f920ea..c994d01a2f 100644 --- a/doc/Pacemaker_Development/pot/Book_Info.pot +++ b/doc/Pacemaker_Development/pot/Book_Info.pot @@ -1,29 +1,29 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Pacemaker Development" msgstr "" #. Tag: subtitle #, no-c-format msgid "Working with the Pacemaker Code Base" msgstr "" #. Tag: para #, no-c-format msgid "This document has guidelines and tips for developers interested in editing Pacemaker source code and submitting changes for inclusion in the project." msgstr "" diff --git a/doc/Pacemaker_Development/pot/Ch-Coding.pot b/doc/Pacemaker_Development/pot/Ch-Coding.pot index ddd5d8e2dc..d1716d820e 100644 --- a/doc/Pacemaker_Development/pot/Ch-Coding.pot +++ b/doc/Pacemaker_Development/pot/Ch-Coding.pot @@ -1,276 +1,276 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "C Coding Guidelines" msgstr "" #. Tag: para #, no-c-format msgid "" msgstr "" #. Tag: title #, no-c-format msgid "C Boilerplate" msgstr "" #. Tag: para #, no-c-format msgid " Cboilerplate boilerplate licensingC boilerplate C boilerplate " msgstr "" #. Tag: para #, no-c-format msgid "Every C file should start like this:" msgstr "" #. Tag: programlisting #, no-c-format msgid "/*\n" " * Copyright (C) <YYYY[-YYYY]> Andrew Beekhof <andrew@beekhof.net>\n" " *\n" " * This source code is licensed under <LICENSE> WITHOUT ANY WARRANTY.\n" " */" msgstr "" #. Tag: para #, no-c-format msgid "<YYYY> is the year the code was originally created (it is the most important date for copyright purposes, as it establishes priority and the point from which expiration is calculated). If the code is modified in later years, add -YYYY with the most recent year of modification." msgstr "" #. Tag: para #, no-c-format msgid "<LICENSE> should follow the policy set forth in the COPYING file, generally one of \"GNU General Public License version 2 or later (GPLv2+)\" or \"GNU Lesser General Public License version 2.1 or later (LGPLv2.1+)\"." msgstr "" #. Tag: title #, no-c-format msgid "Formatting" msgstr "" #. Tag: title #, no-c-format msgid "Whitespace" msgstr "" #. Tag: para #, no-c-format msgid " Cwhitespace whitespace " msgstr "" #. Tag: para #, no-c-format msgid "Indentation must be 4 spaces, no tabs." msgstr "" #. Tag: para #, no-c-format msgid "Do not leave trailing whitespace." msgstr "" #. Tag: title #, no-c-format msgid "Line Length" msgstr "" #. Tag: para #, no-c-format msgid "Lines should be no longer than 80 characters unless limiting line length significantly impacts readability." msgstr "" #. Tag: title #, no-c-format msgid "Pointers" msgstr "" #. Tag: para #, no-c-format msgid " Cpointers pointers " msgstr "" #. Tag: para #, no-c-format msgid "The * goes by the variable name, not the type:" msgstr "" #. Tag: programlisting #, no-c-format msgid "char *foo;" msgstr "" #. Tag: para #, no-c-format msgid "Use a space before the * and after the closing parenthesis in a cast:" msgstr "" #. Tag: programlisting #, no-c-format msgid "char *foo = (char *) bar;" msgstr "" #. Tag: title #, no-c-format msgid "Functions" msgstr "" #. Tag: para #, no-c-format msgid " Cfunctions functions " msgstr "" #. Tag: para #, no-c-format msgid "In the function definition, put the return type on its own line, and place the opening brace by itself on a line:" msgstr "" #. Tag: programlisting #, no-c-format msgid "static int\n" "foo(void)\n" "{" msgstr "" #. Tag: para #, no-c-format msgid "For functions with enough arguments that they must break to the next line, align arguments with the first argument:" msgstr "" #. Tag: programlisting #, no-c-format msgid "static int\n" "function_name(int bar, const char *a, const char *b,\n" " const char *c, const char *d)\n" "{" msgstr "" #. Tag: para #, no-c-format msgid "If a function name gets really long, start the arguments on their own line with 8 spaces of indentation:" msgstr "" #. Tag: programlisting #, no-c-format msgid "static int\n" "really_really_long_function_name_this_is_getting_silly_now(\n" " int bar, const char *a, const char *b,\n" " const char *c, const char *d)\n" "{" msgstr "" #. Tag: title #, no-c-format msgid "Control Statements (if, else, while, for, switch)" msgstr "" #. Tag: para #, no-c-format msgid "The keyword is followed by one space, then left parenthesis without space, condition, right parenthesis, space, opening bracket on the same line. else and else if are on the same line with the ending brace and opening brace, separated by a space:" msgstr "" #. Tag: programlisting #, no-c-format msgid "if (condition1) {\n" " statement1;\n" "} else if (condition2) {\n" " statement2;\n" "} else {\n" " statement3;\n" "}" msgstr "" #. Tag: para #, no-c-format msgid "In a switch statement, case is indented one level, and the body of each case is indented by another level. The opening brace is on the same line as switch." msgstr "" #. Tag: programlisting #, no-c-format msgid "switch (expression) {\n" " case 0:\n" " command1;\n" " break;\n" " case 1:\n" " command2;\n" " break;\n" " default:\n" " command3;\n" "}" msgstr "" #. Tag: title #, no-c-format msgid "Operators" msgstr "" #. Tag: para #, no-c-format msgid " Coperators operators " msgstr "" #. Tag: para #, no-c-format msgid "Operators have spaces from both sides. Do not rely on operator precedence; use parentheses when mixing operators with different priority." msgstr "" #. Tag: para #, no-c-format msgid "No space is used after opening parenthesis and before closing parenthesis." msgstr "" #. Tag: programlisting #, no-c-format msgid "x = a + b - (c * d);" msgstr "" #. Tag: title #, no-c-format msgid "Naming Conventions" msgstr "" #. Tag: para #, no-c-format msgid " Cnaming naming " msgstr "" #. Tag: para #, no-c-format msgid "Any exposed symbols in libraries (non-static function names, type names, etc.) must begin with a prefix appropriate to the library, for example, crm_, pe_, st_, lrm_." msgstr "" #. Tag: title #, no-c-format msgid "vim Settings" msgstr "" #. Tag: para #, no-c-format msgid " vim " msgstr "" #. Tag: para #, no-c-format msgid "Developers who use vim to edit source code can add the following settings to their ~/.vimrc file to follow Pacemaker C coding guidelines:" msgstr "" #. Tag: screen #, no-c-format msgid "\" follow Pacemaker coding guidelines when editing C source code files\n" "filetype plugin indent on\n" "au FileType c setlocal expandtab tabstop=4 softtabstop=4 shiftwidth=4 textwidth=80\n" "autocmd BufNewFile,BufRead *.h set filetype=c\n" "let c_space_errors = 1" msgstr "" diff --git a/doc/Pacemaker_Development/pot/Ch-FAQ.pot b/doc/Pacemaker_Development/pot/Ch-FAQ.pot index 97aa3ec375..fda0b2f70b 100644 --- a/doc/Pacemaker_Development/pot/Ch-FAQ.pot +++ b/doc/Pacemaker_Development/pot/Ch-FAQ.pot @@ -1,139 +1,139 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Frequently Asked Questions" msgstr "" #. Tag: para #, no-c-format msgid "Who is this document intended for?" msgstr "" #. Tag: para #, no-c-format msgid "Anyone who wishes to read and/or edit the Pacemaker source code. Casual contributors should feel free to read just this FAQ, and consult other sections as needed." msgstr "" #. Tag: para #, no-c-format msgid "Where is the source code for Pacemaker?" msgstr "" #. Tag: para #, no-c-format msgid " downloads source code gitGitHub GitHub The source code for Pacemaker is kept on GitHub, as are all software projects under the ClusterLabs umbrella. Pacemaker uses Git for source code management. If you are a Git newbie, the gittutorial(7) man page is an excellent starting point. If you’re familiar with using Git from the command line, you can create a local copy of the Pacemaker source code with: git clone https://github.com/ClusterLabs/pacemaker.git pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "What are the different Git branches and repositories used for?" msgstr "" #. Tag: para #, no-c-format msgid " branches " msgstr "" #. Tag: para #, no-c-format msgid "The master branch is the primary branch used for development." msgstr "" #. Tag: para #, no-c-format msgid "The 1.1 branch contains the latest official release, and normally does not receive any changes. During the release cycle, it will contain release candidates for the next official release, and will receive only bug fixes." msgstr "" #. Tag: para #, no-c-format msgid "The 1.0 repository is a frozen snapshot of the 1.0 release series, and is no longer developed." msgstr "" #. Tag: para #, no-c-format msgid "Messages will be posted to the developers@clusterlabs.org mailing list during the release cycle, with instructions about which branches to use when submitting requests." msgstr "" #. Tag: para #, no-c-format msgid "How do I build from the source code?" msgstr "" #. Tag: para #, no-c-format msgid "See INSTALL.md in the main checkout directory." msgstr "" #. Tag: para #, no-c-format msgid "What coding style should I follow?" msgstr "" #. Tag: para #, no-c-format msgid "You’ll be mostly fine if you simply follow the example of existing code. When unsure, see the relevant section of this document for language-specific recommendations. Pacemaker has grown and evolved organically over many years, so you will see much code that doesn’t conform to the current guidelines. We discourage making changes solely to bring code into conformance, as any change requires developer time for review and opens the possibility of adding bugs. However, new code should follow the guidelines, and it is fine to bring lines of older code into conformance when modifying that code for other reasons." msgstr "" #. Tag: para #, no-c-format msgid "How should I format my Git commit messages?" msgstr "" #. Tag: para #, no-c-format msgid " gitcommit messages commit messages See existing examples in the git log. The first line should look like change-type: affected-code: explanation where change-type can be Fix or Bug for most bug fixes, Feature for new features, Log for changes to log messages or handling, Doc for changes to documentation or comments, or Test for changes in CTS and regression tests. You will sometimes see Low, Med (or Mid) and High used instead for bug fixes, to indicate the severity. The important thing is that only commits with Feature, Fix, Bug, or High will automatically be included in the change log for the next release. The affected-code is the name of the component(s) being changed, for example, crmd or libcrmcommon (it’s more free-form, so don’t sweat getting it exact). The explanation briefly describes the change. The git project recommends the entire summary line stay under 50 characters, but more is fine if needed for clarity. Except for the most simple and obvious of changes, the summary should be followed by a blank line and then a longer explanation of why the change was made." msgstr "" #. Tag: para #, no-c-format msgid "How can I test my changes?" msgstr "" #. Tag: para #, no-c-format msgid "Most importantly, Pacemaker has regression tests for most major components; these will automatically be run for any pull requests submitted through GitHub. Additionally, Pacemaker’s Cluster Test Suite (CTS) can be used to set up a test cluster and run a wide variety of complex tests. This document will have more detail on testing in the future." msgstr "" #. Tag: para #, no-c-format msgid "What is Pacemaker’s license?" msgstr "" #. Tag: para #, no-c-format msgid " licensing Except where noted otherwise in the file itself, the source code for all Pacemaker programs is licensed under version 2 or later of the GNU General Public License (GPLv2+), its headers and libraries under version 2.1 or later of the less restrictive GNU Lesser General Public License (LGPLv2.1+), its documentation under version 4.0 or later of the Creative Commons Attribution-ShareAlike International Public License (CC-BY-SA), and its init scripts under the Revised BSD license. If you find any deviations from this policy, or wish to inquire about alternate licensing arrangements, please e-mail andrew@beekhof.net. Licensing issues are also discussed on the ClusterLabs wiki." msgstr "" #. Tag: para #, no-c-format msgid "How can I contribute my changes to the project?" msgstr "" #. Tag: para #, no-c-format msgid "Contributions of bug fixes or new features are very much appreciated! Patches can be submitted as pull requests via GitHub (the preferred method, due to its excellent features), or e-mailed to the developers@clusterlabs.org mailing list as an attachment in a format Git can import." msgstr "" #. Tag: para #, no-c-format msgid "What if I still have questions?" msgstr "" #. Tag: para #, no-c-format msgid " mailing lists Ask on the developers@clusterlabs.org mailing list for development-related questions, or on the users@clusterlabs.org mailing list for general questions about using Pacemaker. Developers often also hang out on freenode’s #clusterlabs IRC channel." msgstr "" diff --git a/doc/Pacemaker_Development/pot/Ch-Python.pot b/doc/Pacemaker_Development/pot/Ch-Python.pot index 54b56171d9..6d40d89b9b 100644 --- a/doc/Pacemaker_Development/pot/Ch-Python.pot +++ b/doc/Pacemaker_Development/pot/Ch-Python.pot @@ -1,297 +1,297 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Python Coding Guidelines" msgstr "" #. Tag: para #, no-c-format msgid "" msgstr "" #. Tag: title #, no-c-format msgid "Python Boilerplate" msgstr "" #. Tag: para #, no-c-format msgid " Pythonboilerplate boilerplate licensingPython boilerplate Python boilerplate " msgstr "" #. Tag: para #, no-c-format msgid "Every Python file should start like this:" msgstr "" #. Tag: programlisting #, no-c-format msgid "[<SHEBANG>]\n" "\"\"\" <BRIEF-DESCRIPTION>\n" "\"\"\"\n" "\n" "# Pacemaker targets compatibility with Python 2.6+ and 3.2+\n" "from __future__ import print_function, unicode_literals, absolute_import, division\n" "\n" "__copyright__ = \"Copyright (C) <YYYY[-YYYY]> Andrew Beekhof <andrew@beekhof.net>\"\n" "__license__ = \"<LICENSE> WITHOUT ANY WARRANTY\"" msgstr "" #. Tag: para #, no-c-format msgid "If the file is meant to be directly executed, the first line (<SHEBANG>) should be #!/usr/bin/python. If it is meant to be imported, omit this line." msgstr "" #. Tag: para #, no-c-format msgid "<BRIEF-DESCRIPTION> is obviously a brief description of the file’s purpose. The string may contain any other information typically used in a Python file docstring." msgstr "" #. Tag: para #, no-c-format msgid "The import statement is discussed further in ." msgstr "" #. Tag: para #, no-c-format msgid "<YYYY> is the year the code was originally created (it is the most important date for copyright purposes, as it establishes priority and the point from which expiration is calculated). If the code is modified in later years, add -YYYY with the most recent year of modification." msgstr "" #. Tag: para #, no-c-format msgid "<LICENSE> should follow the policy set forth in the COPYING file, generally one of \"GNU General Public License version 2 or later (GPLv2+)\" or \"GNU Lesser General Public License version 2.1 or later (LGPLv2.1+)\"." msgstr "" #. Tag: title #, no-c-format msgid "Python Compatibility" msgstr "" #. Tag: para #, no-c-format msgid " Python2 2 Python3 3 Pythonversions versions " msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker targets compatibility with Python 2.6 and later, and Python 3.2 and later. These versions have added features to be more compatible with each other, allowing us to support both the 2 and 3 series with the same code. It is a good idea to test any changes with both Python 2 and 3." msgstr "" #. Tag: title #, no-c-format msgid "Python Future Imports" msgstr "" #. Tag: para #, no-c-format msgid "The future imports used in mean:" msgstr "" #. Tag: para #, no-c-format msgid "All print statements must use parentheses, and printing without a newline is accomplished with the end=' ' parameter rather than a trailing comma." msgstr "" #. Tag: para #, no-c-format msgid "All string literals will be treated as Unicode (the u prefix is unnecessary, and must not be used, because it is not available in Python 3.2)." msgstr "" #. Tag: para #, no-c-format msgid "Local modules must be imported using from . import (rather than just import). To import one item from a local module, use from .modulename import (rather than from modulename import)." msgstr "" #. Tag: para #, no-c-format msgid "Division using / will always return a floating-point result (use // if you want the integer floor instead)." msgstr "" #. Tag: title #, no-c-format msgid "Other Python Compatibility Requirements" msgstr "" #. Tag: para #, no-c-format msgid "When specifying an exception variable, always use as instead of a comma (e.g. except Exception as e or except (TypeError, IOError) as e). Use e.args to access the error arguments (instead of iterating over or subscripting e)." msgstr "" #. Tag: para #, no-c-format msgid "Use in (not has_key()) to determine if a dictionary has a particular key." msgstr "" #. Tag: para #, no-c-format msgid "Always use the I/O functions from the io module rather than the native I/O functions (e.g. io.open() rather than open())." msgstr "" #. Tag: para #, no-c-format msgid "When opening a file, always use the t (text) or b (binary) mode flag." msgstr "" #. Tag: para #, no-c-format msgid "When creating classes, always specify a parent class to ensure that it is a \"new-style\" class (e.g. class Foo(object): rather than class Foo:)" msgstr "" #. Tag: para #, no-c-format msgid "Be aware of the bytes type added in Python 3. Many places where strings are used in Python 2 use bytes or bytearrays in Python 3 (for example, the pipes used with subprocess.Popen()). Code should handle both possibilities." msgstr "" #. Tag: para #, no-c-format msgid "Be aware that the items(), keys(), and values() methods of dictionaries return lists in Python 2 and views in Python 3. In many case, no special handling is required, but if the code needs to use list methods on the result, cast the result to list first." msgstr "" #. Tag: para #, no-c-format msgid "Do not name variables with or as." msgstr "" #. Tag: para #, no-c-format msgid "Do not raise or catch strings as exceptions (e.g. raise \"Bad thing\")." msgstr "" #. Tag: para #, no-c-format msgid "Do not use the cmp parameter of sorting functions (use key instead, if needed) or the __cmp__() method of classes (implement rich comparison methods such as __lt__() instead, if needed)." msgstr "" #. Tag: para #, no-c-format msgid "Do not use the buffer type." msgstr "" #. Tag: para #, no-c-format msgid "Do not use features not available in all targeted Python versions. Common examples include:" msgstr "" #. Tag: para #, no-c-format msgid "The argparse, html, ipaddress, sysconfig, and UserDict modules" msgstr "" #. Tag: para #, no-c-format msgid "The collections.OrderedDict class" msgstr "" #. Tag: para #, no-c-format msgid "The subprocess.run() function" msgstr "" #. Tag: para #, no-c-format msgid "The subprocess.DEVNULL constant" msgstr "" #. Tag: para #, no-c-format msgid "subprocess module-specific exceptions" msgstr "" #. Tag: para #, no-c-format msgid "Set literals ({1, 2, 3})" msgstr "" #. Tag: title #, no-c-format msgid "Python Usages to Avoid" msgstr "" #. Tag: para #, no-c-format msgid "Avoid the following if possible, otherwise research the compatibility issues involved (hacky workarounds are often available):" msgstr "" #. Tag: para #, no-c-format msgid "long integers" msgstr "" #. Tag: para #, no-c-format msgid "octal integer literals" msgstr "" #. Tag: para #, no-c-format msgid "mixed binary and string data in one data file or variable" msgstr "" #. Tag: para #, no-c-format msgid "metaclasses" msgstr "" #. Tag: para #, no-c-format msgid "locale.strcoll and locale.strxfrm" msgstr "" #. Tag: para #, no-c-format msgid "the configparser and ConfigParser modules" msgstr "" #. Tag: para #, no-c-format msgid "importing compatibility modules such as six (so we don’t have to add them to Pacemaker’s dependencies)" msgstr "" #. Tag: title #, no-c-format msgid "Formatting Python Code" msgstr "" #. Tag: para #, no-c-format msgid " Pythonformatting formatting " msgstr "" #. Tag: para #, no-c-format msgid "Indentation must be 4 spaces, no tabs." msgstr "" #. Tag: para #, no-c-format msgid "Do not leave trailing whitespace." msgstr "" #. Tag: para #, no-c-format msgid "Lines should be no longer than 80 characters unless limiting line length significantly impacts readability. For Python, this limitation is flexible since breaking a line often impacts readability, but definitely keep it under 120 characters." msgstr "" #. Tag: para #, no-c-format msgid "Where not conflicting with this style guide, it is recommended (but not required) to follow PEP 8." msgstr "" #. Tag: para #, no-c-format msgid "It is recommended (but not required) to format Python code such that pylint --disable=line-too-long,too-many-lines,too-many-instance-attributes,too-many-arguments,too-many-statements produces minimal complaints (even better if you don’t need to disable all those checks)." msgstr "" diff --git a/doc/Pacemaker_Development/pot/Revision_History.pot b/doc/Pacemaker_Development/pot/Revision_History.pot index 0a9aa32f12..66ca5f9801 100644 --- a/doc/Pacemaker_Development/pot/Revision_History.pot +++ b/doc/Pacemaker_Development/pot/Revision_History.pot @@ -1,39 +1,39 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Convert coding guidelines and developer FAQ to Publican document" msgstr "" #. Tag: member #, no-c-format msgid "Add Python coding guidelines, and more about licensing" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ap-Debug.pot b/doc/Pacemaker_Explained/pot/Ap-Debug.pot index c906a1c151..79bdc2205d 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Debug.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Debug.pot @@ -1,189 +1,189 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Debugging Cluster Startup" msgstr "" #. Tag: title #, no-c-format msgid "Corosync" msgstr "" #. Tag: title #, no-c-format msgid "Prerequisites" msgstr "" #. Tag: title #, no-c-format msgid "Minimum logging configuration" msgstr "" #. Tag: programlisting #, no-c-format msgid "\n" " # /etc/init.d/openais start\n" " \n" " \n" " logging {\n" " to_syslog: yes\n" " syslog_facility: daemon\n" " }\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "Whatever other logging you have, these two lines are required for Pacemaker clusters" msgstr "" #. Tag: title #, no-c-format msgid "Confirm Corosync Started" msgstr "" #. Tag: title #, no-c-format msgid "Expected output when starting openais" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # /etc/init.d/openais start\n" " \n" " \n" " Starting Corosync daemon (aisexec): starting... rc=0: OK\n" " \n" " " msgstr "" #. Tag: title #, no-c-format msgid "Expected log messages - startup" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep -e \"openais.*network interface\" -e \"AIS Executive Service\" /var/log/messages\n" " \n" " \n" " Aug 27 16:23:37 test1 openais[26337]: [MAIN ] AIS Executive Service RELEASE 'subrev 1152 version 0.80'\n" " Aug 27 16:23:38 test1 openais[26337]: [MAIN ] AIS Executive Service: started and ready to provide service.\n" " Aug 27 16:23:38 test1 openais[26337]: [TOTEM] The network interface [192.168.9.41] is now up.\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "The versions may differ, but you should see Corosync indicate it started and sucessfully attached to the machine's network interface" msgstr "" #. Tag: title #, no-c-format msgid "Expected log messages - membership" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep CLM /var/log/messages\n" " \n" " \n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41)\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41)\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] got nodejoin message 192.168.9.41\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "The exact messages will differ, but you should see a new membership formed with the real IP address of your node" msgstr "" #. Tag: title #, no-c-format msgid "Checking Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Now that we have confirmed that Corosync is functional we can check the rest of the stack." msgstr "" #. Tag: title #, no-c-format msgid "Expected Pacemaker startup logging for Corosync" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep pcmk_plugin_init /var/log/messages\n" " \n" " \n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: CRM: Initialized\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] Logging: Initialized pcmk_plugin_init\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Service: 9\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Local hostname: test1\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "If you don't see these messages, or some like them, there is likely a problem finding or loading the pacemaker plugin." msgstr "" #. Tag: title #, no-c-format msgid "Expected process listing on a 64-bit machine" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # ps axf\n" " \n" " \n" " 3718 ? Ssl 0:05 /usr/sbin/aisexec\n" " 3723 ? SLs 0:00 \\_ /usr/lib64/heartbeat/stonithd\n" " 3724 ? S 0:05 \\_ /usr/lib64/heartbeat/cib\n" " 3725 ? S 0:21 \\_ /usr/lib64/heartbeat/lrmd\n" " 3726 ? S 0:01 \\_ /usr/lib64/heartbeat/attrd\n" " 3727 ? S 0:00 \\_ /usr/lib64/heartbeat/pengine\n" " 3728 ? S 0:01 \\_ /usr/lib64/heartbeat/crmd\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "On 32-bit systems the exact path may differ, but all the above processes should be listed." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Author_Group.pot b/doc/Pacemaker_Explained/pot/Author_Group.pot index 269473e450..22b49850dc 100644 --- a/doc/Pacemaker_Explained/pot/Author_Group.pot +++ b/doc/Pacemaker_Explained/pot/Author_Group.pot @@ -1,139 +1,139 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Primary author" msgstr "" #. Tag: firstname #, no-c-format msgid "Dan" msgstr "" #. Tag: surname #, no-c-format msgid "Frîncu" msgstr "" #. Tag: contrib #, no-c-format msgid "Romanian translation" msgstr "" #. Tag: firstname #, no-c-format msgid "Philipp" msgstr "" #. Tag: surname #, no-c-format msgid "Marek" msgstr "" #. Tag: orgname #, no-c-format msgid "LINBit" msgstr "" #. Tag: contrib #, no-c-format msgid "Style and formatting updates. Indexing." msgstr "" #. Tag: firstname #, no-c-format msgid "Tanja" msgstr "" #. Tag: surname #, no-c-format msgid "Roth" msgstr "" #. Tag: orgname #, no-c-format msgid "SUSE" msgstr "" #. Tag: contrib #, no-c-format msgid "Utilization chapter" msgstr "" #. Tag: contrib #, no-c-format msgid "Resource Templates chapter" msgstr "" #. Tag: contrib #, no-c-format msgid "Multi-Site Clusters chapter" msgstr "" #. Tag: firstname #, no-c-format msgid "Lars" msgstr "" #. Tag: surname #, no-c-format msgid "Marowsky-Bree" msgstr "" #. Tag: firstname #, no-c-format msgid "Yan" msgstr "" #. Tag: surname #, no-c-format msgid "Gao" msgstr "" #. Tag: firstname #, no-c-format msgid "Thomas" msgstr "" #. Tag: surname #, no-c-format msgid "Schraitle" msgstr "" #. Tag: firstname #, no-c-format msgid "Dejan" msgstr "" #. Tag: surname #, no-c-format msgid "Muhamedagic" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Book_Info.pot b/doc/Pacemaker_Explained/pot/Book_Info.pot index fcd9d454d2..775016e5af 100644 --- a/doc/Pacemaker_Explained/pot/Book_Info.pot +++ b/doc/Pacemaker_Explained/pot/Book_Info.pot @@ -1,34 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Configuration Explained" msgstr "" #. Tag: subtitle #, no-c-format msgid "An A-Z guide to Pacemaker's Configuration Options" msgstr "" #. Tag: productname #, no-c-format msgid "Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this, it will focus exclusively on the XML syntax used to configure Pacemaker's Cluster Information Base (CIB)." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Alerts.pot b/doc/Pacemaker_Explained/pot/Ch-Alerts.pot index dc9d827330..3a363f258c 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Alerts.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Alerts.pot @@ -1,486 +1,578 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Alerts" msgstr "" #. Tag: para #, no-c-format msgid " ResourceAlerts Alerts " msgstr "" #. Tag: para #, no-c-format -msgid "Alerts may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.)." +msgid "Alerts (available since Pacemaker 1.1.15) may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.)." msgstr "" #. Tag: title #, no-c-format msgid "Alert Agents" msgstr "" #. Tag: para #, no-c-format msgid "As with resource agents, the cluster calls an external program (an alert agent) to handle alerts. The cluster passes information about the event to the agent via environment variables. Agents can do anything desired with this information (send an e-mail, log to a file, update a monitoring system, etc.)." msgstr "" #. Tag: title #, no-c-format msgid "Simple alert configuration" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\" />\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the cluster will call my-script.sh for each event." msgstr "" #. Tag: para #, no-c-format msgid "Multiple alert agents may be configured; the cluster will call all of them for each event." msgstr "" #. Tag: para #, no-c-format msgid "Alert agents will be called only on cluster nodes. They will be called for events involving Pacemaker Remote nodes, but they will never be called on those nodes." msgstr "" #. Tag: title #, no-c-format msgid "Alert Recipients" msgstr "" #. Tag: para #, no-c-format msgid "Usually alerts are directed towards a recipient. Thus each alert may be additionally configured with one or more recipients. The cluster will call the agent separately for each recipient." msgstr "" #. Tag: title #, no-c-format msgid "Alert configuration with recipient" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" " <recipient id=\"my-alert-recipient\" value=\"some-address\"/>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: para #, no-c-format msgid "In the above example, the cluster will call my-script.sh for each event, passing the recipient some-address as an environment variable." msgstr "" #. Tag: para #, no-c-format msgid "The recipient may be anything the alert agent can recognize — an IP address, an e-mail address, a file name, whatever the particular agent supports." msgstr "" #. Tag: title #, no-c-format msgid "Alert Meta-Attributes" msgstr "" #. Tag: para #, no-c-format msgid "As with resource agents, meta-attributes can be configured for alert agents to affect how Pacemaker calls them." msgstr "" #. Tag: title #, no-c-format msgid "Meta-Attributes of an Alert" msgstr "" #. Tag: entry #, no-c-format msgid "Meta-Attribute" msgstr "" #. Tag: entry #, no-c-format msgid "Default" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "timestamp-format" msgstr "" #. Tag: para #, no-c-format msgid "%H:%M:%S.%06N" msgstr "" #. Tag: para #, no-c-format msgid "Format the cluster will use when sending the event’s timestamp to the agent. This is a string as used with the date(1) command. AlertOptiontimestamp-format Optiontimestamp-format timestamp-format " msgstr "" #. Tag: para #, no-c-format msgid "timeout" msgstr "" #. Tag: para #, no-c-format msgid "30s" msgstr "" #. Tag: para #, no-c-format msgid "If the alert agent does not complete within this amount of time, it will be terminated. AlertOptiontimeout Optiontimeout timeout " msgstr "" #. Tag: para #, no-c-format msgid "Meta-attributes can be configured per alert agent and/or per recipient." msgstr "" #. Tag: title #, no-c-format msgid "Alert configuration with meta-attributes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" " <meta_attributes id=\"my-alert-attributes\">\n" " <nvpair id=\"my-alert-attributes-timeout\" name=\"timeout\"\n" " value=\"15s\"/>\n" " </meta_attributes>\n" " <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\">\n" " <meta_attributes id=\"my-alert-recipient1-attributes\">\n" " <nvpair id=\"my-alert-recipient1-timestamp-format\"\n" " name=\"timestamp-format\" value=\"%D %H:%M\"/>\n" " </meta_attributes>\n" " </recipient>\n" " <recipient id=\"my-alert-recipient2\" value=\"otheruser@example.com\">\n" " <meta_attributes id=\"my-alert-recipient2-attributes\">\n" " <nvpair id=\"my-alert-recipient2-timestamp-format\"\n" " name=\"timestamp-format\" value=\"%c\"/>\n" " </meta_attributes>\n" " </recipient>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: para #, no-c-format msgid "In the above example, the my-script.sh will get called twice for each event, with each call using a 15-second timeout. One call will be passed the recipient someuser@example.com and a timestamp in the format %D %H:%M, while the other call will be passed the recipient otheruser@example.com and a timestamp in the format %c." msgstr "" #. Tag: title #, no-c-format msgid "Alert Instance Attributes" msgstr "" #. Tag: para #, no-c-format msgid "As with resource agents, agent-specific configuration values may be configured as instance attributes. These will be passed to the agent as additional environment variables. The number, names and allowed values of these instance attributes are completely up to the particular agent." msgstr "" #. Tag: title #, no-c-format msgid "Alert configuration with instance attributes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" " <meta_attributes id=\"my-alert-attributes\">\n" " <nvpair id=\"my-alert-attributes-timeout\" name=\"timeout\"\n" " value=\"15s\"/>\n" " </meta_attributes>\n" " <instance_attributes id=\"my-alert-options\">\n" " <nvpair id=\"my-alert-options-debug\" name=\"debug\" value=\"false\"/>\n" " </instance_attributes>\n" " <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" +#. Tag: title +#, no-c-format +msgid "Alert Filters" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Coming in 1.1.18" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "By default, an alert agent will be called for node events, fencing events, and resource events. An agent may choose to ignore certain types of events, but there is still the overhead of calling it for those events. To eliminate that overhead, you may select which types of events the agent should receive." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Alert configuration to receive only node events and fencing events" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<configuration>\n" +" <alerts>\n" +" <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" +" <select>\n" +" <select_nodes />\n" +" <select_fencing />\n" +" </select>\n" +" <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/>\n" +" </alert>\n" +" </alerts>\n" +"</configuration>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The possible options within <select> are <select_nodes>, <select_fencing>, <select_resources>, and <select_attributes>." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "With <select_attributes> (the only event type not enabled by default), the agent will receive alerts when a node attribute changes. If you wish the agent to be called only when certain attributes change, you can configure that as well." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Alert configuration to be called when certain node attributes change" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<configuration>\n" +" <alerts>\n" +" <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" +" <select>\n" +" <select_attributes>\n" +" <attribute id=\"alert-standby\" name=\"standby\" />\n" +" <attribute id=\"alert-shutdown\" name=\"shutdown\" />\n" +" </select_attributes>\n" +" </select>\n" +" <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/>\n" +" </alert>\n" +" </alerts>\n" +"</configuration>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Node attribute alerts are currently considered experimental. Alerts may be limited to attributes set via attrd_updater, and agents may be called multiple times with the same attribute value." +msgstr "" + #. Tag: title #, no-c-format msgid "Using the Sample Alert Agents" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker provides several sample alert agents, installed in /usr/share/pacemaker/alerts by default." msgstr "" #. Tag: para #, no-c-format msgid "While these sample scripts may be copied and used as-is, they are provided mainly as templates to be edited to suit your purposes. See their source code for the full set of instance attributes they support." msgstr "" #. Tag: title #, no-c-format msgid "Sending cluster events as SNMP traps" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"snmp_alert\" path=\"/path/to/alert_snmp.sh\">\n" " <instance_attributes id=\"config_for_alert_snmp\">\n" " <nvpair id=\"trap_node_states\" name=\"trap_node_states\" value=\"all\"/>\n" " </instance_attributes>\n" " <meta_attributes id=\"config_for_timestamp\">\n" " <nvpair id=\"ts_fmt\" name=\"timestamp-format\"\n" " value=\"%Y-%m-%d,%H:%M:%S.%01N\"/>\n" " </meta_attributes>\n" " <recipient id=\"snmp_destination\" value=\"192.168.1.2\"/>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: title #, no-c-format msgid "Sending cluster events as e-mails" msgstr "" #. Tag: programlisting #, no-c-format msgid " <configuration>\n" " <alerts>\n" " <alert id=\"smtp_alert\" path=\"/path/to/alert_smtp.sh\">\n" " <instance_attributes id=\"config_for_alert_smtp\">\n" " <nvpair id=\"email_sender\" name=\"email_sender\"\n" " value=\"donotreply@example.com\"/>\n" " </instance_attributes>\n" " <recipient id=\"smtp_destination\" value=\"admin@example.com\"/>\n" " </alert>\n" " </alerts>\n" " </configuration>" msgstr "" #. Tag: title #, no-c-format msgid "Writing an Alert Agent" msgstr "" #. Tag: title #, no-c-format msgid "Environment variables passed to alert agents" msgstr "" #. Tag: entry #, no-c-format msgid "Environment Variable" msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_kind" msgstr "" #. Tag: para #, no-c-format -msgid "The type of alert (node, fencing, or resource) Environment VariableCRM_alert_kind CRM_alert_kind kind " +msgid "The type of alert (node, fencing, resource, or attribute) Environment VariableCRM_alert_kind CRM_alert_kind kind " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_version" msgstr "" #. Tag: para #, no-c-format msgid "The version of Pacemaker sending the alert Environment VariableCRM_alert_version CRM_alert_version version " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_recipient" msgstr "" #. Tag: para #, no-c-format msgid "The configured recipient Environment VariableCRM_alert_recipient CRM_alert_recipient recipient " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_node_sequence" msgstr "" #. Tag: para #, no-c-format msgid "A sequence number increased whenever an alert is being issued on the local node, which can be used to reference the order in which alerts have been issued by Pacemaker. An alert for an event that happened later in time reliably has a higher sequence number than alerts for earlier events. Be aware that this number has no cluster-wide meaning. Environment VariableCRM_alert_node_sequence CRM_alert_node_sequence sequence " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_timestamp" msgstr "" #. Tag: para #, no-c-format msgid "A timestamp created prior to executing the agent, in the format specified by the timestamp-format meta-attribute. This allows the agent to have a reliable, high-precision time of when the event occurred, regardless of when the agent itself was invoked (which could potentially be delayed due to system load, etc.). Environment VariableCRM_alert_timestamp CRM_alert_timestamp timestamp " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_node" msgstr "" #. Tag: para #, no-c-format msgid "Name of affected node Environment VariableCRM_alert_node CRM_alert_node node " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_desc" msgstr "" #. Tag: para #, no-c-format msgid "Detail about event. For node alerts, this is the node’s current state (member or lost). For fencing alerts, this is a summary of the requested fencing operation, including origin, target, and fencing operation error code, if any. For resource alerts, this is a readable string equivalent of CRM_alert_status. Environment VariableCRM_alert_desc CRM_alert_desc desc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_nodeid" msgstr "" #. Tag: para #, no-c-format msgid "ID of node whose status changed (provided with node alerts only) Environment VariableCRM_alert_nodeid CRM_alert_nodeid nodeid " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_task" msgstr "" #. Tag: para #, no-c-format msgid "The requested fencing or resource operation (provided with fencing and resource alerts only) Environment VariableCRM_alert_task CRM_alert_task task " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_rc" msgstr "" #. Tag: para #, no-c-format msgid "The numerical return code of the fencing or resource operation (provided with fencing and resource alerts only) Environment VariableCRM_alert_rc CRM_alert_rc rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_rsc" msgstr "" #. Tag: para #, no-c-format msgid "The name of the affected resource (resource alerts only) Environment VariableCRM_alert_rsc CRM_alert_rsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_interval" msgstr "" #. Tag: para #, no-c-format msgid "The interval of the resource operation (resource alerts only) Environment VariableCRM_alert_interval CRM_alert_interval interval " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_target_rc" msgstr "" #. Tag: para #, no-c-format msgid "The expected numerical return code of the operation (resource alerts only) Environment VariableCRM_alert_target_rc CRM_alert_target_rc target_rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_status" msgstr "" #. Tag: para #, no-c-format msgid "A numerical code used by Pacemaker to represent the operation result (resource alerts only) Environment VariableCRM_alert_status CRM_alert_status status " msgstr "" +#. Tag: para +#, no-c-format +msgid "CRM_alert_attribute_name" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The name of the node attribute that changed (attribute alerts only) Environment VariableCRM_alert_attribute_name CRM_alert_attribute_name attribute_name " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_alert_attribute_value" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The new value of the node attribute that changed (attribute alerts only) Environment VariableCRM_alert_attribute_value CRM_alert_attribute_value attribute_value " +msgstr "" + #. Tag: para #, no-c-format msgid "Special concerns when writing alert agents:" msgstr "" #. Tag: para #, no-c-format msgid "Alert agents may be called with no recipient (if none is configured), so the agent must be able to handle this situation, even if it only exits in that case. (Users may modify the configuration in stages, and add a recipient later.)" msgstr "" #. Tag: para #, no-c-format msgid "If more than one recipient is configured for an alert, the alert agent will be called once per recipient. If an agent is not able to run concurrently, it should be configured with only a single recipient. The agent is free, however, to interpret the recipient as a list." msgstr "" #. Tag: para #, no-c-format msgid "When a cluster event occurs, all alerts are fired off at the same time as separate processes. Depending on how many alerts and recipients are configured, and on what is done within the alert agents, a significant load burst may occur. The agent could be written to take this into consideration, for example by queueing resource-intensive actions into some other instance, instead of directly executing them." msgstr "" #. Tag: para #, no-c-format msgid "Alert agents are run as the hacluster user, which has a minimal set of permissions. If an agent requires additional privileges, it is recommended to configure sudo to allow the agent to run the necessary commands as another user with the appropriate privileges." msgstr "" #. Tag: para #, no-c-format msgid "As always, take care to validate and sanitize user-configured parameters, such as CRM_alert_timestamp (whose content is specified by the user-configured timestamp-format), CRM_alert_recipient, and all instance attributes. Mostly this is needed simply to protect against configuration errors, but if some user can modify the CIB without having hacluster-level access to the cluster nodes, it is a potential security concern as well, to avoid the possibility of code injection." msgstr "" #. Tag: para #, no-c-format msgid "The alerts interface is designed to be backward compatible with the external scripts interface used by the ocf:pacemaker:ClusterMon resource, which is now deprecated. To preserve this compatibility, the environment variables passed to alert agents are available prepended with CRM_notify_ as well as CRM_alert_. One break in compatibility is that ClusterMon ran external scripts as the root user, while alert agents are run as the hacluster user." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot index 78f9f9a3ee..83a796e634 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot @@ -1,458 +1,458 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Multi-Site Clusters and Tickets" msgstr "" #. Tag: para #, no-c-format msgid "Apart from local clusters, Pacemaker also supports multi-site clusters. That means you can have multiple, geographically dispersed sites, each with a local cluster. Failover between these clusters can be coordinated manually by the administrator, or automatically by a higher-level entity called a Cluster Ticket Registry (CTR)." msgstr "" #. Tag: title #, no-c-format msgid "Challenges for Multi-Site Clusters" msgstr "" #. Tag: para #, no-c-format msgid "Typically, multi-site environments are too far apart to support synchronous communication and data replication between the sites. That leads to significant challenges:" msgstr "" #. Tag: para #, no-c-format msgid "How do we make sure that a cluster site is up and running?" msgstr "" #. Tag: para #, no-c-format msgid "How do we make sure that resources are only started once?" msgstr "" #. Tag: para #, no-c-format msgid "How do we make sure that quorum can be reached between the different sites and a split-brain scenario avoided?" msgstr "" #. Tag: para #, no-c-format msgid "How do we manage failover between sites?" msgstr "" #. Tag: para #, no-c-format msgid "How do we deal with high latency in case of resources that need to be stopped?" msgstr "" #. Tag: para #, no-c-format msgid "In the following sections, learn how to meet these challenges." msgstr "" #. Tag: title #, no-c-format msgid "Conceptual Overview" msgstr "" #. Tag: para #, no-c-format msgid "Multi-site clusters can be considered as “overlay” clusters where each cluster site corresponds to a cluster node in a traditional cluster. The overlay cluster can be managed by a CTR in order to guarantee that any cluster resource will be active on no more than one cluster site. This is achieved by using tickets that are treated as failover domain between cluster sites, in case a site should be down." msgstr "" #. Tag: para #, no-c-format msgid "The following sections explain the individual components and mechanisms that were introduced for multi-site clusters in more detail." msgstr "" #. Tag: title #, no-c-format msgid "Ticket" msgstr "" #. Tag: para #, no-c-format msgid "Tickets are, essentially, cluster-wide attributes. A ticket grants the right to run certain resources on a specific cluster site. Resources can be bound to a certain ticket by rsc_ticket constraints. Only if the ticket is available at a site can the respective resources be started there. Vice versa, if the ticket is revoked, the resources depending on that ticket must be stopped." msgstr "" #. Tag: para #, no-c-format msgid "The ticket thus is similar to a site quorum, i.e. the permission to manage/own resources associated with that site. (One can also think of the current have-quorum flag as a special, cluster-wide ticket that is granted in case of node majority.)" msgstr "" #. Tag: para #, no-c-format msgid "Tickets can be granted and revoked either manually by administrators (which could be the default for classic enterprise clusters), or via the automated CTR mechanism described below." msgstr "" #. Tag: para #, no-c-format msgid "A ticket can only be owned by one site at a time. Initially, none of the sites has a ticket. Each ticket must be granted once by the cluster administrator." msgstr "" #. Tag: para #, no-c-format msgid "The presence or absence of tickets for a site is stored in the CIB as a cluster status. With regards to a certain ticket, there are only two states for a site: true (the site has the ticket) or false (the site does not have the ticket). The absence of a certain ticket (during the initial state of the multi-site cluster) is the same as the value false." msgstr "" #. Tag: title #, no-c-format msgid "Dead Man Dependency" msgstr "" #. Tag: para #, no-c-format msgid "A site can only activate resources safely if it can be sure that the other site has deactivated them. However after a ticket is revoked, it can take a long time until all resources depending on that ticket are stopped \"cleanly\", especially in case of cascaded resources. To cut that process short, the concept of a Dead Man Dependency was introduced." msgstr "" #. Tag: para #, no-c-format msgid "If a dead man dependency is in force, if a ticket is revoked from a site, the nodes that are hosting dependent resources are fenced. This considerably speeds up the recovery process of the cluster and makes sure that resources can be migrated more quickly." msgstr "" #. Tag: para #, no-c-format msgid "This can be configured by specifying a loss-policy=\"fence\" in rsc_ticket constraints." msgstr "" #. Tag: title #, no-c-format msgid "Cluster Ticket Registry" msgstr "" #. Tag: para #, no-c-format msgid "A CTR is a coordinated group of network daemons that automatically handles granting, revoking, and timing out tickets (instead of the administrator revoking the ticket somewhere, waiting for everything to stop, and then granting it on the desired site)." msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker does not implement its own CTR, but interoperates with external software designed for that purpose (similar to how resource and fencing agents are not directly part of pacemaker)." msgstr "" #. Tag: para #, no-c-format msgid "Participating clusters run the CTR daemons, which connect to each other, exchange information about their connectivity, and vote on which sites gets which tickets." msgstr "" #. Tag: para #, no-c-format msgid "A ticket is granted to a site only once the CTR is sure that the ticket has been relinquished by the previous owner, implemented via a timer in most scenarios. If a site loses connection to its peers, its tickets time out and recovery occurs. After the connection timeout plus the recovery timeout has passed, the other sites are allowed to re-acquire the ticket and start the resources again." msgstr "" #. Tag: para #, no-c-format msgid "This can also be thought of as a \"quorum server\", except that it is not a single quorum ticket, but several." msgstr "" #. Tag: title #, no-c-format msgid "Configuration Replication" msgstr "" #. Tag: para #, no-c-format msgid "As usual, the CIB is synchronized within each cluster, but it is not synchronized across cluster sites of a multi-site cluster. You have to configure the resources that will be highly available across the multi-site cluster for every site accordingly." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Ticket Dependencies" msgstr "" #. Tag: para #, no-c-format msgid "The rsc_ticket constraint lets you specify the resources depending on a certain ticket. Together with the constraint, you can set a loss-policy that defines what should happen to the respective resources if the ticket is revoked." msgstr "" #. Tag: para #, no-c-format msgid "The attribute loss-policy can have the following values:" msgstr "" #. Tag: para #, no-c-format msgid "fence: Fence the nodes that are running the relevant resources." msgstr "" #. Tag: para #, no-c-format msgid "stop: Stop the relevant resources." msgstr "" #. Tag: para #, no-c-format msgid "freeze: Do nothing to the relevant resources." msgstr "" #. Tag: para #, no-c-format msgid "demote: Demote relevant resources that are running in master mode to slave mode." msgstr "" #. Tag: title #, no-c-format msgid "Constraint that fences node if ticketA is revoked" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" ticket=\"ticketA\" loss-policy=\"fence\"/>" msgstr "" #. Tag: para #, no-c-format msgid "The example above creates a constraint with the ID rsc1-req-ticketA. It defines that the resource rsc1 depends on ticketA and that the node running the resource should be fenced if ticketA is revoked." msgstr "" #. Tag: para #, no-c-format msgid "If resource rsc1 were a multi-state resource (i.e. it could run in master or slave mode), you might want to configure that only master mode depends on ticketA. With the following configuration, rsc1 will be demoted to slave mode if ticketA is revoked:" msgstr "" #. Tag: title #, no-c-format msgid "Constraint that demotes rsc1 if ticketA is revoked" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" rsc-role=\"Master\" ticket=\"ticketA\" loss-policy=\"demote\"/>" msgstr "" #. Tag: para #, no-c-format msgid "You can create multiple rsc_ticket constraints to let multiple resources depend on the same ticket. However, rsc_ticket also supports resource sets (see ), so one can easily list all the resources in one rsc_ticket constraint instead." msgstr "" #. Tag: title #, no-c-format msgid "Ticket constraint for multiple resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_ticket id=\"resources-dep-ticketA\" ticket=\"ticketA\" loss-policy=\"fence\">\n" " <resource_set id=\"resources-dep-ticketA-0\" role=\"Started\">\n" " <resource_ref id=\"rsc1\"/>\n" " <resource_ref id=\"group1\"/>\n" " <resource_ref id=\"clone1\"/>\n" " </resource_set>\n" " <resource_set id=\"resources-dep-ticketA-1\" role=\"Master\">\n" " <resource_ref id=\"ms1\"/>\n" " </resource_set>\n" "</rsc_ticket>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, there are two resource sets, so we can list resources with different roles in a single rsc_ticket constraint. There’s no dependency between the two resource sets, and there’s no dependency among the resources within a resource set. Each of the resources just depends on ticketA." msgstr "" #. Tag: para #, no-c-format msgid "Referencing resource templates in rsc_ticket constraints, and even referencing them within resource sets, is also supported." msgstr "" #. Tag: para #, no-c-format msgid "If you want other resources to depend on further tickets, create as many constraints as necessary with rsc_ticket." msgstr "" #. Tag: title #, no-c-format msgid "Managing Multi-Site Clusters" msgstr "" #. Tag: title #, no-c-format msgid "Granting and Revoking Tickets Manually" msgstr "" #. Tag: para #, no-c-format msgid "You can grant tickets to sites or revoke them from sites manually. If you want to re-distribute a ticket, you should wait for the dependent resources to stop cleanly at the previous site before you grant the ticket to the new site." msgstr "" #. Tag: para #, no-c-format msgid "Use the crm_ticket command line tool to grant and revoke tickets." msgstr "" #. Tag: para #, no-c-format msgid "To grant a ticket to this site:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --grant" msgstr "" #. Tag: para #, no-c-format msgid "To revoke a ticket from this site:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --revoke" msgstr "" #. Tag: para #, no-c-format msgid "If you are managing tickets manually, use the crm_ticket command with great care, because it cannot check whether the same ticket is already granted elsewhere." msgstr "" #. Tag: title #, no-c-format msgid "Granting and Revoking Tickets via a Cluster Ticket Registry" msgstr "" #. Tag: para #, no-c-format msgid "We will use Booth here as an example of software that can be used with pacemaker as a Cluster Ticket Registry. Booth implements the Raft algorithm to guarantee the distributed consensus among different cluster sites, and manages the ticket distribution (and thus the failover process between sites)." msgstr "" #. Tag: para #, no-c-format msgid "Each of the participating clusters and arbitrators runs the Booth daemon boothd." msgstr "" #. Tag: para #, no-c-format msgid "An arbitrator is the multi-site equivalent of a quorum-only node in a local cluster. If you have a setup with an even number of sites, you need an additional instance to reach consensus about decisions such as failover of resources across sites. In this case, add one or more arbitrators running at additional sites. Arbitrators are single machines that run a booth instance in a special mode. An arbitrator is especially important for a two-site scenario, otherwise there is no way for one site to distinguish between a network failure between it and the other site, and a failure of the other site." msgstr "" #. Tag: para #, no-c-format msgid "The most common multi-site scenario is probably a multi-site cluster with two sites and a single arbitrator on a third site. However, technically, there are no limitations with regards to the number of sites and the number of arbitrators involved." msgstr "" #. Tag: para #, no-c-format msgid "Boothd at each site connects to its peers running at the other sites and exchanges connectivity details. Once a ticket is granted to a site, the booth mechanism will manage the ticket automatically: If the site which holds the ticket is out of service, the booth daemons will vote which of the other sites will get the ticket. To protect against brief connection failures, sites that lose the vote (either explicitly or implicitly by being disconnected from the voting body) need to relinquish the ticket after a time-out. Thus, it is made sure that a ticket will only be re-distributed after it has been relinquished by the previous site. The resources that depend on that ticket will fail over to the new site holding the ticket. The nodes that have run the resources before will be treated according to the loss-policy you set within the rsc_ticket constraint." msgstr "" #. Tag: para #, no-c-format msgid "Before the booth can manage a certain ticket within the multi-site cluster, you initially need to grant it to a site manually via the booth command-line tool. After you have initially granted a ticket to a site, boothd will take over and manage the ticket automatically." msgstr "" #. Tag: para #, no-c-format msgid "The booth command-line tool can be used to grant, list, or revoke tickets and can be run on any machine where boothd is running. If you are managing tickets via Booth, use only booth for manual intervention, not crm_ticket. That ensures the same ticket will only be owned by one cluster site at a time." msgstr "" #. Tag: title #, no-c-format msgid "Booth Requirements" msgstr "" #. Tag: para #, no-c-format msgid "All clusters that will be part of the multi-site cluster must be based on Pacemaker." msgstr "" #. Tag: para #, no-c-format msgid "Booth must be installed on all cluster nodes and on all arbitrators that will be part of the multi-site cluster." msgstr "" #. Tag: para #, no-c-format msgid "Nodes belonging to the same cluster site should be synchronized via NTP. However, time synchronization is not required between the individual cluster sites." msgstr "" #. Tag: title #, no-c-format msgid "General Management of Tickets" msgstr "" #. Tag: para #, no-c-format msgid "Display the information of tickets:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --info" msgstr "" #. Tag: para #, no-c-format msgid "Or you can monitor them with:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_mon --tickets" msgstr "" #. Tag: para #, no-c-format msgid "Display the rsc_ticket constraints that apply to a ticket:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --constraints" msgstr "" #. Tag: para #, no-c-format msgid "When you want to do maintenance or manual switch-over of a ticket, revoking the ticket would trigger the loss policies. If loss-policy=\"fence\", the dependent resources could not be gracefully stopped/demoted, and other unrelated resources could even be affected." msgstr "" #. Tag: para #, no-c-format msgid "The proper way is making the ticket standby first with:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --standby" msgstr "" #. Tag: para #, no-c-format msgid "Then the dependent resources will be stopped or demoted gracefully without triggering the loss policies." msgstr "" #. Tag: para #, no-c-format msgid "If you have finished the maintenance and want to activate the ticket again, you can run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --activate" msgstr "" #. Tag: title #, no-c-format msgid "For more information" msgstr "" #. Tag: para #, no-c-format msgid "SUSE’s Geo Clustering quick start" msgstr "" #. Tag: para #, no-c-format msgid "Booth" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Notifications.pot b/doc/Pacemaker_Explained/pot/Ch-Notifications.pot index 8bf03de422..47164a713a 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Notifications.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Notifications.pot @@ -1,233 +1,233 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Receiving Notification for Cluster Events" msgstr "" #. Tag: para #, no-c-format msgid " ResourceNotification Notification " msgstr "" #. Tag: para #, no-c-format msgid "A Pacemaker cluster is an event-driven system. In this context, an event might be a resource failure or a configuration change, among others." msgstr "" #. Tag: para #, no-c-format msgid "The ocf:pacemaker:ClusterMon resource can monitor the cluster status and trigger alerts on each cluster event. This resource runs crm_mon in the background at regular (configurable) intervals and uses crm_mon capabilities to trigger emails (SMTP), SNMP traps or external programs (via the extra_options parameter)." msgstr "" #. Tag: para #, no-c-format msgid "Depending on your system settings and compilation settings, SNMP or email alerts might be unavailable. Check the output of crm_mon --help to see whether these options are available to you. In any case, executing an external agent will always be available, and you can use this agent to send emails, SNMP traps or whatever action you develop." msgstr "" #. Tag: title #, no-c-format msgid "Configuring SNMP Notifications" msgstr "" #. Tag: para #, no-c-format msgid " ResourceNotificationSNMP NotificationSNMP SNMP " msgstr "" #. Tag: para #, no-c-format msgid "Requires an IP to send SNMP traps to, and an SNMP community string. The Pacemaker MIB is provided with the source, and is typically installed in /usr/share/snmp/mibs/PCMK-MIB.txt." msgstr "" #. Tag: para #, no-c-format msgid "This example uses snmphost.example.com as the SNMP IP and public as the community string:" msgstr "" #. Tag: title #, no-c-format msgid "Configuring ClusterMon to send SNMP traps" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"ClusterMon-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterMon-SNMP\" provider=\"pacemaker\" type=\"ClusterMon\">\n" " <instance_attributes id=\"ClusterMon-instance_attributes\">\n" " <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-S snmphost.example.com -C public\"/>\n" " </instance_attributes>\n" " </primitive>\n" "</clone>" msgstr "" #. Tag: title #, no-c-format msgid "Configuring Email Notifications" msgstr "" #. Tag: para #, no-c-format msgid " ResourceNotificationSMTP NotificationSMTP SMTP " msgstr "" #. Tag: para #, no-c-format msgid "Requires the recipient e-mail address. You can also optionally configure the sender e-mail address, the hostname of the SMTP relay, and a prefix string for the subject line." msgstr "" #. Tag: title #, no-c-format msgid "Configuring ClusterMon to send email alerts" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"ClusterMon-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterMon-SMTP\" provider=\"pacemaker\" type=\"ClusterMon\">\n" " <instance_attributes id=\"ClusterMon-instance_attributes\">\n" " <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-T pacemaker@example.com -F pacemaker@node2.example.com -P PACEMAKER -H mail.example.com\"/>\n" " </instance_attributes>\n" " </primitive>\n" "</clone>" msgstr "" #. Tag: title #, no-c-format msgid "Configuring Notifications via External-Agent" msgstr "" #. Tag: para #, no-c-format msgid "Requires a program (external-agent) to run when resource operations take place, and an external-recipient (IP address, email address, URI). When triggered, the external-agent is fed with dynamically filled environment variables describing precisely the cluster event that occurred. By making smart usage of these variables in your external-agent code, you can trigger any action." msgstr "" #. Tag: title #, no-c-format msgid "Configuring ClusterMon to execute an external-agent" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"ClusterMon-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterMon\" provider=\"pacemaker\" type=\"ClusterMon\">\n" " <instance_attributes id=\"ClusterMon-instance_attributes\">\n" " <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-E /usr/local/bin/example.sh -e 192.168.12.1\"/>\n" " </instance_attributes>\n" " </primitive>\n" "</clone>" msgstr "" #. Tag: title #, no-c-format msgid "Environment Variables Passed to the External Agent" msgstr "" #. Tag: entry #, no-c-format msgid "Environment Variable" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_recipient" msgstr "" #. Tag: para #, no-c-format msgid "The static external-recipient from the resource definition. Environment VariableCRM_notify_recipient CRM_notify_recipient " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_node" msgstr "" #. Tag: para #, no-c-format msgid "The node on which the status change happened. Environment VariableCRM_notify_node CRM_notify_node " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_rsc" msgstr "" #. Tag: para #, no-c-format msgid "The name of the resource that changed the status. Environment VariableCRM_notify_rsc CRM_notify_rsc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_task" msgstr "" #. Tag: para #, no-c-format msgid "The operation that caused the status change. Environment VariableCRM_notify_task CRM_notify_task " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_desc" msgstr "" #. Tag: para #, no-c-format msgid "The textual output relevant error code of the operation (if any) that caused the status change. Environment VariableCRM_notify_desc CRM_notify_desc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_rc" msgstr "" #. Tag: para #, no-c-format msgid "The return code of the operation. Environment VariableCRM_notify_rc CRM_notify_rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_target_rc" msgstr "" #. Tag: para #, no-c-format msgid "The expected return code of the operation. Environment VariableCRM_notify_target_rc CRM_notify_target_rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_status" msgstr "" #. Tag: para #, no-c-format msgid "The numerical representation of the status of the operation. Environment VariableCRM_notify_target_rc CRM_notify_target_rc " msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot b/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot index ddd7fc9845..5e7dc30c2b 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot @@ -1,317 +1,317 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Resource Templates" msgstr "" #. Tag: para #, no-c-format msgid "If you want to create lots of resources with similar configurations, defining a resource template simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Resources with Templates" msgstr "" #. Tag: para #, no-c-format msgid "The primitives referencing the template will inherit all meta-attributes, instance attributes, utilization attributes and operations defined in the template. And you can define specific attributes and operations for any of the primitives. If any of these are defined in both the template and the primitive, the values defined in the primitive will take precedence over the ones defined in the template." msgstr "" #. Tag: para #, no-c-format msgid "Hence, resource templates help to reduce the amount of configuration work. If any changes are needed, they can be done to the template definition and will take effect globally in all resource definitions referencing that template." msgstr "" #. Tag: para #, no-c-format msgid "Resource templates have a syntax similar to that of primitives." msgstr "" #. Tag: title #, no-c-format msgid "Resource template for a migratable Xen virtual machine" msgstr "" #. Tag: programlisting #, no-c-format msgid "<template id=\"vm-template\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" "</template>" msgstr "" #. Tag: para #, no-c-format msgid "Once you define a resource template, you can use it in primitives by specifying the template property." msgstr "" #. Tag: title #, no-c-format msgid "Xen primitive resource using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" template=\"vm-template\">\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm1 will inherit everything from vm-template. For example, the equivalent of the above two examples would be:" msgstr "" #. Tag: title #, no-c-format msgid "Equivalent Xen primitive resource not using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "If you want to overwrite some attributes or operations, add them to the particular primitive’s definition." msgstr "" #. Tag: title #, no-c-format msgid "Xen resource overriding template values" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm2\" template=\"vm-template\">\n" " <meta_attributes id=\"vm2-meta_attributes\">\n" " <nvpair id=\"vm2-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"false\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm2-utilization\">\n" " <nvpair id=\"vm2-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" " <instance_attributes id=\"vm2-instance_attributes\">\n" " <nvpair id=\"vm2-instance_attributes-name\" name=\"name\" value=\"vm2\"/>\n" " <nvpair id=\"vm2-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm2\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"vm2-monitor-30s\" interval=\"30s\" name=\"monitor\" timeout=\"120s\"/>\n" " <op id=\"vm2-stop-0\" interval=\"0\" name=\"stop\" timeout=\"60s\"/>\n" " </operations>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm2 has special attribute values. Its monitor operation has a longer timeout and interval, and the primitive has an additional stop operation." msgstr "" #. Tag: para #, no-c-format msgid "To see the resulting definition of a resource, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml --resource vm2" msgstr "" #. Tag: para #, no-c-format msgid "To see the raw definition of a resource in the CIB, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml-raw --resource vm2" msgstr "" #. Tag: title #, no-c-format msgid "Referencing Templates in Constraints" msgstr "" #. Tag: para #, no-c-format msgid "A resource template can be referenced in the following types of constraints:" msgstr "" #. Tag: para #, no-c-format msgid "order constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "colocation constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "rsc_ticket constraints (for multi-site clusters as described in )" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates referenced in constraints stand for all primitives which are derived from that template. This means, the constraint applies to all primitive resources referencing the resource template. Referencing resource templates in constraints is an alternative to resource sets and can simplify the cluster configuration considerably." msgstr "" #. Tag: para #, no-c-format msgid "For example, given the example templates earlier in this section:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-template-colo-base-rsc\" rsc=\"vm-template\" rsc-role=\"Started\" with-rsc=\"base-rsc\" score=\"INFINITY\"/>" msgstr "" #. Tag: para #, no-c-format msgid "would colocate all VMs with base-rsc and is the equivalent of the following constraint configuration:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-colo-base-rsc\" score=\"INFINITY\">\n" " <resource_set id=\"vm-colo-base-rsc-0\" sequential=\"false\" role=\"Started\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"vm-colo-base-rsc-1\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" "</rsc_colocation>" msgstr "" #. Tag: para #, no-c-format msgid "In a colocation constraint, only one template may be referenced from either rsc or with-rsc; the other reference must be a regular resource." msgstr "" #. Tag: title #, no-c-format msgid "Referencing Resource Templates in Sequential Resource Sets" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates can also be referenced in resource sets." msgstr "" #. Tag: para #, no-c-format msgid "For example:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm-template\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: para #, no-c-format msgid "is the equivalent of the following constraint configuration:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: title #, no-c-format msgid "Referencing Resource Templates in Parallel Resource Sets" msgstr "" #. Tag: para #, no-c-format msgid "If the resources referencing the template can run in parallel:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm-template\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot b/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot similarity index 60% copy from doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot copy to doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot index ddd7fc9845..93e060a84e 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot @@ -1,317 +1,505 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format -msgid "Resource Templates" +msgid "Reusing Parts of the Configuration" msgstr "" #. Tag: para #, no-c-format -msgid "If you want to create lots of resources with similar configurations, defining a resource template simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints." +msgid "Pacemaker provides multiple ways to simplify the configuration XML by reusing parts of it in multiple places." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Besides simplifying the XML, this also allows you to manipulate multiple configuration elements with a single reference." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Reusing Resource Definitions" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If you want to create lots of resources with similar configurations, defining a resource template simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Resources with Templates" msgstr "" #. Tag: para #, no-c-format msgid "The primitives referencing the template will inherit all meta-attributes, instance attributes, utilization attributes and operations defined in the template. And you can define specific attributes and operations for any of the primitives. If any of these are defined in both the template and the primitive, the values defined in the primitive will take precedence over the ones defined in the template." msgstr "" #. Tag: para #, no-c-format msgid "Hence, resource templates help to reduce the amount of configuration work. If any changes are needed, they can be done to the template definition and will take effect globally in all resource definitions referencing that template." msgstr "" #. Tag: para #, no-c-format msgid "Resource templates have a syntax similar to that of primitives." msgstr "" #. Tag: title #, no-c-format msgid "Resource template for a migratable Xen virtual machine" msgstr "" #. Tag: programlisting #, no-c-format msgid "<template id=\"vm-template\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" "</template>" msgstr "" #. Tag: para #, no-c-format msgid "Once you define a resource template, you can use it in primitives by specifying the template property." msgstr "" #. Tag: title #, no-c-format msgid "Xen primitive resource using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" template=\"vm-template\">\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm1 will inherit everything from vm-template. For example, the equivalent of the above two examples would be:" msgstr "" #. Tag: title #, no-c-format msgid "Equivalent Xen primitive resource not using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "If you want to overwrite some attributes or operations, add them to the particular primitive’s definition." msgstr "" #. Tag: title #, no-c-format msgid "Xen resource overriding template values" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm2\" template=\"vm-template\">\n" " <meta_attributes id=\"vm2-meta_attributes\">\n" " <nvpair id=\"vm2-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"false\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm2-utilization\">\n" " <nvpair id=\"vm2-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" " <instance_attributes id=\"vm2-instance_attributes\">\n" " <nvpair id=\"vm2-instance_attributes-name\" name=\"name\" value=\"vm2\"/>\n" " <nvpair id=\"vm2-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm2\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"vm2-monitor-30s\" interval=\"30s\" name=\"monitor\" timeout=\"120s\"/>\n" " <op id=\"vm2-stop-0\" interval=\"0\" name=\"stop\" timeout=\"60s\"/>\n" " </operations>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm2 has special attribute values. Its monitor operation has a longer timeout and interval, and the primitive has an additional stop operation." msgstr "" #. Tag: para #, no-c-format msgid "To see the resulting definition of a resource, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml --resource vm2" msgstr "" #. Tag: para #, no-c-format msgid "To see the raw definition of a resource in the CIB, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml-raw --resource vm2" msgstr "" #. Tag: title #, no-c-format -msgid "Referencing Templates in Constraints" +msgid "Using Templates in Constraints" msgstr "" #. Tag: para #, no-c-format msgid "A resource template can be referenced in the following types of constraints:" msgstr "" #. Tag: para #, no-c-format msgid "order constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "colocation constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "rsc_ticket constraints (for multi-site clusters as described in )" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates referenced in constraints stand for all primitives which are derived from that template. This means, the constraint applies to all primitive resources referencing the resource template. Referencing resource templates in constraints is an alternative to resource sets and can simplify the cluster configuration considerably." msgstr "" #. Tag: para #, no-c-format msgid "For example, given the example templates earlier in this section:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-template-colo-base-rsc\" rsc=\"vm-template\" rsc-role=\"Started\" with-rsc=\"base-rsc\" score=\"INFINITY\"/>" msgstr "" #. Tag: para #, no-c-format msgid "would colocate all VMs with base-rsc and is the equivalent of the following constraint configuration:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-colo-base-rsc\" score=\"INFINITY\">\n" " <resource_set id=\"vm-colo-base-rsc-0\" sequential=\"false\" role=\"Started\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"vm-colo-base-rsc-1\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" "</rsc_colocation>" msgstr "" #. Tag: para #, no-c-format msgid "In a colocation constraint, only one template may be referenced from either rsc or with-rsc; the other reference must be a regular resource." msgstr "" #. Tag: title #, no-c-format -msgid "Referencing Resource Templates in Sequential Resource Sets" +msgid "Using Templates in Resource Sets" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates can also be referenced in resource sets." msgstr "" #. Tag: para #, no-c-format -msgid "For example:" +msgid "For example, given the example templates earlier in this section, then:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm-template\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: para #, no-c-format -msgid "is the equivalent of the following constraint configuration:" +msgid "is the equivalent of the following constraint using a sequential resource set:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" -#. Tag: title -#, no-c-format -msgid "Referencing Resource Templates in Parallel Resource Sets" -msgstr "" - #. Tag: para #, no-c-format -msgid "If the resources referencing the template can run in parallel:" +msgid "Or, if the resources referencing the template can run in parallel, then:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm-template\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" +#. Tag: para +#, no-c-format +msgid "is the equivalent of the following constraint configuration:" +msgstr "" + #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" +#. 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: 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 "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 "Tagging Configuration Elements" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Pacemaker allows you to tag any configuration element that has an XML ID." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The main purpose of tagging is to support higher-level user interface tools; Pacemaker itself only uses tags within constraints. Therefore, what you can do with tags mostly depends on the tools you use." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring Tags" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A tag is simply a named list of XML IDs." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Tag referencing three resources" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<tags>\n" +" <tag id=\"all-vms\">\n" +" <obj_ref id=\"vm1\"/>\n" +" <obj_ref id=\"vm2\"/>\n" +" <obj_ref id=\"vm3\"/>\n" +" </tag>\n" +"</tags>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "What you can do with this new tag depends on what your higher-level tools support. For example, a tool might allow you to enable or disable all of the tagged resources at once, or show the status of just the tagged resources." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A single configuration element can be listed in any number of tags." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Using Tags in Constraints and Resource Sets" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Pacemaker itself only uses tags in constraints. If you supply a tag name instead of a resource name in any constraint, the constraint will apply to all resources listed in that tag." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Constraint using a tag" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order1\" first=\"storage\" then=\"all-vms\" kind=\"Mandatory\" />" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the example above, assuming the all-vms tag is defined as in the previous example, the constraint will behave the same as:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Equivalent constraints without tags" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order1-1\" first=\"storage\" then=\"vm1\" kind=\"Mandatory\" />\n" +"<rsc_order id=\"order1-2\" first=\"storage\" then=\"vm2\" kind=\"Mandatory\" />\n" +"<rsc_order id=\"order1-3\" first=\"storage\" then=\"vm2\" kind=\"Mandatory\" />" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A tag may be used directly in the constraint, or indirectly by being listed in a resource set used in the constraint. When used in a resource set, an expanded tag will honor the set’s sequential property." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot index 6f049ab60d..944ada7d9d 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot @@ -1,362 +1,362 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Utilization and Placement Strategy" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker decides where to place a resource according to the resource allocation scores on every node. The resource will be allocated to the node where the resource has the highest score." msgstr "" #. Tag: para #, no-c-format msgid "If the resource allocation scores on all the nodes are equal, by the default placement strategy, Pacemaker will choose a node with the least number of allocated resources for balancing the load. If the number of resources on each node is equal, the first eligible node listed in the CIB will be chosen to run the resource." msgstr "" #. Tag: para #, no-c-format msgid "Often, in real-world situations, different resources use significantly different proportions of a node’s capacities (memory, I/O, etc.). We cannot balance the load ideally just according to the number of resources allocated to a node. Besides, if resources are placed such that their combined requirements exceed the provided capacity, they may fail to start completely or run with degraded performance." msgstr "" #. Tag: para #, no-c-format msgid "To take these factors into account, Pacemaker allows you to configure:" msgstr "" #. Tag: para #, no-c-format msgid "The capacity a certain node provides." msgstr "" #. Tag: para #, no-c-format msgid "The capacity a certain resource requires." msgstr "" #. Tag: para #, no-c-format msgid "An overall strategy for placement of resources." msgstr "" #. Tag: title #, no-c-format msgid "Utilization attributes" msgstr "" #. Tag: para #, no-c-format msgid "To configure the capacity that a node provides or a resource requires, you can use utilization attributes in node and resource objects. You can name utilization attributes according to your preferences and define as many name/value pairs as your configuration needs. However, the attributes' values must be integers." msgstr "" #. Tag: title #, no-c-format msgid "Specifying CPU and RAM capacities of two nodes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<node id=\"node1\" type=\"normal\" uname=\"node1\">\n" " <utilization id=\"node1-utilization\">\n" " <nvpair id=\"node1-utilization-cpu\" name=\"cpu\" value=\"2\"/>\n" " <nvpair id=\"node1-utilization-memory\" name=\"memory\" value=\"2048\"/>\n" " </utilization>\n" "</node>\n" "<node id=\"node2\" type=\"normal\" uname=\"node2\">\n" " <utilization id=\"node2-utilization\">\n" " <nvpair id=\"node2-utilization-cpu\" name=\"cpu\" value=\"4\"/>\n" " <nvpair id=\"node2-utilization-memory\" name=\"memory\" value=\"4096\"/>\n" " </utilization>\n" "</node>" msgstr "" #. Tag: title #, no-c-format msgid "Specifying CPU and RAM consumed by several resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"rsc-small\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-small-utilization\">\n" " <nvpair id=\"rsc-small-utilization-cpu\" name=\"cpu\" value=\"1\"/>\n" " <nvpair id=\"rsc-small-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" "</primitive>\n" "<primitive id=\"rsc-medium\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-medium-utilization\">\n" " <nvpair id=\"rsc-medium-utilization-cpu\" name=\"cpu\" value=\"2\"/>\n" " <nvpair id=\"rsc-medium-utilization-memory\" name=\"memory\" value=\"2048\"/>\n" " </utilization>\n" "</primitive>\n" "<primitive id=\"rsc-large\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-large-utilization\">\n" " <nvpair id=\"rsc-large-utilization-cpu\" name=\"cpu\" value=\"3\"/>\n" " <nvpair id=\"rsc-large-utilization-memory\" name=\"memory\" value=\"3072\"/>\n" " </utilization>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "A node is considered eligible for a resource if it has sufficient free capacity to satisfy the resource’s requirements. The nature of the required or provided capacities is completely irrelevant to Pacemaker — it just makes sure that all capacity requirements of a resource are satisfied before placing a resource to a node." msgstr "" #. Tag: title #, no-c-format msgid "Placement Strategy" msgstr "" #. Tag: para #, no-c-format msgid "After you have configured the capacities your nodes provide and the capacities your resources require, you need to set the placement-strategy in the global cluster options, otherwise the capacity configurations have no effect." 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. 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 only when deciding whether a node is considered eligible (i.e. whether it has sufficient free capacity to satisfy the resource’s requirements). Load-balancing is still done based on the number of resources allocated to a node." msgstr "" #. Tag: term #, no-c-format msgid "balanced" msgstr "" #. Tag: para #, no-c-format msgid "Utilization values are taken into account when deciding whether a node is eligible to serve a resource and when load-balancing, so an attempt is made to spread the resources in a way that optimizes resource performance." msgstr "" #. Tag: term #, no-c-format msgid "minimal" msgstr "" #. Tag: para #, no-c-format msgid "Utilization values are taken into account only when deciding whether a node is eligible to serve a resource. For load-balancing, an attempt is made to concentrate the resources on as few nodes as possible, thereby enabling possible power savings on the remaining nodes." msgstr "" #. Tag: para #, no-c-format msgid "Set placement-strategy with crm_attribute:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_attribute --name placement-strategy --update balanced" msgstr "" #. Tag: para #, no-c-format msgid "Now Pacemaker will ensure the load from your resources will be distributed evenly throughout the cluster, without the need for convoluted sets of colocation constraints." msgstr "" #. Tag: title #, no-c-format msgid "Allocation Details" msgstr "" #. Tag: title #, no-c-format msgid "Which node is preferred to get consumed first when allocating resources?" msgstr "" #. Tag: para #, no-c-format msgid "The node with the highest node weight gets consumed first. Node weight is a score maintained by the cluster to represent node health." msgstr "" #. Tag: para #, no-c-format msgid "If multiple nodes have the same node weight:" msgstr "" #. Tag: para #, no-c-format msgid "If placement-strategy is default or utilization, the node that has the least number of allocated resources gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If their numbers of allocated resources are equal, the first eligible node listed in the CIB gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If placement-strategy is balanced, the node that has the most free capacity gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If the free capacities of the nodes are equal, the node that has the least number of allocated resources gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If placement-strategy is minimal, the first eligible node listed in the CIB gets consumed first." msgstr "" #. Tag: title #, no-c-format msgid "Which node has more free capacity?" msgstr "" #. Tag: para #, no-c-format msgid "If only one type of utilization attribute has been defined, free capacity is a simple numeric comparison." msgstr "" #. Tag: para #, no-c-format msgid "If multiple types of utilization attributes have been defined, then the node that is numerically highest in the the most attribute types has the most free capacity. For example:" msgstr "" #. Tag: para #, no-c-format msgid "If nodeA has more free cpus, and nodeB has more free memory, then their free capacities are equal." msgstr "" #. Tag: para #, no-c-format msgid "If nodeA has more free cpus, while nodeB has more free memory and storage, then nodeB has more free capacity." msgstr "" #. Tag: title #, no-c-format msgid "Which resource is preferred to be assigned first?" msgstr "" #. Tag: para #, no-c-format msgid "The resource that has the highest priority (see ) gets allocated first." msgstr "" #. Tag: para #, no-c-format msgid "If their priorities are equal, check whether they are already running. The resource that has the highest score on the node where it’s running gets allocated first, to prevent resource shuffling." msgstr "" #. Tag: para #, no-c-format msgid "If the scores above are equal or the resources are not running, the resource has the highest score on the preferred node gets allocated first." msgstr "" #. Tag: para #, no-c-format msgid "If the scores above are equal, the first runnable resource listed in the CIB gets allocated first." msgstr "" #. Tag: title #, no-c-format msgid "Limitations and Workarounds" msgstr "" #. Tag: para #, no-c-format msgid "The type of problem Pacemaker is dealing with here is known as the knapsack problem and falls into the NP-complete category of computer science problems — a fancy way of saying \"it takes a really long time to solve\"." msgstr "" #. Tag: para #, no-c-format msgid "Clearly in a HA cluster, it’s not acceptable to spend minutes, let alone hours or days, finding an optimal solution while services remain unavailable." msgstr "" #. Tag: para #, no-c-format msgid "So instead of trying to solve the problem completely, Pacemaker uses a 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 at the start of this section:" msgstr "" #. Tag: para #, no-c-format msgid "rsc-small would be allocated to node1" msgstr "" #. Tag: para #, no-c-format msgid "rsc-medium would be allocated to node2" msgstr "" #. Tag: para #, no-c-format msgid "rsc-large would remain inactive" msgstr "" #. Tag: para #, no-c-format msgid "Which is not ideal." msgstr "" #. Tag: para #, no-c-format msgid "There are various approaches to dealing with the limitations of pacemaker’s placement strategy:" msgstr "" #. Tag: term #, no-c-format msgid "Ensure you have sufficient physical capacity." msgstr "" #. Tag: para #, no-c-format msgid "It might sound obvious, but if the physical capacity of your nodes is (close to) maxed out by the cluster under normal conditions, then failover isn’t going to go well. Even without the utilization feature, you’ll start hitting timeouts and getting secondary failures." msgstr "" #. Tag: term #, no-c-format msgid "Build some buffer into the capabilities advertised by the nodes." msgstr "" #. Tag: para #, no-c-format msgid "Advertise slightly more resources than we physically have, on the (usually valid) assumption that a resource will not use 100% of the configured amount of CPU, memory and so forth all the time. This practice is sometimes called overcommit." msgstr "" #. Tag: term #, no-c-format msgid "Specify resource priorities." msgstr "" #. Tag: para #, no-c-format msgid "If the cluster is going to sacrifice services, it should be the ones you care about (comparatively) the least. Ensure that resource priorities are properly set so that your most important resources are scheduled first." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot index bda7be86d5..83087da995 100644 --- a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot +++ b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot @@ -1,44 +1,44 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Further Reading" msgstr "" #. Tag: para #, no-c-format msgid "Project Website: " msgstr "" #. Tag: para #, no-c-format msgid "Project Documentation: " msgstr "" #. Tag: para #, no-c-format msgid "SUSE High Availibility Guide: " msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat configuration: " msgstr "" #. Tag: para #, no-c-format msgid "Corosync Configuration: " msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Preface.pot b/doc/Pacemaker_Explained/pot/Preface.pot index eb70fb6c89..f84c72b747 100644 --- a/doc/Pacemaker_Explained/pot/Preface.pot +++ b/doc/Pacemaker_Explained/pot/Preface.pot @@ -1,19 +1,19 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Preface" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Revision_History.pot b/doc/Pacemaker_Explained/pot/Revision_History.pot index eb4f85b805..56bf074103 100644 --- a/doc/Pacemaker_Explained/pot/Revision_History.pot +++ b/doc/Pacemaker_Explained/pot/Revision_History.pot @@ -1,89 +1,99 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: member #, no-c-format msgid "Import from Pages.app" msgstr "" #. Tag: member #, no-c-format msgid "Cleanup and reformatting of docbook xml complete" msgstr "" #. Tag: member #, no-c-format msgid "Split book into chapters and pass validation" msgstr "" #. Tag: member #, no-c-format msgid "Re-organize book for use with Publican" msgstr "" #. Tag: member #, no-c-format msgid "Converted to asciidoc (which is converted to docbook for use with Publican)" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Update for clarity, stylistic consistency and current command-line syntax" msgstr "" #. Tag: member #, no-c-format msgid "Update for Pacemaker 1.1.14" msgstr "" #. Tag: member #, no-c-format msgid "Update for Pacemaker 1.1.15" msgstr "" #. Tag: member #, no-c-format msgid "Overhaul upgrade documentation, and document node health strategies" msgstr "" #. Tag: member #, no-c-format msgid "Update for Pacemaker 1.1.16" msgstr "" +#. Tag: member +#, no-c-format +msgid "Update for Pacemaker 1.1.17" +msgstr "" + +#. Tag: member +#, no-c-format +msgid "Update for Pacemaker 1.1.18" +msgstr "" + diff --git a/doc/Pacemaker_Remote/pot/Author_Group.pot b/doc/Pacemaker_Remote/pot/Author_Group.pot index 85d3f585bc..a6f1fbd132 100644 --- a/doc/Pacemaker_Remote/pot/Author_Group.pot +++ b/doc/Pacemaker_Remote/pot/Author_Group.pot @@ -1,34 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: firstname #, no-c-format msgid "David" msgstr "" #. Tag: surname #, no-c-format msgid "Vossel" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Primary author" msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Book_Info.pot b/doc/Pacemaker_Remote/pot/Book_Info.pot index 23f05227e1..fd3dd34d84 100644 --- a/doc/Pacemaker_Remote/pot/Book_Info.pot +++ b/doc/Pacemaker_Remote/pot/Book_Info.pot @@ -1,74 +1,74 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Pacemaker Remote" msgstr "" #. Tag: subtitle #, no-c-format msgid "Scaling High Availablity Clusters" msgstr "" #. Tag: para #, no-c-format msgid "The document exists as both a reference and deployment guide for the Pacemaker Remote service." msgstr "" #. Tag: para #, no-c-format msgid "The example commands in this document will use:" msgstr "" #. Tag: para #, no-c-format msgid "&DISTRO; &DISTRO_VERSION; as the host operating system" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker Remote to perform resource management within guest nodes and remote nodes" msgstr "" #. Tag: para #, no-c-format msgid "KVM for virtualization" msgstr "" #. Tag: para #, no-c-format msgid "libvirt to manage guest nodes" msgstr "" #. Tag: para #, no-c-format msgid "Corosync to provide messaging and membership services on cluster nodes" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker to perform resource management on cluster nodes" msgstr "" #. Tag: para #, no-c-format msgid "pcs as the cluster configuration toolset" msgstr "" #. Tag: para #, no-c-format msgid "The concepts are the same for other distributions, virtualization platforms, toolsets, and messaging layers, and should be easily adaptable." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot index 3fcbb6f30b..d0f9587009 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot @@ -1,109 +1,109 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Alternative Configurations" msgstr "" #. Tag: para #, no-c-format -msgid "These alternative configurations may be appropriate in limited cases, such as a test cluster, but are not the best method in most situations. They are presented here for completeness and as an example of pacemaker’s flexibility to suit your needs." +msgid "These alternative configurations may be appropriate in limited cases, such as a test cluster, but are not the best method in most situations. They are presented here for completeness and as an example of Pacemaker’s flexibility to suit your needs." msgstr "" #. Tag: title #, no-c-format msgid "Virtual Machines as Cluster Nodes" msgstr "" #. Tag: para #, no-c-format -msgid "The preferred use of virtual machines in a pacemaker cluster is as a cluster resource, whether opaque or as a guest node. However, it is possible to run the full cluster stack on a virtual node instead." +msgid "The preferred use of virtual machines in a Pacemaker cluster is as a cluster resource, whether opaque or as a guest node. However, it is possible to run the full cluster stack on a virtual node instead." msgstr "" #. Tag: para #, no-c-format msgid "This is commonly used to set up test environments; a single physical host (that does not participate in the cluster) runs two or more virtual machines, all running the full cluster stack. This can be used to simulate a larger cluster for testing purposes." msgstr "" #. Tag: para #, no-c-format msgid "In a production environment, fencing becomes more complicated, especially if the underlying hosts run any services besides the clustered VMs. If the VMs are not guaranteed a minimum amount of host resources, CPU and I/O contention can cause timing issues for cluster components." msgstr "" #. Tag: para #, no-c-format msgid "Another situation where this approach is sometimes used is when the cluster owner leases the VMs from a provider and does not have direct access to the underlying host. The main concerns in this case are proper fencing (usually via a custom resource agent that communicates with the provider’s APIs) and maintaining a static IP address between reboots, as well as resource contention issues." msgstr "" #. Tag: title #, no-c-format msgid "Virtual Machines as Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Virtual machines may be configured following the process for remote nodes rather than guest nodes (i.e., using an ocf:pacemaker:remote resource rather than letting the cluster manage the VM directly)." msgstr "" #. Tag: para #, no-c-format msgid "This is mainly useful in testing, to use a single physical host to simulate a larger cluster involving remote nodes. Pacemaker’s Cluster Test Suite (CTS) uses this approach to test remote node functionality." msgstr "" #. Tag: title #, no-c-format msgid "Containers as Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Containers,https://en.wikipedia.org/wiki/Operating-system-level_virtualization and in particular Linux containers (LXC) and Docker, have become a popular method of isolating services in a resource-efficient manner." msgstr "" #. Tag: para #, no-c-format -msgid "The preferred means of integrating containers into Pacemaker is as a cluster resource, whether opaque or using Pacemaker’s built-in resource isolation support.Documentation for this support is planned but not yet available." +msgid "The preferred means of integrating containers into Pacemaker is as a cluster resource, whether opaque or using Pacemaker’s bundle resource type." msgstr "" #. Tag: para #, no-c-format msgid "However, it is possible to run pacemaker_remote inside a container, following the process for guest nodes. This is not recommended but can be useful, for example, in testing scenarios, to simulate a large number of guest nodes." msgstr "" #. Tag: para #, no-c-format msgid "The configuration process is very similar to that described for guest nodes using virtual machines. Key differences:" msgstr "" #. Tag: para #, no-c-format msgid "The underlying host must install the libvirt driver for the desired container technology — for example, the libvirt-daemon-lxc package to get the libvirt-lxc driver for LXC containers." msgstr "" #. Tag: para #, no-c-format msgid "Libvirt XML definitions must be generated for the containers. The pacemaker-cts package includes a script for this purpose, /usr/share/pacemaker/tests/cts/lxc_autogen.sh. Run it with the --help option for details on how to use it. It is intended for testing purposes only, and hardcodes various parameters that would need to be set appropriately in real usage. Of course, you can create XML definitions manually, following the appropriate libvirt driver documentation." msgstr "" #. Tag: para #, no-c-format msgid "To share the authentication key, either share the host’s /etc/pacemaker directory with the container, or copy the key into the container’s filesystem." msgstr "" #. Tag: para #, no-c-format msgid "The VirtualDomain resource for a container will need force_stop=\"true\" and an appropriate hypervisor option, for example hypervisor=\"lxc:///\" for LXC containers." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot index 97e2a2ae11..8d49324bca 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot @@ -1,458 +1,458 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Remote Node Walk-through" msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is: An in-depth walk-through of how to get Pacemaker to integrate a remote node into the cluster as a node capable of running cluster resources." msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is not: A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of remote nodes as quickly as possible." msgstr "" #. Tag: para #, no-c-format msgid "This tutorial requires three machines: two to act as cluster nodes, and a third to act as the remote node." msgstr "" #. Tag: title #, no-c-format msgid "Configure Remote Node" msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Allow cluster-related services through the local firewall:" msgstr "" #. Tag: screen #, no-c-format msgid "# firewall-cmd --permanent --add-service=high-availability\n" "success\n" "# firewall-cmd --reload\n" "success" msgstr "" #. Tag: para #, no-c-format msgid "If you are using iptables directly, or some other firewall solution besides firewalld, simply open the following ports, which can be used by various clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405." msgstr "" #. Tag: para #, no-c-format msgid "If you run into any problems during testing, you might want to disable the firewall and SELinux entirely until you have everything working. This may create significant security issues and should not be performed on machines that will be exposed to the outside world, but may be appropriate during development and testing on a protected host." msgstr "" #. Tag: para #, no-c-format msgid "To disable security measures:" msgstr "" #. Tag: screen #, no-c-format msgid "# setenforce 0\n" "# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" "# systemctl mask firewalld.service\n" "# systemctl stop firewalld.service\n" "# iptables --flush" msgstr "" #. Tag: title #, no-c-format msgid "Configure pacemaker_remote on Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Install the pacemaker_remote daemon on the remote node." msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker-remote resource-agents pcs" msgstr "" #. Tag: para #, no-c-format msgid "Create a location for the shared authentication key:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "All nodes (both cluster nodes and remote nodes) must have the same authentication key installed for the communication to work correctly. If you already have a key on an existing node, copy it to the new remote node. Otherwise, create a new key, for example:" msgstr "" #. Tag: screen #, no-c-format msgid "# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1" msgstr "" #. Tag: para #, no-c-format msgid "Now start and enable the pacemaker_remote daemon on the remote node." msgstr "" #. Tag: screen #, no-c-format msgid "# systemctl enable pacemaker_remote.service\n" "# systemctl start pacemaker_remote.service" msgstr "" #. Tag: para #, no-c-format msgid "Verify the start is successful." msgstr "" #. Tag: screen #, no-c-format msgid "# systemctl status pacemaker_remote\n" "pacemaker_remote.service - Pacemaker Remote Service\n" " Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)\n" " Active: active (running) since Fri 2015-08-21 15:21:20 CDT; 20s ago\n" " Main PID: 21273 (pacemaker_remot)\n" " CGroup: /system.slice/pacemaker_remote.service\n" " └─21273 /usr/sbin/pacemaker_remoted\n" "\n" "Aug 21 15:21:20 remote1 systemd[1]: Starting Pacemaker Remote Service...\n" "Aug 21 15:21:20 remote1 systemd[1]: Started Pacemaker Remote Service.\n" "Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log\n" "Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121.\n" "Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: bind_and_listen: Listening on address ::" msgstr "" #. Tag: title #, no-c-format msgid "Verify Connection to Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Before moving forward, it’s worth verifying that the cluster nodes can contact the remote node on port 3121. Here’s a trick you can use. Connect using ssh from each of the cluster nodes. The connection will get destroyed, but how it is destroyed tells you whether it worked or not." msgstr "" #. Tag: para #, no-c-format msgid "First, add the remote node’s hostname (we’re using remote1 in this tutorial) to the cluster nodes' /etc/hosts files if you haven’t already. This is required unless you have DNS set up in a way where remote1’s address can be discovered." msgstr "" #. Tag: para #, no-c-format msgid "Execute the following on each cluster node, replacing the IP address with the actual IP address of the remote node." msgstr "" #. Tag: screen #, no-c-format msgid "# cat << END >> /etc/hosts\n" "192.168.122.10 remote1\n" "END" msgstr "" #. Tag: para #, no-c-format msgid "If running the ssh command on one of the cluster nodes results in this output before disconnecting, the connection works:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 remote1\n" "ssh_exchange_identification: read: Connection reset by peer" msgstr "" #. Tag: para #, no-c-format msgid "If you see one of these, the connection is not working:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 remote1\n" "ssh: connect to host remote1 port 3121: No route to host" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 remote1\n" "ssh: connect to host remote1 port 3121: Connection refused" msgstr "" #. Tag: para #, no-c-format msgid "Once you can successfully connect to the remote node from the both cluster nodes, move on to setting up Pacemaker on the cluster nodes." msgstr "" #. Tag: title #, no-c-format msgid "Configure Cluster Nodes" msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "On each cluster node, allow cluster-related services through the local firewall, following the same procedure as in ." msgstr "" #. Tag: title #, no-c-format msgid "Install Pacemaker on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "On the two cluster nodes, install the following packages." msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker corosync pcs resource-agents" msgstr "" #. Tag: title #, no-c-format msgid "Copy Authentication Key to Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Create a location for the shared authentication key, and copy it from any existing node:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker\n" "# scp remote1:/etc/pacemaker/authkey /etc/pacemaker/authkey" msgstr "" #. Tag: title #, no-c-format msgid "Configure Corosync on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Corosync handles Pacemaker’s cluster membership and messaging. The corosync config file is located in /etc/corosync/corosync.conf. That config file must be initialized with information about the two cluster nodes before pacemaker can start." msgstr "" #. Tag: para #, no-c-format msgid "To initialize the corosync config file, execute the following pcs command on both nodes, filling in the information in <> with your nodes' information." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster setup --force --local --name mycluster <node1 ip or hostname> <node2 ip or hostname>" msgstr "" #. Tag: title #, no-c-format msgid "Start Pacemaker on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Start the cluster stack on both cluster nodes using the following command." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster start" msgstr "" #. Tag: para #, no-c-format msgid "Verify corosync membership" msgstr "" #. Tag: literallayout #, no-c-format msgid "# pcs status corosync\n" "Membership information\n" "----------------------\n" " Nodeid Votes Name\n" " 1 1 node1 (local)" msgstr "" #. Tag: para #, no-c-format msgid "Verify Pacemaker status. At first, the pcs cluster status output will look like this." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Aug 21 16:14:05 2015\n" "Last change: Fri Aug 21 14:02:14 2015\n" "Stack: corosync\n" "Current DC: NONE\n" "Version: 1.1.12-a14efad\n" "1 Nodes configured, unknown expected votes\n" "0 Resources configured" msgstr "" #. Tag: para #, no-c-format msgid "After about a minute, you should see your two cluster nodes come online." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Aug 21 16:16:32 2015\n" "Last change: Fri Aug 21 14:02:14 2015\n" "Stack: corosync\n" "Current DC: node1 (1) - partition with quorum\n" "Version: 1.1.12-a14efad\n" "2 Nodes configured\n" "0 Resources configured\n" "\n" "Online: [ node1 node2 ]" msgstr "" #. Tag: para #, no-c-format msgid "For the sake of this tutorial, we are going to disable stonith to avoid having to cover fencing device configuration." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs property set stonith-enabled=false" msgstr "" #. Tag: title #, no-c-format msgid "Integrate Remote Node into Cluster" msgstr "" #. Tag: para #, no-c-format msgid "Integrating a remote node into the cluster is achieved through the creation of a remote node connection resource. The remote node connection resource both establishes the connection to the remote node and defines that the remote node exists. Note that this resource is actually internal to Pacemaker’s crmd component. A metadata file for this resource can be found in the /usr/lib/ocf/resource.d/pacemaker/remote file that describes what options are available, but there is no actual ocf:pacemaker:remote resource agent script that performs any work." msgstr "" #. Tag: para #, no-c-format msgid "Define the remote node connection resource to our remote node, remote1, using the following command on any cluster node." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create remote1 ocf:pacemaker:remote" msgstr "" #. Tag: para #, no-c-format msgid "That’s it. After a moment you should see the remote node come online." msgstr "" #. Tag: screen #, no-c-format msgid "Cluster name: mycluster\n" "Last updated: Fri Aug 21 17:13:09 2015\n" "Last change: Fri Aug 21 17:02:02 2015\n" "Stack: corosync\n" "Current DC: node1 (1) - partition with quorum\n" "Version: 1.1.12-a14efad\n" "3 Nodes configured\n" "1 Resources configured\n" "\n" "\n" "Online: [ node1 node2 ]\n" "RemoteOnline: [ remote1 ]\n" "\n" "Full list of resources:\n" "\n" " remote1 (ocf::pacemaker:remote): Started node1\n" "\n" "PCSD Status:\n" " node1: Online\n" " node2: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format msgid "Starting Resources on Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Once the remote node is integrated into the cluster, starting resources on a remote node is the exact same as on cluster nodes. Refer to the Clusters from Scratch document for examples of resource creation." msgstr "" #. Tag: para #, no-c-format msgid "Never involve a remote node connection resource in a resource group, colocation constraint, or order constraint." msgstr "" #. Tag: title #, no-c-format msgid "Fencing Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Remote nodes are fenced the same way as cluster nodes. No special considerations are required. Configure fencing resources for use with remote nodes the same as you would with cluster nodes." msgstr "" #. Tag: para #, no-c-format msgid "Note, however, that remote nodes can never initiate a fencing action. Only cluster nodes are capable of actually executing a fencing operation against another node." msgstr "" #. Tag: title #, no-c-format msgid "Accessing Cluster Tools from a Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Besides allowing the cluster to manage resources on a remote node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on remote nodes natively." msgstr "" #. Tag: para #, no-c-format msgid "Try it: Run crm_mon on the remote node after pacemaker has integrated it into the cluster. These tools just work. These means resource agents such as master/slave resources which need access to tools like crm_master work seamlessly on the remote nodes." msgstr "" #. Tag: para #, no-c-format msgid "Higher-level command shells such as pcs may have partial support on remote nodes, but it is recommended to run them from a cluster node." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Example.pot b/doc/Pacemaker_Remote/pot/Ch-Example.pot index 5fd0b61a8f..f27a1eb1c6 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Example.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Example.pot @@ -1,174 +1,174 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Guest Node Quick Example" msgstr "" #. Tag: para #, no-c-format msgid "If you already know how to use Pacemaker, you’ll likely be able to grasp this new concept of guest nodes by reading through this quick example without having to sort through all the detailed walk-through steps. Here are the key configuration ingredients that make this possible using libvirt and KVM virtual guests. These steps strip everything down to the very basics. guest node nodeguest node guest node " msgstr "" #. Tag: title #, no-c-format msgid "Mile-High View of Configuration Steps" msgstr "" #. Tag: para #, no-c-format msgid "Give each virtual machine that will be used as a guest node a static network address and unique hostname." msgstr "" #. Tag: para #, no-c-format msgid "Put the same authentication key with the path /etc/pacemaker/authkey on every cluster node and virtual machine. This secures remote communication." msgstr "" #. Tag: para #, no-c-format msgid "Run this command if you want to make a somewhat random key:" msgstr "" #. Tag: screen #, no-c-format msgid "dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1" msgstr "" #. Tag: para #, no-c-format msgid "Install pacemaker_remote on every virtual machine, enabling it to start at boot, and if a local firewall is used, allow the node to accept connections on TCP port 3121." msgstr "" #. Tag: screen #, no-c-format msgid "yum install pacemaker-remote resource-agents\n" "systemctl enable pacemaker_remote\n" "firewall-cmd --add-port 3121/tcp --permanent" msgstr "" #. Tag: para #, no-c-format msgid "If you just want to see this work, you may want to simply disable the local firewall and put SELinux in permissive mode while testing. This creates security risks and should not be done on a production machine exposed to the Internet, but can be appropriate for a protected test machine." msgstr "" #. Tag: para #, no-c-format msgid "Create a Pacemaker resource to launch each virtual machine, using the remote-node meta-attribute to let Pacemaker know this will be a guest node capable of running resources." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create vm-guest1 VirtualDomain hypervisor=\"qemu:///system\" config=\"vm-guest1.xml\" meta remote-node=\"guest1\"" msgstr "" #. Tag: para #, no-c-format msgid "The above command will create CIB XML similar to the following:" msgstr "" #. Tag: programlisting #, no-c-format msgid " <primitive class=\"ocf\" id=\"vm-guest1\" provider=\"heartbeat\" type=\"VirtualDomain\">\n" " <instance_attributes id=\"vm-guest-instance_attributes\">\n" " <nvpair id=\"vm-guest1-instance_attributes-hypervisor\" name=\"hypervisor\" value=\"qemu:///system\"/>\n" " <nvpair id=\"vm-guest1-instance_attributes-config\" name=\"config\" value=\"guest1.xml\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"vm-guest1-interval-30s\" interval=\"30s\" name=\"monitor\"/>\n" " </operations>\n" " <meta_attributes id=\"vm-guest1-meta_attributes\">\n" " <nvpair id=\"vm-guest1-meta_attributes-remote-node\" name=\"remote-node\" value=\"guest1\"/>\n" " </meta_attributes>\n" " </primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the meta-attribute remote-node=\"guest1\" tells Pacemaker that this resource is a guest node with the hostname guest1. The cluster will attempt to contact the virtual machine’s pacemaker_remote service at the hostname guest1 after it launches." msgstr "" #. Tag: para #, no-c-format msgid "The ID of the resource creating the virtual machine (vm-guest1 in the above example) must be different from the virtual machine’s uname (guest1 in the above example). Pacemaker will create an implicit internal resource for the pacemaker_remote connection to the guest, named with the value of remote-node, so that value cannot be used as the name of any other resource." msgstr "" #. Tag: title #, no-c-format msgid "Using a Guest Node" msgstr "" #. Tag: para #, no-c-format msgid "Guest nodes will show up in crm_mon output as normal:" msgstr "" #. Tag: title #, no-c-format msgid "Example crm_mon output after guest1 is integrated into cluster" msgstr "" #. Tag: screen #, no-c-format msgid "Last updated: Wed Mar 13 13:52:39 2013\n" "Last change: Wed Mar 13 13:25:17 2013 via crmd on node1\n" "Stack: corosync\n" "Current DC: node1 (24815808) - partition with quorum\n" "Version: 1.1.10\n" "2 Nodes configured, unknown expected votes\n" "2 Resources configured.\n" "\n" "Online: [ node1 guest1]\n" "\n" "vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1" msgstr "" #. Tag: para #, no-c-format msgid "Now, you could place a resource, such as a webserver, on guest1:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create webserver apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=30s\n" "# pcs constraint location webserver prefers guest1" msgstr "" #. Tag: para #, no-c-format msgid "Now, the crm_mon output would show:" msgstr "" #. Tag: screen #, no-c-format msgid "Last updated: Wed Mar 13 13:52:39 2013\n" "Last change: Wed Mar 13 13:25:17 2013 via crmd on node1\n" "Stack: corosync\n" "Current DC: node1 (24815808) - partition with quorum\n" "Version: 1.1.10\n" "2 Nodes configured, unknown expected votes\n" "2 Resources configured.\n" "\n" "Online: [ node1 guest1]\n" "\n" "vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1\n" "webserver (ocf::heartbeat::apache): Started guest1" msgstr "" #. Tag: para #, no-c-format msgid "It is worth noting that after guest1 is integrated into the cluster, nearly all the Pacemaker command-line tools immediately become available to the guest node. This means things like crm_mon, crm_resource, and crm_attribute will work natively on the guest node, as long as the connection between the guest node and a cluster node exists. This is particularly important for any master/slave resources executing on the guest node that need access to crm_master to set transient attributes." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Intro.pot b/doc/Pacemaker_Remote/pot/Ch-Intro.pot index 03f39e7341..dd7ee06b4d 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Intro.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Intro.pot @@ -1,384 +1,379 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Scaling a Pacemaker Cluster" msgstr "" #. Tag: title #, no-c-format msgid "Overview" msgstr "" #. Tag: para #, no-c-format msgid "In a basic Pacemaker high-availability cluster,See the Pacemaker documentation, especially Clusters From Scratch and Pacemaker Explained, for basic information about high-availability using Pacemaker each node runs the full cluster stack of corosync and all Pacemaker components. This allows great flexibility but limits scalability to around 16 nodes." msgstr "" #. Tag: para #, no-c-format msgid "To allow for scalability to dozens or even hundreds of nodes, Pacemaker allows nodes not running the full cluster stack to integrate into the cluster and have the cluster manage their resources as if they were a cluster node." msgstr "" #. Tag: title #, no-c-format msgid "Terms" msgstr "" #. Tag: term #, no-c-format msgid "cluster node" msgstr "" #. Tag: para #, no-c-format msgid "A node running the full high-availability stack of corosync and all Pacemaker components. Cluster nodes may run cluster resources, run all Pacemaker command-line tools (crm_mon, crm_resource and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster’s Designated Controller (DC). cluster node nodecluster node cluster node " msgstr "" #. Tag: term #, no-c-format msgid "pacemaker_remote" msgstr "" #. Tag: para #, no-c-format msgid "A small service daemon that allows a host to be used as a Pacemaker node without running the full cluster stack. Nodes running pacemaker_remote may run cluster resources and most command-line tools, but cannot perform other functions of full cluster nodes such as fencing execution, quorum voting or DC eligibility. The pacemaker_remote daemon is an enhanced version of Pacemaker’s local resource management daemon (LRMD). pacemaker_remote " msgstr "" #. Tag: term #, no-c-format msgid "remote node" msgstr "" #. Tag: para #, no-c-format msgid "A physical host running pacemaker_remote. Remote nodes have a special resource that manages communication with the cluster. This is sometimes referred to as the baremetal case. remote node noderemote node remote node " msgstr "" #. Tag: term #, no-c-format msgid "guest node" msgstr "" #. Tag: para #, no-c-format msgid "A virtual host running pacemaker_remote. Guest nodes differ from remote nodes mainly in that the guest node is itself a resource that the cluster manages. guest node nodeguest node guest node " msgstr "" #. Tag: para #, no-c-format msgid "Remote in this document refers to the node not being a part of the underlying corosync cluster. It has nothing to do with physical proximity. Remote nodes and guest nodes are subject to the same latency requirements as cluster nodes, which means they are typically in the same data center." msgstr "" #. Tag: para #, no-c-format msgid "It is important to distinguish the various roles a virtual machine can serve in Pacemaker clusters:" msgstr "" #. Tag: para #, no-c-format msgid "A virtual machine can run the full cluster stack, in which case it is a cluster node and is not itself managed by the cluster." msgstr "" #. Tag: para #, no-c-format msgid "A virtual machine can be managed by the cluster as a resource, without the cluster having any awareness of the services running inside the virtual machine. The virtual machine is opaque to the cluster." msgstr "" #. Tag: para #, no-c-format msgid "A virtual machine can be a cluster resource, and run pacemaker_remote to make it a guest node, allowing the cluster to manage services inside it. The virtual machine is transparent to the cluster." msgstr "" #. Tag: title #, no-c-format msgid "Support in Pacemaker Versions" msgstr "" #. Tag: para #, no-c-format msgid "It is recommended to run Pacemaker 1.1.12 or later when using pacemaker_remote due to important bug fixes. An overview of changes in pacemaker_remote capability by version (aside from bug fixes, which are included in every version):" msgstr "" #. Tag: title #, no-c-format msgid "1.1.16" msgstr "" #. Tag: para #, no-c-format msgid "Support for watchdog-based fencing (sbd) on remote nodes" msgstr "" #. Tag: title #, no-c-format msgid "1.1.15" msgstr "" #. Tag: para #, no-c-format msgid "If pacemaker_remote is stopped on an active node, it will wait for the cluster to migrate all resources off before exiting, rather than exit immediately and get fenced." msgstr "" #. Tag: title #, no-c-format msgid "1.1.14" msgstr "" #. Tag: para #, no-c-format msgid "Resources that create guest nodes can be included in groups" msgstr "" #. Tag: para #, no-c-format msgid "reconnect_interval option for remote nodes" msgstr "" #. Tag: title #, no-c-format msgid "1.1.13" msgstr "" #. Tag: para #, no-c-format msgid "Support for maintenance mode" msgstr "" #. Tag: para #, no-c-format msgid "Remote nodes can recover without being fenced when the cluster node hosting their connection fails" msgstr "" -#. Tag: para -#, no-c-format -msgid "Running pacemaker_remote within LXC environments is deprecated due to newly added Pacemaker support for isolated resources" -msgstr "" - #. Tag: para #, no-c-format msgid "#kind built-in node attribute for use with rules" msgstr "" #. Tag: title #, no-c-format msgid "1.1.12" msgstr "" #. Tag: para #, no-c-format msgid "Support for permanent node attributes" msgstr "" #. Tag: para #, no-c-format msgid "Support for migration" msgstr "" #. Tag: title #, no-c-format msgid "1.1.11" msgstr "" #. Tag: para #, no-c-format msgid "Support for IPv6" msgstr "" #. Tag: para #, no-c-format msgid "Support for remote nodes" msgstr "" #. Tag: para #, no-c-format msgid "Support for transient node attributes" msgstr "" #. Tag: para #, no-c-format msgid "Support for clusters with mixed endian architectures" msgstr "" #. Tag: title #, no-c-format msgid "1.1.10" msgstr "" #. Tag: para #, no-c-format msgid "remote-connect-timeout for guest nodes" msgstr "" #. Tag: title #, no-c-format msgid "1.1.9" msgstr "" #. Tag: para #, no-c-format msgid "Initial version to include pacemaker_remote" msgstr "" #. Tag: para #, no-c-format msgid "Limited to guest nodes in KVM/LXC environments using only IPv4; all nodes' architectures must have same endianness" msgstr "" #. Tag: title #, no-c-format msgid "Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid " guest node nodeguest node guest node " msgstr "" #. Tag: para #, no-c-format msgid "\"I want a Pacemaker cluster to manage virtual machine resources, but I also want Pacemaker to be able to manage the resources that live within those virtual machines.\"" msgstr "" #. Tag: para #, no-c-format msgid "Without pacemaker_remote, the possibilities for implementing the above use case have significant limitations:" msgstr "" #. Tag: para #, no-c-format msgid "The cluster stack could be run on the physical hosts only, which loses the ability to monitor resources within the guests." msgstr "" #. Tag: para #, no-c-format msgid "A separate cluster could be on the virtual guests, which quickly hits scalability issues." msgstr "" #. Tag: para #, no-c-format msgid "The cluster stack could be run on the guests using the same cluster as the physical hosts, which also hits scalability issues and complicates fencing." msgstr "" #. Tag: para #, no-c-format msgid "With pacemaker_remote:" msgstr "" #. Tag: para #, no-c-format msgid "The physical hosts are cluster nodes (running the full cluster stack)." msgstr "" #. Tag: para #, no-c-format msgid "The virtual machines are guest nodes (running the pacemaker_remote service). Nearly zero configuration is required on the virtual machine." msgstr "" #. Tag: para #, no-c-format msgid "The cluster stack on the cluster nodes launches the virtual machines and immediately connects to the pacemaker_remote service on them, allowing the virtual machines to integrate into the cluster." msgstr "" #. Tag: para #, no-c-format msgid "The key difference here between the guest nodes and the cluster nodes is that the guest nodes do not run the cluster stack. This means they will never become the DC, initiate fencing actions or participate in quorum voting." msgstr "" #. Tag: para #, no-c-format msgid "On the other hand, this also means that they are not bound to the scalability limits associated with the cluster stack (no 16-node corosync member limits to deal with). That isn’t to say that guest nodes can scale indefinitely, but it is known that guest nodes scale horizontally much further than cluster nodes." msgstr "" #. Tag: para #, no-c-format msgid "Other than the quorum limitation, these guest nodes behave just like cluster nodes with respect to resource management. The cluster is fully capable of managing and monitoring resources on each guest node. You can build constraints against guest nodes, put them in standby, or do whatever else you’d expect to be able to do with cluster nodes. They even show up in crm_mon output as nodes." msgstr "" #. Tag: para #, no-c-format msgid "To solidify the concept, below is an example that is very similar to an actual deployment we test in our developer environment to verify guest node scalability:" msgstr "" #. Tag: para #, no-c-format msgid "16 cluster nodes running the full corosync + pacemaker stack" msgstr "" #. Tag: para #, no-c-format msgid "64 Pacemaker-managed virtual machine resources running pacemaker_remote configured as guest nodes" msgstr "" #. Tag: para #, no-c-format msgid "64 Pacemaker-managed webserver and database resources configured to run on the 64 guest nodes" msgstr "" #. Tag: para #, no-c-format msgid "With this deployment, you would have 64 webservers and databases running on 64 virtual machines on 16 hardware nodes, all of which are managed and monitored by the same Pacemaker deployment. It is known that pacemaker_remote can scale to these lengths and possibly much further depending on the specific scenario." msgstr "" #. Tag: title #, no-c-format msgid "Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid " remote node noderemote node remote node " msgstr "" #. Tag: para #, no-c-format msgid "\"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer.\"" msgstr "" #. Tag: para #, no-c-format msgid "Ultimately, the primary advantage of remote nodes over cluster nodes is scalability. There are likely some other use cases related to geographically distributed HA clusters that remote nodes may serve a purpose in, but those use cases are not well understood at this point." msgstr "" #. Tag: para #, no-c-format msgid "Like guest nodes, remote nodes will never become the DC, initiate fencing actions or participate in quorum voting." msgstr "" #. Tag: para #, no-c-format msgid "That is not to say, however, that fencing of a remote node works any differently than that of a cluster node. The Pacemaker policy engine understands how to fence remote nodes. As long as a fencing device exists, the cluster is capable of ensuring remote nodes are fenced in the exact same way as cluster nodes." msgstr "" #. Tag: title #, no-c-format msgid "Expanding the Cluster Stack" msgstr "" #. Tag: para #, no-c-format msgid "With pacemaker_remote, the traditional view of the high-availability stack can be expanded to include a new layer:" msgstr "" #. Tag: title #, no-c-format msgid "Traditional HA Stack" msgstr "" #. Tag: title #, no-c-format msgid "HA Stack With Guest Nodes" msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot index e76f35b752..a20b5674e3 100644 --- a/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot +++ b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot @@ -1,767 +1,767 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Guest Node Walk-through" msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is: An in-depth walk-through of how to get Pacemaker to manage a KVM guest instance and integrate that guest into the cluster as a guest node." msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is not: A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of guest nodes as quickly as possible." msgstr "" #. Tag: title #, no-c-format msgid "Configure the Physical Host" msgstr "" #. Tag: para #, no-c-format msgid "For this example, we will use a single physical host named example-host. A production cluster would likely have multiple physical hosts, in which case you would run the commands here on each one, unless noted otherwise." msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Host" msgstr "" #. Tag: para #, no-c-format msgid "On the physical host, allow cluster-related services through the local firewall:" msgstr "" #. Tag: screen #, no-c-format msgid "# firewall-cmd --permanent --add-service=high-availability\n" "success\n" "# firewall-cmd --reload\n" "success" msgstr "" #. Tag: para #, no-c-format msgid "If you are using iptables directly, or some other firewall solution besides firewalld, simply open the following ports, which can be used by various clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405." msgstr "" #. Tag: para #, no-c-format msgid "If you run into any problems during testing, you might want to disable the firewall and SELinux entirely until you have everything working. This may create significant security issues and should not be performed on machines that will be exposed to the outside world, but may be appropriate during development and testing on a protected host." msgstr "" #. Tag: para #, no-c-format msgid "To disable security measures:" msgstr "" #. Tag: screen #, no-c-format msgid "[root@pcmk-1 ~]# setenforce 0\n" "[root@pcmk-1 ~]# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" "[root@pcmk-1 ~]# systemctl mask firewalld.service\n" "[root@pcmk-1 ~]# systemctl stop firewalld.service\n" "[root@pcmk-1 ~]# iptables --flush" msgstr "" #. Tag: title #, no-c-format msgid "Install Cluster Software" msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker corosync pcs resource-agents" msgstr "" #. Tag: title #, no-c-format msgid "Configure Corosync" msgstr "" #. Tag: para #, no-c-format msgid "Corosync handles pacemaker’s cluster membership and messaging. The corosync config file is located in /etc/corosync/corosync.conf. That config file must be initialized with information about the cluster nodes before pacemaker can start." msgstr "" #. Tag: para #, no-c-format msgid "To initialize the corosync config file, execute the following pcs command, replacing the cluster name and hostname as desired:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster setup --force --local --name mycluster example-host" msgstr "" #. Tag: para #, no-c-format msgid "If you have multiple physical hosts, you would execute the setup command on only one host, but list all of them at the end of the command." msgstr "" #. Tag: title #, no-c-format msgid "Configure Pacemaker for Remote Node Communication" msgstr "" #. Tag: para #, no-c-format msgid "Create a place to hold an authentication key for use with pacemaker_remote:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Generate a key:" msgstr "" #. Tag: screen #, no-c-format msgid "# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1" msgstr "" #. Tag: para #, no-c-format msgid "If you have multiple physical hosts, you would generate the key on only one host, and copy it to the same location on all hosts." msgstr "" #. Tag: title #, no-c-format msgid "Verify Cluster Software" msgstr "" #. Tag: para #, no-c-format msgid "Start the cluster" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster start" msgstr "" #. Tag: para #, no-c-format msgid "Verify corosync membership" msgstr "" #. Tag: literallayout #, no-c-format msgid "# pcs status corosync\n" "\n" "Membership information\n" "----------------------\n" " Nodeid Votes Name\n" " 1 1 example-host (local)" msgstr "" #. Tag: para #, no-c-format msgid "Verify pacemaker status. At first, the output will look like this:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "WARNING: no stonith devices and stonith-enabled is not false\n" "Last updated: Fri Oct 9 15:18:32 2015 Last change: Fri Oct 9 12:42:21 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: NONE\n" "1 node and 0 resources configured\n" "\n" "Node example-host: UNCLEAN (offline)\n" "\n" "Full list of resources:\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "After a short amount of time, you should see your host as a single node in the cluster:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "WARNING: no stonith devices and stonith-enabled is not false\n" "Last updated: Fri Oct 9 15:20:05 2015 Last change: Fri Oct 9 12:42:21 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition WITHOUT quorum\n" "1 node and 0 resources configured\n" "\n" "Online: [ example-host ]\n" "\n" "Full list of resources:\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format msgid "Disable STONITH and Quorum" msgstr "" #. Tag: para #, no-c-format msgid "Now, enable the cluster to work without quorum or stonith. This is required for the sake of getting this tutorial to work with a single cluster node." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs property set stonith-enabled=false\n" "# pcs property set no-quorum-policy=ignore" msgstr "" #. Tag: para #, no-c-format msgid "The use of stonith-enabled=false is completely inappropriate for a production cluster. It tells the cluster to simply pretend that failed nodes are safely powered off. Some vendors will refuse to support clusters that have STONITH disabled. We disable STONITH here only to focus the discussion on pacemaker_remote, and to be able to use a single physical host in the example." msgstr "" #. Tag: para #, no-c-format msgid "Now, the status output should look similar to this:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Oct 9 15:22:49 2015 Last change: Fri Oct 9 15:22:46 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "1 node and 0 resources configured\n" "\n" "Online: [ example-host ]\n" "\n" "Full list of resources:\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "Go ahead and stop the cluster for now after verifying everything is in order." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster stop --force" msgstr "" #. Tag: title #, no-c-format msgid "Install Virtualization Software" msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y kvm libvirt qemu-system qemu-kvm bridge-utils virt-manager\n" "# systemctl enable libvirtd.service" msgstr "" #. Tag: para #, no-c-format msgid "Reboot the host." msgstr "" #. Tag: para #, no-c-format msgid "While KVM is used in this example, any virtualization platform with a Pacemaker resource agent can be used to create a guest node. The resource agent needs only to support usual commands (start, stop, etc.); Pacemaker implements the remote-node meta-attribute, independent of the agent." msgstr "" #. Tag: title #, no-c-format msgid "Configure the KVM guest" msgstr "" #. Tag: title #, no-c-format msgid "Create Guest" msgstr "" #. Tag: para #, no-c-format msgid "We will not outline here the installation steps required to create a KVM guest. There are plenty of tutorials available elsewhere that do that. Just be sure to configure the guest with a hostname and a static IP address (as an example here, we will use guest1 and 192.168.122.10)." msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Guest" msgstr "" #. Tag: para #, no-c-format msgid "On each guest, allow cluster-related services through the local firewall, following the same procedure as in ." msgstr "" #. Tag: title #, no-c-format msgid "Verify Connectivity" msgstr "" #. Tag: para #, no-c-format msgid "At this point, you should be able to ping and ssh into guests from hosts, and vice versa." msgstr "" #. Tag: title #, no-c-format msgid "Configure pacemaker_remote" msgstr "" #. Tag: para #, no-c-format msgid "Install pacemaker_remote, and enable it to run at start-up. Here, we also install the pacemaker package; it is not required, but it contains the dummy resource agent that we will use later for testing." msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker pacemaker-remote resource-agents\n" "# systemctl enable pacemaker_remote.service" msgstr "" #. Tag: para #, no-c-format msgid "Copy the authentication key from a host:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker\n" "# scp root@example-host:/etc/pacemaker/authkey /etc/pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Start pacemaker_remote, and verify the start was successful:" msgstr "" #. Tag: screen #, no-c-format msgid "# systemctl start pacemaker_remote\n" "# systemctl status pacemaker_remote\n" "\n" " pacemaker_remote.service - Pacemaker Remote Service\n" " Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)\n" " Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago\n" " Main PID: 1233 (pacemaker_remot)\n" " CGroup: name=systemd:/system/pacemaker_remote.service\n" " └─1233 /usr/sbin/pacemaker_remoted\n" "\n" " Mar 14 18:24:04 guest1 systemd[1]: Starting Pacemaker Remote Service...\n" " Mar 14 18:24:04 guest1 systemd[1]: Started Pacemaker Remote Service.\n" " Mar 14 18:24:04 guest1 pacemaker_remoted[1233]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121." msgstr "" #. Tag: title #, no-c-format msgid "Verify Host Connection to Guest" msgstr "" #. Tag: para #, no-c-format msgid "Before moving forward, it’s worth verifying that the host can contact the guest on port 3121. Here’s a trick you can use. Connect using ssh from the host. The connection will get destroyed, but how it is destroyed tells you whether it worked or not." msgstr "" #. Tag: para #, no-c-format msgid "First add guest1 to the host machine’s /etc/hosts file if you haven’t already. This is required unless you have DNS setup in a way where guest1’s address can be discovered." msgstr "" #. Tag: screen #, no-c-format msgid "# cat << END >> /etc/hosts\n" "192.168.122.10 guest1\n" "END" msgstr "" #. Tag: para #, no-c-format msgid "If running the ssh command on one of the cluster nodes results in this output before disconnecting, the connection works:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 guest1\n" "ssh_exchange_identification: read: Connection reset by peer" msgstr "" #. Tag: para #, no-c-format msgid "If you see one of these, the connection is not working:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 guest1\n" "ssh: connect to host guest1 port 3121: No route to host" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 guest1\n" "ssh: connect to host guest1 port 3121: Connection refused" msgstr "" #. Tag: para #, no-c-format msgid "Once you can successfully connect to the guest from the host, shutdown the guest. Pacemaker will be managing the virtual machine from this point forward." msgstr "" #. Tag: title #, no-c-format msgid "Integrate Guest into Cluster" msgstr "" #. Tag: para #, no-c-format msgid "Now the fun part, integrating the virtual machine you’ve just created into the cluster. It is incredibly simple." msgstr "" #. Tag: title #, no-c-format msgid "Start the Cluster" msgstr "" #. Tag: para #, no-c-format msgid "On the host, start pacemaker." msgstr "" #. Tag: para #, no-c-format msgid "Wait for the host to become the DC. The output of pcs status should look as it did in ." msgstr "" #. Tag: title #, no-c-format msgid "Integrate as Guest Node" msgstr "" #. Tag: para #, no-c-format msgid "If you didn’t already do this earlier in the verify host to guest connection section, add the KVM guest’s IP address to the host’s /etc/hosts file so we can connect by hostname. For this example:" msgstr "" #. Tag: para #, no-c-format msgid "We will use the VirtualDomain resource agent for the management of the virtual machine. This agent requires the virtual machine’s XML config to be dumped to a file on disk. To do this, pick out the name of the virtual machine you just created from the output of this list." msgstr "" #. Tag: literallayout #, no-c-format msgid "# virsh list --all\n" " Id Name State\n" "----------------------------------------------------\n" " - guest1 shut off" msgstr "" #. Tag: para #, no-c-format msgid "In my case I named it guest1. Dump the xml to a file somewhere on the host using the following command." msgstr "" #. Tag: screen #, no-c-format msgid "# virsh dumpxml guest1 > /etc/pacemaker/guest1.xml" msgstr "" #. Tag: para #, no-c-format msgid "Now just register the resource with pacemaker and you’re set!" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create vm-guest1 VirtualDomain hypervisor=\"qemu:///system\" \\\n" " config=\"/etc/pacemaker/guest1.xml\" meta remote-node=guest1" msgstr "" #. Tag: para #, no-c-format msgid "This example puts the guest XML under /etc/pacemaker because the permissions and SELinux labeling should not need any changes. If you run into trouble with this or any step, try disabling SELinux with setenforce 0. If it works after that, see SELinux documentation for how to troubleshoot, if you wish to reenable SELinux." msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker will automatically monitor pacemaker_remote connections for failure, so it is not necessary to create a recurring monitor on the VirtualDomain resource." msgstr "" #. Tag: para #, no-c-format msgid "Once the vm-guest1 resource is started you will see guest1 appear in the pcs status output as a node. The final pcs status output should look something like this." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Oct 9 18:00:45 2015 Last change: Fri Oct 9 17:53:44 2015 by root via crm_resource on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "2 nodes and 2 resources configured\n" "\n" "Online: [ example-host ]\n" "GuestOnline: [ guest1@example-host ]\n" "\n" "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format msgid "Starting Resources on KVM Guest" msgstr "" #. Tag: para #, no-c-format msgid "The commands below demonstrate how resources can be executed on both the guest node and the cluster node." msgstr "" #. Tag: para #, no-c-format msgid "Create a few Dummy resources. Dummy resources are real resource agents used just for testing purposes. They actually execute on the host they are assigned to just like an apache server or database would, except their execution just means a file was created. When the resource is stopped, that the file it created is removed." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create FAKE1 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE2 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE3 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE4 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE5 ocf:pacemaker:Dummy" msgstr "" #. Tag: para #, no-c-format msgid "Now check your pcs status output. In the resource section, you should see something like the following, where some of the resources started on the cluster node, and some started on the guest node." msgstr "" #. Tag: screen #, no-c-format msgid "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE2 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE3 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE4 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host" msgstr "" #. Tag: para #, no-c-format msgid "The guest node, guest1, reacts just like any other node in the cluster. For example, pick out a resource that is running on your cluster node. For my purposes, I am picking FAKE3 from the output above. We can force FAKE3 to run on guest1 in the exact same way we would any other node." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs constraint location FAKE3 prefers guest1" msgstr "" #. Tag: para #, no-c-format msgid "Now, looking at the bottom of the pcs status output you’ll see FAKE3 is on guest1." msgstr "" #. Tag: screen #, no-c-format msgid "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE2 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE3 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE4 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host" msgstr "" #. Tag: title #, no-c-format msgid "Testing Recovery and Fencing" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker’s policy engine is smart enough to know fencing guest nodes associated with a virtual machine means shutting off/rebooting the virtual machine. No special configuration is necessary to make this happen. If you are interested in testing this functionality out, trying stopping the guest’s pacemaker_remote daemon. This would be equivalent of abruptly terminating a cluster node’s corosync membership without properly shutting it down." msgstr "" #. Tag: para #, no-c-format msgid "ssh into the guest and run this command." msgstr "" #. Tag: screen #, no-c-format msgid "# kill -9 `pidof pacemaker_remoted`" msgstr "" #. Tag: para #, no-c-format msgid "Within a few seconds, your pcs status output will show a monitor failure, and the guest1 node will not be shown while it is being recovered." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Oct 9 18:08:35 2015 Last change: Fri Oct 9 18:07:00 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "2 nodes and 7 resources configured\n" "\n" "Online: [ example-host ]\n" "\n" "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Stopped\n" " FAKE2 (ocf::pacemaker:Dummy): Stopped\n" " FAKE3 (ocf::pacemaker:Dummy): Stopped\n" " FAKE4 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host\n" "\n" "Failed Actions:\n" "* guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none',\n" " last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "A guest node involves two resources: the one you explicitly configured creates the guest, and Pacemaker creates an implicit resource for the pacemaker_remote connection, which will be named the same as the value of the remote-node attribute of the explicit resource. When we killed pacemaker_remote, it is the implicit resource that failed, which is why the failed action starts with guest1 and not vm-guest1." msgstr "" #. Tag: para #, no-c-format msgid "Once recovery of the guest is complete, you’ll see it automatically get re-integrated into the cluster. The final pcs status output should look something like this." msgstr "" #. Tag: screen #, no-c-format msgid "Cluster name: mycluster\n" "Last updated: Fri Oct 9 18:18:30 2015 Last change: Fri Oct 9 18:07:00 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "2 nodes and 7 resources configured\n" "\n" "Online: [ example-host ]\n" "GuestOnline: [ guest1@example-host ]\n" "\n" "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE2 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE3 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE4 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host\n" "\n" "Failed Actions:\n" "* guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none',\n" " last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "Normally, once you’ve investigated and addressed a failed action, you can clear the failure. However Pacemaker does not yet support cleanup for the implicitly created connection resource while the explicit resource is active. If you want to clear the failed action from the status output, stop the guest resource before clearing it. For example:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource disable vm-guest1 --wait\n" "# pcs resource cleanup guest1\n" "# pcs resource enable vm-guest1" msgstr "" #. Tag: title #, no-c-format msgid "Accessing Cluster Tools from Guest Node" msgstr "" #. Tag: para #, no-c-format msgid "Besides allowing the cluster to manage resources on a guest node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on guest nodes natively." msgstr "" #. Tag: para #, no-c-format msgid "Try it: Run crm_mon on the guest after pacemaker has integrated the guest node into the cluster. These tools just work. This means resource agents such as master/slave resources which need access to tools like crm_master work seamlessly on the guest nodes." msgstr "" #. Tag: para #, no-c-format msgid "Higher-level command shells such as pcs may have partial support on guest nodes, but it is recommended to run them from a cluster node." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Options.pot b/doc/Pacemaker_Remote/pot/Ch-Options.pot index 052ae16850..77a04cde59 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Options.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Options.pot @@ -1,232 +1,232 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Configuration Explained" msgstr "" #. Tag: para #, no-c-format msgid "The walk-through examples use some of these options, but don’t explain exactly what they mean or do. This section is meant to be the go-to resource for all the options available for configuring pacemaker_remote-based nodes. configuration " msgstr "" #. Tag: title #, no-c-format msgid "Resource Meta-Attributes for Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid "When configuring a virtual machine as a guest node, the virtual machine is created using one of the usual resource agents for that purpose (for example, ocf:heartbeat:VirtualDomain or ocf:heartbeat:Xen), with additional metadata parameters." msgstr "" #. Tag: para #, no-c-format msgid "No restrictions are enforced on what agents may be used to create a guest node, but obviously the agent must create a distinct environment capable of running the pacemaker_remote daemon and cluster resources. An additional requirement is that fencing the host running the guest node resource must be sufficient for ensuring the guest node is stopped. This means, for example, that not all hypervisors supported by VirtualDomain may be used to create guest nodes; if the guest can survive the hypervisor being fenced, it may not be used as a guest node." msgstr "" #. Tag: para #, no-c-format msgid "Below are the metadata options available to enable a resource as a guest node and define its connection parameters." msgstr "" #. Tag: title #, no-c-format msgid "Meta-attributes for configuring VM resources as guest nodes" msgstr "" #. Tag: entry #, no-c-format msgid "Option" msgstr "" #. Tag: entry #, no-c-format msgid "Default" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "remote-node" msgstr "" #. Tag: para #, no-c-format msgid "none" msgstr "" #. Tag: para #, no-c-format msgid "The node name of the guest node this resource defines. This both enables the resource as a guest node and defines the unique name used to identify the guest node. If no other parameters are set, this value will also be assumed as the hostname to use when connecting to pacemaker_remote on the VM. This value must not overlap with any resource or node IDs." msgstr "" #. Tag: para #, no-c-format msgid "remote-port" msgstr "" #. Tag: para #, no-c-format msgid "3121" msgstr "" #. Tag: para #, no-c-format msgid "The port on the virtual machine that the cluster will use to connect to pacemaker_remote." msgstr "" #. Tag: para #, no-c-format msgid "remote-addr" msgstr "" #. Tag: para #, no-c-format msgid "value of remote-node" msgstr "" #. Tag: para #, no-c-format msgid "The IP address or hostname to use when connecting to pacemaker_remote on the VM." msgstr "" #. Tag: para #, no-c-format msgid "remote-connect-timeout" msgstr "" #. Tag: para #, no-c-format msgid "60s" msgstr "" #. Tag: para #, no-c-format msgid "How long before a pending guest connection will time out." msgstr "" #. Tag: title #, no-c-format msgid "Connection Resources for Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid "A remote node is defined by a connection resource. That connection resource has instance attributes that define where the remote node is located on the network and how to communicate with it." msgstr "" #. Tag: para #, no-c-format msgid "Descriptions of these instance attributes can be retrieved using the following pcs command:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource describe remote\n" "ocf:pacemaker:remote - remote resource agent\n" "\n" "Resource options:\n" " server: Server location to connect to. This can be an ip address or hostname.\n" " port: tcp port to connect to.\n" " reconnect_interval: Interval in seconds at which Pacemaker will attempt to\n" " reconnect to a remote node after an active connection to\n" " the remote node has been severed. When this value is\n" " nonzero, Pacemaker will retry the connection\n" " indefinitely, at the specified interval. As with any\n" " time-based actions, this is not guaranteed to be checked\n" " more frequently than the value of the\n" " cluster-recheck-interval cluster option." msgstr "" #. Tag: para #, no-c-format msgid "When defining a remote node’s connection resource, it is common and recommended to name the connection resource the same as the remote node’s hostname. By default, if no server option is provided, the cluster will attempt to contact the remote node using the resource name as the hostname." msgstr "" #. Tag: para #, no-c-format msgid "Example defining a remote node with the hostname remote1:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create remote1 remote" msgstr "" #. Tag: para #, no-c-format msgid "Example defining a remote node to connect to a specific IP address and port:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create remote1 remote server=192.168.122.200 port=8938" msgstr "" #. Tag: title #, no-c-format msgid "Environment Variables for Daemon Start-up" msgstr "" #. Tag: para #, no-c-format msgid "Authentication and encryption of the connection between cluster nodes and nodes running pacemaker_remote is achieved using with TLS-PSK encryption/authentication over TCP (port 3121 by default). This means that both the cluster node and remote node must share the same private key. By default, this key is placed at /etc/pacemaker/authkey on each node." msgstr "" #. Tag: para #, no-c-format msgid "You can change the default port and/or key location for Pacemaker and pacemaker_remote via environment variables. How these variables are set varies by OS, but usually they are set in the /etc/sysconfig/pacemaker or /etc/default/pacemaker file." msgstr "" #. Tag: screen #, no-c-format msgid "#==#==# Pacemaker Remote\n" "# Use a custom directory for finding the authkey.\n" "PCMK_authkey_location=/etc/pacemaker/authkey\n" "#\n" "# Specify a custom port for Pacemaker Remote connections\n" "PCMK_remote_port=3121" msgstr "" #. Tag: title #, no-c-format msgid "Removing Remote Nodes and Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid "If the resource creating a guest node, or the ocf:pacemaker:remote resource creating a connection to a remote node, is removed from the configuration, the affected node will continue to show up in output as an offline node." msgstr "" #. Tag: para #, no-c-format msgid "If you want to get rid of that output, run (replacing $NODE_NAME appropriately):" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_node --force --remove $NODE_NAME" msgstr "" #. Tag: para #, no-c-format msgid "Be absolutely sure that there are no references to the node’s resource in the configuration before running the above command." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Revision_History.pot b/doc/Pacemaker_Remote/pot/Revision_History.pot index 33e99ff95f..e5aef3b9b2 100644 --- a/doc/Pacemaker_Remote/pot/Revision_History.pot +++ b/doc/Pacemaker_Remote/pot/Revision_History.pot @@ -1,74 +1,74 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-0500\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "MIME-Version: 1.0\n" "Content-Type: application/x-publican; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #, no-c-format msgid "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "David" msgstr "" #. Tag: surname #, no-c-format msgid "Vossel" msgstr "" #. Tag: member #, no-c-format msgid "Import from Pages.app" msgstr "" #. Tag: member #, no-c-format msgid "Added Future Features Section" msgstr "" #. Tag: member #, no-c-format msgid "Added Baremetal remote-node feature documentation" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Targeted CentOS 7.1 and Pacemaker 1.1.12+, updated for current terminology and practice" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Pacemaker 1.1.14" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Pacemaker 1.1.15" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Pacemaker 1.1.16" msgstr ""