public inbox for gentoo-cluster@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dice R. Random" <dicerandom@gmail.com>
To: gentoo-cluster@lists.gentoo.org
Subject: Re: [gentoo-cluster] High-Availability Howto for Gentoo
Date: Tue, 11 Apr 2006 19:23:51 -0700	[thread overview]
Message-ID: <d9b9989b0604111923p572a9962ha03a050418372e2b@mail.gmail.com> (raw)
In-Reply-To: <200604112059.08552.kyron@neuralbs.com>

Hi Eric,

Sorry, forgot to CC the list on this.  Here goes...

On 4/11/06, Eric Thibodeau <kyron@neuralbs.com> wrote:
> 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 ;)...)

Yes, this is exactly what I had in mind :)

>         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

Sorry, I should have mentioned that my application is load balancing /
HA rather than HPC.  There will certainly be some very strict firewall
rulesets in place, however I do have to deal with serving up user
requests.  If someone manages to poke a hole in Apache or whatever and
gets themself a shell I don't want to give them any tools which might
help them along their quest for root.

-- 
gentoo-cluster@gentoo.org mailing list



  reply	other threads:[~2006-04-12  2:23 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 [this message]
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=d9b9989b0604111923p572a9962ha03a050418372e2b@mail.gmail.com \
    --to=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