Age | Commit message (Collapse) | Author | Files | Lines |
|
Please refer to env_config.sh.onap.sample when testing it.
The guide of preparing local env for onap package validation can be found here
https://gerrit.onap.org/r/#/c/75119
Change-Id: I39d6b11544847756126623a7eb3b953dc800c470
Signed-off-by: xudan <xudan16@huawei.com>
|
|
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>
|
|
1. fix the bug 'ShellRunner' object has no attribute 'archive_logs'
2. remove the testarea_supported because it's not very necessary for the test
cases themselves and can make it a little more simple to add a test case
with new test area
JIRA: DOVETAIL-750
Change-Id: I71ee74615200376adca2a0db040753e5fce329bc
Signed-off-by: xudan <xudan16@huawei.com>
|
|
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>
|
|
1. For Functest healthcheck, patrole, refstack_defcore, neutron_trunk and vping
test cases, stop to redefine testcases.yaml.
2. For VNF and bgpvpn, they still have scenario dependencies for Functest.
How to handle them are still under consideration.
3. For other tempest test cases, they rely on tempest_custom. Leave them
under discussion.
JIRA: DOVETAIL-673
Change-Id: Ibd10c9883d8df3749f4a93e280deaca77fe6bc00
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Functest use gambia tag. Other projects use their latest one.
Change-Id: Ibbfde50727149822d8331d998f6b4e173f19e244
Signed-off-by: xudan <xudan16@huawei.com>
|
|
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>
|
|
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>
|
|
If mapping to host's /tmp, it won't clean all .log and .out files before
run a new test. It causes the results file including all previous results.
See https://build.opnfv.org/ci/view/dovetail/job/dovetail-apex-baremetal-default-mandatory-master/26/artifact/results/stress_logs/bottlenecks.stress.ping.out/*view*/
It will affect the results check.
Mapping to DOVETAIL_HOME/results/bottlenecks, which will always be cleaned
before running another test.
Change-Id: I22bfc871d6f041ae38308bf8e8f685993a376973
Signed-off-by: xudan <xudan16@huawei.com>
|
|
All results files including the .out files are stored in Yardstick /tmp
Need to map that with host's /tmp to parse the results.
JIRA: DOVETAIL-727
Change-Id: I5a81e6e6bdf79b2e0074df505deb425c37b93300
Signed-off-by: xudan <xudan16@huawei.com>
|
|
For ping, it set the ssh login username to be ubuntu.
So need to use ubuntu image rather than cirros.
JIRA: DOVETAIL-727
Change-Id: Iaac8c8280a464efe3a431d4eb260c4a0a626e12d
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Change-Id: I32aaee370512c3d7c8d6e1fbb6ef25aebc5d483f
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-726
Change-Id: I57cb14cd5fe03a51e1691d7b48359bdd9b472ae4
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Replacing the generic "dovetail" prefix of the testcase definitions with
the name of the OPNFV test framework which hosts the test.
JIRA: DOVETAIL-719
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
Change-Id: I8f90423b8908197bdc7adddf82c61ff394893f52
|
|
1. Copy a ubuntu image to Bottlenecks to support offline
2. Add an env DEPLOY_SCENARIO to bottlenecks to support DPDK
3. Set push results to DB False
JIRA: DOVETAIL-706
JIRA: DOVETAIL-707
Change-Id: I81f293bb9fddc63fd8be455546ba4642ca670fc7
Signed-off-by: xudan <xudan16@huawei.com>
|
|
The 2 sections 'functest_testsuite' and 'functest_testcase' are used by
all Functest test cases.
They aim to parse the results of Tempest sub test cases.
Remove them, and check the sub test case list,
1. if it's empty, that means no need to check sub test cases
2. if it is not empty, check the sub test cases one by one.
Additional, remove some useless keys in dovetail_config.yml
JIRA: DOVETAIL-658
Change-Id: Ic829264b0c8eaedd8e2b3fa55b38a34644482c20
Signed-off-by: xudan <xudan16@huawei.com>
|
|
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>
|
|
The fraser-based OPNFV tools use the newer cirros-0.4.0 image and we
hence only ask users to download this version in the user guide.
This updates the bottlenecks test to comply with this.
Change-Id: I5a94d6a7196ae04e00150dc17a4a16add2d3fef6
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
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>
|
|
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>
|
|
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>
|
|
Use openstack shade to get endpoint infomation rather than executing
openstack commands directly.
The next step can replace openstack commands by shade for some test cases that
need to create openstack resources (images, flavors) if we agree to use shade.
JIRA: DOVETAIL-659
Change-Id: I72b302fb2d4a61e9249a7e53f81ea9464944dcd3
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Adding the vEPC test case to Dovetail. The test deploys a vEPC using
Juju as VNF manager and performs application level tests.
JIRA: DOVETAIL-650
Change-Id: I15c2cdddee510e12a5faf18efc8950af5cf7b664
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
- 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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: I6a1fa5f27df2f5127eb00156b3135dc79caf5e77
Issue-ID: DOVETAIL-629
Signed-off-by: Moshe <moshehoa@amdocs.com>
|
|
Change-Id: Ie470d03bd168c909fd02c316523049c67a6bb095
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
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>
|
|
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>
|
|
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>
|