[x] - outage ticket: https://pagure.io/fedora-infrastructure/issue/12455 [x] - status update: https://github.com/fedora-infra/statusfpo/pull/56 [x] - announcement sent to devel-announce/infrastructure lists SOP-ish (put this somewhere else) log into batcave01 Put your name next to the machine here (with "in progress"). run: sudo rbac-playbook vhost_update_reboot.yml If it's bare metal (You'll find out because libvirt will give an erorr and the vhost_* playbook will fail) Kevin needs to do it.

This is a overview of the 2025 datacenter move from IAD2 to RDU3. **This is also a DRAFT! Check carefully before depending on anything here! The move will be done in a number of phases. Refreshed hardware in RDU3 will be installed, data and applications will be setup there and switched to, then newer hardware from IAD2 will be shipped to RDU3 and staging env will be re-setup. Considerations

updates for week of 2025-01-27 = openqa - sometime openqa-a64-worker01.iad2.fedoraproject.org openqa-a64-worker02.iad2.fedoraproject.org openqa-a64-worker03.iad2.fedoraproject.org openqa-a64-worker04.iad2.fedoraproject.org openqa-p09-worker01.iad2.fedoraproject.org openqa-p09-worker02.iad2.fedoraproject.org

This document is a checklist/planning document around secondary riscv koji efforts. goals The goal here is to setup and populate a secondary koji for riscv builds. This will allow: fedora maintainers/community to do scratch builds on riscv Move to a setup in fedora infrastructure that more closely matches the primary instance serve as a collaboration point, speading work accross interested community members serve as a stepping stone, one place further to becoming a primary arch

updates for week of 2024-11-18 = openqa - sometime openqa-a64-worker01.iad2.fedoraproject.org openqa-a64-worker02.iad2.fedoraproject.org openqa-a64-worker03.iad2.fedoraproject.org openqa-a64-worker04.iad2.fedoraproject.org openqa-p09-worker01.iad2.fedoraproject.org openqa-p09-worker02.iad2.fedoraproject.org

:::info Location: #meeting:fedoraproject.org matrix room Date: Nov 12, 2024 16:00 (UTC) Agenda Introductions Participants:name (fromwhere)

= Introduction Currently Fedora riscv efforts are using a external koji hub/builders at http://fedora.riscv.rocks/koji As the next step toward being a full arch in fedora/eln/centos stream the next step is to move to a koji hub managed the same way the primary one is in Fedora Infrastructure. We still cannot use local builders as the currently available hardware isn't up to enterprise hosting/use, but it should be before moving to primary = secondary arch scope Ideally we get everything 100% like it is on primary. This will make it more likely/practical to merge to primary. We don't have to do everything all at once however, we can start out with laxer rules and work toward primary.

= openqa outage/updates - 2024-10-08 [x] downtime for affected hosts and guests (qvmhost01/qvmhost02) [x] update www.fedorastatus.org [x] copy xml files off qvmhost's for guests /etc/libvirt/qemu/ [x] reinstall qvmhosts with rhel9 [x] ansible and setup/restore vm's (but don't start them yet) [x] start db server up again [x] sync /var/lib/pgsql off it [x] delete old db-openqa01

Updates for week of 2024-09-30 = openqa - sometime - schedule with adamw openqa-a64-worker01.iad2.fedoraproject.org openqa-a64-worker02.iad2.fedoraproject.org openqa-a64-worker03.iad2.fedoraproject.org openqa-a64-worker04.iad2.fedoraproject.org openqa-p09-worker01.iad2.fedoraproject.org openqa-p09-worker02.iad2.fedoraproject.org

schedule https://cfp.fedoraproject.org/flock-2024/talk/P9AV9Z/ friday aug 9th starting at 9am and running until 1pm. attendees (for however long) remote: abompard (ping me in the Infra channel on Matrix) proposed items to work on:

Updates for week of 2024-07-08 = openqa - sometime openqa-a64-worker01.iad2.fedoraproject.org openqa-a64-worker02.iad2.fedoraproject.org openqa-a64-worker03.iad2.fedoraproject.org openqa-a64-worker04.iad2.fedoraproject.org openqa-p09-worker01.iad2.fedoraproject.org openqa-p09-worker02.iad2.fedoraproject.org

Updates for week of 2024-05-15 = openqa - sometime openqa-a64-worker01.iad2.fedoraproject.org openqa-a64-worker02.iad2.fedoraproject.org openqa-a64-worker03.iad2.fedoraproject.org openqa-a64-worker04.iad2.fedoraproject.org openqa-p09-worker01.iad2.fedoraproject.org openqa-p09-worker02.iad2.fedoraproject.org

Updates week of 2022-11-28 = copr = openqa = monday - 2022-11-28 [x] bvmhost-a64-01.stg.iad2.fedoraproject.org - kevin [x] bvmhost-p09-01.stg.iad2.fedoraproject.org - kevin

To: devel-announce@lists.fedoraproject.org Subject: Automated processing of (most) scm requests On 2022-xx-yy we plan to enable automated processing of (most) scm requests for package maintainers. Requests that are made with --exception will still be processed by release engineering, but all other requests should be processed by an automated process. Requests are processed as soon as the processor gets the message that they have been submitted/edited or there is a new comment on existing request. To get more information about how the automated process works check the documentation.

mon - 2022-08-15 All *.stg.iad2.fedoraproject.org bvmhost-a64-01.stg.iad2.fedoraproject.org - kevin - DONE bvmhost-p09-01.stg.iad2.fedoraproject.org - kevin - DONE bvmhost-x86-01.stg.iad2.fedoraproject.org - kevin - DONE bvmhost-x86-02.stg.iad2.fedoraproject.org - kevin - DONE bvmhost-x86-03.stg.iad2.fedoraproject.org - kevin - DONE bvmhost-x86-04.stg.iad2.fedoraproject.org - kevin - DONE bvmhost-x86-05.stg.iad2.fedoraproject.org - kevin - DONE

schedule 2022-07-06 14UTC to 16:30UTC 14:00 to 14:15UTC - introductions and barcamp voting 14:16 to 15:00UTC - first block of discussions 15:00 to 15:15UTC - break 15:16 to 16:00UTC - second block of discussions 16:01 to 16:30UTC - revisting/roundup/smaller topics discussion blocks - total 90min available, how shall we divide it. Please place an X where you prefer. 9 10min? Votes: