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):

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

@@ 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 -->
-= Build Fedora IoT using rpm-ostree unified core mode =
+= Build Fedora IoT using rpm-ostree unified core =
-{{Change_Proposal_Banner}}
 == 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.
+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: [[User:pwhalen| Paul Whalen]], [[User:idiez| Irene Diez]]
-* Email: <pwhalen@fedoraproject.org>, <idiez@redhat.com>
+* Email: pwhalen@fedoraproject.org, idiez@redhat.com
-<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
-* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
--->
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF40]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 25: / Line 20: @@
 [[Category:SelfContainedChange]]
-* Targeted release: [[Releases/40 | Fedora Linux 40 ]]
+* 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}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 33: / Line 28: @@
 ON_QA -> change is fully code complete
 -->
-* [<will be assigned by the Wrangler> devel thread]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/T4TMOSVB2P7ZVNMDJENHZTTKGEJ3TAL3/ Announced]
-* FESCo issue: <will be assigned by the Wrangler>
+* [https://discussion.fedoraproject.org/t/f40-change-proposal-build-fedora-iot-using-rpm-ostree-unified-core-self-contained/101959 Discussion thread]
-* Tracker bug: <will be assigned by the Wrangler>
+* 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>
 == 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.
+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 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:
+Related changes (already complete):
 * https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore
@@ Line 52: / Line 46: @@
 == 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.
+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 ==
@@ Line 66: / Line 60: @@
 == How To Test ==
-* Upgrade to Fedora 40 IoT Edition
+* Upgrade to Fedora 40 IoT Edition or deploy a new installation.
 == User Experience ==

Search

Changes/Fedora IoT Unified Core: Difference between revisions