Changes between Version 3 and Version 4 of NightlyBuilds

Timestamp:

03/25/09 08:39:57 (8 months ago)

Author:

robl (IP: 140.221.11.29)

Comment:

more details about setting things up

NightlyBuilds

@@ -62 +62 @@
 should end up on that page.  If you find that you have to log into the test
 machine, then we should fix the tests so that's not needed.
+
+== Setting Up Your Own Tests ==
+
+A quick word: You might want to override the defaults, which you can do by
+modifying {{{nightly-tests.cfg}}} (also in the 'nightly' directory). 
+
+=== System Interface Tests === 
+The easiest tests to run are the system interface tests (the ones in
+sysint.d).  These tests are also the ones that will run "out of the box" if
+you just run {{{test/automated/nightly/testscrpt.sh}}}.  
+
+
+=== VFS Tests ===
+Next up in difficulty: the VFS tests.  These tests require two things.  
+
+First, root access.  The test scripts assume passwordless sudo, which isn't a
+problem on our dedicated test machines (no sensitive items there) but might be
+a concern on production machines.   Edit testscrpt.sh and add your machine to
+the list of {{{VFS_HOSTS}}}. 
+
+Second, some external benchmarks.  Several of the VFS tests compile and run
+some common I/O benchmarks (IOzone, bonnie++, dbench).  I have put a tarball
+of the tests we run in
+[[http://www.mcs.anl.gov/~robl/pvfs2/benchmarks-20060512.tar.gz]]
+
+You will have to update your dbench for modern compilers.  I haven't updated
+the benchmarks tarball with this newer version yet.
+
+But once you have all that, then I think this too should work without too much
+mucking around inside the test scripts. 
+
+=== MPI-IO Tests ===
+
+These tests are less complicated in some ways -- they do not require root
+access -- but are still more complicated.  I've made no end of assumptions to
+get these tests to work on our Jazz cluster.  These scripts as written pretty
+much require PBS.   
+
+Here's the general idea:  Allocate some nodes (the scripts allocate 8 nodes
+from Jazz's shared queue, because that's the most nodes with the fastest
+turnaround).  We use PAV (pvfs auto-volume) to partition the allocated nodes
+into I/O nodes (those running pvfs servers) and clients (the ones
+participating in the MPI job).
+
+The specifics include: queue name, executing an MPI job on a subset of PBS
+nodes, configuring PAV for our system.   I can and should write a lot more
+about this part...