[PVFS2-CVS] commit by robl in pvfs2/test/common/pav: README

CVS commit program cvs at parl.clemson.edu
Fri Mar 5 14:02:28 EST 2004


Update of /projects/cvsroot/pvfs2/test/common/pav
In directory acid:/tmp/cvs-serv7622

Modified Files:
	README 
Log Message:
talk a bit more about ways we use PAV


Index: README
===================================================================
RCS file: /projects/cvsroot/pvfs2/test/common/pav/README,v
diff -u -w -p -u -r1.6 -r1.7
--- README	4 Mar 2004 20:56:34 -0000	1.6
+++ README	5 Mar 2004 19:02:28 -0000	1.7
@@ -4,7 +4,7 @@ Idea:
 
 This package is meant to help with the setup and shutdown of PVFS
 volumes.  It was written with the intent of making the testing of such
-volumes simple, since testing PVFS volumes often times involves the
+volumes simple, since testing PVFS volumes often involves the
 time consuming process of making changes to PVFS server code, pushing
 the compiled binaries out to server nodes, setting up PVFS server
 config files, and finally starting the iod and mgr processes.  The pav
@@ -16,6 +16,14 @@ duration of their job.  Sysadmins like t
 to push out new versions of PVFS code onto their cluster wide PVFS
 resource.
 
+Typically, PAV is used in two environments.  In one case, a user has a
+handful of workstations.  Using PAV, he can get a mulit-server PVFS2
+volume up and running and quickly start testing.  In the other common
+case, the user requests an allocation of nodes on a cluster.  With PAV,
+the allocation is split into "io nodes" and "compute nodes".  PVFS2
+servers run on the io nodes while the application runs on the compute
+nodes.  This split keeps the application nodes from perturbing the io
+nodes and should yield more consistent results.
 
 Using pav:
 



More information about the PVFS2-CVS mailing list