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: 14th to 18th November 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
- Reinstalled storinator in rdu-cc with rhel9. Setup so copr folks could backup there.
- Setup new risc-v koji hub instance in aws, handed off to maintainer
- Fedora 37 out the door!
- Fixed some iot composes clogging up bodhi message queue
- Worked on getting container builds working again, some progress, but still no luck.
- Updated all our 32bit arm builders to try and fix a OOM issue with python builds.
CentOS Infra including CentOS CI
- Full redeployed with ansible https://console-openshift-console.apps.ocp.cloud.stg.ci.centos.org/ STG clusters (now with FAS groups/users sync) and using EFS as storage for PVs
- Deployed https://connect.centos.org for Event
- Quickly rebuilt and pushed CentOS 7 linux AMI on AWS due to AWS deprecating older images (so refresh was also needed and good idea)
- Preparing CentOS Stream koji upgrade
Release Engineering
- Fedora 37 is out
- New SOP docs in progress
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
- Moving the Stream 8 builds over to the new infrastructure
- Looking into the compose directory structure at composes.stream.centos.org to have 8 and 9 together
- More of the team is starting to get involved with Content Resolver
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 11,352 (+976) packages from 4,355 (+204) source packages
- Closed bug report on bdii package since package is installable
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
- A number of small to medium sized commits this week
- Filters and rules integration with the code base, resulting code adjustments
- Notification preview feature initial implementation
- Async proxy for FASJSON implementation
- Testing and resulting code adjustments
Start the discussion by commenting on the auto-created topic at discussion.fedoraproject.org