Previous discussion with PM: https://etherpad.opensuse.org/p/ReleaseEngineering-leap-micro-discussion-202... ## Attendees lkocman, wgao, drahn, marita, lemon, jstehlik, jsrain ## Background PM Requested Community edition of SLE Micro. First release will be 5.2. Timeline: Devel start is mid January 2022, April 2022. ## Migration Matrix We're testing Leap -> SLES migration. Do we want to test Leap Micro -> SLE Micro migration as well? PM: Our usecase is mainly Rancher. Best way to ensure that this works is to test this scenario. Marita: Wei you're doing migration from Leap to SLES. It's relatively basic testing in openQA. Marita: Wei and Lemon what do you need to know about this request? Jiri: There is only live migration, and user needs to invoke transactional-update migrate (transaction-update is wrapper for zypper). Wei: we'll need some time Jiri/Daniel: it already works on 5.1 (prototype of Leap Micro 5.1 can already be accessed https://build.opensuse.org/project/show/openSUSE:Leap:Micro:5.1) Jiri: Jose already works on SLE Micro 5.0 -> SLE Micro 5.1 migration via transactional update. SLE Micro 5.1 -> 5.2 is still waiting on submission of the new SUSEConnect-ng. And we're also waiting for the SCC setup. https://confluence.suse.com/display/SMO/Leap+Micro+5.1 5.0 -> 5.1 migration test https://openqa.suse.de/tests/7966564 Jiri: Real work on testing will not be able to start prior mid February. Wei: what about arches for migration testing? Daniel for migration testing on a single platform should be sufficient. Jiri: Priority list is x86_64 (must have), aarch64 (could have), system-z (could have) Wei: for the Leap to SLE Migration, is there any documentation. Not yet Lubos: there is nothing official yet. Wei: we will need some steps Lubos: let's start with documentation here https://en.opensuse.org/SDB:System_upgrade lkocman: I can provide steps for 5.1 Once we have confirmed that this works, we'd create a official documentation request for documentation.suse.com. It would be similar to https://en.opensuse.org/SDB:System_upgrade but with transactional- update instead. Jiri/Lubos: steps should be the same as in case of Leap -> SLE migration with transactional update. lkocman: let's create this request in form of PM Pool (set Daniel as PM, and set SLE Micro 5.2 as a product). https://jira.suse.com/browse/PM-3278