Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
|
|
|
|
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>
|
|
centralize jjb related scripts
Change-Id: I4abeb06f17b48b8e7ac15803db0f3ce7eb0c1b93
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: Iba2a7b5de9cb56c2cc6579fb9ff37b3242a0283f
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
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>
|
|
This reverts commit 3f27c8b519e42295bd76ace5506903f265e48560.
Change-Id: I024ba8c0b960387138a71be9bc19f6d1b72030ca
|
|
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>
|
|
- 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>
|
|
|
|
minor pylint fix in functest/reporting-status
Change-Id: Ibfd4f0da1475c34c40a3d9e00530f8f15eb3c7dc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: Ia1ad4c0654ad2dea7fdb61b81725af9aaafc4750
Signed-off-by: liyin <liyin11@huawei.com>
|
|
Change-Id: I22df519d949fb28eaecc6af99347868023a1e2a8
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
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>
|
|
|
|
+ minor fixes
* unknown => real test case names
* pylint corrections
Change-Id: I75446e4006d41fe1bb25106420910025afa01489
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
http_pass is wrong for nginx, we need to change it to proxy_pass
Change-Id: Ib679b36a4a139c02647564719e1cfc49a9f376a2
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
Change-Id: Iee4c54801d839be949495360141d4ae9353e5ecc
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Changes to method call _set_query
Change-Id: I95837df57cc98c21ff5d95d9753269490c025dd3
Signed-off-by: utkarshrai98 <utkarshrai98@gmail.com>
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
Handle the error and show appropriate message,
without showing the entire error to the users
Change-Id: Ib5213190efc1e87d56a7329a4572b525a5e16a12
Signed-off-by: thuva4 <tharma.thuva@gmail.com>
|
|
remove the unnecessary "$rootscope" in the controller's parameters.
Change-Id: Ia048af9e146e871003307af27faca24a5ee225ca
Signed-off-by: thuva4 <tharma.thuva@gmail.com>
|
|
Now user can't create the pods with the same name.
Just like "Demo" , "deMo" and "demo"
Add unit test for case-insensitive query
Change-Id: Ifddc7b70a38d8504e5fe105fa5cc1a77bf0e39a9
Signed-off-by: thuva4 <tharma.thuva@gmail.com>
|
|
Since landing page have changed from reporting2 to testing,
the nginx configuration need some adoption.
If the pre url change again, we need to config the base_url when start
our docker container. For example:
docker run -itd -p 8084:8000 -e SERVER_URL testresults.opnfv.org/xxx/api opnfv/reporting:latest
Change-Id: If3c9f9af76fcfc8047b5b9559fcc8bd45740d4d2
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
you can disable requiretty by !requiretty or #requiretty
so catch both of those cases
Change-Id: Ic7fb1cf97849258b1e4db34be82794918bf722e0
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
repo [1]"
|
|
|
|
|
|
It has been transfered to sample vnf repo [1]
[1]: https://git.opnfv.org/samplevnf/tree/VNF_Catalogue
Change-Id: I418151bd24517efeb66fc0ae76cb9e091bd130f6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Changing the url of the reporting to the original one.
Change-Id: I2973a4b7d28cbdd725a4764dffbf777c3fc2e937
Signed-off-by: Sakala Venkata Krishna Rohit <rohitsakala@gmail.com>
|
|
Functest CI logs have been FAIL with compass but the CI logs are not
explicit. Remove a redirection to /dev/null to get something more
explicit
Change-Id: Icdf17595b051ccba6c58cbe86ab546e5693375ab
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
very basic approach based on 1 case posca_factor_ping
Give a feedback on the CI activity of bottlenecks
Change-Id: Iaa84abac6b00ba48a771250433a9f9a068de453f
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|