| Line 25: | Line 25: | ||
[[Category:SelfContainedChange]] | [[Category:SelfContainedChange]] | ||
* Targeted release: [ | * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f40/ Fedora Linux 40] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Revision as of 19:40, 15 January 2024
Build Fedora IoT using rpm-ostree unified core mode
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Upstream rpm-ostree development is now focused on "unified core" mode, with plans to deprecate the previous mode in the near future. Fedora IoT is the last rpm-ostree based Fedora edition using this older, soon to be deprecated mode with SilverBlue and Kinoite making the change in Fedora 39. The main advantage of building with unified core mode is that it is stricter and safer, while enabling some post processing steps to happen during or after the image build.
Owner
- Name: Paul Whalen, Irene Diez
- Email: <pwhalen@fedoraproject.org>, <idiez@redhat.com>
Current status
- Targeted release: Fedora Linux 40
- Last updated: 2024-01-15
- [<will be assigned by the Wrangler> devel thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
For more details about the difference between the two modes, you can read the upstream issue: https://github.com/coreos/rpm-ostree/issues/729. See also the history in https://pagure.io/workstation-ostree-config/issue/137.
In addition to the advantages listed above, unified core support is required for adding bootupd integration to Fedora IoT and to align with other ostree editions.
Related changes:
- https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore
- https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
Feedback
Benefit to Fedora
The old mode in rpm-ostree is not maintained anymore, less tested and thus prone to bugs. Moving to the new mode will unify IoT with what is used to build Fedora CoreOS, SilverBlue and Kinoite as well as benefit from the additional testing of those editions. This will also remove maintenance burden on the rpm-ostree project as they will be able to remove the old legacy code. The new mode makes composes work the same on the server side as the client side and makes them safer by more strictly confining scriptlet execution.
Scope
- Proposal owners: Testing with the new mode to ensure there are no regressions.
- Other developers: N/A
- Release engineering: #11815
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A
- Alignment with Community Initiatives: N/A
Upgrade/compatibility impact
- There will be no impact to end users, upgrades will work the same as previous releases
How To Test
- Upgrade to Fedora 40 IoT Edition
User Experience
- There will be no impact to users.
Dependencies
N/A
Contingency Plan
- Contingency mechanism: Revert to older non-unified core mode.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change)
Documentation
N/A (not a System Wide Change)
Release Notes
N/A