From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35909) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SsYiE-0007my-A2 for qemu-devel@nongnu.org; Sat, 21 Jul 2012 08:23:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SsYiD-0004AP-7z for qemu-devel@nongnu.org; Sat, 21 Jul 2012 08:23:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48638) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SsYiC-0004AL-WE for qemu-devel@nongnu.org; Sat, 21 Jul 2012 08:23:09 -0400 Message-ID: <500A9F23.4090806@redhat.com> Date: Sat, 21 Jul 2012 17:52:59 +0530 From: Vijay Bellur MIME-Version: 1.0 References: <20120721082917.GC1046@in.ibm.com> In-Reply-To: <20120721082917.GC1046@in.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: bharata@linux.vnet.ibm.com Cc: Anand Avati , Amar Tumballi , qemu-devel@nongnu.org On 07/21/2012 01:59 PM, Bharata B Rao wrote: > 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. > > 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 'server@port' 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