This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 01 April – 05 April 2024
Infrastructure & Release Engineering
The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
Fedora Infra
- In progress:
- rhel7 EOL
- Migration of registry.fedoraproject.org to quay.io
- add monitoring for dnf countme
- Replace Nagios with Zabbix in Fedora Infrastructure
- notifications do not notify
- DNF countme minor changes post migration
- vmhost-x86-copr02 hardware issues
- PDC retirement
- Move from iptables to firewalld
- fedoraplanet.org: Upgrade Venus to Pluto
- Move mailman to newer release of Fedora or CentOS
- Setup RISC-V builder(s) VM in Fedora Infrastructure
- Update compose hosts to get latest pungi release (4.6.0)
- Deploy new sign hardware/software
- logrotate not working on proxy31
- Revise the webhook2fedoramessaging investigation
- Commits don’t end up on the scm-commits list
- AWS S3 bucket permissions for openQA cloud enablement
- Fixing tests for MDAPI
- Done:
CentOS Infra including CentOS CI
- In progress:
- Done:
Release Engineering
- In progress:
- Packages that fail to build SRPM are not reported during the mass rebuild bugzillas
- Silverblue aarch64 installer image compose always fails on F38 and Rawhide
- Sync RCs to alt/stg dl.fp.o
- i686 builders need to use 32-bit inode numbers
- Fixes for release-candidate.sh in pungi-fedora
- When orphaning packages, keep the original owner as co-maintainer
- adjust torrent_hashes.py to non bittorrent world
- Emit fedmsg when candidate composes are synced to stage
- Publish “latest” tag to quay.io/fedora/fedora
- Use an automated script to control checksums of compose images
- Create an ansible playbook to do the mass-branching
- Package retirements are broken in rawhide
- Done:
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).
Updates
- In progress:
- Initial CentOS 10 batcave sync script for EPEL 10 buildroot
- Presentation for Texas Linux Fest giving overview of Fedora, CentOS, RHEL, and EPEL
- Done:
- Presented onboarding talk to Waterford office new hires, including sections on Fedora, EPEL, and RPM packaging
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
Start the discussion by commenting on the auto-created topic at discussion.fedoraproject.org