[tahoe-lafs-trac-stream] [tahoe-lafs] #1382: immutable peer selection refactoring and enhancements

[tahoe-lafs]

#1382: immutable peer selection refactoring and enhancements
--------------------------+------------------------------------------------
     Reporter:  kevan     |      Owner:  davidsarah
         Type:            |     Status:  assigned
  enhancement             |  Milestone:  eventually
     Priority:  major     |    Version:  1.8.2
    Component:  code-     |   Keywords:  design-review-needed review-needed
  peerselection           |
   Resolution:            |
Launchpad Bug:            |
--------------------------+------------------------------------------------
Changes (by zooko):

 * milestone:  1.11.0 => eventually


Old description:

> I've been working on refactoring and improving immutable peer selection.
> I have several immediate goals for this project.
>
>   * Decouple servers of happiness specific peer selection from the more
> mechanical aspects of peer selection so that it can be easily integrated
> into SDMF and MDMF mutable files now, and other formats later;
>   * Address the shortcomings in the servers of happiness file health
> measure and its current implementation;
>   * Extend servers of happiness to file check, verify, and repair
> operations;
>   * Improve the quality and clarity of the peer selection code, easing
> future maintenance and experimentation.
>
> These improvements correspond roughly to issues presented in tickets
> #610, #614, #1115, #1124, #1130, and #1293. Unifying mutable and
> immutable peer selection is ticket #1057, though I don't expect to
> address that until after MDMF (#393) is merged and until we're done with
> this ticket.

New description:

 I've been working on refactoring and improving immutable peer selection. I
 have several immediate goals for this project.

   * Decouple servers of happiness specific peer selection from the more
 mechanical aspects of peer selection so that it can be easily integrated
 into SDMF and MDMF mutable files now, and other formats later;
   * Address the shortcomings in the servers of happiness file health
 measure and its current implementation;
   * Extend servers of happiness to file check, verify, and repair
 operations;
   * Improve the quality and clarity of the peer selection code, easing
 future maintenance and experimentation.

 These improvements correspond roughly to issues presented in tickets #610,
 #614, #1115, #1124, #1130, and #1293. Unifying mutable and immutable peer
 selection is ticket #1057, though I don't expect to address that until
 after MDMF (#393) is merged and until we're done with this ticket.

--

Comment:

 I'm moving this to Milestone: "eventually", which means that we agree it
 ought to be fixed, but we don't agree that it is going to get fixed in
 1.11.

 If someone (e.g. kevan or markberger) wants to prioritize this, then I
 suppose they **might** finish it in time for Milestone 1.11. In that case
 they can move it back into this milestone when they start working on it.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1382#comment:15>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage