provisioning: add instructions for live-PXE via iPXE #121
Conversation
|
/cc @bgilbert |
|
I manually tested this with testing-devel artifacts on Vultr infrastructure in preparation for coreos/fedora-coreos-tracker#390. The example is referencing the next stable release coreos/fedora-coreos-streams#158, which is the first one with a the initramfs/rootfs split. The VERSION variable may need to adjusted if my guesstimation turns out to be off. |
|
|
||
| Since the traditional FCOS upgrade process requires a disk, live-PXE systems are not able to auto-update in place. For this reason, Zincati is not running there. | ||
|
|
||
| Instead, it is reccomended that images references in the PXE configuration are regularly refreshed. Once infrastructure and configurations are updated, the live-PXE instance simply needs to be rebooted in order to start running the new FCOS version. |
There was a problem hiding this comment.
Is there any way in the ipxe environment/config to do some logic to figure out what the latest is and use that? That would allow people to follow the latest without having to update their configs. The flip side of that is that someone could automate generating the ipxe config and just substitute in the latest version.
There was a problem hiding this comment.
Not that I've seen. Plus I'm not sure that would be a very good approach. We somehow consciously decided to steer away from the Container Linux way (having a current directory and not encoding version into file name), and this mostly follows from it.
What we could add here as a followup is showing how to mirror the current tip of a stream via coreos-installer download. That should make it slightly easier to automate and refresh (not fully though).
This adds a new guide showing how to provision a transient FCOS instance by live-PXE booting it via iPXE.
lucab
force-pushed
the
ups/booting-live-ipxe
branch
from
13bd70f to
1cd78e9
Compare
|
Rebased to avoid duplicated content. |
This adds a new guide showing how to provision a transient FCOS
instance by live-PXE booting it via iPXE.
Ref: #117