Title: OSCAR 4.2.1 testing
Hi Jeremy:
 
Thanks for testing.
 
Can you give us a bit more details about opensm?  I did not see an explicit Requires for tftp-server for the opensm package.  When you said it installs it by default, is it because it was selected in the "group of packages" you chose?
 
I wonder if there is a better way to deal with tftp-server VS atftp-server issue.  Perhaps we should rebuild atftp-server, put it in /opt/atftp-server and make sure that if tftp-server exists, we turn it off first before we turn atftp-server on.
 
P.S. Do you plan to do any tests with imaging your nodes with SystemImager using OpenIB?
 
Cheers,
 
Bernard 


From: Siadal, Jeremy C [mailto:[EMAIL PROTECTED]
Sent: Fri 13/01/2006 11:59
To: Bernard Li; OSCAR-devel
Subject: OSCAR 4.2.1 testing

We've successfully installed two 35-node clusters using OSCAR 4.2.1beta
on RHEL4U3beta. The clusters were installed using x85_64 and ia64
architectures.

Please note that we disable LAM, MPICH, PVM, pfilter, TORQUE, and MAUI
for our production needs.

I've attached the rpm lists that were used. The lists incorporate OpenIB
support that's included in the new RHEL.

One thing to note, when opensm (OpenIB fabric manager--you can find it
listed in Network Servers) is installed on the head node, it installs
tftp-server by default. You will need to manually remove this, as it
will conflict with atftp-server and cause OSCAR to crash.

Jeremy

Reply via email to