On Thu, 18 Apr 2013, Noah Watkins wrote: > On Apr 18, 2013, at 2:08 PM, Josh Durgin <josh.dur...@inktank.com> wrote: > > > I talked to some folks interested in doing a more limited form of this > > yesterday. They started a blueprint [1]. One of their ideas was to have > > erasure coding done by a separate process (or thread perhaps). It would > > use erasure coding on an object and then use librados to store the > > rasure-encoded pieces in a separate pool, and finally leave a marker in > > place of the original object in the first pool. > > This sounds at a high-level similar to work out of Microsoft: > > https://www.usenix.org/system/files/conference/atc12/atc12-final181_0.pdf > > The basic idea is to replicate first, then erasure code in the background.
FWIW, I think a useful (and generic) concept to add to rados would be a redirect symlink sort of thing that says "oh, this object is over there is that other pool", such that client requests will be transparently redirected or proxied. This will enable generic tiering type operations, and probably simplify/enable migration without a lot of additional complexity on the client side. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
