F40 Change Proposal: Fedora IoT Bootable Containers

Fedora IoT Bootable Containers

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.

wiki
Announced

:link: Summary

Fedora IoT uses OSTree to provide an OS suitable for Edge and IoT usecases, Ostree Native Container or Bootable Containers, are a new and interesting mechanism for both building and delivering OSTree content. This brings this initiative to Fedora IoT to enable other means of users consuming Fedora IoT.

:link: Owner

:link: Detailed Description

Fedora IoT uses OSTree to provide an OS suitable for Edge and IoT usecases, Ostree Native Container or Bootable Containers, are a new and interesting mechanism for both building and delivering OSTree content. This brings this initiative to Fedora IoT to enable other means of users consuming Fedora IoT.

:link: Feedback

:link: Benefit to Fedora

This benefits Fedora IoT users by being able to use container technologies in the build pipelines and OS definitions. It allows users to consume Fedora IoT in different ways that may better suit their environment and ecosystem allowing wider adoption. This is an expansion of the technologies available and there is no requirement for users to change.

This will deliver two bootc containers for Fedora IoT users, firstly a cut down minimal version for users to use as a base to build their own vision of Fedora IoT and well as the traditional Fedora IoT user experience.

:link: Scope

  • Proposal owners:

The proposal owners will

    • Enable the creation of bootable containers artifacts in pungi
    • Work with the osbuild team to ensure artifacts are produced
    • Test to ensure the user experience is what’s expected
  • Other developers:

  • Release engineering: #Releng issue number

There’s no direct requirement from release engineering. We may need some adjustment to the koji-osbuild policy.

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

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

  • Alignment with Community Initiatives:

:link: Upgrade/compatibility impact

There is no upgrade impact, this is a new means of deployment of Fedora IoT, existing users and artifacts will continue to work as usual.

:link: 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.

:link: User Experience

There will be a new user experience available for new deployments of Fedora IoT as well as for upgrades where users wish to be able to pull updates via a container registry.

:link: Dependencies

There’s some dependencies on in-progress work in osbuild which we are coordinating with the osbuild team.

:link: Contingency Plan

The contingency plan is to delay shipping OSTree bootable containers if we run into issues with producing them.

:link: Documentation

The Fedora IoT docs will be updated as part of this change.

:link: Release Notes

TBD.

3 Likes

With the move to OSTree Native Containers, will that make it so that every update or channel available is using this model, or will there be a version of Fedora IoT that uses that current model for updates where only the changes to the OS are merged?

The current model remains, this is an additional prototype component.

2 Likes

This change proposal has now been submitted to FESCo with ticket #3160 for voting.

To find out more, please visit our Changes Policy documentation.

1 Like