Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
Added new RFC2544 iteration status field into the
testcase result to be able to exctract the best
RX/TX throughput value from each iteration.
The field equal "Success" if the trhoughput value is in the
given drop percentage range and "Failure" otherwise.
JIRA: YARDSTICK-1389
Change-Id: I2fb2ef036b63a0e7bbf3d6c6568d3bdffa488e1f
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
(cherry picked from commit 0ff5b131fa3f93f8d47b46c2f13661c5b88d37a1)
|
|
Added the PROX L3FWD Grafana dashboard with NFVi metrics
collected from barometer collectd container.
The dashboard has template field for HOST/SUT name
to get the collectd metrics from that SUT.
JIRA: YARDSTICK-1412
Update:
- Added table and graphs for TG NFVi metrics
- Added TG and SUT templates as IP address
- Added IPC(instruction per cycles) metric
Change-Id: I1f8971f551df27ad6a16241693527285610fc82d
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
(cherry picked from commit e63084495f47a9f5b5b61b23529792d6898841bb)
|
|
|
|
|
|
|
|
|
|
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>
(cherry picked from commit 31eac948bba5cf442981fdc7b1392992aaef1f15)
|
|
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>
(cherry picked from commit 7bc7bfb1b43e6329bbfc0ed7a7c5554ebcf10c2b)
|
|
|
|
Add option parameters to TC074 to allow the user to specify
volume type, volume count, availability zone, stack name,
and subnet cidr.
JIRA:YARDSTICK-1294
Change-Id: I161f44b5f2c7e70fcfb80a3b916efc34bd06824c
Signed-off-by: Ameed Ashour <Ameed.Ashour.Ext@nokia.com>
(cherry picked from commit 43c28852a9c9abfe7fc66fca0dcc703b468db0cf)
|
|
On some platform, setting n_rxq option on port separately
does not work well and causes issues like port link down,
so changed the logic to set n_rxq DPDK port option during
adding the port to the bridge which help to resolve
the problem.
JIRA: YARDSTICK-1463
Change-Id: Icdb064153a38afd53b835de8742e6fcef08f66bb
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
(cherry picked from commit adcc29e56130f0f047b99528ce72b6f149643da7)
|
|
JIRA: YARDSTICK-1462
Change-Id: I001a173fc728be6e88f5ae6d38c64b740e536ff2
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
(cherry picked from commit ad63af7f42d07cffde73c32727f170973ce5ba46)
|
|
Add automatic update of traffic profile items library name update, as well
as update of session profile Dmf library name, to avoid the need of user
changing it in template files.
Update affected unit tests.
JIRA: YARDSTICK-1474
Change-Id: I18cc8ca99a47da862753329c87d1a560a97f76fa
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
(cherry picked from commit 1fd3806d6a6bac19f3173da4d6cb94cef81fd7f5)
|
|
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>
(cherry picked from commit ae2ceba66519555749c67eefe2170ea716a1411b)
|
|
Changed the way rabbitmq-server user is created. Fix is needed to
collect KPIs from Trex.
JIRA: YARDSTICK-1479
Change-Id: I54369535fdb7af6af76de30f758227736f83db78
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
(cherry picked from commit d06e6da19db545dfcc6fdfdc706b9cccdb75c498)
|
|
The regex is not compatible with pip version 18.
JIRA: INFRA-310
Change-Id: I6eaf1e3fac183f85c277934929e9065efa88d877
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
(cherry picked from commit a4084d27de22c64ecb690369c7bed49175703adf)
|
|
JIRA: YARDSTICK-1464
Change-Id: Ibbced9e0e04e077ec5c23fc15e97308dd11b7004
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
(cherry picked from commit 81ed5cdea4c36d45c6463523c6a0bc38495e544a)
|
|
|
|
|
|
into stable/gambia
|
|
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)
|
|
|
|
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>
(cherry picked from commit 2f4418798a3cf245f863a617410403f226062ac8)
|
|
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>
(cherry picked from commit 7d5ff45a3b793f5e50b4a32b2438ab11fed6c899)
|
|
Changes to IxNextgen API:
- modify API for traffic model configuration so that it can be used
to create/configure different models
- add methods to start and stop protocols on IxNetwork
- add method for getting assigned ports
JIRA: YARDSTICK-1455
Change-Id: I43c10fea9ba83994caf373ceff8b0252a45439b3
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
(cherry picked from commit 7237241a396871d637f9906c1fc93a8587a7b726)
|
|
JIRA: YARDSTICK-1414
Updated the sampleVNF version to the most recent validated commit.
Provided comments on accepted version types and values, and on where
users can find alternative values, in case they want to try something
different than the version recommended and validated for Yardstick/NSB.
Change-Id: I336f96237fcfa8b580c91c787d722d368cc6c015
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
(cherry picked from commit ee5d6413dbcbab40234e47ed3e74b85b704d6493)
|
|
|
|
|
|
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
|
|
In current implementation of Yardstick, SA context uses the
same SSH key file name for each VM created. E.g. the Yardstick
overrides the key file context each time the new VM is created.
As a result, the key file is valid only for last VM created
by Yardstick causing the connection problem for other VMs.
Solution is to generate different key file name for each VM
name separately.
JIRA: YARDSTICK-1436
Change-Id: I22ae2874695736255aa3314654a2cced9338b53d
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
New IxNextgen API allows to configure Vlans(vlan id, priority, tp id)
to Ethernet layer of device group.
JIRA: YARDSTICK-1420
Change-Id: I1c5fe37b5beb11daf1c539933fcad60832553bb9
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
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>
|
|
Soften sed pattern, in order to cope with new contents of
ansible/install.yaml, recently modified by change 61173.
Previous sed pattern does not work anymore against this changed line:
https://gerrit.opnfv.org/gerrit/#/c/61173/4/ansible/install.yaml@39
JIRA: YARDSTICK-1411
Change-Id: I1e1ebd454900252c29263e746470e18e3139e016
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
|
|
Assigning IXIA ports one by one takes more time than
assign all ports by once. Also, assigning ports in
one call resolves the assign port issues caused on
some IXIA chassis versions.
JIRA: YARDSTICK-1425
Change-Id: Ibb08e40ee1a8762573f6752bdd1f583c5a1d9d2a
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
New unit tests have been added to make sure the right
commands are sent to Spirent LS.
This helps to ensure that the correct commands are sent
to Spirent, so that potentially breaking changes can be
flagged.
JIRA: YARDSTICK-1356
Change-Id: I23f452355afcec2705da7d4665a34b178e2ba729
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
IXIA API sets the src/dst mac of the traffic always into
default value. The `srcmac`/`dstmac` is never set in `traffic_param`
map [1]. Instead the src/dst mac is stored in traffic_param[`outer_l2`].
[1] https://gerrit.opnfv.org/gerrit/gitweb?p=yardstick.git;a=blob;f=yardstick/network_services/traffic_profile/ixia_rfc2544.py;h=44bf2eafc7f8cf03ebd2c8520d316358fe1e5fc2;hb=HEAD#l92
JIRA: YARDSTICK-1423
Change-Id: Iabab7a54404b284d3b95bbea6c8624233c138351
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
|