[tahoe-dev] [tahoe-lafs] #467: change peer-selection to allow introducerless explicit serverlist, alternative backends

[tahoe-lafs]

#467: change peer-selection to allow introducerless explicit serverlist,
alternative backends
---------------------------------------------+------------------------------
 Reporter:  warner                           |           Owner:            
     Type:  enhancement                      |          Status:  new       
 Priority:  major                            |       Milestone:  eventually
Component:  code-peerselection               |         Version:  1.1.0     
 Keywords:  availability preservation cache  |   Launchpad_bug:            
---------------------------------------------+------------------------------
Changes (by davidsarah):

  * milestone:  undecided => eventually


Comment:

 Justin Stottlemyer wrote on tahoe-dev:
 > I could see in my case a (similar style) need. I have a concern that
 while running a private grid with dense storage systems containing 36-45
 nodes. that I could end up with enough shares on a single system that if
 that system were down I could have a failure to retrieve data until that
 box was back up and running.  A slightly different use case, but it may be
 able to use a similar structure.

 This is a similar use case to geographic dispersal, and could probably use
 the same mechanism as that.

 For example, the static configuration could specify a tree of nodes, and
 the share placement algorithm would try to distribute shares as evenly as
 possible between siblings at each level of the tree. In the simplest case,
 you would have a single-level tree and the shares would just be
 distributed between nodes as they are now. In a complicated case the
 levels of the tree could specify: continent / site / room / rack / machine
 / disk.

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