diff --git a/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt b/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt deleted file mode 100644 index b89bf4af04..0000000000 --- a/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt +++ /dev/null @@ -1,60 +0,0 @@ -:compat-mode: legacy -[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?:: - - Pacemaker was spun off from an earlier project called - http://linux-ha.org/[Heartbeat], which combined a cluster layer and a cluster - resource manager. The CRM was made into its own project, Pacemaker, in order to: - - * 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) - * decouple the release cycles of the cluster layer and the cluster resource - manager 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] version 2 and greater - * 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. - -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/Pacemaker_Explained.xml b/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml index 9ad6e3561a..31bb67675d 100644 --- a/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml +++ b/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml @@ -1,39 +1,26 @@ - - - Further Reading - - Project Website: - Project Documentation: - - SUSE High Availibility Guide: - - Corosync Configuration: - - -