Changes/Deprecate Zezere

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

Deprecate Zezere Provisioning Server (IoT)

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

Deprecate use of the Zezere provisioning server, currently used to configure Fedora IoT devices.

Owner

• Name: Paul Whalen
• Email: pwhalen@fedoraproject.org
• Name: Fedora IoT SIG

Current status

• Targeted release: Fedora Linux 42
• Last updated: 2024-12-09
• [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 IoT users can add an SSH key to the root user account using the Zezere provisioning tool. While convenient for most use cases, users have given feedback that this does not work for all. In Fedora 42 we plan to deprecate the Zezere provisioning server in favour of offering a local means for user configuaration - systemd-firstboot - as well as the existing options of FDO or ignition.

Benefit to Fedora

The Zezere provisioning tool has not worked well for all Fedora IoT users. Deprecation will allow us to replace this configuration method with something that is more robust, well tested and already installed by default with systemd.

Scope

• Proposal owners:
  • Remove Zezere from the installed packages, enable systemd-first boot and ensure its compatible with IoT systems
  • Document the change

• Other developers: N/A

• 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 the Fedora Strategy:

Upgrade/compatibility impact

None.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

How To Test

To test, users will need to provision a new Fedora IoT system after the change is made to enable systemd-firstboot.

User Experience

Users who have been unable to use Zezere will have an easier and more straight forward way to configure their system resulting in less frustration during the critical first boot experience.

Contingency Plan

• Contingency mechanism: Continue to include Zezere as we do today.

Documentation

• Fedora IoT Getting started guide will be updated to reflect the change and new configuration option.