Changes/Fedora IoT Unified Core

Guidance
For details on how to fill out this form, see the documentation.

Build Fedora IoT using rpm-ostree unified core mode

This is a proposed Change for Fedora Linux.
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

rpm-ostree upstream development is focusing on the "unified core" mode and the previous mode is being deprecated. Fedora IoT is currently building using the old mode and we've wanted to move over for a while. The main advantage of the 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>, <>

Current status

• Targeted release: Fedora Linux 40
• Last updated: 2023-11-29
• [<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.

On top of the advantages listed above, we need unified core support to be able to add bootupd integration to Fedora IoT and to align with other ostree editions in Fedora.

Scope

• Proposal owners:

• Other developers:

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with Community Initiatives:

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)