From: Loic Dachary <loic@dachary.org>
To: Yuri Weinstein <yweinste@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
Abhishek Varshney <abhishek.varshney@flipkart.com>,
"Dachary, Loic" <ldachary@redhat.com>,
"Weil, Sage" <sage@redhat.com>, "Just, Samuel" <sjust@redhat.com>,
"Dillaman, Jason" <dillaman@redhat.com>,
David Zafman <dzafman@redhat.com>
Subject: Re: ceph v10.2.3 QE validation status
Date: Wed, 7 Sep 2016 08:33:56 +0200 [thread overview]
Message-ID: <57CFB4D4.1060706@dachary.org> (raw)
In-Reply-To: <CAMMFjmFBW+Zdnx8Ux9mtKvh3W187oHL3UDqNpKtkHZ15Q=porg@mail.gmail.com>
Hi Yuri,
The deph-disk suite must be run on VPS.
Cheers
On 06/09/2016 22:26, Yuri Weinstein wrote:
> Missed a line with ceph-disk issue -
>
> ceph-disk:
> http://tracker.ceph.com/issues/15350
> (Loic, Sam pls review/approve)
>
> On Tue, Sep 6, 2016 at 10:12 AM, Yuri Weinstein <yweinste@redhat.com> wrote:
>> Detailed summary of the QE Validation can be found here
>> http://tracker.ceph.com/issues/16344#note-46
>>
>> The following suites were in scope of this point release validation:
>>
>> rados (subset 35/50 297 jobs)
>> rbd
>> rgw
>> fs
>> krbd
>> kcephfs
>> knfs
>> rest
>> hadoop
>> samba
>> ceph-deploy
>> ceph-disk
>> upgrade/client-upgrade
>> upgrade/hammer-x (jewel)
>> upgrade/infernalis-x (jewel)
>> powercycle
>> (please let me know if any suites are missing from this ^ list)
>>
>> ==============================
>> Issues requiring approval/decision:
>>
>> rados:
>> http://tracker.ceph.com/issues/16516 (approved by DavidZ)
>>
>> rbd:
>> multiple issues (Jason pls rview/approve, see notes
>> http://tracker.ceph.com/issues/16344#note-46)
>>
>> krbd:
>> http://tracker.ceph.com/issues/17223
>> http://tracker.ceph.com/issues/17221
>> http://tracker.ceph.com/issues/17222
>> (Jason pls rview/approve)
>>
>> knfs
>> http://tracker.ceph.com/issues/17192
>> (Greg pls rview/approve, note: it's similar we saw in hammer point release)
>>
>> samba:
>> http://tracker.ceph.com/issues/17184
>> (Greg pls rview/approve)
>>
>> upgrade/client-upgrade:about:startpage
>> http://tracker.ceph.com/issues/16506
>> (Sage, Sam, Jason pls rview/approve)
>>
>> upgrade/infernalis-x (jewel):
>> http://tracker.ceph.com/issues/17176
>> (Sam, David pls rview/approve)
>>
>> powercycle:
>> http://tracker.ceph.com/issues/17177
>> (Sage pls rview/approve)
>>
>> Loic, given that we have high number of issues in this release, if you
>> and dev leads find that we need to add more backports we may consider
>> validating a new point RC (sha1).
>>
>> Thx
>> YuriW
>
--
Loïc Dachary, Artisan Logiciel Libre
next prev parent reply other threads:[~2016-09-07 6:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 17:12 ceph v10.2.3 QE validation status Yuri Weinstein
2016-09-06 17:27 ` Gregory Farnum
2016-09-06 17:47 ` Ilya Dryomov
2016-09-06 20:19 ` Jason Dillaman
2016-09-06 20:26 ` Yuri Weinstein
2016-09-07 6:33 ` Loic Dachary [this message]
2016-09-09 12:41 ` Xiaoxi Chen
2016-09-09 18:19 ` Yuri Weinstein
2016-09-12 20:00 ` Loic Dachary
2016-09-13 16:16 ` Yuri Weinstein
2016-09-15 18:16 ` Sage Weil
2016-09-15 19:54 ` Yuri Weinstein
2016-09-15 20:08 ` Yuri Weinstein
2016-09-19 20:12 ` Yuri Weinstein
2016-09-19 20:36 ` Alfredo Deza
2016-09-20 8:45 ` Loic Dachary
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=57CFB4D4.1060706@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=dzafman@redhat.com \
--cc=ldachary@redhat.com \
--cc=sage@redhat.com \
--cc=sjust@redhat.com \
--cc=yweinste@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox