Pbrobinson (talk | contribs) No edit summary |
Pbrobinson (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= Build Fedora IoT Artefacts with | = Build Fedora IoT Artefacts with osbuild = | ||
== Summary == | == Summary == | ||
Build the key Fedora IoT artefacts such as the raw images and the traditional anaconda installer with | Build the key Fedora IoT artefacts such as the raw images and the traditional anaconda installer with osbuild. | ||
== Owner == | == Owner == | ||
| Line 42: | Line 42: | ||
== Detailed Description == | == Detailed Description == | ||
The intention for Fedora IoT was to always use | 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. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 50: | Line 50: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** Test building IoT artefacts with | ** Test building IoT artefacts with osbuild to ensure they're consistent with the existing ones | ||
** Update to Fedora IoT profiles in | ** 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 66: | Line 66: | ||
== 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 | 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. | ||
== How To Test == | == How To Test == | ||
Revision as of 11:55, 29 March 2022
Build Fedora IoT Artefacts with osbuild
Summary
Build the key Fedora IoT artefacts such as the raw images and the traditional anaconda installer with osbuild.
Owner
- Name: Paul Whalen
- Email: pwhalen@redhat.com
- Name: Ondřej Budai
- Email: ondrej@budai.cz
- Name: Peter Robinson
- Email: pbrobinson@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 37
- Last updated: 2022-03-29
- devel thread
- FESCo issue:
- Tracker bug:
- Release Notes tracker:
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.
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 artefacts 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
- Release engineering: #XXXX
- List of deliverables: N/A (not a System Wide Change)
- 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 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.
How To Test
- All Fedora IoT artefacts 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