From Fedora Project Wiki
< Changes
(→Owner) |
|||
Line 8: | Line 8: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". --> | ||
The Fedora IoT Simplified Installer uses coreos-installer-dracut to write an OStree commit straight to disk, without the need for a kickstart or user interaction. This type of installation is ideal for devices connected at the edge where connectivity can be slow or intermittent. | |||
== Owner == | == Owner == |
Revision as of 16:46, 11 January 2023
IoT Simplified Installer
Summary
The Fedora IoT Simplified Installer uses coreos-installer-dracut to write an OStree commit straight to disk, without the need for a kickstart or user interaction. This type of installation is ideal for devices connected at the edge where connectivity can be slow or intermittent.
Owner
- Name: Paul Whalen
- Email: pwhalen@fedoraproject.org
- Name: Antonio Murdaca
- Email: amurdaca@redhat.com
Current status
- Targeted release: Fedora Linux 38
- Last updated: 2023-01-11
- 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
Feedback
Benefit to Fedora
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)