Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Implement code to support traffic_duration field in test case options.
This updates the 'duration' in Landslide session profile.
traffic_duration should always be much less than runner duration/timeout.
JIRA: YARDSTICK-1427
Change-Id: I51094bade683ca8758136ccb619e8894a2ecef72
Signed-off-by: Orest Voznyy <orestx.voznyy@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>
|
|
|
|
Allow yardstick to update IP/MAX of Net traffic
- Implemented functionality for updating traffics IP/MAC address
in ixloadconfiguration.
- Extended http_ixload.py with functions for update IP/MAC
address of netTraffic.
- In HTTP-vFW_IPv4_2Ports_Concurrency.rxf changed name's of
networks from "client network" to "uplink_0 and the same for
server
JIRA: YARDSTICK-1418
Change-Id: I28ef68b77466fff15af589954e3ef63e8099428f
Signed-off-by: Myron Sosyak <myronx.sosyak@intel.com>
Signed-off-by: Taras Chornyi <tarasx.chornyi@intel.com>
|
|
JIRA: YARDSTICK-1466
Change-Id: I2e4b7f54591489a90c44535a09207de8a46d0e24
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@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>
|
|
|
|
Using AgnosticVNF is now possible to create a "black box"
testcase for any VNF.
Example rfc2544 test with TRex as trafficgen
samples/vnf_samples/nsut/agnostic/tc_baremetal_rfc2544_ipv4_64B_trex.yaml
and Ixia
samples/vnf_samples/nsut/agnostic/tc_baremetal_rfc2544_latency_ipv4_64B_ixia.yaml
NOTE:
Yardstick will not interact with VNF.
No KPIs from VNF will be collected
JIRA: YARDSTICK-1438
Change-Id: I408b3dcb90f29c7b41fcf8f883b5abfc4e9c3dbc
Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
|
|
'YARDSTICK-1359', 'YARDSTICK-1356'
* changes:
Add vEPC service request test cases
Add network initiated dedicated bearers creation
Add UE initiated dedicated bearer creation test
Add vEPC infrastructure for Landslide TG
Add vEPC default bearers relocation test case
Add vEPC default bearers create/delete test case
Add Spirent Landslide traffic profile templates
Update LSResourceHelper unittests
Add Spirent Landslide TG API
Added Landslide Resource Helper implementation
Add TclClients for Spirent Landslide TG
|
|
Add UE and network initiated testcase and related session profiles.
JIRA: YARDSTICK-1429
Change-Id: I16d6c065cf346db31e235ac5add57509cfbc8009
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
Adding related pod file, session profile and testcase file.
JIRA: YARDSTICK-1355
Change-Id: Ic97d59ef3a36ac05c6c369c36f917ae95d18d863
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
Adding session profile and test case file.
JIRA: YARDSTICK-1353
Change-Id: Iaa98fd8cb3ed243f9ac157089de32fa23ec0e6b4
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
1. Add yardstick topology and model for fully emulated environment.
2. Add support for black-box testing of real vEPC VNF vs Spirent Landslide
traffic generator:
- vEPC VNF pod file
- topology and model files aware of vEPC VNF connection to Spirent
Landslide TG
- stub class for vEPC VNF, and related unit tests
JIRA: YARDSTICK-1424
Change-Id: If7b6d19919679347c4360f4a0f2e420716e7fd2d
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
This test case runs on Spirent Landslide TG. All vEPC entities are
emulated on Landslide test servers.
Test case actions sequence:
- create default bearers
- start sending traffic
- partial/full bearers relocation between two ENodeB's, Intra-MME
- disconnect all bearers
JIRA: YARDSTICK-1354
Change-Id: I95c7b0001ddb363402013d83ae8617b88b2a4bd9
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
This test case runs on Spirent Landslide TG. All vEPC entities are
emulated on Landslide test server.
Test run configuration is performed in following files:
1. test case file
2. pod file
3. session profile file (landslide_session_default_bearer*.yaml)
The structure of these files represents configuration of different
parts of test cases in this test session. The order of test cases should
always match.
Spirent Landslide test types involved: "SGW_Node", "SGW_Nodal".
Test case actions sequence:
- create default bearers (as per value of "Sessions" key) with
specified rate (session profile key "StartRate")
- send traffic flow(s) (pre-configured in traffic profile) for a number
of seconds (specified in session profile key "duration")
- remove N default bearers with specified rate (session profile key
"DisconnectRate")
Parameters with ALL_CAPS values are placeholders.
User should replace them with their own condifuration.
Session profile file placeholders do not need to be replaced as long as
these parameters are overriden in other files (e.g. pod, test case).
Test results are dispatched according to runner configuration options.
For fully emulated test runs like this one, best suited runner is "Search"
type. In case of testing against real EPC VNFs, user could prefer
different runner type.
JIRA: YARDSTICK-1348
Change-Id: I5caf4878fb212b38d4148a297c5dba03b8ab98a8
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
These files are templates of Spirent Landslide data message flow (DMF)
representing traffic profile of one or multiple traffic flows.
Template files should not be edited directly. Instead, their parameters
could be overriden in test case YAML file, in section "dmf".
JIRA: YARDSTICK-1359
Change-Id: I4980a784a78ca870c18457227248e6e2ac0b8eda
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
|
|
make samples/fio.yaml to support both Openstack and K8s
with context_type specified. It defaultly use Heat context, if
for k8s,
yardstick -d task start samples/fio.yaml --task-args
'{"context_type": "Kubernetes"}'
JIRA: YARDSTICK-1309
Change-Id: I2b0d61cf2f197ec8c60bda0ab4ff51594709f482
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
make samples/lmbench.yaml to support both Openstack and K8s
with context_type specified. It defaultly use Heat context, if
for k8s,
yardstick -d task start samples/lmbench.yaml --task-args
'{"context_type": "Kubernetes"}'
JIRA: YARDSTICK-1310
Change-Id: Ifa542e830fb5ab7823bd4f994ab5d7a8e8a5b415
Signed-off-by: rexlee8776 <limingjiang@huawei.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>
|
|
|
|
|
|
Add source and destination seed value in IXIA RFC2544 traffic profile.
The default value for both parameters is 1.
JIRA: YARDSTICK-1401
Change-Id: I3351194c8be9ac42cbf5655996d50b9b69884c72
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
JIRA: YARDSTICK-1380
Change-Id: I2163eeb9ab17e4f0216ddaed688e78acdf51a1ff
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
|
|
|
|
Because of performance issues in TRex due to the extra power needed to
retrieve the latency statistics, this parameter will be optional and disabled
by default.
JIRA: YARDSTICK-1388
Change-Id: I07c0ec7bef86fd438d078cbd6748b98bc8cc0b37
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
Make sercurity group can be configured via the context.
The format would be:
context:
name: demo
image: yardstick-image
flavor: yardstick-flavor
user: ubuntu
security_group:
rules:
- remote_ip_prefix: "0.0.0.0/0"
protocol: "tcp"
port_range_min: 1
port_range_max: 65535
- remote_ip_prefix: "0.0.0.0/0"
protocol: "udp"
port_range_min: 1
port_range_max: 65535
- remote_ip_prefix: "0.0.0.0/0"
protocol: "icmp"
JIRA: YARDSTICK-1360
Change-Id: I00c45767ee2d70b790590e824599d5a4c274bced
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Changes made in test cases for trex TG files to be able to run tests
for standalone setup (OVS-DPDK/SRIOV).
- tg__0: trafficgen_1
Changes to improve templates for tc_trex:
- flavor: images: changed to default name: yardstick-nsb-image.img
- default path for files under contexts section
- RAM size
JIRA: YARDSTICK-1368
Change-Id: Ida85de219acd566840de1a94975b8050c7f59b9b
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
Added IP random range `seed` configuration option into IXIA
traffic profile.
JIRA: YARDSTICK-1364
Change-Id: Ic050b6cc48ea75ac6d0470bf7ec1b188649811e1
Signed-off-by: Sosyak, Myronx <myronx.sosyak@intel.com>
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@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>
|
|
- Implemented handling of UDP source and destination ports from
IXIA traffic profile.
- UDP ports can be defined as a single value or as a random range.
Ports range is configured with two parameters 'fixed_bits' and
'mask_bits'.
- For example '8-48' range definition will create a repeatable
pattern of four values that fall within the range of 8 and 56.
JIRA: YARDSTICK-1363
Change-Id: I0ace722f6be843ea79c3d3f4de22cb8fa5669d4f
Signed-off-by: Myron Sosyak <myronx.sosyak@intel.com>
Signed-off-by: Pshyk Serhiy <serhiyx.pshyk@intel.com>
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
Added pktgen VNF topology, VNF descriptor and traffic profile files.
JIRA: YARDSTICK-1346
Change-Id: Ifb1824edb2dc8db1afa83a53573fb2ed1c2a79ea
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
This patch is supposed to be coordinated with
https://gerrit.opnfv.org/gerrit/59901
to support dpdk scenario for Bottlenecks
JIRA: YARDSTICK-1332
Change-Id: I4ae3d05523d0624d689702cb8eb23be364830de1
Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com>
|
|
The acl_rules.yaml is unused, so renamed it to sample config.
Updated the config with example of possible ACL configuration.
JIRA: YARDSTICK-1304
Change-Id: If0537cf55f4c96f57844caed5bf1c9050647e0d5
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
Now "NSPerf" scenario will inform about the traffic generator PIDs after
setup process. With this information, IterationIPC runner will be able
to receive the messages sent by those traffic generators and control
the main iteration loop.
The following example, using vFW as VNF and OpenStack as context, makes
use of this new runner implementation:
/samples/vnf_samples/nsut/vfw/
tc_heat_rfc2544_ipv4_1rule_1flow_64B_trex_iterationipc.yaml
JIRA: YARDSTICK-1127
Change-Id: I46b1368bc209680b88ff9fb5c3b9beadf6271ac9
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@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>
|
|
|
|
This patch allows user to configure ACL/vFW SampleVNF ACL
via configuration file provided in TC definition. The
Yardstick applies the rules to SampleVNF from specified config
file + rules generated by Yardstick (default rules).
The example of SampleVNF ACL CLI commands generated/applied
by Yardstick can be found at (using default ACL config file):
ACL VNF ACL CLI commands:
acl/tc_heat_rfc2544_ipv4_1rule_1flow_64B_trex.yaml
http://paste.openstack.org/show/723303/
vFW VNF ACL CLI commands:
vfw/tc_heat_rfc2544_ipv4_1rule_1flow_64B_trex.yaml
http://paste.openstack.org/show/723304/
Change-Id: I76a630261a982083b628e3985fc3bec14ca495db
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
|
|
|