summaryrefslogtreecommitdiff
path: root/tempest/scenario/manager.py
diff options
context:
space:
mode:
authorRohan Kanade <rohan.kanade@izeltech.com>2013-12-10 18:59:35 +0530
committerAndrea Frittoli (andreaf) <andrea.frittoli@hp.com>2015-03-26 14:50:03 -0400
commit9ce97dfa353e3659aa0ec0a7f62ed3a7e54c4bdf (patch)
treef0e757951c9f7fb61651afdf74f26e1c8d147fc8 /tempest/scenario/manager.py
parent171d05e97fccfba1a88b38320ce259ae3b47d31a (diff)
downloadtempest-9ce97dfa353e3659aa0ec0a7f62ed3a7e54c4bdf.tar.gz
Start instances using fixed network when possible
Uses the fixed_network_name option to select which network to boot test instances on. This allows Tempest to be run in environments where there are multiple networks available. This problem does not apply to nova-network environments because it will happily start instances with multiple networks attached, so the behavior is left as before in that case. Co-Authored-By: Ben Nemec <bnemec@redhat.com> Co-Authored-By: Vincent Untz <vuntz@suse.com> Co-Authored-By: git-harry <git-harry@live.co.uk> Change-Id: Ib5b84b59e3d182d8b9cc83954537c32f3eb9e388 Closes-Bug: #1250866
Diffstat (limited to 'tempest/scenario/manager.py')
-rw-r--r--tempest/scenario/manager.py3
1 files changed, 3 insertions, 0 deletions
diff --git a/tempest/scenario/manager.py b/tempest/scenario/manager.py
index f8cc17cde..bae829677 100644
--- a/tempest/scenario/manager.py
+++ b/tempest/scenario/manager.py
@@ -24,6 +24,7 @@ from tempest_lib import exceptions as lib_exc
from tempest import clients
from tempest.common import credentials
+from tempest.common import fixed_network
from tempest.common.utils.linux import remote_client
from tempest import config
from tempest import exceptions
@@ -184,6 +185,8 @@ class ScenarioTest(tempest.test.BaseTestCase):
flavor = CONF.compute.flavor_ref
if create_kwargs is None:
create_kwargs = {}
+ network = self.get_tenant_network()
+ fixed_network.set_networks_kwarg(network, create_kwargs)
LOG.debug("Creating a server (name: %s, image: %s, flavor: %s)",
name, image, flavor)