From: Loic Dachary <loic@dachary.org>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: rbd and the next giant release
Date: Tue, 10 Feb 2015 16:17:31 +0100 [thread overview]
Message-ID: <54DA210B.1000901@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
Hi Josh,
The rbd teuthology suite for the next giant release as found in https://github.com/ceph/ceph/commits/giant-backports came back (see http://pulpito.ceph.com/loic-2015-02-02_23:28:17-rbd-giant-backports---basic-multi) with one ceph-qa-suite error which was fixed (see http://tracker.ceph.com/issues/10501#teuthology-run-6b08a729540c61f3c8b15c5a3ce9382634bf800c-february-2015 for the details).
Do you think it is ready for QE to start their own round of testing ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-02-10 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 15:17 Loic Dachary [this message]
2015-02-10 16:40 ` rbd and the next giant release Josh Durgin
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=54DA210B.1000901@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).