< Features
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
== Current status == | == Current status == | ||
* Targeted release: [[ | * Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]] | ||
* Last updated: (04/02/2009) | * Last updated: (04/02/2009) | ||
* Percentage of completion: 90% | * Percentage of completion: 90% | ||
| Line 69: | Line 69: | ||
== 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. --> | ||
The GFS2 filesystem allows sharing of a filesystem across multiple nodes in an HA environment. | |||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
This feature depends on the cman package, which | This feature depends on the cman package, the corosync package and the dlm kernel module, which are already part of Fedora. | ||
== Contingency Plan == | == Contingency Plan == | ||
| Line 82: | Line 84: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* [http://en.wikipedia.org/wiki/Red_Hat_Cluster_Suite Cluster Suite] on Wikipedia | |||
* [http://en.wikipedia.org/wiki/Global_File_System GFS/GFS2] on Wikipedia | |||
== Release Notes == | == Release Notes == | ||
Revision as of 10:24, 4 February 2009
Feature Name
A stable version of the GFS2 cluster filesystem
Summary
A cluster filesystem allowing simultaneous access to shared storage from multiple nodes, designed for SAN environments. It is also possible to use GFS2 as a single node (local) filesystem by selecting the lock_nolock lock "module".
Owner
- Name: Steven Whitehouse
- email: <swhiteho@redhat.com>
- mailing list: <cluster-devel@redhat.com>
Current status
- Targeted release: Fedora 40
- Last updated: (04/02/2009)
- Percentage of completion: 90%
Detailed Description
GFS2 is part of the upstream kernel, but is still listed as experimental. The plan is that this will become stable before the release of F-11. Also the gfs2-utils package is part of Fedora already, and again we hope to declare this stable before F-11.
Benefit to Fedora
The main benefit is a stable cluster filesystem which works seamlessly with the Red Hat cluster infrastructure.
Scope
Most of the remaining work now is testing and bug fixing.
How To Test
Read the docs, create a filesystem, run an application on it, check to see whether there are any problems/bugs and if so report them via the usual bugzilla process.
We will also be running the Red Hat QE tests, some performance tests and basically anything else that we can get our hands on in order to try and cover as many possible tests as possible. Any filesystem test suite would be a good thing to test with, whether for performance or correctness. We also want to see lots of testing with real applications, Apache, Samba, NFS (over GFS2), exim, sendmail, yourfavouriteapplicationhere, etc. Basically anything that uses the filesystem.
You don't need any special hardware to do single node tests - you can create a filesystem in a single file and mount it loopback. For multiple node tests you will need some shared storage (iSCSI, FC, or some other kind of SAN) plus a method of fencing failed nodes (this can be done manually if you don't have any fencing hardware, but power switches and/or remote access controllers are recommended).
If everything is working correctly, the results should be exactly the same as you'd expect running the application on a local filesystem. One point to watch though is that many applications are not written to run in a clustered environment, so if you are expecting multiple copies of an application to share the same set of data files, then please check that the application does support this mode of operation first. Usually it will require some method for inter-node communication at the application level.
User Experience
The GFS2 filesystem allows sharing of a filesystem across multiple nodes in an HA environment.
Dependencies
This feature depends on the cman package, the corosync package and the dlm kernel module, which are already part of Fedora.
Contingency Plan
If this is not ready in time, we can just push out that date at which we consider GFS2 stable. There are no other packages at the moment which depend on this feature.
Documentation
- Cluster Suite on Wikipedia
- GFS/GFS2 on Wikipedia
Release Notes
Comments and Discussion