From Fedora Project Wiki
< Features
It has been requested that this page be deleted.
Except for pacemaker inclusion, this Feature page is just a repeat of the cluster capabilities in Fedora 11 and is not needed.
Except for pacemaker inclusion, this Feature page is just a repeat of the cluster capabilities in Fedora 11 and is not needed.
Cluster
Summary
This is a significant update to the clustering stack - both for high availability and load balancing.
Owner
- Name: LonHohberger
- email: lhh@redhat.com
- Name: FabioMassimoDiNitto
- email: fabbione@redhat.com
Current status
- Targeted release: Fedora 40
- Last updated: 24 Jan 2012
- Percentage of completion: 70%
Detailed Description
Upstream has been developing the new version of the stack. 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 (50% complete)
- Convergence on a single set of resource agents from the Linux clustering community
- Enhanced fencing support in the Pacemaker Cluster Resource Manager
- Separation of GFS2-specific utilities in to a separate project.
Note that this transition includes deprecations:
- CMAN will no longer provide quorum. Instead, this functionality is now part of Corosync
- Removal of the obsolete 'rgmanager' package. All users are advised to use Pacemaker for their failover needs.
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
How To Test
User Experience
Dependencies
- corosync (2.0)
- pacemaker
- cluster-glue
- dlm (in review)
All packagers and upstreams have been informed upfront and worked together to achieve this goal.
Contingency Plan
None necessary
Documentation
Release Notes
- The update to version 2.0 (needle) of the Corosync Cluster Engine offers:
- Plugin ABI & API stability guarantees for the duration of Corosync 2.0's lifetime
- High performance, cluster-wide messaging
- Improved quorum subsystem
- Improved configuration management
- The update to version 1.1.7 of the Pacemaker Cluster Resource Manager offers:
- Improved fencing subsystem which can be used in either GFS2 standalone environments or resource-driven clusters (which may or may not include GFS2)
- Improved logging via the libqb framework