Upstream has been developing the new version of the stack with several goals in mind, including better scalability, higher performance, increased reliability, more hardware support. The updated release lays down the path of better integration with other cluster solutions (such as [http://www.linux-ha.org heartbeat], [http://oss.oracle.com/projects/ocfs2/ OCFS2], and [http://www.clusterlabs.org pacemaker]) by sharing the same core components.

+

Upstream has been developing a new version of the cluster stack which is currently shipped with Fedora 16. The major features are:

+

* Improved quorum subsystem which is integrated in to the Corosync Cluster Engine (95% complete)

+

* A new command-line interface for administration of both the Corosync Cluster Engine and the Pacemaker Cluster Resource Manager as well as monitoring (50% complete)

+

* Convergence on a single set of resource agents from the Linux clustering community

+

* Enhanced fencing support provided by stonith-ng, which is part of the Pacemaker project.

+

* Separation of GFS2-specific utilities in to a separate project (100%)

* The rgmanager package. All users are advised to use Pacemaker for their failover needs.

+

* The openais package. This provided some of the SA Forum AIS APIs, which were rarely used.

+

* The heartbeat package. Upstream development has stopped and equivalent or superior functionality is provided by the [http://corosync.org Corosync] package.

+

* The piranha package. Superior functionality is provided by the [http://keepalived.org Keepalived] package.

+

* The ricci package. Similar agent-style communication can be provided by Matahari or other projects.

+

* The luci package. This will be replaced by Sunzi, although it is not clear this part will make Fedora 17.

+

* The clustermon package. This was part of the ricci/luci administration stack and is no longer required.

+

* Several agents in the resource-agents package which previously relied on examination of cluster.conf at run-time.

== Benefit to Fedora ==

== Benefit to Fedora ==

−

The increased reliability and versatility of the cluster components included in Fedora 12 allow administrators to deploy Fedora in environments where greater availability and clustered file systems are required.

+

The increased reliability and versatility of the cluster components included in Fedora 17 allow administrators to deploy Fedora in environments where greater availability and clustered file systems are required.

<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->

<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->

+

Removal of rgmanager matches the capabilities offered by several other Linux distributions and allows the Fedora community to consort efforts on a single failover stack.

== Scope ==

== Scope ==

<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->

<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->

+

This change impacts several utilities and other applications, including:

+

* The DLM, which used AIS Checkpoints to replicate data about POSIX locks (100% complete)

+

* Clustered LVM, which used CMAN APIs, will need to be ported to corosync. (?% complete)

+

* Fence-virt, which used CMAN APIs and AIS Checkpoints, will need to be ported to corosync. (0% complete)

+

* Pacemaker, which used CMAN APIs, will need to be ported to corosync (100% complete)

+

* Clustered mirroring, which uses AIS Checkpoints will need to be ported to corosync (?% complete)

+

* QPid, which used CMAN APIs, will need to be ported to corosync (?% complete)

== How To Test ==

== How To Test ==

Line 42:

Line 65:

3. What are the expected results of those actions?

3. What are the expected results of those actions?

-->

-->

+

The initial use cases required for high availability are documented in the [http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ Clusters from Scratch] manual.

+

+

Information about how to run GFS2 in standalone mode will be provided as development nears completion.

== User Experience ==

== User Experience ==

<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. -->

<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. -->

+

Some differences will be noticeable by users:

+

* Users of the rgmanager package will need to learn the Pacemaker package, which is a more dynamic, complex, full-featured cluster resource manager.

+

* Users who relied on cluster.conf (whether using ccs, luci, or hand-editing) will need to learn:

+

** The crm and/or pcs commands and become familiar with the CIB, which is an XML database of the failover resource configuration combined with some run-time state information.

+

** The layout, syntax, and use of corosync.conf

+

* Users who relied on the clustat command will need to learn the following commands:

+

** cibadmin

+

** crm_mon

+

** crm_resource

== Dependencies ==

== Dependencies ==

−

* lvm2-cluster

+

* corosync (2.0)

−

* asterisk (openais plugin)

+

−

* qpidc (corosync libcpg user)

+

* pacemaker

* pacemaker

* cluster-glue

* cluster-glue

+

* dlm (in review currently)

+

* libqb

+

* pcs (in review currently)

All packagers and upstreams have been informed upfront and worked together to achieve this goal.

All packagers and upstreams have been informed upfront and worked together to achieve this goal.

The rgmanager package. All users are advised to use Pacemaker for their failover needs.

The openais package. This provided some of the SA Forum AIS APIs, which were rarely used.

The heartbeat package. Upstream development has stopped and equivalent or superior functionality is provided by the Corosync package.

The piranha package. Superior functionality is provided by the Keepalived package.

The ricci package. Similar agent-style communication can be provided by Matahari or other projects.

The luci package. This will be replaced by Sunzi, although it is not clear this part will make Fedora 17.

The clustermon package. This was part of the ricci/luci administration stack and is no longer required.

Several agents in the resource-agents package which previously relied on examination of cluster.conf at run-time.

Benefit to Fedora

The increased reliability and versatility of the cluster components included in Fedora 17 allow administrators to deploy Fedora in environments where greater availability and clustered file systems are required.
Removal of rgmanager matches the capabilities offered by several other Linux distributions and allows the Fedora community to consort efforts on a single failover stack.

Scope

This change impacts several utilities and other applications, including:

The DLM, which used AIS Checkpoints to replicate data about POSIX locks (100% complete)

Clustered LVM, which used CMAN APIs, will need to be ported to corosync. (?% complete)

Fence-virt, which used CMAN APIs and AIS Checkpoints, will need to be ported to corosync. (0% complete)

Pacemaker, which used CMAN APIs, will need to be ported to corosync (100% complete)

Clustered mirroring, which uses AIS Checkpoints will need to be ported to corosync (?% complete)

QPid, which used CMAN APIs, will need to be ported to corosync (?% complete)

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.