Skip to content
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

Port GCE OEM setup to systemd-sysext image #1146

Closed
pothos opened this issue Aug 2, 2023 · 0 comments · Fixed by flatcar/scripts#1441
Closed

Port GCE OEM setup to systemd-sysext image #1146

pothos opened this issue Aug 2, 2023 · 0 comments · Fixed by flatcar/scripts#1441
Assignees
Labels
area/sysext sysext roadmap

Comments

@pothos
Copy link
Member

pothos commented Aug 2, 2023

As was already done for the Azure OEM setup in #769 we want to port the GCE OEM setup over to systemd-sysext to benefit from updates.

A benefit of sysext images is that they can have a strict coupling to the Flatcar VERSION_ID which enables to use dynamical linking to save space and make the OEM tool packages simpler: we can remove the GCE nspawn "container".
The base Ignition configuration is also not needed anymore because the sysext's OEM files already become part of the /usr hierarchy and systemd services there can get started through an Upholds= drop-in.
For the /etc/profile.d/google-cloud-sdk.sh file we probably need a helper systemd unit that sets up symlinks to the file in the sysext image. The ssh service enablement is common for many OEMs and we should cover this from the base image as suggested in #1142.

The migration action has to be defined in the update_engine flatcar-postinst hook like it was done for Azure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sysext sysext roadmap
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants