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-november-22nd-26th/
# 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
------
* Discourse2fedmsg mini initiative nearing completion
### Fedora Infra
* Some issues post mainframe migration on s390x builders. Investigation ongoing
* Issues with some users password expiring, abompard fixed with a script
* Business as usual
### CentOS Infra including CentOS CI
* Announced switch to 8-stream based container for cico-workspace (ci infra)
(https://lists.centos.org/pipermail/ci-users/2021-November/002187.html)
* Work completed to allow SIG to switch buildroot from centos 8 to RHEL8 (https://pagure.io/centos-infra/issue/400)
* New SIGs tags:
* Automotive experimental (Stream 9)
* Storage TDX-devel (Stream 8)
* Fixed issue with debuginfod pkgs filtered out (https://pagure.io/centos-infra/issue/532) after process change for Stream 9/SIGs
* Tuned mirror.stream.centos.org pool due to hard-disk space constraint on sponsored/donated nodes (https://pagure.io/centos-infra/issue/529)
### Release Engineering
* F33 distgit branches had the wrong EOL set to 16-11-2021 but the real f33 EOL is 30-11-2021
* FCOS prunned OStree compose repo, saved about 2TB of disk space
* 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
-------
* Investigating AWS cleanups
* Finishing Content Resolver buildroot changes
* Wrote ELN docs about package differences (in FAQ) (https://docs.fedoraproject.org/en-US/eln/faq/) and adding packages to ELN Extras (https://docs.fedoraproject.org/en-US/eln/extras/)
* Many PTOs this week
## Datanommer/Datagrepper V.2
Goal of this Initiative
-----------------------
The datanommer and datagrepper stacks are currently relying on fedmsg which
we want to deprecate.
These two applications need to be ported off fedmsg to fedora-messaging.
As these applications are 'old-timers' in the fedora infrastructure, we would
also like to look at optimizing the database or potentially redesigning it to
better suit the current infrastructure needs.
For a phase two, we would like to focus on a DB overhaul.
Updates
-------
* The DB had been rebooted a few times and the script restarted. 40 days to go.
## 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
-------
* Duffy has sub-commands
* Serving the web app
* Initial setup of DB schema
* Interactive shell for debugging and development
* Initialize DB connection and related code when starting the app
* Ongoing: API endpoints
* Wednesday’s review + planning call: Conversation with Fedora QA about how Duffy can serve them
* CI: Let dependabot check for transient updates (and apply them)
## FCOS OpenShift migration
Goal of this Initiative
-----------------------
Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the newly
deployed fedora infra OCP4 cluster.
Updates
-------
* Work complete, handed over to the Fedora CoreOS team.
## 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 Next is ready, but not announced yet
* EPEL Steering Committee is evaluating some alternative plans that may let us launch EPEL 9 and EPEL 9 Next together
* Hoping to announce on the same day as the CentOS Stream 9 launch promotion (1-2 weeks)
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/).
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-november-22nd-26th/
# 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
------
* Discourse2fedmsg mini initiative nearing completion
### Fedora Infra
* Some issues post mainframe migration on s390x builders. Investigation ongoing
* Issues with some users password expiring, abompard fixed with a script
* Business as usual
### CentOS Infra including CentOS CI
* Announced switch to 8-stream based container for cico-workspace (ci infra)
(https://lists.centos.org/pipermail/ci-users/2021-November/002187.html)
* Work completed to allow SIG to switch buildroot from centos 8 to RHEL8 (https://pagure.io/centos-infra/issue/400)
* New SIGs tags:
* Automotive experimental (Stream 9)
* Storage TDX-devel (Stream 8)
* Fixed issue with debuginfod pkgs filtered out (https://pagure.io/centos-infra/issue/532) after process change for Stream 9/SIGs
* Tuned mirror.stream.centos.org pool due to hard-disk space constraint on sponsored/donated nodes (https://pagure.io/centos-infra/issue/529)
### Release Engineering
* F33 distgit branches had the wrong EOL set to 16-11-2021 but the real f33 EOL is 30-11-2021
* FCOS prunned OStree compose repo, saved about 2TB of disk space
* 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
-------
* Investigating AWS cleanups
* Finishing Content Resolver buildroot changes
* Wrote ELN docs about package differences (in FAQ) (https://docs.fedoraproject.org/en-US/eln/faq/) and adding packages to ELN Extras (https://docs.fedoraproject.org/en-US/eln/extras/)
* Many PTOs this week
## Datanommer/Datagrepper V.2
Goal of this Initiative
-----------------------
The datanommer and datagrepper stacks are currently relying on fedmsg which
we want to deprecate.
These two applications need to be ported off fedmsg to fedora-messaging.
As these applications are 'old-timers' in the fedora infrastructure, we would
also like to look at optimizing the database or potentially redesigning it to
better suit the current infrastructure needs.
For a phase two, we would like to focus on a DB overhaul.
Updates
-------
* The DB had been rebooted a few times and the script restarted. 40 days to go.
## 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
-------
* Duffy has sub-commands
* Serving the web app
* Initial setup of DB schema
* Interactive shell for debugging and development
* Initialize DB connection and related code when starting the app
* Ongoing: API endpoints
* Wednesday’s review + planning call: Conversation with Fedora QA about how Duffy can serve them
* CI: Let dependabot check for transient updates (and apply them)
## FCOS OpenShift migration
Goal of this Initiative
-----------------------
Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the newly
deployed fedora infra OCP4 cluster.
Updates
-------
* Work complete, handed over to the Fedora CoreOS team.
## 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 Next is ready, but not announced yet
* EPEL Steering Committee is evaluating some alternative plans that may let us launch EPEL 9 and EPEL 9 Next together
* Hoping to announce on the same day as the CentOS Stream 9 launch promotion (1-2 weeks)
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 on the list, report it: https://pagure.io/fedora-infrastructure
