Permanently ongoing work to complete, improve, and update Fedora Server documentation.
General maintenance of Fedora Server Edition, bugs, bug fixes, request for improvement, release testing.
According to our Technical Specifications core services, named roles, are to be supported by Ansible for installation, configuration and administration.
System updates are the weakest point in the life cycle of a Fedora server. There is a possibility that afterward the system will no longer be operational or will only be usable with errors. The aim is to establish a system that creates a backup of the system partitions within a very short time before an update and provides a reliable procedure for restoring the state before the update in case of problems. Particular consideration must be given to lodging in a remote data center without direct access to a terminal or USB ports.
See the WIKI page for more information
Timeline: Should be implemented with release F45.
Fedora Server in standalone mode currently uses only a simple name/password authentication by default. More elaborate procedures must be installed and configured by the system administrator. It is a complex process and usually not even feasible for standalone servers. The recently available Local Authentication Hub (LocalKDC) provides local Kerberos keys, exclusively locally via Unix domain sockets and executed on demand by socket activation. It significantly expands the functionality for file services such as Samba and can also become bases for the login function of NFS v4.
There are 2 Parts:
-
Optimize Server updating process by providing a (temporary) fall-back system copy
- Optionally backup the temporary fall-back to an external device
- Maybe using an UrBackup client device
-
Optimize Backing up the complete Server
- Maybe by packaging and configuring UrBackup (https://www.urbackup.org/) or a comparable solution
Special attention to pay to standalone servers without integration into a centralized backup management. And it becomes even more complicated if they are located in a remote data center without even access to a console or USB port.
The 2024/2025 Fedora Server User Survey showed that the majority of attendees use Fedora Server in a domestic environment, either exclusively or in addition to a professional usage. We want to take this into account and honor this with a special spin-off for this purpose.
The objective is not to release a YABD (Yet Another Boring Device), but something dedicated and special.
- low power consumption / environment friendlyness
- affordability
- optionally reuse older equipment
- Provide a ready to use installation with a typical set of software pre-installed and pre-configured
- Completely usage of Fedora distributables under Fedora QA und Fedora security regime
See more general details at the wiki page.
We need an ansible playbook (and the matching roles) to allow people to quickly setup PXE boot for Fedora Server installs.