summaryrefslogtreecommitdiffstats
path: root/etc
AgeCommit message (Collapse)AuthorFilesLines
2018-05-18Correct the names of sub test cases due to the new Tempest versionxudan9-55/+30
1. Change from Functest Danube to Fraser, the Tempest version it integrates is from 14.0.0 to 17.1.0. 2. Some sub test cases names have been changed. 3. Some are removed from tempest_smoke. 4. Some are new added into tempest_smoke. JIRA: DOVETAIL-657 Change-Id: Ie5611f5b7a5888bea3942667907341bd071d399d Signed-off-by: xudan <xudan16@huawei.com>
2018-05-17Adding OpenStack controller database HA test caseGeorg Kunz3-19/+27
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-15Updating the list of OS interop testsGeorg Kunz1-190/+184
Updating the list of test cases used in the OpenStack Interop test case to match i) the tests used in the 2017.09 guideline, and ii) the version of Tempest used by Functest We keep the explicit list of test cases in the test case definition file for now to enable Dovetail to verify the list of executed tests corresponds to the tests we want to run. JIRA: DOVETAIL-644 Change-Id: Ic627ef2bbad1dcfa5dd8773301c68dffb545a3b2 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-15Renaming test cases for better readabilityGeorg Kunz85-785/+304
This patchset proposes a new naming scheme for test cases. The ides is to replace the current numbered scheme <testarea>.tc<number> with: <testarea>.<capability/test case description> The motivation for this is that a the numbering does not convey any information about what the test case is doing and hides to which test case implementation in Functest or Yardstick a test case spec refers. Note: this patchset has not yet been tested in Dovetail itself. Its goal is start a discussion about the naming scheme. JIRA: DOVETAIL-647 Change-Id: If33b4bf88e451b372c2af10895ff92a87d9d961d Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-15Split tempest_smoke test casexudan10-135/+184
1. Total number of sub test cases is 119 2. Remove all 14 object_storage test cases which need swift 3. Remove 26 test cases already included in osinterop test area 4. Remove 21 test cases already included in ipv6 test area 5. Remove 2 scenario test cases already included in tempest test area 6. Split other 56 test cases into 8 groups Change-Id: I9eef20593ebf5f69347a2ec3a612c9ebc5a753db Signed-off-by: xudan <xudan16@huawei.com>
2018-05-14Switching to functest:fraser container tagGeorg Kunz1-1/+1
switching to functest:fraser from functest:opnfv-6.0.0 to incorporate bug fixes which have been backported to stable/fraser. Change-Id: Ieab9064ac0187b3460b09fe74861fc844b0b0195 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-11Adding Neutron trunk port tests to proposed_tests suiteGeorg Kunz4-0/+28
Adding the Neutron trunk port tempest tests to Dovetail and the proposed_tests test suite. JIRA: DOVETAIL-648 Change-Id: Ia77980a245fd1bca6e5f0e567467432e12bf974e Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-11Fixing SDNVPN tempest API testsGeorg Kunz2-2/+2
The code to run Tempest tests has changed in SDNVPN between Euphrates and Fraser, causing these tests to fail. Moreover, due to a bug in SDNVPN, not all bgpvpn API tests are currently being run. This is being addressed by https://gerrit.opnfv.org/gerrit/#/c/57299/ and needs to be cherrypicked to Fraser 6.1 for inclusion in OVP 2.0. Change-Id: I0a7575e8a9ebc23af5edaa26c1a9ce1e8149919c Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-08Improve the CLI of Dovetail toolxudan1-1/+12
The CLI of dovetail tool needs some improvement. 1. Add an option '--testcase' to support specify test case. 2. Add an option '--no-clean' to keep functest/yardstick/bottlenecks containers for debugging after running the test cases. 3. Improve the local report section. a. Remove some info that is not necessary b. Make the info more clearly JIRA: DOVETAIL-588 Change-Id: Ic769a6e2788b407c3df08ccd593a0ecdaa35e5ea Signed-off-by: xudan <xudan16@huawei.com>
2018-05-07Decoupling Bottlenecks Docker config items from source codexudan1-0/+12
There are some special Docker setting items when creating Bottlenecks Docker Cntainers. Move the special settings to config files. Disable the function to push results to DB. JIRA: DOVETAIL-645 Change-Id: Icc033222edf74c0fe4853dede2794f4226fd4252 Signed-off-by: xudan <xudan16@huawei.com>
2018-05-04Remove local DBxudan3-4/+3
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-05-01Integrating Functest Patrole test caseGeorg Kunz5-1/+34
Adding the new Patrole test case of Functest to Dovetail and to the proposed_tests test suite. JIRA: DOVETAIL-649 Change-Id: I2c3f583cdbd3af75cec020b0fe97f287d23498a5 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-04-17Switch to OPNFV Fraser releasexudan36-47/+41
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-17Implementation of API validaton exemption in dovetailGeorg Kunz3-0/+1655
This patch adds the ability to Dovetail to disable strict API response validation in Tempest-based test cases run by Functest. Corresponding updates of the web portal and backporting of this patch to OVP 1.0.0 (Danube) will follow. JIRA: DOVETAIL-633 Change-Id: Iace99ea1b6224ea907a2c3af8676e9285e6ad3ee Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-04-10Add functest healthcheck test suiteEddie Arrage6-0/+100
- Add Functest healthcheck tier to Dovetail as new test suite - Intention is that these test cases are not part of mandatory test cases in compliance program - Use for debug and SUT pre-flight check - May consider running tc001 (connection_check) at other test execution stages to determine if SUT is still functioning, as this test takes < 10 sec (more important as test complexity increases such as in vnf test tier) - Replacement for patch: https://gerrit.opnfv.org/gerrit/#/c/52461/ - Removed CI filters, as suggested Change-Id: I2e72931b27e43359d6250f6959a17af8526c5094 Signed-off-by: Eddie Arrage <eddie.arrage@huawei.com>
2018-04-10Decoupling Yardstick Docker config items from source codexudan2-10/+13
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-04-10Support to specify docker image for each test casexudan8-1/+8
1. Currently each type of test cases will use one docker image. 2. For example, Functest test cases use opnfv/functest-restapi:euphrates Yardstick uses opnfv/yardstick:opnfv-5.1.0 3. It needs to support to specify the docker image for each test case. 4. For example, vping test cases use opnfv/functest-smoke:euphrates sdnvpn uses opnfv/functest-features:euphrates 5. The benefit of this is that these docker images are well verified by Functest CI and from Functest plan, they may not support functest-restapi docker image in its future release. JIRA: DOVETAIL-638 Change-Id: I8a30eea2233aeff809af2e241b6c939194397832 Signed-off-by: xudan <xudan16@huawei.com>
2018-04-08Removing outdated patch for Yardstick HA testsGeorg Kunz1-133/+0
This patch was needed to modify the timeout values of the HA test cases in Yardstick for the Danube release. In Euphrates, the timeout values have been fixed upstream, so the patch is not needed anymore. The code for applying the patch was already removed in https://gerrit.opnfv.org/gerrit/#/c/51997/ Change-Id: I67cceb57c063378d77f6cbc720bc6464d2be4aed Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-04-04Decoupling Functest Docker config items from source codexudan8-13/+4
There are some special Docker setting item when creating Functest Containers. 1. Remove the extra settings which are required by Functest Danube. 2. Remove the settings for pushing results to DB because Dovetail plans to disable this function. 3. Move the other special Functest settings to config files. JIRA: DOVETAIL-639 Change-Id: Ibc4090b5c0aafdf9ed64e65a9a92e34a12a16df5 Signed-off-by: xudan <xudan16@huawei.com>
2018-03-29Integrate dovetail with ONAPMoshe7-0/+112
Change-Id: I6a1fa5f27df2f5127eb00156b3135dc79caf5e77 Issue-ID: DOVETAIL-629 Signed-off-by: Moshe <moshehoa@amdocs.com>
2018-03-15Disable restricts of sdnvpn test casesxudan6-1/+12
1. The original testcases.yaml file of Functest restricts sdnvpn test cases to run on Fuel, Apex or Netvirt on bgpvpn scenario. https://github.com/opnfv/functest/blob/master/functest/ci/testcases.yaml#L278 2. Dovetail has a testcases.yaml file to allow sdnvpn test cases run on any commercial SUTs. https://github.com/opnfv/dovetail/blob/master/etc/userconfig/testcases.yaml#L113 Change-Id: I0d5ed5b22e55dc3dc0fe584dc57b28239334b7de Signed-off-by: xudan <xudan16@huawei.com>
2018-03-15substitute image copy with docker volumeSerenaFeng4-2/+38
Change-Id: Ie470d03bd168c909fd02c316523049c67a6bb095 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2018-03-14Add process info to pod.yaml to specify the info of a special processxudan2-1/+35
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-06Separate valid docker tags for functest and yardstickGeorg Kunz2-6/+7
Specifying separate valid docker tags for functest and yardstick for input validation. DOVETAIL-592 Change-Id: I3365cdbd9ab521bf1368750c3f34b6863b3f7ec8 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-03-06leverage data_files to eliminate so many hardcoded abs_path_seekingsSerenaFeng80-0/+2052
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>