Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I33ad2bcb19e5dac01e6f1197924318aa49da5db2
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
Change-Id: I2553afdcc6515494c0a198cfa4091f1b214fe3f1
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I8dd00f3ef996c8847d803b690423bf381676e49d
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Vsperf do not follow OPNFV version/installer/scenario.
So we need develop a specific version.
In this patch, we do the follow change:
1. Get version from build_tag.
2. Remove installer for page.
3. Use case_name as primary key
4. Show the last 50 days for Vsperf job does not run frequently.
Change-Id: I6af50b5fcceadfcc0b66a0d9b45b3639f6a88421
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
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>
|
|
remove
* tempest_full_parallel
* rally_full
Change-Id: Ibb944e7d32dc3cf0fc0b87a269c9e2f0327410e4
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
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>
|
|
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>
|
|
|
|
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>
|
|
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>
|
|
Change-Id: I19916f1e4dd04297cc7d73e93a12767d335c0d99
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
- 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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: Ibfd36814ac09d16ba4b3d365e04bf3b39a1ef7db
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
fix some pep8 errors in other projects
Change-Id: Iea68b0d495f7fbe892ec866fb70b8354ad9ff3c2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
not updated since Colorado and data model changed
- minor fixes to match data model
- pep8/pylint correction
Change-Id: I3a0a9ea689d25b3cfff35cb1ec39329981627bc6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
- fix right path (version duplicated in path)
- fix template for nav links in qtip reporting page
Change-Id: I7e14bea3feb5e6fad694e2837b3048b9cd8d5825
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
the goal is to vizualize more quickly the HA and NOHA scenario
Note that if no scenario is available, the table title is displayed
Change-Id: Ibdade30aadf40fe4f7b9bfe547d23c186cb3e1df
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
- change node installation process
- clean setup (no need of pbr)
Change-Id: I9015486e3892e7c949bad5140cc4180ec9f07aa7
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Since testapi have done some changes on scenarios api,
so landing page should do some adoption.
Change-Id: Ib5d1df03e2c50c7d6c038200d97f2057b90e48af
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
In fuel we may deal with x86 or aarch64 architecture
We generate dedicated reporting page
- fuel@x86
- fuel@aarch64
However when there is no results for one of the architecture
the test on the number of architecture lead to a bug
Change-Id: I9906bd6078c8493587dc667eb23399a1e8311e77
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I5fd940b8c1be1c327cfcd481c27049f94ae2f175
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Testing reporting provides
- static reporting pages [1] (jinja2)
- landing pages including test case catalogue [2] (angular)
It consumes the Test API to build web pages providing status for
the testing projects (so far functest, yardstick, storperf and
qtip).
Dockerization has been initiated [3]. The goal is to replace the
static page hosted on testresults.opnfv.org by a docker regenerated
and redeployed when reporting code is changed
But the docker and more generally the testing reporting directory
must be refactored to
- manage dependencies properly
- leverage tox (py27, docs, pylint, pep8)
This patch
- setups tox (py27, pep8, pylint, docs)
- integrate the requirement management
- fix pep8 errors
- introduce 1 dummy unit test
This patch does not
- fix pylint errors
- create any doc
[1]: http://testresults.opnfv.org/reporting2/display/index.html
[2]: http://testresults.opnfv.org/reporting2/reporting/index.html
[3]: https://gerrit.opnfv.org/gerrit/#/c/36735/
Change-Id: I4613de7ca7036d6c6bbb8f58ade492b1d673599b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
In the patch, I make build pages(landing page ...),
when docker build, when run a container, we can set
the api url(default:testresults.opnfv.org/reporting2) by -e;
For example:
1. In testresults.opnfv.org:
docker run -itd -p 8888:8000 -p 80:80 opnfv/reporting:tag
visit: http://testresults.opnfv.org/reporting2/reporting/index.html
2. Personal use:
docker run -itd -p 8888:8000 -p 80:80 -e SERVER_URL=192.168.131.2:8888 opnfv/reporting:tag
visit: http://192.168.131.2:8888/reporting/index.html
Change-Id: Ib838c12e785151acf9852f25eab254aedc520a1d
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
Jenkins Jobs have been added for automating the deployment of the
reporting dashboard. Also multijob has been added for automating the
update of docker in the docker hub and generating docs which is empty
for now. Modified unit tests of reporting to make it run from any
directory.
Modified the testapi jenkins jobs yaml file to generic so that many
other modules which may have the same usecases can be integrated easily
just like the reporting one that is done now.
Change-Id: Id13a55416e17199dae1dd6ce64f7c167d117ba37
Signed-off-by: Sakala Venkata Krishna Rohit <rohitsakala@gmail.com>
|
|
Change-Id: Ifb2047e688117c7c9af33031467f2025d530f187
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Due to pagination feature introduced in test API, reporting pages
only considered the first page of results retrieved by the API
the number of pages is now detected to aggregate the results
JIRA: RELENG-259
Change-Id: I0ac90b125baf8c16341c8db22f5602fedd4cdf1b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: Ic9792023b9041dbe8081ff9840caa2cf2901b189
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
JIRA: RELENG-231
Change-Id: Id0b770575c0d91a58b3503f8580bd658337b2cd0
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Change-Id: Iff8ada7637648a320fc7ef4a0fb3e187186964e5
Signed-off-by: Ray Paik <rpaik@linuxfoundation.org>
|
|
- remove link to daisy for storperf results
- fix yardstick installer page links
Change-Id: Idae2163862c681db05cfc24c5c29eaea793d3c88
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
as case have been renamed in testcases.yaml
no more need or translation name/Db name
Change-Id: I0656ec478369224d44d9c3cdf0c6426f140e4029
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|