9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan9 usage but used to parallel MPI on linux..
Date: Mon, 31 Oct 2016 10:18:28 +0000	[thread overview]
Message-ID: <3be8d0bcba6b94f503385797c2113718@hamnavoe.com> (raw)

Quoting from the Plan 9 wiki (whose web interface doesn't seem to
be functioning at present):

> LEVEL 8: RESEARCH AND COMPUTATION GRIDS WITH CUSTOM CONTROL LAYERS AND UNIQUE CAPABILITIES
>
> In its role as a research operating system, the capabilities of Plan
> 9 as a distributed system are often extended by specific projects
> for specific purposes or to match specific hardware. Plan 9 does not
> include any built-in capability for things like task dispatch and
> load balancing between nodes. The Plan 9 approach is to provide the
> cleanest possible set of supporting abstractions for the creation of
> whatever type of high-level clustering you wish to create. Some
> examples of research grids with custom software and capabilities:
>
>  *	The main Bell Labs Murray Hill installation includes additional
> 	software and extensive location specific configuration
>  *	The [Laboratorio de Sistemas | http://lsub.org] and project
> 	leader Francisco J Ballesteros (Nemo) created Plan B and the
> 	Octopus, derived from Plan 9 and Inferno respectively.
>  *	The [XCPU project | http://xcpu.sourceforge.net] is clustering
> 	software for Plan 9 and other operating systems created at the Los
> 	Alamos National Laboratory
>  *	The [Plan 9 on IBM Blue Gene |
> 	http://doc.cat-v.org/plan_9/blue_gene] project utilizes special
> 	purpose tools to let Plan 9 control the architecture of the IBM
> 	Blue Gene L.
>  *	The [ANTS | http://ants.9gridchan.org] Advanced Namespace ToolS
> 	are a 9gridchan project for creating failure-tolerant grids and
> 	persistent LAN/WAN user environments.
>
> These are examples of projects which are built on 9p and the Plan 9
> design and customize or extend the operating system for additional
> clustering, task management, and specific purposes. The flexibility
> of Plan 9 is one of its great virtues. Most Plan 9 users customize
> their setups to a greater or lesser extent with their own scripts or
> changes to the default configuration. Even if you aren't aspiring to
> build a 20-node "Manta Ray" swarm to challenge Nemo's Octopus,
> studying these larger custom systems may help you find useful
> customizations for your own system, and the Plan 9 modular design
> means that some of the software tools used by these projects are
> independently useful.




             reply	other threads:[~2016-10-31 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 10:18 Richard Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-31  0:33 Darren Wise
2016-10-31  2:01 ` Chris McGee

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=3be8d0bcba6b94f503385797c2113718@hamnavoe.com \
    --to=9fans@hamnavoe.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).