Hi Just want to give a short overview about the things I was able to do so far: 1) provo-mirror.opensuse.org * The machine is up and running, currently as a normal mirror server. * The mirrorbrain frontend is prepared and I took the freedom to play along with the mod_autoindex_mb to provide a bit more information to our mirror users: https://provo-mirror.opensuse.org/ => the content is in the mirrorbrain-icons RPM in openSUSE:infrastructure - submit requests welcome ;-) * https://mirrors.opensuse.org will also be handled by this machine during the downtime 2) new mirrordb machine * There is a new mirrordb machine named nala running in Provo inside a private network (same as in Nuremberg) - this mirrordb machine will just have a copy (dump) of the Nuremberg database. No updates aka scanner is planned to run during the downtime. 3) new status machine * status2.opensuse.org already has taken over the alias status.opensuse.org from status1.opensuse.org * there is a MySQL master - master setup between the two nodes (SSL encrypted, of course, but I have 250ms latency...). So far everything seems to work, thanks to the low amount of changes on status.opensuse.org 4) new keyserver machine * https://keyserver2.opensuse.org works already * I need to wait for someone who can open the needed additional ports in the firewall to get the commandline "gpg" calls also work * in general, it should be fine to point the keyserver alias ot the new machine during the downtime 5) new login machine * apache and ldap are ready * the ldap proxy can not reach the master server - this is clearly something to investigate after the downtime. I need to find a way to connect into the DMZ like on the other login nodes... That's it so far. For tomorrow, the major part will be the switch over of download.opensuse.org to the provo-mirror... CU, Lars -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org