This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. We provide you with both an infographic and a 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: 03rd – 07th November 2025
Continue readingThis 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: 27 October – 31 October 2025
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
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: 20th – 24th October 2025
Continue readingThis 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: Oct 13 – Oct 17 2025
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
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: Oct 6 – Oct 10 2025
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
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: 22nd – 26th September 2025
Continue readingThis 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: 1st – 5th September 2025
Continue readingWe are excited to announce the general availability of the MetaSource (or MDAPI 4) in both the staging and production Fedora Infrastructure environments. The release includes an architectural rewrite of the MDAPI from Python to Go, making it a performant source of RPM repositories metadata as a REST service with 1:1 API compatibility. More details about the developments and acknowledgements are below.
The project faced a critical challenge due to its dependence on SQLite3-based RPM repositories metadata which were deprecated by the Fedora Linux 41 release. Rather than applying temporary workarounds on the existing codebase, we took this opportunity to fundamentally redesign the project. The improvements included optimized processing of XML-based RPM repositories metadata, swifter response towards HTTP REST operations, interactive documentation for ecosystem experience, stellar coverage across functional testcases among other things. The move from Python to Go programming language allowed us to take advantage of the performance benefits and resource efficiency – all while ensuring that the solution stays simple enough to maintain for a high-throughput HTTP service for a cloud-native first deployment.
| Services | Sample Count | Total Duration | Per request Duration |
| MDAPI MDAPI v3.1.7 | 1000 requests | 63 minutes, 3 seconds | 3.7828 seconds |
| MetaSource MDAPI v4.0.0 | 1000 requests | 42 minutes, 30 seconds | 2.5505 seconds |
| Services | Average Memory | Minimum Memory | Maximum Memory |
| MDAPI MDAPI v3.1.7 | 157.09 MiB 160,861 KiB | 99.16 MiB 101,544 KiB | 204.34 MiB 209,248 KiB |
| MetaSource MDAPI v4.0.0 | 109.72 MiB 112,350 KiB | 81.66 MiB 83,616 KiB | 174.52 MiB 178,712 KiB |
MetaSource (or MDAPI v4.0.0) performs roughly 33% faster than MDAPI v3.1.7 while using about 30% lesser memory than that on sustained querying operations. This means that MetaSource would be able to address approx 50% additional requests without furthering resource consumption. Please note that the results may vary depending on unknown variables like network bandwidth and querying nature.
| Services | Sample Duration | Total Count | Per request Duration |
| MDAPI MDAPI v3.1.7 | 500 seconds | 148 requests | 7.3615 seconds |
| MetaSource MDAPI v4.0.0 | 500 seconds | 310 requests | 3.5530 seconds |
| Services | Average Memory | Minimum Memory | Maximum Memory |
| MDAPI MDAPI v3.1.7 | 217.41 MiB 222,625 KiB | 136.73 MiB 140,008 KiB | 289.93 MiB 296,888 KiB |
| MetaSource MDAPI v4.0.0 | 187.02 MiB 191,510 KiB | 130.68 MiB 133,816 KiB | 257.44 MiB 263,624 KiB |
MetaSource (or MDAPI v4.0.0) performs roughly 52% faster than MDAPI v3.1.7 while using about 14% lesser memory than that on concurrent querying operations. This means that MetaSource would be able to address approx 110% additional requests without furthering resource consumption. Please note that the results may vary depending on unknown variables like network bandwidth and querying nature.
This project would not have been possible without the help of Akashdeep Dhar, Kevin Fenzi, David Kirwan, Michal Konecny, James Antill, Steve Milner, Shounak Dey and countless others who have either contributed to Fedora Infrastructure projects ecosystem or the createrepo_c project. We ask the readers to contribute to the project by developing, maintaining, testing or documenting the project.
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!
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
Continue readingCopyright © 2025 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments