All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuri Weinstein <yweinste@redhat.com>
To: Josh Durgin <jdurgin@redhat.com>
Cc: Sage Weil <sweil@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: client/cluster compatibility testing
Date: Mon, 20 Apr 2015 17:17:54 -0400 (EDT)	[thread overview]
Message-ID: <402130240.3271153.1429564674313.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5530229F.5020509@redhat.com>

We have a PR https://github.com/ceph/ceph-qa-suite/pull/414 that addressed part of this issue, e.g. added hammer-x to the mix (it's ready to be merged).

We also have two tickets where requirements for this suite were captured:
http://tracker.ceph.com/issues/11413
http://tracker.ceph.com/issues/11414

Per Josh's comment "Also I think we'll want to start doing mixed-client-version tests, particularly for things like rbd's exclusive locking", I assigned #11414 for next steps.

Question/request to the team leads - pls either agree with a need to add specific tests for mixed clients testing (and pls add tickets as you feel necessary.) or suggest otherwise.

I am guessing:

rbd - confirmed by Josh, we need those
rados - Sam, Sage?
cephfs - Greg?
rgw - Yehuda?

I am sure I missing lots of others...

What do you think?

Thx
YuriW

----- Original Message -----
From: "Josh Durgin" <jdurgin@redhat.com>
To: "Sage Weil" <sweil@redhat.com>, ceph-devel@vger.kernel.org
Sent: Thursday, April 16, 2015 1:59:11 PM
Subject: Re: client/cluster compatibility testing

On 04/16/2015 09:42 AM, Sage Weil wrote:
> I think the simplest way to address this is to talk about compatibility in
> terms of the upstream stable releases (firefly, hammer, etc.), and test
> that compatibility with teuthology tests from ceph-qa-suite.git.  We have
> some basic inter-version client/cluster tests already in
> suites/upgrade/client-upgrade.  Currently these test new (version "x")
> clients against a given release (dumpling, firefly).  I think we just need
> to add hammer to that mix, and then add a second set of tests that do the
> reverse: test clients from a given release (dumpling, firefly, hammer)
> against an arbitrary cluster version ("x").

The suites in suites/upgrade/$version-x do this, and use a mixed
version cluster rather than a purely version x cluster. It seems like
people would want that intra-cluster version coverage for smooth
upgrades.

Just need to add hammer-x there too (Yuri's renaming the client ones to
be $version-client-x for less confusion).

Also I think we'll want to start doing mixed-client-version tests,
particularly for things like rbd's exclusive locking:

http://tracker.ceph.com/issues/11405

Josh
--
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-04-20 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 16:42 client/cluster compatibility testing Sage Weil
2015-04-16 20:59 ` Josh Durgin
2015-04-20 21:17   ` Yuri Weinstein [this message]
2015-04-16 20:59 ` Yuri Weinstein

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=402130240.3271153.1429564674313.JavaMail.zimbra@redhat.com \
    --to=yweinste@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jdurgin@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.