Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
JIRA: YARDSTICK-1090
We have k8-nosdn-stor4nfv-ha/noha scenario in compass,
so we need to add this files to trigger it.
Change-Id: I79709c53b8542434f7324ad907fa95b4855839d3
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: I999b44cc4e0ec1029c6efca224e691298a007689
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
JIRA: YARDSTICK-1090
We have k8-nosdn-stor4nfv-ha/noha scenario in compass,
so we need to add this files to trigger it.
Change-Id: Iefa3a83407bff7d3c1de1959f35b6d8e5eecd145
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: YARDSTICK-1082
Change-Id: I00080d0317a54b73a6cd571198e9446962c11b5a
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-1046
Change-Id: I12223876d1cf1f3e45152f6b7996b75a66b16fe6
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
This testcase confirms the resiliency of Opendaylight
in a noHA deployment
SPEC: https://gerrit.opnfv.org/gerrit/#/c/49245/
Change-Id: I810011c35c7bb6377f9295330cf7122d10cf74c3
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
https://build.opnfv.org/ci/job/yardstick-joid-baremetal-daily-master/2206/console
Change-Id: Ib5fc186caa285ef8f6a879fd1fd2f786b07a257a
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
adding missing scenario for Apex.
https://gerrit.opnfv.org/gerrit/#/c/50045/
JIRA: YARDSTICK-998
Change-Id: I211f567587a4864b403ce321fea007a3c0963136
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
The opnfv_os-odl-fdio_dvr-noha_daily.yaml test suite file is wrongly put in Yardstick root directory,
this patch moves this file to the 'test_suites' directory.
Change-Id: Ib3f75845c7af658dc6f96ac2de737cfbd1faf15a
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-823
We need to create test sutie opnfv_os-nosdn-openbaton-ha_daily.yaml
to enable this scenario.
Change-Id: Ia800a9c74aaecf0d73e6f0fd559630b741ad2432
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
Change-Id: I35e6471bb561eb773bd188b36b912969188955d2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: I46c6b56e1293c3d594804d77a73c391922f03653
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: Ib2b165c41121b29b2af378dc420c2360786de3f0
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-814
Test suite:
"opnfv_os-odl-fdio-ha_daily.yaml",
"opnfv_os-odl-dvr-noha_daily.yaml",
"opnfv_os-odl-sfc-noha_daily.yaml"
are missing in yardstick-apex-baremetal-daily-euphrates job.
We need to create them.
Change-Id: I6d8bbeb17cd887776f1f3b401ec80523ea90d3c1
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: I723477edf810a220816a2e67aa80f7f144efb3a6
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
For now just copied and renamed opnfv_os-nosdn-nofeature-ha_daily.yaml
Change-Id: Idbd37a3e21220aa407d053157da71b449bad15ee
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Change-Id: I664437d598db9f9dcc7036e306b8a4edc40287cf
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: RDSTICK-811
We need to create opnfv_k8-ovn-lb-noha_daily.yaml so that we
can run kubernetes test in k8-ovn-lb-noha scenario.
Change-Id: I9c18b6d68c96ef917f3b65e494e3c2d9e1beefdd
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: Ib7cfb36d89551a187f5ee681454e61444a08c585
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: YARDSTICK-800
We have k8-nosdn-lb-noha scenario with kubernetes deployment.
So we need to add k8-nosdn-lb-noha test suite to run test case.
Change-Id: Id6dc73ad999733ddfa2e03673c20f7e92a8250a3
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: I56961d143bdd723f4e957a4c02ba4127ccddadb3
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-712
Change-Id: If91c936a3a59580a987cb6762db5d063edf6c9d7
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
In deployments with ODL, security groups behave badly because of an
IPv6 rule that causes IPv4 packets to be incorrectly routed.
This is described in:
https://jira.opnfv.org/browse/ARMBAND-61
As a consequence, Yardstick TC011 fails because iperf cannot
create a connection.
The proposed solution is to temporarily comment out TC011
from test suites with ODL.
As mentioned here, security groups support for IPv6 is partial:
artifacts.opnfv.org/ipv6/docs/gapanalysis/gap-analysis-odl-boron.html
On nosdn deployments this issue is not reproducing and the test runs ok.
JIRA: ARMBAND-269
Change-Id: Id5fede27262c21d777ec8e9988941643d16f9417
Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
|
|
JIRA: YARDSTICK-695
Change-Id: I826cb2ea07949b1eaae4df4cb77175ec8f5df89b
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-634
Change-Id: I586d5177598efeda8ac3937d1eb04cd5b97b6ec6
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-624
Change-Id: Ia783bec53e4d889736db7e510d28c32377d4f9b2
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
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>
|
|
JIRA: YARDSTICK-589
Change-Id: I1690d4e2bd741fe1514c8496ee6ff10b72158859
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
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>
|
|
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>
|
|
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-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-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>
|