-
Notifications
You must be signed in to change notification settings - Fork 87
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
Dynamic parititioning scheme #74
Comments
@lzap did this PR get reopened on the new repo? |
melcorr
pushed a commit
to melcorr/foreman-documentation
that referenced
this issue
Sep 25, 2020
Yes I think we can close this one. |
melcorr
pushed a commit
to melcorr/foreman-documentation
that referenced
this issue
Oct 14, 2020
as part of issue theforeman#74
ianf77
pushed a commit
to ianf77/foreman-documentation
that referenced
this issue
Feb 14, 2022
as part of issue theforeman#74
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've noticed that we have an undocumented feature (surprise!): dynamic partitioning scheme. Since Foreman does not ship with any dynamic partitioning scheme, I've decided to file a PR to include one with the following explanation:
When a partition template contains line starting with "#Dynamic", the contents will be put into %pre shell scriplet rather and it's expected it creates a file "/tmp/diskpart.cfg" which is then included into the Kickstart partitioning section. This allows generating parititioning scheme on the managed node befure
Anaconda starts installation.
This template is an example of such dynamic partitioning scheme. It follows recommended scheme of Red Hat Enterprise Linux for servers (no extra allocation for hibernation):
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/ch-swapspace
The PR is here: theforeman/community-templates#672
The text was updated successfully, but these errors were encountered: