This is a draft page to be discussed with Integration team to define priorities for Guilin
X-projects
- Maintain java11
- create python3.8 baseline image
Repositories
- Adopt the approach to create a repo for new use cases / simulators
- Add linters to all the new repositories
- Add new linters (tobot, bashate, rst)
- How to get a consistent view on all the repositories, shall we tag all the repositories,..
- update xtesting repo and put in place the build chain in ONAP (move from gitlab.com to ONAP)
- update jave/python3.8 in ONAP (move from gitlab.com to ONAP)
Robot pod
- Adopt micro-service approach introduced by Daniel (propto in F)
- move the helm chart back to OOM
Use case support
- Write an documentation 'Use case guideline"
- Test creation of an override.yaml per use case to be able to deploy adhoc environment in windriver
Tests
- update the tests
- harden the simulators/emulators (no more in xfail lists)
- clean? are all the tests still maintained?
- archive CIST? => projects can bring back their tests in their repository but jenkins CSIT not needed anymore
- move some of the CIST tests in Daily CI
- introduction of python_sdk for new tests (deprecate onap-tests)
- improve security tests (Integration and Built Tests For Releases)
- How to measure the test coverage?
- How to get better healthcheck tests and "force" project to update them when they provide a new version of their code
- Support OOM on a use case for Core on F→ G migration
Labs
- include endpoint supervizion page? (cachet?)
- Ops guideline (Zabbix/Prometheus/...) ?
CI/CD
- 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 | people interested | 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 | ||||
| reinsource xtesting build chain | ||||
| testsuite | adopt microservice approach | |||
| finalize python3 migration | ||||
| Move OOM chart back to helm | ||||
| use case | create a starting guide | |||
| create overide.yaml per use case / to dedicated automatic deployment | ||||
| tests | update/maintenance of existing tests | |||
| component coverage | ||||
| discussions with projects to improve healthcheck | ||||
| update security tests - check versions of upstream components | ||||
| update security tests check java11/python3.8 | ||||
| update security tests - check certificates validity | ||||
| update security tests - check limits | ||||
| update existing security tests (review xfail list, cist,..) | ||||
| archive CIST? | ||||
| move CIST to E2E tests in CI | ||||
| 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) |