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 with both infographic and text versions of the weekly report. If you just want to look at what we did quickly, look at the infographic. If you are interested in more in-depth details look at the text version.
Week: November 07th – 11th 2022
Highlights of the week
Infrastructure & Release Engineering
Goal of this Initiative
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.).
The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on.
- FMN queue finally caught up, and we made the processing of messages 5x faster
- Grew some netapp volumes to accommodate more usage
- Business as usual (tickets, fixing down machines, etc)
CentOS Infra including CentOS CI
- Still WIP for Kiwi plugin for koji/cbs.centos.org
- Openshift STG deployment in AWS to replace CI OCP (on-premises) (WIP) but already deployed and available https://console-openshift-console.apps.ocp.cloud.stg.ci.centos.org/ (using FAS STG account for OAuth)
- Duffy CI temporary issue (upgraded to RHEL 8.7) was quickly resolved
- AWS/EC2 EBS volumes tuning for old centos stream 8 composes origin nodes
- Lost (again) two other sponsors for nodes in centos infrastructure
- RC1.6 and RC1.7 composes made. So far 1.7 is looking pretty good.
- RCs synced to internal mirrors
- Fedora Media Writer 5.0.4 is out
- Business as usual
Emerging RHEL + 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 latest CentOS Stream.
- Contributions to the CentOS Stream compose tests (t_functional) are now being automatically tested in PRs. This should streamline contributions. It’s also a building block for running these tests on composes automatically.
- Sync of c8s builds into the new system continues.
- Preparing a testing c8s compose in the new system.
- Kernel testing in ELN revealed a crash while running debug kernels on aarch64 and ppc64le.
- The bug is complex and difficult to track down.
- Catching it in ELN gives us much more time than if we had only found it once CentOS Stream 10 had started.
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.
- EPEL 9 is up to 10,376 (+869) packages from 4,151 (+231) source packages
- RHEL 8.7 in now in epel8 buildroot
- KDE Plasma Desktop update build has started for epel8.
- Refined EPEL package request guide (pull request)
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 to email or IRC.
The initiative’s goal 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. The community will profit from speedier notifications based on their 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.
- The monthly planning call (for Nov) was done yesterday. On track to deliver:
- Deployment to a staging environment of work to date
- Testing end-to-end for ‘Email’ notifications – a rule can be created & installed, a message is consumed, the rule is consulted and a notification is then sent via email
- Working on a new feature – ‘message preview’ where a user can create a rule and it will generate a preview of how many notifications they will receive based on that rule before installing it. More to come on this as the month progresses.