Age | Commit message (Collapse) | Author | Files | Lines |
|
- 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>
|
|
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>
|
|
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>
|
|
fix some pep8 errors in other projects
Change-Id: Iea68b0d495f7fbe892ec866fb70b8354ad9ff3c2
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>
|
|
|
|
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>
|
|
Change-Id: Ie573486080fbd36857ff0709d53f6bdcdd43363e
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: RELENG-165
In this patch, I upload the backend code
usage:
docker run -itd -p 8000:8000 -e SERVER_URL=server_ip:8000 opnfv/reporting:<tag>
note: must point SERVER_URL, it is the api server.
visit landing page:
http://server_ip:8000/reporting/index.html
Change-Id: I10121574e0c4b2733a8084c986d7a2746e7ce2a4
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
Create associated static storperf page
Prepare vsperf, qtip, bottlenecks
Put Yardstick scenario class into utils directory
Change-Id: I874d1733fe3f37dc5dd557559478e7e0b25371d7
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: RELENG-165
In this patch, I do the follow things:
1.deploy tornado server(currently I haven't write any backend code,
since the backend code depend on the testapi and I need to
communicate with Serena).
2.landing page code(almostly finished. But I haven't the data, so
for now, the data this page shows is a mock json. When the testapi
and my backend code ready, this page will finally finished)
3.deployment: supervisor + nginx + tornado + angular
usage:
docker run -itd -p 8000:8000 opnfv/reporting:<tag>
visit landing page:
http://server_ip:8000/reporting/index.html
test api:
http://server_ip:8000/landing-page/filters
visit old reporting page:
http://server_ip:8000/display/master/yardstick/status-apex.html
Change-Id: I527ab2661ce9e84b2942ebe673afbf5f2bc7878f
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
JIRA: RELENG-181
Since we just decide to use dynamic server, we need to deploy a dynamic
server such as tornado . But when I use the Dockerfile to build image,
it failed due to some reasons. So I need fix it first and then deploy
the dynamic server.
Then we can use this command:
docker run -it -d -p 8080:80 opnfv/releng:latest
And visit reporting page by http://server_ip:8080/display/...
Change-Id: Id04575c7b38e4c07625ce217d23ebca1c5bf0191
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
- dockerization
- create util function for all the test projects
- create a common config files
- add unit tests
- pep8
JIRA: RELENG-162
Change-Id: Ib209be4233084100ff238a7aeb2843ccc24a6f1e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|