summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-04-19extra loopback cleanupRoss Brattain2-5/+13
try to cleanup in the shell script in case ansible errors maybe it is hopeless because of docker JIRA: YARDSTICK-1096 JIRA: YARDSTICK-1054 Change-Id: I759ded4731a7710a194a81530cfb35376eb7800d Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-19disable DPDK images for ARMRoss Brattain1-1/+3
We are trying to compile DPDK for the os-nosdn-ovs-ha scenario because we added TC042  "Measure network latency using testpmd and pktgen-dpdk". However it looks like TC042 is only enabled for compass in opnfv_os-nosdn-kvm_ovs_dpdk-ha https://gerrit.opnfv.org/gerrit/#/c/54659/1/tests/opnfv/test_suites/opnfv_os-nosdn-kvm_ovs_dpdk-ha_daily.yaml - file_name: opnfv_yardstick_tc042.yaml constraint: installer: compass pod: huawei-pod1 We don't actually need TC042 and DPDK or os-nosdn-ovs-ha. But in order to run TC042 we have to know beforehand that we are going to use DPDK, so we have a conditional in the load_images.sh script that tries to guess when we will need a DPDK image. The conditional only checks for *[_-]ovs[_-]* if [[ $DEPLOY_SCENARIO == *[_-]ovs[_-]* ]]; then ansible-playbook \ -e img_property="nsb" \ -e YARD_IMG_ARCH=${YARD_IMG_ARCH} \ -vvv -i inventory.ini build_yardstick_image.yml if [ ! -f "${QCOW_NSB_IMAGE}" ]; then echo "Failed building QCOW NSB image" exit 1 fi fi For this release we won't be able to get DPDK images to compile on ARM, we should fix this conditional and not try to compile. Also change the shell glob to match *[_-]ovs_dpdk[_-]* to only enable DPDK images for ovs_dpdk scenarios JIRA: YARDSTICK-1124 Change-Id: I03142e6b8aa00dc9cdf9b446868fb723cd10198b Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-19Merge "Update neutron delete_neutron_net function."Emma Foley4-24/+34
2018-04-19MessagingConsumer accepts messages from multiple producersRodolfo Alonso Hernandez2-27/+32
The messaging consumer now can store a list of PID of several producers. The notification handler can compare the procedence of a message from a list of PID. JIRA: YARDSTICK-1074 Change-Id: I193f83c2b471e5bf1298ac728be52533aded0c1a Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-04-18Merge "add verbose to debug losetup delete"Ross Brattain1-1/+1
2018-04-18DPDK: detect dpdk_make_arch based on image archRoss Brattain2-2/+8
JIRA: YARDSTICK-1124 Change-Id: I26e5854f5117a3b45ac7fa4d4b06f325dcd4d97a Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-18Merge "remove apex lake tc007 from test suites"Ross Brattain4-52/+0
2018-04-18Merge "Replace neutron create security group full with shade."Rodolfo Alonso Hernandez5-110/+170
2018-04-18Update the dummy-scenario-heat-context testcaseEmma Foley1-3/+4
The testcase is included in the docs to demonstrate definining a heat context. It previously used cirros, but this is not included by default. Set-up instructions/scripts add yardstick-image and yardstick-flavor, so these have been added to the testcase instead. A default value for context_name was also added. Change-Id: I5f642086971487b334ae48a5cf5c9b71e9b99e2e Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-04-17remove apex lake tc007 from test suitesRoss Brattain4-52/+0
fixes opnfv_os-nosdn-fdio-noha_daily.yaml failures due to missing testcase Change-Id: I5f050d72334da46b94de5fa3662047bf694f7e3e Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-17fix unittest test_deploy_try_retrieve_context_does_not_existRoss Brattain1-1/+1
unittest is failing due to mock being called multiple times. I assume this is due to parallelization of tests in Jenkins somehow ====================================================================== FAIL: test_deploy_try_retrieve_context_does_not_exist (benchmark.contexts.test_heat.HeatContextTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master/.tox/py3/lib/python3.5/site-packages/mock/mock.py", line 1305, in patched return func(*args, **keywargs) File "/home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master/yardstick/tests/unit/benchmark/contexts/test_heat.py", line 309, in test_deploy_try_retrieve_context_does_not_exist mock_path_exists.assert_called_once_with(key_filename) File "/home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master/.tox/py3/lib/python3.5/site-packages/mock/mock.py", line 947, in assert_called_once_with raise AssertionError(msg) AssertionError: Expected 'exists' to be called once. Called 3 times. ---------------------------------------------------------------------- Change-Id: I696c63ef9f7943b841e2d3d533c92f18aa7044da Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-17OpenStack deployment: delete RS or all VMsStepan Andrushko5-24/+56
New parameter is added to shell script to delete data for VMs either from input file or all. Added disk images removal as per new input parameter. JIRA: YARDSTICK-1123 Change-Id: I8d2cee4a3a7ad7147f4d59303bab656d80370221 Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
2018-04-17Remove unused methods in SampleVNFEmma Foley2-90/+0
The following private methods are unused in yardstick/network_services/vnf_generic/vnf/sample_vnf.py:SampleVNF * _build_ports(self) * _get_route_data(self, route_index, route_type) * _get_port0localip6(self) * _get_port1localip6(self) * _get_port0prefixlen6(self) * _get_port1prefixlen6(self) * _get_port0gateway6(self) * _get_port1gateway6(self) They are being removed as: * _get_port* functions are already implemented and used in MultiPortConfig * _get_route_data is an auxillary functions used by the previous ones * _build_ports is implemented in the helpers JIRA: YARDSTICK-1122 Change-Id: Ie7a706cd87b610ea56f89214118a02e612a70dc0 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-04-16Improve "Libvirt.create_snapshot_qemu" functionRodolfo Alonso Hernandez3-18/+111
Improved "Libvirt.create_snapshot_qemu" function: - Check if the base image is present in the remote host. If not, try to copy from the execution host. - Check the execution status. In case the command fails, raise an exception. JIRA: YARDSTICK-944 Change-Id: I78bd0d3ed6a1f35ed772c0d192bb240009a580ed Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-04-16Update neutron delete_neutron_net function.Shobhi Jain4-24/+34
Update the changes done in patch [1]. JIRA: YARDSTICK-890 [1] https://gerrit.opnfv.org/gerrit/#/c/52361/ Change-Id: Iccbf16d0a2e72919d5092366241ff41686f01a58 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
2018-04-16Replace neutron create security group full with shade.Shobhi Jain5-110/+170
Function create_security_group_full now uses shade client. Remove openstack util's private 'get_security_groups', 'get_security_group_id' & 'create_security_group' functions as 'create_security_group_full' now uses 'get_security_group' & 'create_security_group' function defined in shade client library. JIRA: YARDSTICK-890 Change-Id: Ibd5b9ca9b7ce99b3e40c5dcc545f2af672ce2203 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
2018-04-16Merge "Remove tool provisioning in Standalone contexts"Emma Foley2-9/+5
2018-04-16Get HA test case results on failureMiikka Koistinen5-75/+55
Now, yardstick HA test cases (which have 'sla action: monitor') do not output results if the test case SLA validation fails. This patch modifies the task runner and the serviceHA scenario so that during an SLA validation failure the test result data is captured correctly. Do similar changes in the general scenario. JIRA: YARDSTICK-1115 Change-Id: I648a8b229600c0ad089320ac3f803698f73aa800 Signed-off-by: Miikka Koistinen <miikka.koistinen@nokia.com>
2018-04-16Merge "Bugfix: interface down HA tc050 attack and monitor logistic wrong"Rex Lee2-91/+42
2018-04-13Add MQ consumer, producer and payload base classesRodolfo Alonso Hernandez12-0/+490
Added MessagingProducer base class. A class implementing this base class can send a cast message using the MQ service installed in the Yardstick jumphost (RabbitMQ by default, other MQ could be implemented). The producer will send messages to an specific topic. Added MessagingConsumer base class. A class implementing this base class will be able to receive any message sent by a MessagingPorducer class publishing messages in the topic subscribed. By default both Producer and Consumer "fanout" is True. That means every Consumer will create a fanout Queue attached to the MQ Exchange topic. All Consumers attached to this topic will receive the message sent by the Producer [1]. Added Payload base class. To send data through the message queue service, a Payload derived object should be created. This base class allows to define the attributes container in the class, convert the object to a dict and retrieve the object from a dict. Added a new library, "oslo.messaging", to implement the RPC client and server. [1]http://blog.thedigitalcatonline.com/blog/2013/08/21/some-tips-about-amqp-direct-exchanges/ JIRA: YARDSTICK-1074 Change-Id: I63932b5fb3de2bdc1270fc83295630a2a349e2a6 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-04-13Bugfix: interface down HA tc050 attack and monitor logistic wrongrexlee87762-91/+42
1. simplify the attack to be one interface 2. move monitor step before attack 3. update rst doc to match JIRA: YARDSTICK-1120 Change-Id: Icfa21d58e7ccdbeaca8a9a1a3098cceb21c981c3 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-04-13Merge "Bugfix: to list all used loop device"Rodolfo Alonso Hernandez1-1/+2
2018-04-13Merge "Bugfix: Can't get image list in API"Jing Lu6-47/+105
2018-04-12Bugfix: to list all used loop deviceting wu1-1/+2
Bug fix in script "build_yardstick_image.yml", to - Use option "-a" to list all used loop devices, to be more compatible. - Ignore the error and continue, if the debug command failed. JIRA: YARDSTICK-1121 Change-Id: I24aaebb2ffe3107ca5c619401725aa8c8e1af295 Signed-off-by: ting wu <ting.wu@enea.com>
2018-04-12Bugfix: Can't get image list in APIchenjiankun6-47/+105
JIRA: YARDSTICK-1110 To match OpenStack Pike release, we upgrade novaclient from 7.1.1 to 9.1.1. And the client interface has changed, it no longer has nova_client.images attribute. So I use shade instead. Later will change all same issue. Change-Id: Ie4f54069d4346e44e2ad925439930504b945cbad Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2018-04-11Merge "Bug fix in using Unixbench"Rodolfo Alonso Hernandez1-1/+1
2018-04-11Add docker support for Ubuntu 17.10 with YardstickJohn O Loughlin2-14/+2
JIRA: YARDSTICK-1119 Change-Id: I6d9b21667605f1c0a157c2a72e708c36b90e8c3a Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-04-11Upgrade collectd to version 5.8John O Loughlin1-1/+1
Update collectd version to 5.8 as it's the latest stable and supports GCC 7 JIRA: YARDSTICK-1114 Change-Id: I9147b7277d87047eda729664d5ee3e8ab2c145af Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-04-11Merge "Add support for dpdk 17.05"Emma Foley7-21/+23
2018-04-11Add support for dpdk 17.05John O Loughlin7-21/+23
Add support for dpdk 17.05. Add option to dpdk scripts to download dpdk 17.08 17.11 and 18.02. These are currently unsupported due to prox build issues. JIRA: YARDSTICK-1113 Change-Id: I585566364a4d1f04a696439af96c50c0e9d38033 Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-04-11Bug fix in using Unixbenchliyin1-1/+1
JIRA: YARDSTICK-1117 This bug will cause the error in running unixbench. "no such file named ./run" So we have to fix it. Change-Id: I141fcb5567fbb0e3df97aee677cb946a25a9788e Signed-off-by: liyin <liyin11@huawei.com>
2018-04-10Bugfix: k8 scenario fixrexlee87762-45/+19
JIRA: YARDSTICK-1109 Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 3b1316647b50bc3bbb1eb6216aa07fd4dff34edf)
2018-04-07docker/supervisor.sh: Fix condition block endAlexandru Avadanii1-3/+3
Fixes: 18546b4f Change-Id: I51fcb48e790ff7c57273a3f6712ccb2b9bc4aa32 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit ead90064d12be552bd334828d41ffffa75fad01b)
2018-04-07docker/supervisor.sh: Fix condition block endAlexandru Avadanii1-3/+3
Fixes: 18546b4f Change-Id: I51fcb48e790ff7c57273a3f6712ccb2b9bc4aa32 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-06[AArch64] Dockerfile: Fix malformed patchAlexandru Avadanii1-2/+2
Change-Id: Ia2dfc6c4def8e71e36747b8f27cbf22700f676b1 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit 161f7d676b4404a5445681a7871e086b751fdafc)
2018-04-06[AArch64] Dockerfile: Fix malformed patchAlexandru Avadanii1-2/+2
Change-Id: Ia2dfc6c4def8e71e36747b8f27cbf22700f676b1 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-06Merge "Bugfix: k8 scenario fix"Abhijit Sinha2-45/+19
2018-04-06[docs] Updated baremetal instalation instructionsChornyi, TarasX1-0/+9
JIRA: YARDSTICK-1111 Change-Id: Iefab24f74c87a0855c2d70090ac34256ffa9200c Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
2018-04-03[userguide] Use literalinclude directive in 05-operationEmma Foley1-75/+9
Uses literalinclude directive instead of having a copy of the file content in documentation. This means that any update to this file is detected, and the most up-to-date content is used. If a testcase is updated, the updates wil be picked up. The examples used are ones that are tested reqularly. JIRA: YARDSTICK-1066 Change-Id: I15d967eb04d1e6f4348683d8746fa9989dceda94 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-04-03[docs] update the user guide for "yardstick-operation"Emma Foley4-1/+367
* Add a new chapter: operation which shows how to use Yardstick and how to create test cases * Include details on how to reuse and keep VNFs between testcases JIRA: YARDSTICK-885 JIRA: YARDSTICK-886 Change-Id: I365152e8812427a3c54259adbc18d5ddb216d775 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-04-03[docs] Move user guide chapters to make room for new chapter.Emma Foley15-551/+437
* Increment the numbering on chapters * Fix some of the changes flagged by doc8 Change-Id: Ie03d165297671dfd50b9de339612cdc8bf00b988 Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-04-03Bugfix: k8 scenario fixrexlee87762-45/+19
JIRA: YARDSTICK-1109 Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-03-31ADD tc042 into CIliyin3-0/+31
JIRA: YARDSTICK-1108 We add this test case in ovs_dpdk-ha and ovs_dpdk-noha testsuites also add image build into load_images script Change-Id: I2b0c6b106dd98c3693df18dba46259ff8ef0a76e Signed-off-by: liyin <liyin11@huawei.com>
2018-03-29add verbose to debug losetup deleteRoss Brattain1-1/+1
JIRA: YARDSTICK-1096 JIRA: YARDSTICK-1054 Change-Id: I5a11dbd2638782c5e499cb94dd5882b8bf696e8d Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-29Merge "Fix RabbitMQ service installation and initialization"Ross Brattain2-3/+7
2018-03-29Merge "don't print exceptions in atexit handler"Ross Brattain1-1/+1
2018-03-29Merge "task: don't hide exceptions in Task"Ross Brattain1-6/+9
2018-03-29don't print exceptions in atexit handlerRoss Brattain1-1/+1
atexit handler calls terminate_all after the regular python execution path, and it looks like the traceback stack is None somehow. In this context log.debug("", exc_info=True) doesn't work it prints out NoneType on Python3 and causes other problems on Python2.7 remove the exc_info=True from the logging call JIRA: YARDSTICK-1107 Change-Id: Ida0a0ced7ff5e017e2f8608880e3bb531724af95 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-28add new Fraser scenariosRoss Brattain10-0/+304
New scenarios from wiki: https://wiki.opnfv.org/display/SWREL/Fraser+Scenario+Statu Change-Id: Ifd6e45e73be2bbb99743aa3f4981d22899aab92a Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-28Merge "restore Heat stack failure logs for CI"Ross Brattain2-1/+27