From: Loic Dachary <loic@dachary.org>
To: "Chen, Xiaoxi" <xiaoxi.chen@intel.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Add a converter in OSDMap to split the ruleset into rule
Date: Fri, 15 Aug 2014 11:26:16 +0200 [thread overview]
Message-ID: <53EDD238.4020602@dachary.org> (raw)
In-Reply-To: <53EDD0C8.5020007@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
On 15/08/2014 11:20, Loic Dachary wrote:
> Hi,
>
> I've added a few comments inline at https://github.com/xiaoxichen/ceph/commit/354c09131a64ac1e1a67c71794d1a3bab8334ca8 . Could you explain in pseudo code, in the commit message, what upgrade strategy you are trying to implement ?
>
> For testing purposes, I would create border cases (i.e. having a rule with ruleid != ruleset) in a script similar to
>
> https://github.com/ceph/ceph/blob/firefly/src/test/mon/osd-crush.sh
>
> and then trigger the upgrade and check that it enforces the constraint.
Which is exactly what you did ;-)
>
> There is a need for a change near
>
> https://github.com/ceph/ceph/blob/master/src/crush/CrushWrapper.cc#L787
>
> so that it does not pick a ruleset different from the ruleid. Maybe that could be a first step in the right direction ? I mean, not modifying the existing maps yet, just enforcing ruleid == ruleset by changing the code. So that a new cluster does not suffer from this inconsistency.
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-08-15 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 9:20 Add a converter in OSDMap to split the ruleset into rule Loic Dachary
2014-08-15 9:26 ` Loic Dachary [this message]
2014-08-15 9:52 ` Chen, Xiaoxi
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=53EDD238.4020602@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=xiaoxi.chen@intel.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.