Pynfs

From Linux NFS

(Created page with "pynfs is intended for NFSv4.0 and NFSv4.1 testing. Unlike the Connectathon suite, it knows how to parse and generate the protocol itself, so can talk directly to the client or s...")

pynfs is intended for NFSv4.0 and NFSv4.1 testing. Unlike the Connectathon suite, it knows how to parse and generate the protocol itself, so can talk directly to the client or server to be tested. This makes it particularly well-suited for testing:

pynfs is intended for NFSv4.0 and NFSv4.1 testing. Unlike the Connectathon suite, it knows how to parse and generate the protocol itself, so can talk directly to the client or server to be tested. This makes it particularly well-suited for testing:

-

* responses to incorrect or malicious protocol

+

* responses to incorrect or malicious protocol

-

* responses to unusual error conditions

+

* responses to unusual error conditions

-

* protocol conformance

+

* protocol conformance

-

* correctness of new features that don't yet have corresponding client or server side implementations to test against

+

* correctness of new features that don't yet have corresponding client or server side implementations to test against

The server-testing code is currently more useful than the client-testing code.

The server-testing code is currently more useful than the client-testing code.

The original pynfs was written by Peter Åstrand. It was rewritten mainly by Fred Isaman at [http://citi.umich.edu/project/nfsv4/pynfs/ citi] with a nicer test framework and clearer output, and briefly renamed to "newpynfs" (then back to "pynfs"). Fred then later forked a NFSv4.1 pynfs--also named "pynfs", which has been since merged back into pynfs. The resulting project supports all minor versions and will forever be named just pynfs. Hopefully.

The original pynfs was written by Peter Åstrand. It was rewritten mainly by Fred Isaman at [http://citi.umich.edu/project/nfsv4/pynfs/ citi] with a nicer test framework and clearer output, and briefly renamed to "newpynfs" (then back to "pynfs"). Fred then later forked a NFSv4.1 pynfs--also named "pynfs", which has been since merged back into pynfs. The resulting project supports all minor versions and will forever be named just pynfs. Hopefully.

Revision as of 15:33, 15 October 2012

pynfs is intended for NFSv4.0 and NFSv4.1 testing. Unlike the Connectathon suite, it knows how to parse and generate the protocol itself, so can talk directly to the client or server to be tested. This makes it particularly well-suited for testing:

responses to incorrect or malicious protocol

responses to unusual error conditions

protocol conformance

correctness of new features that don't yet have corresponding client or server side implementations to test against

The server-testing code is currently more useful than the client-testing code.

Note that test results should *not* be considered authoritative statements about the protocol--if you find that a server fails a test, you should consult the rfc's and think carefully before assuming that the server is at fault. (However, we do appreciate patches if you find a test that requires incorrect behavior.)

Download

History

The original pynfs was written by Peter Åstrand. It was rewritten mainly by Fred Isaman at citi with a nicer test framework and clearer output, and briefly renamed to "newpynfs" (then back to "pynfs"). Fred then later forked a NFSv4.1 pynfs--also named "pynfs", which has been since merged back into pynfs. The resulting project supports all minor versions and will forever be named just pynfs. Hopefully.