Dynamic disk space partitioning during installation with a kick start file
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
We are using kickstart file to fully automate the OS installation. But recently we have different hard-disk storage volumes (500GB, 700GB, 1TB ...etc.). As of now we have to create multiple copies of the ISO image to handle that. This is a little bit hard to maintain and troubleshoot if any issue happened.
Describe the solution you'd like
Is it possible to have a parameter under the "partition" field to accept partition size as a precentage instead of the actual value.
As of now the partition feild looks like : {"mountpoint": "/boot", "size": 128, "filesystem": "ext4"}
Expected : {"mountpoint": "/boot", "sizeprecent": 10, "filesystem": "ext4"}
as per above example the /boot will have a 10% of the harddrive.
Describe alternatives you've considered
We have to create multiple copies of the ISO image
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the kickstart parser and the installation code that handles the partition field. Determine how available disk capacity is calculated, then verify that percentage-based partition sizes produce the requested partition proportions on disks of different capacities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100