From Fedora Project Wiki
(Created page with "= Move Fedora CoreOS updates from OSTree to OCI =")
 
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Move Fedora CoreOS updates from OSTree to OCI =
= Move Fedora CoreOS updates from OSTree to OCI =
{{Change_Proposal_Banner}}
== Summary ==
Change Fedora CoreOS to receive updates from quay.io/fedora/fedora-coreos instead of the Fedora OSTree repository.
== Owner ==
* Name/Email: [[jbtrystram | Jean-Baptiste Trystram]], jbtrystram@redhat.com
* Name/Email: [[User:Siosm| Timothée Ravier]], siosm@fedoraproject.org
* Name/Email: [[User:jlebon|Jonathan Lebon]], jonathan@jlebon.com
* Name/Email: [[User:Dustymabe|Dusty Mabe]], dusty@dustymabe.com
== Current status ==
[[Category:ChangeReadyForWrangler]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
[[Category:SelfContainedChange]]
* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f42/ Fedora Linux 42]
* 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
Bugzilla state meanings:
ASSIGNED -> accepted by FESCo with ongoing development
MODIFIED -> change is substantially done and testable
ON_QA -> change is fully code complete
-->
* [<link to devel-announce post will be added by Wrangler> Announced]
* [<will be assigned by the Wrangler> Discussion 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 ==
Currently, Fedora CoreOS hosts pull updates from the OSTree repository. With this change, the hosts will pull updates from the Quay.io container registry instead. At first, this should be a transparent change. We will notably keep using rpm-ostree for updates (and not yet bootc).
This is preliminary work to switching to bootc to manage the system and will enable us to deliver the following changes in the future:
* Moving from rpm-ostree to bootc, which only supports OCI.
* Better support for mirroring updates in disconnected setups.
* Moving away from maintaining a Cincinnati server towards having the graph live in an OCI registry alongside the update payload. This also allows users to maintain their own update graphs.
* Users will be able to create their own customized versions of Fedora CoreOS by building a derived container image.
== Feedback ==
None yet.
== Benefit to Fedora ==
Alignment with the work happening in the [https://https://docs.fedoraproject.org/en-US/bootc/getting-started/#_what_is_a_bootable_container Bootable Containers] initiative.
== Scope ==
* Proposal owners:
** Publish an upgrade graph containing the digest pullspec for each FCOS release. This mirrors the current update graph containing the same information, but pointing at OSTree commit checksums.
** Change new nodes on `next` to use OCI from the start.
** After a number of FCOS releases, ship a migration script to switch existing `next` nodes to use OCI.
** Repeat the last two steps for `testing`, and then `stable`.
** Down the line, stop publishing new OSTree commits to the OSTree repo. This will not happen until at least f43.
* Other developers: N/A (not needed for this Change)
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:
** Part of the work to align with Bootable Containers
== Upgrade/compatibility impact ==
We will issue a barrier release to migrate users to switch to OCI images.
== How To Test ==
Once the changes are ready, it will be possible to test it on the '''next''' stream before it gets rolled out there. This can be done by switching a '''next''' node from the OSTree remote to the OCI remote:
    rpm-ostree rebase ostree-remote-image:fedora:registry:quay.io/fedora/fedora-coreos:$NEXT_VERSION
where `$NEXT_VERSION` is a tag for a '''next''' release that's _not_ the latest. Then, watch Zincati fetch the latest '''next''' release using OCI.
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
Describe what Users will see or notice, for example:
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->
This change won't be visible to users running auto-updates, except cosmetic changes in `rpm-ostree status` output.
   
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
Revert the change to switch back to the OSTree repo. Both will be active until the Fedora 43 release.
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
We will update the Fedora CoreOS documentation alongside the transition. This is currently tracked in: https://github.com/coreos/fedora-coreos-tracker/issues/1823.
   
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
-->

Latest revision as of 16:31, 14 January 2025

Move Fedora CoreOS updates from OSTree to OCI

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

Change Fedora CoreOS to receive updates from quay.io/fedora/fedora-coreos instead of the Fedora OSTree repository.

Owner

Current status

  • Targeted release: Fedora Linux 42
  • Last updated: 2025-01-14
  • [<link to devel-announce post will be added by Wrangler> Announced]
  • [<will be assigned by the Wrangler> Discussion 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

Currently, Fedora CoreOS hosts pull updates from the OSTree repository. With this change, the hosts will pull updates from the Quay.io container registry instead. At first, this should be a transparent change. We will notably keep using rpm-ostree for updates (and not yet bootc).

This is preliminary work to switching to bootc to manage the system and will enable us to deliver the following changes in the future:

  • Moving from rpm-ostree to bootc, which only supports OCI.
  • Better support for mirroring updates in disconnected setups.
  • Moving away from maintaining a Cincinnati server towards having the graph live in an OCI registry alongside the update payload. This also allows users to maintain their own update graphs.
  • Users will be able to create their own customized versions of Fedora CoreOS by building a derived container image.

Feedback

None yet.

Benefit to Fedora

Alignment with the work happening in the Bootable Containers initiative.

Scope

  • Proposal owners:
    • Publish an upgrade graph containing the digest pullspec for each FCOS release. This mirrors the current update graph containing the same information, but pointing at OSTree commit checksums.
    • Change new nodes on next to use OCI from the start.
    • After a number of FCOS releases, ship a migration script to switch existing next nodes to use OCI.
    • Repeat the last two steps for testing, and then stable.
    • Down the line, stop publishing new OSTree commits to the OSTree repo. This will not happen until at least f43.
  • Other developers: N/A (not needed for this Change)
  • Release engineering: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy:
    • Part of the work to align with Bootable Containers

Upgrade/compatibility impact

We will issue a barrier release to migrate users to switch to OCI images.

How To Test

Once the changes are ready, it will be possible to test it on the next stream before it gets rolled out there. This can be done by switching a next node from the OSTree remote to the OCI remote: 

   rpm-ostree rebase ostree-remote-image:fedora:registry:quay.io/fedora/fedora-coreos:$NEXT_VERSION

where $NEXT_VERSION is a tag for a next release that's _not_ the latest. Then, watch Zincati fetch the latest next release using OCI.

User Experience

This change won't be visible to users running auto-updates, except cosmetic changes in rpm-ostree status output.

Contingency Plan

Revert the change to switch back to the OSTree repo. Both will be active until the Fedora 43 release.

Documentation

We will update the Fedora CoreOS documentation alongside the transition. This is currently tracked in: https://github.com/coreos/fedora-coreos-tracker/issues/1823.

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/CoreOSOstree2OCIUpdates&oldid=728669"