From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] DHCP
Date: Sun, 16 Jun 2002 18:19:01 -0400 [thread overview]
Message-ID: <b770f7909e4434ce0e856a9f72475ff9@plan9.bell-labs.com> (raw)
I'm about to replace the current file system based state sharing in
dhcpd with the one from the internet draft:
"DHCP Failover Protocol", Ralph Droms, Bernard Volz, K. Kinnear, Arun
Kapur, Mark Stapp, Greg Rabil, Mike Dooley, Steve Gonczi, 01/24/2002,
<draft-ietf-dhc-failover-10.txt>
The current dhcpd addresses the case of a single cpu falling over, but
has a single point of failure if we lose the shared file server all
the servers are running from.
The IETF draft separates the address space so that each server only serves
from its own pool of addresses but updates the others' state through
a special protocol so that each can take over should its partner fail.
I'm a bit bothered that it only supports 2 servers but maybe I'm
being silly.
Another possible solution would be to use the current dhcpd but run it
on top of either
(1) a very reliable file server (venti?)
or
(2) a replicated file service that runs on all the servers' machines.
I don't really have (1) though venti might get there.
I know how to do (2) but then I'ld have to handle
inconsistencies and the solution looks like it'll
get so dhcp dependent that I should just go with the
draft standard.
Any comments? Someone already done it or something better?
I'm going to start on the draft version but I have nothing
against stopping or changing it later.
next reply other threads:[~2002-06-16 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 22:19 presotto [this message]
2002-06-19 12:45 ` plan9
2002-06-19 9:48 ` Sam Hopkins
2002-06-16 22:29 ynl
2002-06-19 13:53 presotto
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=b770f7909e4434ce0e856a9f72475ff9@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).