summaryrefslogtreecommitdiffstats
path: root/etc/conf/cmd_config.yml
AgeCommit message (Collapse)AuthorFilesLines
2019-05-23Change the OVP version to ovp.2019.0xPanagiotis Karalis1-1/+1
The OVP version is updated from ovp.2018.09 to ovp.2019.0x Change-Id: Ibbfe186f791c521155173fd405b0147844893cf8 Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com>
2019-05-09Add Licensexudan1-0/+9
Many files in Dovetail repo are lacking of License after LF scanning. Add all of them except the following files: 1. docker/Dockerfile.aarch64.patch 2. 0001-Allow-additional-properties-in-API-responses.patch 3. docs/images/dovetail_offline_mode.xcf 4. docs/images/dovetail_onfline_mode.xcf 5. all png files 6. all empty files Change-Id: If1a0b7c2d35d6682c87c4eb9106e1998dc4ca3bc Signed-off-by: xudan <xudan16@huawei.com>
2019-04-03Push CI results to OPNFV test DBxudan1-0/+5
In order to use OPNFV test results page to do the ayalysis of all OVP test cases, it needs to push all results generated by Dovetail CI jobs to test DB and then using http://testresults.opnfv.org/test/#/results to check all results. The following data must contain in the POST body: 1. project_name 2. case_name 3. details 4. installer 5. scenario 6. pod_name 7. build_tag 8. criteria 9. start_date 10. stop_date 11. version JIRA: DOVETAIL-767 Change-Id: I925ae249e24efd7bfb1c68a69150e9c22f0cdf36 Signed-off-by: xudan <xudan16@huawei.com>
2018-09-13Update code base and docs to 2018.09xudan1-1/+1
The official name of the next release is going to be 2018.09. We need to rename all occurrences of 2018.08 in the code base, the documentation, and the web portal. JIRA: DOVETAIL-740 Change-Id: Ie0e532d6671b7590454e9afd960a2934f313a022 Signed-off-by: xudan <xudan16@huawei.com>
2018-08-14Rename ovp.next to be ovp.2018.08xudan1-1/+1
Change-Id: I32aaee370512c3d7c8d6e1fbb6ef25aebc5d483f Signed-off-by: xudan <xudan16@huawei.com>
2018-07-17Update test suite ovp.nextxudan1-0/+10
Update test suite ovp.next according to the latest OVP scope. Modify Dovetail daily jobs to run all the scope. There should be 2 jobs. One for all mandatory test cases and the other for all optional ones. That's mainly because of that the total executed time will be too large (more than 300 minutes). Then the job will always failed because of time out. It's hard to enlarge the time because it's already larger than common 3 hours. Split it into 2 jobs can avoid the time out issue and make the results clearer for reviewing. JIRA: DOVETAIL-694 Change-Id: Ie0ea6221868941781af1477f7c7719f7cb4351a4 Signed-off-by: xudan <xudan16@huawei.com>
2018-07-13Remove the yardstick_tag and functest_tagxudan1-28/+0
These 2 commands can't work now. Also there is no need to support them, so remove them. JIRA: DOVETAIL-695 Change-Id: I6707c7fc1d19fe06690cd14ef39f9d421d00a2bc Signed-off-by: xudan <xudan16@huawei.com>
2018-07-12Enable OVP tests to run on a DPDK-enabled systemPanagiotis Karalis1-0/+4
DPDK-enabled NFVIs require support for hugepages which in turn is configured by means of extra_specs in flavors. Currently, Functest enables hugepage support if the name of the scenario contains the substring "ovs". Dovetail allows end users to run all tests on DPDK-enabled systems and the documentation has been updates accordingly. JIRA: DOVETAIL-665 Change-Id: If4898da168f8b4c69a045ef3b00b8a8862f29b0c Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com>
2018-05-15Renaming test cases for better readabilityGeorg Kunz1-1/+1
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-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-04Remove local DBxudan1-1/+2
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-17Implementation of API validaton exemption in dovetailGeorg Kunz1-0/+5
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-03-29Integrate dovetail with ONAPMoshe1-0/+7
Change-Id: I6a1fa5f27df2f5127eb00156b3135dc79caf5e77 Issue-ID: DOVETAIL-629 Signed-off-by: Moshe <moshehoa@amdocs.com>
2018-03-06Separate valid docker tags for functest and yardstickGeorg Kunz1-3/+3
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_seekingsSerenaFeng1-0/+71
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>