Running tests in parallel | HP Cluster Test Software instruction

7 Running tests in parallel

It is possible to run tests on independent groups of nodes in the same cluster in parallel. This is done from the command line, using the run_cluster_script command (see “Utility commands” (page 51)). The run_cluster_script command does basically what the FileLoad Script menu item does in the Cluster Test GUI – loads and runs a cluster script describing one or more tests. (See “Using scripts to run tests” (page 12).)

You may run as many simultaneous cluster scripts as you like, provided they don’t use the same nodes. For example, in a 256-node cluster of HP ProLiant BL280c G6 Server Blades, you could run 16 separate cluster scripts, each on the nodes in one enclosure. No attempt is made to check that the nodes in question are actually unused.

CAUTION: Running tests in parallel is an advanced use of Cluster Test. The responsibility of making sure a node is not subjected to multiple, simultaneous tests is yours. Make sure you assign specific nodes to testers. Running simultaneous tests on a single node will most likely cause all tests to fail.

By default, files associated with tests run from a single run_cluster_script command go into a separate time-stamped directory under /opt/clustertest/logs, the same as a single invocation of testnodes.pl. If you would like to have all your separate run_cluster_script files go into the same directory, you can use the –logdiroption to control which directory the test files go into – perhaps the same directory being used by the current .pl. File names are assigned sequence numbers, so several run_cluster_script commands can share a single directory without conflict.

Scripts used with run_cluster_script.pl should adhere to one of the following forms:

•<full path to test script><full path to machines file><interconnect>

•<full path to machines file><interconnect><full path to test script><[optional test script parameters]>

•<full path to machines file><interconnect><test name><[optional test parameters]>

This last form is for a test script with the machines file and interconnect at the beginning of the line.