This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat.
We provide you both infographics 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: 19th September – 23rd September 2022
Highlights of the week
Infrastructure & Release Engineering
Goal of this Initiative
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.).
The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on.
Planning board
Docs
Update
Fedora Infra
- Proxies moving to f36 (ran into fun amazon nvme firmware bug)
- Reissued all fedora-messaging and vpn certs that expired this year.
- Closed 2 really old infra tickets (6year and 5year) and got them done.
CentOS Infra including CentOS CI
- Reverting to ansible-core 2.12 for CentOS infra
- Kiwi plugin now live on cbs.centos.org
- CentOS Stream 9 basic support for infra baseline+monitoring role
Release Engineering
- We are at 77 opened tickets
- Investigation on quay updates
- Testing of SCM toddler in staging
CentOS Stream
Goal of this Initiative
This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream.
Updates
- Manually push c8s modules, working around CVE checker problems.
- Building several modules for Stream 8 that were stuck in CVE checker: 389-ds, 2 container tools modules, and virt. Also two standard module releases: python38 and python39
- Focusing on centpkg-sig and its support of the exploded SRPM format.
- Discussed details around repo split (BaseOS, AppStream, CRB, etc.) in Content Resolver and working on a standalone script for now.
EPEL
Goal of this initiative
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 and Scientific Linux (SL), Oracle Linux (OL).
EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more.
Updates
- EPEL 9 is up to 8736 (+97) packages from 3684 (+44) source packages
- Major overhaul of python-peewee in rawhide to prepare for building for epel9
- Based on survey responses, there is demand for training on EPEL packaging
- Reported fail to install bug for rust-resctl-bench
- “Will It Install” tracker updated with dates when a package was added to epel, as well as when it started failing to install.
FMN replacement
Goal of this initiative
FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC.
The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper.
Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether.
Updates
- Added logic to create a user in the DB once logged into the frontend
- Reworked the backend’s authentication with Ipsilon
- Added new unit tests for the consumer
- Investigated ORM models and their relationship to each other for the DB structure
Start the discussion by commenting on the auto-created topic at discussion.fedoraproject.org