All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sam.just@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Separating Peering from PG
Date: Fri, 21 Jun 2013 19:10:46 +0200	[thread overview]
Message-ID: <51C48916.7090102@dachary.org> (raw)
In-Reply-To: <CA+4uBUYTieHXeOWQXtqvRg6jX-fS1cedt74H2-v36FZhSwqo0A@mail.gmail.com>

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



On 06/21/2013 06:38 PM, Samuel Just wrote:
> I'm not sure I understand, by PG::RecoveryStats, do you mean PG::RecoveryState?

Yes I do, sorry for the confusion. Fixed the typos for clarity, hopefully.

* Move PG::RecoveryState in PGRecoveryState.{cc,h}
* Create PGInterface : an abstract base class for PG enumerating all PG methods used by PGRecoveryState
* Move Peering states / methods out of PGRecoveryState.{cc,h} and into PGPeering.{cc,h}
* Write tests for PGPeering.{cc,h}, using a fixture derived from PGInterface

Cheers

> -Sam
> 
> On Fri, Jun 21, 2013 at 6:37 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Sage,
>>
>> In order to move the PG peering code out of PG.{cc,h} (which is the next step in refactoring PGs as suggested by Sam http://pad.ceph.com/p/Erasure_encoding_as_a_storage_backend ) I think it would be sensible to:
>>
>> * Move PG::RecoveryStats in PGRecoveryStat.{cc,h}
>> * Create PGInterface : an abstract base class for PG enumerating all PG methods used by PGRecoveryStats
>> * Move Peering states / methods out of PGRecoveryStat.{cc,h} and into PGPeering.{cc,h}
>> * Write tests for PGPeering.{cc,h}, using a fixture derived from PGInterface
>>
>> Because this approach not only moves the peering out of PG.{cc,h} but also the rest of the state logic, I would like to know if this seems sensible to you. Also, introducing an abstract base class to help isolate the PG interface and facilitate writing fixtures has not been discussed yet.
>>
>> Cheers
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>> All that is necessary for the triumph of evil is that good people do nothing.
>>
> --
> 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
All that is necessary for the triumph of evil is that good people do nothing.


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

  reply	other threads:[~2013-06-21 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 13:37 Separating Peering from PG Loic Dachary
2013-06-21 16:38 ` Samuel Just
2013-06-21 17:10   ` Loic Dachary [this message]
2013-06-21 17:51     ` Loic Dachary
2013-06-24 15:03       ` Loic Dachary

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=51C48916.7090102@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sam.just@inktank.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.