pacemaker/doc/Pacemaker_Explained/pot/Ap-FAQ.pot

# 
# AUTHOR <EMAIL@ADDRESS>, 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"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#, no-c-format
msgid "FAQ"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Why is the Project Called Pacemaker?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Pacemaker</primary> </indexterm> First of all, the reason it’s not called the CRM is because of the abundance of terms <footnote><para><ulink url=\"http://en.wikipedia.org/wiki/CRM\">http://en.wikipedia.org/wiki/CRM</ulink></para></footnote> that are commonly abbreviated to those three letters. The Pacemaker name came from Kham, <footnote><para><ulink url=\"http://khamsouk.souvanlasy.com/\">http://khamsouk.souvanlasy.com/</ulink></para></footnote> a good friend of Pacemaker developer Andrew Beekhof’s, and was originally used by a Java GUI that Beekhof was prototyping in early 2007. Alas, other commitments prevented the GUI from progressing much and, when it came time to choose a name for this project, Lars Marowsky-Bree suggested it was an even better fit for an independent CRM. The idea stems from the analogy between the role of this software and that of the little device that keeps the human heart pumping. Pacemaker monitors the cluster and intervenes when necessary to ensure the smooth operation of the services it provides. There were a number of other names (and acronyms) tossed around, but suffice to say \"Pacemaker\" was the best."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Why was the Pacemaker Project Created?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The decision was made to spin-off the CRM into its own project after the 2.1.3 Heartbeat release in order to:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "support both the Corosync and Heartbeat cluster stacks equally"
msgstr ""

#. Tag: para
#, no-c-format
msgid "decouple the release cycles of two projects at very different stages of their life-cycles"
msgstr ""

#. Tag: para
#, no-c-format
msgid "foster clearer package boundaries, thus leading to better and more stable interfaces"
msgstr ""

#. Tag: para
#, no-c-format
msgid "What Messaging Layers are Supported?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Messaging Layers</primary> </indexterm>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://www.corosync.org/\">Corosync</ulink>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<ulink url=\"http://linux-ha.org/\">Heartbeat</ulink>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Can I Choose Which Messaging Layer to Use at Run Time?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Yes. The CRM will automatically detect which started it and behave accordingly."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Can I Have a Mixed Heartbeat-Corosync Cluster?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "No."
msgstr ""

#. Tag: para
#, no-c-format
msgid "<anchor id=\"q-messaging-layer\" xreflabel=\"[q-messaging-layer]\"></anchor> Which Messaging Layer Should I Choose?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Cluster</primary><secondary>Choosing Between Heartbeat and Corosync</secondary> </indexterm> <indexterm> <primary>Choosing Between Heartbeat and Corosync</primary> </indexterm> <indexterm> <primary>Cluster Stack</primary><secondary>Corosync</secondary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm> <indexterm> <primary>Corosync</primary> </indexterm> <indexterm> <primary>Cluster Stack</primary><secondary>Heartbeat</secondary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm> <indexterm> <primary>Heartbeat</primary> </indexterm> You can choose from multiple messaging layers, including heartbeat, corosync 1 (with or without CMAN), and corosync 2. Corosync 2 is the current state of the art due to its more advanced features and better support for pacemaker, but often the best choice is to use whatever comes with your Linux distribution, and follow the distribution’s setup instructions."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Where Can I Get Pre-built Packages?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Most major Linux distributions have pacemaker packages in their standard package repositories. See the <ulink url=\"http://clusterlabs.org/wiki/Install\">Install wiki page</ulink> for details."
msgstr ""

#. Tag: para
#, no-c-format
msgid "What Versions of Pacemaker Are Supported?"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Some Linux distributions (such as Red Hat Enterprise Linux and SUSE Linux Enterprise) offer technical support for their customers; contact them for details of such support. For help within the community (mailing lists, IRC, etc.) from Pacemaker developers and users, refer to the <ulink url=\"http://clusterlabs.org/wiki/Releases\">Releases wiki page</ulink> for an up-to-date list of versions considered to be supported by the project. When seeking assistance, please try to ensure you have one of these versions."
msgstr ""