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: 12th – 16th May 2025
Continue readingWe announced the end of OpenID authentication in Fedora in March. The original date of this was set to 20th May 2025. The progress could be followed in this ticket.
We reached to services that are using OpenID for authentication and asked them to move to OIDC. There were few that we already helped to move:
This plan will allow us to potentially migrate from current solution to something better maintained without breaking the OpenID authentication.
This means that the new date for end of OpenID support in Fedora is to be decided.
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: 31st March – 4th April 2025
Continue readingOn the latest Fedora Infrastructure weekly meeting we decided on a date of OpenID authentication sunset. The date is 20th May 2025.
The OpenID is being replaced by OpenIDConnect (OIDC) in most of the modern web and most of the Fedora infrastructure is already using OIDC as the default authentication method. OIDC offers us better security by handling both authentication and authorization. It also allows us to have more control over services that are using Fedora Account System (FAS) for authentication.
With the End Of Life of OpenID we will switch to OIDC for everything and no longer support authentication with OpenID. If your web or service is already using OIDC for authentication nothing will change for you. If you are still using OpenID open a ticket on Fedora Infrastructure issue tracker and we will help you with migration to OIDC. For users using FAS as authentication option there should be no change at all.
We will be reaching to services we identified as using OpenID directly, but as we don’t have control over OpenID authentication we can’t identify everyone.
If you are interested in following this work feel free to watch this ticket.
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: 10 – 14 March 2025
Continue readingHello readers of community blog!
Recently on community blog round table meeting we had an interesting conversation about the future of community blog and we would like to hear your feedback on that discussion.
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: 10th Feb – 14th Feb 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: 20th January – 24th January 2025
Continue readingThe Fedora Project has instances in a number of datacenters and clouds all over the world, but a majority of instances are in a datacenter located in Virginia, USA. This datacenter space, along with the majority of servers in it, were generously provided by our primary sponsor, Red Hat. We moved to our current space from another Red Hat datacenter back in 2020, and now it’s time to move again.
So why would we want to move? Well, there’s a number of reasons:
After a bunch of discussion and planning, we will be moving to a new datacenter near Raleigh, NC. This site will give us room to expand and has much more available power, allowing for higher densities.
The good news – most of the new hardware has already been purchased! We plan to install and set up the new hardware in the new datacenter, logically switch to the new site with slightly temporarily diminished capacity ( mostly in staging ).Then, we will ship the newer machines from the old datacenter to the new one, bringing everything back to greater than 100% capacity.
Our goal is to complete this move over the course of a few weeks, and have everything back up with greater capacity than before, and with as minimal impact to the project as possible.
We are looking at mid May to do the switchover, after Fedora 42 has been released. Timing is still tentative, but we will provide more detailed information as the plan dates solidify. Our next key milestone is to use the Beta Go/No-Go as an indicator that this is the best time to execute the move. At the end of this transition we expect everybody’s experience will be faster builds, faster tests, and to have room for further expansion in the future.
This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of 2024. As these teams are working closely together, we will summarize the work done in one blog post by both teams.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
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