...
- improve CI chains and CI testing gate
- new smoke use case
- vFW CL
- CDS
- ...
- integration of Portal GUI tests
- finalize windriver/gitlab.com pipelines
- introduce a weekly CI chain including robustness tests
Caterogy | Task | nb people interested (add a "|" if you think it is valuable) | contacts | priority | Comment |
---|---|---|---|---|---|
X-project | maintain java11 | | | |||
create python 3.8 baseline | | | ||||
maintain oparent | | | ||||
Repositories | Finalize generalization of linters | | | |||
Create new repo (simu/use cases) | | | ||||
reinsource build chain for java | | | medium | it is working very well in gitlan..but it is better to reinsource if we want to have contributors only allowed to contribute to ONAP. it is cleaner | ||
reinsource xtesting build chain | | | low | same than for java | ||
testsuite | adopt microservice approach | | | we missed it in Frankfurt to be done with the python3 final step + OOM chart back to helm | ||
finalize python3 migration | | | ||||
Move OOM chart back to helm | | | ||||
use case | create a starting guide | | | can be based on the slide deck shared with use case people | ||
create overide.yaml per use case / to dedicated automatic deployment | | | will depend if issue on windriver (slow access through python client) is fixed | |||
tests | update/maintenance of existing tests | | | all | ||
component coverage | good idea but how to do that... | ||||
discussions with projects to improve healthcheck | | | status to be shared with PTLs + discussed with RM to set a milestone criteria? | |||
update security tests - check versions of upstream components | | | ||||
update security tests check java11/python3.8 | | | ||||
update security tests - check certificates validity | | | there was a script somewhere..need to find it, create a test and integrate it in CI | |||
update security tests - check limits | || | test already exists and in CI => not valid for daily (unlimited) but good in gating to be used for Guilin criteria | |||
update existing security tests (review xfail list, cist,..) | | | the xfail lists of the different security tests will be reset for guilin | |||
archive CIST? | | | current CSIT = functional tests => must be reinsourced by the project real CIST must be in CI | |||
move CIST to E2E tests in CI | | | to be discussed with the projects maintaining their CIST tests | |||
deprecate onap-tests / use python-onapsdk | | | ||||
Support OOM for a migration | | | ||||
stress tests | | | ||||
long duration tests | | | ||||
update integration web page | | | ||||
Labs | supervision/monitoring | | | |||
Create a ops guideline (with OOM?) | | | ||||
infra gate (functest)? | | | ||||
CI/CD | Integrate vFW Cl test | | | |||
Integrate CDS tests | | | ||||
Integrate GUI tests | | | ||||
Create 5G xtesting dockers and integrate in CI? | | | ||||
finalize windriver pipelines | | | ||||
introduce a weekly pipleine (for long duration tests) | | |