(Created page with "= FedFS <!-- The name of your feature --> = == Summary == <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall ...") |
(→Owner) |
||
| Line 7: | Line 7: | ||
== Owner == | == Owner == | ||
<!--This should link to your home wiki page so we know who you are--> | <!--This should link to your home wiki page so we know who you are--> | ||
* Name: [[User: | * Name: [[User:JeffLayton| Jeff Layton]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved--> | <!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved--> | ||
Revision as of 17:00, 31 August 2011
FedFS
Summary
RFC 5716 introduces the Federated File System (FedFS, for short). FedFS is an extensible standardized mechanism by which system administrators construct a coherent namespace across multiple file servers using file system referrals.
Owner
- Name: Jeff Layton
- Email: jlayton@redhat.com
Current status
- Targeted release: Fedora 17
- Last updated: August 31, 2011
- Percentage of completion: 10%
Detailed Description
RFC 5716 introduces the Federated File System (FedFS, for short). FedFS is an extensible standardized mechanism by which system administrators construct a coherent namespace across multiple file servers using file system referrals.
A file system referral is like a symbolic link to another file system share, but it is not visible to applications. It behaves like an automounted directory where a new file system mount is done when an application first accesses that directory. The arguments of the mount operation are controlled by information returned by the file server.
Today, file system referral mechanisms exist in several network file system protocols. FedFS provides its namespace features by leveraging referral mechanisms already built in to network file system protocols. Thus no change to file system protocols or clients is required.
Currently, the Linux FedFS implementation supports only NFS version 4 referrals. More on NFS version 4 referrals can be found in RFC 3530. FedFS may support other network file system protocols in the future.
Benefit to Fedora
See detailed description. As this is an emerging standard, we want Fedora to be one of the first operating systems to support it.
Scope
Much of the work for this has already been done. Chuck Lever of Oracle has done an implementation of the required userspace tools for this. He's also pushing for the upstream inclusion of the required kernel patches. With luck, those will make 3.2. We'll probably also need to do some documentation and/or articles describing how to set up both the client and server for FedFS.
How To Test
(FIXME: Make this less skeletal)
- set up fedfs domain and server(s)
- set up fedfs clients
- test that fedfs referrals work
User Experience
The casual Fedora user won't see any changes with this. This should only change the experience for someone who makes the effort to set up and use FedFS.
Dependencies
Contingency Plan
If this can't be completed in time, we simply won't ship with FedFS enabled, or may just ship the client side pieces initially.
Documentation
No upstream docs yet. We'll probably need to create some.
Release Notes
- We'll probably just want to mention that this release supports FedFS.