aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-04-24Merge "Add a new runner to test end-to-end fast data path"Rex Lee1-0/+8
2017-04-23Merge "Add SRIOV support"Kubi8-13/+124
2017-04-20Yardstick virtualenv supportchenjiankun5-6/+9
JIRA: YARDSTICK-620 In the patch, I separate python-setuptools from install.sh and separate appdirs from requirements.txt because there will be error when install them in virtualenv. Also I will update the documentation when this patch merged; Change-Id: I99a532d1851983775869e7c5e8e65fd0229e86df Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-04-18Add SRIOV supportJing Zhang8-13/+124
A generic provider network solution is introduced. To identify whether a network specified in the test case is a provider network new attributes are introduced in the test case network section: networks: test-net: cidr: '192.168.1.0/24' provider: "sriov" physical_network: 'physnet1' If the "provider" attribute is present, the network is an existing provider network. If the value is "sriov", binding:vnic_type=direct is added to the interface in the heat deployment template. In orchestrator/heat.py, the interface creating functions are given a new parameter that tells if the network in use is a provider network. The benchmark/contexts/model.py is changed to store the value of the provider attribute from the test case and function calls to port creation is updated with the provider parameter. The same change is made in contexts/heat.py as well. Also calls for creating a new tenant network is replaced for creating a new provider network if the provider attribute is present. Update-1: Change test_model.py Update-2: Per comment, change comment style to """" Update-3: Change test_heat.py Update-4: Add unit test cases to pass coverage test Update-5: Add SRIOV provider network example in opnfv_yardstick_tc008.yaml Update-6: Per comment, remove empty line in orchestrator/test_heat.py Update-7: Per comment, change comment lines in orchestrator/test_heat.py Update-8: Add more unit test cases to pass coverage test Update-9: Change to create SRIOV provider network on the fly so as to support co-current test runs Update-10: Per comment, init physical_network to 'physnet1' Change-Id: I76004c4fcc9bffcfd8ed021fd647e0cecb346ef4 JIRA: YARDSTICK-612 Signed-off-by: Jing Zhang <jing.c.zhang@nokia.com>
2017-04-17KVMFORNFV:Passing breaktrace option to cyclictest.kalyanreddy1-2/+4
This patch is used to add breaktrace option to monitor the latency values while executing cyclictest test cases as a part of kvmfornfv verify and daily jobs. Change-Id: I035ea72a8946a9d3db37a6ee33ffbf3ca67834a2 Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com>
2017-04-13Merge "Bugfix: fix typo"Rex Lee3-1/+3
2017-04-13Bugfix: fix typoJingLu53-1/+3
Change-Id: I9b7cd5f94b1663af3b807ce24c941868b10d85d1 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-11Add a new runner to test end-to-end fast data pathJing Zhang1-0/+8
This runner caters testing fast host data path (e.g. SRIOV) plus fast VM data path (VM running pktgen-dpdk). It is implemented as a new flavor of the existing Iteration runner. (1) Add a new SLA action rate-control (2) While the SLA target is not met, reduce packet rate until packet loss target is met. Change-Id: I633f391f1790f03ff31458458d79d3f272475ab5 JIRA: YARDSTICK-615 Signed-off-by: Jing Zhang <jing.c.zhang@nokia.com>
2017-04-11KVMFORNFV: Grafana config for Packet Forwarding test cases.kalyanreddy1-0/+2636
This patch is used for adding configuration file to opnfv grafana dashboard for kvmfornfv packet forwarding test cases as a part of daily job. Change-Id: If2f06d2c01a7f6863ae1aa25942c3197856d895b Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com>
2017-04-10Merge "cyclictest: use raw strings to escape \[8"Jing Lu1-4/+6
2017-04-06Merge "attacker_general: fix logging to use %s"Jing Lu1-11/+10
2017-04-06cyclictest: use raw strings to escape \[8Ross Brattain1-4/+6
Change-Id: I36d93eacab2470f90af5653104ad5c07853411bf Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-04-06pip install yardstick failed in ApexJingLu53-18/+1
JIRA: YARDSTICK-625 In Apex, yardstick uninstall and install via pip failed. This bug blocks yardstick CI jobs. This patch enables pip install yardstick in editable mode. So the install_yardstick() in yardstick_verify is unnecessary. Change-Id: If290dac5fee5584601064ae9753ae2340643d3ca Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-06Bugfix: fix ubuntu image name typoJingLu51-1/+1
Change-Id: I8722f2ddd096bc784f45d4bcf58ea6a84d319fb2 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-05Bugfix: fix query job status in TC074JingLu58-13/+14
JIRA: YARDSTICK-621 The storperf job status query in TC074 didn' work properly. The cause is the "type: status" is not passed in the URL. This patch also update storperf VM image to xenial. Change-Id: Idd9f501416b24612f6045a57ba2a95e2ed3a9572 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-04attacker_general: fix logging to use %sRoss Brattain1-11/+10
Change-Id: Ib451d7883eb5df13cfe95477cea43c076ac0452a Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-04-05Merge "Add opnfv_os-ovn-nofeature-noha_daily test suite"Jing Lu1-0/+62
2017-04-05Merge "Yardstick virtualenv support"Jing Lu22-252/+244
2017-04-05Add opnfv_os-ovn-nofeature-noha_daily test suiteJingLu51-0/+62
JIRA: YARDSTICK-624 Change-Id: Ia783bec53e4d889736db7e510d28c32377d4f9b2 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-01Merge "yardstick offline support"Jing Lu2-36/+53
2017-04-01Bugfix: take test case modification into effect in load_images.shJingLu51-0/+2
JIRA: YARDSTICK-622 Bug log: https://build.opnfv.org/ci/view/armband/job/yardstick-fuel-armband-baremetal-daily-danube/24/console This error is because the file changes done in the load_images.sh is not updated. After file modification, pip install -U . is required to tack changes into effect. Change-Id: I8be3ffc963e3d5cec861b68a33efc2fa5bdabbd2 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-01Yardstick virtualenv supportchenjiankun22-252/+244
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-03-31Refine documentationJingLu52-48/+45
Change-Id: Ic9a84954fdb18ac97afde01541b4c84157df8441 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-31Merge "Store packetsize in influxdb"Rex Lee2-3/+4
2017-03-31Store packetsize in influxdbJing Zhang2-3/+4
This allows calculating throughput in Gbps. Add: test_pktgen.py Change-Id: I7e2132ec71985c14570ef18b952b2264ebf7abbc JIRA: YARKSTICK-611 Signed-off-by: Jing Zhang <jing.c.zhang@nokia.com>
2017-03-31Merge "add yardstick_user_interface chapter in userguide"Jing Lu9-12/+17
2017-03-31Merge "Bugfix: cacert should suppot insecure mode if needed"Jing Lu1-0/+1
2017-03-30add yardstick_user_interface chapter in userguideJingLu59-12/+17
JIRA: YARDSTICK-618 Change-Id: I690c24d665016a381ae1ed7d8fa94d5a34bc1b1b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-30Merge "Bugfix: Add test suite for opnfv_os-odl_l3-ovs-ha_daily scenario"Jing Lu1-0/+62
2017-03-30Merge "Refine documentation"Jing Lu21-478/+840
2017-03-30Refine documentationJingLu521-478/+840
Change-Id: I0d3387a520e3decf51bb0f7db53996f148a611d0 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-30Bugfix: Add test suite for opnfv_os-odl_l3-ovs-ha_daily scenarioJingLu51-0/+62
JIRA: YARDSTICK-617 Apex has a new scenario 'opnfv_os-odl_l3-ovs-ha_daily' in CI. This patch add yardstick test suite for this scenario. Change-Id: I50eb84fb506e7cf87cbd6bcb67f3df6d185d8b6b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-30Bugfix: cacert should suppot insecure mode if neededrexlee87761-0/+1
currently, we use env variable "OS_CACERT" to specify the location of cert file. but if there's no cacert and use for personal verification, it's better to also support insecure mode by set OS_CACERT=False JIRA: YARDSTICK-616 Change-Id: I73b0860863bf6386f9114328c52594ef87e02fa3 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-03-29Merge "Set work directory in Yardstick container"Jing Lu1-0/+3
2017-03-28Bugfix: improper license header in swagger docschenjiankun3-74/+50
JIRA: YARDSTICK-609 In the patch: https://gerrit.opnfv.org/gerrit/#/c/28833/ It update the license header, but it is improper to swagger yaml file. The license information will show in swagger docs. So I remove it. Change-Id: Ib87f0f43a95e3b2145c4b59059c4573000f1997c Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-28yardstick offline supportchenjiankun2-36/+53
JIRA: YARDSTICK-597 Currently yardstick can not run offline. In some case this will block the process, causing yardstick job failed The reason is yardstick will pull the latest code when run in CI. Actually we need not pull the latest code because the code in yardstick is already the latest code. So I remove them. Also I check the environment variable and yardstick-image when fetch openrc file and load images. Change-Id: I797da272932ab5292aa40585c82c119aa71b8849 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-28Merge "Bugfix: Error validating value 'cirros-0.3.5'"Jing Lu1-21/+25
2017-03-28Merge "Bugfix:add storperf flavor for TC074"Jing Lu4-6/+18
2017-03-28Set work directory in Yardstick containerJingLu51-0/+3
JIRA: YARDSTICK-608 Set the work directory to /home/opnfv/repos in yardstick docker container to help users better understand file structure. This is a improvement related with document improvement. Change-Id: Ief4b76e6d6898ceab4a546574f5a09d51eb0d945 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-28Bugfix: Error validating value 'cirros-0.3.5'JingLu51-21/+25
JIRA: YARDSTICK-607 some scenarios come with a Cirros-0.3.5 image, Yardstick's load_images.sh will load a second cirros-0.3.5 image, causing the following error: 2017-03-27 07:42:58,317 yardstick.orchestrator.heat heat.py:449 INFO Creating stack 'demo-2ada98f3' error: failed to deploy stack: 'ERROR: Property error: : resources.ares.demo-2ada98f3.properties.image: : Error validating value 'cirros-0.3.5': No images unique match found for {'name': u'cirros-0.3.5'} This patch fixs this error by skipping load cirros image if there already exist one in the glance. Change-Id: I4d43d82d331f6575efd4560be9b6be175e03cd1b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-27Merge "pathspec 'master' did not match any file(s) known to git"Jing Lu1-2/+1
2017-03-27Merge "model: pylint fixes"Rex Lee2-3/+3
2017-03-27pathspec 'master' did not match any file(s) known to gitchenjiankun1-2/+1
JIRA: YARDSTICK-605 On stable branch, exec_tests.sh will also try to git checkout master branch, which cause error "pathspec 'master' did not match any file(s) known to git." This is a remianing bug from the previous release. see at: https://build.opnfv.org/ci/view/yardstick/job/yardstick-apex-lf-pod1-daily-danube/62/console This error occur in line 48. But the reason is 'set -e' If we set 'set -e': 'git checkout master && git pull' return 1 but it will go on executing; but 'git checkout master' will return 1 and terminate immediately. If we do not set, it will return 1 but will terminate immediately. Actually we not need 'git checkout master' here because it is already in stable/danube branch. So I remove it. Change-Id: I106a1da28cf2deee90ebcb25adaf638a210928ee Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-03-27Merge "Bugfix:HA test cases rely on dynamic ip addresses in fuel pods"Jing Lu10-10/+30
2017-03-25Bugfix:HA test cases rely on dynamic ip addresses in fuel podsJingLu510-10/+30
JIRA: YARDSTICK-602 change HA test cases to rely on dynamical generated pod.yaml in fuel pods Change-Id: I0efb01489eb2dd94babf1a45bff2fbf6adef5f6e Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-25Bugfix:add storperf flavor for TC074JingLu54-6/+18
JIRA: YARDSTICK-604 the storperf container now uses a flavor called "storperf", if this flavor is absent, stack creating process will fail. also the openstack variables that passed to the storperf container also needs a update Change-Id: Iab4be6491cc9b24526948e5571f0476ec885a93d Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-24Update cirros image to latest versionMichael Polenchuk19-24/+24
Change-Id: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-03-23model: pylint fixesRoss Brattain2-3/+3
remove redundnant parens replace type with isinstance fix import order Change-Id: I0407cbbf6993290f392f17c398827603b5bc1ebd Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-03-23Merge "Update yardstick framework architecture in userguide"Jing Lu13-141/+300
2017-03-23Merge "Bugfix: Could not load EntryPoint.parse when using 'openstack -h'"Jing Lu1-10/+10