On Fri, Aug 24, 2012 at 8:49 AM, Stephen Perkins <[email protected]> wrote: > I'd like to get feedback from folks as to where the best place would be to > insert a "shim" into the RADOS object storage. ... > I would assume that it is "possible" to configure RADOS to store only 1 copy > of a file (bear with me here).
RADOS stores objects, not files. The Ceph File System stores file metadata in mds journals and directory objects, and file data striped over several objects. > I'd like to see where it may be possible to insert a "shim" in the storage > such that I can take the file to be stored and apply some erasure coding to > it. Therefore, the file now becomes multiple files that are handed off to > RADOS. > > The shim would also have to take read file requests and read some small > portion of the fragments and recombine. Sounds like you want a client library on top of RADOS. Getting that even remotely performant is going to be a huge engineering challenge. Zooko will tell you that Tahoe-LAFS ain't a filesystem, largely for that reason (and if you do run into him, say hi from Tv!). Good luck! -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
