Fix RFC2544 Trex template

Use template traffic profile instead of static one

JIRA: YARDSTICK-1592

Change-Id: I665896c4e533cd7b29f8b906c8c10f769f9268a7
Signed-off-by: Chornyi Taras <tarasx.chornyi@intel.com>

diff --git a/samples/vnf_samples/nsut/agnostic/tc_baremetal_rfc2544_ipv4_trex_tmpl.yaml b/samples/vnf_samples/nsut/agnostic/tc_baremetal_rfc2544_ipv4_trex_tmpl.yaml
index 79c3b90..71d9074 100644 (file)
--- a/samples/vnf_samples/nsut/agnostic/tc_baremetal_rfc2544_ipv4_trex_tmpl.yaml
+++ b/samples/vnf_samples/nsut/agnostic/tc_baremetal_rfc2544_ipv4_trex_tmpl.yaml
@@ -23,7 +23,7 @@
 schema: yardstick:task:0.1
 scenarios:
 - type: NSPerf-RFC2544
-  traffic_profile: ../../traffic_profiles/ipv4_throughput.yaml
+  traffic_profile: ../../traffic_profiles/ipv4_throughput-tmpl.yaml
   topology: agnostic_vnf_topology_trex_tmpl.yaml
   extra_args:
     vports: {{vports}}
@@ -48,6 +48,7 @@ scenarios:
     traffic_type: 4
     rfc2544:
       allowed_drop_rate: {{drop_rate}}
+    tg__0:
       queues_per_port: {{queues_per_port}}
     vnf__0:
         []