Tag: Fedora Infrastructure (page 1 of 6)

Less than 2 weeks until the Datacenter move

It’s less than 2 weeks until the switch of fedoraproject to our new datacenter, so I thought I would provide a reminder and status update.

Currently we are still on track to switch to the new datacenter the week of June 30th. As mentioned in previous posts:

  • End users hopefully will not be affected (mirrorlists, docs, etc should all be up and working all the time)
  • Contributors should expect for applications and services to be down or not fully working on Monday the 30th and Tuesday the 1st. Contributors are advised to hold their work until later in the week and not report problems for those days as we work to migrate things.
  • Starting Wednesday the 2nd things should be up in the new datacenter and we will start fixing issues that are reported as we can do so.

We ask for your patience in the next few weeks as we setup to do a smooth transfer of resources.

Another update on the Fedoraproject Datacenter Move

Here’s another update on the upcoming fedoraproject Datacenter move.

Summary: there have been some delays, the current target switch week
to the new Datacenter is now the week of 2025-06-30.
( formerly 2025-05-16 ).

Continue reading

2025 Fedora Datacenter move update

In January this year, we let the community know that we were going to be moving datacenters ( see https://communityblog.fedoraproject.org/fedora-datacenter-move-later-this-year-2025-version/ ). Some things have changed a little, so here’s some updates on the progress of this move and some more detailed plans.

Back in that initial post, we were targeting May to switch to the new datacenter, but due to various issues beyond our control, the current plan is now to switch to the new datacenter the week of June 16th. This is the week after DevConf.cz, and two weeks after Flock.

We already have new hardware in the new datacenter and should be getting access to it in the coming weeks. Then, we will build out a copy of our existing infrastructure there. Anything that can be setup and prepped for the move will be. After that, in May we hope to move a few things that are somewhat isolated from the rest of our infrastructure (OpenQA, Fedora CoreOS, and possibly more).

Then, the week of June 16th we will migrate applications and data to the new datacenter.

Fedora Project users should not notice much during this change. Mirrorlists, mirrors, docs, and other user facing applications should continue working as always. Updates pushes may be delayed a few days while the switch happens. Our goal is to keep any end user impact to a minimum.

For Fedora Contributors, Monday and Tuesday we plan to “move” the bulk of applications and services. Contributors should avoiding doing much on those days as services may be moving around or syncing in various ways. Starting Wednesday, we will make sure everything is switched and fix problems or issues as they are found. Thursday and Friday will continue stabilization work.

It’s worth noting that some things are not included in this move:

  • pagure.io is not moving now (It will likely move later in the year, details on that later!), so it should be available the entire time of the switch.
  • discussion.fedoraproject.org is not affected.
  • mirrorlists and all static content like docs, fedoraproject.org download site, etc.

The following week the newest of the old hardware in our old datacenter will be powered off and shipped to the new datacenter. This hardware will add additional capacity to some systems like openqa and builders.

Finally after that we will rebuild our staging setup. Some of that work may be done in advance, but we will be focusing on the production setup.

This move will get us moved to new (faster!) hardware, increase capacity in various of our systems, add ipv6 connectivity, move to power10, and leave us room to grow and add more as needed later. Thanks in advance for your patience with this move.

End of OpenID authentication in Fedora Account System

On the latest Fedora Infrastructure weekly meeting we decided on a date of OpenID authentication sunset. The date is 20th May 2025.

Why the change?

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.

What will change for you?

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.

What will happen now?

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.

End of Life of github2fedmsg

As was already announced in Announcing Webhook To Fedora Messaging Fedora Infrastructure team is working on replacement of github2fedmsg service. As the replacement is already deployed and users already had a few months to migrate to webhook2fedmsg we decided to say goodbye to github2fedmsg. The date that github2fedmsg will be decommissioned in fedora infra is 3rd February

Continue reading

CPE Update Q3 2024

This is a summary of the work done on initiatives by the CPE Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives + day-to-day work that needs to be done. Some of the sub-teams  are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.

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 reading

Communishift is now available

Long time after first announcement of this Fedora hosted OpenShift for community we are finally able to say that it’s available. It took us (Fedora Infrastructure Team) a long time to get over all the legal issues of hosting this in Fedora Infrastructure, but we were finally able to solve all those issues.

Communishift is made mainly for hosting containerized projects related to Fedora, but not ready for infrastructure deployment yet. For example you have a neat idea for service that will help Fedora and need to test it something. Or you want to try a testing deployment for something you already have at hand, but it was never deployed in OpenShift. If you don’t meet any of those, feel free to request the communishift project anyway and we will look at the request individually.

Continue reading

2023 Year in Review: Infra & Releng

This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of 2023. 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 reading

2023 Year in Review: Community Platform Engineering (CPE)

This is a summary of the work done on initiatives by the Community Platform Engineering (CPE) Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives and day-to-day work that needs to be done. Some of the sub-teams are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.

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 reading

FMN Replacement – Final Post

It’s been a busy month on the Fedora Messaging Notifications (FMN) Replacement team, but we’ve pushed through to the finish line and are very happy to announce the arrival of the shiny new FMN.

Continue reading
Olderposts

Copyright © 2025 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑