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/).
Week: 8th - 12th August 2022
If you wish to read this in form of a blog post, check the post on Fedora community blog:
https://communityblog.fedoraproject.org/?p=11316
# 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.
Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-08-10.pdf
Link to docs: https://docs.fedoraproject.org/en-US/infra/
Update
------
### Fedora Infra
* Some great nest talks and discussions, check them out on replay!
* Debugging instability in 32bit arm builders again. ;(
* Rebalanced the s390x builders.
* Business as usual
### CentOS Infra including CentOS CI
* koji/cbs.centos.org upgrade complete
* Kick off for Stream infra handover to I&R
* Adapted ansible baseline role to include workaround for Rsync issue on CentOS Stream 8
* Enabled RHEL9 Buildroots on cbs/koji for SIGs
### Release Engineering
* Mass branching yesterday (f37 split off rawhide, which is now f38)
## 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
-------
* Git source moved from git.centos.org to gitlab, for c8s modules.
## 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 7233 (+106) packages from 3207 (+27) source packages
* “State of EPEL” presentation at Nest conference, recording will be posted to YouTube at a later date
* EPEL Survey has launched and is available through the end of August https://tinyurl.com/epelsurvey2022
* epel-release has been improved with a recommends on dnf-command(config-manager) to ensure crb enabling script can work out of the box
* KDE Plasma updated from 5.23 to 5.24 (LTS release) in epel8-next and epel9-next
## 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
-------
* Unit tests/coverage tests on frontend (Vue.js)
* Auth/OIDC work on both frontend and backend
* Initial backend connection via SQLAlchemy/fastAPI
* Basic functionality of connecting to FASJSON
* CI improvements and fixes
Kindest regards,
CPE Team
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/).
Week: 8th - 12th August 2022
If you wish to read this in form of a blog post, check the post on Fedora community blog:
https://communityblog.fedoraproject.org/?p=11316
# 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.
Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-08-10.pdf
Link to docs: https://docs.fedoraproject.org/en-US/infra/
Update
------
### Fedora Infra
* Some great nest talks and discussions, check them out on replay!
* Debugging instability in 32bit arm builders again. ;(
* Rebalanced the s390x builders.
* Business as usual
### CentOS Infra including CentOS CI
* koji/cbs.centos.org upgrade complete
* Kick off for Stream infra handover to I&R
* Adapted ansible baseline role to include workaround for Rsync issue on CentOS Stream 8
* Enabled RHEL9 Buildroots on cbs/koji for SIGs
### Release Engineering
* Mass branching yesterday (f37 split off rawhide, which is now f38)
## 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
-------
* Git source moved from git.centos.org to gitlab, for c8s modules.
## 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 7233 (+106) packages from 3207 (+27) source packages
* “State of EPEL” presentation at Nest conference, recording will be posted to YouTube at a later date
* EPEL Survey has launched and is available through the end of August https://tinyurl.com/epelsurvey2022
* epel-release has been improved with a recommends on dnf-command(config-manager) to ensure crb enabling script can work out of the box
* KDE Plasma updated from 5.23 to 5.24 (LTS release) in epel8-next and epel9-next
## 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
-------
* Unit tests/coverage tests on frontend (Vue.js)
* Auth/OIDC work on both frontend and backend
* Initial backend connection via SQLAlchemy/fastAPI
* Basic functionality of connecting to FASJSON
* CI improvements and fixes
Kindest regards,
CPE Team
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
