From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 and VMs
Date: Fri, 2 Sep 2016 16:01:42 -0700 [thread overview]
Message-ID: <20160902230142.B547B124AEB1@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 02 Sep 2016 15:08:16 PDT." <20160902220816.GA70550@wopr>
On Fri, 02 Sep 2016 15:08:16 PDT Kurt H Maier <khm@sciops.net> wrote:
>
> > However, if anyone makes plan9 work under bhyve or khyve I'm
> > interested.
>
> I'm also interested in this, and every once in a while I test it out.
> Nothing worth reporting yet, but once I get something running I'll
> report it here.
Great!
> > Separately, an interesting project would be to implement plan9
> > sandboxes (ala linux "containers" or freebsd "jails)" so that
> > one can easily set up a cluster of plan9 boxes.
>
> mycroft's ANTS tools can be used to do this very effectively. He's
> written copious documentation, including step-by-step walkthroughs, that
> cover doing just this. I've got his code preserved, but I need to
> gather up the various texts and stash them in a repo alongside the code.
[I had meant to post the following on that silly "9fans dead
or alive" thread. Better late than never!]
What I want is to have multiple plan9 virtual nodes (each with
its own IP address and a full set of udp/tcp ports and network
interfaces and potentially independent storage and each can be
started up/shutdown independently). For the experts this is
probably trivially doable given plan9 namespaces.
The idea is to be able to easily bring up a cluster of nodes
providing a set of services. Example: a venti backup server.
a source mirror server etc.
Going one step further, a deployment program should be able to
read a single config file, build or pull in all the required
binaries from some standard repo, add in storage, data files
etc. and stand up all the services.
I was thinking that a platform-as-a-service setup can make
application services largely independent of the underluing OS.
Particularly if they are built in Go!
next prev parent reply other threads:[~2016-09-02 23:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 21:42 Adriano Verardo
2016-09-01 22:16 ` Julius Schmidt
2016-09-01 22:49 ` Nickolas Peter
2016-09-01 22:49 ` Nickolas Peter
2016-09-02 2:49 ` Adriano Verardo
2021-11-21 21:35 ` Conor Williams
2016-09-02 2:58 ` Adriano Verardo
[not found] ` <CAJDwFdg87Tki4Ldx+NY+mGnHV6iBUKuGgOY-CU5+4QLAiTYzWg@mail.gmail.com>
[not found] ` <CAJDwFdj2F=pkd9qu4R_HRZ__hd1SwHZ21dkCuQQUgbN=HiNUiw@mail.gmail.com>
2016-09-02 3:06 ` Prof Brucee
2016-09-02 3:15 ` Adriano Verardo
2016-09-02 10:27 ` cinap_lenrek
2016-09-02 10:30 ` cinap_lenrek
2016-09-02 16:37 ` Adriano Verardo
2016-09-02 17:41 ` cinap_lenrek
2016-09-02 20:54 ` Adriano Verardo
2016-09-02 21:09 ` Bakul Shah
2016-09-02 21:15 ` stanley lieber
2016-09-02 22:00 ` Bakul Shah
2016-09-02 22:08 ` Kurt H Maier
2016-09-02 23:01 ` Bakul Shah [this message]
2016-09-02 23:02 ` Lyndon Nerenberg
2016-09-03 17:15 ` Bakul Shah
2016-09-02 21:15 ` cinap_lenrek
2016-09-03 1:50 ` Adriano Verardo
2016-09-03 6:52 ` hiro
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=20160902230142.B547B124AEB1@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).