#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2018-05-14 18:03-0500\n"
"PO-Revision-Date: 2018-05-14 18:03-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#, no-c-format
msgid "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 "Pacemaker was spun off from an earlier project called <ulink url=\"http://linux-ha.org/\">Heartbeat</ulink>, which combined a cluster layer and a cluster resource manager. The CRM was made into its own project, Pacemaker, in order to:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "support both the Corosync and Heartbeat cluster stacks equally (Heartbeat support was dropped in Pacemaker 2.0, as the project had faded out by then)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "decouple the release cycles of the cluster layer and the cluster resource manager 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> version 2 and greater"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Historically, Pacemaker 1 also supported Corosync version 1 (with either CMAN or a pacemaker plugin) and Heartbeat. Support for these legacy stacks was dropped with Pacemaker 2.0."
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 ""