Using heat orchestrator for sdnvpn - test case 2 03/63903/2
authornikoskarandreas <nick@intracom-telecom.com>
Tue, 23 Oct 2018 11:07:29 +0000 (14:07 +0300)
committernikoskarandreas <nick@intracom-telecom.com>
Thu, 1 Nov 2018 10:11:00 +0000 (12:11 +0200)
commit7fdfe9d8e38550ab1e610f86990d1bb306f47055
treee42b22190a9a106526398a4f3b36f652ecced9e9
parentb17b3d80849b9c9989fb4deeb6001a6ff78261c1
Using heat orchestrator for sdnvpn - test case 2

Heat orchestrator and the use of Heat Orchestrator Template
is introduced in sdnvpn test cases. The deployment of the
nodes and networks under test is performed as a stack with the
use of the openstack api and the use of the other apis is kept
to as little as possible. The scenarios that are executed are
the same as in the orginal test cases.

This is the implementation of sdnvpn test case 2:
Tenant separation

JIRA: SDNVPN-219

Change-Id: I20f5ed8f7d250873f0223c1cd00c6c05d00fbfa8
Signed-off-by: nikoskarandreas <nick@intracom-telecom.com>
sdnvpn/artifacts/testcase_2bis.yaml [new file with mode: 0644]
sdnvpn/test/functest/config.yaml
sdnvpn/test/functest/testcase_2bis.py [new file with mode: 0644]