Infrastructure Archives – Page 2 of 29

Category: Infrastructure (page 2 of 29)

All articles in this category are related to the Infrastructure team in the Fedora Project. https://fedoraproject.org/wiki/Infrastructure

Introducing User Interface for Webhook To Fedora Messaging

As a part of our move from Fedmsg to Fedora Messaging in the last year, we announced the general availability of the Webhook To Fedora Messaging service. While the project was developed to replace the (now decommissioned) GitHub2Fedmsg service, we did not have a user interface for managing webhook binds with Fedora Messaging. The migrating users of the GitHub2Fedmsg service had to hence request for the creation of webhook binds via an issue tracker and the incoming users had to utilize the Swagger UI to create the webhook binds by themselves – which worked just fine but was definitely not ideal.

Given that since then, the project has evolved significantly into an ecosystem of Webhook-based communications to the Fedora Messaging. The support for Forgejo and GitLab repositories was added to support the Fedora Project’s and CentOS Project’s transitions to these platforms respectively. With active discussions around the frontend requests and design architectures, we finally came around to making an interactive user interface available for the Webhook To Fedora Messaging users. Please feel free to give it a try on the production environment and consider helping with the maintenance efforts of the project!

Infra and RelEng Update – Week 35

August 29, 2025 / lenkaseg / 0 Comments

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you both infographic 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: 25 Aug – 29 Aug 2025

An image with the word release schedule planner over a calendar.

Outreachy Internship Update: Building the Fedora Release Schedule Planner API

August 17, 2025 / Antony Nyagah / Comments Off

As part of my Outreachy internship with the Fedora Project, I’m building an API to modernize how Fedora plans its release cycles.

With the help of my mentor Tomáš Hrčka, the goal is to replace the current XML-heavy system currently on pagure.io with something flexible, easy to use, and well-structured.

Explore the source code on Codeberg: Fedora Release Schedule Planner.

Why This Project Matters

Fedora’s current release planning tools rely on manual XML editing, which is challenging for newcomers and difficult to scale. This project aims to:

Improve contributor experience with interactive API documentation.
Support seamless querying and updating of release data.
Allow smoother integration with Fedora’s broader tooling.

Progress Highlights

Framework migration:
- Transitioned from Flask to FastAPI (PR Link)
- Leveraged Pydantic for data validation due to deep integration with FastAPI
- Introduced auto-generated Swagger documentation

Documentation for the release schedule planner API

Code refactor:
- Adopted modular architecture with clean routing (PR Link)
- Standardized endpoint naming
CI/CD setup:
- Integrated a CI pipeline using Forgejo Actions for automated testing (PR Link)

These changes already make onboarding contributors easier and improve testability.

What’s Next

I’m excited about these upcoming milestones:

Refining and aligning tests with the FastAPI structure.
Integrating with Fedora infrastructure for live data.
Strengthening the deployment pipeline for production.

Challenges

My biggest challenge and opportunity is simultaneously learning new backend technologies like FastAPI and OpenID Connect for authorization, along with techniques to improve developer onboarding. Though the learning curve is steep, my mentor’s continuous guidance on the Fedora infrastructure, career development and general advice makes it manageable.

Reflections

This internship has been an incredible learning experience. I’m gaining hands-on exposure to backend architecture, continuous integration practices, and open-source collaboration. More importantly, the chance to build something lasting for Fedora makes the work genuinely rewarding.

There’s a lot left to tackle, and I’m looking forward to pushing it further.

Infra and RelEng Update – Week 32

August 8, 2025 / lenkaseg / Comments Off

Week: 04 Aug – 08 Aug 2025

Infra and RelEng Update – Week 31, 2025

August 1, 2025 / jnsamyak / Comments Off

Week: 28th July – 01st August, 2025

Infra and RelEng Update – Week 30 2025

July 25, 2025 / zlopez / Comments Off

Week: 21st – 25th July 2025

Infra and RelEng Update – Week 29

July 18, 2025 / lenkaseg / Comments Off

Week: 14 July – 18 July 2025

Infrastructure & Release Engineering

The 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.).
List of planned/in-progress issues