Self Introduction: Prakash Mishra
by Prakash Mishra
Hello everyone,
I'm Prakash from Bangalore in India. I currently work as a Golang developer
working mainly with Kubernetes Operators and multi cluster Kubernetes
management. I've used Fedora as my daily driver for large parts in the
past.
I started my contribution journey with Vipul(Vipul SIddharth) back in 2016
by contributing to Fedora QA when we were attending university. My career
took me down a different path later as I got more involved with the
Kubernetes community here in India.
I recently got involved with Fedora Infrastructure and the KubeDev SIG
where David(Dkirwan) and Leo(Lrossett) have helped me immensely in getting
started. David and I spent a couple of hours today migrating
https://stg.whatcanidoforfedora.org to OCP4. The changes can be viewed
here:
https://pagure.io/fedora-infra/ansible/c/46b773c87a1dc6edd1c19425c6ef2fa1....
I look forward to working with you and I hope you have a great weekend
ahead.
Cheers,
Prakash Mishra.
2 years
CPE Weekly Update – Week of April 4th – 8th
by Michal Konecny
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-4th-8th/
# 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-06-04-2022.pdf
Update
------
### Fedora Infra
* Started F36 final freeze
* Completed mass update/reboot last week before freeze
* Hit fun koji bug that made it write our signed with mode 600 so it
didn’t sync. Found and fixed all files and patched koji.
* Had issue with s390x z/vm instances, but they are now back online
(many thanks dhorak!)
* Internal mail MX changed, blocking emails from fedoraproject.org ->
redhat.com. Updated to new one and slowly caught up.
* Completed ansible upgrade. Only thing left to fix is fedora-messaging
callback.
### CentOS Infra including CentOS CI
* Issues with Jenkins openshift sync plugins
* Duffy onboarding with Nils and Pedro
* Bussiness as usual, mirror tickets and koji tag requests ..
### Release Engineering
* F36 releng final freeze
* Retirement of FTI (Fails To Install) packages in F36
* Lots of stalled epel package requests
* F37 changes are landing in our tracker
## 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
-------
* Planning completed yesterday, focusing on:
* 8 + 9 workflow parity
* Build imports from c8s koji to c9s koji
* Deploying sync2gitlab service
* CVE checker service deployment
* Testing making github actions running in test suite
## 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
-------
* Tests and fixes for cicoclient
* Deployment preparation with Fabian, Pedro and Mark
* Work on the Ansible role for Duffy
* Meetings, meetings(, meetings!)
## Bodhi
Goal of this Initiative
-----------------------
This initiative is to separate Bodhi into multiple sub packages, fix
integration and unit tests in CI, fix dependency management and automate
part of the release process.
Read ARC team findings in detail at:
https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html
Updates
-------
* Bodhi 6.0 will be deployed to production a couple of weeks after the
Fedora release
* E-mail about what’s new in Bodhi 6.0 sent to devel-announce
* Wrapping up dependency management
## 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 up to 2247 source packages (increase of 33 from last week)
* Rebuilt hwinfo epel8 package to be compatible with unannounced
libx86emu soname bump
* qt6 on its way to epel9 testing, which will allow more applications
* Other notable new epel9 packages:
* uwsgi
* akmods
* Notable mailing list discussions:
* [Slowing down the stalled request
process](https://lists.fedoraproject.org/archives/list/epel-devel@lists.f...
* [Dependency policy for packages in less common RHEL channels
(HighAvailability, ResilientStorage,
etc.)](https://lists.fedoraproject.org/archives/list/epel-devel@lists.fed...)
* [EPEL8 packages needing care and
feeding](https://lists.fedoraproject.org/archives/list/epel-devel@lists.f...
Kindest regards,
CPE Team
2 years, 1 month
Bodhi 6.0: What's new
by Aurelien Bompard
Hey everyone!
Bodhi 6.0 will be published in a few days, and deployed to production a
couple weeks after the Fedora release. It has backwards-incompatible
changes, here's what you need to know.
== Authentication ==
Bodhi gained support for OpenID Connect (OIDC) authentication, like most of
Fedora's webapps. OpenID still works but is not the default, you can access
it by using `/login?method=openid` as the login URL.
Version 6.0 of the Bodhi client uses only OIDC, plain OpenID support has
been dropped. Version 5.7.5 of the Bodhi client, however, uses the new
OpenID login URL and has been available for about a month now, you'll need
at least version 5.7.5 to use the Bodhi client with the updated server.
The client's API has changed, so if you have a piece of code that imports
from `bodhi.client`, you'll have to update it to use the new API, and in
the meantime use version 5.7.5.
As a user of the `bodhi` CLI, you'll notice that the `--username` and
`--password` options have disappeared. Instead the Bodhi client will ask
you to open your browser to a URL to authenticate. The authentication
tokens will be saved and you'll be able to use the `bodhi` CLI without
authenticating afterwards (or non-interactively).
== Code reorganization ==
The Bodhi source code has been reorganized to drop the hacks used in
`setup.py` to support sub-projects. Instead, `bodhi-server`, `bodhi-client`
and `bodhi-messages` are now actual Python package directories in the repo.
The import path has not changed.
Bodhi's Python project metadata and dependencies are now managed with
Poetry <https://python-poetry.org/>.
== Other changes ==
- Serialized `Release` objects sent in the messages don't contain the
`composes` property anymore
- The `koji-build-group.build.complete` messages now contain an `update`
property
- In the Bodhi client API, the `save_override()` method has been extended
to allow setting the expiration date directly
- Misc bug fixes
If you have any questions, feel free to ask the Bodhi team in our matrix
room: <https://matrix.to/#/#bodhi:matrix.org>.
If you are importing the bodhi client code in your app/script, or using the
bodhi client in an "unusual" manner, we'll help you migrate.
Thanks!
Aurélien Bompard
2 years, 1 month
Fedora 36 Final freeze now in effect!
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 36
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 36 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2022-04-19 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list.
Thanks,
kevin
2 years, 1 month
CPE Weekly Update – Week of March 28th – April 1st
by Lenka Segura
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-march-2...
# 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-30-03-2022.pdf
Update
------
### Fedora Infra
* Got ELN resigned with f37/rawhide key and SOPs updated to do that at
branching
* Work on Infra SOPs ongoing
* Adjusted vhost_reboot playbook to handle OCP4 master node vm’s correctly.
* OCP4 clusters all upgraded to latest version.
### CentOS Infra including CentOS CI
* koji/cbs builders reconfigured to use Proxy (
https://pagure.io/centos-infra/issue/645) to reach gitlab.com
* Extras repository for CentOS Stream 8 now live (
https://lists.centos.org/pipermail/centos-devel/2022-March/120292.html)
* Finishing ansible 2.9 => 2.12 (https://pagure.io/centos-infra/issue/496)
conversion (role and collections)
* Collab with Niels for Duffy ansible role (Pedro and Fabian)
* Business as usual
### Release Engineering
* Fedora 36 Beta released
* Fedora 36 FTI packages retired
* Work on SCM request automation is near finish - PR (
https://pagure.io/fedora-infra/toddlers/pull-request/93)
## 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
-------
* First set of changes for CVE checker posted to gitlab.
* ELN composes failing, troubleshooting the cause and updating our teams
support docs (watcher duty)
* Stream 9 presentations being worked on for Summit
* Team planning for the goals and deliverables for the coming months (q2)
scheduled for Tue
## 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 3.0.0a3 with even fewer missing dependencies!
* Handover conversations
* Testing & Documentation
* Deployment playbooks and testing thereof
* Script to migrate existing tenants
## Image builder for Fedora IoT
Goal of this Initiative
-----------------------
Integration of Image builder as a service with Fedora infra to allow Fedora
IoT migrate their pipeline to Fedora infra.
Updates
-------
* Full stack deployed in staging across kojihub and all builders
* Testing complete
* Ansible changes made and ready for whenever it needs to be deployed to
prod
* Both image builder and fedora IoT teams have tested and seem happy
* Working on some form of documentation + handover to infra this week
## Bodhi
Goal of this Initiative
-----------------------
This initiative is to separate Bodhi into multiple sub packages, fix
integration and unit tests in CI, fix dependency management and automate
part of the release process.
Read ARC team findings in detail at:
https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html
Updates
-------
* Fedpkg compatibility for Bodhi >= 6.0
* Updated links to the documentation to GitHub pages
* Dependency management (finishing touches)
* Exclude `composes` property when serializing the Release object
* Next major release draws near (~ 2 weeks?)
## 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 up to 2214 source packages (increase of 27 from last week)
* EPEL8 Playground has been retired (actually happened back in January)
* Evaluation of EPEL9 Modular
* Investigation of CVE’s in EPEL packages
Kindest regards,
CPE Team
2 years, 1 month