From: Marcel Lauhoff <ml@irq0.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD-Based Object Stubs
Date: Thu, 28 May 2015 12:01:54 +0200 [thread overview]
Message-ID: <87617dc965.fsf@irq0.org> (raw)
In-Reply-To: <CAC6JEv8KPsi1w37-XvNg00s4gC6hv=N5p5NWty56dFv3=e3eQA@mail.gmail.com>
Gregory Farnum <greg@gregs42.com> writes:
> On Wed, May 27, 2015 at 1:39 AM, Marcel Lauhoff <ml@irq0.org> 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@irq0.org
http://irq0.org
next prev parent reply other threads:[~2015-05-28 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 8:39 OSD-Based Object Stubs Marcel Lauhoff
2015-05-27 9:24 ` Haomai Wang
2015-05-27 16:37 ` Robert LeBlanc
2015-05-28 9:45 ` Marcel Lauhoff
2015-05-28 5:56 ` Gregory Farnum
2015-05-28 10:01 ` Marcel Lauhoff [this message]
2015-06-09 23:58 ` Gregory Farnum
2015-06-20 10:18 ` Marcel Lauhoff
2015-06-23 12:38 ` Gregory Farnum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87617dc965.fsf@irq0.org \
--to=ml@irq0.org \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.