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

[Vijay Bellur]

On 07/21/2012 01:59 PM, Bharata B Rao wrote:
> We now
> specify the gluster backed image like this:
>
> -drive file=gluster:address@hidden:volname:image
>
> - Here 'gluster' is the protocol.
> - 'address@hidden' 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.
>
> Note that we are no longer using volfiles directly and use volume names
> instead. For this to work, gluster management daemon (glusterd) needs to
> be running on the QEMU node.


glusterd needs to be running on the server that is specified in 
'address@hidden' option.



> Scenarios
> ---------
> Base: QEMU boots from directly from image on gluster brick.
> Fuse mount: QEMU boots from VM image on gluster FUSE mount.
> Fuse bypass: QEMU uses gluster protocol and uses standard client volfile.
> Fuse bypass custom: QEMU uses gluster protocol and uses a minimal client
>         volfile that just has client xlator.
> RPC bypass: QEMU uses just posix xlator and doesn't depend on gluster server.

For the Fuse mount, Fuse bypass and Fuse bypass custom scenarios, I 
assume a single local gluster brick is being used. Is this correct?

Thanks,
Vijay