qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Merging the quorum block driver
Date: Thu, 19 Sep 2013 15:21:46 +0200	[thread overview]
Message-ID: <20130919132146.GB3631@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20130919125536.GA12498@irqsave.net>

Am 19.09.2013 um 14:55 hat Benoît Canet geschrieben:
> Le Thursday 19 Sep 2013 à 10:57:50 (+0200), Kevin Wolf a écrit :
> > Am 19.09.2013 um 10:26 hat Stefan Hajnoczi geschrieben:
> > > On Wed, Sep 18, 2013 at 05:05:27PM +0200, Benoît Canet wrote:
> > > > Le Tuesday 17 Sep 2013 à 14:44:13 (+0200), Stefan Hajnoczi a écrit :
> > > > > Hi Benoit,
> > > > > Kevin and I had a chance to chat face-to-face and we discussed what
> > > > > concrete changes are necessary to merge quorum (without solving all the
> > > > > other block layers problems at once).
> > > > > 
> > > > > I think quorum could be merged relatively quickly (and without massive
> > > > > BlockFilter investments) by changing the following:
> > > > > 
> > > > > 1. Defining children on the command-line
> > > > > 
> > > > > Existing "filter" drivers use the protocol filename to embed their
> > > > > children, for example the blkverify driver.  This is a big hack because
> > > > > we have no proper syntax or escaping for the embedded drive definitions
> > > > > in the file= option.
> > > > > 
> > > > > This was one of the main arguments against merging quorum.  Now that
> > > > > Kevin has implemented driver-specific open options (see
> > > > > block/qcow2.c:qcow2_runtime_opts), it is possible for the quorum driver
> > > > > to open children specific on the command-line:
> > > > > 
> > > > >   -drive if=none,file.driver=quorum,format=raw,\
> > > > >          file.children0.file=/nfs1/test.qcow2,\
> > > > >          file.children1.file=/nfs2/test.qcow2,\
> > > > >          file.children2.file=/nfs3/test.qcow2
> > 
> > By the way, I think he concrete syntax might have to be a bit different
> > so it can be mapped to QAPI for blockdev-add. I think we'll want to use
> > a JSON list for the children; a mapping to QDict and to the command line
> > is yet to be implemented I guess.
> 
> Hi,
> 
> Just to make sure I'll code the right thing; is the following correct ?
> 
> -drive if=none,file.driver=quorum,format=raw,\
>        file.children=[/nfs1/test.qcow2, /nfs2/test.qcow2, /nfs3/test.qcow2], \
>        file.vote_threshold=2

I was thinking more along the lines of:

    -drive if=none,file.driver=quorum,format=raw,\
           file.children[0].file.filename=/nfs1/test.qcow2, \
           file.children[1].file.filename=/nfs2/test.qcow2, \
           file.children[1].file.cache.direct=on, \
           file.children[2].file.driver=nbd, \
           file.children[2].file.host=localhost, \
           file.vote_threshold=2

The exact syntax doesn't matter all that much as long as it can be
mapped to QAPI, but as you can see this allows specifying detailed
options even for the children. I think this is a requirement.

Kevin

  reply	other threads:[~2013-09-19 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 12:44 [Qemu-devel] Merging the quorum block driver Stefan Hajnoczi
2013-09-17 16:13 ` Benoît Canet
2013-09-18 15:05 ` Benoît Canet
2013-09-19  8:26   ` Stefan Hajnoczi
2013-09-19  8:57     ` Kevin Wolf
2013-09-19 12:55       ` Benoît Canet
2013-09-19 13:21         ` Kevin Wolf [this message]
2013-09-19 13:38           ` Benoît Canet
2013-09-19 14:23             ` Kevin Wolf
2013-09-20 12:08               ` Benoît Canet
2013-09-20 14:26                 ` Kevin Wolf
2013-09-19 14:51           ` Eric Blake
2013-09-19 15:05             ` Daniel P. Berrange

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=20130919132146.GB3631@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@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).