[tahoe-lafs-trac-stream] [Tahoe-LAFS] #467: allow the user to specify which servers a given gateway will use for uploads

[Tahoe-LAFS]

#467: allow the user to specify which servers a given gateway will use for
uploads
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:
         Type:           |     Status:  new
  enhancement            |
     Priority:  major    |  Milestone:  soon
    Component:  code-    |    Version:  1.1.0
  peerselection          |   Keywords:  availability preservation cache
   Resolution:           |  anti-censorship placement backend rollback add-
Launchpad Bug:           |  only
-------------------------+-------------------------------------------------

Comment (by leif):

 The [https://github.com/tahoe-lafs/tahoe-lafs/pull/204 preferred_peers
 branch landed] a couple months ago.

 The [https://github.com/tahoe-lafs/tahoe-lafs/compare/master...leif
 :introless-multiintro introless-multiintro] branch (which is also
 discussed in #68) works and is up to date with master but I still have a
 few things I want to do with it before opening a pull request for it
 (tests, and moving the introless config to a JSON file).

 The current thing it implements includes roughly what was described in
 this ticket, but (as discussed with Brian at last week's Nuts and Bolts
 meeting) I'm going to change the configuration interface to use a JSON
 file instead of hacking structured data into the key names in `[client-
 server-selection]` (as described in this ticket).

 I'm tempted to add this to the 1.10.3 milestone (#68 is already there),
 but actually there are other things I want to do to satisfy this ticket
 which I don't think will happen by then (even if the introless-multiintro
 branch does):
 * actually do what the title implies, and allow the user to specify that
 some servers should be used for uploads while others are read-only (a per-
 server configuration, plus a default for introduced servers without a
 local configuration).
 * require that specific servers receive shares in order for an upload to
 be considered successful ("`peers.required`")

 Or maybe those should be two separate tickets and this one can close if
 introless-multiintro lands without those features?

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467#comment:33>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage