[tahoe-dev] [tahoe-lafs] #68: implement distributed introduction, remove Introducer as a single point of failure

[tahoe-lafs]

#68: implement distributed introduction, remove Introducer as a single point of
failure
------------------------------+---------------------------------------------
     Reporter:  lvo           |       Owner:  writefaruq                                                   
         Type:  enhancement   |      Status:  new                                                          
     Priority:  major         |   Milestone:  1.9.0                                                        
    Component:  code-network  |     Version:  0.2.0                                                        
   Resolution:                |    Keywords:  scalability availability introduction gsoc docs review-needed
Launchpad Bug:                |  
------------------------------+---------------------------------------------

Comment (by zooko):

 Hm. Myckel: Could you please reproduce this and then about 10 seconds
 after you shutdown one storage server, click the "Report an Incident"
 button on the welcome page. Then again when you attempt to mkdir, please
 click the "Report an Incident" button a few seconds after you've done so.

 Each time you click "Report an Incident" it creates a file in the
 {{{logs/incidents}}}. Please attach those files to this ticket.

 Faruq: we should write a unit test of this workflow—create two
 introducers, create a storage server point at both introducers, create a
 storage client pointing at both introducers, shutdown one of the servers,
 then, um, then initiate an operation in the storage client, such as mkdir
 (which is what Myckel did manually) or any other operation that uses
 storage servers.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/68#comment:75>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage