From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Interested in improving networking in Plan 9
Date: Mon, 31 Aug 2009 11:52:37 -0400 [thread overview]
Message-ID: <41f21b94249accd4df903782d3ed243e@coraid.com> (raw)
In-Reply-To: <a4e6962a0908310757m6aadf842rff3b0c725f13234b@mail.gmail.com>
> > i can see in principle how this could be a good idea (no more
> > comments, though). could you elaborate, though. i have found
> > editing /lib/ndb/local works well at the scales i see.
[...]
> machines, even with multiple admins. I have a feeling it starts to
> break down with thousands of machines, particularly in an environment
> where machines are appearing and disappearing at regular intervals
> (clouds, HPC partitioning, or Blue Gene). Hundreds of thousands of
> nodes with this sort of behavior probably makes it impractical. Of
> course -- this won't effect the casual user, but its something that
> effects us.
so plunkers like us with a few hundred machines are just "casual users"?
i'd hate for plan 9 to become harder to use outside a hpc environment.
it would be good to be flexable enough to support fairly degnerate cases
like just flat files.
> > i also don't know what you mean by "transient, task specific services".
> > i can only think of things like ramfs or cdfs. but they live in my
> > namespace so ndb doesn't enter into the picture.
> >
>
> There is the relatively mundane configuration examples of publishing
> multiple file servers, authentication servers, and cpu servers.
how many file servers and authentication servers are you running?
- erik
next prev parent reply other threads:[~2009-08-31 15:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 7:21 Vinu Rajashekhar
2009-08-30 14:21 ` ron minnich
2009-08-30 16:19 ` Eric Van Hensbergen
2009-08-30 17:07 ` erik quanstrom
2009-08-30 17:40 ` Venkatesh Srinivas
2009-08-30 17:53 ` erik quanstrom
[not found] ` <c81a07350908300842w3df8321aidf55096b65eb9b77@mail.gmail.com>
2009-08-30 18:17 ` ron minnich
2009-08-30 18:35 ` ron minnich
2009-08-31 3:34 ` erik quanstrom
2009-08-31 12:45 ` Eric Van Hensbergen
2009-08-31 12:51 ` erik quanstrom
2009-08-31 12:59 ` Vinu Rajashekhar
2009-08-31 13:05 ` erik quanstrom
2009-08-31 13:48 ` Anthony Sorace
2009-08-31 14:51 ` Devon H. O'Dell
2009-08-31 15:03 ` Vinu Rajashekhar
2009-08-31 13:42 ` Eric Van Hensbergen
2009-08-31 14:04 ` erik quanstrom
2009-08-31 14:25 ` Eric Van Hensbergen
2009-08-31 14:36 ` erik quanstrom
2009-08-31 14:57 ` Eric Van Hensbergen
2009-08-31 15:52 ` erik quanstrom [this message]
2009-08-31 16:12 ` Eric Van Hensbergen
2009-08-31 14:55 ` Francisco J Ballesteros
2009-08-31 15:09 ` Eric Van Hensbergen
2009-08-31 15:56 ` erik quanstrom
2009-08-31 16:16 ` Bakul Shah
2009-08-31 16:33 ` Eric Van Hensbergen
2009-09-02 16:50 ` Bakul Shah
2009-09-02 17:10 ` Robert Raschke
2009-09-03 11:21 ` matt
2009-09-03 12:50 ` erik quanstrom
2009-09-03 16:13 ` Anthony Sorace
2009-09-03 16:29 ` erik quanstrom
2009-09-03 16:34 ` Robert Raschke
2009-09-03 21:50 ` Daniel Lyons
2009-09-03 19:08 ` Steve Simon
2009-08-31 17:09 ` Devon H. O'Dell
2009-08-31 17:20 ` erik quanstrom
2009-08-31 17:32 ` Devon H. O'Dell
2009-08-31 18:00 ` erik quanstrom
2009-08-31 4:17 ` Federico G. Benavento
2009-08-31 4:53 ` Vinu Rajashekhar
2009-08-30 17:22 erik quanstrom
2009-08-30 17:36 ` Vinu Rajashekhar
2009-08-30 17:56 ` 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=41f21b94249accd4df903782d3ed243e@coraid.com \
--to=quanstro@coraid.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).