I've recently redesigned the way the test tree is created and used. The previous method was:
* Run test_tree.py locally, with the exported root as argument. * Run nfs4st, which required the test tree to be located at the toplevel of the servers exported resources.
This has two drawbacks:
1) It is not always possible to run the test_tree.py locally on the server. This is the case for NetApp Filers, for example.
2) Requiring the directories doc, src, tmp etc to be located on the toplevel on the server was inflexible.
The new method is:
* Run the new program test_tree_net.py. It does the same work as test_tree.py, but via NFSv4, over the network. It can optionally take a prefix. A directory tree with different kinds of files will be created under <prefix>/nfs4st/
* Run the nfs4st.py test application with the same prefix as test_tree_net.py.
Example:
./test_tree_net.py myserver/testing ./nfs4st.py myserver/testing AccessSuite