os/Fedora: add Fedora 44 support for the base role #497
Reference in New Issue
Block a user
Delete Branch "benvin/fedora-44-base"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
We want to manage Fedora 44 hosts with this Puppet codebase, starting with the
baserole only. Fedora reuses the RedHat osfamily code paths (dnf/yum, crypto-policies, firewalld, openvox), so this adds the Fedora-specific hieradata, repositories, and gates needed forbaseto compile and apply, mirroring how AlmaLinux is wired and consuming the artifactapirpm-internal-f<major>/rpm-vendor-f<major>local repos. Everything is keyed offfacts.os.release.majorso a future Fedora release only needs its artifactapi local repos created, not new hieradata.How
hieradata/os/Fedora/all_releases.yaml:profiles::yum::global::repos:fedoraandupdatesproxied through artifactapi'sfedoraremote, plus the artifactapi localsrpm-internal-f%{major}andrpm-vendor-f%{major}; GPG via the on-diskfedora-gpg-keys; metalink/mirrorlist cleared so only the artifactapi baseurl is used.crypto_policies::policy: DEFAULT,profiles::puppet::agent::openvox_enable: true, andlm-sensors::package: lm_sensors.p7zip/dstat/iotop(absent on Fedora) and include7zipandiotop-c, plus the samecrypto-policies-scripts/lzo/policycoreutils/unar/xzadditions AlmaLinux carries.profiles::fedora::baseviahiera_include.profiles::fedora::base(ensures NetworkManager enabled) as the Fedora analogue ofprofiles::almalinux::base; deliberately minimal so it can grow into workstation/laptop use later.profiles::puppet::agentselect the OpenVox distribution path (fedora/<major>on Fedora,el/<major>elsewhere); AlmaLinux/Debian behaviour is unchanged.Validation
puppet-lint, puppet manifest validate, andyamllintall pass via the repo's pre-commit hooks on the changed files.Note for reviewer
OpenVox does not yet publish a Fedora 44 build (
openvox7/fedora/currently has only 36/40/41), soopenvox-agentwill 404 until upstream publishes f44 or a build is placed inrpm-internal-f44. The Puppet code produces the correct path for when that exists; installing the agent is a prerequisite for a Fedora 44 host to actually run.https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv