[Service] Make it possible to use non-auto sizes for volumes with adjust_by_ram #1111
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.
Problem
In Agama a volume can have automatic sizes based on one or several of the following reasons:
But the third one was not working because it was impossible to set the sizes manually for volumes with the property
adjust_by_ram
in their corresponding outline.Solution
This sets the new YaST setting
ignore_adjust_by_ram
if the user has decided to manually enforce sizes. So now it's possible to honor the automatic size or to use custom sizes instead.Using the automatic size
Forcing manual sizes
To get some background on how this functionality compares to the traditional YaST checkbox "Enlarge to RAM Size for Suspend", see the dedicated section at the description of #1081.
Additionally, this pull request enables
adjust_by_ram
for swap at the Tumbleweed product, to raise awareness and get feedback.Testing
Dependencies
Needs yast/yast-storage-ng#1376 at yast2-storage-ng, which implies the corresponding rpm dependency has been updated.