All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongsheng Yang <dongsheng.yang@easystack.cn>
To: Ilya Dryomov <idryomov@gmail.com>,
	Radoslaw Zarzynski <rzarzynski@mirantis.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	"Yan, Zheng" <zyan@redhat.com>,
	Yunchuan Wen <yunchuan.wen@kylin-cloud.com>
Subject: Re: RBD volumes for bare-metal hosts
Date: Tue, 12 Jul 2016 15:46:15 +0800	[thread overview]
Message-ID: <5784A047.20200@easystack.cn> (raw)
In-Reply-To: <CAOi1vP_JFBXVEsQxTAkbtGR1WyXdoeev=--xT6gircBff5EAYw@mail.gmail.com>



On 07/06/2016 07:41 AM, Ilya Dryomov wrote:
> On Wed, Jul 6, 2016 at 12:16 AM, Radoslaw Zarzynski
> <rzarzynski@mirantis.com> wrote:
>> Hello Guys,
>>
>> I wonder about a method for providing bare-metal hosts with an access
>> to RBD volumes.
>>
>> The most obvious solution is krbd. Unfortunately, it has a substantial
>> feature gap in comparison to librbd [1][2]. exclusive-lock seems to be
>> the basic dependency that should be satisfied to even start thinking
>> about the rest. Is someone working on this feature? What are the plans
>> in general?
> The code for exclusive-lock, object-map and fast-diff is pretty much
> ready.

Hi Ilya,
     Sounds great! But where can I read these code, I did not find it
in https://github.com/ceph/ceph-client. could you give a reference
for it. thanx a lot.

Yang
>   We had a large prerequisite that had to go in before any of
> these and it's been merged into 4.7, so it's now a matter of review and
> more comprehensive testing.  deep-flatten isn't ready, but should
> follow shortly after.
>
> Note that you can disable all of these features dynamically and that
> the image is perfectly usable with none of them enabled.  Unless you
> have clones or discard a lot, in which case object-map can help, the
> I/O path is the same.
>
> No concrete plans for mirroring support yet.
>
> Thanks,
>
>                  Ilya
> --
> 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
>


  parent reply	other threads:[~2016-07-12  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 22:16 RBD volumes for bare-metal hosts Radoslaw Zarzynski
2016-07-05 23:41 ` Ilya Dryomov
2016-07-06  0:21   ` Radoslaw Zarzynski
2016-07-07 10:43     ` Ilya Dryomov
2016-07-12  7:46   ` Dongsheng Yang [this message]
2016-07-12  8:00     ` Ilya Dryomov
2016-07-12  8:03       ` Dongsheng Yang

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=5784A047.20200@easystack.cn \
    --to=dongsheng.yang@easystack.cn \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=rzarzynski@mirantis.com \
    --cc=yunchuan.wen@kylin-cloud.com \
    --cc=zyan@redhat.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.