| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
historical data
JIRA: YARDSTICK-1458
The TG is only sampled at the end of every test interval.
This is incorrect. It should be sampled every interval.
Change-Id: I612ead8a243a7d9930874d02adc9b959b843b99b
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
|
|
JIRA: YARDSTICK-1457
Field types must be consistent across points in a measurement, otherwise
influxdb rejects newer points with "field type conflict" error.
This error was faced when "theor_max_throughput" field, meant to be
assigned as a float from "TxThroughput" sample, was instead assigned as
an int from initial value of theor_max_thruput variable. This especially
occured for subsequent packet sizes, when theor_max_thruput variable was
reset to its default int value.
This fix changes the default value of theor_max_thruput variable to 0.0,
and also makes sure that the default value for "Actual_throughput" field
is consistently a float.
Change-Id: If8d4f1297094709fe9657ab3e2b8adaad09815b2
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
JIRA: YARDSTICK-1419
When using prox_binsearch algorithm, a binary search is
performed, increasing lower bound when step was successful
and decreasing upper bound when the step was a failure.
This runs until the test_precision (as specified in the
traffic profile) is reached. When the test precision
is reached, the test is not completed until the
runner duration is reached.
As runner duration is usually high (e.g. 1800sec), the
tests take much too long to execute.
This makes it difficult to create test suites.
Change-Id: I6cc503a09fb534a556c61c805e6df4786bb8cc4b
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
List of changes:
- Added 'Status' field to indicate status of each search iteration.
Possible values are 'Success', 'Failure', 'Result'.
- Removed reporting of duplicated stats with 'Success_' prefix.
Instead 'Status' field is set to 'Success'
- Removed reporting of duplicated stats with 'Result_' prefix.
Instead 'Status' field is set to 'Result'
- Updated Prox_BM_L2FWD-4Port_MultiSize-1518452496550.json dashboard
to query success and result status by 'Status' field value.
JIRA: YARDSTICK-1386
Change-Id: I9a21a102af6cb4db137e805011b5d81c4943d77b
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
List of changes made in ProxBinSearchProfile:
- Removed reporting of redundant records with zero values
- Fixed issue with results data from one step reported in the next step
- Added 'Step_Id' field to reflect to which search step current record belongs
- Added 'Confirmation_Retry' field to reflect retry number of current test.
This value depends on 'confirmation' configuration option of a runner.
JIRA: YARDSTICK-1379
Change-Id: Idc3f7e26ece41ac0dfbfee659daf310a2879e024
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
JIRA: YARDSTICK-1252
CPU grouping in grafana for better representation
Throughput table is difficult to read as the tests
run longer the values can overlap
Default time in dashboard should be always last 1hour in
dashboard (auto refresh can be also checked)
Add one column in table with Gbps throughput (Rx
Throughput) plus code change in yardstick
Boxes are not aligned and big and small, need to be fixed
boxes are now aligned,
Added Seperate graphe for LINE Rate
Change-Id: Ief31777c2e7a18aab4bf21fb6ccc0e93a3bb9178
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1105
Running a vPE test ends up with up to 25% drooped packets.
This is due to tolerated loss being incorrectly configured,
test duration was too short and test interval was too
short.
Note This is due to the fact that vPE use case have by
default a tolerated loss of 100%, Now changed to 0.001,
same as L2FWD
Also: Grafan dashboard has been updated to show all SUT
CPUS Utilization in 1 panel. And LINE rate MIN, MAX & TEST
Rate have been added
Change-Id: I7adae2199b3f656fe460705b6aeb3aa69c767d50
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1221
In order to increase accuracy of result the following are done :-
- Improve Measurement Accuracy (YARDSTICK-1212)
- Improve Sampling Interval (YARDSTICK-1219)
- Allow 4 PROX ports to be read simultaneously (YARDSTICK-1220)
This change does the following :-
- Stores LINE Rate statistics of Sample
- Requires a confirmation retry before deciding to increase or
decrease this is configurable.
- Allows the user to disable Sampling or specify a sample interval
- Added Code Coverage of ProxDurationRunner based on YARDSTICK-1199
Change-Id: I27242ac1849c9a2712866385b5fbc05977c71516
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1212
Change-Id: Ic4d4a3c00e4e278f4de06cc176ff663892895569
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
|
|
There were some pep8 errors in the
prox_binsearch.py file. These are fixed here.
JIRA: YARDSTICK-1173
Change-Id: I817bba89c6ba298bb0f27b2538aa7585cb286754
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
The success criteria needed a fix for throughput
calculation. The results on success criteria were
muliplied by 1000*1000 which is not correct and
not needed as this was leading to false results
in grafana.
JIRA: YARDSTICK-1172
Change-Id: I56b24a700f8a565db80897aeab796e7039cae5c9
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
JIRA: YARDSTICK-1035
Do not hardcode NIC/interface speed in PROX test. Test assumes
NIC used is 10Gbps. This is incorrect. It could support 1Gbps,
10Gbps, 25Gbps, 40Gbps or something else.
This is used to calculate pps (Packets Per Second)
In Baremetal the NIC speed could be extracted. however when
run on a virtual machine this is not possible.
Solution:
Add in options section of test file.
eg.
Options:
interface_speed_gbps: 10
Where 10 refers to a 10Gbps. In a setup where multiple interfaces
are used. This will refer to the speed of the slowest connection.
Change-Id: I89ab16479a2cdd1d79e52cbcc5a972762c60d057
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1036
This stores a number of extra counters in influxdb for Prox test cases.
It also stores existing counters with a "succcess_" tag.
Previously throughput where stored without success or failure indication.
Also "Result_" counters are also stored.
These can now be used by Grafana to graph output.
Change-Id: Ie5636c14ecbab1b53a988bdfbd47ddd1fcdbd695
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-802
Added Prox BNG and BNG-QoS Test
- The tests supports BM, Openstack Heat
- Supports 4 ports
- Test added for BNG traffic profile
- Fixed the Prox heat test cases with
proper upstream and downstream links
- Grafana Dashboard for BNG & BNG-QoS added
- Increased the test Duration to 300
TODO:
- Test does not Terminate correctly
Update:
Added new helper class for run_test: Genric, MPLS
and BNG tests.
Change-Id: Ib40811bedb45a3c3030643943f32679a4044e076
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@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>
|
|
PROX was added to samplevnf project
https://git.opnfv.org/samplevnf/tree/VNFs/DPPD-PROX
JIRA: YARDSTICK-638
Change-Id: If9875b1130c6bed87deb8720b0d8b28ede9289d9
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
DanielMartinBuckley
Emma Foley
Patrice Buriez
Serhiy Pshyk
Xavier Simonart
Abhijit Sinha
Ross Brattain