Added upgrading Service Packs in SLES using SSM #76
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| - Feature Name: Apply Service Packs to SLES and/or openSUSE Leap using SSM | ||
| - Start Date: 2023-03-10 | ||
|
|
||
| # Summary | ||
| [summary]: #summary | ||
|
|
||
| Provice an easy mechanism to upgrade SLES and/or openSUSE Leap systems from one service pack the next one | ||
|
|
||
| # Motivation | ||
| [motivation]: #motivation | ||
|
|
||
| - Users of openSUSE and SUSE Linux Enterprise Server (SLES) need to update their versions. When doing it for a large installed base, an easier procedure could be performed using SSM. | ||
| - As a sysadmin I want to upgrade my installed base of OpenSUSE/SLES servers to latest version (i.e. SP4 to SP5) using SSM so that I can do it in less time and with control on which systems are selected. | ||
| - The outcome would be to have updates for my systems running from Uyuni / SUSE Manager for a set of systems selected with SSM. I could later on review status and check that everythign went fine, or any issue found. | ||
|
|
||
|
|
||
| # Detailed design | ||
| [design]: #detailed-design | ||
|
|
||
| Apply `zypper migration` to systems selected in SSM | ||
|
There was a problem hiding this comment. This would not be the implementation. We should use the mechanism we already have in place for migrate one machine, and allow the usage of SSM to upgrade multiple at the same time |
||
|
|
||
| # Drawbacks | ||
| [drawbacks]: #drawbacks | ||
|
|
||
| Why should we **not** do this? | ||
|
|
||
| * No corner cases observed | ||
|
|
||
| # Alternatives | ||
| [alternatives]: #alternatives | ||
|
|
||
| - Manual upgrade. (Slow, cumbersome and error prone) | ||
| - Customized script using API (Common use case, could be included in product) | ||
|
There was a problem hiding this comment. |
||
| - Using SALT states (not sure they can apply to SSM selections) | ||
|
|
||
| # Unresolved questions | ||
| [unresolved]: #unresolved-questions | ||
|
|
||
| - None so far. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we already this mechanism in place: https://documentation.suse.com/suma/4.2/en/suse-manager/client-configuration/client-upgrades-product-migration.html
What we would need is to have support to make in more then one minion at a time (batch SP migration)