[tahoe-dev] Tahoe prefered peer selection

[Yu Xiang]

Dear Leif,
Thanks for the reply! I still have one question.
Iv'e installed the current code you commited, since i don't have so many
servers i am using the public test grid of tahoe to test it, that means i
have to go to localhost:3456 to get the server ids to be setup, however,
when i start the tahoe client node at my local computer the web ui directly
showed an exception <type 'exceptions.AttributeError'>: Client instance has
no attribute '_node_key'. I've read about the node key link you provided,
and that means a node id is encrypted by this key, but does this error
suggests i should set it up somewhere in the cfg file?

Thanks for your help! I really appreciate it!

Best,
Yu



On Thu, Jun 13, 2013 at 2:24 AM, Leif Ryge <leif at synthesize.us> wrote:

> On Wed, Jun 12, 2013 at 10:09:01PM -0400, Yu Xiang wrote:
> > Dear leif,
> > i am recently trying to set chunks to be sent to prefered servers in
> > tahoe-lafs, and i came across your code in
> > https://github.com/tahoe-lafs/tahoe-lafs/pull/39, which is really what i
> > need. However, there are something that i don't fully understand in the
> > code, hopefully you can help me with this, since it's really urgent and
> > i've tried many methods and spent plenty of time on this before i met
> this
> > perfectly matched code. I really need this help.
> >
> > First it seems that i have to type in preferred peers in tahoe.cfg file,
> > but in which format? from the code it should be peers.prefered ,
> pstrip()?
> > but in this case i am not able to compile the code successfully for now,
> i
> > did the changes in the files in your commit, are there anything else i
> need
> > to change?
> >
> > Thanks in advance! Your help will be highly appreciated since i really
> need
> > this!
> >
> > Best,
> > Yu
>
> Thanks for asking! You've caused me to discover a problem with the
> preferred peers code and/or documentation.
>
> I've been using a comma-seperated list of node IDs (you can find the
> nodeid in the my_nodeid file in the storage node's directory). But, it
> appears that the method I'm using to obtain it - the storage_client
> object's get_longname method - now (as of 1.10) returns the new node
> key instead! This is displayed in the web ui in the same place as the
> nodeid was, but is prefixed with v0- which I *think* should not go in
> the preferred peers list.
>
> So, I *think* the current code should work if you list whatever you see
> in the web ui under a node's nickname, except if it starts with v0- you
> should remove that part. But I'm going to do some more testing now, and
> will push updated docs (and possibly code) in the near future.
>
> Btw, would you mind CC'ing the tahoe-dev list? I'm not sure if anyone
> else is using this code, but I'd like to keep information about it there
> just in case.
>
> ~leif
>
> ps: you can read about the new node keys here:
> https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/nodekeys.rst
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130613/50d0790e/attachment-0001.html>