Title: Recommended hardware
Hi John:
 
We have the Cluster Register which keeps track of the number of registered installations of OSCAR:
 
http://oscar.openclustergroup.org/cluster-register
 
(I encourage you to register your cluster)
 
If you look at the full details, some times they list model #s of their hardware.
 
At any rate, the place I work for has some IBM HS20 blades and also some Sun Opteron nodes (Sun Fire X4100), they both work fine with OSCAR.  The IBM HS20s are running OSCAR 3.0 and the Sun Fires are running OSCAR development code (from SVN trunk).
 
The latest version of SystemImager has a new functionality where you can build the boot kernel/initrd.img from the OS you are running, therefore if the OS installs fine on your hardware, you are "guranteed" that SystemImager will work with it.  Although this functionality is still somewhat experimental, I have had good experiences with it (in fact I used this feature to install OSCAR on the Sun Fires, they use SAS HD and would otherwise not work with stock SystemImager binaries...)
 
If you have problems with your hardware, I'm sure we'll be able to help you figure out the problem :)
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of OSCAR
Sent: Friday, February 10, 2006 7:02
To: [email protected]
Subject: [Oscar-users] Recommended hardware

We're getting ready to deploy a new cluster and I'm back to looking at hardware options.  Is there a list anywhere of what people have installed OSCAR clusters on?  I'm looking to minimize deployment issues and am specifically interested in blade systems and opteron based systems (probably sun or ibm).

Any advice is appreciated.  :)

John Artman
CCNA, MCP, RHCE/CT
Senior Systems Engineer
ENSCO Inc.


The information contained in this email message is intended only for the use of the individuals to whom it is addressed and may contain information that is privileged and sensitive. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by email at the above referenced address. Thank you.

Reply via email to