aboutsummaryrefslogtreecommitdiffstats
path: root/etc
AgeCommit message (Collapse)AuthorFilesLines
2019-03-15Add VNF descriptor for vIMS testcasetreyad2-0/+82
This patch defines: - vims-topology.yaml --> Define topology - tc_vims_baremetal_sipp.yaml,tc_vims_heat_sipp.yaml --> test cases in yardstick format (scenarios/context) JIRA: YARDSTICK-1443 Change-Id: Id0253c9fe7e0b65cdb1d57f853b229f7d628c84f Signed-off-by: treyad <treyad@viosoft.com>
2019-02-21Unify TG and VNF names in infrastructure filesOrest Voznyy9-19/+17
Update naming in related files, i.e. pod, docs, docstrings. Rename TGs and VNFs to follow a single naming convention, for all VNFs: name: trafficgen_0 role: tg__0 name: vnf_0 role: vnf__0 JIRA: YARDSTICK-1578 Change-Id: I7596b915939f242349a99721b6088ae738dd277f Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
2019-01-17Add NSB test descriptors for vIPSEC testcasetreyad1-0/+84
JIRA: YARDSTICK-1452 Change-Id: Id9731ab52da76efb553a89629ca4639ff3c09650 Signed-off-by: treyad <treyad@viosoft.com>
2018-11-13Fix multiport/scale-out baremetal ansible scriptsMytnyk, Volodymyr1-0/+37
- 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>
2018-09-15Add network initiated dedicated bearers creationOrest Voznyy1-0/+164
Adding related pod file, session profile and testcase file. JIRA: YARDSTICK-1355 Change-Id: Ic97d59ef3a36ac05c6c369c36f917ae95d18d863 Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
2018-09-15Add vEPC infrastructure for Landslide TGOrest Voznyy1-0/+37
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>
2018-09-15Add vEPC default bearers create/delete test caseOrest Voznyy1-0/+130
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>
2018-09-05Add TclClients for Spirent Landslide TGOrest Voznyy1-0/+2
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>
2018-05-08Merge "Add pod.yaml files for Apex"Ross Brattain2-0/+86
2018-05-04Add IxNetwork API Python Binding packageRodolfo Alonso Hernandez3-4/+1
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>
2018-04-26OpenStack deployment using kollaStepan Andrushko3-15/+180
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>
2018-04-20Add pod.yaml files for ApexDimitrios Markou2-0/+86
JIRA: YARDSTICK-1097 Change-Id: If116174c562bc08c0b7602324599bc85d8c60be0 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
2018-03-12Merge "Update the fuel pod.yaml"Ross Brattain1-0/+13
2018-03-08Update the fuel pod.yamlDimitrios Markou1-0/+13
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>
2018-03-06Allow VMs to access internetJohn O Loughlin1-0/+6
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>
2018-02-12Create host VMs configurationJohn O Loughlin1-2/+2
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>
2018-02-12Create host networking configurationJohn O Loughlin1-1/+2
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>
2018-02-07Add a missing colon in the sample configRodolfo Alonso Hernandez1-1/+1
Just in case anyone uses this file for testing. Change-Id: Iff0489f839f3985e43ac31d2a89147e5f16c59e9 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-01-31Merge "Modify fuel_baremetal pod config file"Ross Brattain1-10/+10
2018-01-26Modify fuel_baremetal pod config fileting wu1-10/+10
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>
2018-01-24Check RS for virtualized OpenStack/YardstickStepan Andrushko1-0/+34
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>
2018-01-04delete obsoleted zte pod infozhihui wu1-50/+0
Delete zte pod info in yardstick/etc/yardstick/nodes. Change-Id: Ie22fd9fa4b84529f0b2a7d113776d3559106e67a Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2017-10-18Adding sample trex exampleDeepak S1-0/+38
Change-Id: I3b79d33dba5cc559634122a135ff469f054214fc Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-17Merge "fix invalid chracters in ansible scripts"Ross Brattain1-9/+9
2017-10-15Adding sample multi-port ansible scriptDeepak S1-0/+37
- trex - ixia - ixia correlated Change-Id: I7d1414227c27c2bb03454eac94592e07c434f070 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-15fix invalid chracters in ansible scriptsDeepak S1-9/+9
Change-Id: I3d1a491e4c0f0554a861d9bb24fbd0ac94835759 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-12collectd: set intel_pmu events path and OVS socket pathRoss Brattain1-2/+6
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>
2017-10-05Merge "Adding scale out templates for ovs_dpdk/sriov using 2 node setup"Ross Brattain2-0/+44
2017-10-05Merge "Adding 2 node ixia generic scale-out test case generation"Ross Brattain1-0/+54
2017-10-05Merge "Adding auto generate scale-out support for correlated traffic"Ross Brattain1-0/+77
2017-10-03Adding sample testcases to run on standalone contextDeepak S6-0/+165
- vFW - vCGNAPT - vACL - UDP Replay - vPE (Only OVS supported) Change-Id: Idbc4d1d6bc1283e40d2fcb9457a871a9198ad147 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-03Adding auto generate scale-out support for correlated trafficDeepak S1-0/+77
Change-Id: I2755b596068545c1a3a672ceff47d814a44ae050 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-03Adding 2 node ixia generic scale-out test case generationDeepak S1-0/+54
Change-Id: I7da2d5bcd7c58c669e28a7271e4c6848c003e84a Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-10-03Adding scale out templates for ovs_dpdk/sriov using 2 node setupDeepak S2-0/+44
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>
2017-10-02add collectd resource node capabilityRoss Brattain1-0/+25
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>
2017-09-29bugfix: tc054 default value is wrongrexlee87761-0/+22
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>
2017-08-24Standardized TRex client library pathMaciej Skrocki1-0/+1
- 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>
2017-08-12Move the comment above the config parameter line to avoid the expectionDeepak S1-1/+2
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>
2017-08-08IXIA traffic generatorDeepak S1-0/+90
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>
2017-07-28Merge "Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migration"Rex Lee1-0/+5
2017-07-27Adding support for multi-dispatcherDeepak S1-1/+1
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>
2017-07-26Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migrationchenjiankun1-0/+5
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>
2017-06-07Fix configuration error in TC025tjuyinkanglin1-0/+50
JIRA: YARDSTICK-647 Change-Id: Idc2a87d20a631c37f151cc945de155ef8855e9c3 Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
2017-04-01Yardstick virtualenv supportchenjiankun1-0/+33
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>
2017-02-17Update missing license headersDeepak S5-0/+40
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-01-19Adding sample yardstick.conf & pod files to help describe the topologyDeepak S2-0/+82
JIRA: YARDSTICK-487 Change-Id:I23dabcf6b4b7d49b8eb0f18778cddd50a1195a05 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2016-12-26Use ConfigParser to write yardstick.confchenjiankun1-13/+12
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>
2016-10-10Bugfix: no pod.yaml file error when run test case not in the root pathchenjiankun1-0/+0
JIRA: YARDSTICK-364 Change-Id: I8c460064c058f77971140f69689ba638179f89d9 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-09-21get rid of private key in reporexlee87761-27/+0
JIRA: YARDSTICK-356 Change-Id: I1ef7c665f7baa15f61e2bca8c0f0d0e6d0f77248 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-09-05Bugfix: use key_file instead passwork to log onto node in fuel baremetal pod.JingLu51-5/+5
Change-Id: I03101df2aeeebfc7b5f65a8c21c0a462d819e57f Signed-off-by: JingLu5 <lvjing5@huawei.com>