Age | Commit message (Collapse) | Author | Files | Lines |
|
YARDSTICK-839
In a scale-up test the VNF number can start from
0 to MAX (num_vnf-1)
The NSB PROX BM test nodes are currently marked as:
tg__0: trafficgen_1.yardstick
vnf__0: vnf.yardstick
They need to be changed to the below:
tg__0: tg_0.yardstick
vnf__0: vnf_0.yardstick
Changes done are:
- All BM Prox test cases have tg_0 and vnf_0 as default
test nodes
- The prox-baremetal-1/2/4.yaml sample pod file
- Cleaned Up some unused Prox test/config files
Change-Id: I819011bcb35eda62b17dd3e1035918918c582b13
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
As per defect:
- the "context:" stanza of every tc_prox_baremetal*.yaml"
file has an incorrect pathname for the config file
- tc_prox_baremetal_binsearch.yaml and
tc_prox_baremetal_ramp.yaml refer to
"prox-baremetal.yml", which idoes not exist
- incorrect prox bin path
Resolution:
- Unify the pod file name and path for all BM tests
- Prox bin path changed to "/opt/nsb_bin/prox"
Change-Id: I16b25189104ad5585ddc1c2c0dd71b3c4c2aecd3
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
Also rename private to uplink, public to downlink
for scale-out template we need to count from 0
so we can use range() without +1/-1 errors
vnf_0, vnf_1
tg_0, tg_1
also fix Ixia defaults
Change-Id: I6aecfbb95f99af20f012a9df19c19be77d1b5b77
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
|
|
JIRA: YARDSTICK-802
Added Prox L3FWD and Packet buffering tests
- The tests supports BM and Openstack Heat
- L3FWD tests suports 2 and 4 ports
- Packet flow buffering test is a 1 port test
- Grafana Dashboards are added
TODO: Latency stats are missing in KPI collection
Need to invetigate that
Coverage if needed!
Change-Id: I216a170488d5578622cf8c3748a6277b380f016a
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|