diff --git a/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt b/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt new file mode 100644 index 0000000000..98e62ad2f4 --- /dev/null +++ b/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt @@ -0,0 +1,81 @@ +[appendix] + +[[ap-faq]] +== FAQ == + + +[qanda] +Why is the Project Called Pacemaker?:: + indexterm:[Pacemaker] + First of all, the reason it's not called the CRM is because of the abundance + of terms footnote:[http://en.wikipedia.org/wiki/CRM] that are commonly + abbreviated to those three letters. The Pacemaker name came from Kham, + footnote:[http://khamsouk.souvanlasy.com/] 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. + +Why was the Pacemaker Project Created?:: + + The decision was made to spin-off the CRM into its own project after the 2.1.3 + Heartbeat release in order to: + + * support both the Corosync and Heartbeat cluster stacks equally + * decouple the release cycles of two projects at very different stages of their life-cycles + * foster clearer package boundaries, thus leading to better and more stable interfaces + +What Messaging Layers are Supported?:: + indexterm:[Messaging Layers] + + * http://www.corosync.org/[Corosync] + * http://linux-ha.org/[Heartbeat] + +Can I Choose Which Messaging Layer to Use at Run Time?:: + + Yes. The CRM will automatically detect which started it and behave accordingly. + +Can I Have a Mixed Heartbeat-Corosync Cluster?:: + + No. + +Which Messaging Layer Should I Choose?:: + indexterm:[Cluster,Choosing Between Heartbeat and Corosync] + indexterm:[Cluster Stack,Corosync] indexterm:[Corosync] + indexterm:[Cluster Stack,Heartbeat] indexterm:[Heartbeat] + Ultimately the choice of cluster stack is a personal decision that + must be made in the context of you or your company's needs and + strategic direction. Pacemaker functions equally well with + heartbeat or corosync. Here are some factors that may influence the decision: + + * SUSE, Red Hat and Oracle are all putting their collective + weight behind the Corosync cluster stack. + * Using Corosync gives your applications access to the following + additional cluster services: + ** distributed locking service + ** extended virtual synchronization service + ** cluster closed process group service + * It is likely that Pacemaker, at some point in the future, will make + use of some of these additional services not provided by Heartbeat. + +Where Can I Get Pre-built Packages?:: + + Most major Linux distributions have pacemaker packages in their standard + package repositories. See the http://clusterlabs.org/wiki/Install[Install wiki + page] for details. + +What Versions of Pacemaker Are Supported?:: + + 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 http://clusterlabs.org/wiki/Releases[Releases wiki page] + 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. diff --git a/doc/Pacemaker_Explained/en-US/Ap-FAQ.xml b/doc/Pacemaker_Explained/en-US/Ap-FAQ.xml deleted file mode 100644 index 9e6d69f4c3..0000000000 --- a/doc/Pacemaker_Explained/en-US/Ap-FAQ.xml +++ /dev/null @@ -1,95 +0,0 @@ - <appendix id="ap-faq"> - <title>FAQ</title> - <qandaset defaultlabel="qanda"> - <qandadiv> - <title>History</title> - <qandaentry> - <question> - <para>Why is the Project Called <indexterm significance="preferred"><primary>Pacemaker</primary><secondary>naming</secondary></indexterm>Pacemaker?</para> - </question> - <answer> - <para>First of all, the reason its not called the CRM is because of the abundance of terms<footnote><para><ulink url="http://en.wikipedia.org/wiki/CRM"/></para></footnote> that are commonly abbreviated to those three letters.</para> - <para> - The Pacemaker name came from Kham<footnote><para><ulink url="http://khamsouk.souvanlasy.com/"/></para></footnote>, a good friend of mine, and was originally used by a Java GUI that I was prototyping in early 2007. - Alas other commitments have prevented the GUI from progressing much and, when it came time to choose a name for this project, Lars suggested it was an even better fit for an independent CRM. - </para> - <para> - 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. - </para> - <para>There were a number of other names (and acronyms) tossed around, but suffice to say "Pacemaker" was the best</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>Why was the Pacemaker Project Created?</para> - </question> - <answer> - <para>The decision was made to spin-off the CRM into its own project after the 2.1.3 Heartbeat release in order to - <itemizedlist spacing="compact"> - <listitem><para>support both the Corosync and Heartbeat cluster stacks equally</para></listitem> - <listitem><para>decouple the release cycles of two projects at very different stages of their life-cycles</para></listitem> - <listitem><para>foster the clearer package boundaries, thus leading to</para></listitem> - <listitem><para>better and more stable interfaces</para></listitem> - </itemizedlist></para> - </answer> - </qandaentry> - </qandadiv> - <qandadiv> - <title>Setup</title> - <qandaentry> - <question> - <para>What <indexterm significance="preferred"><primary>Messaging Layers </primary></indexterm>Messaging Layers are Supported?</para> - </question> - <answer> - <itemizedlist spacing="compact"> - <listitem><para>Corosync (<ulink url="http://www.corosync.org/"/>)</para></listitem> - <listitem><para>Heartbeat (<ulink url="http://linux-ha.org/"/>)</para></listitem> - </itemizedlist> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>Can I Choose which Messaging Layer to use at Run Time?</para> - </question> - <answer> - <para>Yes. The CRM will automatically detect which started it and behave accordingly.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>Can I Have a Mixed Heartbeat-Corosync Cluster?</para> - </question> - <answer> - <para>No.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>Which Messaging Layer Should I Choose?</para> - </question> - <answer> - <para>This is discussed in <xref linkend="ap-install"/>.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>Where Can I Get Pre-built Packages?</para> - </question> - <answer> - <para>Official packages for most major .rpm and based distributions are available from the ClusterLabs Website<footnote><para><ulink url="http://www.clusterlabs.org/rpm"/></para></footnote>.</para> - <para>For Debian packages, building from source and details on using the above repositories, see our installation page<footnote><para><ulink url="http://clusterlabs.org/wiki/Install"/></para></footnote>.</para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para>What Versions of Pacemaker Are Supported?</para> - </question> - <answer> - <para>Please refer to the Releases page<footnote><para><ulink url="http://clusterlabs.org/wiki/Releases"/></para></footnote> for an up-to-date list of versions supported directly by the project.</para> - <para>When seeking assistance, please try to ensure you have one of these versions.</para> - </answer> - </qandaentry> - </qandadiv> - </qandaset> - </appendix>