All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: "Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	"Shiozawa, Kensuke" <shiozawa.kennsu@jp.fujitsu.com>,
	"Nakao, Takanori" <nakao.takanori@jp.fujitsu.com>
Subject: Re: Erasure Code Plugins : PLUGINS_V3 feature
Date: Thu, 06 Aug 2015 15:57:58 +0200	[thread overview]
Message-ID: <55C367E6.8040902@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AB68E6A@g01jpexmbyt24>

[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]

Hi Takeshi,

https://github.com/ceph/ceph/pull/5493 is ready for your review. The matching integration tests can be found at https://github.com/ceph/ceph-qa-suite/pull/523

Cheers

On 06/08/2015 02:28, Miyamae, Takeshi wrote:
> Dear Sage,
> 
>> note that what this really means is that the on-disk encoding needs to remain fixed.
> 
> Thank you for letting us know the important notice.
> We have no plan to change shec's format at this moment, but we will remember the
> comment for any future events.
> 
> Best Regards,
> Takeshi Miyamae
> 
> -----Original Message-----
> From: Sage Weil [mailto:sweil@redhat.com] 
> Sent: Thursday, August 6, 2015 3:45 AM
> To: Loic Dachary; Miyamae, Takeshi/宮前 剛
> Cc: Samuel Just; Ceph Development
> Subject: Re: Erasure Code Plugins : PLUGINS_V3 feature
> 
> On Wed, 5 Aug 2015, Loic Dachary wrote:
>> Hi Sam,
>>
>> How does this proposal sound ? It would be great if that was done 
>> before the feature freeze.
> 
> I think it's a good time.
> 
> Takeshi, note that what this really means is that the on-disk encoding needs to remain fixed.  If we decide to change it down the line, we'll have to make a 'shec2' or similar so that the old format is still decodable (or ensure that existing data can still be read in some other way).
> 
> Sound good?
> 
> sage
> 
> 
>>
>> Cheers
>>
>> On 29/07/2015 11:16, Loic Dachary wrote:
>>> Hi Sam,
>>>
>>> The SHEC plugin[0] has been running in the rados runs[1] in the past few months. It also has a matching corpus verification which runs on every make check[2] as well as its optimized variants. I believe the flag "experimental" can now be removed. 
>>>
>>> In order to do so, we need to use a PLUGINS_V3 feature, in the same way we did back in Giant when the ISA and LRC plugins were introduced[3]. This won't be necessary in the future, when there is a generic plugin mechanism, but right now that's what we need. It would be a commit very similar to the one implementing PLUGINS_V2[4].
>>>
>>> Is this agreeable to you ? Or would you rather see another way to resolve this ?
>>>
>>> Cheers
>>>
>>> [0] https://github.com/ceph/ceph/tree/master/src/erasure-code/shec
>>> [1] 
>>> https://github.com/ceph/ceph-qa-suite/tree/master/suites/rados/thras
>>> h-erasure-code-shec [2] 
>>> https://github.com/ceph/ceph-erasure-code-corpus/blob/master/v0.92-9
>>> 88/non-regression.sh#L52 [3] http://tracker.ceph.com/issues/9343
>>> [4] 
>>> https://github.com/ceph/ceph/commit/9687150ceac9cc7e506bc227f430d420
>>> 7a6d7489
>>>
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>
>>

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-08-06 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  9:16 Erasure Code Plugins : PLUGINS_V3 feature Loic Dachary
2015-08-05  8:21 ` Loic Dachary
2015-08-05 18:44   ` Sage Weil
2015-08-06  0:28     ` Miyamae, Takeshi
2015-08-06 13:57       ` Loic Dachary [this message]
2015-08-07  5:12         ` 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=55C367E6.8040902@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.