All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Farnum <greg@gregs42.com>
To: Shishir Gowda <Shishir.Gowda@sandisk.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Ceph tier’ing enhancements blue print for jewel
Date: Tue, 9 Jun 2015 23:46:39 -0700	[thread overview]
Message-ID: <CAC6JEv9OPeAETB4M6fdouXLwQ_ocgsPswDXw2Vdntbd7n=uKHg@mail.gmail.com> (raw)
In-Reply-To: <EA545303A8F8E842820A172C3D641D6E1B0628FD@SACMBXIP01.sdcorp.global.sandisk.com>

On Tue, Jun 9, 2015 at 7:52 PM, Shishir Gowda <Shishir.Gowda@sandisk.com> wrote:
> Hi All,
>
> We have uploaded the blueprint for the enhancements we are proposing for ceph tier’ing functionality for Jewel release @
>
> http://tracker.ceph.com/projects/ceph/wiki/Tiering-enhacement
>
> Soliciting comments/feedback for the same.

By and large this looks pretty sensible to me in a quick read. The
things I noticed:
1) There's a reference to the policy function getting passed in data
about how full the pool is. Note that while we expose stuff to cache
pool users in terms of pools, in the internal implementations the
flushing functions are based on how full the local PG is — that's
because we don't have any up-to-date information about the global pool
(and we really can't). I imagine just substituting PG for pool in your
description should work, but if not that's something to address.

2) Are you sure you want to expose these policies via RGW? That sounds
both excessively complicated (from the UI perspective) and liable to
abuse by users. Plus it seems a little redundant — I could imagine
people wanting the very fastest storage, but then they should just
store those objects in RGW buckets which are stored on pools with
appropriate policies (I forget what this mechanism is called, but
there's some sort of placement thing when creating buckets). Otherwise
the enhancements for things like direct-read-from-EC-shards etc seem
to cover RGW's performance needs pretty well.

3) While a bunch of the docs and possibly some of the code imply that
you have a single cache and a single base tier, I think in general you
can set up tier chains. We want to preserve that, so the $CACHE and
$BASE language used in the tier functions needs to be capable of that.
-Greg
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-06-10  6:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  2:52 Ceph tier’ing enhancements blue print for jewel Shishir Gowda
2015-06-10  6:46 ` Gregory Farnum [this message]
2015-06-11  8:14   ` Shishir Gowda
2015-06-17  0:56     ` Allen Samuels
2015-06-11  1:42 ` Li Wang

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='CAC6JEv9OPeAETB4M6fdouXLwQ_ocgsPswDXw2Vdntbd7n=uKHg@mail.gmail.com' \
    --to=greg@gregs42.com \
    --cc=Shishir.Gowda@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    /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.