| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
JIRA: YARDSTICK-1404
The test scripts require an extra argument to support collectd.
Also the CPU utilization is a different variable name structure
in the JSON file.
Change-Id: I127b7e86c0f93f7743331a2d71eb81d690e42471
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
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
Addition of Prox L2Fwd, MPLS test cases for BM and Heat.
updates:
Most of tg_prox and prox_vnf were absorbed into the base classes.
delete most of ProxDpdkVnfSetupEnvHelper, it is handled by DpdkVnfSetupEnvHelper baseclass
use standard _build_pipeline_kwargs methods
don't use terminate() use baseclass version
add new method kill_vnf that runs pkill -x
replace resource_helper.execute() with vnf_execture for dumping stats
In order to share code between tg_prox and vnf_prox
refactor to have tg_prox hold and wrap a ProxApproxVnf instance and call
methods on that class. Do this instead of multiple-inheritance.
Implement ProxApproxVnf.terminate() using prox socket command
based exit, (stop_all, quit, force_quit).
vnf_execute calls resource_helper.execute() which calls
socket methods on the sut object.
Since tg_prox wraps the VNF object, we can call
terminate on the VNF object and it should work correctly.
move prox config generation to parent process
we need to get core number info from config file
inside the TG processes, so we need to generate
the config in the parent process so the data is
copied to the child during the fork.
moved more config file methods to the setup_helper class.
we run force_quit after quit, so the socket should already be closed
this will trigger socket error, so add _ignore_errors option for
vnf_execute to ignore socket errors
Fixed the terminate issue. Added MPLS tests.
Added TG Stats in_packet/out_packet
Fixed compile (pep8) issues
Fixed MPLS TG port stats, in/out packets
Added Grafana dashboards for L2FWD and MPLS
Traffic profiles modified for tolerated loss and
precision as per DATS tests.
Added unit test case for Mpls
Single port test stats collection support.
Change-Id: Idd9493f597c668a3bb7d90e167e6a418546106e8
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
DanielMartinBuckley
Abhijit Sinha
Ross Brattain