public inbox for gentoo-cluster@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin Bronder <jsbronder@gmail.com>
To: gentoo-cluster@lists.gentoo.org
Subject: Re: [gentoo-cluster] High-Availability Howto for Gentoo
Date: Sat, 08 Apr 2006 23:18:31 -0400	[thread overview]
Message-ID: <44387D07.1080509@gmail.com> (raw)
In-Reply-To: <789d27b10604070830l52bb779em85e15979bb0fe733@mail.gmail.com>

Greetings,

I'm currently employed at a site with some Xserve G5's and a smattering 
of PIII's.
I cannot comment on High Availability Clusters, but I'll be more then 
willing to
discuss the HPC side of clusters.

Right now we primarily run OS X on the G5's, however work is in progress 
to allow
job-submission time switching between OS X and Linux (Debian or Gentoo 
currently,
others in the future possibly) based upon user-submitted requests.

As we run a variety of operating systems, I personally prefer to compile 
the HPC-
orientated applications from source.  Anyways, I noticed a request for 
software
recommendations earlier in this thread, so here's a list of the first 
things I
end up installing when we build a test/development cluster, along with
the versions I have running.

Torque (2.0.0p5)
Mpich (1.2.7)
Mpichgm (Myrinet support, based on 1.2.6 )
Mpiexec (0.80)
Atlas (3.7.11)
HPL (To test the install mainly)

We also find it nice to have server(s) providing:
LDAP
DHCP and related netbooting services.  (We've written our own, highly 
alpha stage right now).
NFS for home directories only.  We've found numerous scalability 
problems with diskless.

Of course the shameless plug for our MyPBS package is also required,
http://sourceforge.net/projects/my-pbs/

This is just a quick list of of what I think any documentation on a HPC 
cluster needs to
cover at minimum.  I'm by no means an expert, but I would like to offer 
my help.

Hanni Ali wrote:

> Ok,
>
> I suggest we try to put the documentation together on gentoo-wiki.com 
> <http://gentoo-wiki.com> I've always found this site an excellent 
> resource.
>
> There are already two stubs which I feel we should build on and kyron 
> has compiled an excellent list of programs if you follow the links.
>
> http://gentoo-wiki.com/Index:HOWTO#Build_a_Gentoo_High_Performance_Cluster
>
> I suggest we start Build a Gentoo High Availability Cluster.
>
> http://www.gentoo.org/proj/en/cluster/
>
> This is the gentoo cluster page and we only have three How To's All of 
> which have floors I've kept tabs on problems I've run into with the 
> HPC howto and distcc howto. I feel we should keep openMosix separate 
> and have a completely separate set of Howto's for that.
>
> My clusters are generally diskless nodes so I suggest we try to 
> incorporate this howto into the gentoo-wiki
>
> http://www.gentoo.org/doc/en/diskless-howto.xml 
> <http://www.gentoo.org/doc/en/diskless-howto.xml>
>
> Though this also has it's fair share of difficulties.
>
> I'm prepared to share a certain amount of my work on this. It would be 
> nice to make this documentation easily understandable for all and I'm 
> always up for people adding where they run into problems and WHY into 
> these sort of documents.
>
> I'm looking carefully at HA diskless nodes and ways in which to ensure 
> redundancy if the master node fails. Suggestions on this would be 
> welcomed.
>
> How many people would be interested in helping out with this. If 
> you've read this far it must be because it's a Friday afternoon so 
> anything can distract you!
>
> Cheers
>
> Hanni
>
>

-- 
Justin Bronder
University of Maine, Orono

Advanced Computing Research Lab
20 Godfrey Dr
Orono, ME 04473
www.clusters.umaine.edu

Mathematics Department
425 Neville Hall
Orono, ME 04469


-- 
gentoo-cluster@gentoo.org mailing list



      parent reply	other threads:[~2006-04-09  3:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 11:18 [gentoo-cluster] High-Availability Howto for Gentoo Mathias Weigt
2006-04-07 11:39 ` Hanni Ali
2006-04-07 12:16   ` Jared Greenwald
2006-04-07 14:52 ` Bryan Stalcup
2006-04-07 15:30   ` Hanni Ali
2006-04-07 20:31     ` Jan Klopper
2006-04-11  6:57       ` Ramon van Alteren
2006-04-11  9:59         ` Hanni Ali
2006-04-11 13:17           ` Ramon van Alteren
2006-04-11 14:47             ` busby
2006-04-11 16:01               ` Hanni Ali
2006-04-11 16:13                 ` busby
2006-04-11 16:38                   ` Hanni Ali
2006-04-11 16:55                   ` Ramon van Alteren
2006-04-11 18:40                     ` busby
2006-04-11 20:56                       ` Ramon van Alteren
2006-04-11 23:11                 ` Dice R. Random
2006-04-12  0:59                   ` Eric Thibodeau
2006-04-12  2:23                     ` Dice R. Random
2006-04-11 16:10               ` Brady Catherman
2006-04-11 20:51                 ` Donnie Berkholz
2006-04-11 21:57                   ` Brady Catherman
2006-04-11 22:02                     ` Donnie Berkholz
2006-04-11 20:36             ` Donnie Berkholz
2006-04-09  3:18     ` Justin Bronder [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44387D07.1080509@gmail.com \
    --to=jsbronder@gmail.com \
    --cc=gentoo-cluster@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox