The Public Test Grid

This page is about the "Public Test Grid", which is also called the "pubgrid". The pubgrid has several purposes:

• to make it easier for people new to tahoe to begin to experiment
• to enable small-scale trial use of tahoe
• to help the tahoe community gain experience with grids of heterogenous servers without a pre-existing social organization

The pubgrid also has two critical non-goals

• The pubgrid is not intended to provide large-scale storage, and it is not intended to be reliable. Don't store any data in the pubgrid if losing it would cause trouble.
• Don't view the pubgrid as a free hundreds-of-MB backup service.

History

Note that the introducer furl has changed recently (as of Feb. 2013).

A version of the pubgrid existed until some time in 2012, when the introducer was lost. In February of 2013, a new introducer was created, resulting in a change of furl.

It is an interesting philosophical question as to whether the pubgrid with the new introducer is a different grid or not. If servers that had been connecting to the new introducer are repointed to the new introducer, it can be considered the same grid with a change of introducer, with the property that files from the old grid may still be accessible.

Cautions

The canonical way to access Tahoe-LAFS grids is to run your own client node. Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, while storage nodes provide storage of ciphertext. However, writing to the publically-writeable test directory (below) means that others can see and change your files.

Publicly writable test directory

URI:DIR2:ddg5n76x6stjb35psrcn7i3ytu:etbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa . Note that anyone may view and change this data.

How To Connect To The Public Test Grid

The test grid is subject to being updated at random times, so compatibility is likely to break without notice. Also note that an upgrade could require all files and directories to be flushed, especially as storage formats change.

The test grid is currently running an 1.0.0-compatible release (allmydata-tahoe: 1.9.2) (see "My versions" on the welcome page for the current version of the web gateway server).

Set up the code according to docs/quickstart.rst and docs/running.rst​. This creates a client node in the .tahoe subdirectory of your home directory. Edit the following lines into the .tahoe/tahoe.cfg file:

[node] nickname = Another nickname than "None"

[client] introducer.furl = pb://hckqqn4vq5ggzuukfztpuu4wykwefa6d@publictestgrid.e271.net:50213,198.186.193.74:50213/introducer

Then run bin/tahoe start.

We created a shared public directory: feel free to use it for experimentation -- once your node is up and listening on port 3456, ​this URL should give you access to that directory.

Social Norms

By running a client node, you can store data in the pubgrid. The storage is provided by people who run storage nodes, and they share disk space and network capacity as a courtesy to the tahoe community in order to help newcomers and promote experimentation.

Norms for the pubgrid are similar to those for some private grids:

• If you are just trying out tahoe and not contributing a server, only store a small amount of data, perhaps 1-20 MB. This is perfectly fine; people contribute resources so that new people can experiment.
• If you are a more serious pubgrid participant, contribute some amount of disk space and run stable servers with public IP addresses (so that clients can connect to them). Then, only store about half as much in shares (3.3x expansion for 3/10 encoding) as you provide in storage.
• People storing more than the above small amounts of data, as well as those running servers should be on the ​tahoe-dev mailing list.

Suggested server setup:

• Enable expiration with 1-month lease maximums on your node, to keep it from just filling up.

Other Public Volunteer Grids

• ​VolunteerGrid2 (Discontinued)

Contact Info

If the pubgrid introducer appears to be down, either send an email to the tahoe-dev mailing list or contact PRab on ​irc://freenode/tahoe-lafs