[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 research
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Old description:

> I am quite sure you are aware of the problem [of] an introducer [...]
> 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 [...] 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 [of] an introducer [...]
 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
 [...] 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 (by zooko):

 I'd like to get this into trunk ASAP! So it can get thoroughly tested out
 for Tahoe-LAFS v1.11. If I understand correctly, lebek's notes at
 comment:92 and [//pipermail/tahoe-dev/2012-November/007867.html our
 discussion] from a weekly dev chat are telling us what next steps to take.

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