When CentOS Stream 8 workload (itself EOL since June 2024 now) was migrated/consolidated to same koji infra that was used for centos stream 9 , we had a temporary single node (kojihub) setup to still present the (old) centos stream 8 buildroot to outside and at the previous url : https://koji.mbox.centos.org/koji/
As we are reviewing all the services still running from the DC that needs to be cleared out, I asked internal stakeholders about that old (unused) kojihub infra and was told to just nuke it.
We'll just send mail to centos-devel list to announce it and come with a date for full decommission (before DC move)
Metadata Update from @arrfab: - Issue marked as blocking: #1579 - Issue tagged with: centos-common-infra, centos-stream, dc-move, medium-gain, medium-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
Starting to decom first storage/backup space that was still used for koji.mbox setup. We'll just keep an offsite backup but nothing more. Then I'll just decom the VM/ip addresses/etc
@gwmngilfen : as a FYI, trimmed data from that buffer pool in backup plan/storage box and it's also working with fstrim for underlying VDO volume :
/backup: 5.3 TiB (5831650357248 bytes) trimmed lvs|egrep 'LV|backup|vpool' LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert backup vg_r7615-2 vwi-aov--- 50.00t vpool0 54.38 vpool0 vg_r7615-2 dwi-ao---- 40.00t 68.21
all gone so closing
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.