[tahoe-lafs-trac-stream] [Tahoe-LAFS] #573: Allow client to control which storage servers receive shares
Tahoe-LAFS
trac at tahoe-lafs.org
Wed Dec 31 03:42:27 UTC 2014
#573: Allow client to control which storage servers receive shares
------------------------------------+-------------------------------------
Reporter: swillden | Owner:
Type: enhancement | Status: reopened
Priority: normal | Milestone: undecided
Component: code-peerselection | Version: 1.2.0
Resolution: | Keywords: extensibility usability
Launchpad Bug: |
------------------------------------+-------------------------------------
Comment (by linshu):
Daria,
Thanks for reopening the ticket.
Basically, my idea is continuing using the PSI framework implemented by
Warner. But, instead of using a fix algorithm inside Tahoe, we can use a
callback to hook up an outside server selection function.
The input of the callback will be online servers got from
storage_client.get_connected_servers() call, the return will be a sorted
set of active servers.
In the server data structure or announcement, we can extend an external
extension dictionary for 3rd party announcing their own parameters matrix,
then the 3rd party sorting callback can use these extension to do the real
sorting.
In this way, Tahoe framework will be total topology and server preference
un-aware. Giving the both neutral Tahoe framework and extensible friendly
interface to 3rd party and future server selection capability.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/573#comment:17>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list