Age | Commit message (Collapse) | Author | Files | Lines |
|
opnfv_yardstick_tc027.yaml 's configure file is written for physical pod
it shouldn't be added into virtual pod task, so remove it. otherwise, task will failed
Change-Id: Ic2f03c6522cace32426a7aade1da56ed2c1766d1
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit ab99b83b03f3583c51c03fc821d48b77e2bd2273)
|
|
as we discussed yersterday, for daily jenkins task,
i have a new idea, i add a precondition check and a key parameter in test case,
if environment info(eg. "DEPLOY_SCENARIO") meet the preconditon which was defined in test case ,
this test case will run, if not meet, this test case will skip.
and default is allow all test case to run, so this patch will not influence existing test case.
any comments are welcomed
Change-Id: I4300ac58994d51c0ddb4dd6d58b7191f796ddcee
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit ff5cb9501b155e07fe75f03062217270b9745131)
|
|
JIRA: -
Change-Id: Ibc44bf11fb8bef4878ec57187877624a557f9937
Signed-off-by: QiLiang <liangqi1@huawei.com>
(cherry picked from commit 556a2f2226391043eee47acb5163adfc8342e157)
|
|
Change-Id: Id4c8b1bc05e768bdb2b8f17798f13f4d83dcd9d6
Signed-off-by: Ricardo Noriega <ricardo.noriega.de.soto@ericsson.com>
(cherry picked from commit 805aaa50d226e8c91b69af0252aef68eda1551c3)
|
|
JIRA: -
Change-Id: I0cd58a2acb0a2a55431eebd6b4adcde95d50d7bc
Signed-off-by: QiLiang <liangqi1@huawei.com>
(cherry picked from commit 22e55a637eb9fe70fbb378494242f5f6f196f3c0)
|
|
Change-Id: Ia3760a4fcc17f810940240d1778939333e8ffdc6
Signed-off-by: wym_libra <yimin.wang@huawei.com>
(cherry picked from commit c8ea364de2f2d7bb4703f4beb86897c23dc88c39)
|
|
Test Case 040 :parser is added into weekly yaml
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Change-Id: I0cb4a9e273b5cac55b9a7a278ea17b1ad78d1ac6
|
|
Change-Id: I6587794b7206cb3d5f13b6c448670d1c97ecd596
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit cfbefd9ad48e07a1890e022e94cbae117e04f87a)
|
|
Change-Id: I4609fcb4427413fd6cde435f7bd062c9dde61949
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Added TC 10, 11 and 14.
Removed TC 1 as it is already included in TC 37
Change-Id: Iea483c4a26c657984769400f2949ca300c2504bd
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit 2a2ebe6b1ea2ff317f4a3ca6a8e8fab811350eae)
|
|
JIRA:YARDSTICK-187
Change-Id: Ia15d17afdef145f7b230a8a4d25a61eed5cdfd76
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Add test case description for Packet delay variation between VMs (TC011)
and test case .yaml task file.
** Please note that the SLA value has not yet been determined. **
Change-Id: I68a374224946d46c173ad477c14cb79d573b1eee
Signed-off-by: wym_libra <yimin.wang@huawei.com>
(cherry picked from commit 09c6f91228759e22a08bd9344962d65c1818e6b3)
|
|
In Heat Liberty release OS::Nova::Server will always use the user
pre-configured in the image (e.g. "fedora" for stock Fedora cloud
images, "ubuntu" for stock Ubuntu cloud images, "cloud-user" for
stock CentOS cloud images etc)
Change all ec2-user -> ubuntu
Add admin-user in Heat model for backwards compatibility.
Refer below links for detalis:
https://etherpad.opnfv.org/p/yardstick_release_b_troubleshooting
https://github.com/openstack/heat/commit/e423bec7f10b0f5d07f05d195b3b7860f6bceb00
http://blog.scottlowe.org/2015/04/23/ubuntu-openstack-heat-cloud-init/
JIRA: -
Change-Id: I6b8b2b21daf113a3a86aee1126b0c3e74737ef4f
Signed-off-by: QiLiang <liangqi1@huawei.com>
(cherry picked from commit 9d36842e3966185e97cc5732aa7a0edd2050bfe2)
|
|
Change-Id: I667a54793be39c74a9f787b055b07fda9b2ba06c
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit a6415b5199936de2eb247a26f18e47a368b82afa)
|
|
JIRA: YARDSTICK-219
Change-Id: I5f403e6c922f5e6ea790dc9cdb589cbc98e66ded
Signed-off-by: user <user@TRAFCLASS-PACKET1.fuel.local>
(cherry picked from commit 174560a6b7d4a23763564fcfc87c2dd7e60aa241)
|
|
Add test case description for Control node-OpenStack service down (TC019)
and test case .yaml task file.
** Please note that the SLA value has not yet been determined. **
JIRA: YARDSTICK-135
Change-Id: Id512159034929dc197d2c7fdf6cc672ecddfb996
Signed-off-by: wym_libra <yimin.wang@huawei.com>
(cherry picked from commit 32b39d0f576dc5c71678fd0b6b8feab6f2173939)
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: I0554d0a211392902207ba9ceccf0b98dc3c2cdf1
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
(cherry picked from commit e749d09788edbd1040dabb082e13bd1a1cbc3a7a)
|
|
Change-Id: Id557b5ef4d686da041b8097e390c7e5b563a0c3c
JIRA:-
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit 2b0c67e7b5984e200b92c134510e7e112cf30a35)
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: Ibbba1d9864e788fb6c81cc00c503e9f69e885651
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
(cherry picked from commit 884e58ab48d0dcdc5e57b87ea181c0a4b8151fc8)
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: Ifa2555336098e68d0fad8045e2f759aed587ad92
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
(cherry picked from commit bde7eae17a1fc9ec163451b8d62825daa2fec297)
|
|
Includes
- Yardstick Scenario for integration with ApexLake
- Yardstick Task .yaml file
- Documentation
JIRA: YARDSTICK-219
Change-Id: Iabde8fa63f346cf1e4a02691f22d1761de79a239
Signed-off-by: Vincenzo Riccobene <vincenzox.m.riccobene@intel.com>
(cherry picked from commit 6f6ed9af46d616b073481799c157ed3bc88a8810)
|
|
Test case yaml and .rst file for ipv6
Change-Id: Ib9a554dc05445023687efb0ac608c7cbd0da4c21
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
run unixbench to get the score of processing performance
This patch includes the .yaml for the test case and the .rst for test case description.
JIRA:YARDSTICK-116
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Change-Id: Ic75119d1db19dacc57edfa4dce607e0e29ae8db4
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit db643f9a2a416c0888931a347488a51264350c8f)
|
|
running Parser Yang-to-Tosca module as a tool, validating output against expected outcome.
this patch is about task yaml and rst for test case description.
JIRA:YARDSTICK-224
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Change-Id: Id254c5cf45de33b023bef889a58044a21ed0db43
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit 45e85a7f6df63ca4ca702f519ca19e5bcbb1bc23)
|
|
Change-Id: I299eb5a94afb8a29dee89938ff1d7b1bb7f43f3b
JIRA:-
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit 7766def60d167a55e4a0fbbb3d94e5bfe6241e08)
|
|
JIRA: YARDSTICK-93
Change-Id: I74adef0e6bae52a7080479d7054a92342f7324a7
Signed-off-by: QiLiang <liangqi1@huawei.com>
(cherry picked from commit 738fb0942c39e5f1ecad87ae9dd776f1019d2491)
|
|
JIRA: YARDSTICK-122
Change-Id: I8144215059a9abea08314a4c1e6a733dcdf0df53
Signed-off-by: QiLiang <liangqi1@huawei.com>
(cherry picked from commit a33f57371c740e0ab749bfffa4d31c08ef5c5b74)
|
|
1) add "attacker_baremetal.py" for fault injection
2) modify the monitor to excute on remote node after ssh connection
3) move all shell scripts together
JIRA: YARDSTICK-182
Change-Id: Ibb9dc908224ddb8b99a0140b75c1a046503f6dfb
Signed-off-by: wym_libra <yimin.wang@huawei.com>
(cherry picked from commit 4f4edd840823ff6a0151e3f5220241183e27e560)
|
|
idea: refact the Monitor class in old file "monitor.py" with the base
class and sub-class.
detail:
1) the BaseMonitor is the base class of other monitor
2) each monitor run in independent process
3) there are two monitor("openstack-cmd" and "process") for the first test case
4) MonitorMgr class used to manager monitor process
JIRA: YARDSTICK-149
Change-Id: I2eede94481f740812212e6cb673d175b5f543c15
Signed-off-by: wym_libra <yimin.wang@huawei.com>
(cherry picked from commit 2733defda816a84d2b9c2e361a5970b9de4923f4)
|
|
with jnon and fatih's help, new docker image has been uploaded
so this part is about parser verify
validating output against expected outcome.
Change-Id: If50d241a5338888f14fd11a752dc72678e0c569b
JIRA:YARDSTICK-224
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit d93f6ca5bf0d4f22ec0fd90eac1bf8b9c09db820)
|
|
JIRA: YARDSTICK-213
Change-Id: I55ff36b02a0d0e0334505d68d361b8a14d36063c
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit 45b1cc64209dec07475e5263469328231c524aa7)
|
|
JIRA:YARDSTICK-187
Change-Id: I1cecd400b4449a09d22d43f4a42e889f00dd4fe7
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit cd80b44f3fd9b8c9e2afc51bc67d7a5cf34fb1c6)
|
|
JIRA: YARDSTICK-214
Change-Id: I3a2358e8c36755a684f09524bd6fc8af9bf43f60
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit c27b74456831c0f7c827b4840649a898d66cd52f)
|
|
JIRA: YARDSTICK-213
Change-Id: I3f1f521da6a824c96cbc8712a098c61ff6b0540d
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
(cherry picked from commit 605d252b9c72c0d41a720c45774d4481bb902c77)
|
|
- add runner_id tag
- add test case name tag
- add task_id tag
JIRA: YARDSTICK-212
Change-Id: I75c27e23942a6e2189019e94bfe8026a5fd67621
Signed-off-by: QiLiang <liangqi1@huawei.com>
Conflicts:
yardstick/dispatcher/influxdb.py
(cherry picked from commit 65e32e513544392ce84c190434d23281b5c1afd2)
Change-Id: Idcd582f96f2813e04d80a8c0677d9124b373fb48
|
|
Supports:
- Basic influxDB write with timestamp
- Add general result format func
- Add UT
TODO:
- refine database schema (e.g. add more tags) plan in another patch
JIRA: YARDSTICK-212
Change-Id: I1526568bbd850f1343135420ec59ed1b833bb99f
Signed-off-by: QiLiang <liangqi1@huawei.com>
(cherry picked from commit 99ba990d4a01c0f3f4837f11a24b695f4a2393d2)
|
|
opnfv-jump-1: apex stable/brahmaputra branch
intel-pod5: joid stable/brahmaputra branch
intel-pod2: apex master branch
intel-pod6: joid master branch
intel-pod8: compass master branch
Change-Id: Ia659e10525863ee11854a266df58449c625c7f7c
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: yardstick-210
Change-Id: Ib888b654e742761a8be1b263f643950ea02380f8
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Dummy Context Usage:
- if no context specified in the task file then automatically use
Dummy Context
- or specify the context with type Dummy in the task file, like
context:
type: Dummy
Note: context without type name default use Heat Context.
(e.g. samples/fio.yaml)
JIRA: -
Change-Id: I7f798a7260bdd6ac24902e2c835a3b121319fd8c
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
JIRA:YARDSTICK-184
Change-Id: Iedd4a3708e08305b1c8fa7a8e1766ceef03ab8bb
Signed-off-by: kubi <jean.gaoliang@huawei.com>
|
|
Add test case description for Memory Latency (TC010) and test case
.yaml task file.
JIRA: YARDSTICK-94
Change-Id: If7fb120868c9901fe097f310aa249e1fbc8a94ee
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|
|
Change-Id: Ic0f7261dc07eb38d014a8790ac13e5310ec4ef8a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Similar to Yardstick TC001. Main difference is that each packet size
is run 10 times before next packet size.
JIRA: YARDSTICK-87
Change-Id: If0f59590dff9c8e5b86760667f01a373afe8aff0
|
|
New test case using pktgen tool. Based on TC001, but with additional
packet sizes and more repetitions of each test combination,
respectively. Test case takes approx.3 hours to complete.
Change-Id: Iba2de5efa33d6e2c960772fa5345595f6d7ab4e6
JIRA: YARDSTICK-80
|
|
refactor the attacker implement.
1) BaseAttacker is added
2) a simple attacker named "kill-process" inherit the BaseAttacker
3) serviceha.py selects an attacker through the BaseAttacker by attacker name
JIRA: YARDSTICK-149
Change-Id: Ib718d5edc6b5e14bc3ea0592e0146468ff70b43e
Signed-off-by: wym_libra <yimin.wang@huawei.com>
|
|
Change-Id: I39d589bfc0652d51b7e6d9e139b83160bf7f3692
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
This change adds the possibility to run scenarios as "background
tasks".
Background scenarios/tasks:
- are started before all "normal scenarios"
- runs in parallel with "normal scenarios"
- terminates when all "normal scenarios" have completed
their tasks
They are intended as a way to perform background tasks, e.g. collect
data such as cpuload etc, in parallel with the execution of normal
benchmarking scenarios.
Note that we already have the 'run_in_parallel' attribute but
this attribute has a couple of issues and do not solve all the
uses cases.
Change-Id: I9c5230bfdbbb66030f57b658ce1db87ff2c2d62b
Signed-off-by: Jo¶rgen Karlsson <jorgen.w.karlsson@ericsson.com>
|
|
Add test case description for Memory Bandwidth (TC012) and test case
.yaml task file.
JIRA: YARDSTICK-113
Change-Id: I6f2b0bb8c920f3ece3a41bac744cc1ec1fd35cbc
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
|
|
This commit contains almost all of Jira #79. Misses still to collect
all results in one single .json file, now everything is written to
/tmp/yardstick.out. However, this may not be needed at all once the
database for test result collection is in place.
Change-Id: I210a477c3b5a110e97a6220e68d3ddc31ccce93a
JIRA: YARDSTICK-79
|