From: Yuri Weinstein <yweinste@redhat.com>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: client/cluster compatibility testing
Date: Thu, 16 Apr 2015 16:59:47 -0400 (EDT) [thread overview]
Message-ID: <1543401580.1470287.1429217987676.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1504160935130.18547@cobra.newdream.net>
Yea, Sage, that sounds reasonable.
I added a ticket to capture this plan (http://tracker.ceph.com/issues/11413) and will add those tests soon.
Please add your comments to the ticket above.
I am assuming that it will look something like this for dumpling, firefly and hammer:
dumpling(stable) -> client-x
firefly(stable) -> client-x
hammer(stable) -> client-x
and reverse
dumpling-client(stable) -> cluster-x
firefly-cluster(stable) -> cluster-x
hammer-cluster(stable) -> cluster-x
Yes?
Thx
YuriW
----- Original Message -----
From: "Sage Weil" <sweil@redhat.com>
To: ceph-devel@vger.kernel.org
Sent: Thursday, April 16, 2015 9:42:29 AM
Subject: client/cluster compatibility testing
Now that there are several different vendors shipping and supporting Ceph
in their products, we'll invariably have people running different
versions of Ceph that are interested in interoperability. If we focus
just on client <-> cluster compatability, I think the issues are (1)
compatibility between upstream ceph versions (firefly vs hammer) and
(2) ensuring that any downstream changes the vendor makes don't break that
compatibility.
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").
We'll obviously run these tests on upstream releases to ensure that we are
not breaking compatibility (or are doing so in known, explicit ways).
Downstream folks can run the same test suites against any changes they
make as well to ensure that their product is "compatible with firefly
clients," or whatever.
Does that sound reasonable?
sage
--
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
prev parent reply other threads:[~2015-04-16 20:59 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
2015-04-16 20:59 ` Yuri Weinstein [this message]
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=1543401580.1470287.1429217987676.JavaMail.zimbra@redhat.com \
--to=yweinste@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--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.