Re: If the machine run the introducer down,what can i do
Hey dstainton415 and str4d: Is there an hour per week we could all get together on IRC and/or a videoconferencing and/or screen-sharing tool and work on this? Str4d and I had previously agreed on Monday 22:00Z, but that hasn't really come together yet, and also I'm not sure if DST [*] changes Str4d's availability for that. Regards, Zooko [*] Fuck DST! ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
Hi Zooko, Yes... a once a week meeting sounds good and doable. I reside in Berlin... and I am usually awake during CET daylight hours. I would like to suggest we meet at 17:00 UTC because it would be convenient for me as I would simply stay in my office a bit longer and chat with you two. 22:00 UTC is a bit late for work nights... so I would suggest 21:00 UTC or earlier... unless it happens to be the weekend or friday night. I'm not particular about which day we meet as I currently do not have much of a weekly schedule to follow other than the square 9-6 mon-fri routine. Cheers! David On Mon, Mar 17, 2014 at 3:30 PM, Zooko Wilcox-OHearn zo...@leastauthority.com wrote: Hey dstainton415 and str4d: Is there an hour per week we could all get together on IRC and/or a videoconferencing and/or screen-sharing tool and work on this? Str4d and I had previously agreed on Monday 22:00Z, but that hasn't really come together yet, and also I'm not sure if DST [*] changes Str4d's availability for that. Regards, Zooko [*] Fuck DST! ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
That's right. If you have a backup of the introducer's private keys then you could set up a new introducer that would have the same FURL. If not, then you'll have to put in the new introducer's FURL to each storage server and each client. The multi-introducer ticket that str4d mentioned is ticket #68: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/68# implement distributed introduction, remove Introducer as a single point of failure The state of that ticket is: test-needed — it is waiting for someone to write unit tests that test the code changed by the patch. Regards, Zooko ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
On 03/17/2014 10:08 PM, Zooko Wilcox-OHearn wrote: That's right. If you have a backup of the introducer's private keys then you could set up a new introducer that would have the same FURL. If not, then you'll have to put in the new introducer's FURL to each storage server and each client. The multi-introducer ticket that str4d mentioned is ticket #68: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/68# implement distributed introduction, remove Introducer as a single point of failure The state of that ticket is: test-needed — it is waiting for someone to write unit tests that test the code changed by the patch. Regards, Zooko ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev Still the chicken-egg-problem needs to be solved: How can a virgin node get knowledge about the network without bootstrappers? :-) Of course, you can have multiple bootstrap nodes (introducer in your terms) so you have ruled out the SPoF (single point of failure) but still privacy matters are left: all introducer owner know about the network's structure, at least which IPs run the storage nodes. Okay, maybe not a topic here, as Tahoe-LAFS != Freenet. So a good advice for you @topic start is that you run your introducer on a RAID1 with at least 3 physical drives and none are SSDs please (SSD = electronic method = shorter life of the disk, HDD = magnetic = longer-lasting storage). Regards, Roland signature.asc Description: OpenPGP digital signature ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey Zooko and David, I was busy over the past several weeks, but my timetable has settled down. And yep, DST has altered my availability. I am generally available from 21:00 UTC most days, but can meet at 20:00 UTC if that is better. str4d -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJTJ8H5AAoJENXeOJaUpGWyHIQIAI5wjdc1ydDzXlJS8Oei3PqD qZU2H1yhF4WrtHt6HH5dmvjzj/RaovbrwZxYeDTqUIkoVymN27fPk1BoKnr32oYW 2Eu3UoJLDtWr2HlVbcSdh23K6AP0FVffRqN++49UOoVF6JFDWVLXiIgpz2MgHcdn XRzxAanSfHhZ95i7ia4Z64AD+8dYIroKC+Pqwi+f5RmnU+y6Ky3V2Lf58Yq4KRy0 EYreghaO81Um4SEvlZ+LW8PbgTbW/PpVt4ACqrZi8VHu8pHJErv10lIUUNtE+crn LZ7UF1j6AlJ9U5Frtt42RieiFpoo628l/jJxpl5qqGN871IWJShft44+Oxuzqgc= =sSNQ -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
On Sun, Mar 9, 2014 at 7:59 PM, xiao_s_yuan xiao_s_y...@163.com wrote: If the machine run the introducer down and can not run again,is that means I should create a new introducer on the other machine and change the furl in all the storage and client nodes? And If I can still find the file or directory in the grid? ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev I think you are correct, you need a new introducer, and the nodes in the grid need to know its furl. -- -- ظ ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Re: If the machine run the introducer down,what can i do
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is exactly why the I2P version of Tahoe-LAFS uses a multi-introducer patch which allows multiple introducers to be used for the same grid; introducers can go down indefinitely (a common problem in I2P) without destroying the grid. But if all known introducers go down, you still have the same problem of informing all nodes of the new grid. (We also have a separate monitoring script that pulls a list of known introducers from a volunteer and adds them automatically; this just abstracts the failure point back a step). There are relevant tickets on the Tahoe-LAFS bug tracker about both the multi-introducer system, and a no-introducers system. One (or both) of these should eventually get merged into Tahoe-LAFS. str4d On 03/11/2014 02:28 PM, Zancas Dearana wrote: On Sun, Mar 9, 2014 at 7:59 PM, xiao_s_yuan xiao_s_y...@163.com wrote: If the machine run the introducer down and can not run again,is that means I should create a new introducer on the other machine and change the furl in all the storage and client nodes? And If I can still find the file or directory in the grid? ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev I think you are correct, you need a new introducer, and the nodes in the grid need to know its furl. ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBCgAGBQJTHm+OAAoJENXeOJaUpGWyEmwH/24aPj/XmnZn9zH/PUPdMRO4 w1W3FoUF4lZHKhocqhMJnCrlVS+3SI2l4H5X0oc8RNeXsjzLyltlv1iExNuqd2Vd 0zgAZbllXKw36gNZtqWswrwqWYIbBK3qOiozJzB6iN9I8+HXUulMLp4dEbQ9uUOh ZHGYugoSqSy5czSMr3hVgxbnye2OHSRdSbT6LkJXzsSReLKZssPZinWBzxeVlFMM enPx3A13BG3/cKmfodZ/RByCOaLVoTk1eplKtiZkVuToQ5NFuEhZLRVzaDbVQOQ+ EAH+KNW+m6lk3+3kXMCGRfcWz5DZwpnih6SUv7jHjjejwyNIWHaol1V7jP/z6JQ= =CUeg -END PGP SIGNATURE- ___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
If the machine run the introducer down,what can i do
If the machine run the introducer down and can not run again,is that means I should create a new introducer on the other machine and change the furl in all the storage and client nodes? And If I can still find the file or directory in the grid?___ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
