All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: dillaman@redhat.com, Gregory Farnum <gfarnum@redhat.com>
Cc: Brett Niver <bniver@redhat.com>, John Spray <jspray@redhat.com>,
	Sage Weil <sweil@redhat.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Testing with Bluestore and Filestore
Date: Thu, 2 Mar 2017 14:02:25 -0600	[thread overview]
Message-ID: <02cc6e71-c469-9e3b-8883-afe2bd7aecb9@redhat.com> (raw)
In-Reply-To: <CA+aFP1BrsLFXr=nu2aucFT1RzR3eufY4Ut4XKp9UkafNfXhujA@mail.gmail.com>



On 03/02/2017 12:40 PM, Jason Dillaman wrote:
> On Thu, Mar 2, 2017 at 1:36 PM, Gregory Farnum <gfarnum@redhat.com> wrote:
>> On Thu, Mar 2, 2017 at 8:36 AM, Brett Niver <bniver@redhat.com> wrote:
>>> Sage,
>>>
>>> Perhaps this has already been discussed, but Jason had a good idea,
>>> that perhaps instead of testing both BS and FS upstream independently,
>>>  and doubling our testing, we might have teuthology randomly pick
>>> which to use.
>>>
>>> That would potentially reduce TCs and also give us the testing that
>>> would help prepare for working thru the migration/transition once BS
>>> is ready.
>>
>> This is really what the subset functionality is for, although I think
>> John had started working on a feature in this area that would let the
>> subset functionality go across the rados configuration options while
>> guaranteeing full combinatorial explosion on the FS tests.
>> -Greg
>
> I was actually thinking that OSDs should be randomly assigned an
> object store by teuthology (i.e. roughly 50% FileStore vs 50%
> BlueStore in the same cluster in the same test run). Right now, the
> tests (at least for RBD) running 100% FileStore or 100% BlueStore with
> no intermixing (and no verification that PGs comprised of FileStore
> and BlueStore OSDs behave properly). That would also have the added
> benefit of eliminating half the test cases in the RBD suite even
> before you apply a subset.

Seems reasonable to me.  If the clusters are small we'll get pure 
bluestore and pure filestore every once and a while too which would be good.

Mark

>
>>>
>>> Brett
>>> --
>>> 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:[~2017-03-02 20:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 16:36 Testing with Bluestore and Filestore Brett Niver
2017-03-02 18:36 ` Gregory Farnum
2017-03-02 18:40   ` Jason Dillaman
2017-03-02 20:02     ` Mark Nelson [this message]
2017-03-02 20:20       ` Sage Weil

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=02cc6e71-c469-9e3b-8883-afe2bd7aecb9@redhat.com \
    --to=mnelson@redhat.com \
    --cc=bniver@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=gfarnum@redhat.com \
    --cc=jspray@redhat.com \
    --cc=sweil@redhat.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.