Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: YARDSTICK-635
Change-Id: Ic27517714db9325e7a3b1ef623c49af61c36b2b5
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
(cherry picked from commit 2fb95fbb9380ea7ce92dcb32cd2f0789b9f91bdc)
|
|
JIRA: YARDSTICK-633
Change-Id: I65fd1ba11504dc61485f83c3bcc93bec4d41883b
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
(cherry picked from commit 27cc0643cf93f4b44c12fbdfcc3e0841d46214c4)
|
|
JIRA: YARDSTICK-634
Change-Id: I586d5177598efeda8ac3937d1eb04cd5b97b6ec6
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
(cherry picked from commit 5c4b29189bd69912c9bc356a15a46db764045537)
|
|
Change-Id: Ib38e94610a108ff7195cefdfaf048e0f4fd894e8
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 6604cb5f2d6e3c819cb8488f1ad3468184822cf9)
|
|
JIRA: YARDSTICK-628
Change-Id: I7d1b84232a7477a2854ef1625cc63521999eff65
Signed-off-by: xudan <xudan16@huawei.com>
(cherry picked from commit 3f7829f0f28ce4d517ea8654122ee0d686fddf3e)
|
|
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-624
Change-Id: Ia783bec53e4d889736db7e510d28c32377d4f9b2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit da47f4de9d57f40ecc7cedeac18c0d061bd21c84)
|
|
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: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
(cherry picked from commit 043727feabaf7cabb719dbd3d52274bcd0dbea66)
|
|
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-589
Change-Id: I1690d4e2bd741fe1514c8496ee6ff10b72158859
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit f7371c36ff26ae9a8f526d0b76d13020a2239a23)
|
|
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)
|
|
Change-Id: I46e4e21787a9b0a3104b2a684d62f50681258205
Signed-off-by: Romanos Skiadas <rski@intracom-telecom.com>
|
|
|
|
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
|
|
due to https://gerrit.opnfv.org/gerrit/#/c/27605/
os-odl_l2-bgpvpn-ha in apex has already been renamed to
be os-odl-bgpvpn-ha, so add a new one.
Change-Id: I167bf295b67b2dddbd3da2aa5a2dca666b3fa152
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
new scenario os-odl-gluon-noha in apex pod
Change-Id: I0151ce227e2a3ff476044f0b5c8d4ed61d20b21a
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
files and TC052
JIRA: YARDSTICK-547
Change-Id: Idde2dc56436c9cf4b8696bfd0056ab4e47c97c9a
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
have multiple commands: yardstick tc025, tc050 ,tc051, tc053, tc054"
|
|
multiple commands: yardstick tc025, tc050 ,tc051, tc053, tc054
JIRA: YARDSTICK-546
Change-Id: Id94b32f5e053f3f6a7c78980dce22b3aab7bbd13
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
JIRA: YARDSTICK-545
Change-Id: Ifd3348e029f0ddbfa0117b4eef4493d443a4de4d
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
JIRA: YARDSTICK-534
This test case uses nstat to monitor network metrics provided by the kernel in
a host and calculate IP datagram error rate, ICMP message error rate, TCP
segment error rate and UDP datagram error rate.
Change-Id: I2fe6457bb5c95d0446c1463991ae31cc664b09f8
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
This patch implements test suites for kvmfornfv os-nosdn-kvm_ovs_dpdk_bar-ha
and os-nosdn-kvm_ovs_dpdk_bar-noha scenarios.
Change-Id: Idb7d360aa5b91a15d1c69566418a9da4b68db7ab
Signed-off-by: Navya Bathula <navyax.bathula@intel.com>
|
|
This patch implements test suites for kvmfornfv os-nosdn-kvm_ovs_dpdk-ha
and os-nosdn-kvm_ovs_dpdk-noha scenarios.
Change-Id: Ia7b17dda262df5d81cac87372b70510192044a40
Co-Authored-By: Navya <b.navya4@tcs.com>
Signed-off-by: KalyanReddy <reddyx.gundarapu@intel.com>
|
|
JIRA: YARDSTICK-456
Currently we do not have a API to get a list of all test cases;
Currently the test case info is from the comment;
So I create a API to get a list of all test cases;
And create a 'description' attribute to record info of a test case;
And use the CLI call this API;
Change-Id: Ife800600446683664097835c7b9f11899c85771d
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
JIRA: YARDSTICK-485
In OpenStack Newton, the 'm1.tiny', 'm1.small', 'm1.medium' and 'm1.large' will
not be automatic created. This may cause errors as some Yardstick testcases are
using one of these flavor. Therefore, it's better change all the flavor option
in task configuration file to 'yardstick-flavor'.
Change-Id: Ibb29a77ef331bbf728dec9894a2e9f17c19d5ebd
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-417
This patch adds a smoke test suite for Yardstick. The smoke test suite consists
of 3 test cases: TC002 Ping, TC005 Fio, TC012 LMbench.
3 test suites for components, features and performance tiers are also provided.
Change-Id: Ic5223c1401270d126aabb4bf062e40da9464e18f
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
|
|
JIRA: YARDSTICK-365
This patch upgrades the base Ubuntu version of Yardstick VM image from
trusty(14.04) to xenial(16.04).
If you still want to use Ubuntu 14.04 to build Yardstick custom image you can
use command:
sudo ./tools/yardstick-img-modify tools/ubuntu-server-cloudimg-modify.sh trusty
And now the "yardstick-trusty-server" is rename as "yardstick-image".
Change-Id: I0765f3aee2d17eea1ad2257d0f576cdb9ef2b18d
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-363
Change-Id: Ic0186cd0678277b0b1b04a57a322f6193c1cf52e
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-373
Change-Id: Ia06ec788c50098cec0c22c6fb1eec97d7a4c9031
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
JIRA: YARDSTICK-363
Change-Id: I5f1c8b1f0038619102aa6e446853988093172d9c
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-325
This patch removes ping_lxd_test.yaml and changes vm image used for lxd senarios.
In the *-lxd-* scenariois, Cirros LXC 0.3 image will be used for Ping test case.
For yardstick generic test, a dedicated yardstick vm image will be used.
Change-Id: I5f9e7a92e3e5dded0014baec77085d80cc904b52
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-325
This patch adds a ping_lxd_test TC. ping_lxd_test is a dedicated ping test case for lxd scenarios.
It uses Cirros LXC 0.3 image to test the image requirement of lxd.
Change-Id: I11dce7ee884cfb0f151d3a60daf7ac82226956a3
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-363
1. fuel pod.yaml node id update according to the real environment
2. add constaints to run ipv6 on one fuel physical pod(lf-pod2)
Change-Id: I5b91f1bea84f2c79e0b9c3195028e38ddad55363
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-358
1. plan to support fuel first
2. apex/joid situation will be taken care of
in another patch
Change-Id: Ia9293a2e925d874cc6182e975f563d92fb91a2c7
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
opnfv_os-nosdn-fdio-noha_daily.yaml scenarios along with support for hugepages which is needed for these scenarios"
|
|
opnfv_os-nosdn-fdio-noha_daily.yaml scenarios along with support for hugepages which is needed for these scenarios
JIRA: YARDSTICK-347
Change-Id: Ie4840b328393488fb8e118c3f2cd610d61fdc283
Signed-off-by: juraj.linkes <jlinkes@cisco.com>
|
|
JIRA: YARDSTICK-270
1)description info amended according to really tested
2)hyper-thread status check added
Change-Id: I813a41ff1e55c2d816fa55b773cf6c4bdd2af2bd
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: YARDSTICK-348
Change-Id: I42751980bb33782da3fa33a9d4f110da153737dc
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
JIRA: YARDSTICK-344
In some cases, m1.tiny is too small to boot a VM instance.
So this patch changes m1.tiny to yardstick-flavor.
Change-Id: I2970717d934adcf764aea576087c1aed55e377fe
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-342
Change-Id: I5341f377425042b459bd15d623903c8674a3075a
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|