summaryrefslogtreecommitdiffstats
path: root/utils
AgeCommit message (Collapse)AuthorFilesLines
2017-10-27bugfix: E722 do not use bare exceptSerenaFeng3-4/+4
new added pep8 check: https://build.opnfv.org/ci/job/testapi-verify-master/435/console Change-Id: I29c1ffbb534babf55ec2fe675001cc85b9e2e922 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-23Merge "allow authentication to be disabled"Serena Feng5-8/+18
2017-10-20bug fix: score calculation based on build_tagMorgan Richomme1-3/+4
we were used to count the number of PASS of the last 4 runs it works 80% of the cases 4 runs 4 OK => 3 points 3 OK => 3 points 2 OK => 2 points 1 OK => 1 point 0 => 0 it is different from the normal score calculation 4 OK => 3 points 3 OK => 2 points 2 OK => 2 points 1 OK => 1 point 0 => 0 Change-Id: Ib8df2c294e0036246176c181b7a7ac290ebea07e Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-20allow authentication to be disabledSerenaFeng5-8/+18
in local deployment situation, authentication can be disabled by setting authenticate=False of ui section in config.ini JIRA: RELENG-324 Change-Id: I9157d1723851feb12435033dbdd59035e3eb5777 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-20criteria field must be 'PASS/FAIL'SerenaFeng5-2/+33
criteria must be fix with 'PASS/FAIL', case insensitive or else, BADREQUEST exception will be raises JIRA: RELENG-327 Change-Id: Ic648b9d38937fc63924e42cfdf5345cdaa32e1ed Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-19Extend the Functest reporting black listMorgan Richomme1-0/+2
remove * tempest_full_parallel * rally_full Change-Id: Ibb944e7d32dc3cf0fc0b87a269c9e2f0327410e4 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-18Add new function to get indivial test score for aarch64Morgan Richomme3-7/+54
as architecture is not considered as a constraints (unlike scenario or installer) we need to work on the build tag to retrieve the data but it is not possible to use regex directly in the API so retrieveing the accurate results require extra processing * based on build_tag, filter the results properly per scenario * build a table build_tag time for a given scenario * keep only the last 4 results * evaluation criteria field It would simplified if architecture could be declared as a constraint then querying the resuls will not change and not require intermediate steps JIRA: FUNCTEST-880 Change-Id: Id4fe4f56babf0964d41e299905c804e0d837c3d7 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-16delete legacy update codeSerenaFeng14-610/+0
update directory was employed to update TestAPI before auto deployment is adopted, now it is useless and can be deleted. Change-Id: I4e5ae84e80879cd9f711dc1d02224ae4f5902e49 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-16fix yamllint verify failSerenaFeng3-1/+5
fail record: https://build.opnfv.org/ci/job/opnfv-yamllint-verify-master/1050/console Change-Id: Ic709b9a3d1d3642a3deebd930714a2ba2de22da6 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-16Merge "Added license metadata to specify Apache-2.0"Serena Feng2-0/+2
2017-10-16Merge "Update table headers in the reporting page"Serena Feng1-3/+3
2017-10-13Added license metadata to specify Apache-2.0rpaik2-0/+2
Change-Id: Id2e6b148f896eee5122339e501c8604e74ef774c Signed-off-by: rpaik <rpaik@linuxfoundation.org>
2017-10-12Change criteria 'SUCCESS' to 'PASS' in yardstick reportingchenjiankun1-2/+1
To keep consistent with other testing project, yardstick should change criteria value from 'SUCCESS' to 'PASS' Change-Id: I8d8779927a74749e7c43df4e55e1888c49cbbbaf Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-10-12bugfix: trend graph not show in fuel x86 and aarch64chenjiankun1-2/+14
The trend tool will read installer field in scenario_history.txt But now this field is fuel not fuel@x86 or fuel@aarch64. So I change fuel -> fuel@x86 & fuel@aarch64. Change-Id: I8e97e57febd559f65be559b16bceee5cf8268926 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-10-11Merge "Fix jenkins-jnlp-connect.sh for missing a quotation mark"Aric Gardner1-1/+1
2017-10-11Merge "Add fuel@x86 and fuel@arm support"Morgan Richomme3-118/+166
2017-10-11Add fuel@x86 and fuel@arm supportchenjiankun3-118/+166
Since scenario data do not have a field named architecture, So I choose pod_name for now. For example: pod_name: arm-pod5 I assume that it is based arm architecture Change-Id: I92159a5e08b1ed80701494483fd9922dbd459193 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-10-11put htmlize directory under jjb/relengSerenaFeng3-105/+0
centralize jjb related scripts Change-Id: I4abeb06f17b48b8e7ac15803db0f3ce7eb0c1b93 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-10-10Fix jenkins-jnlp-connect.sh for missing a quotation markAlex Yang1-1/+1
Change-Id: Iba2a7b5de9cb56c2cc6579fb9ff37b3242a0283f Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-10-07Change score calculation for functest reportingMorgan Richomme1-5/+19
the goal is not to penalize scenario with few iteration due to CI pipeline constraints until now the top score was calculated on the base on 4 iterations, it means whatever the number of iterations, we always consider the possible top score based on at least 4 iterations each case can get - 3 points (last 4 iterations PASS) - 2 points (more than 1 PASS over the last 10 days but 1 FAIL of the last 4) - 1 point (at least 1 PASS over the last 10 days) - no point (never work) so if we consider a scenario with 10 cases, the top score is 30 = 10*3 (max points) the coefficient to calculate the top score is not the number of iterations - 1 iteration => possible top score 10 - 2 iterations => top score 20 - 3 iterations => top score 20 - 4 or more iterations => top score 30 previously top score was systematically 30 https://wiki.opnfv.org/plugins/servlet/mobile#content/view/6828617 Change-Id: I01102bc00766b7f5b58e73befa7d5328fcc895cc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-10-04Revert "fetch_os_creds.sh: Fix unbound BUILD_TAG"Alexandru Avadanii1-2/+4
This reverts commit 3f27c8b519e42295bd76ace5506903f265e48560. Change-Id: I024ba8c0b960387138a71be9bc19f6d1b72030ca
2017-10-04fetch_os_creds.sh: Fix unbound BUILD_TAGAlexandru Avadanii1-4/+2
Fuel baremetal deployments provide a certificate, which should be copied over to test containers. Virtual deployments do not, hence the need to determine the deployment type and decide whether the certificate should be transferred in the first place. However, the Docker args we contruct will try to map the certificate file no matter what, so we will instead try to transfer the cert from Salt Master in all deployments, and just create an empty file in case it does not exist. Change-Id: I3d3fe6cabf552a88841c529ce38446b2e54b3053 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-10-03Update table headers in the reporting pageYujun Zhang1-3/+3
Change-Id: I19916f1e4dd04297cc7d73e93a12767d335c0d99 Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
2017-09-30Fix status reporting pageYujun Zhang4-19/+12
- use data in last 10 days instead of 1 day - hide installers without any data - remove redundant qtip reporting Change-Id: If73a439572b6a1cf09c7d34f643fb14be82196ca Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
2017-09-29Merge "Fix Bottlenecks status page cann't be shown."Morgan Richomme1-1/+5
2017-09-29Change Euphrates imageMorgan Richomme2-3/+3
minor pylint fix in functest/reporting-status Change-Id: Ibfd4f0da1475c34c40a3d9e00530f8f15eb3c7dc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-29Fix Bottlenecks status page cann't be shown.liyin1-1/+5
Change-Id: Ia1ad4c0654ad2dea7fdb61b81725af9aaafc4750 Signed-off-by: liyin <liyin11@huawei.com>
2017-09-29Compass: fetch openrc for euphratesLinda Wang1-5/+5
Change-Id: I22df519d949fb28eaecc6af99347868023a1e2a8 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2017-09-26reporting adoption for Euphrateschenjiankun4-4/+4
Danube -> Euphrates in euphrates.html add euphrates dir fix CONFIG_REPORTING_YAML value fix import error in scenario.py Change-Id: Ic0457bf8d1c67bd21ef6a31564792eb98cfca9ad Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-09-25Merge "cloudify_ims reporting fixes"Morgan Richomme4-164/+182
2017-09-22cloudify_ims reporting fixesMorgan Richomme4-164/+182
+ minor fixes * unknown => real test case names * pylint corrections Change-Id: I75446e4006d41fe1bb25106420910025afa01489 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-22Merge "Bugfix: Change http_pass to proxy_pass"Morgan Richomme1-1/+1
2017-09-21Merge "bugfix: autoupdate failed due to mingle with watchdog"Morgan Richomme1-10/+7
2017-09-21refactor one click deployment in testapiSerenaFeng3-55/+55
substitue docker-compose.template with string description, so that user can wget deploy.py and execute directly. Change-Id: I9703a1c8dfbdc46470561d54c6663e3728540162 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-09-21bugfix: autoupdate failed due to mingle with watchdogSerenaFeng1-10/+7
1. In the original design, if the auto-job starts soon after the watchdog starts, the auto update might be mingled with connectivity check, which may lead to update failure. so instead, the connectivity is checked first, if failed and module is not in deploying, restart module. 2. only automate-docker-deploy job will impact the container status during auto-job, so substitue auto-job status check with automate-docker-deploy's 3. the watchdog is not only for testapi, but also for reporting, and all docker container server deployed in testresults.opnfv.org, so move it under utils/test/opts, which is leveraged to store tool-sets employed for testing tools. Change-Id: I766f3a534a3d510ce7509d4e742150150ccd8f54 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-09-20add one click deployment of testapi and reportingSerenaFeng1-0/+67
leverage docker compose to deploy testresults set testapi/reporting/mongo usage: python one_click_deploy.sh -tp 8082 -rp 8084 -tl http://host_ip:8082 Change-Id: I8dfb868637749b82ec86e58220376b03ad50664d Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-09-20Bugfix: Change http_pass to proxy_passchenjiankun1-1/+1
http_pass is wrong for nginx, we need to change it to proxy_pass Change-Id: Ib679b36a4a139c02647564719e1cfc49a9f376a2 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-09-20Merge "Add Euphrates pages for reporting"Morgan Richomme6-23/+267
2017-09-18Add Euphrates pages for reportingMorgan Richomme6-23/+267
Change-Id: Iee4c54801d839be949495360141d4ae9353e5ecc Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2017-09-18Bug Fix: Using library for urlencodeutkarshrai981-19/+18
Changes to method call _set_query Change-Id: I95837df57cc98c21ff5d95d9753269490c025dd3 Signed-off-by: utkarshrai98 <utkarshrai98@gmail.com>
2017-09-16Merge "testing for raise in config.py"Serena Feng1-0/+9
2017-09-12leverage LFID authentication to pod creationSerenaFeng10-23/+128
only valid linux foundation user is allowed to create the new pod add owner field in pods to track the pod creator Change-Id: Icada07152069f7c826bfa6122cb86db8c4e3bf68 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-09-12leverage token_check only when posting resultsSerenaFeng3-77/+17
In this patch begin to consider the LFID authentication, token check only effects results, the permission of other resources(pods/projects...) will be checked by LFID. Change-Id: I20f6f221e3bd75ebf06dcd91012898b913f1d0be Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2017-09-12testing for raise in config.pyutkarshrai981-0/+9
Change-Id: I3b4f21307af55c8f32332502ddcb9315074b7202 Signed-off-by: utkarshrai98 <utkarshrai98@gmail.com> Testing for the raise in test_config.py Change-Id: Iea7ae53b5eac51d3e3eaf9f23d6e8cd79919f103 Signed-off-by: utkarshrai98 <utkarshrai98@gmail.com>
2017-09-12Merge "add case-insensitive for find pods query"Serena Feng4-4/+24
2017-09-12Merge "update Readme.rst to be consistent with current implementation"Serena Feng1-36/+65
2017-09-11Merge "Fix for when requiretty is disabled with a !"Aric Gardner1-1/+1
2017-09-11Merge "Fix the error in the podscontroller."Aric Gardner1-2/+2
2017-09-11Merge "Handle error in front-end"Aric Gardner1-4/+5
2017-09-11fuel, armband: Remove SALT_MASTER_IP paramAlexandru Avadanii1-15/+15
Fuel@OPNFV mcpcontrol network (equiv to old admin/PXE net) has been configured to use 192.168.10.0/24 during E release cycle. However, due to overlapping with Ericsson-pod1 networks, we decided to re-use the old CIDR Fuel used before E release (10.20.0.0/24). This allows reusing the INSTALLER_IP param instead of recently added SALT_MASTER_IP param. Current change refactors all usage of SALT_MASTER_IP in favor of old INSTALLER_IP, thus reducing complexity and providing a familiar env to leagcy Fuel users. JIRA: FUEL-285 Change-Id: I1e89cca08ce4cb9bf3a82a06043c91ee26aa0794 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>