[tahoe-dev] [tahoe-lafs] #777: Facility to automatically renew leases of root caps

[tahoe-lafs]

#777: Facility to automatically renew leases of root caps
---------------------------+------------------------------------------------
 Reporter:  kpreid         |           Owner:           
     Type:  enhancement    |          Status:  new      
 Priority:  major          |       Milestone:  undecided
Component:  code-frontend  |         Version:  unknown  
 Keywords:  leases         |   Launchpad_bug:           
---------------------------+------------------------------------------------

Comment(by warner):

 How many aliases do you have? What about creating a master directory that
 contains all of them, and then doing deep-check on an alias that points to
 that?

 (*something* has to be the starting point.. I generally only have one
 alias per grid)

 I agree that the node should have a built-in renewal mechanism. I've
 wondered how to configure/manage it: it should be possible to check on the
 status/progress of the renewal process through the webapi, including
 finding out which files had problems or needed repair, but these status
 pages should not be reachable without knowing the secret alias values.

 Maybe a tahoe.cfg section that lists aliases which should be auto-checked,
 and then any WUI directory page which matches one of the alias values
 should include a link that says "a deep-repair process is working on this
 directory and its children, click here for progress". And/or a page which
 lists all the deep-repair processes currently running, with alias names
 (but not dircaps) and general information about their progress (but no
 access to pages with filecaps or dircaps), and instructions to type "tahoe
 webopen ALIASNAME:" for more details.

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