diff --git a/html/pacemaker/doc/deprecated/build-1.1.txt b/html/pacemaker/doc/deprecated/build-1.1.txt index 7ffa1d7..ea1d55b 100644 --- a/html/pacemaker/doc/deprecated/build-1.1.txt +++ b/html/pacemaker/doc/deprecated/build-1.1.txt @@ -1,2 +1,2 @@ -Requires Corosync 2.x
+Requires Corosync 2.x or greater
Generated on Tue Jul 10 20:30:09 EST 2012 from version: 7201d5d (HEAD, master) diff --git a/html/pacemaker/doc/deprecated/desc-1.1-crmsh.txt b/html/pacemaker/doc/deprecated/desc-1.1-crmsh.txt index 702ab75..ace8c11 100644 --- a/html/pacemaker/doc/deprecated/desc-1.1-crmsh.txt +++ b/html/pacemaker/doc/deprecated/desc-1.1-crmsh.txt @@ -1 +1 @@ -Requires Corosync 2.x and optimized for the crmsh CLI +Requires Corosync 2.x or greater; optimized for the crmsh CLI diff --git a/html/pacemaker/doc/deprecated/title-1.1-crmsh.txt b/html/pacemaker/doc/deprecated/title-1.1-crmsh.txt index f4989f1..fc2dd6e 100644 --- a/html/pacemaker/doc/deprecated/title-1.1-crmsh.txt +++ b/html/pacemaker/doc/deprecated/title-1.1-crmsh.txt @@ -1 +1 @@ -Pacemaker 1.1 for Corosync 2.x and crmsh +Pacemaker 1.1 for Corosync 2.x or greater and crmsh diff --git a/src/faq.html b/src/faq.html index 8ac5ed4..74b140c 100644 --- a/src/faq.html +++ b/src/faq.html @@ -1,141 +1,133 @@ --- layout: default title: FAQ ---

Frequently Asked Questions

Q: Where can I get Pacemaker?

A: Pacemaker ships as part of most modern distributions, so you can usually just launch your favorite package manager on:

If all else fails, you can try installing from source.

Q: Is there any documentation?

A: Yes. You can find the set relevant to your version in our documentation index.

Q: Where should I ask questions?

A: Often basic questions can be answered on irc, but sending them to the mailing list is always a good idea so that everyone can benefit from the answer.

Q: Do I need shared storage?

A: No. We can help manage it if you have some, but Pacemaker itself has no need for shared storage.

Q: Which cluster filesystems does Pacemaker support?

A: Pacemaker supports the popular OCFS2 and GFS2 filesystems. As you'd expect, you can use them on top of real disks or network block devices like DRBD.

Q: What kind of applications can I manage with Pacemaker?

A: Pacemaker is application agnostic, meaning anything that can be scripted can be made highly available - provided the script conforms to one of the supported standards: LSB, OCF, Systemd, or Upstart.

Q: Can I use Pacemaker with Heartbeat?

-

A: Yes. Pacemaker started off life as part - of the Heartbeat project and continues to support it as an - alternative to Corosync. See - this documentation for more details

- +

A: Only Pacemaker versions less than 2.0.0. See + this documentation for details.

Q: Can I use Pacemaker with CMAN?

-

A: Yes. Pacemaker added support - for CMAN - v3 in version 1.1.5 to better integrate with distros - that have traditionally shipped and/or supported the RHCS - cluster stack instead of Pacemaker. This is particularly - relevant for those looking to use GFS2 or OCFS2. See +

A: Only Pacemaker versions greater than or equal to + 1.1.5 and less than 2.0.0. See the documentation - for more details

+ for details

Q: Can I use Pacemaker with Corosync 1.x?

-

A: Yes. You will need to configure - Corosync to load Pacemaker's custom plugin to provide the - membership and quorum information we require. See - the documentation for more details.

- -

Q: Can I use Pacemaker with Corosync 2.x?

-

A: Yes. Pacemaker can obtain the - membership and quorum information it requires directly from - Corosync in this configuration. See - the documentation for more details.

+

A: Only Pacemaker versions less than 2.0.0. You will need to configure + Corosync to load Pacemaker's custom plugin. See + the documentation for details.

+ +

Q: Can I use Pacemaker with Corosync 2.x or greater?

+

A: Yes. This is the only option supported by + Pacemaker 2.0.0 and greater. See the documentation + for details.

Q: Do I need a fencing device?

A: Yes. Fencing is the only 100% reliable way to ensure the integrity of your data and that applications are only active on one host. Although Pacemaker is technically able to function without Fencing, there are a good reasons SUSE and Red Hat will not support such a configuration.

Q: Do I need to know XML to configure Pacemaker?

A: No. Although Pacemaker uses XML as its native configuration format, there exist 2 CLIs and at least 4 GUIs that present the configuration in a human friendly format.

Q: How do I synchronize the cluster configuration?

A: Any changes to Pacemaker's configuration are automatically replicated to other machines. The configuration is also versioned, so any offline machines will be updated when they return.

Q: Should I choose pcs or crmsh?

A: Arguably the best advice is to use whichever one comes with your distro. This is the one that will be tailored to that environment, receive regular bugfixes and feature in the documentation.

Of course, for years people have been side-loading all of Pacemaker onto enterprise distros that didn't ship it, so doing the same for just a configuration tool should be easy if your favorite distro does not ship your favorite tool.

Q: What if my question isn't here?

A: See the getting help section and let us know!

diff --git a/src/quickstart.html b/src/quickstart.html index 276fe26..9ae9a9a 100644 --- a/src/quickstart.html +++ b/src/quickstart.html @@ -1,87 +1,71 @@ --- layout: pacemaker title: Quickstart ---

Quickstart

{% include quickstart-common.html %}

Quickstart Editions

We have a quickstart edition for each major distro. To continue, select the distribution you'll be using:

Why Does Each Distribution Have its Own Quickstart?

- Instead of re-inventing the wheel, Pacemaker makes use of - the messaging, membership and quorum capabilities of other - projects (such as Heartbeat or Corosync). + Now that all distributions have standardized on Corosync 2 or + greater as the underlying cluster layer, the differences are + minimal.

- Pacemaker is fully functional with all three current - Corosync release series (1.2.x, 1.4.x and 2.0.x) as well - as Heartbeat. However this has been a source of confusion - because Pacemaker needs to be set up differently depending - on what each distribution ships. We call each combination - of Pacemaker + Corosync (or Heartbeat) a "stack". + However, in the past, Pacemaker also supported Corosync 1 (with or + without CMAN) as well as Heartbeat. Different distributions + supported different cluster layers, requiring different set-up. + We call each combination of Pacemaker and cluster layer a "stack".

For example, on RHEL6 the supported stack is based on CMAN which has APIs Pacemaker can use to obtain the membership and quroum information it needs. Although CMAN uses Corosync underneath, it is configured via cluster.conf and Pacemaker is started as a separate init script.

However SLES11 doesn't ship CMAN, so its users configure corosync.conf directly and enable a custom plugin that gets loaded into Corosync (because Corosync 1.4 doesn't have the quorum and membership APIs needed by Pacemaker). This plugin also starts Pacemaker automatically when Corosync is started.

To confuse things further, SLES users start Corosync with the openAIS init script because it used to be part of that project.

-

- Eventually everyone will move to Corosync 2 which removes - support for CMAN and custom plugins BUT natively includes - the APIs Pacemaker needs for quorum and membership. In - this case, users would configure corosync.conf and use the - Pacemaker init-script to start up after Corosync. -

-

- There are some architectural differences between the - different stacks, and some are more elegant than others, - but the most important thing by far is that everyone is - getting membership and quorum information from the same - place. -

See this post for a longer discussion on the different stack options and how they relate to cluster filesystems in particular.