From: Oksana Vohchana <ovoshcha@redhat.com>
To: qemu-devel@nongnu.org
Cc: ovoshcha@redhat.com, philmd@redhat.com, wainersm@redhat.com,
crosa@redhat.com
Subject: [PATCH v2 1/4] Acceptance test: adds param 'address' in _get_free_port
Date: Tue, 25 Feb 2020 15:12:59 +0200 [thread overview]
Message-ID: <20200225131302.4792-2-ovoshcha@redhat.com> (raw)
In-Reply-To: <20200225131302.4792-1-ovoshcha@redhat.com>
In the migration test function _get_free_port works only for localhost,
but in the case to use migration through an RDMA we need to get a free port
on the configured network RDMA-interface.
This patch is the start for another migration option
Signed-off-by: Oksana Vohchana <ovoshcha@redhat.com>
---
tests/acceptance/migration.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/acceptance/migration.py b/tests/acceptance/migration.py
index a8367ca023..e4c39b85a1 100644
--- a/tests/acceptance/migration.py
+++ b/tests/acceptance/migration.py
@@ -52,8 +52,8 @@ class Migration(Test):
source_vm.qmp('migrate', uri=src_uri)
self.assert_migration(source_vm, dest_vm)
- def _get_free_port(self):
- port = network.find_free_port()
+ def _get_free_port(self, address='localhost'):
+ port = network.find_free_port(address=address)
if port is None:
self.cancel('Failed to find a free port')
return port
--
2.21.1
next prev parent reply other threads:[~2020-02-25 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 13:12 [PATCH v2 0/4] Acceptance test: Extension of migration tests Oksana Vohchana
2020-02-25 13:12 ` Oksana Vohchana [this message]
2020-02-25 13:13 ` [PATCH v2 2/4] Acceptance test: EXEC migration Oksana Vohchana
2020-02-25 13:13 ` [PATCH v2 3/4] Acceptance test: provides new functions Oksana Vohchana
2020-02-25 13:13 ` [PATCH v2 4/4] Acceptance test: provides to use RDMA transport for migration test Oksana Vohchana
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=20200225131302.4792-2-ovoshcha@redhat.com \
--to=ovoshcha@redhat.com \
--cc=crosa@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.