Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
JIRA: YARDSTICK-635
Change-Id: Ic27517714db9325e7a3b1ef623c49af61c36b2b5
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
JIRA: YARDSTICK-633
Change-Id: I65fd1ba11504dc61485f83c3bcc93bec4d41883b
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
Change-Id: Ib38e94610a108ff7195cefdfaf048e0f4fd894e8
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
JIRA: YARDSTICK-628
Change-Id: I7d1b84232a7477a2854ef1625cc63521999eff65
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
A generic provider network solution is introduced. To identify whether a network specified in the test case is a provider network new attributes are introduced in the test case network section:
networks:
test-net:
cidr: '192.168.1.0/24'
provider: "sriov"
physical_network: 'physnet1'
If the "provider" attribute is present, the network is an existing provider network. If the value is "sriov", binding:vnic_type=direct is added to the interface in the heat deployment template. In orchestrator/heat.py, the interface creating functions are given a new parameter that tells if the network in use is a provider network. The benchmark/contexts/model.py is changed to store the value of the provider attribute from the test case and function calls to port creation is updated with the provider parameter. The same change is made in contexts/heat.py as well. Also calls for creating a new tenant network is replaced for creating a new provider network if the provider attribute is present.
Update-1: Change test_model.py
Update-2: Per comment, change comment style to """"
Update-3: Change test_heat.py
Update-4: Add unit test cases to pass coverage test
Update-5: Add SRIOV provider network example in opnfv_yardstick_tc008.yaml
Update-6: Per comment, remove empty line in orchestrator/test_heat.py
Update-7: Per comment, change comment lines in orchestrator/test_heat.py
Update-8: Add more unit test cases to pass coverage test
Update-9: Change to create SRIOV provider network on the fly so as to support co-current test runs
Update-10: Per comment, init physical_network to 'physnet1'
Change-Id: I76004c4fcc9bffcfd8ed021fd647e0cecb346ef4
JIRA: YARDSTICK-612
Signed-off-by: Jing Zhang <jing.c.zhang@nokia.com>
|
|
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>
|
|
|
|
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>
|
|
Change-Id: Iffa1e4529e5b6e9664ac503a5815ea9a034d7515
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093
Signed-off-by: Deepak S <deepak.s@linux.intel.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>
|
|
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-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-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-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>
|
|
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-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>
|
|
Change-Id: I4dee79252f909a0c201834ae9b05c9af98213ad7
Signed-off-by: wangwulin <wangwulin@huawei.com>
|
|
Change-Id: I9d62fc93bb37c58e374a93081a338b00ddd1305a
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Change-Id: Ib8329f6feeadacb312171782730ef2807eda5455
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
Change-Id: Icbe2815c0fd0890c579d49a4180854ceb7487ecf
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-287
Change-Id: I676c4401406503a016f829ec3691a006d329f941
Signed-off-by: tjuyinkanglin <14_ykl@tongji.edu.cn>
|
|
|
|
|
|
JIRA:YARDSTICK-233
Change-Id: I5fd879ceae7ec2bfaf75db50bdc0e8d3a1ec1f88
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|
|
also fix a bug about path to pod.yaml
also update test suites for TC063
also update 03-list-of-tcs.rst for TC063
Change-Id: I8fdacd109669e9998b10250a18c2c622cd72f0a1
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Change-Id: Ic495293d37b51b95009000559b451ef7c12cfcbe
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: Ie67985ebf28acc08cc53b312b4f90e65923b5fc4
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
Add task configration file for TC074_Storperf and update test suite file
Add test case description for TC074_Storperf
Update Dockerfile to add ubuntu image used by Storperf
Update yardstick-verify to load ubuntu image and install Storperf
Modify plugin.py to support local installation
Change-Id: I4de764c7924aac98de6e6a8664f9d5c0b58cf31b
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
|
|
|