From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sjust@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shu, Xinxin" <xinxin.shu@intel.com>
Subject: Re: rados and the next firefly release v0.80.10
Date: Thu, 28 May 2015 18:09:49 +0200 [thread overview]
Message-ID: <55673DCD.7030903@dachary.org> (raw)
In-Reply-To: <555F89CA.8080005@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
For the record:
[28.05 18:09] <sjusthm> loicd: you have my ack
On 22/05/2015 21:55, Loic Dachary wrote:
> Hi Sam,
>
> The next firefly release as found at https://github.com/ceph/ceph/tree/firefly (68211f695941ee128eb9a7fd0d80b615c0ded6cf) passed the rados suite (http://tracker.ceph.com/issues/11090#rados). It includes https://github.com/ceph/ceph/pull/4556 which is the pull request backporting the fix for "OSD::load_pgs: we need to handle the case where an upgrade from earlier versions which ignored non-existent pgs resurrects a pg with a prehistoric osdmap" http://tracker.ceph.com/issues/11429 to firefly (the corresponding ceph-qa-suite pull request https://github.com/ceph/ceph-qa-suite/pull/435 has also been tested and merged).
>
> Do you think it is ready for QE to start their own round of testing ?
>
> Cheers
>
> P.S. http://tracker.ceph.com/issues/11090#Release-information has direct links to the pull requests merged into firefly since v0.80.9 in case you need more context about one of them.
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-05-28 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 19:55 rados and the next firefly release v0.80.10 Loic Dachary
2015-05-28 16:09 ` Loic Dachary [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=55673DCD.7030903@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@redhat.com \
--cc=xinxin.shu@intel.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