Gregory Farnum <greg@xxxxxxxxxxx> writes: > On Wed, May 27, 2015 at 1:39 AM, Marcel Lauhoff <ml@xxxxxxxx> wrote: >> Hi, >> >> I wrote a prototype for an OSD-based object stub feature. An object stub >> being an object with it's data moved /elsewhere/. I hope to get some >> feedback, especially whether I'm on the right path here and if it >> is a feature you are interested in. >> >> >> >> Code is in my "osd-stubs" branch: >> https://github.com/ceph/ceph/compare/master...irq0:osd-stubs >> https://github.com/irq0/ceph/tree/osd-stubs >> >> Tools to toy around with osd-stubs + web server to send stubs to: >> https://github.com/irq0/ceph_osd-stub_tools >> >> >> >> Related: >> - https://wiki.ceph.com/Planning/Blueprints/%3CSIDEBOARD%3E/osd:_tiering:_object_redirects > > Do you have a shorter summary than the code of how these stub and > unstub operations relate to the object redirects? We didn't make a > great deal of use of them but the basic data structures are mostly > present in the codebase, are interpreted in at least some of the right > places, and were definitely intended to cover this kind of use case. > :) > -Greg As far as I understood the redirect feature it is about pointing to other objects inside the Ceph cluster. The stubs feature allows pointing to anything. An HTTP server in concept code. Then stubs use an IMHO simpler approach to getting objects back: It's the task of the OSD. Stubbed objects just take longer to access, due to unstubbing it first. Redirects on the other hand leave this to the client: Object redirected -> Tell client to retrieve it elsewhere. ~marcel -- Marcel Lauhoff Mail/XMPP: ml@xxxxxxxx http://irq0.org -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
