Meeting minutes from Leap Micro 5.2 migration testing discussion
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
Hello together,
Gesendet: Donnerstag, 13. Januar 2022 um 11:18 Uhr Von: "Lubos Kocman" <lubos.kocman@suse.com> An: "factory@lists.opensuse.org" <factory@lists.opensuse.org> Cc: "results@suse.de" <results@suse.de> Betreff: Meeting minutes from Leap Micro 5.2 migration testing discussion
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
That is only a little bit correct. I created an (un-)official documentation for a migration from SLES to Leap on zsystems: https://en.opensuse.org/ZSystems/Upgrade_SLES_to_openSUSE That is required in our team to use openSUSE in the LinuxONE Community Cloud. Only Enterprise distributions are officially supported by IBM and that is the possibilty to develop based on openSUSE then. This upgrade path is tested with SLES 15 SP1 and SLES 15 SP3. You can make it official and use it also for Leap Micro. Best regards, Sarah P.S. One hint. IBM is already providing minimal SLE installations. Therefore, the change for SLE Micro makes it more interesting.
Sarah Julia Kriesch píše v Čt 13. 01. 2022 v 12:12 +0100:
Hello together,
Gesendet: Donnerstag, 13. Januar 2022 um 11:18 Uhr Von: "Lubos Kocman" <lubos.kocman@suse.com> An: "factory@lists.opensuse.org" <factory@lists.opensuse.org> Cc: "results@suse.de" <results@suse.de> Betreff: Meeting minutes from Leap Micro 5.2 migration testing discussion
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
That is only a little bit correct. I created an (un-)official documentation for a migration from SLES to Leap on zsystems: https://en.opensuse.org/ZSystems/Upgrade_SLES_to_openSUSE
Ah yes but that is for Leap to SLES or SLES to Leap. This is a different distribution (Leap Micro) where we have to use transactional-update migrate etc ... However it should be close to identical to migraton of Leap to SLES with transactional updates on.
That is required in our team to use openSUSE in the LinuxONE Community Cloud. Only Enterprise distributions are officially supported by IBM and that is the possibilty to develop based on openSUSE then. This upgrade path is tested with SLES 15 SP1 and SLES 15 SP3. You can make it official and use it also for Leap Micro.
Best regards, Sarah
P.S. One hint. IBM is already providing minimal SLE installations. Therefore, the change for SLE Micro makes it more interesting.
-- Best regards Lubos Kocman openSUSE Leap Release Manager
participants (2)
-
Lubos Kocman -
Sarah Julia Kriesch