...
dovetail and community development progress map
CI and POD resource for dovetail
...
question description in details: https://wiki.opnfv.org/display/dovetail/Dovetail+Home?preview=/2926467/8690170/dovetail%20requirements%20from%20infra_v1.pptx
| View file | ||||
|---|---|---|---|---|
|
CI resource: https://build.opnfv.org/ci/view/dovetail/
...
| SUT | status |
|---|---|
| fuel | ongoing |
| compass | ongoing |
| apex | ongoing |
| joid |
community regular CI test case run history(for each release)
...
http://testresults.opnfv.org/test/swagger/spec.html#!/spec/List_all_Test_Results
version=coloradodanube
case=?, such as tempestrefstack_smoke_serialdefcore
For yardstick
http://testresults.opnfv.org/grafana/dashboard/db/os-nosdn-nofeature-ha-sample
version=coloradodanube
Time filter: 20162016703/09/2220-2017/16/10 30 (Colorado.1danube1.0- Coloradodanube.3.0)
Remaing questions
For functest:
1. tempest_full_parallel not runs in CI in Colorado, however, some testcase proposed for compliance includes in tempest_full_parallel
Suggestion: put tempest_full_parallel into weekly CI in Danube
2. In Colorado, the failed testcase can be seen, however, in master/D, it doesn’t exists. Besides, the skipped testcase is also needed
Suggestion: keep failed testcase shown in master/D
patch: https://gerrit.opnfv.org/gerrit/#/c/28025/,refstack integration, completed and merged in Dabune.
For yardstick
1. If a testcase don’t have test result, didn’t run or failed? can’t make a judgement
...