sbsv2/raptor/test/cluster/README
author kelvzhu
Mon, 18 Oct 2010 16:16:46 +0800
changeset 655 3f65fd25dfd4
parent 591 22486c9c7b15
permissions -rw-r--r--
sync up SVN codes
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
591
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     1
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     2
Testing a Cluster to See if it is Correctly Configured
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     3
--------------------------------------------------------
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     4
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     5
The tests in this directory can be seen only as examples of how to test a cluster.  They would have to be customised before use on any particular cluster.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     6
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     7
The tests here are aimed at:
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     8
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
     9
1) Testing that the configuration of each nodes and that services such as NIS,DNS and NTP are configured.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    10
  This requires that logins for the current user work on all nodes.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    11
2) Checking that raptor-relevant software is installed and that the compiler can obtain licenses.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    12
3) Testing that PVM is installed and will run without crashing (solves a problem that has occurred in the past).
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    13
4) Tests that PVM can run commands on all nodes.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    14
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    15
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    16
Typically one would run headtest.sh which performs the tests relating to items 1-3. It causes "nodetest.sh" to be run on all nodes.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    17
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    18
e.g.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    19
	./headtest.sh node1 node2 node3
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    20
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    21
pvmtest.sh can be used to check that pvm is working by running the compiler on each node via pvm.
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    22
	./pvmtest node1 node2 node3
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    23
22486c9c7b15 raptor v2.14.0
jjkang
parents:
diff changeset
    24
None of these tests is automatic - one must simply observe the output.