summaryrefslogtreecommitdiffstats
path: root/docs/submodules/yardstick
AgeCommit message (Collapse)AuthorFilesLines
2018-05-17Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Update samples/test_suite.yaml" into stable/fraser - Update samples/test_suite.yaml The sample test suite at sample/test_suite.yaml contained incorrect syntax. It has been updated to add the "default" parameter to "task_args" when running a testcase. JIRA: YARDSTICK-1125 Change-Id: I53409168e47d969317145623df1e2c789396cc32 Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 7b00d64494bdd61f2ab37005de76fa5f6496d45d)
2018-05-17Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Fix log typos in benchmark/scenarios/availability" into stable/fraser - Fix log typos in benchmark/scenarios/availability This commit fixes multiple log message typos and all the emerged pylint errors. MonitorProcess/MonitorOpenstackCmd.verify_SLA() repeat already logged information, so these prints are removed. JIRA: YARDSTICK-1145 Change-Id: Ifef26e4b4ff7766089caec24785511969c2d663e Signed-off-by: Miikka Koistinen <miikka.koistinen@nokia.com> (cherry picked from commit 6fa51bdcc7ad7e4d407f2803fc05b1cfaf66c115)
2018-05-17Update git submodulesRex Lee1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Remove unused methods in SampleVNF" into stable/fraser - Remove unused methods in SampleVNF 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> (cherry picked from commit 50bcd3e477bc29abb43ed73643d551ff55a73403)
2018-05-16Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Update the dummy-scenario-heat-context testcase" into stable/fraser - Update the dummy-scenario-heat-context testcase 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> (cherry picked from commit f37e4dcf771caec3be52e95047997aa22cbd7a88)
2018-05-16Update git submodulesJing Lu1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Document for Euphrates test case results" into stable/fraser - Document for Euphrates test case results JIRA: YARDSTICK-1132 In B and C releases, Yardstick provides an overview of the results of test cases developed by Yardstick, executed on OPNFV community labs. This work has not been done for the D and E releases, although result analysis for Euphrates is available at (https://wiki.opnfv.org/display/yardstick/Euphrates+release+test+results+analysis). We plan to restart to provide a basic test case results analysis for Fraser and compare performance data with Euphrates. This JIRA ticket will be resolved into 3 commits: 1. Document for E release test case data; 2. Document for F release test case data; 3. Document for results analysis. Change-Id: I372a60807ac3dfaab87e70cdb956c1059b019f7a Signed-off-by: JingLu5 <lvjing5@huawei.com> (cherry picked from commit 4c20fb57684bc21e7ae0461341088100e518307d)
2018-05-15Update git submodulesDimitrios Markou1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Implement Virtual Switch resilience test case This testcase tests the resilience of the Virtual Switch in an OpenStack environment. It can only run in a non Ubuntu distro because it is limited by this bug [0] [0]: JIRA: YARDSTICK-1140 Change-Id: Ia1480fba9f3549d1144c80699056b501d3b07a0f Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit 53f5951a47fcaa5a3f8bcd6ea1020e54a1b285d3)
2018-05-15Update git submodulesDimitrios Markou1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Bug Fix: Start openvswitch service in Centos distro JIRA: YARDSTICK-1142 Change-Id: I82c479c95e10de37416081eacf2d8bee396e50dc Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit d00660e583ef89fe07149c7f0cffcced7cd72133)
2018-05-15Update git submodulesDimitrios Markou1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Add support for restarting a service JIRA: YARDSTICK-1138 Change-Id: Id57defb574eb7e0f5be81b52803cdb05f46796ab Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit 131b9f04a360ccc894510a275bd33c57634608fc)
2018-05-15Update git submodulesDimitrios Markou1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Add ODL HA testcase This testcase confirms the resiliency of Opendaylight in a HA deployment SPEC: https://gerrit.opnfv.org/gerrit/#/c/50991 JIRA: HA-33 JIRA: YARSTICK-955 Change-Id: I4cb39d1970ed0333a43fbb58f8c7138908379dcb Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit d16b2e14fe420a646d4399986bd9f4d1ae3a606d)
2018-05-15Update git submodulesDimitrios Markou1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Add pod.yaml files for Apex JIRA: YARDSTICK-1097 Change-Id: If116174c562bc08c0b7602324599bc85d8c60be0 Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com> (cherry picked from commit 6f374141466640655cc57277b4b49d6deffa9092)
2018-04-26Update git submodulesrexlee87761-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - [release] Yardstick Fraser 6.0.0 Release notes JIRA: YARDSTICK-1129 Change-Id: I5adb2e9547c58b90d3eafb0e2b90015ce5472cfa Signed-off-by: rexlee8776 <limingjiang@huawei.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com> (cherry picked from commit a324c1b922ae2598dbe25e9b2885620ef09f4901)
2018-04-26Update git submoduleschenjiankun1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Bugfix: ansible can't not run without config JIRA: YARDSTICK-1135 Ansible need ansible.cfg when run in the remote node. However the file name is wrong. Need: setup.cfg -> ansible.cfg Change-Id: Ifa674fb624ca83d90c3ac9ad3bfe148013bf8bfd Signed-off-by: chenjiankun <chenjiankun1@huawei.com> (cherry picked from commit 170842f20426ad244f3e49b3780b0256302b0be3)
2018-04-25Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - nsb_setup: pin docker image version to release tag The install scripts pull tags for stable releases. We need to temporarily pin the image tag to the unreleased tag because we have to update the code before we actually tag the image. Or maybe we should make this a parameter to the script JIRA: YARDSTICK-1137 Change-Id: I2e5f13ffe19d1c19fd7b8e071df28fd225be3d79 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-24Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "extra loopback cleanup" into stable/fraser - extra loopback cleanup 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-24Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "[docs] Updated baremetal instalation instructions" into stable/fraser - [docs] Updated baremetal instalation instructions JIRA: YARDSTICK-1111 Change-Id: Iefab24f74c87a0855c2d70090ac34256ffa9200c Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com> (cherry picked from commit 1c4a5e82aec771aba616879a9a351bade6d6d8d0)
2018-04-24Update git submodulesJack Chan1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Bugfix: Can't get image list in API" into stable/fraser - Bugfix: Can't get image list in API 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> (cherry picked from commit 5ac59e495d74b64ab377f1ba25bb00b11da14e67)
2018-04-23Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - remove more old apexlake testcases fix fraser failures Change-Id: I8bb12a762054a4c3274cc6e0297e948b92700e7e Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-20Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - disable NSB (DPDK) image load for ARM we skip the building now but we also need to skip the image loading JIRA: YARDSTICK-1124 Change-Id: I27c40d6319e74374282203132cfc2c7ebff9b094 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com> (cherry picked from commit 15cec319ab06f161c239ead78da9ecdf1673b7ce)
2018-04-20Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - disable DPDK images for ARM 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> (cherry picked from commit 50154694f8dc37726d456cfb8efddc6d3e126dbd)
2018-04-19Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - remove apex lake tc007 from test suites 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> (cherry picked from commit 01ef85fc8234c8ddeaae65eceaf5bbb9545b9e98)
2018-04-18Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "[userguide] Use literalinclude directive in 05-operation" into stable/fraser - [userguide] Use literalinclude directive in 05-operation 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> (cherry picked from commit ee9995c42368ee04ba06cd101b086c57dbbb3bba)
2018-04-17Update git submodulesJack Chan1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "Bugfix: interface down HA tc050 attack and monitor logistic wrong" into stable/fraser - Bugfix: interface down HA tc050 attack and monitor logistic wrong 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> (cherry picked from commit af7f0bea3a0d24bdf084622acc9932ccd261e42e)
2018-04-16Update git submodulesRex Lee1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "[docs] update the user guide for "yardstick-operation"" into stable/fraser - [docs] update the user guide for "yardstick-operation" * 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: I630e701136b9d573539fe69ea0a42018a67d040f Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 5b4cee9606f26f4c208fcd1aec544ddd436b8162)
2018-04-13Update git submodulesRex Lee1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Merge "[docs] Move user guide chapters to make room for new chapter." into stable/fraser - [docs] Move user guide chapters to make room for new chapter. * Increment the numbering on chapters * Fix some of the changes flagged by doc8 Change-Id: I9dbf4a3d33c2b38f7567bc3493466e72a59e1a0c Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 3248682fcc789f95ff8246a8d1f208a6a3abd46d)
2018-04-12Update git submodulesliyin1-0/+0
* Update docs/submodules/yardstick from branch 'stable/fraser' - Bug fix in using Unixbench 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> (cherry picked from commit 941d3b0c0fa4583c49fa6fd2aa3686a1b55ab187) - Bugfix: k8 scenario fix JIRA: YARDSTICK-1109 Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf Signed-off-by: rexlee8776 <limingjiang@huawei.com> (cherry picked from commit 3b1316647b50bc3bbb1eb6216aa07fd4dff34edf) - docker/supervisor.sh: Fix condition block end Fixes: 18546b4f Change-Id: I51fcb48e790ff7c57273a3f6712ccb2b9bc4aa32 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit ead90064d12be552bd334828d41ffffa75fad01b) - [AArch64] Dockerfile: Fix malformed patch Change-Id: Ia2dfc6c4def8e71e36747b8f27cbf22700f676b1 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit 161f7d676b4404a5445681a7871e086b751fdafc)
2018-04-07Update git submodulesAlexandru Avadanii1-0/+0
* Update docs/submodules/yardstick from branch 'master' - docker/supervisor.sh: Fix condition block end Fixes: 18546b4f Change-Id: I51fcb48e790ff7c57273a3f6712ccb2b9bc4aa32 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-06Update git submodulesAlexandru Avadanii1-0/+0
* Update docs/submodules/yardstick from branch 'master' - [AArch64] Dockerfile: Fix malformed patch Change-Id: Ia2dfc6c4def8e71e36747b8f27cbf22700f676b1 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-06Update git submodulesAbhijit Sinha1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Bugfix: k8 scenario fix" - Bugfix: k8 scenario fix JIRA: YARDSTICK-1109 Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-04-04Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/yardstick from branch 'master' - [userguide] Use literalinclude directive in 05-operation 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> - [docs] update the user guide for "yardstick-operation" * 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> - [docs] Move user guide chapters to make room for new chapter. * 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-03-31Update git submodulesliyin1-0/+0
* Update docs/submodules/yardstick from branch 'master' - ADD tc042 into CI 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-29Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Fix RabbitMQ service installation and initialization" - Fix RabbitMQ service installation and initialization RabbitMQ service added in [1] is not correctly installed and initialized: - There is an error during the installation process ("\" character missing). - In the installation script, the service needs to be started first. - In the container installation, the service needs to be started via supervisor. [1]https://gerrit.opnfv.org/gerrit/#/c/53597/ JIRA: YARDSTICK-1103 Change-Id: Iade3d6ce4b522e6f576af71b7afe5559081f7929 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-29Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "don't print exceptions in atexit handler" - don't print exceptions in atexit handler 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-29Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "task: don't hide exceptions in Task" - task: don't hide exceptions in Task If the Task raised an exception we currently hide it and replace it with RuntimeError. This is bad. If an exception occured, then we don't have a result so re-raise the original exception. Or we could log the traceback and raise RuntimeError, but that doesn't seem to be a good idea. Sample traceback after re-raising original. Without this patch the ValueError is only written to _write_error_data 2018-03-25 22:57:56,511 yardstick.benchmark.contexts.node node.py:85 DEBUG BareMetals: [] 2018-03-25 22:57:56,511 yardstick.benchmark.contexts.node node.py:89 DEBUG Env: {} 2018-03-25 22:57:56,511 yardstick.cmd.commands.task task.py:57 INFO Task FAILED Traceback (most recent call last): File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/cmd/commands/task.py", line 54, in do_start result = Task().start(param, **kwargs) File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/core/task.py", line 103, in start task_args_fnames) File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/core/task.py", line 321, in _parse_tasks task_args_fnames[i] File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/core/task.py", line 558, in parse_task context.init(cfg_attrs) File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/contexts/heat.py", line 131, in init server = Server(name, self, server_attrs) File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/contexts/model.py", line 210, in __init__ (name, p)) ValueError: server 'trafficgen_1', placement 'pgrp2' is invalid 2018-03-25 22:57:56,512 yardstick.cmd.commands.task task.py:62 INFO Task FAILED 2018-03-25 22:57:56,662 yardstick.benchmark.runners.base base.py:124 DEBUG Terminating all runners NoneType JIRA: YARDSTICK-1102 Change-Id: I7e6fa41fc1d36f6d438a1602ab60cb41ffbee1e9 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-29Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - add new Fraser scenarios 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-28Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "restore Heat stack failure logs for CI" - restore Heat stack failure logs for CI We need to see what Heat failures occured so that we can debug CI failures. The only way to do this seems to be to use the private event_utils.get_events function to query for all failures Also since we had a failure go ahead and dump the Heat template that failed. Sample output: 2018-03-25 23:50:08,765 [INFO] yardstick.orchestrator.heat heat.py:629 Creating stack 'yardstick-460ed969' START 2018-03-25 23:50:21,932 [ERROR] yardstick.orchestrator.heat heat.py:644 Resource CREATE failed: BadRequest: resources.yardstick-460ed969-xe1: Invalid input for operation: physical_network 'nosuch' unknown for flat provider network. Neutron server returns request_ids: ['req-6f981f1e-a9e2-4114-af84-1ee528aed51b'] 2018-03-25 23:50:21,933 [ERROR] yardstick.orchestrator.heat heat.py:644 BadRequest: resources.yardstick-460ed969-xe1: Invalid input for operation: physical_network 'nosuch' unknown for flat provider network. Neutron server returns request_ids: ['req-6f981f1e-a9e2-4114-af84-1ee528aed51b'] 2018-03-25 23:50:21,972 [ERROR] yardstick.orchestrator.heat heat.py:645 {'description': '\n' 'All referred generated resources are prefixed with the ' 'template\n' 'name (i.e. yardstick-460ed969).\n', 'heat_template_version': '2013-05-23', 'outputs': {'trafficgen_1.yardstick-460ed969': {'description': 'VM UUID', 'value': {'get_resource': 'trafficgen_1.yardstick-460ed969'}}, 'trafficgen_1.yardstick-460ed969-fip': {'description': 'floating ' 'ip ' JIRA: YARDSTICK-998 Change-Id: Ia8f4e5ba7e280fb9086519680d5ee90a2b442e6b Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-28Update git submodulesRex Lee1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Replace neutron create security group rule with shade." - Replace neutron create security group rule with shade. Rename create_secgroup_rule with create_security_group_rule. Function create_security_group_rule now uses shade client. JIRA: YARDSTICK-890 Change-Id: Ie0ebac67a281e55dc95c0e3e33ba43de80aba9ec Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
2018-03-28Update git submodulesRex Lee1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Dashboard for TC056" - Dashboard for TC056 This is dashboard for Yardstick test case TC056. JIRA: YARDSTICK-1085 Change-Id: I8bf2149f8dd9081022deb280101815cb1dd417ec Signed-off-by: Mika Rautakumpu <mika.rautakumpu@nokia.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Improve "Libvirt.virsh_destroy_vm" function" - Improve "Libvirt.virsh_destroy_vm" function Read the command exit code and log a warning in case the VM destroy process went wrong. JIRA: YARDSTICK-943 Change-Id: I2750b8d4a8f67af081c1988510cf5aca848a2cf1 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Improve "Libvirt.virsh_create_vm" function" - Improve "Libvirt.virsh_create_vm" function Read the command exit code and raise an exception in case the VM boot process went wrong. JIRA: YARDSTICK-941 Change-Id: Ibabaae8983213a33799ad00fa4d9541bbabea857 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Improve NSB Standalone XML generation" - Improve NSB Standalone XML generation Delayed the generation of the XML file until the last step. The following functions will return a XML string insted: - Libvirt.build_vm_xml - SriovContext._enable_interfaces - OvsDpdkContext._enable_interfaces The XML file will be written just before copying the file to the compute hosting the VMs. JIRA: YARDSTICK-939 Change-Id: Icc80f4741903bbe335db4ebccab395b72fa87e82 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Improve OVS-DPDK setup process" - Improve OVS-DPDK setup process Improved OVS-DPDK setup process: - Added log string for each command executed. - Removed unnecessary 'kill' command. - Check if commands are executed correctly. JIRA: YARDSTICK-922 Change-Id: I09fba96ffa39cde1e000a3c4382d474219c99985 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Improve OVS-DPDK boot process" - Improve OVS-DPDK boot process Check if hugepages are present in the system. Check if every command executed during the boot up process exits correctly. JIRA: YARDSTICK-917 Change-Id: Ic0c8a72199ad80e3a65488cc88d0692863751284 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Replace neutron floating ip deletion with shade." - Replace neutron floating ip deletion with shade. Function delete_floating_ip now uses shade client. JIRA: YARDSTICK-890 Change-Id: I960630926b664266afbe7be00bb1352243b41be0 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Replace neutron floating ip creation with shade." - Replace neutron floating ip creation with shade. Function create_floating_ip now uses shade client instead of neutron client. JIRA: YARDSTICK-890 Change-Id: I3defd691dad998cebf98442b52f0555b176f1af4 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Replace neutron router interface deletion with shade." - Replace neutron router interface deletion with shade. Function remove_interface_router now uses shade client instead of neutron client. JIRA: YARDSTICK-890 Change-Id: I6bd36e35a339cce64dfa8b69c1e7b56cd70af956 Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
2018-03-27Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "env: validate installer_ip from environment" - env: validate installer_ip from environment validate installer_ip is proper IPv4 address in case of user error Change-Id: Ib01916bc85ec411c159af1564f5142177f464047 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-26Update git submodulesRodolfo Alonso Hernandez1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Install RabitMQ for RPC messaging between processes" - Install RabitMQ for RPC messaging between processes In NetworkServices Tescases, the TGs (traffic generators) run the traffic in a separate process. In order to synchronize the traffic injection and the runner interval loops, an RPC server is needed to publish/subscribe events. RabbitMQ is a well supported MQ in Linux (used in OpenStack or collectd) and supported by Python implemented projects like oslo.messaging [1]. RabbitMQ default configuration: - Port: 5672 - User/password: yardstick/yardstick [1]https://github.com/openstack/oslo.messaging JIRA: YARDSTICK-1068 Change-Id: I15db294ee430fb38e574a59b9ce1bf0f8b651a67 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-24Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "Test case spec for SDN controller resilience in non-HA config" - Test case spec for SDN controller resilience in non-HA config This is the test case specification for verifying the HA capabilities of a SDN controller running in a non-HA configuration. JIRA: HA-31 JIRA: YARDSTICK-955 Change-Id: I10f9ce4a2888092c033d2c02bf9a5a950b8b12dc Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-03-24Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "ansible: disable Extra cloud image kernel stub" - ansible: disable Extra cloud image kernel stub JIRA: YARDSTICK-900 Change-Id: Icd3e5333fa30c77fec462dd26b70f0f28b8ca67f Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-03-24Update git submodulesRoss Brattain1-0/+0
* Update docs/submodules/yardstick from branch 'master' - Merge "use basename to delete yardstick image loop devices" - use basename to delete yardstick image loop devices the full path probably isn't matching, so just grep for the basename JIRA: YARDSTICK-1096 JIRA: YARDSTICK-1054 Change-Id: I403a7f51310c0856fae0f79d115ba0786b7c417c Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>