From Fedora Project Wiki
No edit summary
(Deferring to F38)
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Build Fedora IoT Artefacts with osbuild =
= Build Fedora IoT Artifacts with osbuild =


== Summary ==
== Summary ==
Build the key Fedora IoT artefacts such as the raw images and the traditional anaconda installer with osbuild.
Build the key Fedora IoT artifacts such as the raw images and the traditional anaconda installer with osbuild.


== Owner ==
== Owner ==
* Name: [[User:pwhalen| Paul Whalen]]
* Name: [[User:pwhalen| Paul Whalen]], [[User:gicmo| Christian Kellner]], [[User:obudai| Ondřej Budai]], [[User:pbrobinson| Peter Robinson]]
* Email: [mailto:pwhalen@redhat.com| pwhalen@redhat.com]
* Email: [mailto:pwhalen@fedoraproject.org pwhalen@fedoraproject.org], [mailto:ckellner@redhat.com ckellner@redhat.com], [mailto:obudai@redhat.com ondrej@budai.cz], [mailto:pbrobinson@fedoraproject.org pbrobinson@fedoraproject.org]
* Name: [[User:obudai| Ondřej Budai]]
* Email: [mailto:obudai@redhat.com| ondrej@budai.cz]
* Name: [[User:pbrobinson| Peter Robinson]]
* Email: [mailto:pbrobinson@fedoraproject.org| pbrobinson@fedoraproject.org]
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF38]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 25: Line 17:
[[Category:SelfContainedChange]]
[[Category:SelfContainedChange]]


* Targeted release: [[Releases/37 | Fedora 37 ]]  
* Targeted release: [[Releases/38 | Fedora Linux 38 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* 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  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 35: Line 27:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* devel thread
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/IIKJJL7LFDWRGZIYBEHFDSM4F6H4USQ6/devel thread]
* FESCo issue:  
* FESCo issue: [https://pagure.io/fesco/issue/2778 #2778]
* Tracker bug:  
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2075530 #2075530]
* Release Notes tracker:  
* Release Notes tracker: <will NOT be assigned by Wrangler>


== Detailed Description ==
== Detailed Description ==


The intention for Fedora IoT was to always use osbuild for building release artefacts but it wasn't initially ready to do that. With the work being done as part of "RHEL for Edge" the Fedora IoT deliverables now sadly trail behind the features and functionality of the downstream. This will move all existing deliverable artefacts over to being created with osbuild which will allow us to bring Fedora IoT back to being the true upstream for RHEL for Edge and allow us to use the leading edge that is Fedora to continue to innovate in the Edge and IoT space.
The intention for Fedora IoT was to always use osbuild for building release artifacts but it wasn't initially ready to do that. With the work being done as part of "RHEL for Edge" the Fedora IoT deliverables now sadly trail behind the features and functionality of the downstream. This will move all existing deliverable artifacts over to being created with osbuild which will allow us to bring Fedora IoT back to being the true upstream for RHEL for Edge and allow us to use the leading edge that is Fedora to continue to innovate in the Edge and IoT space.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 50: Line 42:
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:
** Test building IoT artefacts with osbuild to ensure they're consistent with the existing ones
** Test building IoT artifacts with osbuild to ensure they're consistent with the existing ones
** Update to Fedora IoT profiles in osbuild
** Update to Fedora IoT profiles in osbuild
** Update to pungi configs to move over the artefact creation
** Update to pungi configs to move over the artefact creation
Line 57: Line 49:
** No impact
** No impact


* Release engineering: [https://pagure.io/releng/issue/XXXX #XXXX]
* Release engineering: [https://pagure.io/releng/issue/10722 #10722]
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
Line 66: Line 58:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
There is no upgrade impact. Existing IoT users will upgrade as before as only new release artefacts will use the new mechanism. The deployment of the artefacts should not initially change with them being created with osbuild. There may well be new enhancements in the future but those are out of scope of this change.
There is no upgrade impact. Existing IoT users will upgrade as before as only new release artifacts will use the new mechanism. The deployment of the artifacts should not initially change with them being created with osbuild. There may well be new enhancements in the future but those are out of scope of this change.


== How To Test ==
== How To Test ==


* All Fedora IoT artefacts should be consumable and testable as  before.
* All Fedora IoT artifacts should be consumable and testable as  before.


== User Experience ==
== User Experience ==

Latest revision as of 17:15, 11 October 2022

Build Fedora IoT Artifacts with osbuild

Summary

Build the key Fedora IoT artifacts such as the raw images and the traditional anaconda installer with osbuild.

Owner

Current status

Detailed Description

The intention for Fedora IoT was to always use osbuild for building release artifacts but it wasn't initially ready to do that. With the work being done as part of "RHEL for Edge" the Fedora IoT deliverables now sadly trail behind the features and functionality of the downstream. This will move all existing deliverable artifacts over to being created with osbuild which will allow us to bring Fedora IoT back to being the true upstream for RHEL for Edge and allow us to use the leading edge that is Fedora to continue to innovate in the Edge and IoT space.

Benefit to Fedora

The benefit to Fedora is to allow the IoT Edition to go back to being the true upstream for RHEL for Edge and for Fedora to be where all the cool new innovation on the edge is being done.

Scope

  • Proposal owners:
    • Test building IoT artifacts with osbuild to ensure they're consistent with the existing ones
    • Update to Fedora IoT profiles in osbuild
    • Update to pungi configs to move over the artefact creation
  • Other developers:
    • No impact
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

There is no upgrade impact. Existing IoT users will upgrade as before as only new release artifacts will use the new mechanism. The deployment of the artifacts should not initially change with them being created with osbuild. There may well be new enhancements in the future but those are out of scope of this change.

How To Test

  • All Fedora IoT artifacts should be consumable and testable as before.

User Experience

There should be no IoT users, there is no impact to non IoT Edition users.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Roll back to the current means of generating images.
  • Contingency deadline: Beta
  • Blocks release? No.
  • Blocks product? No.

Documentation

N/A (not a System Wide Change)

Release Notes

N/A