Age | Commit message (Collapse) | Author | Files | Lines |
|
- Fixed ansible scripts to generate multiport baremetal TCs
for vACL/vFW/vCGNAPT.
- Added scale out correlated traffic TCs for vACL/vFW/vCGNAPT.
JIRA: YARDSTICK-1347
Change-Id: I3f6232dab1a45c70d1e22fbe2c7b0c3cb4773a4e
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@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>
|
|
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 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 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>
|
|
|
|
Add IxNetwork python package to the requirements list.
This module is needed for the "NSPerf" scenarios using IXIA as traffic
generator, when IxNetwork is the program used to handle the IXIA
generator.
The latest version of this module is 8.40.1124.9 [1]. The license type
is MIT.
[1] https://pypi.python.org/pypi/ixnetwork
JIRA: YARDSTICK-1106
Change-Id: I279933c95994f5120930256a104c4192a0b9900d
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
OpenStack deployment using Kolla installer for all-in-one mode and
multinode inside VMs which are already created. Two types of OpenStack
nodes are supported as input in sample files, like
infra_deploy_two.yaml.sample: controller and compute.
JIRA: YARDSTICK-1078
Change-Id: I51616a7a17ac565a01ec6da57b589290237d18ee
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
JIRA: YARDSTICK-1097
Change-Id: If116174c562bc08c0b7602324599bc85d8c60be0
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
|
|
Fuel except Controller and Compute nodes
it deploys an ODL node in noHA and HA deployment
and also a Gateway node in a noHA deployment.
So it is essential to describe them in Fuel's pod.
JIRA: YARDSTICK-1050
Change-Id: Iee6c25c5b2e2e4e661ceb0591bf2437f7f7fa7f8
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Add option to the config file for default network.
Check to see if 1 default network is defined.
Enable nat on all defined networks.
Add default gateway to VM
JIRA: YARDSTICK-1016
Change-Id: Ie943a7c7b4f1a9673774cf8fedaba0af352cd7f4
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
Using xml files deploy the VM's using the virt plugin.
This code generates the user-data network-config meta-data
and the vm's xml. It also deploys the vm
JIRA: YARDSTICK-963
Change-Id: I97f2d20d0ab75a4444b8b8e6fb65e9e463870af7
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
Create host networking configuration based on the input
configuration file. To define the networks using libvirt,
a temporary XML file is generated for each network.
JIRA: YARDSTICK-962
Change-Id: I24d1c4d2f2e62884675599deb7db255862283ea4
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
Just in case anyone uses this file for testing.
Change-Id: Iff0489f839f3985e43ac31d2a89147e5f16c59e9
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
|
|
The current HA testcases failed on fuel baremetal installer
with reason "SSHTimeout". This is due to incorrect ssh login
info in the pod config file. The change is to by running
'prepare_env.sh' script to
- read env vars 'USER_NAME' and 'SSH_KEY'
- replace the 'node_username' to env var 'USER_NAME'
- replace the "node_keyfile" to env var 'SSH_KEY'
JIRA: ARMBAND-317
Change-Id: I0239892f447ae99ab4025eedcd133e1b6f04e5a5
Signed-off-by: ting wu <ting.wu@enea.com>
|
|
Draft for env requirements reading and validation
Script can be run from tools/virt_ci_rampup.sh. First requirement file is
parsed/stored. This file must be created in ahead and named as
'infra_deploy.yaml'. Then separate ansible role is used to validate
resources. Ansible-role fails if there is not enough resources on the host
for cpu, ram, disk space.
JIRA: YARDSTICK-945
Change-Id: I86cd4bdc963de3aa51392fc73a239cbd426bc64a
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
Delete zte pod info in yardstick/etc/yardstick/nodes.
Change-Id: Ie22fd9fa4b84529f0b2a7d113776d3559106e67a
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I3b79d33dba5cc559634122a135ff469f054214fc
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
|
|
- trex
- ixia
- ixia correlated
Change-Id: I7d1414227c27c2bb03454eac94592e07c434f070
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I3d1a491e4c0f0554a861d9bb24fbd0ac94835759
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
switch from hardcoded path to dynamic path
based on bin_path
also enable proxy for install_collectd
add barometer settings for virt and ovs_stats
Change-Id: Id138aef548332a3e3fcb3963b746e7c9f10c0948
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
|
|
|
|
- vFW
- vCGNAPT
- vACL
- UDP Replay
- vPE (Only OVS supported)
Change-Id: Idbc4d1d6bc1283e40d2fcb9457a871a9198ad147
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I2755b596068545c1a3a672ceff47d814a44ae050
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I7da2d5bcd7c58c669e28a7271e4c6848c003e84a
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
2 - node setup:
- Traffic generator starts new stream on both uplink and downlink
This patch addes amsible scripts to enable scale_out testcases
- vfw
Change-Id: I0340636bce3e74cd6175f728b9e7e014a4eb2fd5
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
allow manually adding collectd nodes using Node context.
if a node is present with a collectd config dict then
we can create a ResourceProfile object for it
and connect to collectd.
example
nodes:
-
name: compute_0
role: Compute
ip: 1.1.1.1
user: root
password: r00t
collectd:
interval: 5
plugins:
ovs_stats: {}
Change-Id: Ie0c00fdb58373206071daa1fb13faf175c4313e0
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
management route ip is not common in most SUTs, so it should
be removed.
also huawei pod1 ipmi info should updated so this test case
can be added into ci later
Change-Id: I3a29c59c473ee7087d4d61753ffc955b061571fb
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
- path should be defined via TREX_CLIENT_LIB environmental variable e.g. TREX_CLIENT_LIB=/opt/trex_client/stl
- refactored unit tests
Change-Id: I18767e48daf774432c010f1b88d18a4f0ee4e156
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Traceback (most recent call last):
File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/cmd/commands/task.py", line 54, in do_start
result = Task().start(param, **kwargs)
File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/core/task.py", line 148, in start
self._do_output(output_config, result)
File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/core/task.py", line 227, in _do_output
dispatchers = DispatcherBase.get(output_config)
File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/dispatcher/base.py", line 46, in get
for out_type in config['DEFAULT']['dispatcher']]
File "/opt/nsb_bin/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/dispatcher/base.py", line 38, in get_cls
raise RuntimeError("No such dispatcher_type %s" % dispatcher_type)
RuntimeError: No such dispatcher_type Http # setup multiple dipatcher with comma deperted e.g. file
Change-Id: I497d0d9ce7fdb7ea2913af6ebeb4bb9008344fed
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I09bcb3f2c4b945283070d442589d3bf00468abbc
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
JIRA: YARDSTICK-684
This patch adds the support to enable multi-dispatcher of result.
e.g.
[DEFAULT]
debug = False
dispatcher = file, http
Change-Id: Id0e1a1bba14edd899fcf5b275be1f0a091b6db77
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: YARDSTICK-174
This live migration test case is based on share storage, default share
storage is enabled.
This test case will do some config work. And do live migration and
calculate the migration time and downtime.
Change-Id: I6601601edebdd0ac6434ba632b1eba9e9bd4fda0
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-647
Change-Id: Idc2a87d20a631c37f151cc945de155ef8855e9c3
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
JIRA: YARDSTICK-620
Currently we recommend using docker to run yardstick.
And it is hard to use virtualenv to install yardstick.
So I modify install.sh in yardstick root path.
It will support using virtualenv to install yardstick(including API) in
linux.
In this patch, I make yardstick support read yardstick configuration
have priority over constants.
Change-Id: I9ea1241b228532a6497451e6c8f232173ddb783e
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
JIRA: YARDSTICK-487
Change-Id:I23dabcf6b4b7d49b8eb0f18778cddd50a1195a05
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
JIRA: YARDSTICK-474
Currently, I use file.write() method to write config in yardstick.conf.
But it is not recommended.
So I change to use ConfigParser to write config in yardstick.conf
Change-Id: Ia789cf09296afd5d1507bcf99f165378bf87c591
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-364
Change-Id: I8c460064c058f77971140f69689ba638179f89d9
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-356
Change-Id: I1ef7c665f7baa15f61e2bca8c0f0d0e6d0f77248
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Change-Id: I03101df2aeeebfc7b5f65a8c21c0a462d819e57f
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Due to lacking support for floating IPs in ODL VPNService,
the default test cases fail.
The replaced test cases are:
opnfv_yardstick_tc043.yaml(Node ping test)
opnfv_yardstick_tc019.yaml(Node HA test)
Change-Id: Ib829430e00488697dc7543ea7143026dc68ff834
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: Yardstick-313
Change-Id: I7dc908e55e9c3c891a525a3285c6ae42a1bcae48
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|