Hi everyone,

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/).

If you wish to read this in form of a blog post, check the post on
Fedora community blog:
https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-december-6th-10th/

# 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.

Update
------

### Fedora Infra
* Discourse2fedmsg completed and deployed in prod
* groups support for oauth2 for discourse put on hold due to a potential upstream solution
* Switched to qemu/libvirt from the “Advanced Virt” stack
* All staging builders moved to f35, but our fedora messaging plugin is broken in f35 hub.
* New bodhi deployment this week


### CentOS Infra including CentOS CI
* CentOS Stream 9 [artwork deployed](https://pagure.io/centos-infra/issue/477) (Kudos to Artwork SIG !) :
  * https://www.centos.org
  * https://blog.centos.org
  * https://lists.centos.org
* Meeting[s] to prepare the Community Cage DC move
* Identified (and [fixed](https://pagure.io/centos-infra/issue/551)) small issue for PowerDNS geoip setup for 9-stream * Bussiness as Usual (koji/cbs tags, new mirrors for 7 / 8-stream and 9-stream)



### Release Engineering
* epel9 branches are popping up ~520 in the last week
* F36 change request reviews are landing in releng tracker
* business as usual


## 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
-------
* Stream 9 composes were broken over the weekend, the backlog is now clear and a compose was pushed yesterday * Gitlab authentication suffered some effects of the auth.redhat.com migration, we expect this is now resolved
* Implementing Content Resolver performance optimisations


## CentOS Duffy CI
Goal of this Initiative
-----------------------
Duffy is a system within CentOS CI Infra which allows tenants to provision and
access bare metal resources of multiple architectures for the purposes of
CI testing.
We need to add the ability to checkout VMs in CentOS CI in Duffy. We have
OpenNebula hypervisor available, and have started developing playbooks which
can be used to create VMs using the OpenNebula API, but due to the current state
of how Duffy is deployed, we are blocked with new dev work to add the
VM checkout functionality.

Updates
-------
* API endpoints with database connection (finally)
* Extended documentation for API endpoints (in progress)
* Command-line option to avoid overriding existing database when performing migration
* Backend work (started): Background tasks like provisioning nodes, clean up
* Endpoint authentication with API key / token pertaining to a certain project / tenant (in progress)



## OSCI – Distrobaker monitoring
Goal of this Initiative
-----------------------
This initiative is to improve the Distrobaker monitoring to monitor
side-tags and module builds. Distrobaker is a service which rebuilds
the CentOS 9 Stream Koji builds for RHEL 9 in Brew.

Updates
-------
* Currently working on adding metrics for the sidetag comparison code.

## 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 (and EPEL9 Next) launched!](https://communityblog.fedoraproject.org/epel-9-is-now-available/)
* Already have 501 packages in testing (255 builds, 158 bodhi updates)
* [Quickstart documentation](https://docs.fedoraproject.org/en-US/epel/#_quickstart) updated * EPEL Steering Committee [decided to standardize](https://pagure.io/epel/issue/133) on {distro}+epel-{version} pattern for mock configs rather than a generic epel-{version} config
* centos-stream+epel-9 configs added to mock-core-configs


Kindest regards,
CPE Team
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to