[tahoe-dev] [tahoe-lafs] #68: implement distributed introduction, remove Introducer as a single point of failure
tahoe-lafs
trac at tahoe-lafs.org
Sun Oct 24 05:30:15 UTC 2010
#68: implement distributed introduction, remove Introducer as a single point of
failure
------------------------------+---------------------------------------------
Reporter: lvo | Owner: writefaruq
Type: enhancement | Status: new
Priority: major | Milestone: 1.9.0
Component: code-network | Version: 0.2.0
Resolution: | Keywords: scalability availability introduction gsoc docs review-needed
Launchpad Bug: |
------------------------------+---------------------------------------------
Comment (by writefaruq):
The final GSoC code is here
http://code.google.com/p/google-summer-of-code-2010-tahoe-
lafs/downloads/detail?name=MOFaruque_Sarker.tar.gz&can=2&q=#makechanges
Some hints to use it
- Get a fresh copy of tahoe-lafs
- Apply the above patch(es)
- Check configuration.txt to find steps to configure
A seond file "BASEDIR/introducers" configures introducers. It is necessary
to
write all FURL entries into this file. Each line in this file contains
exactly
one FURL entry. For backward compatibility reasons, any "introducer.furl"
entry found in tahoe.cfg file will automatically be copied into this file.
Keeping
any FURL entry in tahoe.cfg file is not recommended for new users.
- Edit BASEDIR/introducers and add FURLs for each introducer. Of course
you need to run them before you get a FURL.
- Play with them as you like.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/68#comment:73>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-dev
mailing list