The items on this page are determined during M1 of the release process
| Item | RA Dependency (version) | Validation Plan (description or link) | Notes |
|---|---|---|---|
| RI1 | RI1 is unsupported for the Lakelse release. This was discussed and acknowledged by the TSC at the July 13 TSC meeting. | ||
| RI2 | RA2 Kali | Validated by running the corresponding RC2 testsuite in GitLab. This RC-2 testsuite version is determined based on the Kuberenetes version deployed by RI2 Kuberef. | Currently the old "opnfv-poc" space in GitLab is used. In order to migrate the functionality to the "Anuket" project in GitLab, maintainer role would be required to setup/configure runners. |
| RC1 | RA1 Lakelse | Fully automatically verified by gates and deliverable verifications as described in RC guidelines https://github.com/cntt-n/CNTT/tree/master/doc/ref_cert#readme | Functest Wallaby was released May 23 https://lists.onap.org/g/onap-tsc/message/7864 RC1 leverages its own RA1 compatible (regarding RC1 testing coverage) SUTs. Then it avoids the former OPNFV circular dependencies between test tools and installer (not to reproduce the falsy wheel between RI1 and RC1) It should be noted that Jenkins had been partially down for a month (being shutdown during 2 weeks + build servers hs). Jenkins action plan are needed before any RC1 or RC2 commitment. |
| RC2 | RA2 Lakelse | Fully automatically verified by gates and deliverable verifications as described in RC guidelines https://github.com/cntt-n/CNTT/tree/master/doc/ref_cert#readme | RC2 leverages its own RA2 compatible (regarding the testing coverage) SUTs Then it avoids the former OPNFV circular dependencies between test tools and installer (not to reproduce the falsy wheel between RI1 and RC1) It should be noted that Jenkins had been partially down for a month (being shutdown during 2 weeks + build servers hs). Jenkins action plan are needed before any RC1 or RC2 commitment. |
...