From: Loic Dachary <loic@dachary.org>
To: Yuri Weinstein <yweinste@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: dumpling & giant backports update
Date: Tue, 10 Feb 2015 17:25:00 +0100 [thread overview]
Message-ID: <54DA30DC.5040109@dachary.org> (raw)
In-Reply-To: <190003157.14855539.1423585180297.JavaMail.zimbra@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
On 10/02/2015 17:19, Yuri Weinstein wrote:
> Hi Loic
>
> I was thinking that as soon as one of the branches is declared "ready" we will merge *-backports with the main branch and execute appropriate set of suites as we run them in the Octo lab for released branches.
>
Ok.
> For dumpling:
> rados
> rbd
> rgw
> fs
> ceph-deploy
> upgrade/dumpling
>
> For giant:
> rados
> rbd
> rgw
> fs
> krbd
> kcephfs
> knfs
> haddop
> samba
> rest
> multimds
> multi-version
> upgrade/giant
> powecycle
>
> Not sure if we need to run more tests, e.g. giant-x kind of suites for upgrades.
>
> Do you agree with this plan?
Yes !
Cheers
>
> Thx
> YuriW
>
> ----- Original Message -----
> From: "Loic Dachary" <loic@dachary.org>
> To: "Yuri Weinstein" <yuri.weinstein@inktank.com>
> Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
> Sent: Tuesday, February 10, 2015 7:25:55 AM
> Subject: dumpling & giant backports update
>
> Hi Yuri,
>
> The dumpling integration branch https://github.com/ceph/ceph/commits/dumpling-backports is ready for Josh and Sam and we are expecting approval from Yehuda (the details are here http://tracker.ceph.com/issues/10560).
>
> The giant integration branch https://github.com/ceph/ceph/commits/giant-backports is ready for Sam and we are expecting approval from Josh and Yehuda (the details are here http://tracker.ceph.com/issues/10501).
>
> It is likely that we get approval for one branch or the other in the next 48h. When we do, I assume you will be conducting your own round of testing, using the dumpling-backports and/or giant-backports branch. Do you have a list of suites you plan to run already ? I'm also curious to understand who will be analyzing the results and ultimately declare that it is ready to be released.
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-02-10 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 15:25 dumpling & giant backports update Loic Dachary
2015-02-10 16:19 ` Yuri Weinstein
2015-02-10 16:25 ` Loic Dachary [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-02 23:09 Loic Dachary
2015-02-02 23:13 ` 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=54DA30DC.5040109@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--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 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.