Well, we haven't actually talked about it much on the list because we've been in idle for so long but the next couple of weeks are going to be interesting.
This weekend: FUDCon! This is good, but also bad. Lots of us will be in one place and likely busy during the day. If alerts go out people may not get to them right away, etc, etc. If you're not coming to FUDCon please do stay around on IRC and pay attention when things go down. Even people without access to things can look and see the mirrorlist is down at ibiblio but nowhere else, sometimes little details like that can be very helpful when someone who does have access shows up to get to work. Next weekend (the 12th): The big move! https://fedorahosted.org/fedora-infrastructure/ticket/1845 This is going to be a very strange project I can just tell already. Smooge and I will be on site but also largely unavailable. Lots of people have offered to help with this and really the thing we're going to need is verification. I'm working on some procedures to follow as things come back online. Having users around to verify that things are back up and configured right could be a big time saver. For example, xen2 is back online, then dennis or someone could verify RSA access, console access PDU acces, etc. Those are all time consuming things but also can be done in parallel provided we have the people on hand to do it. So starting with the 12th, stop by #fedora-admin, we'll try to keep the migration stuff in there so people watching will know "oh, the whole buildsys is back online but we're waiting for an fsck on /mnt/koji". For stuff that's going wrong outside of the move (like the mirrorlist becoming unavailable) we'll stick that in #fedora-noc. The idea being that stuff in #fedora-noc needs to be handled immediately even though there's a move going on. questions? comments? -Mike _______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
