From: Eric Thibodeau <kyron@neuralbs.com>
To: gentoo-cluster@lists.gentoo.org
Cc: "Dice R. Random" <dicerandom@gmail.com>
Subject: Re: [gentoo-cluster] High-Availability Howto for Gentoo
Date: Tue, 11 Apr 2006 20:59:08 -0400 [thread overview]
Message-ID: <200604112059.08552.kyron@neuralbs.com> (raw)
In-Reply-To: <d9b9989b0604111611u96e7690pdf1dfc8fe54f62d8@mail.gmail.com>
Mr. Rand(),
I tend to prone the Diskless approach for the reasons you are mentionning.
You can easily switch between roots with a network boot just by modifying
your dhcp config and rebooting a node. This is really neat since you can have
the dev environment on the actual cluster, test the new root with new libs
and simply reboot some available nodes to test them. Furthermore, this
approach opens the way to having multiple boot profiles with
application-specific orientations (/me is thinking of the hellish deal of
parallel Matlab with a polluted environment and the booting into a really
optimized one for real MPI work ;)...)
As for the "un-ncecessary attacker blahblahblah... Put your head behing the
firewall. Beowulf nodes aren't meant to be publically available if they are
to be efficient. nonetheless, departmental clusters (by night) could aslo be
very possible with the diskless approach (even more so since you don't modify
the current OS, which is most probably some horribly expensive Windows with
the latest and greates Office suite which the deparment thinks is more
important that the licences for Matlab...t'is not like we're trying to do
some scientific work here eh!... (oops...dropped that one)...
Hehe, in any case, I have had only great experiences with diskless nodes at
the moment and really hope to see the Gentoo community take off on Clusterd
(with or without disks ;)
Le Mardi 11 Avril 2006 19:11, Dice R. Random a écrit :
> Hi all,
>
> On 4/11/06, Hanni Ali <hanni.ali@gmail.com> wrote:
> > Gentoo Cluster Handbook
> > I. Sys Admin Requirements - What reader must know before moving forward
> > (maybe describe clustering types here?)
> > i) Networking options etc.
> > ii) Disked vs Diskless
> > iii) more...
>
> I'm particularly interested in what people are using for diskless
> nodes and managing upgrades of system images across the cluster. I'm
> envisioning a system where I have a build environment in which I can
> upgrade system software and test functionality on a development
> machine and then take a snapshot of the system and copy that up to a
> NAS device so that the nodes can then boot it. It would be even
> better if I could specify which packages I wanted (or rather, didn't
> want) on the system images so that I could avoid having un-necessary
> and potentially attacker-friendly packages such as gcc and portage on
> the cluster nodes.
>
--
Eric Thibodeau
Neural Bucket Solutions Inc.
T. (514) 736-1436
C. (514) 710-0517
--
gentoo-cluster@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-12 0:59 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 [this message]
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
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=200604112059.08552.kyron@neuralbs.com \
--to=kyron@neuralbs.com \
--cc=dicerandom@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