summaryrefslogtreecommitdiffstats
path: root/etc/conf/yardstick_config.yml
AgeCommit message (Collapse)AuthorFilesLines
2019-02-01Add ONAP VVP Heat Template validation testsStamatis Katsaounis1-0/+1
Change-Id: I9a3d56932ce41191901381831013768d1c57a749 Signed-off-by: Stamatis Katsaounis <mokats@intracom-telecom.com>
2018-12-20Simplify project conf filesxudan1-7/+4
1. use copy commands instead of pre_copy 2. remove redundant items in project conf files 3. make the volume mapping clearer Change-Id: I6c6aa58fac65d7e40105e0a54f6544ee5c47db31 Signed-off-by: xudan <xudan16@huawei.com>
2018-11-23Integrate k8s test cassesxudan1-7/+23
In order to integrate k8s test cases, Dovetail framework should do some refactor and make it more general for k8s test cases as well as ONAP ones. Integrate 2 k8s test cases. JIRA: DOVETAIL-748 Change-Id: Ibd87754ffb5fb29f6b4ce79232af860c2ed2da9c Signed-off-by: xudan <xudan16@huawei.com>
2018-10-11Change to Gambia version by using latest docker imagesxudan1-1/+1
Functest use gambia tag. Other projects use their latest one. Change-Id: Ibbfde50727149822d8331d998f6b4e173f19e244 Signed-off-by: xudan <xudan16@huawei.com>
2018-09-21Updating the container tags of the test projectsGeorg Kunz1-1/+1
Setting the container versions of the test tools to a specific release tag. Change-Id: I3422be006ff80035cecc9ec22eba50b02ed97be6 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-07-03Adapt Yardstick fraserxudan1-3/+3
Yardstick fraser has changed from openstack python client to shade. OS_INSECURE is not a key for shade. It needs to be OS_VERIFY. Change-Id: I0973853d0527b04ec371ad4f6ce2f6c67ef50ccf Signed-off-by: xudan <xudan16@huawei.com>
2018-05-27Archive all test case result filesxudan1-1/+0
1. All detailed tempest test cases results are recorded with file tempest-report.html rather than tempest.log now. 2. Archive all results files include functest.log, yardstick.log ... for each test case. Otherwise, they will all be in one log file. 3. Support to set the source files and dest files need to be archived with the test case config files rather than hardcode with the source code. 4. Give the file which used to be parse the results (PASS/FAIL) with the test case config files rather than hardcode with the source code. Change-Id: I30f435d91ab90cf20def47007f177fe98187484d Signed-off-by: xudan <xudan16@huawei.com>
2018-05-17Adding OpenStack controller database HA test caseGeorg Kunz1-4/+0
Adding the OpenStack controller database HA test case (Yardstick tc090) to Dovetail and the proposed_tests test suite. JIRA: DOVETAIL-654 Change-Id: I4d20b907de8df2e9567891354b49e832cce13c7c Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-04Remove local DBxudan1-1/+1
Remove local DB and can just report without launch local DB. Need to do a little modification with the web portal code. JIRA: DOVETAIL-593 Change-Id: I595db39cce4156596ee0522d4b7e642a23d78ab9 Signed-off-by: xudan <xudan16@huawei.com>
2018-04-17Switch to OPNFV Fraser releasexudan1-1/+1
1. Use Functest Fraser docker images whose tag is fraser 2. Use Yardstick stable docker images 3. Functest fraser has moved testcases.yaml file from functest/ci to xtesting/ci 4. Functest fraser has removed 'functest env prepare' command 5. Functest uses rally to execute osinterop test cases instead of refstack_client Change-Id: I81ebefe6ea959ca77c2c87f1d75ef56ac18c165f Signed-off-by: xudan <xudan16@huawei.com>
2018-04-10Decoupling Yardstick Docker config items from source codexudan1-8/+12
There are some special Docker setting items when creating Yardstick Docker Containers. 1. Remove the extra settings which are required by Yardstick Danube. 2. Remove the settings for pushing results to DB because Dovetail plan to disable this function. 3. Move the other special Functest settings to config files. JIRA: DOVETAIL-640 Change-Id: Ic2d90393e227d7886b14d805eaa307b7aef56e4a Signed-off-by: xudan <xudan16@huawei.com>
2018-03-14Add process info to pod.yaml to specify the info of a special processxudan1-1/+9
1. Many HA test cases try to kill special processes with their name. 2. Then they check corresponding openstack services and the status of processes' recovery. 3. For different SUTs, the names of the processes and the hosts' names may be different. 4. So there is a requirement for Dovetail tool to provide one way to allow users to specify all the infos about process name and its host name. 5. All process infos can be added into file DOVETAIL_HOME/user_config/pod.yaml 6. The infos include 'attack_process' and 'attack_host' for each HA test cases. 7. If not given in this file, will use Yardtsick default values. JIRA: DOVETAIL-627 Change-Id: I83cee991f72a8685080ed562597c70d73002623a Signed-off-by: xudan <xudan16@huawei.com>
2018-03-06leverage data_files to eliminate so many hardcoded abs_path_seekingsSerenaFeng1-0/+26
1. mv conf/ userconfig/ compliance/ patch to etc/ 2. after installation etc/ will be put under /etc/dovetail 3. leveraging /etc/dovetail in coding Change-Id: Icf9cb00ff7fc7cf35755f60d3e258b23e2c70839 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>