[tahoe-lafs-trac-stream] [tahoe-lafs] #68: implement distributed introduction, remove Introducer as a single point of failure

[tahoe-lafs]

#68: implement distributed introduction, remove Introducer as a single point of
failure
-------------------------+-------------------------------------------------
     Reporter:  lvo      |      Owner:  lebek
         Type:           |     Status:  new
  enhancement            |  Milestone:  soon
     Priority:  major    |    Version:  0.2.0
    Component:  code-    |   Keywords:  scalability availability
  network                |  introduction gsoc docs anti-censorship test-
   Resolution:           |  needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by zooko):

 * milestone:  1.10.0 => soon


Old description:

> I am quite sure you are aware of the problem that an introducer/vdrive
> server crash bringing everything down.  I read your roadmap.txt but I
> didn't find anything specific to address this.  May I suggest using
> introducers.furl and vdrives.furl where multiple entries can be used  and
> the information is updated to all introducers at the same time when a
> peer makes an update.
>
> Also, upon adding a new introducer, there should be a way to discover all
> the info currently on the existing introducer.  I think I am making this
> part sounds more trivial than it is.
>
> Thanks
> Lu

New description:

 I am quite sure you are aware of the problem that an introducer/vdrive
 server crash bringing everything down.  I read your roadmap.txt but I
 didn't find anything specific to address this.  May I suggest using
 introducers.furl and vdrives.furl where multiple entries can be used  and
 the information is updated to all introducers at the same time when a peer
 makes an update.

 Also, upon adding a new introducer, there should be a way to discover all
 the info currently on the existing introducer.  I think I am making this
 part sounds more trivial than it is.

 Thanks
 Lu

--

Comment:

 This isn't ready for Tahoe-LAFS v1.10, but as [//pipermail/tahoe-
 dev/2012-November/007867.html recently discussed], we've decided we'd like
 to try integrating it into trunk ASAP! Lebek, or anyone else who wants to
 help, please see that mailing list discussion and reply on tahoe-dev, or
 this ticket, or join us at the next Weekly Dev Chat.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/68#comment:94>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage