CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: ceph-devel@vger.kernel.org
Subject: Osd placement rule questions
Date: Thu, 05 Jul 2012 15:45:22 +1200	[thread overview]
Message-ID: <4FF50DD2.6030507@catalyst.net.nz> (raw)

Hi,

I am experimenting with ceph (rbd only for now), and have a few 
questions about what is possible via placement rules.

For example I am looking at a setup with a local datacenter 
(datacenter0) and a remote one (datacenter1). I'm using a placement rule:

rule rbd {
         ruleset 2
         type replicated
         min_size 1
         max_size 10
         step take datacenter0
         step chooseleaf firstn -1 type host
         step emit
         step take datacenter1
         step chooseleaf firstn 1 type host
         step emit
}

and I have the rdb pool set to size 3.

So I *think* I am saying I want 2 replicas in datacenter0 and one in 
datacenter1 [1].

The questions I have are:

1/ I would like to be able to have a way to say something like: Make 2 
copies at datacenter0, 1 at datacenter1 - wait for the ones at 
datacenter0 to be written but not the ones at datacenter1 (so 
asynchronous for the latter). Is this possible, or planned?

2/ Also I would like to be able to say make my number of copies 3, but 
if I lose datacenter0 (where 2 copies are), don't try to have 3 copies 
at datacenter1 (so run degraded in that case). Is that possible?

Cheers

Mark

[1] Might make more sense to have 2 copies at each, but I'm just trying 
to see how this placement business works at this point...



             reply	other threads:[~2012-07-05  3:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05  3:45 Mark Kirkwood [this message]
2012-07-05  3:57 ` Osd placement rule questions Sage Weil
2012-07-05  4:55   ` Mark Kirkwood

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=4FF50DD2.6030507@catalyst.net.nz \
    --to=mark.kirkwood@catalyst.net.nz \
    --cc=ceph-devel@vger.kernel.org \
    /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