Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
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-478
JIRA: DOVETAIL-473 adds 6 test areas:
- forwarding packets through virtual networks in data path
- filtering packets based on security rules and port security in data path
- dynamic network runtime operations through the life of a VNF
- correct behavior after common virtual machine life cycles events
- simple virtual machine resource scheduling on multiple nodes
- storage security
Add Tempest test cases belong to this 6 test areas to Dovetail CI daily jobs.
Change-Id: I1535d96f3a85cdd8ac4f0c4375c68ce47bd9df93
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-474
Add Bottlenecks resiliency test case "posca_factor_ping" into proposed_tests.
Change-Id: I76aea651014fb4722ddae07559f417d3f840eee2
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
JIRA: DOVETAIL-468
1. docker image used
yardstick: danube.3.1
functest: cvp.0.2.0
testapi: cvp.0.3.0
dovetail: cvp.0.3.0
2. main changes
fix dovetail docker version to be 17.03.0-ce
adapt yardstick danube.3.1
For more information, refer to
https://wiki.opnfv.org/display/dovetail/Running+history+for+the+dovetail+tool
Change-Id: Ie8bb2cfbad4b416404f5aaa2c40c1d3832be676f
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-446
1.add vping to proposed_tests
2.delete out-dated nfvi test cases
Change-Id: I181b00b02abe6fed4ff51e947576c1b71321cdd2
Signed-off-by: MatthewLi <lijun_1203@126.com>
|
|
JIRA: DOVETAIL-466
1. Yardstick danube.3.1 needs a yardstick.conf file in /etc/yardstick
2. Copy the file /home/opnfv/repos/yardstick/etc/yardstick/yardstick.conf.sample
to /etc/yardstick/yardstick.conf
3. If user wants to store the results in the local file, set the dispatcher to
be 'file'.
4. If user wants to push the results into the DB, set the dispatcher to be 'http'
and target to be the api url getting from the user.
Change-Id: I39c30883b471ab7cb29ed6d63ba8c232da39c135
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-447
docker images used
yardstick danube.3.0
functest cvp.0.2.0
testapi cvp.0.2.0
dovetail cvp.0.2.0
main changes
1, fix yardstick HA bugs
2, fix functest sdnvpn offlinebugs
3, fix dovetail https bugs, etc.
for more info, refer to
https://wiki.opnfv.org/display/dovetail/Running+history+for+the+dovetail+tool
Change-Id: I4edb61b84ed80d8d7624f69db372fec60d73aa38
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-447
Change-Id: Id49d6ded8188900b58349e1983ac3fc8b40b6059
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-428
1. Change the name of Yardstick result file from opnfv_yardstick_tc019.out to
dovetail.ha.tc001.out. Because opnfv_yardstick_tc019 is the name defined in
Yardstick and dovetail.ha.tc001 is the name defined in Dovetail.
2. Check whether the file exists before reporting the results are stored in file.
3. Delete test cases vping_ssh, vping_userdata and sdnvpn.tc003 from the testsuite
proposed_tests.
Change-Id: I4cb16947729479616a03abd9e91b76f9a41a949c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-438
1. Need an env variable DOVETAIL_HOME in env_config.sh
2. env_config.sh, pod.yaml and id_rsa should be put in path DOVETAIL_HOME/pre_config
3. the results will also be put in this path
4. no need to give the path of openstack credential file while running a testsuite
5. if running with the code, source the env_config.sh file before running
source $DOVETAIL_HOME/env_config.sh
dovetail run --testsuite <testsuite_name>
6. if running with Dovetail docker image
docker run -it --privileged=true -e DOVETAIL_HOME=<dovetail_home_path>
-v <dovetail_home_path>:<dovetail_home_path>
-v /var/run/docker.sock:/var/run/docker.sock
opnfv/dovetail:latest /bin/bash
Change-Id: Ia23078f27a34e293d0075e49c673930f41069cb6
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
JIRA: DOVETAIL-212
after communicating with Tim/jose, help to add vpn testcase into proposed_tests
reference: https://wiki.opnfv.org/display/sdnvpn/SDNVPN+Testing#SDNVPNTesting-TestcompliancetemplateforDovetail
Change-Id: Id34a2cadba625abbdbc59ef11affeccba24fa10c
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-417
1. If report results with files, all results will be stored in local files.
2. If report to database, will get results from database and stored with file results.json
Change-Id: Ic30037bd66cd37042f82b75fac2043a876e21c6f
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-409
1. HA test cases need a file pod.yaml, in this file it can use the password or the key.
2. If use key, Dovetail need to pass the key file $DOVETAIL_HOME/dovetail/userconfig/id_rsa
to yardstick Container.
3. Add a directory $DOVETAIL_HOME/dovetail/userconfig and a sample_pod.yaml
4. ha.tc001 tc003 tc005 tc006 tc009 are ready.
Change-Id: I391cc211dba2cf0740dd0dcaee8a5c2d712eaee1
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-405
1. All HA test cases running in CI are SSH timeout.
2. The reason is that HA test cases need a file pod.yaml providing the info of
each node of Openstack.
3. This pod.yaml should be put in $DOVETAIL_HOME/dovetail/userconfig by users.
4. Dovetail's CI jobs should also do some adaptions. JIRA: DOVETAIL-407
5. modify file .gitignore to ignore directories results/ and userconfig/.
Change-Id: I5c681445ec83c9d67a0151370f5b56840ffe444c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
JIRA: DOVETAIL-401
1. modify all Ipv6 test cases, change tempest_smoke_serial/tempest_full_parallel
into tempest_custom, add ID of each sub-testcases.
2. Some sub-testcases in ipv6.tc002, ipv6.tc003, ipv6.tc004 and ipv6.tc005 can not
be found in the full tempest test case list.
2. disable testcases' script_result_acquired to enable tempest_custom run multiple times.
3. use build_tag-testcase_name(such as daily-master-79a6e392-28bb-4c40-9d88-a03bed99da2d-dovetail.ipv6.tc025)
as the unique ID of each testcase.
4. comment out the progress bar, because it has some problems when print the report text.
5. Functest has changed the TEST_DB_URL from http://<testapi>:<port>/apv/v1 to
http://<testapi>:<port>/apv/v1/results.
6. Functest has changed the TEST_DB_URL to file://<file_path>/<file_name>.
see https://gerrit.opnfv.org/gerrit/#/c/33511/
Change-Id: I524f6702377f215f526158214842481eb44565be
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-398
JIRA: DOVETAIL-399
1. this testsuite will run in community CI, see
https://gerrit.opnfv.org/gerrit/#/c/33509/
2. HA testcases please see
https://wiki.opnfv.org/pages/viewpage.action?pageId=8684344
3. vimops testcases deleted, since it's covered in defcore
Change-Id: Ied9c8867e0aa99e33fd213030e6471aa5cfb86e8
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
JIRA: DOVETAIL-375
JIRA: DOVETAIL-390
1. defcore test cases are erroneously judged because of:
a) defcore results json data lack some keys
b) some sub-testcases' names are the same as the prefix of another sub-testcases.
2. this patch removes the extra keys and judge sub-testcases accurately.
3. remove "store_type" in functest_config.yml and yardstick_config.yml.
4. change some log levels from info to debug.
Change-Id: I5f126e70309409cac66ef9a0909f1573d325098b
Signed-off-by: xudan <xudan16@huawei.com>
|
|
defcore.txt
JIRA: DOVETAIL-394
for refstack, userguide is listed in https://gerrit.opnfv.org/gerrit/#/c/33049/
in CI, use the automate way to generate tempest.conf to let refstack run against SUT, i.e., defcore.tc001.yml
will provide a way to let user can let refstack run against SUT manually, i.e. defcore.tc002.yml
since the tempest.conf autometely generated may not satisfied with SUT, users can adjust its tempest.conf to let the defcore testcases pass.
Change-Id: I5ed212c9c6d864d352d1c497ea039cc553461158
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
since yardstick changes its openrc location
see
https://gerrit.opnfv.org/gerrit/#/c/32861/
Change-Id: Ib85910fe5521fb398c47e389e2baf127342b1c0b
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
JIRA: DOVETAIL-375
1, together with other testsuite from functest, such as tempest etc.
this should merge after https://gerrit.opnfv.org/gerrit/#/c/31313/
2, delete some unnecessary definition
3, bugfix of docker cp inside container, see
https://build.opnfv.org/ci/view/dovetail/job/dovetail-compass-baremetal-debug-master/361/console
4, disable tempest testcaes since changed to refstack_defcore
Change-Id: I67503e348af4a3f697f1b4106bfe81c05add8aa0
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-381
Now DoveTail's results dir is defined in $DOVETAIL_HOME/dovetail/conf/dovetail_config.yml,
and its default value is /home/opnfv/dovetail/results.
Since customer's jumphost may not have this dir and they don't want to create it,
Dovetail needs to change this dir into $DOVETAIL_HOME/results.
Change-Id: I616fb2da87bcfaabfd78d8762897e378168f694d
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-370
Change-Id: I60c9f431358f848e24abcb865c4b2ca8c3b2d843
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-164
usage:
dovetail run --testsuite <testsuite> --offline
1,if --offline given, can run offline by using local docker images
(if there is no images, will get an error in log, images can be
pulled from dockerhub or downloaded from artifacts.opnfv.org )
2,if --offline not given, will run online, which means
pull docker image from dockerhub
Change-Id: I87ab35c82e59fb13a7a88c38d233e89285efc4d3
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-373
1. add an option --report/-r to choose the report type.
2. "-r file" will store results with files.
3. "-r http://192.168.135.2:8000/api/v1" will push results into DB.
The DB url can replaced by user's local DB or official DB.
4. Default report type is defined as "report_dest" in dovetail_config.yml.
5. Yardstick can't push results of one testcase into DB now, so both "-r file"
and "-r http://..." will be regarded as "file".
Change-Id: Ieaa017ab59c5b15235bf306ef57cdc56beb22af8
Signed-off-by: xudan <xudan16@huawei.com>
|
|
yardstick.log"
|
|
JIRA: DOVETAIL-371
1. remove all the envs in functest_config.yml and yardstick_config.yml
2. remove all relative cmds in cmd_config.yml
3. remove all the envs when running a new functest/yardstick container
4. add some variables just for functest pushing results to db
5. get the external network name for yardstick
6. make --debug/-d just control the log level shown on the screen
7. set requests=2.10.0 since python-openstackclient needs
'requests!=2.12.2,!=2.13.0,>=2.10.0'
Change-Id: I9f941e09d067fc95a14c3c9be1374f41df4a9a16
Signed-off-by: xudan <xudan16@huawei.com>
|
|
yardstick.log
1. For Fuel, yardstick prepare_env.sh will fail when
pwd != /home/opnfv/repos/yardstick
2. Modify yardstick_config.yml in Dovetail to change pwd to that path.
3. Use log file /tmp/yardstick/yardstick.log created by cmd "yardstick task start"
rather than redirecting the console output to yardstick.log.
JIRA: DOVETAIL-363
Change-Id: Ie0475cfabc66e342be868f0924a5fccd6fa74b58
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. change file name from openstack.creds to openrc.sh
2. change the cmd --creds to --openrc/-o
3. now the path of --openrc can be relative path no restrict to abspath
4. remove the useless "work_dir" in dovetail_config.yml
JIRA: DOVETAIL-369
JIRA: DOVETAIL-367
Change-Id: I2592438eef060f84132ff7fa226aea93ea947362
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-355
Change-Id: I04a74caa080e0fd2ea11648f8085947ef8d556b1
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Functest has changed it's way to generate the local result file.
see Gerrit: https://gerrit.opnfv.org/gerrit/#/c/28513/
Dovetail needs to do some adaptions to fit this change.
JIRA: DOVETAIL-350
Change-Id: I681f74832f582f26c8874f7d2726c8588f430612
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-186
Change-Id: Id0eec6652c9595c660436dec89a309a77b16bc03
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: Ibf0bb781c0f0b6be73526bf45231040e68510f76
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-170
Change-Id: Id56e30fdb3fb5b652e2145dd406b71986997f200
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
'CON_DEBUG'"
|
|
JIRA: DOVETAIL-166
Check the results of each cmds executed in test case
1. the results of pre_condition, post_condition, cmds need to be checked,
so it can get a quick fail, dont need to go through the next step
2. it's more accurate to show where error occurred as early as possible
3. get results from shell scripts
Change-Id: I5c1e59839c55b92de0e83e7e1eb552aa364b3f80
Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
|
|
JIRA: DOVETAIL-167
Change-Id: Ieb35f6aa2a6868af7d6dad5727bb3b345709275a
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
|
|
JIRA: DOVETAIL-157
dovetail tool must not depend on any installers or any SUT, so openstack rc files need to be provided to eliminate this dependency.
1. input parameters "SUT_IP"/"SUT_TYPE" must be optional, may be finally will be removed
2. new parameter "creds" to specify the file used to get access to openstack of SUT
Change-Id: I877efb2a6abc198c32ed6d52b9418a35597d5867
Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
|
|
1. change the entry_points of setup.cfg into dovetail.run:main
2. after setup the command 'dovetail -d true --testsuite debug' can just be
successfully executed under folder dovetail/dovetail. That is mainly because
of the load functions of testcase.py using relative paths.
3. using absolute path instead of relative path can support the command
successfully executed under any path.
JIRA: DOVETAIL-154
Change-Id: I4a2ad39a1a60e7e63efc55515781d27b823aa894
Signed-off-by: xudan <xudan16@huawei.com>
|
|
1. use this config to support example test case
Change-Id: I3fda73c408ed4b2bfb75aac52e0292fa4de9161b
Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
|
|
1. move conf/dovetail_config.py into utils/
2. change the open file path in dovetail_config.py
3. do some modification about all 'from conf.dovetail_config import ***'
JIRA: DOVETAIL-158
Change-Id: I7670e6de993899e4e2a604cbc501dc3339896ef1
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-46
1. for now a testcase has two kinds of validation types(functest, yardstick),
and it is not enough to check the complete funcionality
2. add new validation type(shell) for extra validation of the test case to make
result more accurate and more convincing.
Change-Id: I5c049a71f11cca71a7914f8af704c1983aba3dca
Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
|