From: Het Gala <het.gala@nutanix.com>
To: qemu-devel@nongnu.org
Cc: prerna.saxena@nutanix.com, quintela@redhat.com,
dgilbert@redhat.com, pbonzini@redhat.com, berrange@redhat.com,
armbru@redhat.com, eblake@redhat.com, manish.mishra@nutanix.com,
aravind.retnakaran@nutanix.com
Subject: Re: [PATCH v6 1/9] migration: introduced 'MigrateAddress' in QAPI for migration wire protocol.
Date: Wed, 28 Jun 2023 16:45:29 +0530 [thread overview]
Message-ID: <b6c64f09-9fd9-b076-d18e-5f07004f7f2e@nutanix.com> (raw)
In-Reply-To: <119c9352-e93f-cb77-f2b0-935d808b0f1e@nutanix.com>
On 13/06/23 10:58 am, Het Gala wrote:
>
> On 06/06/23 3:45 pm, Het Gala wrote:
>> This patch introduces well defined MigrateAddress struct and its related
>> child objects.
>>
>> The existing argument of 'migrate' and 'migrate-incoming' QAPI - 'uri'
>> is of string type. The current migration flow follows double encoding
>> scheme for fetching migration parameters such as 'uri' and this is
>> not an ideal design.
>>
>> Motive for intoducing struct level design is to prevent double encoding
>> of QAPI arguments, as Qemu should be able to directly use the QAPI
>> arguments without any level of encoding.
>>
>> Suggested-by: Aravind Retnakaran <aravind.retnakaran@nutanix.com>
>> Signed-off-by: Het Gala <het.gala@nutanix.com>
>> Reviewed-by: Juan Quintela <quintela@redhat.com>
>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>> ---
>> qapi/migration.json | 45 +++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 45 insertions(+)
>>
>> diff --git a/qapi/migration.json b/qapi/migration.json
>> index 179af0c4d8..e61d25eba2 100644
>> --- a/qapi/migration.json
>> +++ b/qapi/migration.json
>> @@ -1407,6 +1407,51 @@
>> ##
>> { 'command': 'migrate-continue', 'data': {'state':
>> 'MigrationStatus'} }
>> +##
>> +##
>> +# @MigrationAddress:
>> +#
>> +# Migration endpoint configuration.
>> +#
>> +# Since 8.1
>> +##
>> +{ 'union': 'MigrationAddress',
>> + 'base': { 'transport' : 'MigrationAddressType'},
>> + 'discriminator': 'transport',
>> + 'data': {
>> + 'socket': 'SocketAddress',
>> + 'exec': 'MigrationExecCommand',
>> + 'rdma': 'InetSocketAddress' } }
>> +
>> ##
>> # @migrate:
>> #
>
> Hi maintainers, this is just a reminder mail for v6 patchset for
> modification the QAPI design for migration qapis - 'migrate' and
> 'incoming-migrate'. From the last discussion, I have modified
> definitions specifically around QAPIs in patch 1 and 6, and have tried
> to make it short and consice and meaningful. Please have a look at it
> and suggest if any changes required. Tagging maintainers who have
> actively participated in the discussion in last few iterations :
> Markus, Daniel, Eric, Juan - but regardless other maintainers are also
> very well welcomed to share their opinions.
>
This is just a friendly reminder mail for v6 patchset discusiion for
modification of QAPI design for migration qapis. I know the maintainers
were quite busy with KVM forum during the time I had sent out first
reminder. Hope to get some positive reviews on the v6 patches soon.
Thanks in advance !!
Regards,
Het Gala
next prev parent reply other threads:[~2023-06-28 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:15 [PATCH v6 0/9] migration: Modify 'migrate' and 'migrate-incoming' QAPI commands for migration Het Gala
2023-06-06 10:15 ` [PATCH v6 1/9] migration: introduced 'MigrateAddress' in QAPI for migration wire protocol Het Gala
2023-06-13 5:28 ` Het Gala
2023-06-28 11:15 ` Het Gala [this message]
2023-07-05 11:21 ` Markus Armbruster
2023-07-05 12:49 ` Het Gala
2023-07-05 12:58 ` Markus Armbruster
2023-06-06 10:15 ` [PATCH v6 2/9] migration: convert uri parameter into 'MigrateAddress' struct Het Gala
2023-07-05 11:29 ` Markus Armbruster
2023-07-05 13:18 ` Het Gala
2023-06-06 10:15 ` [PATCH v6 3/9] migration: convert socket backend to accept MigrateAddress struct Het Gala
2023-06-06 10:15 ` [PATCH v6 4/9] migration: convert rdma " Het Gala
2023-06-06 10:15 ` [PATCH v6 5/9] migration: convert exec " Het Gala
2023-06-06 10:15 ` [PATCH v6 6/9] migration: modified migration QAPIs to accept 'channels' argument for migration Het Gala
2023-06-08 11:52 ` Het Gala
2023-06-06 10:15 ` [PATCH v6 7/9] migration: modify migration_channels_and_uri_compatible() to incorporate newer migration QAPI syntax Het Gala
2023-06-06 10:15 ` [PATCH v6 8/9] migration: Introduced MigrateChannelList struct to migration code flow Het Gala
2023-06-06 10:15 ` [PATCH v6 9/9] migration: adding test case for modified QAPI syntax Het Gala
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=b6c64f09-9fd9-b076-d18e-5f07004f7f2e@nutanix.com \
--to=het.gala@nutanix.com \
--cc=aravind.retnakaran@nutanix.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=manish.mishra@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).