From: Jeff Cody <jcody@redhat.com>
To: Prasanna Kumar Kalever <pkalever@redhat.com>
Cc: kwolf@redhat.com, peter.maydell@linaro.org, pkrempa@redhat.com,
stefanha@gmail.com, qemu-devel@nongnu.org, deepakcs@redhat.com,
bharata@linux.vnet.ibm.com, rtalur@redhat.com
Subject: Re: [Qemu-devel] [PATCH v13 3/3] block/gluster: add support for multiple gluster servers
Date: Thu, 12 Nov 2015 11:23:35 -0500 [thread overview]
Message-ID: <20151112162335.GA16646@localhost.localdomain> (raw)
In-Reply-To: <442468387.9450444.1447322642567.JavaMail.zimbra@redhat.com>
On Thu, Nov 12, 2015 at 05:04:02AM -0500, Prasanna Kumar Kalever wrote:
> On Tuesday, November 10, 2015 9:37:20 PM, Eric Blake wrote:
> >
> > On 11/10/2015 02:09 AM, Prasanna Kumar Kalever wrote:
> > > This patch adds a way to specify multiple volfile servers to the gluster
> > > block backend of QEMU with tcp|rdma transport types and their port numbers.
> > >
> >
> > [...]
>
> [...]
>
> >
> > Overall, I think we are probably on the right track for the QMP
> > interface; but since blockdev-add is NOT stable yet for 2.5, it won't
> > hurt to wait to get this in until 2.6, to make sure we have plenty of
> > time; and it would also be nice to make sure we get nbd, nfs, rbd,
> > sheepdog all supported in the same release; possibly by sharing common
> > types instead of introducing GlusterServer as a one-off type.
>
> We are hoping this to go in 2.5 which is really important for gluster
> hyper-convergence release (next Feb).
>
> Is there any possibility of getting exception for this patch ?
>
> Thanks,
> -Prasanna
>
Today is the hard freeze for 2.5 for new features. As the v14 patches
hit the list today, I will review them, and if they look good I can
pull patches into my tree.
Whether there is an exception is really up to Peter Maydell
(added him to the cc) - if all looks good with the patches, I could
send a pull request out later today with them, but that will be late
in the evening for Peter.
-Jeff
next prev parent reply other threads:[~2015-11-12 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 9:09 [Qemu-devel] [PATCH 0/3] block/gluster: add support for multiple gluster servers Prasanna Kumar Kalever
2015-11-10 9:09 ` [Qemu-devel] [PATCH v2 1/3] block/gluster: rename [server, volname, image] -> [host, volume, path] Prasanna Kumar Kalever
2015-11-10 15:28 ` Eric Blake
2015-11-10 9:09 ` [Qemu-devel] [PATCH v2 2/3] block/gluster: code cleanup Prasanna Kumar Kalever
2015-11-10 9:09 ` [Qemu-devel] [PATCH v13 3/3] block/gluster: add support for multiple gluster servers Prasanna Kumar Kalever
2015-11-10 16:07 ` Eric Blake
2015-11-10 17:19 ` Jeff Cody
2015-11-12 10:04 ` Prasanna Kumar Kalever
2015-11-12 16:23 ` Jeff Cody [this message]
2015-11-13 4:54 ` Jeff Cody
2015-11-10 17:24 ` Jeff Cody
2015-11-12 9:46 ` Prasanna Kumar Kalever
2015-11-10 15:26 ` [Qemu-devel] [PATCH 0/3] " Eric Blake
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=20151112162335.GA16646@localhost.localdomain \
--to=jcody@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=deepakcs@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pkalever@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rtalur@redhat.com \
--cc=stefanha@gmail.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).