-
Notifications
You must be signed in to change notification settings - Fork 59
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
re-using existing disks when doing an install; re-creating partitions with Ignition #418
Comments
Specifically, the Ignition config for the live system would:
As an alternative, we could avoid step 3 by having step 1 inject the partition info into the Ignition config. But the proposed approach would be more self-contained. |
With this workflow, the data partitions selected for preservation may end up being lost if an issue were to happen (power loss, etc.) between the beginning of the installation process (step 2) and the partition restoration step (3). |
Also related to: #399 |
I am currently looking if it could be possible to reuse a partition layout while ensuring there is enough space for the installation thus avoiding the repartitioning step. |
Actually in the version using classic installer, I save the partitions numbers above partition Done properly no change in ignition is needed. |
Implemented via |
Thanks @bgilbert! The fix for this went into stable stream release |
During our internal cabal meeting, the topic of installing *CoreOS onto existing infrastructure was discussed; specifically the need for preserving existing partitions during the install phase.
One of the suggested approaches was to determine the existing partition table of a disk, determine which partitions need to be preserved, and then have Ignition create the partition table with the preserved partitions included.
@jlebon suggested we discuss this path for installing + preserving partitions in more detail, so filing this issue as place to start.
cc: @glennswest
The text was updated successfully, but these errors were encountered: