[tahoe-dev] Grid in a Box script.
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 when I want to do integration testing for other tools I'm working on which are clients of the webapi: I want to quickly create a new empty grid to run the integration tests against. When I'm done I can nuke that Grid in a Box directory. There is no packaging config or README yet. The best docs are in the --help output. Let me know if you find this useful. Regards, nejucomo ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
[tahoe-dev] dynamic 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 if and when they change? Or does every node need a dyndns-equivalent account? Best regards, -- Anders anders.gen...@gmail.com ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] dynamic ip
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, all clients should be able to annouce their respective ip addresses if and when they change? Or does every node need a dyndns-equivalent account? Best regards, -- Anders anders.gen...@gmail.com I'm using tahoe-lafs on a LAN with dhcp for all the storage nodes and the clients (but not the introducer) and it works like a charm :) the only problem I face is to find a storage node if the tahoe proces doesn't start or if for some reason crashes since the status page doesn't show the last valid ip of offline nodes, just the ip of online nodes anyway I can look at the webpage of the status of the introducer to try to scavenge the last announced ip address of the storage nodes... ...then I've also implemented a dynamic dns which is updated by the dhcp server so when a client gets an addres it's name is consistend in the dns, so I have an offline list of all the nodes partecipating on the grid which I can check (it would be nice if the indroducer web page had an inventory utility like this, or simply an history of nodes and their addresses... ;) ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] Grid in a Box script.
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 to use that introducer, and also to use N = K = happy = 1. I use this when I want to do integration testing for other tools I'm working on which are clients of the webapi: I want to quickly create a new empty grid to run the integration tests against. When I'm done I can nuke that Grid in a Box directory. There is no packaging config or README yet. The best docs are in the --help output. Let me know if you find this useful. Regards, nejucomo Nice! I actually wrote something very similar a few days ago, but in bash: https://github.com/leif/tahoe-lafs/blob/truckee/quickgrid.sh I think yours is better :) ~leif signature.asc Description: Digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: [tahoe-dev] dynamic ip
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 are some challenges in the friends want to pool their extra storage use case. Thanks, Eric On Jun 15, 2013 11:05 AM, sickness sickn...@tiscali.it wrote: 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, all clients should be able to annouce their respective ip addresses if and when they change? Or does every node need a dyndns-equivalent account? Best regards, -- Anders anders.gen...@gmail.com I'm using tahoe-lafs on a LAN with dhcp for all the storage nodes and the clients (but not the introducer) and it works like a charm :) the only problem I face is to find a storage node if the tahoe proces doesn't start or if for some reason crashes since the status page doesn't show the last valid ip of offline nodes, just the ip of online nodes anyway I can look at the webpage of the status of the introducer to try to scavenge the last announced ip address of the storage nodes... ...then I've also implemented a dynamic dns which is updated by the dhcp server so when a client gets an addres it's name is consistend in the dns, so I have an offline list of all the nodes partecipating on the grid which I can check (it would be nice if the indroducer web page had an inventory utility like this, or simply an history of nodes and their addresses... ;) ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
