From Fedora Project Wiki
< Changes
No edit summary |
|||
| (21 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= Build Fedora IoT using rpm-ostree unified core | = Build Fedora IoT using rpm-ostree unified core = | ||
== Summary == | == Summary == | ||
Upstream rpm-ostree development is now focused on "unified core" mode, with plans to deprecate the previous mode in the | Upstream rpm-ostree development is now focused on "unified core" mode, with plans to deprecate the previous mode in the 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. This change will align IoT with the other ostree-based editions in Fedora. | ||
== Owner == | == Owner == | ||
* Name: [[User:pwhalen| Paul Whalen]], [[User:idiez| Irene Diez]] | * Name: [[User:pwhalen| Paul Whalen]], [[User:idiez| Irene Diez]] | ||
* Email: | * Email: pwhalen@fedoraproject.org, idiez@redhat.com | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF40]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 29: | Line 28: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* [ | * [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/T4TMOSVB2P7ZVNMDJENHZTTKGEJ3TAL3/ Announced] | ||
* FESCo issue: | * [https://discussion.fedoraproject.org/t/f40-change-proposal-build-fedora-iot-using-rpm-ostree-unified-core-self-contained/101959 Discussion thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/3161 #3161] | ||
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2263306 #2263306] | |||
* Release notes tracker: <will be assigned by the Wrangler> | * Release notes tracker: <will be assigned by the Wrangler> | ||
== Detailed Description == | == Detailed Description == | ||
To learn about the differences between unified core and the previous mode, please read the upstream | To learn about the differences between unified core and the previous mode, please read the upstream [https://github.com/coreos/rpm-ostree/issues/729 issue]. The main advantage is that it is stricter and safer, while enabling some post processing steps to happen during or after the image build. In addition, unified core support is required for bootupd integration in Fedora IoT and to align with other rpm-ostree editions in Fedora. | ||
In addition | |||
Related changes (already complete): | Related changes (already complete): | ||
| Line 48: | Line 46: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
The previous | The previous mode in rpm-ostree is not maintained anymore, less tested and thus prone to bugs. Moving to unified core will align IoT with what is used to build Fedora CoreOS, SilverBlue and Kinoite as well as benefit from the additional testing those editions receive. Making the change in IoT should also reduce the maintenance burden from the rpm-ostree project as they will be able to remove the old code. Unified core makes composes work the same on the server side as the client side and makes them safer by more strictly confining scriptlet execution. | ||
== Scope == | == Scope == | ||
Latest revision as of 09:12, 8 February 2024
Build Fedora IoT using rpm-ostree unified core
Summary
Upstream rpm-ostree development is now focused on "unified core" mode, with plans to deprecate the previous mode in the 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. This change will align IoT with the other ostree-based editions in Fedora.
Owner
- Name: Paul Whalen, Irene Diez
- Email: pwhalen@fedoraproject.org, idiez@redhat.com
Current status
- Targeted release: Fedora Linux 40
- Last updated: 2024-02-08
- Announced
- Discussion thread
- FESCo issue: #3161
- Tracker bug: #2263306
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
To learn about the differences between unified core and the previous mode, please read the upstream issue. The main advantage is that it is stricter and safer, while enabling some post processing steps to happen during or after the image build. In addition, unified core support is required for bootupd integration in Fedora IoT and to align with other rpm-ostree editions in Fedora.
Related changes (already complete):
- https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore
- https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd
Feedback
Benefit to Fedora
The previous mode in rpm-ostree is not maintained anymore, less tested and thus prone to bugs. Moving to unified core will align IoT with what is used to build Fedora CoreOS, SilverBlue and Kinoite as well as benefit from the additional testing those editions receive. Making the change in IoT should also reduce the maintenance burden from the rpm-ostree project as they will be able to remove the old code. Unified core 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 or deploy a new installation.
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