From Fedora Project Wiki
m (Removing QA category)
Line 6: Line 6:
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->


= Feature Name =
= NFSv4Default =
<!-- The name of your feature -->


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
Changed the default NFS protocol to version 4.


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[steved | Steve Dickson]]
* Name: [[User:FASAcountName| Your Name]]


<!-- 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-->
* email: steved@redhat.com
* email: <your email address so we can contact you, invite you to meetings, etc.>


== Current status ==
== Current status ==
* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]  
* Targeted release: [[Releases/12 | Fedora 12 ]]  
* Last updated: (DATE)
* Last updated: July 15, 2009
* Percentage of completion: XX%
* Percentage of completion: 30%


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
The latest version of the NFS protocol is version 4, which was
first introduced in Fedora F-2 (the first distro to have such
support). The current default NFS version is version 3. Meaning
when an simple NFS mount is done (i.e. mount server:/export /mnt)
version 3 is the first protocol version that is tried.
 
With the proposed changes, version 4 would be tried first. If
the server does not support version 4, the mount would then
try version 3.


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- 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?-->
One of the major benefit is performance. In version 4, the server
now has state which means it can communicate with each
NFS client. The means the server can issue things called
delegations (or leases) for files allowing the v4 client
to aggressively cache which drastically cuts down on
network traffic between the client and server. 
 
There a number of other benefits which are documented in
the following link:
      http://www.iaps.com/NFSv4-new-features.html


== 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?-->
There are basically three parts to make this happen:
1) Change the exports on the server so v3 and v2 exports
  can *seamlessly* be used by v4 clients.


== How To Test ==
2) Change the mount command to start negotiating with the
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
  version 4 protocol and then fall back to version 3 if
  the server does not support v4 (similar to what happens
  today with version 3 and version 4)


Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
3) Introduce a NFS mount configuration file where users
  can define which protocol version should be negotiated.


A good "how to test" should answer these four questions:
== How To Test ==
 
The usual Connectathon tests will be used and well as anyother
0. What special hardware / data / etc. is needed (if any)?
filesystem tests that are available (such as fsx).
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->


== 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. -->
This transition should be seamless to the users...  


== 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)? -->
The only dependency is on the nfs-utils package.


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
If the code is not ready, then the version 3 will still be the default.
 


== 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. -->
http://www.nfsv4.org/
*


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*Fedora now use NFS version 4 as the default protocol version.
*


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/NFSv4Default]]  




Revision as of 13:25, 15 July 2009

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.


NFSv4Default

Summary

Changed the default NFS protocol to version 4.

Owner

  • email: steved@redhat.com

Current status

  • Targeted release: Fedora 12
  • Last updated: July 15, 2009
  • Percentage of completion: 30%


Detailed Description

The latest version of the NFS protocol is version 4, which was first introduced in Fedora F-2 (the first distro to have such support). The current default NFS version is version 3. Meaning when an simple NFS mount is done (i.e. mount server:/export /mnt) version 3 is the first protocol version that is tried.

With the proposed changes, version 4 would be tried first. If the server does not support version 4, the mount would then try version 3.

Benefit to Fedora

One of the major benefit is performance. In version 4, the server now has state which means it can communicate with each NFS client. The means the server can issue things called delegations (or leases) for files allowing the v4 client to aggressively cache which drastically cuts down on network traffic between the client and server.

There a number of other benefits which are documented in the following link: 

     http://www.iaps.com/NFSv4-new-features.html

Scope

There are basically three parts to make this happen: 1) Change the exports on the server so v3 and v2 exports 

  can *seamlessly* be used by v4 clients.

2) Change the mount command to start negotiating with the 

  version 4 protocol and then fall back to version 3 if
  the server does not support v4 (similar to what happens
  today with version 3 and version 4)

3) Introduce a NFS mount configuration file where users 

  can define which protocol version should be negotiated.

How To Test

The usual Connectathon tests will be used and well as anyother filesystem tests that are available (such as fsx).

User Experience

This transition should be seamless to the users...

Dependencies

The only dependency is on the nfs-utils package.

Contingency Plan

If the code is not ready, then the version 3 will still be the default.


Documentation

http://www.nfsv4.org/

Release Notes

  • Fedora now use NFS version 4 as the default protocol version.

Comments and Discussion


Retrieved from "https://fedoraproject.org/w/index.php?title=Features/EmptyTemplate&oldid=113521"