<div class="gmail_quote">2008/12/9 Joe Landman <span dir="ltr"><<a href="mailto:firstname.lastname@example.org">email@example.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d"> </div><br>Which tools do you have in mind? The Autoyast package that we have set up for our customers installs the OS locally, as well as pdsh, ganglia, and several other tools. Then in our finishing scripts which the autoyast.xml file links to, we set up SGE, adjust NIS/mounts, ...<br>
<br>As I indicated, we get operational compute nodes shortly after turning them on. The current version of autoyast.xml + finishing scripts we have constructed also builds a RAID0 for local scratch, uses xfs file systems for root and scratch, installs OFED RPMs (on SuSE), updates the kernel to a late model (<a href="http://188.8.131.52/" target="_blank">184.108.40.206</a> or so) and does some sysctl tuning.
<div class="Ih2E3d"><br> </div></blockquote>
<div>That's how Streamline originally installed their clusters. Works fine - you do a generic SuSE install, and let the Autoyast tools do all the 'heavy lifting' then run a post-install script which integrates your nodes into the cluster, as Joe says by enabling NSI binding, copying across the batch startup script (yada yada...).</div>
<div>I agree with Joe this would probably be a good way forward for you.</div>