From: Loic Dachary <loic@dachary.org>
To: "Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Cc: "Shiozawa, Kensuke" <shiozawa.kennsu@jp.fujitsu.com>,
"Nakao, Takanori" <nakao.takanori@jp.fujitsu.com>
Subject: Re: conditions for removing experimental feature marks
Date: Mon, 16 Feb 2015 10:16:47 +0100 [thread overview]
Message-ID: <54E1B57F.3070201@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AA6CEB8@g01jpexmbyt24>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
Hi,
On 16/02/2015 08:37, Miyamae, Takeshi wrote:
> Dear Loic,
>
> Thank you for your help on the pull request of SHEC last week.
> We believe that marking experimental feature on SHEC was inevitable and
> the way to restrict the feature is proper.
>
> By the way, could you let us know what are the conditions for removing
> experimental feature marks in the future?
> Are additional thorough tests required?
The next step is to run integration tests with the shec plugin. The integration tests have shown that the shec plugin does not disrupt anything. Now we should check if it works properly under stress and upgrades. I created two tickets for that purpose:
http://tracker.ceph.com/issues/10886 : integration / theuthology integration / theuthology thrasher tests for the shec erasure code plugin
http://tracker.ceph.com/issues/10887 : erasure-code: allow upgrades for shec plugins
It would be fantastic if you could work on http://tracker.ceph.com/issues/7291 : it would make the integration of new erasure code plugins easier. I realize that it is infrastructure work not directly of interest to the shec plugin implementation.
Running teuthology locally is non trivial, maybe we can provide you with access to the community lab so that you can run teuthology suites against the existing teuthology cluster (i.e. http://pulpito.ceph.com/). Would you like me to ask ?
Cheers
> Best regards,
> Takeshi Miyamae
>
--
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-16 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 7:37 conditions for removing experimental feature marks Miyamae, Takeshi
2015-02-16 9:16 ` Loic Dachary [this message]
2015-03-10 10:35 ` Miyamae, Takeshi
2015-03-10 14:25 ` Loic Dachary
2015-03-19 2:20 ` Miyamae, Takeshi
2015-03-19 7:15 ` Loic Dachary
2015-03-19 7:25 ` Loic Dachary
2015-03-19 8:50 ` Miyamae, Takeshi
2015-03-19 10:07 ` Loic Dachary
2015-03-20 0:07 ` Miyamae, Takeshi
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=54E1B57F.3070201@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=miyamae.takeshi@jp.fujitsu.com \
--cc=nakao.takanori@jp.fujitsu.com \
--cc=shiozawa.kennsu@jp.fujitsu.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.