Bright:Intel Cluster Ready

From Define Wiki
Revision as of 16:58, 16 January 2014 by David (talk | contribs) (Created page with "* Assumes that all the pacakges were installed as part of the default installation (Refer to the admin guide to install if not) == Prepare the system == Need to run as <tt>cm...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  • Assumes that all the pacakges were installed as part of the default installation (Refer to the admin guide to install if not)

Prepare the system

Need to run as cmsupport

[root@mycluster ~]# su - cmsupport
[cmsupport@mycluster ~]$ clck-prepare
Created non InfiniBand node list file /home/cmsupport/intel-cluster-ready/nodelist
Created InfiniBand node list file /home/cmsupport/intel-cluster-ready/nodelist.ib

Run Cluster Checker

[root@mycluster ~]# su - cmsupport
[cmsupport@mycluster ~]$ module initadd intel-cluster-runtime
[cmsupport@mycluster ~]$ module load intel-cluster-runtime
[cmsupport@mycluster ~]$ cluster-check --certification

Handling Test Failures

The cluster checker produces several output files, with .xml, .out, .debug suffixes, which include time stamps in the filenames. If tests fail, the out- put files can be consulted for details. The output files can be found in the ̃/intel-cluster-ready/logs directory. When debugging and re-running tests, the option ---include_only test_name can be passed to cluster-check to execute only the test named “<test>” (and the tests on which it depends). In a heterogeneous cluster the cluster check run fails as a result of hardware differences. To resolve the failures, it is necessary to create mul- tiple groups of homogeneous hardware. For more information, the Intel Cluster Checker documentation can be consulted.