Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I9b7cd5f94b1663af3b807ce24c941868b10d85d1
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit a84dfcb92e1de313fea7841224be5a374a2d2184)
|
|
|
|
Change-Id: I8722f2ddd096bc784f45d4bcf58ea6a84d319fb2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 571ee6afca03120c393def421eb35a466f9a940b)
|
|
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>
(cherry picked from commit b2fb23ca8ccc1acedaa9156552af4ba347f24103)
|
|
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>
(cherry picked from commit d2cb7ce7331d8da4c3b5b70b09dac49cf65d1710)
|
|
|
|
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>
(cherry picked from commit b74d875134b988a26441d559a9e700aaa68d6a0c)
|
|
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>
(cherry picked from commit 38df788fc4a683717a6e7cbd498fad1e7cbe7209)
|
|
JIRA: YARDSTICK-624
Change-Id: Ia783bec53e4d889736db7e510d28c32377d4f9b2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit da47f4de9d57f40ecc7cedeac18c0d061bd21c84)
|
|
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>
|
|
|
|
Change-Id: Ic9a84954fdb18ac97afde01541b4c84157df8441
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-618
Change-Id: I690c24d665016a381ae1ed7d8fa94d5a34bc1b1b
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 0ce79677b81b47a7f66e43af896cfa9632da6bee)
|
|
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>
(cherry picked from commit 3f70095d15afb86567f885cbfbd89183d857f671)
|
|
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>
(cherry picked from commit 0e930373273dc76db929e8e885beb97e04636ad2)
|
|
Change-Id: I0d3387a520e3decf51bb0f7db53996f148a611d0
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 2347f3977823bfd0c4b1fa832d9046b8a625596b)
|
|
Labels serve as anchors/ refs when referenced from other documents
This patch adds labels to docs/*/*/index.rst
Change-Id: I046277771130cc6298636fb30f9d6dae7de224cf
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
(cherry picked from commit 6509a1b7ce0cd16f17ea3116af25794938c93566)
|
|
Currently Yardstick doesnt have any UI which gives detail analysis
of the test-results.
This commit generates a HTML page after the execution of a command
"yardstick report generate <task-ID> <TC-name>" which intern
can be executed after the execution of test-case.
Used: Highcharts.js for the graphs.
JIRA: YARDSTICK-280
Change-Id: Ic98cc348719f3922bff178f52e7944a4a931763a
Signed-off-by: Rajesh K <4k.rajesh@gmail.com>
(cherry picked from commit 25b21add71fcf7c2c795bd950b5117d69fac68fb)
|
|
Change-Id: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
(cherry picked from commit 043727feabaf7cabb719dbd3d52274bcd0dbea66)
|
|
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>
(cherry picked from commit 343970dc9c6193e28863e4ab8bae801b5060ae6a)
|
|
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>
(cherry picked from commit 6e77001bcd07f30f9edcf4103528002f4c4ec536)
|
|
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>
(cherry picked from commit 0691766d310e00d7f1cec763427db271076b5633)
|
|
stable/danube
|
|
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>
|
|
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>
(cherry picked from commit 6c414e6f46861f71aa68db43ffabcad2305f3f32)
|
|
|
|
|
|
|
|
JIRA: YARDSTICK-597
Currently yardstick can not run offline.
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.
Change-Id: Ief87c529625ccaa26e758a2206318b3797bbfd74
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
(cherry picked from commit 52634e40e5668e2d8c031781d1b15b482b0511f4)
|
|
JIRA: YARDSTICK-590
This patch update the yardstick framework architecture in the userguide,
also fix some rst grammar mistakes
Change-Id: I84e7c24b4cd936a01f4c191e9f530f15f9f711de
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 7150e6bc49098937edcac0fa9fa108329c74af4a)
|
|
JIRA: YARDSTICK-599
Python-openstackclient 3.7.0 has a issus that cause -help info can not be
loaded properly when executing 'openstack -h' command.
Change-Id: I0a5f7a0943d56764b1c4d5d7335aa67b30f39b4c
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit ff3501f28a80537cb9a2453708e2d3d62c4a3292)
|
|
|
|
JIRA: YARDSTICK-601
This error is cause because the TC 002 configuration file has been modified in
image section, the old sed command in load_images.sh
"sed -i 's/image: cirros-0.3.3/image: TestVM/g' tests/opnfv/test_cases/opnfv_yardstick_tc002.yaml samples/ping.yaml" didn't work properly.
Change-Id: Ie897213622d05bb267f94b466eb2529e797d484e
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 2fb078e21a3cd0dc69732f33b5a6ecc422eb577d)
|
|
Get the arch from a compute node
Also move code that depends on YARD_IMG_ARCH,
after YARD_IMG_ARCH gets set
JIRA: YARDSTICK-591
Change-Id: I5ed3ef9cfa92e5bf9e6ada21396d18643cf1a55c
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
(cherry picked from commit 13d68ab65475ec556383480a17dbaf63e3ab140c)
|
|
We should have run shellcheck on this.
This is why we don't use the shell, too many
obscure gotchas.
shellcheck: load_images.sh:25:75: warning: sudo doesn't affect redirects. Use .. | sudo tee -a file [SC2024]
sudo echo foo >> /etc/foo won't work,
the >> will be run in the current shell,
replace with:
echo foo | sudo tee -a /etc/foo
shellcheck: load_images.sh:47:15: warning: Declare and assign separately to avoid masking return values. [SC2155]
replace local cmd='a' with two line version
shellcheck: load_images.sh:141:32: error: [ .. ] can't match globs. Use [[ .. ]] or grep. [SC2081]
use [[ ]]
Change-Id: I14d9768612ea147eaf139603f7eb8753e979ba2c
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
(cherry picked from commit 892d2e536e46a6e6427c061931c58f80b542589d)
|
|
Vivid is end of life, and thus not supported.
Change-Id: Ia293fcd6fd2a3279a642a6dbbb7ad1811334c3e1
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
(cherry picked from commit 14172bb39e8e30f37ec5bb80be6b187ab6858e88)
|
|
fixes for shellcheck warning
ubuntu-server-cloudimg-modify.sh:51:23: warning: Quote this to prevent word splitting. [SC2046]
ubuntu-server-cloudimg-modify.sh:51:30: note: Double quote to prevent globbing and word splitting. [SC2086]
Change-Id: I6cff0713a0471e5ce94211d42a7c8b45e3761c4d
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
(cherry picked from commit 8a2b7cdb29ff6a56d06e8f83fc098def40e1ed51)
|
|
|
|
During recent rework, we lost the explicit copy of qemu-aarch64-static
from docker to chroot; so when trying to execute AArch64 binaries
inside chroot, no emulator was present to handle it.
This change brings back (inside chroot) the missing emulator binary.
JIRA: YARDSTICK-595
Change-Id: I146e2eeec2e9452a0db36f0bf0a466a8affc2005
Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
(cherry picked from commit 742ee6f3249a6204a351fe02c1334c9b14213e51)
|
|
JIRA: YARDSTICK-594
Change-Id: Ieaf13a875d00c279d4da57dcdba5bcfb09f44e8f
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit f83a3a15d16333c422ba15b745e94d64712d73bb)
|
|
qemu-user-static from Trusty crashes when ssl is used in chroot.
JIRA: YARDSTICK-592
Change-Id: I81e8f04d7469082ceb6512cb09e11dfa672e5e98
Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
(cherry picked from commit 9d9925c30e9c7ad477041c28251b411432457568)
|
|
JIRA: YARDSTICK-598
As we have replaced 'glance image-create' command with 'openstack image create'
command, we also need to update the disk-format for openstack CLI. the
'root-tar' is no longer a valid choice. (choose from 'ami', 'ari', 'aki',
'vhd', 'vmdk', 'raw', 'qcow2', 'vhdx', 'vdi', 'iso', 'ploop')
Change-Id: I53f839f658c5a6f216f5bb942b1c4f4dcdbf9814
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit d64fbf2f276a98a7cc37d92c57f5b7f3517286b8)
|
|
|
|
|
|
MD5 is broken and should not be used
Change-Id: Ib168932387f58f0a538d865f8ef4e3cda046a35a
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
(cherry picked from commit fe655f15b0838b41c8c91543898ceebf23f1494c)
|
|
return True
JIRA: YARDSTICK-600
Bugfix: netperf_bottleneck execute failed because is_same_heat_context return True
So it exit without warning.
I will remove the 'return True' from it.
Change-Id: I48d62bd15ec359e2121f236c48d9d349174f2c10
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-589
Change-Id: I1690d4e2bd741fe1514c8496ee6ff10b72158859
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit f7371c36ff26ae9a8f526d0b76d13020a2239a23)
|
|
JIRA: YARDSTICK-573
Since the yardstick framework now has supported an improved node type context,
this patch adds support for VM vcpu pinning ability in the node type context.
It provides several scripts that can be used to configurate the controller and
compute nodes.
Change-Id: If2c6e7b1b85ff78b9d2a5997bf03bdc6877aaf74
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit f138b480ea4c9954d107555d7a46ec3d4375653f)
|
|
JIRA: YARDSTICK-574
Since the yardstick framework now has supported an improved node type context,
this patch adds support for VM NUMA pinning ability in the node type context.
It provides several scripts that can be used to configurate the controller and
compute nodes
Change-Id: If5eafdca6df1b1196bc17bfdd12aea9f4016752f
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit be4fad1e486f6c4bf993335f0aecaa3682a37da8)
|
|
JIRA: YARDSTICK-589
Some new scenarios, e.g, opnfv_k8-nosdn-nofeature-noha_daily, have been added
in the Danube release, test suite files for these scenarios should be added.
Change-Id: If3f4ef233b7b1516e182ed28f15feece1728e6d9
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 94d0c6200c8f39988911eedffea703f8b4737fcf)
|