Hi, Note that you also need to update https://github.com/dachary/ceph-erasure-code-corpus/blob/master/v0.85-764-gf3a1532/non-regression.sh to include non regression tests for the most common cases of the SHEC plugin encoding / decoding. This is run by make check (this repository is a submodule of Ceph). It helps make sure that content encoded / decoded with a given version of the plugin can be encoded / decoded exactly in the same way by all future versions. Cheers On 06/01/2015 12:49, Miyamae, Takeshi wrote: > Dear Loic, > > I'm Takeshi Miyamae, one of the authors of SHEC's blueprint. > > Shingled Erasure Code (SHEC) > https://wiki.ceph.com/Planning/Blueprints/Hammer/Shingled_Erasure_Code_(SHEC) > > We have revised our blueprint shown in the last CDS to extend our erasure code > layouts and describe the guideline for choosing SHEC among various EC plugins. > We believe the blueprint now answers all the comments given at the CDS. > > In addition, we would like to ask for your advice on the schedule of our github > pull request. More specifically, we would like to know its deadline for Hammer > release. > (As we have not really completed our verification of SHEC, we are wondering if > we should make it open for early preview.) > > Thank you in advance, > Takeshi Miyamae > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Loïc Dachary, Artisan Logiciel Libre
Attachment:
signature.asc
Description: OpenPGP digital signature
