A cluster of V120s - Newcomer basic questions

Hi Folks,

I've been reading the Sun Cluster manuals for the last week and a half, but still haven't got a firm grip on some of the concepts, so I'd like to bounce some ideas of you more experienced folks to see if what I'm trying to do is even workable.

I'm trying to upgrade a small-ish system from its current ramshackle basis of disparate hardware to something more concise and organized, but as is often the case, I have a small budget. What I do have, though, is about fifteen V120s sitting in the warehouse. What I'm looking to do is build a cluster of ten V120s, which would be the processing core of the network. All sunray, db, filestorage and email gateway functions would be handled by other systems, this cluster would simply run the hundreds of little scripts we use to generate reports, deliverables and the likes, no major software applications needed.

On the surface it seems like a simple idea, the V120s have dual 10/100 ethernet ports, one for the private network, one for the public. The cluster would NFS mount files from my two file servers, scripts would access the db, output files to email or the file server etc.etc., but the Sun documentation keeps talking about needing dual backside network interfaces, lots of redundant paths to disk storage etc. and I'm getting a bit lost. Is it possible to create a simple cluster of redundant systems without all of the dual path requirements?

Said another way, is this idea of a very simple stack of V120s practicle? I would really like it if my users can log onto the Sunray servers, ssh over to the cluster, write/edit their scripts, toss them into cron and let the cluster munch on them.

Would appreciate any insight and guidance you folks can provide.

Thanks

Simon

[1792 byte] By [Simon_Ca] at [2007-11-26 18:10:23]
# 1

Hi Simon,

the definition of "cluster" is not consistent across the industry. I think there are compute clusters, used in number crunching and job scheduling, and High Availability clusters to offer HA services to clients.

Looking at your requirements, it seems as if Sun Cluster is not the right fit, but what you want is an engine that is capable of distributing jobs to a "cluster" of compute nodes and deliver the results to clients. This has less to do with HA clusters, like Sun Cluster.

You should have a look at the Sun Grid Engine, e.g. at http://www.sun.com/software/gridware/.

To answer your questions about Sun Cluster though. One of the goals of an HA configuration is to prevent single errors to disrupt service. So redundant interconnects, redundant paths to shared storage and redundant networks all try to achieve this. You could run an HA cluster without this redundancy but at the end would have worse availability.

Regards

Hartmut

HartmutSa at 2007-7-9 5:42:42 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 2
It sounds like you want a Sun Grid Engine (cluster) configuration rather than a Sun Cluster. Grid Engine allows you to schedule jobs to a set of target machines. Sun Cluster is more for making applications highly available.Tim
Tim.Reada at 2007-7-9 5:42:42 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...