All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Koleos Fuskus <koleosfuscus@yahoo.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: erasure code & reliability model
Date: Mon, 26 May 2014 14:14:16 +0200	[thread overview]
Message-ID: <53833018.6000301@dachary.org> (raw)
In-Reply-To: <1401102147.93930.YahooMailNeo@web165006.mail.bf1.yahoo.com>

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

Hi koleosfuskus,

I've added a link to the page in https://wiki.ceph.com/Development for future reference.

Cheers

On 26/05/2014 13:02, Koleos Fuskus wrote:
> Hello Guang,
> 
> Here is the wiki: https://wiki.ceph.com/Development/Add_erasure_coding_to_the_durability_modeling
> 
> Koleos
> 
> 
> 
> On Monday, May 26, 2014 10:05 AM, Guang Yang <yguang11@outlook.com> wrote:
> Hello Loic and Koleos,
> Do we have any wiki page documenting the progress and report of this effort? We are very interested in such as well.
> 
> Thanks,
> Guang
> 
> 
> 
> 
> On May 8, 2014, at 1:19 AM, Loic Dachary <loic@dachary.org> wrote:
> 
>>
>> Hi,
>>
>> On 07/05/2014 18:43, Koleos Fuskus wrote:> Hi Loic,
>>>
>>> What do you mean by action plan? if is the schedule, it is published on my proposal in melange site. Indeed, the details of my proposal are private, if is that what you mean, I can added on the wiki. If you want this part to be public no problem. 
>>
>> Yes, that's what I meant :-) You could collect snippets from the proposal posted on melange and present them on a subpage https://wiki.ceph.com/Development and we can use this as the "home page" of your work ? 
>>
>>> Actually I am using some of my free time on reading ceph documentation (web and papers). Do you have any specific document to recommend me? Maybe we can discuss again about the durability model on Friday/Monday.  I need some more understanding about the ceph architecture.
>>
>> I'm connected on irc.oftc.net#ceph-devel today and tomorrow if you'd like to chat during this "community bonding" phase (I don't remember how google calls this for GSoC participants ;-)
>>
>> Cheers
>>
>>>
>>> Cheers,
>>> Verónica
>>> On Wednesday, May 7, 2014 8:12 AM, Loic Dachary <loic@dachary.org> wrote:
>>> Hi Veronica,
>>>
>>> I was really happy to hear you're going to work on the erasure code reliability model. Unless I'm mistaken your action plan was not published. Would you mind adding it to the wiki so I can comment on it ? Someone else might be interested to contribute too. I've had a discussion yesterday about durability models (internally) and it is not well understood. Your insight would be precious.
>>>
>>> Cheers
>>>
>>> -- 
>>> Loïc Dachary, Artisan Logiciel Libre
>>>
>>>
>>
>> -- 
>> Loïc Dachary, Artisan Logiciel Libre
>>
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

      parent reply	other threads:[~2014-05-26 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  6:11 erasure code & reliability model Loic Dachary
     [not found] ` <1399481022.50289.YahooMailNeo@web165001.mail.bf1.yahoo.com>
2014-05-07 17:19   ` Loic Dachary
2014-05-26  8:05     ` Guang Yang
     [not found]       ` <1401102147.93930.YahooMailNeo@web165006.mail.bf1.yahoo.com>
2014-05-26 11:27         ` Guang Yang
2014-05-26 12:14         ` Loic Dachary [this message]

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=53833018.6000301@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=koleosfuscus@yahoo.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.