Closed berendt closed 2 years ago
New role access model / scoping in Yoga is not yet activated by default, needs more testing and maturing. https://github.com/osism/issues/issues/269 Focus topic for R4.
Daily CI on yoga, use stable branches ("zuul-3") in testbed. Upgrade test is incomplete, not yet automated, documentation for test missing. Manual tests have been carried out successfully.
Enabling automated upgrade tests for yoga is a goal for R3, own story.
Release Notes: Link upstream docs, only reproduce highlights relevant for SCS in our own docs.
Services to test: OpenStack core, octavia, designate, barbican, ceilometer (see testbed deployment scope). http://docs.osism.de/testbed/overview.html#software-bill-of-materials-sbom
Test upgrades still cause problems according to @ra-beer. Will be verified by tomorrow. If need be, a separate call will be scheduled.
Testbed switched to Yoga by default: https://github.com/osism/testbed/commit/21ef67458f46205dee34f339425be6952f72243d
Upgrade tests in testbed enabled (Xena -> Yoga), no more problems there.
An open point at the moment is to scan the release notes of Yoga for special features and to list them in the release notes of OSISM. Everything else is done.
As a potential SCS operator, I want to have the ability to deploy (a well-working and tested) OpenStack Yoga with SCS R3 (2022-09) release. As existing SCS operator, I want to have the ability to seamlessly upgrade from previous SCS R2 (Xena) to SCS R3 (Yoga).
TODO
Definition of Ready:
Definition of Done: