setup-root: Detect initial sysext MVP#62
Merged
pothos merged 2 commits intoflatcar-masterfrom Jun 6, 2023
Merged
Conversation
We have implemented the building of OEM sysext images but the update path is still in progress. Instead of blocking the migration for new deployments, we will lose the version coupling by using "initial" as version in the file name and SYSEXT_LEVEL instead of VERSION_ID for the extension release file. Detect the initial sysext MVP path to activate the OEM sysext.
The list of old files per OEM needs to be maintained somewhere. Instead of doing this in the initrd script, we can use the update-engine post-inst action which already is a place for migration logic. Expect that the post-inst action writes all old OEM files to clean up to the migration flag file that triggers the deletion.
This was referenced May 31, 2023
Member
|
I'll pull this PR into flatcar/scripts#858. |
krnowak
approved these changes
Jun 6, 2023
Member
Author
|
I'll create a follow up for the download now that we know the file name for the fallback download from release artifacts ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
setup-root: Detect initial sysext MVP
We have implemented the building of OEM sysext images but the update
path is still in progress. Instead of blocking the migration for new
deployments, we will lose the version coupling by using "initial" as
version in the file name and SYSEXT_LEVEL instead of VERSION_ID for the
extension release file.
Detect the initial sysext MVP path to activate the OEM sysext.
setup-root: Read old OEM files from the migration flag file
The list of old files per OEM needs to be maintained somewhere. Instead
of doing this in the initrd script, we can use the update-engine
post-inst action which already is a place for migration logic.
Expect that the post-inst action writes all old OEM files to clean up to
the migration flag file that triggers the deletion.
How to use
Requires changes in https://github.com/flatcar/scripts/pull/858/files#diff-3b2def625e0988b47d34144d412cb632e946cd13b7b57ad3918b4322cbef9262R165 to use SYSEXT_LEVEL and in https://github.com/flatcar/scripts/pull/858/files#diff-1390361e20f8ec710779da5680655da8aef20d972df05b5c0c4ca5e3ad80a1adR552 to overwrite the version to be
initialTesting done
to be done with the scripts PR