Mailinglist Archive: opensuse (3506 mails)
| < Previous | Next > |
Re: [SLE] SUSE = Ubuntu?
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Date: Wed, 27 Sep 2006 17:20:46 +0000 (UTC)
- Message-id: <20060927171915.GA29771@xxxxxxxxxxxxxxxx>
On Fri, Sep 22, 2006 at 12:46:09AM -0500, M Harris wrote:
> On Thursday 21 September 2006 15:15, Josef Wolf wrote:
> > Sounds interesting. You made me curious. Can you please provide some
> > more info?
>
> http://www.beowulf.org/
>
> First, see the above link for general info regarding the concept
> generally...
Well, I know the general concept of a cluster and beowulf. But you
mentioned "network is your data". When you ssh to a different host to
start your app, your data is located on this host. Having a tunnel to
forward the display back to your original host don't make any difference
here. So what do you mean when you say that your data is redundantly
distributed? How is the data to be distributed to make sure it will be
accessible from anywhere and won't disappear regardless which machines
fail?
> [ ... ] which specific drives are mirroring her spreadsheets... she
> only knows that this virtual space in this mega network looks to her
> like a real stand-alone machine... uh, virtual distributed network
> processing.... or, uh.... virtual distributed network hosting...
> I haven't decided yet. But the idea is that the "network brain" is
> completely redundant, auto-scaling, auto-backing, and transparent to
> the user. [ ... ] the network shifts, replicates/mirrors, everything
> stays up... all except for the brain cells that died.
This is why I asked. And this is obviosly more than just executing
remotely with forwarded X-display (as you described on a different
fork of this thread).
> On Thursday 21 September 2006 15:15, Josef Wolf wrote:
> > Sounds interesting. You made me curious. Can you please provide some
> > more info?
>
> http://www.beowulf.org/
>
> First, see the above link for general info regarding the concept
> generally...
Well, I know the general concept of a cluster and beowulf. But you
mentioned "network is your data". When you ssh to a different host to
start your app, your data is located on this host. Having a tunnel to
forward the display back to your original host don't make any difference
here. So what do you mean when you say that your data is redundantly
distributed? How is the data to be distributed to make sure it will be
accessible from anywhere and won't disappear regardless which machines
fail?
> [ ... ] which specific drives are mirroring her spreadsheets... she
> only knows that this virtual space in this mega network looks to her
> like a real stand-alone machine... uh, virtual distributed network
> processing.... or, uh.... virtual distributed network hosting...
> I haven't decided yet. But the idea is that the "network brain" is
> completely redundant, auto-scaling, auto-backing, and transparent to
> the user. [ ... ] the network shifts, replicates/mirrors, everything
> stays up... all except for the brain cells that died.
This is why I asked. And this is obviosly more than just executing
remotely with forwarded X-display (as you described on a different
fork of this thread).
| < Previous | Next > |