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

[WIP] Add support for /home reuse to automatic partitioning #5799

Closed
wants to merge 1 commit into from

Conversation

rvykydal
Copy link
Contributor

@rvykydal rvykydal commented Aug 5, 2024

This is a draft, POC of an approach, WIP (see the commit message). Esp. will need to be updated on top of #5435 but that should be fine.

Tested to be working on all partitioning schemes, reuse of unencrypted autopart.

The idea is kickstart (the request structure) just providing flexible enough mechanism, most of the logic, checks, assumptions should be in the UI / client providing the feature.

The kickstart API desn't have to be public/published, now it is just base for the discussion, tests, PartitioningRequest structure update and work on webui UI support.

Related pykickstart PR: pykickstart/pykickstart#499

@pep8speaks
Copy link

pep8speaks commented Aug 5, 2024

Hello @rvykydal! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 71:20: E111 indentation is not a multiple of four
Line 306:100: E501 line too long (103 > 99 characters)

Line 75:100: E501 line too long (100 > 99 characters)

Comment last updated at 2024-08-06 07:59:35 UTC

@github-actions github-actions bot added the f41 label Aug 5, 2024
We use destroy only for plain partition mountpoints as we can't destroy
lv or btrfs subvolume - it would not free space for the new one (and its
vg or btrfs volume). For lvs and btrfs subvols we reuse reformat from
mount point assignment (real erase would be perhaps better, even for
mount point assignment as recreating the device complicates the logic)

TODO:
+ unify biosboot partition with other stuff (configurable)
+ look at all roots
+ test with plain
+ test with lvm
+ test with thin lvm
+ --remove should fail silently?
+ kickstart support (--erase --reuse --remove)
- kickstart tests
- reuse fstab mount options (/home is missing compression)
+ add checks that the device found is unique (including biosboot/efi)
- checks for recreate only on plain partition?
- create check for usability of the /home reuse (for UI)
- update unit tests
- luks ?
- efi partitions, we have only biosboot so far
- update for device_id: rhinstaller#5435
- add better mount point assignment kickstart tests, we update code
there (fedora, lvm, plain)
@rvykydal
Copy link
Contributor Author

rvykydal commented Aug 9, 2024

I am going to rebase the PR on top of #5435 and #5810

@rvykydal
Copy link
Contributor Author

rvykydal commented Aug 9, 2024

I am going to rebase the PR on top of #5435 and #5810

Done in #5814, closing this one.

@rvykydal rvykydal closed this Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants