[tahoe-dev] Building user made storage pool
Paul Rabahy
prabahy at gmail.com
Fri Sep 13 15:40:27 UTC 2013
Hi,
This sounds very similar to what Tahoe-LAFS can do.
* User comes to some service website, adds IP or DNS of own storage node
Tahoe uses the introducer (instead of a website) for this. Each node
configures its introducer.furl to the same thing and that puts them all on
the same grid.
* All nodes reconfigure automatically to add this storage node
Each node checks in with the introducer to learn about other nodes. This
happens automatically behind the scenes.
* User then access to all storage node together (large redundant disk)
This is exactly how a gird on tahoe works. Each node can provide storage
for all the other nodes, but this is configurable. They are not required to
share any space or can limit how much they share.
It is my understanding that in its current implementation Tahoe-LAFS will
not scale one grid to thousands of nodes. Each node tries to maintain a TCP
connection to all of the other nodes that it knows about. Because of this,
a grid of more than a few hundred will likely not work properly or bog down
the machine.
There is lots of good info in the wiki[
https://tahoe-lafs.org/trac/tahoe-lafs/wiki] and the Public Grid[
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid] works almost just how
you are talking.
On Fri, Sep 13, 2013 at 7:35 AM, Jerzy Łogiewa <jerzyma at interia.eu> wrote:
> I want to build user storage pool like that:
>
> * User comes to some service website, adds IP or DNS of own storage node
> * All nodes reconfigure automatically to add this storage node
> * User then access to all storage node together (large redundant disk)
>
> Is it possible with Tahoe?
>
> Idea is: Massive user supported storage pool, made of thousand+ of
> distributed storage node. But, automatic configuration plus storage node
> supported and configure by many people. "Big disk" for small community,
> maybe of not so technical (sysadmin) user.
>
> Sorry for my English!
>
> --
> Jerzy Łogiewa -- jerzyma at interia.eu
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130913/2f600f18/attachment.html>
More information about the tahoe-dev
mailing list