[tahoe-dev] [tahoe-lafs] #213: good handling of small numbers of servers, or strange choice of servers

[tahoe-lafs]

#213: good handling of small numbers of servers, or strange choice of servers
---------------------------+------------------------------------------------
     Reporter:  zooko      |        Type:  enhancement                               
       Status:  new        |    Priority:  major                                     
    Milestone:  undecided  |   Component:  code-peerselection                        
      Version:  1.6.0      |    Keywords:  usability availability preservation repair
Launchpad_bug:             |  
---------------------------+------------------------------------------------
Changes (by USSJoin):

 * cc: ussjoin@… (added)
  * version:  0.7.0 => 1.6.0


Comment:

 So after some discussions today on my long-term use-case, it would seem
 that the same functionality set could solve this, #398, and #467. Let me
 explain:

 I control a small number of nodes-- let's say four. I want to be able to
 tell my uploads that they should always leave four shares on the four
 nodes *I* own, and send the remaining six to the grid. That way, if I'm
 offline with *only* my four nodes for company, I can still use my files;
 similarly, when I go offline, people with access can *also* use my files.

 In this case, I might also want to be able to configure the use of helpers
 etc. on a per-subnet basis; that is, "use the helper unless the node
 you're pushing to is on my LAN, in which case, it's silly."

 Ideally I could also set up a modified rebalancer that says "make four
 shares and put them on my local grid subset," but that's secondary.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/213#comment:8>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid