[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2788: add connection-policy configuration

[Tahoe-LAFS]

#2788: add connection-policy configuration
------------------------------+-----------------------
     Reporter:  warner        |      Owner:
         Type:  enhancement   |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-network  |    Version:  1.11.0
   Resolution:                |   Keywords:
Launchpad Bug:                |
------------------------------+-----------------------

Comment (by warner):

 Thoughts from our meeting today:

 * the smallest cleanup change that we could probably land right now would
 be a follow-on to #2759, which would change the `tub_options` that are
 passed through `StorageFarmBroker` into `NativeStorageServer`. It would
 change that `tub_options` from a dictionary into a tuple of two
 dictionaries. The first dict would be used to call `Tub.setOption()` as
 now. The second would be used to call `Tub.addConnectionHintHandler()` (so
 the keys would be hint types and the values would be handler instances).
 * the next step would be to wait for a Foolscap release that exposes
 `DefaultTCP` in a stable place
 ([https://foolscap.lothar.com/trac/ticket/260 foolscap#260]), then change
 the `tub_options` default to include `{"tcp": DefaultTCP()}`, and change
 `NativeStorageServer.start_connecting()` to call
 `Tub.removeAllConnectionHintHandlers()` first. This will make it easy to
 modify the global connection policy in a later step

 In parallel to that, we can continue as planned (in
 comment:11:ticket:2759) to add patches that read from `connections.yaml`,
 one section at a time (maybe starting with `introducers`), leaving the
 connection policy stuff (and thus Tor) until the end.

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