[tahoe-dev] [tahoe-lafs] #913: Support running a storage node per drive easily

[tahoe-lafs]

#913: Support running a storage node per drive easily
-------------------------+--------------------------------------------------
 Reporter:  davidsarah   |           Owner:  nobody   
     Type:  enhancement  |          Status:  new      
 Priority:  major        |       Milestone:  undecided
Component:  unknown      |         Version:  1.5.0    
 Keywords:  usability    |   Launchpad_bug:           
-------------------------+--------------------------------------------------

Comment(by zooko):

 Replying to [comment:8 qwasty]:
 > Zooko: Don't forget to automate all that, or it will be inaccessible to
 people like me who are not sysadmins.

 Well, much as I personally want to encourage this sort of use case, I have
 limited time and I don't think I will have time to implement these layers
 of automation in the forseeable future.  I think the thing that is most
 needed at this stage is experience reports from people who actually
 deployed Tahoe-LAFS grids and observed the things that worked well and the
 things that didn't.

 Now actually when wearing one of my other hats I am doing exactly that --
 maintaining the allmydata.com production grid and posting bug reports or
 asking allmydata.com users to post bug reports to this trac.

 However, my individual use case will not cover all of the layers of
 documentation and automation that would be necessary to achieve wide
 acceptance.

 Therefore, if you see what I am getting at, it is up to you!  You must
 deploy a Tahoe-LAFS grid!  And you must open trac tickets explaining what
 didn't work, and posting to the tahoe-dev list summarizing what was good
 and bad about the experience.

 One nice thing about layers of automation is that they can be written
 completely outside of the Tahoe-LAFS core, using the WAPI, cmdline, or
 perhaps the (new, unstable) FUSE interface.  That means it is easier for
 them to be written by people who don't have the expertise to make changes
 to the Tahoe-LAFS core.  See [wiki:RelatedProjects the RelatedProjects
 page] (http://allmydata.org/trac/tahoe/wiki/RelatedProjects ) for examples
 of this sort of auxiliary tool such as Kevin Reid's cron script, Andrej
 Falout's obackup, and François Deppierraz's puppet-tahoe.  These are all
 tools that can be used to automate and control your Tahoe-LAFS nodes.

 Maybe people who are interested in this sort of use case should explore
 those tools and consider contributing to those tools to extend them to
 cover your use case.


 > Also, would it be better to fill all nodes to the same percentage of
 capacity?

 David-Sarah recently had a similar idea and opened #872 (Adjust the
 probability of selecting a node according to its storage capacity (or
 other fitness measure)).  It could be interesting!  Again, we may need
 more help in terms of bug reports, testing, documentation, code review,
 and writing patches if we're going to accomplish that goal along with many
 other useful and widely-demanded features.

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