qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@gmail.com>
To: Yehuda Sadeh Weinraub <yehudasa@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	ceph-devel@vger.kernel.org,
	Josh Durgin <josh.durgin@dreamhost.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH v2 2/2] rbd: allow configuration of rados from the rbd filename
Date: Fri, 8 Apr 2011 10:07:10 +0900	[thread overview]
Message-ID: <BANLkTimqJdCRnevPHCG79ZJ=FMi9Fi9XHQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTingpiVSTt6DpSwP-6hydGWDx8E=ag@mail.gmail.com>

2011/4/8 Yehuda Sadeh Weinraub <yehudasa@gmail.com>:
> On Thu, Apr 7, 2011 at 2:54 AM, Yoshiaki Tamura
> <tamura.yoshiaki@gmail.com> wrote:
>> 2011/4/7 Stefan Hajnoczi <stefanha@gmail.com>:
>>> On Thu, Apr 07, 2011 at 10:14:03AM +0900, Yoshiaki Tamura wrote:
>>>> 2011/3/29 Josh Durgin <josh.durgin@dreamhost.com>:
>>>> > The new format is rbd:pool/image[@snapshot][:option1=value1[:option2=value2...]]
>>>> > Each option is used to configure rados, and may be any Ceph option, or "conf".
>>>> > The "conf" option specifies a Ceph configuration file to read.
>>>> >
>>>> > This allows rbd volumes from more than one Ceph cluster to be used by
>>>> > specifying different monitor addresses, as well as having different
>>>> > logging levels or locations for different volumes.
>>>> >
>>>> > Signed-off-by: Josh Durgin <josh.durgin@dreamhost.com>
>>>> > ---
>>>> >  block/rbd.c |  119 ++++++++++++++++++++++++++++++++++++++++++++++++++--------
>>>> >  1 files changed, 102 insertions(+), 17 deletions(-)
>>>> >
>>>> > diff --git a/block/rbd.c b/block/rbd.c
>>>> > index cb76dd3..bc3323d 100644
>>>> > --- a/block/rbd.c
>>>> > +++ b/block/rbd.c
>>>> > @@ -22,13 +22,17 @@
>>>> >  /*
>>>> >  * When specifying the image filename use:
>>>> >  *
>>>> > - * rbd:poolname/devicename
>>>> > + * rbd:poolname/devicename[@snapshotname][:option1=value1[:option2=value2...]]
>>>>
>>>> I'm not sure IIUC, but currently this @snapshotname seems to be
>>>> meaningless; it doesn't allow you to boot from a snapshot because it's
>>>> read only.  Am I misunderstanding or tested incorrectly?
>>>
>>> Read-only block devices are supported by QEMU and can be useful.
>>
>> I agree.  My expectation was that @snapshotname is introduced to have
>> writable snapshot.
>>
> The RADOS backend doesn't support writable snapshots. However, down
> the rbd roadmap we plan to have layering which in a sense is writable
> snapshots. The whole shift to librbd was done so that introducing such
> new functionality will be transparent and will not require much or any
> changes in the qemu code.

Thanks.  It made things clear :)  I think it's a good move.

Yoshi

>
> Yehuda
>

  reply	other threads:[~2011-04-08  1:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 23:15 [Qemu-devel] [PATCH v2 1/2] rbd: use the higher level librbd instead of just librados Josh Durgin
2011-03-28 23:15 ` [Qemu-devel] [PATCH v2 2/2] rbd: allow configuration of rados from the rbd filename Josh Durgin
2011-04-07  1:14   ` [Qemu-devel] " Yoshiaki Tamura
2011-04-07  8:47     ` Stefan Hajnoczi
2011-04-07  9:54       ` Yoshiaki Tamura
2011-04-07 16:16         ` Yehuda Sadeh Weinraub
2011-04-08  1:07           ` Yoshiaki Tamura [this message]
2011-04-08  8:43 ` [Qemu-devel] Re: [PATCH v2 1/2] rbd: use the higher level librbd instead of just librados Stefan Hajnoczi
2011-04-08 16:14   ` Stefan Hajnoczi
2011-04-08 18:36   ` Josh Durgin
2011-04-12  0:18   ` [Qemu-devel] " Josh Durgin
2011-04-12  8:54     ` Stefan Hajnoczi
2011-04-12 15:38       ` Sage Weil
2011-04-12 21:14         ` Stefan Hajnoczi
2011-04-12 18:28       ` Josh Durgin

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='BANLkTimqJdCRnevPHCG79ZJ=FMi9Fi9XHQ@mail.gmail.com' \
    --to=tamura.yoshiaki@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@dreamhost.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=yehudasa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).