https://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&feed=atom&action=historyCluster: C3 Tools INSTALL - Revision history2024-03-29T02:14:43ZRevision history for this page on the wikiMediaWiki 1.32.1https://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10082&oldid=prevKay at 16:41, 3 August 20092009-08-03T16:41:08Z<p></p>
<a href="https://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10082&oldid=10081">Show changes</a>Kayhttps://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10081&oldid=prevKay at 16:40, 3 August 20092009-08-03T16:40:41Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 16:40, 3 August 2009</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><pre><nowiki></div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><pre><nowiki></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> C3 version 4.0: Cluster Command & Control Suite</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> Oak Ridge National Laboratory, Oak Ridge, TN,</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> Authors: M.Brim, R.Flanery, G.A.Geist, B.Luethke, S.L.Scott</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> (C) 2001 All Rights Reserved</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> NOTICE</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> Permission to use, copy, modify, and distribute this software and</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> its documentation for any purpose and without fee is hereby granted</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> provided that the above copyright notice appear in all copies and</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> that both the copyright notice and this permission notice appear in</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> supporting documentation.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> Neither the Oak Ridge National Laboratory nor the Authors make any</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> representations about the suitability of this software for any</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> purpose. This software is provided "as is" without express or</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> implied warranty.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> The C3 tools were funded by the U.S. Department of Energy.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">I. REQUIRED SOFTWARE</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">--------------------</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Before C3 can be installed on a system, you must ensure that the following</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">software is installed on your system. The following seven software packages</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">are required: the C3 tools suite, Rsync, SSH (or OpenSSH), Python, and Perl.</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">You must also configure that system to support host name resolution of the</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">machines listed in the configuration file (either through DNS or /etc/hosts).</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> Finally, if you wish to use the C3 pushimage command, which pushes system</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">images across a cluster, you must install SystemImager.</ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div></nowiki></pre></div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div></nowiki></pre></div></td></tr>
</table>Kayhttps://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10080&oldid=prevKay: Replacing page with '<pre><nowiki>
</nowiki></pre>'2009-08-03T16:40:21Z<p>Replacing page with '<pre><nowiki> </nowiki></pre>'</p>
<a href="https://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10080&oldid=10079">Show changes</a>Kayhttps://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10079&oldid=prevKay at 16:39, 3 August 20092009-08-03T16:39:24Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 16:39, 3 August 2009</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l701" >Line 701:</td>
<td colspan="2" class="diff-lineno">Line 701:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> 2. Full Man Page - enter "man <command>" at the command line</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> 2. Full Man Page - enter "man <command>" at the command line</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div></nowiki></pre></div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div></nowiki></pre></div></td></tr>
</table>Kayhttps://wiki.cs.earlham.edu/index.php?title=Cluster:_C3_Tools_INSTALL&diff=10078&oldid=prevKay: New page: <pre><nowiki> C3 version 4.0: Cluster Command & Control Suite Oak Ridge National Laboratory, Oak Ridge, TN, Authors: M.Brim, R.Flanery, G.A.Geist, B.Luethke, S...2009-08-03T16:38:39Z<p>New page: <pre><nowiki> C3 version 4.0: Cluster Command & Control Suite Oak Ridge National Laboratory, Oak Ridge, TN, Authors: M.Brim, R.Flanery, G.A.Geist, B.Luethke, S...</p>
<p><b>New page</b></p><div><pre><nowiki><br />
C3 version 4.0: Cluster Command & Control Suite<br />
<br />
Oak Ridge National Laboratory, Oak Ridge, TN,<br />
<br />
Authors: M.Brim, R.Flanery, G.A.Geist, B.Luethke, S.L.Scott<br />
<br />
(C) 2001 All Rights Reserved<br />
<br />
<br />
<br />
NOTICE<br />
<br />
<br />
<br />
Permission to use, copy, modify, and distribute this software and<br />
<br />
its documentation for any purpose and without fee is hereby granted<br />
<br />
provided that the above copyright notice appear in all copies and<br />
<br />
that both the copyright notice and this permission notice appear in<br />
<br />
supporting documentation.<br />
<br />
<br />
<br />
Neither the Oak Ridge National Laboratory nor the Authors make any<br />
<br />
representations about the suitability of this software for any<br />
<br />
purpose. This software is provided "as is" without express or<br />
<br />
implied warranty.<br />
<br />
<br />
<br />
The C3 tools were funded by the U.S. Department of Energy.<br />
<br />
<br />
<br />
<br />
<br />
I. REQUIRED SOFTWARE<br />
<br />
--------------------<br />
<br />
<br />
<br />
Before C3 can be installed on a system, you must ensure that the following <br />
<br />
software is installed on your system. The following seven software packages<br />
<br />
are required: the C3 tools suite, Rsync, SSH (or OpenSSH), Python, and Perl.<br />
<br />
You must also configure that system to support host name resolution of the <br />
<br />
machines listed in the configuration file (either through DNS or /etc/hosts).<br />
<br />
Finally, if you wish to use the C3 pushimage command, which pushes system <br />
<br />
images across a cluster, you must install SystemImager.<br />
<br />
<br />
<br />
Instructions for obtaining each of these software packages are given below.<br />
<br />
<br />
<br />
C3 tools may be obtained from http://www.csm.ornl.gov/torc/C3<br />
<br />
<br />
<br />
Rsync, Perl, SSH, and Python should be included with your distribution.<br />
<br />
If they are not then download the source or binaries from their respected<br />
<br />
web sites.<br />
<br />
<br />
<br />
Perl may be obtained from http://www.perl.com<br />
<br />
C3 requires 5.005 or greater<br />
<br />
<br />
<br />
Python may be obtained from <br />
<br />
http://www.python.org/<br />
<br />
C3 version 3 requires Python 2.0 or greater<br />
<br />
<br />
<br />
additionally C3 requires either the binary or a link to the python <br />
<br />
interpreter to be in your path (and that it be named python2). To <br />
<br />
check it type "python2 -V" and make sure you get output (the current <br />
<br />
version of python being run). If you do not get any output then you must <br />
<br />
find where the python library is on your machine and create a link to<br />
<br />
the binary. Such as "ln -s /usr/bin/python /usr/bin/python2" if<br />
<br />
/usr/bin/python is where your python binary is located and /usr/bin<br />
<br />
is in your path.<br />
<br />
<br />
<br />
SystemImager may be obtained from <br />
<br />
http://www.systemimager.org/<br />
<br />
<br />
<br />
<br />
<br />
II. C3 INSTALLATION<br />
<br />
----------------<br />
<br />
NOTE: if you are wanting to use the scalable model of the C3 tolls then follow<br />
<br />
steps A and B, read C as it still pertains to the scalable model, then see the <br />
<br />
README.scale file for the scalable instructions.<br />
<br />
<br />
<br />
A. pre-install<br />
<br />
Begin by making sure that Rsync, OpenSSL, OpenSSH, PERL, and<br />
<br />
Python are installed. Install Systemimager, if needed. Install DNS<br />
<br />
or /etc/hosts as needed, and make sure that hostname resolution is <br />
<br />
supported.<br />
<br />
<br />
<br />
Directions for downloading each of these packages are given in <br />
<br />
Section I above. Perl, Python, Rsync, OpenSSH, and OpenSSL are included <br />
<br />
with most distributions<br />
<br />
<br />
<br />
You will need root access to install these packages on your system. <br />
<br />
Follow the instruction in each package if you need to install them.<br />
<br />
<br />
<br />
B. C3 install<br />
<br />
After you complete the pre-install (step A), install the Cluster <br />
<br />
Command & Control (C3) tools. Begin by untar'ring the C3 package <br />
<br />
and running the install script. The install script places the C3 <br />
<br />
scripts in /opt/c3-4 and the man pages in the appropriate directory. <br />
<br />
<br />
<br />
The C3 install script installs the C3 command suite, but does not <br />
<br />
configure the commands or any local clusters for operation. <br />
<br />
Directions for the remaining tasks are given below.<br />
<br />
<br />
<br />
C. C3 configuration<br />
<br />
Specific instances of C3 commands identify their compute nodes with <br />
<br />
the help of **cluster configuration files**: files that name a set<br />
<br />
of accessible clusters, and that list and describe the set of <br />
<br />
machines in each accessible cluster. Cluster configuration files <br />
<br />
are accessed in one of two ways:<br />
<br />
<br />
<br />
-. explicitly: an instance of a C3 command names a specific <br />
<br />
configuration file, using a command-line switch.<br />
<br />
<br />
<br />
-. implicitly: an instance of a C3 command fails to name a specific<br />
<br />
configuration file, and the command defaults to the list of cluster<br />
<br />
descriptions given in /etc/c3.conf.<br />
<br />
<br />
<br />
When you install C3, you should create a default configuration file <br />
<br />
that is appropriate to the site. This file, which should be named<br />
<br />
/etc/c3.conf, should consist of a list of **cluster descriptor<br />
<br />
blocks**: syntactic objects that name and describe a single cluster <br />
<br />
that is accessible to that system's users. <br />
<br />
<br />
<br />
The following is an example of a default configuration file that <br />
<br />
contains exactly one cluster descriptor block: a block that <br />
<br />
describes a cluster of 64 nodes:<br />
<br />
<br />
<br />
cluster local {<br />
<br />
htorc-00:node0 #head node<br />
<br />
node[1-64] #compute nodes<br />
<br />
}<br />
<br />
<br />
<br />
Cluster description blocks consist of the following basic elements:<br />
<br />
<br />
<br />
-. a **cluster tag**: the word "cluster", followed by a label,<br />
<br />
which assigns a name to the cluster. This name--here, "local"--<br />
<br />
can be supplied to C3 commands as a way of specifying the cluster<br />
<br />
on which a command should execute.<br />
<br />
<br />
<br />
-. an open curly brace, which signals the start of the cluster's<br />
<br />
declaration proper.<br />
<br />
<br />
<br />
-. a **head node descriptor**: a line that names the interfaces<br />
<br />
on the cluster's head node. The head node descriptor shown here<br />
<br />
has two parts:<br />
<br />
<br />
<br />
-. The string to the left of the colon identifies the head <br />
<br />
node's **external** interface: a network card that links <br />
<br />
the head node to computers outside the cluster. This string<br />
<br />
can be the interface's IP address or DNS-style hostname.<br />
<br />
-. The string to the right of the colon identifies the head <br />
<br />
node's **internal** interface: a network card that links the<br />
<br />
head node to nodes inside the cluster. This string can be <br />
<br />
the interface's IP address or DNS-style hostname.<br />
<br />
<br />
<br />
Here, the head node descriptor names a head node with an external<br />
<br />
interface named htorc-00, and an internal interface named node0.<br />
<br />
<br />
<br />
A cluster that has no external interface--i.e., a cluster that is<br />
<br />
on a closed system--can be specified by either<br />
<br />
<br />
<br />
-. making the internal and external name the same, or<br />
<br />
-. dropping the colon, and using one name in the specifier. <br />
<br />
<br />
<br />
-. a list of **compute node descriptors**: a series of individual<br />
<br />
descriptors that name the cluster's compute nodes. <br />
<br />
<br />
<br />
The example given here contains exactly one compute node <br />
<br />
descriptor. This descriptor uses a **range qualifier** to <br />
<br />
specify a cluster that contains 64 compute nodes, named node1, <br />
<br />
node2, etc., up through node64. A range qualifier consists of <br />
<br />
-. a first, nonnegative integer, followed by <br />
<br />
-. a dash, followed by <br />
<br />
-. a second integer that is at least as large as the first.<br />
<br />
<br />
<br />
In the current version of the C3 tools et, these range values are <br />
<br />
treated as numbers, with no leading zeroes. A declaration like<br />
<br />
<br />
<br />
cluster local {<br />
<br />
htorc-00:node0 #head node<br />
<br />
node[01-64] #compute nodes<br />
<br />
}<br />
<br />
<br />
<br />
expands to the same 64 nodes as the declaration shown above. To <br />
<br />
specify a set of nodes with names like node01, node09, node10, ...<br />
<br />
node64, use declarations like<br />
<br />
<br />
<br />
cluster local {<br />
<br />
htorc-00:node0 #head node<br />
<br />
node0[1-9] #compute nodes node01..node09<br />
<br />
node[10-64] #compute nodes node10..node64<br />
<br />
}<br />
<br />
<br />
<br />
-. a final, closing curly brace.<br />
<br />
<br />
<br />
Configuration files that specify multiple clusters are constituted as<br />
<br />
a list of cluster descriptor blocks--one per accessible cluster.<br />
<br />
The following example of a cluster configuration file contains three <br />
<br />
blocks that specify configurations for clusters named local, torc, <br />
<br />
and my-cluster, respectively:<br />
<br />
<br />
<br />
cluster local {<br />
<br />
htorc-00:node0 #head node<br />
<br />
node[1-64] #compute nodes<br />
<br />
exclude 2<br />
<br />
exclude [55-60]<br />
<br />
}<br />
<br />
<br />
<br />
cluster torc {<br />
<br />
:orc-00b<br />
<br />
}<br />
<br />
<br />
<br />
cluster my-cluster {<br />
<br />
osiris:192.192.192.2<br />
<br />
woody<br />
<br />
dead riggs<br />
<br />
}<br />
<br />
<br />
<br />
The first cluster in the file has a special significance that is<br />
<br />
analogous to the special significance accorded to the first <br />
<br />
declaration in a make file. Any instance of a C3 command that fails<br />
<br />
to name the cluster on which it should run executes, by default, on <br />
<br />
the first cluster in the configuration file. Here, for example, any<br />
<br />
command that fails to name its target cluster would default to local.<br />
<br />
<br />
<br />
The cluster configuration file shown above illustrates three final<br />
<br />
features of the cluster definition language: **exclude qualifiers**,<br />
<br />
**dead qualifiers**, and **indirect cluster** descriptors.<br />
<br />
<br />
<br />
**Exclude qualifiers** allow nodes to be excluded from a cluster's<br />
<br />
configuration: i.e., to be identified as offline for the purpose of<br />
<br />
a command execution. Exclude qualifiers may only be applied to <br />
<br />
range declarations, and must follow immediately after a range <br />
<br />
declaration to which they are being applied. A series of exclude <br />
<br />
declarations is ended by a non-exclude declaration, or the final "}" <br />
<br />
in a cluster declaration block. <br />
<br />
<br />
<br />
An exclude qualifier can be written in one of three ways:<br />
<br />
-. "exclude n", where n is the number of a node to exclude from the<br />
<br />
cluster;<br />
<br />
-. "exclude[m-n]", where m, m+1, m+2, ..., n-1, n is the range of <br />
<br />
nodes to exclude; or as<br />
<br />
-. "exclude [m-n], which has the same effect as "exclude[m-n]".<br />
<br />
Note that a string like "exclude5" is parsed as a node name, rather <br />
<br />
than as an exclude qualifier.<br />
<br />
<br />
<br />
In the above example, the two exclude qualifiers have the effect of<br />
<br />
causing node2, node55, node56 node57, node58, node59, and node60 to <br />
<br />
be treated as offline for the purpose of computation.<br />
<br />
<br />
<br />
**Dead qualifiers** are similar to exclude qualifiers, but apply to<br />
<br />
individual machines. In the example given above, the machine named<br />
<br />
"riggs" in the cluster named "my-cluster" is excluded from all<br />
<br />
computations.<br />
<br />
<br />
<br />
"Dead", like "exclude", is not a reserved word in the current version<br />
<br />
of the C3 suite. A specification block like<br />
<br />
<br />
<br />
cluster my-cluster {<br />
<br />
alive:alive<br />
<br />
dead<br />
<br />
}<br />
<br />
<br />
<br />
for example, declares a two-machine cluster with a head node named <br />
<br />
"alive" and a compute node named "dead".<br />
<br />
<br />
<br />
An **indirect cluster descriptor** is treated as a reference to <br />
<br />
another cluster, rather than as a characterization of a cluster per <br />
<br />
se. In the example shown above, the descriptor<br />
<br />
<br />
<br />
cluster torc {<br />
<br />
:orc-00b<br />
<br />
}<br />
<br />
<br />
<br />
is an indirect cluster descriptor. An indirect descriptor consists <br />
<br />
of<br />
<br />
<br />
<br />
-. a cluster tag, followed by, <br />
<br />
-. an **indirect head head node descriptor**, followed by<br />
<br />
-. an empty list of compute node descriptors.<br />
<br />
<br />
<br />
An indirect head node descriptor consists of an initial colon, <br />
<br />
followed by a string that names a **remote** system. This name, <br />
<br />
which can either be an IP address or a DNS-style hostname, is checked<br />
<br />
whenever a C3 command executes to verify that that the machine being<br />
<br />
referenced is **not** the machine on which that command is currently <br />
<br />
executing.<br />
<br />
<br />
<br />
A command that is destined for an indirect cluster is executed by <br />
<br />
<br />
<br />
-. first forwarding that command to the remote cluster's head node<br />
<br />
-. next, executing that command, relative to the remote machine's <br />
<br />
default configuration file.<br />
<br />
<br />
<br />
For this feature to work properly, the remote machine must also <br />
<br />
support a fully operational C3 suite (version 4.0) placed in the <br />
<br />
/opt/c3-4 directory. <br />
<br />
<br />
<br />
The indirect cluster descriptors can be used to construct **chains** <br />
<br />
of remote references: that is, multi-node configurations where an<br />
<br />
indirect cluster descriptor on a machine A references an indirect <br />
<br />
cluster descriptor on a machine B. Here, it is the system <br />
<br />
administrator's responsibility to avoid circular references.<br />
<br />
<br />
<br />
D. Post-install<br />
<br />
For the C3 ckill command to work properly, ckillnode must be copied <br />
<br />
to a directory on each compute node on every supported cluster. The <br />
<br />
easy way to install ckillnode is to use cexec and cpush. After <br />
<br />
installing and configuring C3 (cf. steps A-C above), use the <br />
<br />
following two commands to push ckillnode to each node in the default <br />
<br />
cluster.<br />
<br />
<br />
<br />
cexec mkdir /opt/c3-4<br />
<br />
cpush /opt/c3-4/ckillnode<br />
<br />
<br />
<br />
For the scalable version a full C3 install is needed on each node.<br />
<br />
This can be accomplished by either installing the RPM on each node<br />
<br />
or pushing the tarball out and using cexec (non-scalable at this point)<br />
<br />
to run the install script on each node.<br />
<br />
<br />
<br />
This completes the installation of the C3 tools.<br />
<br />
<br />
<br />
E. Notes<br />
<br />
The relative positions of nodes in c3.conf files can be significant<br />
<br />
for C3 command execution. Version 3 of the C3 suite allows the use <br />
<br />
of node ranges on the command line. The command line parameters used<br />
<br />
to specify the indices of compute nodes refer to relative node <br />
<br />
positions in c3.conf. <br />
<br />
<br />
<br />
Consider, for example, the semantics of node range parameters, <br />
<br />
relative to the following c3.conf file:<br />
<br />
<br />
<br />
cluster local {<br />
<br />
htorc-00:node0 #head node<br />
<br />
node[1-64] #compute nodes<br />
<br />
exclude 60<br />
<br />
node[129-256]<br />
<br />
}<br />
<br />
<br />
<br />
This cluster is made up of 192 nodes. Here, <br />
<br />
<br />
<br />
-. the 64 nodes named node1 through node64 correspond to slots 0-63<br />
<br />
-. the 128 nodes named node129 through node256 correspond to slots<br />
<br />
64-191--and **not**, for example, to slots 129-256.<br />
<br />
<br />
<br />
Note also that the excluded node--node60--acts as a place holder in <br />
<br />
the range of indices: node60 is a relative index of 59, which allows<br />
<br />
nodes node61, node62, node63, and node64 to correspond to 60, 61, 62,<br />
<br />
and 63, respectively. This "place holder" effect is an important <br />
<br />
reason for explicitly specifying that a node is dead or excluded--as<br />
<br />
opposed to simply dropping that line from the specification.<br />
<br />
<br />
<br />
Two new tools in version 3.1 of the C3 tools suite support the <br />
<br />
management of node numbers. The first, cname, inputs a node name,<br />
<br />
and outputs that node's relative position (slot number). The second,<br />
<br />
cnum, inputs a range of slot numbers, and outputs the names of the<br />
<br />
corresponding compute nodes.<br />
<br />
<br />
<br />
<br />
<br />
III C3 SUITE DOCUMENTATION<br />
<br />
---------------------------<br />
<br />
<br />
<br />
C3 command documentation may be found in two locations.<br />
<br />
1. Quick Usage Info - enter "<command> --help" at the command line<br />
<br />
2. Full Man Page - enter "man <command>" at the command line<br />
<br />
</nowiki></pre></div>Kay