summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-04-26Merge "JIRA: DOVETAIL-352 Updating the test specification document with ↵Christopher Price4-48/+632
iterative inprovements."
2017-04-26Merge "Bugfix: All HA testcases are SSH timeout in CI jobs"hongbo tian3-12/+20
2017-04-26JIRA: DOVETAIL-352 Updating the test specification document with iterative ↵ChristopherPrice4-48/+632
inprovements. JIRA tasks are being created for specific sections of the document. Refer to the doc for links to relevant JIRA tasks. Change-Id: I1717d56b8817c38802a227db320f30029f68fbd0 Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
2017-04-25Merge "AArch64 support for Dovetail docker"hongbo tian1-0/+32
2017-04-25Bugfix: All HA testcases are SSH timeout in CI jobsxudan3-12/+20
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>
2017-04-25Bugfix: KeyError when tempest_custom runs wrongxudan2-10/+14
JIRA: DOVETAIL-406 1. When there are something wrong with the test case tempest_custom, it's details json data are "details": {}, So it will throw KeyError exception in this situation. 2. Catch this exception and set all sub_testcases FAIL. 3. Disable the exceed_max_retry_times(). Change-Id: I6bdfc5944a535625b2211a3bd8096a13b81b339e Signed-off-by: xudan <xudan16@huawei.com>
2017-04-24AArch64 support for Dovetail dockerAlexandru Nemes1-0/+32
Add aarch64 patch for Dovetail docker file; The patch should be applied from releng Move to Ubuntu 16.04 in order, since docker.io package was not available for arm on Ubuntu 14.04. Added "pip install -U setuptools", since installation of other components failed because setuptools was missing. Change-Id: If00346d89c48be86c6d9b830f75c1792c39d6bb3 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
2017-04-24Merge "skip ha and rename tempest.conf"hongbo tian2-13/+13
2017-04-22skip ha and rename tempest.confMatthewLi2-13/+13
1) ha testcases need node configure file, skip it temporarily 2) tempest.conf-->refstack_tempest.conf, then it will not covered by other tempest testcases, can used for users to debug Change-Id: Ieb7101d8c406e294755629fd11a686f90b6c0a7f Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-04-22Bugfix about the ipv6 results checkerxudan1-0/+6
JIRA: DOVETAIL-404 1. IPV6 sub-testcase's name includes [id], which will affects the regex. 2. Remove the [id] from the name of the sub_testcases. Change-Id: I51b567e8382fa4e701f8b32ba7ea195d49fd31eb Signed-off-by: xudan <xudan16@huawei.com>
2017-04-21Merge "add defcore/ha testcases to proposed_tests"hongbo tian23-94/+158
2017-04-21use Functest tempest_custom test cases to run all Ipv6 test casesxudan33-85/+166
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>
2017-04-21add defcore/ha testcases to proposed_testsMatthewLi23-94/+158
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>
2017-04-21fix tox errorMatthewLi1-2/+2
see logs https://build.opnfv.org/ci/job/dovetail-verify-master/560/console Change-Id: Ifa66087c4c8fcbaae809aae380587a4f03eded6c Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-04-21Merge "put dovetail test result back in log and not generte report file"hongbo tian2-6/+6
2017-04-19set dovetail.log level by command linexudan2-7/+10
JIRA: DOVETAIL-400 1. set both the dovetail.log and screen log level by command --debug. 2. if --report http://testapi_url:port/api/v1/, change it into --report http://testapi_url:port/api/v1 Change-Id: I7cf697d4ac9072fc2d302a67ccde0f452d84be8f Signed-off-by: xudan <xudan16@huawei.com>
2017-04-18put dovetail test result back in log and not generte report fileMatthewLi2-6/+6
Change-Id: I2da5e7844f5ce034d4c0cfaa4592e6cd47002049 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-04-18Merge "fix click and pytz package version"hongbo tian2-3/+2
2017-04-16fix click and pytz package versionMatthewLi2-3/+2
JIRA: DOVETAIL-376 Change-Id: Ia269ca7cdd34c71b4531b28e42e40415190ae398 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-04-14directory updatehongbotian15-304/+0
JIRA: DOVETAIL-395 1. since plugfest has its own plan, the files are removed Change-Id: I4989d1e0e1af483205733b3130e3f1152a8933c7 Signed-off-by: hongbotian <hongbo.tianhongbo@huawei.com>
2017-04-13Merge "dovetail tool: bugfix: test cases are erroneously judged"hongbo tian6-75/+97
2017-04-12dovetail tool: bugfix: test cases are erroneously judgedxudan6-75/+97
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>
2017-04-12Merge "refstack: add manually method to let user can set its tempest.conf ↵hongbo tian5-2/+38
and defcore.txt"
2017-04-10refstack: add manually method to let user can set its tempest.conf and ↵MatthewLi5-2/+38
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>
2017-04-10dovetail tool: show progress during executing test casesxudan1-1/+6
JIRA: DOVETAIL-159 1. It takes long time to execute test cases that most of users think it hangs there, so a progress is needed to show the test is running. 2. add dynamic progress during execution 3. it' s a fake progress only showing the test is alive, not to show the percentage of completion. Change-Id: I0294659f79e8e09d1bcdd36d8f391d933e35b635 Signed-off-by: xudan <xudan16@huawei.com>
2017-04-05Merge "fix yardstick openrc location"hongbo tian1-1/+1
2017-04-05Merge "bugfix of pbr after updating"hongbo tian1-0/+8
2017-04-01fix yardstick openrc locationMatthewLi1-1/+1
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>
2017-04-01Merge "refstack result parse"hongbo tian8-48/+52
2017-04-01refstack result parseMatthewLi8-48/+52
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>
2017-04-01Merge "dovetail tool: check push_to_db success or fail"hongbo tian2-9/+38
2017-03-31dovetail tool: change results dir into $DOVETAIL_HOME/resultsxudan2-1/+7
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>
2017-03-31dovetail tool: check push_to_db success or failxudan2-9/+38
JIRA: DOVETAIL-380 If Functest fails to push results to db, there is just an error log in functest.log Dovetail needs to know the failure. Dovetail will get the results from db with keys, build_tag and testcase. If it can get the results data, it means push_to_db success. Fix the duration time wrong. Change-Id: If03bdf0ceb2f1a9d422381cdf06e1fd207358bd5 Signed-off-by: xudan <xudan16@huawei.com>
2017-03-30bugfix of pbr after updatingMatthewLi1-0/+8
JIRA: DOVETAIL-388 Change-Id: I3611624c955fa735aabfd00b456bd7f8455080e5 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-03-30Merge "dovetail tool: change function pull_image"hongbo tian2-21/+31
2017-03-30Merge "dovetail tool: set a unique build_tag for each DoveTail test"hongbo tian3-6/+10
2017-03-30Merge "dovetail tool: support centos 7"hongbo tian1-3/+14
2017-03-30dovetail tool: refstack testcase integrationMatthewLi6-7/+314
JIRA: DOVETAIL-370 Change-Id: I60c9f431358f848e24abcb865c4b2ca8c3b2d843 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-03-30dovetail tool: support centos 7xudan1-3/+14
JIRA: DOVETAIL-383 The script launch_db.sh can just support ubuntu now. Make it support centos 7. Change-Id: Ic6123ac82cb81bacb2d0c2d394619b8d8d7b3296 Signed-off-by: xudan <xudan16@huawei.com>
2017-03-30dovetail tool: set a unique build_tag for each DoveTail testxudan3-6/+10
JIRA: DOVETAIL-379 1. create a uuid for each test, and set build_tag=daily-master-<uuid> 2. the reason it starts with "daily_master" is that it's the requirement of functest when push data to DB. Change-Id: I9a59d5695a9f0d83bf4330379f1949a2a04f876c Signed-off-by: xudan <xudan16@huawei.com>
2017-03-30dovetail tool: change function pull_imagexudan2-21/+31
JIRA: DOVETAIL-378 1. test_runner checks the result of cmd "pull image". If fail to pull, then break the running. 2. pull_image will return None when there are errors, otherwise return image name. 3. if there is an old image named the same as the new one, the old one's tag will be changed into <none>. In this case, the old image needs to be removed. 4. if there are some containers using this old image, the remove will be skipped rather than logging error. Change-Id: I940cb18911112d5e13f3c14f87ddbdbaced3538a Signed-off-by: xudan <xudan16@huawei.com>
2017-03-29Draft one of the test specification.ChristopherPrice2-0/+367
JIRA: DOVETAIL-352 Needs a lot more work, but the directory tree and layout are according to our needs in order to have this published as a CVP document. Will push patches to restructure the repo according to the new requirements later. Change-Id: I9d4316407c94bc3096d322f6206eccf236d349da Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
2017-03-29dovetail tool: offline supportMatthewLi6-4/+29
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>
2017-03-25dovetail tool: Add an option cmd for pushing results into DBxudan7-37/+92
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>
2017-03-24Launch a local TESTAPI DB instanceLeo Wang3-0/+205
JIRA: DOVETAIL-374 User may want to dry run the test, and does not intend to upload test results to OPNFV DB. So dovetail provide a way to launch a local TESTAPI DB instance, then user can upload test results to this local db, and browse test results locally. Change-Id: I17b6153c9a308bd3cd59a2450c415200496cb855 Signed-off-by: Leo Wang <grakiss.wanglei@huawei.com>
2017-03-23bugfix of package errorMatthewLi3-6/+11
JIRA: DOVETAIL-376 Change-Id: I91e0efff01d445e3f74718d730c8ff48c6413b26 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-03-22Merge "dovetail tool: Bugfix about the prepare_env of yardstick and get the ↵hongbo tian2-9/+12
yardstick.log"
2017-03-21dovetail tool: remove installer and CI related variablesxudan9-101/+60
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>
2017-03-21dovetail tool: Bugfix about the prepare_env of yardstick and get the ↵xudan2-9/+12
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>
2017-03-20dovetail tool: change name of credentials from creds to openrcxudan6-14/+17
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>