Age | Commit message (Collapse) | Author | Files | Lines |
|
Files added:
tc_prox_sriov_multi-flow-scale-up.yaml
tc_prox_ovs-dpdk_multi-flow-scale-up.yaml
JIRA: YARDSTICK-1551
Change-Id: I63c5adf79b00af4413dd1f131e918651567710d7
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
JIRA: YARDSTICK-1460
Change-Id: Id6a633873a9b6fc8829d5282596200610cec5426
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
|
|
|
|
Topology file changed as original did not work.
Added 'standalone-args.yaml' file for context information/details
JIRA: YARDSTICK-1547
Change-Id: I76dc782dac14db50dc8802f4f69cf077da0257a2
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
JIRA: YARDSTICK-1547
Change-Id: I5915c0e8df343e2c21396a9892d4728377e333bc
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
Corrected the generator config file by adding the
latency position validated the test case with it.
JIRA: YARDSTICK-1530
Change-Id: I18dd1c7add8fc77bb59354fa96540ba8690057a4
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
JIRA: YARDSTICK-1524
Add dashboard, Traffic Profile support, PROX IRQ support, topology
Change-Id: I0c0cde66f4f4d3d25aa77c502bd4349cc1b3eca2
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
Files renamed to include dpdk in name.
User/Password fields not needed in standalone context.
Fix with OvS test case file dpdk port number added.
JIRA: YARDSTICK-1500
JIRA: YARDSTICK-1475
JIRA: YARDSTICK-1471
Change-Id: I0422b5341172f098b1ff95b51b6fbc71b1b049f0
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
|
|
|
|
|
|
JIRA: YARDSTICK-1475
Change-Id: I511130ad65acbd2a052b6285c8408bfc098adbb6
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
|
|
This contains two files: 2 & 4 port test cases.
JIRA: YARDSTICK-1515
Change-Id: I9b6b5fd47a854571bc4e9f67c570b183e65245db
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
Changes made to prox_bm.yaml file for 4 port support.
JIRA: YARDSTICK-1471
Change-Id: I7e7873bd6d2337659ca19abfd4d2b4db5d89fc95
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
Patch contains two test case files: 2 Port & 4 Port
JIRA: YARDSTICK-1501
Change-Id: Ia3fff6ea97577d078a216d5d02f8e5257df1bd13
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
Patch contains two test case files: 2 Port & 4 Port
JIRA: YARDSTICK-1500
Change-Id: Ia80ef1de072f1402196cc65089ab6929c09ecb6f
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
|
|
JIRA: YARDSTICK-1460
Cores running "mode=lat" must be properly configured with a correct
"lat pos" parameter. When this parameter is missing, PROX exits with
an error message.
When the "lat pos" parameter is missing for cores running "mode=gen",
latency values are not written into the packets.
Also fixed some typos, packet inline format, IP len and UDP len.
Change-Id: Ice06c5d74686c80f09bc60f568993dbf3165b338
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
|
|
No sample testcase for prox SRIOV standalone.
Renamed pod file so that other prox testcases can use this file
JIRA: YARDSTICK-1471
Change-Id: Icc20e395a3fb4c9d1398f85198d64682b2a9ee33
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
No sample testcase for prox OvS-DPDK standalone.
JIRA: YARDSTICK-1475
Change-Id: Ide65444d08d6c90e7e98d59b7d1f4cba8ca7397f
Signed-off-by: Carey, Alan <alan.carey@intel.com>
|
|
Removing the "keyfile" from the pod file to align with other
pod files for 1 and 4 port. The file when used as such currently
gives an error. This change will fix that.
JIRA:YARDSTICK-1477
Change-Id: Ibfa9387d068a0098ea0eb0b31ad96108d0602abc
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
JIRA: YARDSTICK-1037
Adjusted number of RX/TX descriptors to 2048, instead of default 256,
in order to cope with interrupts during which no packets are received
by the core, which results in the NIC dropping packets when it gets out
of available descriptors to buffer them.
Also adjusted mempool size, because more descriptors need more mbufs.
This change aligns L3FWD test case with other test cases, for which
number of RX/TX descriptors is already set to 2048.
Change-Id: I11378c078398aca799295b619bb3d14dbee04ca3
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
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>
|
|
JIRA: YARDSTICK-1101
The traffic generated by the generator in bng-4 result in
non-symmetrical use of the cores on the SUT, as a whole
range of IP addresses is skipped.
Update cpe0 and cpe1 in gen files.
In addition, for the routing table (ipv4.lua) for the BNG
should be slighly different: while the BNG is a 4 ports
test, only 2 of the ports are used as outgoing routing
ports (the inet ports). Hence, the routing table should
only use the mac of those two ports. The bad configuration
(using 4 ports) result in an issue when BNG SUT and GEN
are connected through a switch, packets are sent by the
BNG SUT through the INET interfaces, but sometimes with
the MAC of the CPE interface...
Hence, packets are received on the wrong interface on the
Gen site (resulting in some interfaces, the CPE ones,
being overloaded)
Created ipv4_bng.lua and remove mac 0 and 2
Change-Id: I97019f0415d2f58d50ec855d04800eb705f41541
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-1101
Problem was incorrect generator and changed the traffic profile to allow
a tolerated loss of 5%.
ARP packets are not managed (just passed thru the system) therefor the
tolerated loss must be higehr than normal.
Change-Id: I03bd62b397a66b50961e810d033c6894d0b3e9a6
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>
|
|
The uplink and downlink interfaces for the 4 port
test cases were inconsistent and fixed in this commit.
This affects all the 4 port PROX test cases.
Tested on: Heat L2fwd-4 and L3fwd-4 test case.
JIRA: YARDSTICK-1185
Change-Id: Ia2ce7ed0dc395b812f84ede94e259b42dc833579
Signed-off-by:Abhijit Sinha <abhijit.sinha@intel.com>
|
|
|
|
JIRA: YARDSTICK-1211
Change-Id: I0899d470ca5a0ec7d42d36a9ff9c39cc7369310c
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
|
|
|
|
Add PROX and vFW scale out TCs with availability zone
configuration. To be able to specify the availability
zone for specific VNF or TG the following example of
command line option shoud be used:
yardstick -d task start --task-args='{
"num_vnfs": 2, "availability_zone":
{
"vnf_0": "az_0", "tg_0": "az_0",
"vnf_1": "az_1", "tg_1": "az_1",
... }}' <SCALE-OUT-TC-FILE>
The steps to run new scale-out TCs is documented in the
userguide.
JIRA: YARDSTICK-1203
Change-Id: Ib3878485c5483981fe9b48ab02995712bcc31ae5
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
The Prox L2-fwd test case has a bad packet, which fails
the test case to run in OpenStack context as it's dropped
by the neutron.
This fix is needed to successfully run the L2fwd 2 and
4 port test cases in heat based test cases.
Change-Id: I86df31a6df1eaa6f968e46af159ac6a0157f402c
JIRA: YARDSTICK-1164
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
|
|
JIRA: YARDSTICK-1037
NSB PROX L3FWD was incorrect. The routing table (ipv4.lua) was incorrect.
Also a specific ipv4 for 2 port configuration is required.
Change-Id: I3a5fd1ea1d1ddf74cbdd6a5d9e7ced42d3c1d6e9
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
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>
|
|
These scale-up TCs replace PROX static TCs which will be removed
by separate commit once those new TCs are merged.
Change-Id: I892a81c4bfd199782fb561faccc11e70a49675ae
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@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>
|
|
The "context:file" of tc_prox_baremetal_lw_aftr
has an incorrect path, compaired to all other
prox test cases.
Change-Id: Id24e74905f36bc84fdf93d1a2966211ecad55c8b
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
|
|
JIRA: YARDSTICK-1003
- There are redundant files for Prox vnf descriptors
tg and vnf for 1, 2 and 4 port set-up.
- We can use one vnf descriptor file per prox tg and prox vnf,
reducing the number of redundant files.
- Tested on Prox BM L2fwd 2 and 4 port test case.
Change-Id: I4c61fd11725121f19392443460ac2ad39c934e2d
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
JIRA: YARDSTICK-965
Removed the redundant files and directory from
Prox test folder.
Change-Id: I6167f0a4ccdd581153dad3ec9f5eaaf2619aacbd
Signed-off-by: Abhijit Sinha <abhijit.sinha@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>
|
|
|
|
Changed Copyright notice on tuples.lua from "Intel Copyright" to Apache 2.0
Change-Id: I85e6f9eb86c116d552f86cddf05b3b368b32f776
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
JIRA: YARDSTICK-802
Addition of PROX LW_AFTR basked on PROX/DATS v037 test_104_lw_aftr.py
- This support BM and Openstack Heat
- This supports 4 Ports ONLY
- Grafana Dashboards included
- Code Coverage / Unit testing
Change-Id: If2170ab458bf687256d5f1a1e840a3b9d2788ef7
Signed-off-by: Daniel MArtin Buckley <daniel.m.buckley@intel.com>
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>
|