The Tahoe-LAFS decentralized secure filesystem.
Go to file
2007-03-28 10:48:29 -07:00
bin rename bin/allmydata to bin/allmydata-tahoe, so the package can co-exist with the regular (amdlib) package 2007-01-19 20:05:33 -07:00
dapper/debian debian: change name of debian packages to 'allmydata-tahoe' to avoid conflicts 2006-12-05 14:40:02 -07:00
docs add the 'Denver Airport' design doc, for Chord-based peer selection 2006-12-01 19:09:14 -07:00
misc control.py: fix get_memory_usage, add a sample client tool 2007-03-07 20:31:49 -07:00
pyfec pyfec: correctly handle wrongly typed input by raising exception 2007-03-27 23:53:32 -07:00
sid/debian debian: change name of debian packages to 'allmydata-tahoe' to avoid conflicts 2006-12-05 14:40:02 -07:00
src remove left-over early encode mechanism 2007-03-28 00:06:03 -07:00
twisted/plugins tests: add support for figleaf code-coverage gathering 2006-12-06 15:26:12 -07:00
.darcs-boringfile more work on a memory-footprint test program 2007-03-12 16:28:37 -07:00
client.tac clients now get the queen's pburl from a file named roster_pburl, not hardcoded in the .tac file 2006-12-04 04:27:40 -07:00
Makefile start work on a memory-measuring test tool 2007-03-08 18:12:24 -07:00
MANIFEST.in add distutils-based packaging 2006-12-05 01:29:26 -07:00
queen.tac add beginning queen code 2006-11-30 15:39:24 -07:00
README added a README explaining how to get started and what library dependencies are needed 2007-03-28 10:48:29 -07:00
roadmap.txt switch to pyfec 2007-03-28 00:05:16 -07:00
setup.py use pyfec instead of py_ecc for erasure coding and update API to codec 2007-02-01 16:07:00 -07:00
simulator.py fix bug in simulator graphing (still doesn't work though) 2006-11-29 11:42:07 -07:00
sizes.py some pointless fussing about with sizes.py 2006-11-30 15:14:39 -07:00

Welcome to the AllMyData "tahoe" project. This project implements a
scalable distributed fault-tolerant filestore.

The main application code is in the 'allmydata' package, under src/allmydata/
. There is also a patched version of PyCrypto (adding a faster CTR-mode) in
src/Crypto/ which gets installed to the 'allmydata.Crypto' package (since the
API is different than the normal Crypto package). It also includes Zooko's
PyFEC library, a fast python wrapper around the Rizzo 'fec' C library,
installed to the 'pyfec' package and located in src/pyfec/ .

DEPENDENCIES:

 Python 2.4 or newer (tested against both 2.4 and 2.5)
  http://python.org/
 Twisted (probably 2.4.0 or newer) (subpackages 'core', 'web'
  http://twistedmatrix.com/
  You'll want the following subpackages: core, web, trial, conch.
  Note that Twisted requires zope.interface, and that the standard
  batteries-included Twisted distribution includes a copy.
 Foolscap (probably 0.0.7 or newer)
  - note: since the Foolscap wire protocol is not yet compatible from one
    release to the next, make sure all of your nodes are using the same
    version of Foolscap
  http://twistedmatrix.com/trac/wiki/FoolsCap
 Nevow (probably 0.9.0 or later)
  http://divmod.org/trac/wiki/DivmodNevow

BUILDING:

 Just type 'make'. If the desired version of 'python' is not already on your
 $PATH, then type 'make PYTHON=/path/to/your/preferred/python'.

 'make test' runs the unit test suite.

 'make deb-dapper' or 'make deb-sid' will construct a debian package named
 'allmydata-tahoe'.

RUNNING:

 The installed package creates an 'allmydata-tahoe' executable, usually in
 /usr/bin . This tool is used to create, start, and stop nodes.

 Somewhere in your mesh there must be a central 'queen' node. This is
 constructed by running 'allmydata-tahoe create-queen --basedir WHERE'. Once
 constructed, you can start the queen by running 'allmydata-tahoe start
 --basedir WHERE'. Inside that base directory, there will be a pair of files
 'introducer.furl' and 'vdrive.furl'. Make a copy of these, as they'll be
 needed on the client nodes.

 To construct a client node, pick a new working directory for it, then run
 'allmydata-tahoe create-client --basedir $HERE'. Copy the two .furl files
 from the queen into this new directory, then run 'allmydata-tahoe start
 --basedir $HERE'. After that, the client node should be off and running. The
 first thing it will do is connect to the queen and introduce itself to all
 other nodes on the mesh. You can follow its progress by looking at the
 $HERE/twistd.log file.

 To actually use the client, enable the web interface by writing a port
 number (like "8080") into a file named $HERE/webport and then restarting the
 node with 'allmydata-tahoe restart --basedir $HERE'. This will prompt the
 client node to run a webserver on the desired port, through which you can
 view, upload, download, and delete files.