CEPH filesystem development
 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>,
	"Paul Von-Stamwitz (PVonStamwitz@us.fujitsu.com)"
	<PVonStamwitz@us.fujitsu.com>
Subject: Re: Deadline of Github pull request for Hammer release (question)
Date: Tue, 13 Jan 2015 11:26:08 +0100	[thread overview]
Message-ID: <54B4F2C0.2040805@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AA40849@g01jpexmbyt24>

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

Hi,

On 13/01/2015 11:24, Miyamae, Takeshi wrote:
> Hi Loic,
> 
>> Although we're late in the Hammer roadmap, it's a good time for an early preview. It will help show what needs to be changed to accomodate the SHEC plugin.
> 
> Thank you for your advices.
> We have uploaded our latest codes to the following folk repository for an early review.
> 
> https://github.com/miyamae-takeshi/multiple-shec

It's 404 ? Is it a private repository maybe ?

> 
> SHEC is located in src/erasure-code/shec directory.
> 
> We are verifying SHEC's advantages on our Ceph cluster. It takes a little bit more.
> Would you please start the review before that?
> 
> Best regards,
> Takeshi Miyamae
> 
> -----Original Message-----
> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Loic Dachary
> Sent: Wednesday, January 7, 2015 12:52 AM
> To: Miyamae, Takeshi/宮前 剛
> Cc: Ceph Development; Shiozawa, Kensuke/塩沢 賢輔; Nakao, Takanori/中尾 鷹詔
> Subject: Re: Deadline of Github pull request for Hammer release (question)
> 
> Hi,
> 
> 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)
> 
> The work you have done is quite impressive :-)
> 
>> 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.
> 
> Great.
> 
>> 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.)
> 
> Although we're late in the Hammer roadmap, it's a good time for an early preview. It will help show what needs to be changed to accomodate the SHEC plugin.
> 
> Cheers
> 
>> 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@vger.kernel.org More majordomo 
>> info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> --
> 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-01-13 10:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 11:49 Deadline of Github pull request for Hammer release (question) Miyamae, Takeshi
2015-01-06 15:51 ` Loic Dachary
2015-01-13 10:24   ` Miyamae, Takeshi
2015-01-13 10:26     ` Loic Dachary [this message]
2015-01-13 10:34       ` Miyamae, Takeshi
2015-01-13 12:45         ` Loic Dachary
2015-01-13 17:05           ` Miyamae, Takeshi
2015-01-13 18:03             ` Loic Dachary
2015-01-20  0:48               ` Miyamae, Takeshi
2015-01-20  7:22                 ` Loic Dachary
2015-01-20  9:07                   ` Miyamae, Takeshi
2015-01-21 14:12                     ` Loic Dachary
2015-01-22  8:42                       ` Miyamae, Takeshi
2015-01-22  9:28                         ` Loic Dachary
2015-01-22 16:34                           ` Miyamae, Takeshi
2015-01-22 17:29                             ` Loic Dachary
2015-01-23  1:16                               ` Miyamae, Takeshi
2015-01-23  9:08                                 ` Loic Dachary
2015-01-23 12:47                                   ` Miyamae, Takeshi
2015-01-23 13:38                                     ` Loic Dachary
2015-01-24 15:52                                       ` Miyamae, Takeshi
2015-01-21 14:31                     ` Loic Dachary
2015-01-23 13:46 ` Loic Dachary
2015-01-26  5:43   ` Miyamae, Takeshi
2015-01-26 11:02     ` Loic Dachary
2015-01-26  8:00   ` 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=54B4F2C0.2040805@dachary.org \
    --to=loic@dachary.org \
    --cc=PVonStamwitz@us.fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox