Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GuidedProposal: internal settings to be used by Agama #1376

Merged
merged 3 commits into from
Mar 22, 2024

Conversation

ancorgs
Copy link
Contributor

@ancorgs ancorgs commented Mar 22, 2024

Problem

We wanted to add the following two functionalities to Agama:

  • Having volumes that automatically adjust their sizes based on the RAM size. As always in Agama, those automatic calculation need to offer the possibility of being overriden by the user.
  • Make a proposal without automatically adding the partitions needed for booting.

Solution

This adds two new settings to ProposalSettings and VolumeSpecification to make all that possible.

None of the changes affect YaST or AutoYaST for now.

Testing

  • Added new unit tests
  • Tested manually through Agama

Other pull requests

See agama-project/agama#1111 as an example on how Agama relies on this.

@coveralls
Copy link

Coverage Status

coverage: 97.81%. remained the same
when pulling 134a16d on ancorgs:agama_settings_fixed
into 92516eb on yast:master.

Copy link
Contributor

@joseivanlopez joseivanlopez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ancorgs ancorgs merged commit 123b26f into yast:master Mar 22, 2024
7 checks passed
@yast-bot
Copy link

❌ Internal Jenkins job #1151 failed

@yast-bot
Copy link

✔️ Internal Jenkins job #1152 successfully finished

ancorgs added a commit to agama-project/agama that referenced this pull request Mar 22, 2024
…ust_by_ram (#1111)

## Problem

In Agama a volume can have automatic sizes based on one or several of
the following reasons:

- Snapshots
- Fallbacks from other volumes (eg. "/" max size can exist or not based
on the existence of "/home")
- Size of the RAM

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

| The table | The form |
|-|-|
|
![table-auto](https://github.com/openSUSE/agama/assets/3638289/4f7d2b6f-b728-4d47-aca4-8321301e822a)
|
![form-auto](https://github.com/openSUSE/agama/assets/3638289/eb072fd2-011f-4eb8-8c02-1a218053254b)
|

Forcing manual sizes

| The table | The form |
|-|-|
|
![table-man](https://github.com/openSUSE/agama/assets/3638289/a25510fa-b4fd-40f4-bc4c-c096995a6c57)
|
![form-man](https://github.com/openSUSE/agama/assets/3638289/59994396-3627-4dac-b18b-5aa63ce0dbcc)
|



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

- Added a new unit test
- Tested manually (see screenshots above)

## Dependencies

Needs yast/yast-storage-ng#1376 at
yast2-storage-ng, which implies the corresponding rpm dependency has
been updated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants