CPE Weekly Update - Week 34 2022

Originally published at: CPE Weekly Update - Week 34 2022 – Fedora Community Blog

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 (https://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: 22th August – 26th August 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

  • F37 beta freeze in effect
  • Mass update/reboot cycle finished up
  • Fixed issue with old imported wiki pages (fche gets all the credit!)
  • Note that fedora-infrastructure tracker is down to 47 open tickets!

CentOS Infra including CentOS CI

Release Engineering

  • Switched rawhide to use systemd-nspawn for builds/composes (only one issue so far with ostree installer images)
  • F37 compose started failing today

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

  • Recovering from F2F
  • Fix problems with CVE checker, again.
  • Solved permission problems stopping c8s module builds in new infra, but still not finished a module build.

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

  • EPEL9 is up to 7427 (+88) packages from 3322 (+44) source packages
  • “State of EPEL” presentation at CentOS Dojo (slides, video)
  • “The Road to EPEL 9” presentation at DevConf.US (slides, video)
  • Rebuilt bloaty in EPEL 9 for unannounced soname bump in re2

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

  • Planning meeting: stages of the project
  • First community email being drafted
  • Integrated various frontend components
  • First shot at a rules page
  • Ongoing/started: SQLAlchemy integration, authentication frontend/backend, fedora messaging consumer