Age | Commit message (Collapse) | Author | Files | Lines |
|
Change default container tag to be:
1. Functest ovp.1.0.0
2. testapi ovp.1.0.0
Add test suite ovp.1.0.0 and set it to be the default test suite.
Comment out bottlenecks CLI for initial release.
JIRA: DOVETAIL-580
Change-Id: I956e49e43fc7ba0176c14079b7228089db5dc108
Signed-off-by: xudan <xudan16@huawei.com>
(cherry picked from commit c47b8dde0e39e273372b091a3d8da1cc15b7ae9f)
|
|
When Tempest test cases failed at the SetupClass, the record is the class name
of the test cases rather than the name of the test cases.
The local summary will say they are passed wrongly.
JIRA: DOVETAIL-575
Change-Id: Iec879378770017eddd37e9a99346d980355bb6e2
Signed-off-by: xudan <xudan16@huawei.com>
(cherry picked from commit cb03da10feb8af4cd48add8ab96b134f6d6ebd1c)
|
|
Change-Id: I9c585f132c10ef726cd859e4abe3c9a874cbe0bc
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Change-Id: Ie981fc1288d7da52bfaa72c58ebab5a1ec7c75a5
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. Some tempest test cases have alias test cases because of the different
versions of tempest.
2. However, Dovetail fixes the version of tempest to be 14.0.0 in its first
release. So the number of test cases that can be executed in osinterop
is always 205. And for different SUTs, the 205 test cases are all the same.
3. In this situation, there is no need to list the alias test cases.
4. Just list all the 205 test cases which will not confuse users when they
reading dovetail docs.
JIRA: DOVETAIL-566
Change-Id: I5e39dd82314833c8c0a6c1732c990f671ae64420
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-573
Change-Id: Ibefd6c2c07e107de0911122a15293667f9042bd9
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. Currently, dovetail.tempest.tc004 has 13 sub test cases defined in its
config file and specification document of the test case. All these
sub test cases are picked from tempest based on it's version 15.0.0.
2. For Dovetail 1st release, it fixes the version of Functest to be
opnfv/dovetail:cvp.0.5.0, and Functest integretes tempest 14.0.0
in this version and it's E release.
3. There is one sub test case in dovetail.tempest.tc004 that is new in
tempest 15.0.0, so it can not be recognized and executed by Functest D
and E release. It is 'test_server_connectivity_cold_migration_revert'.
4. Remove this sub test case from dovetail.tempest.tc004. This means remove it
from the test case config file and specification document.
JIRA: DOVETAIL-561
Change-Id: Ia927af040794c7027a741a282ed75fe401f99ff1
Signed-off-by: xudan <xudan16@huawei.com>
|
|
The name of the compressed result file included a timestamp according
to the pattern "day_hour_minute". This is a rather uncommon timestamp
and can cause confusion. This patch changes the timestamp to a more
common "YearMonthDay-HourMinute" format.
Please note: Please check if this change has an impact on the web
portal.
Change-Id: Ife41050bc1d5ca6942706b756d03a1d0d251ae41
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
changes:
1. add usage example in hosts.yaml.sample
2. fix /etc/hosts from wrong format {'hostname': 'ip'} to
the right 'ip hostnames'
3. fix --add-hosts from wrong usage --add-host {'hostname': 'ip'} to
the right --add-host='hostnames':ip
4. support per ip mapping mutiple hostnames, which is also
in line with /etc/hosts schema
JIRA: DOVETAIL-556
Change-Id: I92e8cb0fd3476b61f5c73a69e34c4a66aef51d6e
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
The script launch_db.sh will print "Already Exists" logs when the DB has been
initialized by the data stored in JumpHost.
Ignore this kind of logs because it won't affect the launch of the DB but
it will confuse users.
JIRA: DOVETAIL-557
Change-Id: I23616b10bbadc49888731e943d0a4ee4425045f5
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-550
Change-Id: I871ec1fdf8d33efe3ed00602d0184c7b35896c17
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. The scripts for building local DB and testapi service just work on Ubuntu.
2. For Centos, they fails to do that.
3. This is mainly because of that Centos can't use the IP of the JumpHost
to connect the DB and testapi. It needs to use the internal IPs of the
DB container and the testapi container.
4. Change the IPs in the scripts to be the containers' internal IPs.
JIRA: DOVETAIL-548
Change-Id: I71aed82cb620b58bcd43ace61497db65c5bd7ecc
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Get the admin endpoints of all service.
JIRA: DOVETAIL-546
Change-Id: Ie0ac3bc5b4eb0885046e207b73217994a4f0e358
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Hardware info:
Use ansible to get all hardware info from all nodes.
JIRA: DOVETAIL-540
Change-Id: I6a2dde1b2ebae2af8f702008c23110ebe63cc06f
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. If there throw an exception during the test of one sdnvpn test case,
it will not do the clean.
2. Then there are many resources left, such as network, subnet, server...
3. This is a bug of sdnvpn see JIRA: SDNVPN-184
4. The patch for fixing this bug https://gerrit.opnfv.org/gerrit/#/c/44777/
5. Currently, use functest module "functest openstack clean" to clean the SUT.
JIRA: DOVETAIL-524
Change-Id: I629fc6fdc9e4c95960f6122358ff219a467d441b
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. The SDNVPN DB initialization information lacks two test cases,
functest_testcase_4 and functest_testcase_8.
2. So the results of these 2 test cases cannot be pushed into DB.
3. Add these 2 test cases info to DB.
JIRA: DOVETAIL-535
Change-Id: I1c6d049b942806924f15dd106452fd9b4d554454
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. Now there is a testsuite proposed_tests for beta tests which may
cause some confusions.
2. Copy all test cases to testsuite cvp.0.8.0 for beta testers to use.
3. Update userguide with testsuite cvp.0.8.0
JIRA: DOVETAIL-528
Change-Id: I35bc7dee6e07a9125a4c1991b0049f6e2d705cc5
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Move SDNVPN test cases after tempest test cases, then the resources left will
not effect tempest test cases.
JIRA: DOVETAIL-524
Change-Id: I815ae7f3a3be0225be1e9695f13d4552946bffb5
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
SDNVPN test cases failed due to wrong module name.
The module name needs to be changed into "sdnvpn.test.functest.testcase_1"
Refer to patch https://gerrit.opnfv.org/gerrit/#/c/41385/
Currently Dovetail uses functest:cvp.0.5.0 which uses module name "testcase_1".
JIRA: DOVETAIL-510
Change-Id: I3232760d3af34125c7da71a5d2c62ca32693c82b
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
|
|
|
|
1. Dovetail generate a tar file for uploading results to CVP web portal.
2. If users don't run with option --report, it shouldn't generate the tar file.
Because users can not upload results to CVP if they don't run with --report.
3. If it generates the tar file when user run dovetail without --report,
the tar file is invalid because it lacks of results.json.
JIRA: DOVETAIL-511
Change-Id: I4d21f21f0b278962564d810369df03100b38f003
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
1. When test dovetail, users can build local DB and testapi to store and
report the results.
2. The script for building local DB and testapi needs some updates.
JIRA: DOVETAIL-507
Change-Id: I8bc96bfea27f424468cafaa2e05894065ef44ad9
Signed-off-by: xudan <xudan16@huawei.com>
|
|
The directory tree of results tar file is wrong, so web portal cannot parse it.
Reset the tar file.
JIRA: DOVETAIL-508
Change-Id: I8475323294e84ca51242b700570926d5c0177390
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. Currently, the log level of yardstick is DEBUG and cannot be modified.
2. Make it can be changed from CLI.
3. When use dovetail run --debug, can see all Yardstick logs (including DEBUG)
in dovetail.log.
4. When run without debug option, cannot see Yardstick debug logs in
dovetail.logs.
5. yardstick.log always doesn't include debug logs.
JIRA: DOVETAIL-506
Change-Id: Iaafb61232a22e16fff2fa4605bf7e262b022085e
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. Currently, dovetail can run a test suite or a test area in that test suite.
2. The test areas in one test suite are not divided into optional and mandatory.
3. Split them and support to run just mandatory or optional.
4. Support to run multiple test areas.
JIRA: DOVETAIL-505
Change-Id: I42cd7b4e11c3e3674c806e9bc999b782bf5c85c6
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Rename the "defcore" test area to "osinterop".
The DefCore working group has been
renamed OpenStack InterOp Working Group some time ago.
JIRA: DOVETAIL-499
Change-Id: I144af767632c8fb83859e5e04b6427bb1a538348
Signed-off-by: xudan <xudan16@huawei.com>
|
|
docker image used
opnfv/yardstick: danube.3.2
opnfv/functest: cvp.0.5.0
opnfv/bottlenecks: cvp.0.4.0
opnfv/testapi: cvp.0.6.0
opnfv/dovetail:web.cvp.0.6.0
opnfv/dovetail:api.cvp.0.6.0
opnfv/dovetail: cvp.0.6.0
main changes
Merge all test specification docs about test area tempest and defcore
Merge addendum doc and workflow doc
Remake aarch64 patch for Dovetail container
Remove some tempest test cases that are not too common
Add additional Tempest API test cases into test case tempest.tc005
persist db file in host for mongo container
add nginx to host static files
add a sample tempest_conf.yaml file into userconfig
Add a patch to set ha SLA to be 30 seconds
Modify logs
Bugfix: the config files in useeconfig will cover user's config
Bugfix: functest only keeps the last test case's log
Bugfix: pre_condition cmds is just executed once
For more information, refer to https://wiki.opnfv.org/display/dovetail/Running+history+for+the+dovetail+tool
JIRA: DOVETAIL-497
Change-Id: I74626bbf65ce0121cc7b53394c85694e15df8484
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
JIRA: DOVETAIL-498
Change-Id: Ie98fc89cc840b557aa4186c6c2bee2d610432af0
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. According to ha test specification doc, the SLA of process recover time
is 30 seconds.
2. However, the SLA in Yardstick test cases are all 20 seconds.
3. Add a patch to change the SLA in yardstick test cases.
JIRA: DOVETAIL-496
Change-Id: Ib8f229fdfbb3289bf70d6ee900132b3db3a21b17
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
Change-Id: I2a19b9f3e6c44bedef5d3cb20f480405e4d6d5e2
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. According to the latest dovetail test case specification document,
there are 5 new Tempest api test cases.
2. Add them into tempest.tc005 so they can be tested in CI.
JIRA: DOVETAIL-495
Change-Id: Ib8057d01b99472aeb91cf564d09b67407c572235
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. Now there are 2 sample files tempest_conf.yaml and hosts.yaml in userconfig,
and thet will cover user's tempest_conf.yaml and hosts.yaml
in $DOVETAIL_HOME/pre_config.
2. Rename the files in userconfig to be tempest_conf.yaml.sample
and hosts.yaml.sample.
3. Add the hosts info in file /etc/hosts in Dovetail Container.
JIRA: DOVETAIL-492
Change-Id: I2b5694a8058b864b510925eec595d6f2bd1062ff
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
JIRA: DOVETAIL-490
1. Dovetail just keeps the last tempest/defcore/ipv6/bgpvpn test's log file.
2. All log files should be kept, so users and developers can know the reason
of failed test cases.
3. tempest logs will be stored in directory tempest_logs/
4. defcore logs will be stored in directory defcore_logs/
5. IPv6 logs will be stored in directory ipv6_logs/
6. bgpvpn logs will be stored in directory bgpvpn_logs/
7. All vping logs are in functest.log
Change-Id: I79eae79cb32d65ce1ada3dd6f4c6dfd3945fc512
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-489
1. All the cmds defined in pre_condition is just executed once for each type
i.e. functest, yardstick, bottlenecks...
2. The copy cmds defined in each functest test cases are just executed for the
first test case rather than all test cases.
3. Make the cmds to be executed for each test case.
Change-Id: I571f0eb9dd3cab77fc8597e5a9b5246398804d3e
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-488
Keep db file in host to avoid data lost
Change-Id: If039789eabfb8847ea344c016cb74e226be43f73
Signed-off-by: grakiss <grakiss.wanglei@huawei.com>
|
|
JIRA: DOVETAIL-485
Tornado does not support directory listing, so add nginx to host static files, and support log file browsing
Change-Id: Ic1427ab9c64661b3993ac60943f470b125a0fbe7
Signed-off-by: grakiss <grakiss.wanglei@huawei.com>
|
|
1. Functest cvp.0.5.0 supports to config tempest.conf file when running
tempest test cases.
2. Dovetail provides a sample tempest_conf.yaml file, and user can edit
this file before running tempest test cases.
3. All the values in this file will be used to update tempest.conf file.
Change-Id: I1afb50f1405c6cef992132899e0549396f587872
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-483
1. docker image used
yardstick: danube.3.2
functest: cvp.0.5.0
bottlenecks: cvp.0.4.0
testapi: cvp.0.5.0
dovetail: cvp.0.5.0
2. main changes
Bugfix: wrong command in function 'check_https_enabled'
Use opnfv/functest:cvp.0.5.0 and do some adaptions in dovetail tool
Create a tar file for all logs
Add tempest test cases into proposed_tests
Fix testapi base_url for public_url
Add user guide for results operations on web
3. For more information, refer to
https://wiki.opnfv.org/display/dovetail/Running+history+for+the+dovetail+tool
Change-Id: Iec548b077a704ff68d6b93de3436e109d59371cd
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-482
1. In function check_https_enabled, it will use cmd
"openstack catalog show identity |awk '/public/ {print $4}'"
to check if it is https.
2. However, this command will not work if it is https.
3. Check https via OS_AUTH_URL rather than "openstack catalog show identity".
Change-Id: If40ffa8e9b33c38123ff4b834198a8eaaedc1c9c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
In order to use functest cvp.0.5.0, Dovetail tool needs some adaptions.
Change-Id: I9d0a23791c246a6c4961f229eaeb1f52f9b4995a
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
|
|
JIRA: DOVETAIL-479
User may want to upload all logs along with the results,
so others may check the running logs to make sure what' s going on during the test.
Change-Id: Ice906264bbdf091d3353d6d2e146653aeb057f5f
Signed-off-by: grakiss <grakiss.wanglei@huawei.com>
|