From: Dan Mick <dan.mick@inktank.com>
To: ruslan usifov <ruslan.usifov@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: does still not recommended place rbd device on nodes, where osd daemon located?
Date: Wed, 21 Nov 2012 12:29:14 -0800 [thread overview]
Message-ID: <50AD399A.2010203@inktank.com> (raw)
In-Reply-To: <CAHULbCmMvBWq7xpZ1faTieROUpHSBBnNKcr6x3VC5sDkLodjrQ@mail.gmail.com>
Still not certain I'm understanding *just* what you mean, but I'll point
out that you can set up a cluster with rbd images, mount them from a
separate non-virtualized host with kernel rbd, and expand those images
and take advantage of the newly-available space on the separate host,
just as though you were expanding a RAID device. Maybe that fits your
use case, Ruslan?
On 11/21/2012 12:05 PM, ruslan usifov wrote:
> Yes i mean exactly this. it's a great pity :-( Maybe present some ceph
> equivalent that solve my problem?
>
> 2012/11/21 Gregory Farnum <greg@inktank.com>:
>> On Wed, Nov 21, 2012 at 4:33 AM, ruslan usifov <ruslan.usifov@gmail.com> wrote:
>>> So, not possible use ceph as scalable block device without visualization?
>>
>> I'm not sure I understand, but if you're trying to take a bunch of
>> compute nodes and glue their disks together, no, that's not a
>> supported use case at this time. There are a number of deadlock issues
>> caused by this sort of loopback; it's the same reason you shouldn't
>> mount NFS on the server host.
>> We may in the future manage to release an rbd-fuse client that you can
>> use to do this with a little less pain, but it's not ready at this
>> point.
>> -Greg
> --
> 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
>
next prev parent reply other threads:[~2012-11-21 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 15:01 does still not recommended place rbd device on nodes, where osd daemon located? ruslan usifov
2012-11-20 16:50 ` Sage Weil
2012-11-21 12:33 ` ruslan usifov
2012-11-21 19:15 ` Gregory Farnum
2012-11-21 20:05 ` ruslan usifov
2012-11-21 20:29 ` Dan Mick [this message]
[not found] ` <CAHULbC=crXP5=L3hXvmY9zFgF1KnR06-1opwbVvyiFHLykh5tg@mail.gmail.com>
2012-11-22 16:32 ` Fwd: " ruslan usifov
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=50AD399A.2010203@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ruslan.usifov@gmail.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.