CORD-2282 Create mcord-ng4t profile
Change-Id: Ib9f4bf71d04b21f6a9592527f901f5a5425a0b4e
(cherry picked from commit d730b6dc465b0f7ecff6491d1b47cde9e36db037)
diff --git a/mcord-spirent-test-playbook.yml b/mcord-spirent-test-playbook.yml
index 66af4e3..a80a61f 100644
--- a/mcord-spirent-test-playbook.yml
+++ b/mcord-spirent-test-playbook.yml
@@ -15,7 +15,7 @@
---
-# mcord-test-playbook.yml
+# mcord-spirent-test-playbook.yml
# Tests CiaB cord-pod XOS configuration
- name: Include vars
@@ -30,5 +30,29 @@
- name: Run base M-CORD tests
hosts: head
become: no
+ # These variables could be elevated to the profile. Think about
+ # doing this after the E2E test framework is complete.
+ vars:
+ test_networks:
+ - management
+ - sgi_network
+ - s11_network
+ - spgw_network
+ test_services:
+ - venb
+ - vspgwc
+ - vspgwu
+ test_ports:
+ - { vm: venb, network: management }
+ - { vm: venb, network: s11_network }
+ - { vm: venb, network: sgi_network }
+ - { vm: venb, network: s1u_network }
+ - { vm: vspgwc, network: management }
+ - { vm: vspgwc, network: s11_network }
+ - { vm: vspgwc, network: spgw_network }
+ - { vm: vspgwu, network: management }
+ - { vm: vspgwu, network: s1u_network }
+ - { vm: vspgwu, network: sgi_network }
+ - { vm: vspgwu, network: spgw_network }
roles:
- - test-mcord-base-spirent
+ - test-mcord-base