From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>, Prasanna Kalever <pkalever@redhat.com>
Cc: qemu-devel@nongnu.org, "Bose, Sahina" <sabose@redhat.com>,
Sankarshan Mukhopadhyay <sankarshan@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Regarding the status of Gluster's multi volfile server patches
Date: Tue, 14 Jun 2016 16:00:28 -0600 [thread overview]
Message-ID: <57607E7C.8000303@redhat.com> (raw)
In-Reply-To: <20160614123614.GC823@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
On 06/14/2016 06:36 AM, Jeff Cody wrote:
> On Tue, Jun 14, 2016 at 03:27:55PM +0530, Prasanna Kalever wrote:
>> Hello,
>>
>> Can someone please help me in tracking the QAPI changes for union
>> discriminator addition,
>> the below [1] gluster related patches are awaiting from very long,
>> because of the dependency with QMP design changes.
>>
>> These patches [1] also stuck changes in libvirt/vdsm. It will be
>> really helpful for us, if someone can suggest what can be done to
>> accept this patches as early as possible.
>>
>> Many thanks in advance.
>>
>> [1] https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg06324.html
>
>
> Hi Prasanna,
>
> The last I know, as of v15 / v16, is that the libvirt team (Eric Blake)
> still has outstanding concerns on the QAPI interface.
>
> Eric, are your concerns regarding the API for this series still outstanding,
> or is this something you'd be comfortable supporting in libvirt with the
> current proposed interface?
I've currently posted all patches in my working tree, but review says I
need another round of review before it gets merged:
https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg03569.html
https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg03900.html
I'm also one or two patches shy of being able to use one union type as
the branch of another flat union type, where I still have to write the
patch, but it should be easy on top of the qapi patches that have landed
so far.
I also know that we want to get NBD converted for blockdev-add at the
same time, and that NBD, gluster, sheepdog, and other network-based
devices will share similar issues, so on my plate is to review this series:
https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01048.html
Can you please point me to the last proposal for gluster, and/or repost
any series you have for proposing the idea? I want to help get working
blockdev-add into 2.7 if at all possible.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-06-14 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 9:57 [Qemu-devel] Regarding the status of Gluster's multi volfile server patches Prasanna Kalever
2016-06-14 12:36 ` Jeff Cody
2016-06-14 22:00 ` Eric Blake [this message]
2016-06-15 7:04 ` Prasanna Kalever
2016-06-15 8:40 ` Prasanna Kalever
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=57607E7C.8000303@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jcody@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkalever@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sabose@redhat.com \
--cc=sankarshan@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).