9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A note about new software for Plan 9
Date: Mon, 11 Mar 2013 22:56:29 -0700	[thread overview]
Message-ID: <20130312055629.66739B82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 12 Mar 2013 04:20:16 -0000." <ed6f9992bd1f39cffbbfcc9d547aea16@sphericalharmony.com>

On Tue, 12 Mar 2013 04:20:16 -0000 mycroftiv@sphericalharmony.com wrote:
>
> Do you think it would be helpful or welcome to re-post some of this
> material here on 9fans?

Your explanations are ok.  My guess is people don't have time
or sufficient motivation to dig deeper and read your papers.
Posting more stuff here won't help.

Motivation (for me at least) has to come from attempting to
solve "interesting" (i.e. practical, fun, &/or challenging)
problems.  Here are some examples (your ANTS may/may not be
relevant):

Jails solve specific problems (by isolating servers I reduce
exposure and can manage each service independently). In a
previous job we needed to simulate many independent virtual
hosts on each physical machine to test routing software.  We
used something similar to jail to simulate large IP networks.

Migrating a service to another machine without taking it down
so that a physical machines can be repaired/upgraded etc.

If you could bundle off a few services and move them onto a
new machine that can help with scaling during peak hours.

Controlled namespace sharing (Rangboom did this I think).
These have many uses -- screen sharing, something like google
drive or dropbox, collaborative work, etc.

Instantly bring up a brand new machine with nothing but pxe
(background installation! -- until a local FS is created and
needed files copied, you work off of a `staging' server
provided namespace).

Ability to have the same work environment and no loss of data
or context regardless of where I am in the world (and may be
not even on the same machine).

Ability to move a program closer to the data it operates on
(different pieces may be in different places).

Map N virtual machines on M physical machines -- you can do your
own virtual cluster!

Making clusters resilient against node failures.



  reply	other threads:[~2013-03-12  5:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  4:20 mycroftiv
2013-03-12  5:56 ` Bakul Shah [this message]
2013-03-12 12:33   ` sl
  -- strict thread matches above, loose matches on Subject: below --
2013-03-13  2:51 mycroftiv
2013-03-12  3:17 mycroftiv
2013-03-12  3:52 ` Bakul Shah
2013-03-12 14:57   ` Joel C. Salomon
2013-03-12 14:59     ` erik quanstrom
2013-03-12 18:27     ` Bakul Shah
2013-03-12  1:22 mycroftiv
2013-03-12  1:26 ` erik quanstrom

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=20130312055629.66739B82A@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).