diff options
| author |   nikoskarandreas <nick@intracom-telecom.com> | 2018-07-12 19:40:30 +0300 |
|---|---|---|
| committer |   Stamatis Katsaounis <mokats@intracom-telecom.com> | 2018-11-01 16:33:13 +0200 |
| commit | 95dad3f4a73a22988c7a9b4694ce0d7e90cd8147 (patch) | |
| tree | bee89fef29ce5f36b0d3f646cec44b51ad869ac6 /docs | |
| parent | 5f3157c897eaa5ef538d716e905f55085654a6c5 (diff) | |
Using heat orchestrator for sdnvpn - test case 1
Heat orchestrator and the use of Heat Orchestrator Templates
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 heat 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 1:
VPN provides connectivity between subnets
and also base functions for heat api access and some utilities.
JIRA: SDNVPN-237
JIRA: SDNVPN-219
Change-Id: Ic284722e600652c9058da96d349dff9398bcacf1
Signed-off-by: nikoskarandreas <nick@intracom-telecom.com>
(cherry picked from commit cfcb04c938abdcddd76bcdd2375b4a81ea28fa51)
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions