From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH] migration: allow clearing migration string parameters
Date: Wed, 1 Mar 2017 12:32:23 +0000 [thread overview]
Message-ID: <20170301123223.12489-1-berrange@redhat.com> (raw)
Some of the migration parameters are strings, which default to NULL,
eg tls_hostname and tls_creds.
The mgmt app will set the tls_creds parameter on both source and target
QEMU instances, in order to trigger use of TLS for migration.
After performing a TLS encrypted migration though, migration might be
used for other reasons - for example, to save the QEMU state to a file.
We need TLS turned off when doing this, but the migrate-set-parameters
QAPI command does not provide any facility to clear/reset parameters
to their default state.
If you simply ommit the tls_creds parameter in migrate-set-parameters,
then 'has_tls_creds' will be false and so no action will be taken. The
only option that works with migrate-set-parameters is to treat "" on
the wire as equivalent to requesting NULL. Failing that we would have
to create a new 'migrate-reset-parameters' method to explicitly put
a parameter back to its default value.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
CC'ing Eric & Markus since this is related to QAPI schema for migrate
monitor commands
migration/migration.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/migration/migration.c b/migration/migration.c
index c6ae69d..a5d41a9 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -872,11 +872,19 @@ void qmp_migrate_set_parameters(MigrationParameters *params, Error **errp)
}
if (params->has_tls_creds) {
g_free(s->parameters.tls_creds);
- s->parameters.tls_creds = g_strdup(params->tls_creds);
+ if (*params->tls_creds == '\0') {
+ s->parameters.tls_creds = NULL;
+ } else {
+ s->parameters.tls_creds = g_strdup(params->tls_creds);
+ }
}
if (params->has_tls_hostname) {
g_free(s->parameters.tls_hostname);
- s->parameters.tls_hostname = g_strdup(params->tls_hostname);
+ if (*params->tls_hostnane == '\0') {
+ s->parameters.tls_hostnane = NULL;
+ } else {
+ s->parameters.tls_hostname = g_strdup(params->tls_hostname);
+ }
}
if (params->has_max_bandwidth) {
s->parameters.max_bandwidth = params->max_bandwidth;
--
2.9.3
next reply other threads:[~2017-03-01 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 12:32 Daniel P. Berrange [this message]
2017-03-01 12:39 ` [Qemu-devel] [PATCH] migration: allow clearing migration string parameters no-reply
2017-03-01 12:40 ` no-reply
2017-03-01 14:36 ` Eric Blake
2017-03-01 14:48 ` Daniel P. Berrange
2017-03-01 15:36 ` Eric Blake
2017-03-02 7:55 ` Markus Armbruster
2017-03-02 12:33 ` Daniel P. Berrange
2017-03-03 14:44 ` Markus Armbruster
2017-03-03 16:18 ` Daniel P. Berrange
2017-03-03 17:05 ` Markus Armbruster
2017-03-03 17:08 ` Daniel P. Berrange
2017-03-14 18:49 ` Dr. David Alan Gilbert
2017-03-15 6:26 ` Markus Armbruster
2017-03-15 9:32 ` Dr. David Alan Gilbert
2017-03-15 10:30 ` Markus Armbruster
2017-03-15 10:36 ` Dr. David Alan Gilbert
2017-03-15 10:49 ` 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=20170301123223.12489-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.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).