summaryrefslogtreecommitdiffstats
path: root/samples/vnf_samples/nsut/prox
AgeCommit message (Collapse)AuthorFilesLines
2018-10-04Fix NSB PROX L3FWD dropping packetsPatrice Buriez2-2/+14
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> (cherry picked from commit 3adfba6bac0133bdbaa3db62e16f662e11d84fb8)
2018-09-04NSB NFVi PROX Missing VNF Statistics for CPU UtilizationDanielMartinBuckley37-0/+149
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>
2018-08-02NSB NFVi PROX BNG and vPE losing many packetsDanielMartinBuckley9-10/+109
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>
2018-06-27NSB NFVi PROX BNG losing many packetsDanielMartinBuckley8-22/+44
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>
2018-06-27NSB NFVi PROX VPE losing many packetsDanielMartinBuckley2-3/+6
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>
2018-06-26Merge "Addition of Configurable Sampling and Configurable Confirmation Retry"Abhijit Sinha1-2/+8
2018-06-26Addition of Configurable Sampling and Configurable Confirmation RetryDanielMartinBuckley1-2/+8
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>
2018-06-26NSB Topology fix for Prox 4 port test caseAbhijit Sinha14-47/+52
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>
2018-06-21Merge "Add scale out TCs with availability zone support"Rodolfo Alonso Hernandez2-0/+166
2018-06-07Fix latency in l2 and l3 PROX generator config filesXavier Simonart4-20/+85
JIRA: YARDSTICK-1211 Change-Id: I0899d470ca5a0ec7d42d36a9ff9c39cc7369310c Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-05-28Merge "PROX: [WIP] Added scale up TCs."Rodolfo Alonso Hernandez10-0/+810
2018-05-25Add scale out TCs with availability zone supportMytnyk, Volodymyr2-0/+166
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>
2018-05-09Fix Prox L2fwd generator packetAbhijit Sinha2-12/+7
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>
2018-03-16Merge "NSB PROX L3FWD Dropping packets"Abhijit Sinha10-97/+207
2018-03-15NSB PROX L3FWD Dropping packetsDanielMartinBuckley10-97/+207
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>
2018-03-09Do NOT hardcode interface speed for PROX testsDanielMartinBuckley2-0/+4
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>
2018-03-05PROX: [WIP] Added scale up TCs.Mytnyk, Volodymyr10-0/+810
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>
2018-02-28Addition of storage of extra counters for GrafanaDanielMartinBuckley2-8/+18
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>
2018-02-14BugFix: Fix to pod context filenameXavier Simonart1-1/+1
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>
2018-02-08Prox vnf descriptor cleanupAbhijit Sinha3-6/+6
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>
2018-01-23Cleanup of redundant files from Prox directoryAbhijit Sinha15-631/+0
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>
2017-11-14NSB Prox BM test case fixes for scale upAbhijit Sinha28-337/+99
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>
2017-11-09Merge "NSB Prox LW_AFTR Test"Ross Brattain5-0/+66084
2017-11-07Fixed incorrect Copyright NoticeDanielMartinBuckley1-27/+10
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>
2017-11-07NSB Prox LW_AFTR TestDanielMartinBuckley5-0/+66084
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>
2017-10-23BugFix: Fix to pod filename ext and prox pathAbhijit Sinha38-99/+99
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>
2017-10-11Bug in NSB Prox ACL Test 4 PortDanielMartinBuckley1-1/+1
JIRA: YARDSTICK-802 Generator was incorrectly configured to generated traffic for p0, p1 (twice), and p3 Should be p0, p1, p2 and p3 Change-Id: Ib62a3c6523b1eda635b8c727c36e140fd480003e Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
2017-10-06NSB Prox vPE TestAbhijit Sinha9-0/+4924
JIRA: YARDSTICK-802 Addition of Prox vPE test case - The tests supports BM, Openstack Heat - Supports 4 ports - Grafana dashboards included - Added support for parameters.lua for prox additional files - Unit tests for code coverage Change-Id: I5cccb351dacba88a293ae4b8aba1f0a803d62e6d Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com> Signed-off-by: Daniel MArtin Buckley <daniel.m.buckley@intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-10-02Prox L3FWD 2-port test fixAbhijit Sinha1-5/+0
JIRA: YARDSTICK-802 Updated the handle config for l3fwd 2 port test The tx and rx descripters is removed as they were not there in original DATS config. The BM test was dropping packets beacuse of this. Change-Id: I40d113267cbb3376a772b5a5aaecf74bea9d06fb Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
2017-09-28Adjusted IPs in some prox tests.Maciej Skrocki2-4/+4
Change-Id: Iff39fa5b90d1ae5534ce1fff31dfb84c1e47340c Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-09-28Addition of Prox NSB BNG and BNG-QoS testAbhijit Sinha31-215/+66887
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>
2017-09-21Bumped samplevnfs flavor disk size to 6G.Maciej Skrocki12-21/+20
Since we increased the images size the 4G is not sufficient anymore. Change-Id: Iae25cf4cfb7a6cc69c8d28771c183a2342ac38d0 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-09-20Addition of PROX NSB tests to yardstickDanielMartinBuckley21-100/+1299
JIRA: YARDSTICK-802 Addition of PROX L2FWD_Multiflow, ACL, Load Balancing plus grafana dashboards Supports 2 and 4 port Baremetal & Heat Change-Id: I1f3990d5451de265ee3901302569c355ece3b146 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
2017-09-19prox testcases: private -> uplink,public -> downlink, vnf_0, tg_0Ross Brattain16-142/+346
Change-Id: I85afff4582bf538fcd0be5b4db1405a4da2573f9 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-09-18NSB: count from 0, vnf_0, tg_9, private->uplink, public->downlinkRoss Brattain43-213/+213
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>
2017-09-06Addition of Prox NSB tests in yardstickAbhijit Sinha15-0/+1065
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>
2017-09-04Addition of Prox NSB changes in yardstickabhijitsinha45-22/+1905
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>
2017-08-14PROX VNF and TGRoss Brattain35-0/+34965
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>