Changes/ArmMinimalImageOSBuild: Difference between revisions

Revision as of 17:52, 16 January 2024

= Build Arm Minimal Image with osbuild

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

Build the Arm minimal image to be built using osbuild.

Owner

Name: Peter Robinson
Email: <pbrobinson@fedoraproject.org>

Current status

Targeted release: Fedora Linux 40
Last updated: 2024-01-16
[<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

The Fedora Arm Minimal image is widely used as a base for various usecases from low level board bring up right through to the basis of other images. Over time the existing ImageFactory build process has stagnated limiting our ability to enhance this image. The osbuild team have worked with the Arm SIG to enable a number of enhancements around things like Arm SystemReady and other such functionality to improve this image creation process and to make it easier to use these images with a much wider range of Arm devices making it easier to bring up new types of Arm device in Fedora. In the future we are planning further enhancements to ensure it's easy for developers and users to make use of the Fedora within the Arm ecosystem.

Feedback

Benefit to Fedora

The Fedora arm Minimal Image currently requires a number of changes and hacks to be used on specific devices or SoCs, the move to osbuild will reduce or entirely eliminate these hacks right away with further enhancements coming in the future.

Scope

Proposal owners:

The proposal owners will:

- Enable the creation of Minimal image using osbuild in pungi
- Test the available artifacts

Other developers:

Release engineering: #Releng issue number

Changes to the pungi config to use osbuild for minimal image will be submitted as a PR by feature owners.

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

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

Alignment with Community Initiatives:

Upgrade/compatibility impact

No upgrade impact. Only for new users.

How To Test

There will be a new Minimal Image, it will be testable in the same way as the old image. Test various SoCs with arm-image-installer to ensure devices boot and run as expected.

User Experience

There should be no change to the user experience for existing users. We will enable the wider use of

Dependencies

All changes are already in osbuild but we will work with the osbuild team if any issues arise.

Contingency Plan

The contingency plan is to build the Arm minimal image in the same way we currently do.

Documentation

There should be no changes required to documentation for existing users, docs will be updated for specific devices where enhancements have been made.

Release Notes

TBD.

@@ Line 51: / Line 51: @@
 == Scope ==
 * Proposal owners:
-The proposal owners will
+The proposal owners will:
-** Enable the creation of bootable containers artifacts in pungi
+** Enable the creation of Minimal image using osbuild in pungi
-** Work with the osbuild team to ensure artifacts are produced
+** Test the available artifacts
-** Test to ensure the user experience is what's expected
 * Other developers:
@@ Line 71: / Line 70: @@
 == How To Test ==
-There will be new bootc containers published, once they are enabled we will update documentation on how to use and consume them and ways to provide feedback.
+There will be a new Minimal Image, it will be testable in the same way as the old image. Test various SoCs with arm-image-installer to ensure devices boot and run as expected.
 == User Experience ==

Search