Age | Commit message (Collapse) | Author | Files | Lines |
|
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-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)
|
|
JIRA: YARDSTICK-593
The yardstick-image now built dosen't have test tools in it.
This patch aims to fix this issus.
Change-Id: I9863a933106236835c16e21f84aa107ffd554df7
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit bd90c394fe223c5d465d70fb24076ef1d9258c91)
|
|
|
|
Change-Id: Ie17ba0ac941d1b96148ee23ed9522a93309f56c5
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
empty directory.
JIRA: YARDSTICK-588
ubuntu-server-cloudimg-modify.sh: fixes and cleanup
https://build.opnfv.org/ci/view/fuel/job/yardstick-fuel-virtual-daily-master/1233/console
saw this in an error log, not sure if it is a real error
+ [[ amd64 = \a\r\m\6\4 ]]
+ git clone https://github.com/kdlucas/byte-unixbench.git /opt/tempT
fatal: destination path '/opt/tempT' already exists and is not an empty
directory.
+ error_trap
+ local rc=128
+ set +e
+ '[' -z '' ']'
+ exitcode=128
workaround by deletign /opt/tempT always before cloning
also improve ln with relative symlink and forcing filename target
Change-Id: Ia9c35a877207494623055b1b2134f7834fadedf8
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
(cherry picked from commit f31b7d56c07c17607df605aacc9b60bf786428e0)
|
|
JIRA: YARDSTICK-586
When run tc072, there is a bug: network_utilization: parse error, see the log:
ERROR ('network_utilization: parse error', [], [u'05:10:46', u'IFACE',
u'rxpck/s', u'txpck/s', u'rxkB/s', u'txkB/s', u'rxcmp/s',
u'txcmp/s', u'rxmcst/s', u'%ifutil'])
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/runners/duration.py",
line 69, in _worker_process
method(data)
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/networking/netutilization.py",
line 191, in run
result.update(self._get_network_utilization())
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/networking/netutilization.py",
line 182, in _get_network_utilization
result = self._filtrate_result(raw_result)
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/networking/netutilization.py",
line 146, in _filtrate_result
fields, line)
RuntimeError: ('network_utilization: parse error', [], [u'05:10:46',
u'IFACE', u'rxpck/s', u'txpck/s', u'rxkB/s', u'txkB/s',
u'rxcmp/s', u'txcmp/s', u'rxmcst/s', u'%ifutil'])
Maybe the tool has some changes.
Change-Id: I6c4fe3fe9f749ec942fb5fbd799b8f4ab9a5c16c
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-587
When run in https environment, there is a bug:
error: failed to deploy stack: '_init_() got an unexpected keyword argument 'ca_cert''
The reason is the key pass to Session() is cacert, but the key should be
verify.
Change-Id: Ia9fc1d7908c2fca9d827a5f64deac7cd333d5c07
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
(cherry picked from commit 747e3c5f8a882b07b6876aae61c84d05a8b832f4)
|
|
|
|
|
|
Updating the trex version and downloading the right version for vnf testing :)
Change-Id: Iaca74ce627a05128a60bdc331968d2c56c06522f
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
load_images.sh arm64 change had issue with shell
load_images.sh: line 34: [: amd64=: unary operator expected
https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/894/console
Change-Id: I14f0b8628db7ac90a4966f85e9e7e27a0e0fae02
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: YARDSTICK-585
In CI when run tc070, there is a error: Failed executing command: 'free -s 1 -c 10'
Here it is the log:
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/runners/duration.py",
line 69, in _worker_process
method(data)
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/compute/memload.py",
line 126, in run
result.update(self._get_mem_usage())
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/compute/memload.py",
line 116, in _get_mem_usage
result = self._execute_command(cmd)
File
"/usr/local/lib/python2.7/dist-packages/yardstick/benchmark/scenarios/compute/memload.py",
line 70, in _execute_command
cmd, stderr)
RuntimeError: ('Failed executing command: ', 'free -s 1 -c 10',u"free: seconds argument `1' failed\n")
And it is a bug of free. the -c option should in front of -s, so change the position will solve
this problem.
Also it has another bug:
'KeyError', there no 'cached' keyword, so I change it to 'buff/cache'.
Change-Id: I0ca16e8d8cc11c6a3b2f364cadbdb3ea367eee53
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
using API in parallel"
|
|
isinstance allows for matching with list and dict subclasses
as well and list and dict themselves
Use collections.Mapping for dict
We still have to use list, because iterable is too generic,
strings are iterable for example.
use dict literal for point
fix logging to use deferred interpolation
Change-Id: I4c9b27fd07b57139e86315e39f58d54cc18e402d
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
in parallel
JIRA: YARDSTICK-575
Currently yardstick will create stacks with the same name when run using
API in parallel.
The reason is there is a global variable in context base and the core
will always deploy the first context in Context.list. When run in
parallel, it will run in the one process. So yardstick will deploy
stacks with the same name.
The solution is do not use Context.list in yardstick core. And using a
local variable instead.
BTW, if we use API to call yardstick core, we can not config the output
way. So I parse yardstick.conf when task start. And I think we can
include scenario_cfg, context_cfg, yardstick_cfg in one config object
later so that we can get all config in one object.
Change-Id: I1ada4ef486bd252e78c3a2e49c6a39b3f8f16a7c
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
It looks like jsonutils.load uses a codec reader
to read from the file, but we already are using
Python 3.5 open() which should already do the UTF-8
decode itself.
return json.load(codecs.getreader(encoding)(fp), **kwargs)C
When we use jsonutils.load() we get a TypeErorr when concating
str and bytes
2017-02-28 16:42:38,431 yardstick.cmd.commands.task task.py:61 ERROR
Traceback (most recent call last):
File "yardstick/yardstick/cmd/commands/task.py", line 58, in do_start
self._finish()
File "yardstick/yardstick/cmd/commands/task.py", line 69, in _finish
result = read_json_from_file(self.output_file).get('result')
File "yardstick/yardstick/common/utils.py", line 136, in read_json_from_file
return jsonutils.load(f)
File "yardstick_venv3/lib/python3.5/site-packages/oslo_serialization/jsonutils.py", line 241, in load
return json.load(codecs.getreader(encoding)(fp), **kwargs)
File "/usr/lib/python3.5/json/__init__.py", line 265, in load
return loads(fp.read(),
File "yardstick_venv3/lib/python3.5/codecs.py", line 497, in read
data = self.bytebuffer + newdata
TypeError: can't concat bytes to str
So switch back to jsonutils.loads() which does nothing if the
bytes are already decoded.
JIRA: YARDSTICK-584
Change-Id: I36acfda3df2b46d16a87f2741a04fe7ee8e8d89b
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|