Age | Commit message (Collapse) | Author | Files | Lines |
|
intel_pmu needs to download a config file based on the
CPU model. When generating VNF images we don't have
access to the actual vCPU that will be used, so we
can't predownload. This code was meant to be a fix
for that by downloading all the configs and then
selecting one that matched the vCPU.
However we have license issues with intel_pmu enven GPLv2 code,
so remove it for now.
Change-Id: I5257ff7c4ddc1d40537dadb29efa40d1d68cb852
Signed-off-by: Ross Brattain <ross.b.brattain@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>
|
|
Changed how "test_cli_scenario" tests check the presence
of a string.
Fixed "test_scenario_show_Lmbench": logic in [1] was incorrectly
assigning an string value instead of the result of the "in"
clause.
[1] https://github.com/opnfv/yardstick/blob/stable/euphrates/tests/functional/test_cli_scenario.py#L35-L36
Change-Id: I71fceabad972e4c0d9e78cbfeb85dcd6a5ae4bda
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
Created two new class functions for Scenario class:
* "get_description" will return the first line of the docstring,
if exists.
* "get_scenario_type" will return the value of "__scenario_type__"
variable.
Change-Id: I8e3b47e33e0bae101b874c3975bb9c383397d188
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@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>
|
|
by default ConfigParser will lowercase everything,
unless you override optionxform.
also sort key value in inventory line for consistency
https://docs.python.org/3/library/configparser.html#configparser.ConfigParser.optionxform
Transforms the option name option as found in an input file or as passed in by
client code to the form that should be used in the internal structures. The
default implementation returns a lower-case version of option; subclasses may
override this or client code can set an attribute of this name on instances to
affect this behavior.
You don’t need to subclass the parser to use this method, you can also set it
on an instance, to a function that takes a string argument and returns a
string. Setting it to str, for example, would make option names case sensitive:
cfgparser = ConfigParser()
cfgparser.optionxform = str
Note that when reading configuration files, whitespace around the option names
is stripped before optionxform() is called.
YARDSTICK-833
Change-Id: Ia1810b0c77922d84e11c9e538540b38816338593
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Change-Id: Id8aa734fee431d90cbdc1e0eb2173784ada822fe
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
The links to the docs in README were pointing to Colorodo documentation.
For master, this should not be pinned to a particular release, but
should show the most recent docs at all times.
Change-Id: I3186ea0dbc5105812407a0f87e02d99899a951a0
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
Users would like to ensure placement of VMs on specific compute nodes so
that the measurements are meaningful. Examples: Measure network
performance in different scenarios (VMs in same host, in different
hosts, across fabric, across tenants)
Example:
context:
name: yardstick
placement_groups:
pgrp1:
policy: "availability"
servers:
tg_0:
floating_ip: true
placement: "pgrp1"
availability_zone: "zone2"
vnf_0:
floating_ip: true
placement: "pgrp1"
availability_zone: "zone1"
Change-Id: I28a757c25ae3f5b3571ab3edd82d51ceba32c302
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
We don't really know what core we are going to use for the
VNF before we generate the MultiPortConfig, so these
methods are incorrect.
We may need some more advanced method to validate
the vCPU topology, but that will probably happen
in the MultiPortConfig
Change-Id: Ifee7ae4589ce0fce67771fb8d8b8dce0a0f06409
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
This brings it to parity with its non-Ixia counterpart (ipv4_throughput.yaml).
Change-Id: I4c91d1ae507c7b5e0a23dcf49606b16891b400bd
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: YARDSTICK-831
Change-Id: I587c486572f439952b8a31da664d1e2c1fb8dc27
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
We used to try to probe all the cores that the VNF was using
and only dump CPU stats for those cores.
We can't really detect those core accurately and we would rather
dump all the core information and let influxdb and grafana filter
the information.
We do end up with excessive KPI output, especially on systems with 88
cores, but this is manageable.
The core logic was partially removed, this finishes the removal.
Change-Id: I5cbb694fd982519e2df54db49a21ed5948e13537
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
This patch is used to remove the livemigration testcase result loaded
to json as there is no dashboard implemented for the testcase
Change-Id: I7a9589a0bbc5f2a28587c2878da042fc50af18e0
Signed-off-by: Navya Bathula <navyax.bathula@intel.com>
|
|
Change-Id: I0380deec3e41a6dc02571ed9c4fa16e304f7f85e
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-73
add a new chapter about how to work with test case, now just add three sub chapter,
sample test case, release test case, test case description file, will update more for
how to write a new test case.
Change-Id: I44906917e76ad6d4890f345c963b9e4440f6be39
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
- concurrency
- connections/second
- throughput
Change-Id: Idb977462952fba2e6a9684e916dfeca810f1ee94
Signed-off-by: Jennifer Li <jennifer.li@intel.com>
|
|
rename xe0, xe1 to uplink_0, downlink_0
enumerate tgs/vnfs starting from 0.
add disable_dhcp
Change-Id: Ia4f08b3ad5ab298192c249d04b10a6efbe4f210e
Signed-off-by: Ross Brattain <ross.b.brattain@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>
|
|
|
|
|
|
Change-Id: I2f98b75e9bbcd3d0cd4666c097a3280dd89eb02a
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Update:
Added Prox NSB test case documentation
Change-Id: Ia2f47d823581fc7f193d3123f080dd87f29d4b99
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
Change-Id: I09bc55e296d2c641f10819972ec0d48a289432b8
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
Change-Id: Ie5ff6fe4f867ce68a33a3a857d8d051ba0020395
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
JIRA: YARDSTICK-500
Change-Id: I6eef884ef6262abe49fc13bc353ca14a72a5b648
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
Signed-off-by: Martin Banszel <martinx.banszel@intel.com>
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
|
|
|
|
|
|
Removed the abs function which can potentially mask
negative dropped packets.
Dropped packets in Prox workload VNF = rx_packets - tx_packets
Change-Id: I510a351e899cdf9a1f366d632b9f0528b1d9dcce
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
|
|
|
|
|
|
The opnfv_os-odl-fdio_dvr-noha_daily.yaml test suite file is wrongly put in Yardstick root directory,
this patch moves this file to the 'test_suites' directory.
Change-Id: Ib3f75845c7af658dc6f96ac2de737cfbd1faf15a
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
Change-Id: If6b70791213099d53c82993bd22ac9eed6000c32
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: I7e437612ca52b75b71e38962a84d0dcdb453d5dd
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
|
|
Change-Id: I6bd8a87f70954f288975e3e73e3cfbd36ae561dc
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
Change-Id: I9d246828790467c2a57ba410826ee9751fff89c5
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
From some reason Heat/Neutron is now creating
interfaces such that xe0 and xe1 are swapped.
xe0 fa:16:3e:38:c7:66 0000:00:05.0
xe1 fa:16:3e:2f:f3:e2 0000:00:03.0
this causes the DPDK port numbering to be swapped.
xe0 is DPDK port 1 because it has higher PCI address
xe1 is DPDK port 0 because it has lower PCI address.
The VNF is configured correctly because it uses DPDK port numbers,
whereas TRex was using interface list ordering.
Modify trex_cfg.yaml to use DPDK port ordering. This also
requires running generate_cfg() after setup() in instantiate()
+------------------------------------+-------------------+------------------------------+--------+
| Name | MAC Address | Fixed IP Addresses | Status |
+------------------------------------+-------------------+------------------------------+--------+
| vnf_0.yardstick-af5ccb47-xe0-port | fa:16:3e:66:a5:e4 | ip_address='10.1.0.7', | ACTIVE |
| vnf_0.yardstick-af5ccb47-mgmt-port | fa:16:3e:fa:98:fe | ip_address='10.0.1.10', | ACTIVE |
| tg_0.yardstick-af5ccb47-xe1-port | fa:16:3e:2f:f3:e2 | ip_address='10.1.1.9', | ACTIVE |
| vnf_0.yardstick-af5ccb47-xe1-port | fa:16:3e:f3:1d:f5 | ip_address='10.1.1.4', | ACTIVE |
| | fa:16:3e:e3:8c:65 | ip_address='10.0.1.1', | ACTIVE |
| | fa:16:3e:ff:d1:b7 | ip_address='11.191.14.110', | N/A |
| tg_0.yardstick-af5ccb47-xe0-port | fa:16:3e:38:c7:66 | ip_address='10.1.0.8', | ACTIVE |
| | fa:16:3e:ff:53:5f | ip_address='11.191.14.101', | DOWN |
| | fa:16:3e:23:5d:2c | ip_address='10.0.1.2', | ACTIVE |
| tg_0.yardstick-af5ccb47-mgmt-port | fa:16:3e:7a:df:4e | ip_address='10.0.1.5', | ACTIVE |
| | fa:16:3e:22:65:36 | ip_address='11.191.14.109', | N/A |
+------------------------------------+-------------------+------------------------------+--------+
/sys/devices/pci0000:00/0000:00:03.0/virtio0/net/ens3/address:fa:16:3e:2f:f3:e2
/sys/devices/pci0000:00/0000:00:05.0/virtio2/net/ens5/address:fa:16:3e:38:c7:66
Change-Id: Iaef2c7d9a5af7f45bd805a8ad6ee545ce0495cb1
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
RFC2544 tests should include the following frame sizes:
9.1 Frame sizes to be used on Ethernet
64, 128, 256, 512, 1024, 1280, 1518
Change-Id: I6ab9cccf2bb3b2678f50da157a9a49c0d9564cbd
Signed-off-by: Dino Simeon Madarang <dinox.madarang@intel.com>
Reviewed-by: Alain Jebara <alain.jebara@intel.com>
Reviewed-by: Deepak S <deepak.s@linux.intel.com>
Reviewed-by: Ross Brattain <ross.b.brattain@intel.com>
Reviewed-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
|
|
|
|
|
|
|