From: "Daniel P. Berrange" <berrange@redhat.com>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: Amar Tumballi <amarts@redhat.com>,
Anand Avati <aavati@redhat.com>,
qemu-devel@nongnu.org, Vijay Bellur <vbellur@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2
Date: Mon, 23 Jul 2012 10:16:43 +0100 [thread overview]
Message-ID: <20120723091643.GA7339@redhat.com> (raw)
In-Reply-To: <20120721082917.GC1046@in.ibm.com>
On Sat, Jul 21, 2012 at 01:59:17PM +0530, Bharata B Rao wrote:
> Hi,
>
> Here is the v2 patchset for supporting GlusterFS protocol from QEMU.
>
> This set of patches enables QEMU to boot VM images from gluster volumes.
> This is achieved by adding gluster as a new block backend driver in QEMU.
> Its already possible to boot from VM images on gluster volumes, but this
> patchset provides the ability to boot VM images from gluster volumes by
> by-passing the FUSE layer in gluster. In case the image is present on the
> local system, it is possible to even bypass client and server translator and
> hence the RPC overhead.
>
> The major change in this version is to not implement libglusterfs based
> gluster backend within QEMU but instead use libgfapi. libgfapi library
> from GlusterFS project provides APIs to access gluster volumes directly.
> With the use of libgfapi, the specification of gluster backend from QEMU
> matches more closely with the GlusterFS's way of specifying volumes. We now
> specify the gluster backed image like this:
>
> -drive file=gluster:server@port:volname:image
>
> - Here 'gluster' is the protocol.
> - 'server@port' specifies the server where the volume file specification for
> the given volume resides. 'port' is the port number on which gluster
> management daemon (glusterd) is listening. This is optional and if not
> specified, QEMU will send 0 which will make libgfapi to use the default
> port.
> - 'volname' is the name of the gluster volume which contains the VM image.
> - 'image' is the path to the actual VM image in the gluster volume.
I don't think we should be using '@' as a field separator here, when ":"
can do that job just fine. In addition we already have a precendent set
with the sheepdog driver for using ':' for separating all fields:
-drive file=sheepdog:example.org:6000:imagename
If you want to allow for port number to be omitted, this can be handled
thus:
-drive file=sheepdog:example.org::imagename
which is how -chardev deals with omitted port numbers
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-07-23 9:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 8:29 [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 Bharata B Rao
2012-07-21 8:30 ` [Qemu-devel] [RFC PATCH 1/2] qemu: Add a config option for GlusterFS as block backend Bharata B Rao
2012-07-21 8:31 ` [Qemu-devel] [RFC PATCH 2/2] block: gluster " Bharata B Rao
2012-07-22 15:38 ` Stefan Hajnoczi
2012-07-23 8:32 ` Bharata B Rao
2012-07-23 9:06 ` Stefan Hajnoczi
2012-07-21 12:22 ` [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 Vijay Bellur
2012-07-21 13:04 ` Bharata B Rao
2012-07-22 14:42 ` Stefan Hajnoczi
2012-07-23 8:50 ` Bharata B Rao
2012-07-23 9:20 ` Stefan Hajnoczi
2012-07-23 9:34 ` ronnie sahlberg
2012-07-23 9:35 ` Stefan Hajnoczi
2012-07-23 14:34 ` Eric Blake
2012-07-24 3:34 ` Bharata B Rao
2012-07-24 10:24 ` Kevin Wolf
2012-07-24 11:30 ` Markus Armbruster
2012-07-23 9:36 ` Vijay Bellur
2012-07-23 9:16 ` Daniel P. Berrange [this message]
2012-07-23 9:28 ` ronnie sahlberg
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=20120723091643.GA7339@redhat.com \
--to=berrange@redhat.com \
--cc=aavati@redhat.com \
--cc=amarts@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=vbellur@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 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).