Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ie03dfe7d1227578bb50e5e4460e50b9dc59dd202
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-791
In some use cases, Fio is used with a job file instead of parameters.
This work is about adding support for the job file and add a new test case
for volume testing.
Change-Id: I312d61bf6e7d95f23eedb0b6487f6103b7d76355
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
apexlake is unmaintained, so remove it
From some reason orchestrator/heat.py started failing
so fixup those unittests
Change-Id: Ie06508b5ab7c9dcf9fdfca83e173a188a894d564
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093
Signed-off-by: Deepak S <deepak.s@linux.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>
|
|
Montreal testbed
Change-Id: Icd4d56de8bd60b2b4333459ce8669363ba54a33b
Signed-off-by: user <user@TRAFCLASS-PACKET1.fuel.local>
|
|
JIRA: YARDSTICK-219
Change-Id: I5f403e6c922f5e6ea790dc9cdb589cbc98e66ded
Signed-off-by: user <user@TRAFCLASS-PACKET1.fuel.local>
|
|
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>
|