If it helps, I've noticed that Tahoe seems to be designed for use in a
business environment where one entity controls all of the nodes, each node
has a static IP, there is very little down time, very little node turnover,
very high internode bandwidth compared to gateway-user bandwidth, etc.
There
On Sat, Jun 15, 2013 at 05:43:13PM +0200, Nathan wrote:
> Hello,
>
> In the spirit of release early/often here's a python script I just wrote:
>
> https://github.com/nejucomo/lafs-giab
>
> "giab" is "Grid in a Box". It creates an introducer, and a storage node,
> and configures the storage node
On Sat, Jun 15, 2013 at 06:34:03PM +0200, Anders wrote:
>
> Dear list!
>
> I am slightly uncertain about the inner workings of the tahoe grid when it
> comes to (storage)nodes with dynamically assigned ip addresses.
> I would have though that as long as the introducer is running on a static ip,
Dear list!
I am slightly uncertain about the inner workings of the tahoe grid when it
comes to (storage)nodes with dynamically assigned ip addresses.
I would have though that as long as the introducer is running on a static ip,
all clients should be able to annouce their respective ip addresses
Hello,
In the spirit of release early/often here's a python script I just wrote:
https://github.com/nejucomo/lafs-giab
"giab" is "Grid in a Box". It creates an introducer, and a storage node,
and configures the storage node to use that introducer, and also to use N =
K = happy = 1.
I use this
