Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Added traffic update capability to Ixload TG"
- Added traffic update capability to Ixload TG
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "[docs] Transition to local docs build job."
- [docs] Transition to local docs build job.
Docs builds have transitioned to using local
build jobs. This allows Yardstick docs to be
built and verified locally.
The time taken to build and verify docs in the
gate for new changes should be reduced, as the
docs for each project will be built separately.
This change also allow contributers to test
their docs builds locally, using tox::
tox -e docs
tox -e docs-linkcheck
TODO: Update the dev guide to include new tox
environment
Related: DOCS-191
JIRA: YARDSTICK-1415
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
Change-Id: Ib8bab85475dcd5127a2c41a2d55dce8f8d9da574
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Adds option parameters to TC074"
- Adds option parameters to TC074
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add 4 port topology for agnostic vnf and Ixia tg"
- Add 4 port topology for agnostic vnf and Ixia tg
JIRA: YARDSTICK-1466
Change-Id: I2e4b7f54591489a90c44535a09207de8a46d0e24
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add OvS 2.8.1 support into SA context"
- Add OvS 2.8.1 support into SA context
JIRA: YARDSTICK-1462
Change-Id: I001a173fc728be6e88f5ae6d38c64b740e536ff2
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Configure n_rxq DPDK port option when adding the port"
- Configure n_rxq DPDK port option when adding the port
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Modify handling Ixia traffic profile parameters"
- Modify handling Ixia traffic profile parameters
Modified Ixia traffic profile class to handle all traffic parameters as
optional.
JIRA: YARDSTICK-1456
Change-Id: Ib7ee1728baad0f271dd6a923b94bc686bc9bffc6
Signed-off-by: Oleksandr Naumets <oleksandrx.naumets@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Add IxNextgen API for creating BGP protocol layer
Added functionality to create BGP protocol layer for device group
JIRA: YARDSTICK-1465
Change-Id: Ib18b979ce09589b5eda438f01f4f8845295e4c71
Signed-off-by: Oleksandr Naumets <oleksandrx.naumets@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Update Ixia tg to use new API for traffic model creation
JIRA: YARDSTICK-1464
Change-Id: Ibbced9e0e04e077ec5c23fc15e97308dd11b7004
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Fix influxdb "field type conflict" error"
- Fix influxdb "field type conflict" error
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Fix NSB PROX L3FWD dropping packets"
- Fix NSB PROX L3FWD dropping packets
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "NSB PROX NFVi Test does not stop after reaching expected precision"
- NSB PROX NFVi Test does not stop after reaching expected precision
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Modify IxNextgen API for traffic model configuration
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Update the pinned sampleVNF version
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "SA: Fix private key file name generation issue"
- SA: Fix private key file name generation issue
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "[NSB] Adds support for running "black box" test cases for VNFs"
- [NSB] Adds support for running "black box" test cases for VNFs
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge changes from topics 'YARDSTICK-1354', 'YARDSTICK-1348', '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 vEPC service request test cases
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>
- Add network initiated dedicated bearers creation
Adding related pod file, session profile and testcase file.
JIRA: YARDSTICK-1355
Change-Id: Ic97d59ef3a36ac05c6c369c36f917ae95d18d863
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
- Add UE initiated dedicated bearer creation test
Adding session profile and test case file.
JIRA: YARDSTICK-1353
Change-Id: Iaa98fd8cb3ed243f9ac157089de32fa23ec0e6b4
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
- Add vEPC infrastructure for Landslide TG
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>
- Add vEPC default bearers relocation test case
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>
- Add vEPC default bearers create/delete test case
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>
- Add Spirent Landslide traffic profile templates
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>
- Update LSResourceHelper unittests
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>
- Add Spirent Landslide TG API
New TG class "LandslideTrafficGen" represents an interface to use Spirent
Landslide API to configure and execute vEPC test cases on
hardware/software Spirent environment. For that purpose this class and its
helper classes use Spirent Landslide REST API calls and Landslide TCL API
calls via library module lsapi.py.
Change-Id: Ib6560d5cd2483c6c9f5c95568345ac39bfebbd4d
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
- Added Landslide Resource Helper implementation
Class "LandslideResourceHelper" provides API for operations needed
- to configure Landslide test session
- manage test session execution (start/stop/abort)
- collect measurements during test run
This helper class API is responsible to for configure Landslide test runs:
- create test user
- create test servers (for emulation of specific vEPC blocks)
- create SUTs (actual tested VNFs performing specific vEPC roles)
- create test session (contains actual test cases)
- create DMFs (pre-defined traffic flows in traffic profile)
- operate traffic run execution (start, stop, abort)
- monitor test run status
- collect KPIs on TG side
Some of these features use Landslide REST API.
Other ones use Landslide TCL API.
JIRA: YARDSTICK-1356
Change-Id: I8fc8a7d85301121da465d054b8d38ae09a541c36
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
- Add TclClients for Spirent Landslide TG
Add class "LandslideTclClient" which holds TCL calls wrappers for
operations on the LandSlide TG.
It also introduces several new parameters in
- test case YAML file structure:
* session_profile: YAML file holding a template of Landslide test
session for specific vEPC test scenario
* dmf: test case options member holding traffic flow specific parameters
for designated test scenario, that override ones in traffic_profile
YAML file
* test_cases: test case options member holding parameters specific to
designated vEPC test case, overriding those in session_profile
template file
- pod YAML file structure:
* tas_manager: holds parameters used to connect to Spirent Landslide TAS
* config: list of entries describing Landslide test servers access,
their network interfaces configuration, information of vEPC elements
emulated by specific test server
Class "LandslideProfile" implements access to traffic profile template
from "LandslideResourceHelper" class.
JIRA: YARDSTICK-1356
Change-Id: Ia6428072b1e72025be17c94e5141bd23f7993247
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Add IxNextgen API for creating Vlans configurations
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Fix Yardstick Docker image ARM build
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Cleanup unittests for test_lmbench"
- Cleanup unittests for test_lmbench
unused-arg check was re-enabled after being disabled at a file level.
Changes were made so that the file conforms to our testing conventions.
Change-Id: Ie34a0088258c1aaff6cb0fdf0b86b37920d35bd6
JIRA: YARDSTICK-1384
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Assign IXIA ports in one call instead of one by one
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add UT: ArithmeticRunner exception handling"
- Add UT: ArithmeticRunner exception handling
* Use time.sleep to avoid multiprocessing.Queue broken pipe error.
JIRA: YARDSTICK-1245
Change-Id: I1ef1f8e68a553278996b38c226314c13dd974faa
Signed-off-by: Miikka Koistinen <miikka.koistinen@nokia.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- IXIA traffic mac address is set incorrectly
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Update configure_uwsgi run in baremetal/container"
- Update configure_uwsgi run in baremetal/container
Now "daemonize" prevents from installing Yardstick on baremetal.
Configuring:
"daemonize" in case "container" installation mode;
"logto" in case "baremetal" installation mode;
JIRA: YARDSTICK-1395
Change-Id: Ie390464db9c0816583edc711ed6526629d091bd3
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Revert "Bugfix: ansible version should be the same both in Dockerfile and requirements.txt""
- Revert "Bugfix: ansible version should be the same both in Dockerfile and requirements.txt"
This reverts commit 662de49b9f6c116d15882aed9e678cd3cf67494b.
JIRA: YARDSTICK-1411
Change-Id: Id277aa8711c9ff77e085d26c90546eecc3490535
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Create a sample fio test case base on kubernetes"
- Create a sample fio test case base on kubernetes
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Create a sample lmbench test case base on kubernetes"
- Create a sample lmbench test case base on kubernetes
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "tc046 kill keystone process condition incorrect - dovetail"
- tc046 kill keystone process condition incorrect - dovetail
Change-Id: If01abfd5a99b4cea74f835e258f3a982af9446cd
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add IxNextgen API for creating PPPoX configurations"
- Add IxNextgen API for creating PPPoX configurations
New IxNextgen API allows to perform the following configurations on IxNetwork:
- add topology
- add device group to topology
- add ethernet protocol layer to device group
- add ipv4 protocol layer to device group
- add pppox protocol layer to device group
JIRA: YARDSTICK-1408
Change-Id: Icf5bb5f24784cf2c167c515b04c81471ac425e38
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add container pull option to install.yaml"
- Add container pull option to install.yaml
Supported Yardstick installation modes in yardstick.yaml: baremetal
and container. First is used to install Yardstick on baremetal,
another is used during docker build to install Yardstick in container.
Added third option: 'container pull': to pull docker image
(opnfv/yardstick) from Docker hub and start container.
JIRA: YARDSTICK-1392
Change-Id: I4158de3eb6fcbe0018a15fdda89a3e3ab29c26bb
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add k8s scenario test suite in Gambia"
- Add k8s scenario test suite in Gambia
JIRA: YARDSTICK-1410
Change-Id: I23b4c0bcfa9aa431e259930a41d4171ff5b4e8a1
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Fix CLI argument handling in nsb_setup.sh
CLI argument $1 was used for both admin-openrc file with OpenStack
credentials and Yardstick Docker image, so obviously one of them would
be wrong, and NSB setup would fail at some point.
Historically, admin-openrc could be supplied as CLI argument $1, but
change https://gerrit.opnfv.org/gerrit/56493 broke it, which means
specifying Yardstick Docker image as CLI argument never worked.
This fix implements support for the following CLI options:
-o openrc Specify admin-openrc file with OpenStack credentials
-i image Specify Yardstick Docker image
-h Provide usage information
For backward compatibility reasons, admin-openrc file can be supplied
either with the -o option, or as a CLI argument.
JIRA: YARDSTICK-1137
Change-Id: I3e9904970560468c24b21738203bc67b7591f9e4
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Merge latest changes to Dashboard from L2FWD to L3FWD dashboard"
- Merge latest changes to Dashboard from L2FWD to L3FWD dashboard
Come changes re: Status == "Result" and Status == "Success" and
L3FWD changes onto latest L3FWD Dashboard
Change-Id: I62d0cfc30167085ad5efe348ab118f1defbc4901
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "NSB NFVi PROX Missing VNF Statistics for CPU Utilization"
- NSB NFVi PROX Missing VNF Statistics for CPU Utilization
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- TRex IMIX data must return percentage value
Function "_create_imix_data" must return the weight in percentage, not in
absolute value.
JIRA: YARDSTICK-1406
Change-Id: I3bc409bab17ae5778a6783f4319699009a5437fa
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Adopt infra_deploy to spawn VM on LTS Ubuntu 18"
- Adopt infra_deploy to spawn VM on LTS Ubuntu 18
Add possibility ro reuse infra_deploy.yaml to spawn VMs on jump host,
depending on jump host Ubuntu version: either 16 or 18.
JIRA: YARDSTICK-1396
Change-Id: Id0682c03098e611fe3a51cbd24d8ff2dda7c552a
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add source and destination seed value in IXIA RFC2544"
- Add source and destination seed value in IXIA RFC2544
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Assign static IP to VM for standalone context"
- Assign static IP to VM for standalone context
During VM spawning IP address should be assigned by DHCP server in
the local network. Sometimes DHCP server is not capable to assign IP
address. So, need to add static IP address.
JIRA: YARDSTICK-1402
Change-Id: Ie59c340eb88eddcaff043496fc20aa48b49205ec
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Updated documentation for stanalone context
Added details about hosts configurations in order to run tests for
standalone context.
Changes made to '13-nsb-installation.rst'.
JIRA: YARDSTICK-1402
Change-Id: I4e3304065343014a80b85fc712cdde3ca62d8b2e
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Bugfix: ansible version should be the same both in Dockerfile and requirements.txt
Because Dockerfile is using ansible script to install yardstick requirements.
Or it may lead to exception when installing Yardstick.
Change-Id: Ia83cf76675a7f3f1d0aa5c311e7b72be5c7ca5c3
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Bugfix: openstack router list broken in Yardstick container - dovetail"
- Bugfix: openstack router list broken in Yardstick container - dovetail
Dependancy of python-openstackclient is not constrained.
This patch specify openstacksdk and openstackclient's version according to [1].
This patch apply for bugfix and need to backported to fraser stable branch.
Continual work need to be done in Gambia according to YARDSTICK-1398.
[1]
https://github.com/openstack/requirements/blob/stable/pike/upper-constraints.txt
JIRA: DOVETAIL-728
Change-Id: I57c718e192699ac322150458d18508b06c93d22b
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Change tc_trex files to execute standalone tests"
- Change tc_trex files to execute standalone tests
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Make TRex IMIX traffic mode configurable"
- Make TRex IMIX traffic mode configurable
Enable TRex IMIX generation using two modes:
- Distribution in packages.
- Distribution in byes.
The default one will be distribution in packages, like the default
one in IxNetwork.
JIRA: YARDSTICK-1397
Change-Id: I86b2527968496218b0515349fc0a2680a84261e5
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- ping bottlenecks failed when security group rule do not support ipv6 - dovetail
JIRA: YARDSTICK-1380
Change-Id: I2163eeb9ab17e4f0216ddaed688e78acdf51a1ff
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Make security group configurable - dovetail"
- Make security group configurable - dovetail
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>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Fix setting `flow` configuration in TC yaml"
- Fix setting `flow` configuration in TC yaml
The `flow` configuration is not applied to the traffic
profile if `seed` or `count` option is missing in the
TC definition.
- Fix `seed` backward compatibility.
JIRA: YARDSTICK-1383
Change-Id: Ic874fb2be1c13009f94eb3a80194bfe81d7a923b
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Fix issues with 'Success_' stats reported by ProxBinSearchProfile"
- Fix issues with 'Success_' stats reported by ProxBinSearchProfile
List of changes:
- Added 'Status' field to indicate status of each search iteration.
Possible values are 'Success', 'Failure', 'Result'.
- Removed reporting of duplicated stats with 'Success_' prefix.
Instead 'Status' field is set to 'Success'
- Removed reporting of duplicated stats with 'Result_' prefix.
Instead 'Status' field is set to 'Result'
- Updated Prox_BM_L2FWD-4Port_MultiSize-1518452496550.json dashboard
to query success and result status by 'Status' field value.
JIRA: YARDSTICK-1386
Change-Id: I9a21a102af6cb4db137e805011b5d81c4943d77b
Signed-off-by: Serhiy Pshyk <serhiyx.pshyk@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Runners crash on test startup."
- Runners crash on test startup.
JIRA: YARDSTICK-1393
The problem resides in this traffic generator class: this class
is inheriting from SampleVNFTrafficGen and overriding the
__init__ method but is NOT calling the parent class __init__
one.
Change-Id: I206a66e361a3e2eb50bb5fa01ddadae25b4a9f54
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Provide access to VM in Standalone context"
- Provide access to VM in Standalone context
Add possibility to access VM with SampleVNF image, which is spawned on
baremetal server using password or key pairs (provided or generated).
Changes provided for OVS-DPDK and SRIOV cases.
JIRA: YARDSTICK-1260
Change-Id: I89cf17dc83f02abe23d206b24b9d0ec1298d3231
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Provide average latency results in IXIA KPIs"
- Provide average latency results in IXIA KPIs
IXIA KPIs will provide an average value of all port latency values:
max, min and avg.
JIRA: YARDSTICK-1394
Change-Id: Ib7c7b5300e8343a1af0a20cb4e49c0bd669c1143
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|