As many of you already know, Red Hat has asked all employees to work
from home. I know that many (most?) of you don't work from a Red Hat
office normally (particularly if you're not a Red Hat employee!), but
I want to check on the impact that an extended shutdown might have on
the infrastructure, particularly the release engineering activities as
we approach the Fedora 32 GA (currently scheduled for 21 April).
In addition, what are our personnel risks? For example, if Mohan gets
too sick to work, do we have enough shared knowledge and access to cut
Obviously, everyone is going to be impacted in some way, even if none
of us get sick. This is a stressful and uncertain time. I've made it
clear to Fedora and Red Hat leadership that we will continue with the
schedule, but that the priority is the health of our community
members. I don't want anyone working beyond what's reasonable for
their personal situation. I just need to understand the risks so we
can make plans to mitigate them or adjust the release schedule.
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Just forwarding on this to the infrastructure list too
in case anyone else needs to know. Spread the word. :)
----- Forwarded message from Kevin Fenzi <kevin(a)scrye.com> -----
Date: Fri, 13 Mar 2020 12:55:36 -0700
From: Kevin Fenzi <kevin(a)scrye.com>
Subject: NOTICE: Upcoming extended downtime for Fedora Project Communishift
You are receiving this email because you are in the Fedora Project
Communishift system group that tracks users who have been
granted provisioning ability in Communishift.
We would like to notify you of some upcoming extended downtime
for the communishift cluster. As some of you may know, later
this year the Fedora Project is moving entirely out of our main
datacenter in Phoenix, AZ, USA (where the communishift cluster
is currently located).
We explored various options to migrate the cluster to minimize
downtime, but we just don't have extra hardware or resources to
setup a duplicate cluster anywhere currently. So, unfortunately,
that means we will need to power off the cluster, ship it to a
new datacenter and bring it back up there.
The estimated timeline for this looks like:
2020-04-13 - power off, derack, pack and ship
2020-04-20 - Arrival at new DC (or before)
2020-04-23 - Unpack, re-rack, cable, network
2020-04-30 - Reconfigure/reinstall
2020-05-08 - fully back in service
Note that these dates are subject to shipping and availability of
people to rack and setup and other items beyond our control.
We will update the following ticket with progress/status:
To be ready for this outage, we recommend you back up all your
application configuration and data. Due to network changes we may
have to reinstall the cluster and thus you may need to reload your
You can find information on this at:
Please let us know if there is anything we can do to assist
you during this move or if you have any questions for us.
----- End forwarded message -----
You are kindly invited to the meeting:
Fedora Infrastructure on 2020-03-12 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.
There's several smallish issues in our koji:
* texlive doesn't build ( https://pagure.io/koji/issue/1119 )
* you can't use the interface to look at newRepo and other tasks made by
a sidetag thats since been deleted ( https://pagure.io/koji/issue/1866 )
I'd like to propose upgrading to the 1.20.1 bugfix release that has
fixes for both these things.
There's no schema changes so we can easily roll back to 1.20.0 if
https://pagure.io/koji/roadmap/1.20.1/ has the full list of bugfixes in