From Fedora Project Wiki
No edit summary
m (Fix typography issues for automatic processing)
 
(14 intermediate revisions by 2 users not shown)
Line 4: Line 4:
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->


NFStest <!-- The name of your feature -->
= NFStest = <!-- The name of your feature -->


== Summary ==
== Summary ==
Line 19: Line 19:
== Current status ==
== Current status ==
* Targeted release: Fedora 19  
* Targeted release: Fedora 19  
* Last updated: 27 November 2012
* Last updated: 2012-11-27
* Percentage of completion: 100%
* Percentage of completion: 100%


<!-- 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. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Line 44: Line 43:
== 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?-->
<!-- 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?-->
the inclusion of nfstest benefits Fedora by providing customers with a tool to test NFS functionality and a development platform for creating new NFS tests. It is our hope this will increase adoption of NFSv4 and pNFS.
The inclusion of nfstest benefits Fedora by providing customers with a tool to test NFS functionality and a development platform for creating new NFS tests. It is our hope this will increase adoption of NFSv4 and pNFS.


== 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?-->
At this point, all of the development is done. The scope of change that will affect the over all distribution is very small. NFStest is a standalone package for testing NFS functionality.


== How To Test ==
== How To Test ==
Line 63: Line 63:
3. What are the expected results of those actions?
3. What are the expected results of those actions?
-->
-->
There is no special hardware or data needed to test NFStest.


== 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. -->
Users may use NFStest to check the functionality of their NFS 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)? -->
python > 2.6


== 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 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.  -->
No contingency plan is necessary. All the development is done.


== 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. -->
*
* website:  http://wiki.linux-nfs.org/wiki/index.php/NFStest
* GIT tree: http://git.linux-nfs.org/?p=mora/nfstest.git;a=blob;f=README


== 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 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. -->
<!-- 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. -->
*
* More detailed information can be found at: http://wiki.linux-nfs.org/wiki/index.php/NFStest


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/Your_Feature_Name]]  <!-- 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/NFStest]]  <!-- 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 -->




[[Category:FeaturePageIncomplete]]
[[Category:FeatureAcceptedF19]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 12:57, 28 February 2013


NFStest

Summary

Provides a set of tools for testing either the NFS client or the NFS server, most of the functionality is focused mainly on testing the client.

Owner

  • Email: steved@redhat.com

Current status

  • Targeted release: Fedora 19
  • Last updated: 2012-11-27
  • Percentage of completion: 100%

Detailed Description

NFStest provides a set of tools for testing either the NFS client or the NFS server, including the framework for developing more tests. These tools include the following:

  • Process command line arguments
  • Provide functionality for PASS/FAIL
  • Provide test grouping functionality
  • Provide multiple client support
  • Logging mechanism
  • Debug info control
  • Mount/Unmount control
  • Create files/directories
  • Provide mechanism to start a packet trace
  • Provide mechanism to simulate a network partition
  • Support for pNFS testing
  • Provide mechanism to automate packet trace inspection

Benefit to Fedora

The inclusion of nfstest benefits Fedora by providing customers with a tool to test NFS functionality and a development platform for creating new NFS tests. It is our hope this will increase adoption of NFSv4 and pNFS.

Scope

At this point, all of the development is done. The scope of change that will affect the over all distribution is very small. NFStest is a standalone package for testing NFS functionality.

How To Test

There is no special hardware or data needed to test NFStest.

User Experience

Users may use NFStest to check the functionality of their NFS environment.

Dependencies

python > 2.6

Contingency Plan

No contingency plan is necessary. All the development is done.

Documentation

Release Notes

Comments and Discussion