On Fri, Feb 21, 2020, at 4:46 PM, Benjamin Gilbert wrote:
On Fri, Feb 21, 2020 at 10:57 AM Joel Kessler
<joel(a)kessler.family> wrote:
> The reason for putting my own partition in front of the system partitions, would be
that if I re execute ignition on this device
> the defined partition should not be erased and possible to expand with a new
ignition file. The sysroot partition should get all the remaining space.
There's currently no way to put a new partition before the partitions
shipped with the OS. Work is in progress to allow moving the root
partition, but I don't expect that we'll ever support moving /boot or
/boot/efi.
In general, Ignition is intended to run exactly once per system, and
running it more than once is not supported. (There is a limited
exception for live ISO/PXE systems, where, arguably, every boot is the
first boot.) Why do you want to run Ignition more than once?
How does one reprovision an existing machine without losing its data? How can one update a
machine's config when the canonical config is the ignition?
For the latter, I hope to write an ansible role that takes an .fcc as input and enforces
it on a host. Obviously doesn't work with arbitrary scripts, but anything declarative
should work in concept...
V/r,
James Cassell