[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH 0/3] GlusterFS support in QEMU

From: Bharata B Rao
Subject: Re: [Qemu-devel] [RFC PATCH 0/3] GlusterFS support in QEMU
Date: Fri, 6 Jul 2012 11:05:53 +0530
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, Jun 11, 2012 at 07:48:07PM +0530, Bharata B Rao wrote:
> # qemu-system-x86_64 --enable-kvm --nographic -smp 4 -m 1024 -drive 
> file=gluster:c-qemu.vol:/F16,format=gluster

If you notice above, I am directly feeding the gluster volume file to QEMU.
During my discussions with GlusterFS developers, I realized that it is more
relevant to use volume name than volume file directly. Hence I am proposing
that QEMU should have the gluster specifications like this:

-drive file=gluster:volfileserver:volumename:imagename

Note that volfile server and volume name combination is the standard way
of specifying a volume in gluster world.

QEMU would pass volfileserver:volumename to libglusterfsclient which will
contact the server and fetch the right client volume file to use. This
specification change has two side effects:

1. It limits the QEMU user to pick volfiles that are generated only
   by gluster CLI. This should be fine as long as gluster CLI provides
   the capability to generate or regenerate volume files for a given volume
   with the xlator set that QEMU user is interested in. GlusterFS developers
   tell me that this can be provided with some enhancements to

   Note that custom volume files could be typically needed when GlusterFS
   server is co-located with QEMU in which case you would like to get rid
   of client-server overhead and RPC communication overhead.

2. As of now, the specification of volfileserver:volumename picks the
   default client volume file for the given volume name. Since we want to
   have the flexibility to pick the volfile of our choice, we could slightly
   extend the specification like this:


   that would instruct gluster to pick a custom volume file.

   Eg. volfileserver:myvol.rpcbypass would pick myvol.rpcbypass.vol volume
   file for the volume myvol.

   Here also, the creation of custom volume file is done by gluster CLI, so
   that gluster is in a position to pick the right volume file.

   As per my current understanding, such custom volfile extensions works with

Request QEMU developers to comment on the new specification and point out any
use cases that wouldn't be possible or would be hindered by this
volfileserver:volumename specification.

I also request the GlusterFS developers (on CC) to validate my understanding
of gluster here and let me know if the proposed enhancements to
glusterCLI/glusterd are indeed feasible.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]