infrastructure May 2023

infrastructure@lists.fedoraproject.org

9 participants
8 discussions

Start a nNew thread

hyperkitty/mailman3 now updated to the latest
by Reon Beon 13 Nov '23

13 Nov '23

Nice.

5 7

AWS gp2 -> gp3
by Miroslav Suchý 13 Sep '23

13 Sep '23

tl;dr I want to change **all** storage types in AWS from gp2 to gp3 next week. The recent Change proposal https://fedoraproject.org/wiki/Changes/CloudEC2gp3 brought to my attention that gp3 is actually faster and cheaper than gp2. The comparision is as follows: gp2: * $0.10 per GB-month * IOPS: 100 IOPB, burstable to 3000 IOPS * Throughput: Throughput limit is between 128 MiB/s and 250 MiB/s, depending on the volume size. gp3: * IOPS: 3000 for free, addional IOPS can be bought * Throughput 125 MiB/s for free, addional throughput can be bought For more information see https://aws.amazon.com/blogs/storage/migrate-your-amazon-ebs-volumes-from-g… We have about 150 volumes of gp2 type in AWS. Copr is the most prominent user, but there are other: libravatar, taiga, TF, and other... The type of the storage can be changed on the fly - even for attached and volumes in-use. I already tried that with my private server. Unless somebody will have objections I plan to change volume types to gp3 for Copr next week and for all other services in week following Easter. I also modified fedimg template to allow gp3 https://pagure.io/fedora-infra/ansible/c/034cf953db5d0519eb327136abd72a2ee6… If you have scripts outside of fedora-infra/ansible to provision instances that uses gp2 for volumes, it will be great if you can move it to gp3. Miroslav

4 18

Ansible role for cron task
by seddik alaoui ismaili 30 May '23

30 May '23

Hi folks, We decided to add cron to compress some merged logs. So I realize that we didn't have any Ansible role to do this. Currently we manage cron tasks separately in the component's role, and IMO it will be difficult to find/make modifications when needed. Do you think it's beneficial to create new one ? Or perhaps someone has clever ideas :) ? +1/-1 ?? seddik (saibug)

4 5

Planned Outage of s390x affecting all koji 2023-06-01
by Stephen Smoogen 26 May '23

26 May '23

Planned Outage - koji/s390x - 2023-06-01 05:00 UTC There will be an outage starting at 2023-06-01 05:00 UTC, which will last approximately 24 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2023-06-01 05:00UTC' Reason for outage: The Red Hat Westford location will have more power line work done. This will require the building to be powered down in places which will affect various services like network connections and s390x builders. Affected Services: koji builds and composes will be affected with builds waiting until the s390x builders are able to complete the work. Ticket Link: https://pagure.io/fedora-infrastructure/issue/11345 Please join #fedora-admin or #fedora-noc on irc.libera.chat or add comments to the ticket for this outage above. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Planned Outage - Server updates/reboots - 2023-05-17 21:00 UTC
by Kevin Fenzi 15 May '23

15 May '23

Planned Outage - Server updates/reboots - 2023-05-17 21:00 UTC There will be an outage starting at 2023-05-17 21:00 UTC which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2023-05-17 21:00UTC' Reason for outage: We will be updating various servers to newest versions of packages and os levels. As part of this outage, koji builders will be moved from Fedora 37 to Fedora 38. Services may be up and down in the outage window. Affected Services: Most services will be affected for short periods of time. Ticket Link: https://pagure.io/fedora-infrastructure/issue/11312 Please join #fedora-admin or #fedora-noc on irc.libera.chat or add comments to the ticket for this outage above.

1 0

SOP for adding externally hosted services?
by Tim Flink 09 May '23

09 May '23

We're looking to deploy an instance of ReportPortal [1] for displaying and analyzing the output of automated tests in Fedora. This aligns with the goals of Testing Farm and instead of having it hosted with the other Fedora hosted apps, it looks to be easier to rely on their setup/infrastructure. Are there requirements around having something like reportportal.fedoraproject.org point to the service once it's up? I couldn't find anything by searching through the lists but I have a vague recollection of hearing talk about requirements in the past. Thanks, Tim [1] https://reportportal.io/

2 2

Do koji's compose directories need cleaning?
by Mattia Verga 07 May '23

07 May '23

I'm unsure if this is something desired or if it is better to open a formal ticket on [releng|infra]. Looking in the compose directories of Koji I've noticed that there seem to be a lot of garbage leftover from old stuff: - in https://kojipkgs.fedoraproject.org/compose/iot/ there are composes back to Fedora 31 - in https://kojipkgs.fedoraproject.org/compose/updates/ there are composes back to Fedora 31, EPEL6, Fedora Modular 30 - again in https://kojipkgs.fedoraproject.org/compose/updates/ there are garbage directories starting with "[[ release.id_prefix.title() ]]-" which seem quite recent - again in https://kojipkgs.fedoraproject.org/compose/updates/ there are some ".shelve" files related to f26, f27 and f28 Do we want to clean those things up? Mattia

2 1

This list and discussion.fedoraproject.org
by Kevin Fenzi 04 May '23

04 May '23

As some of you who follow the devel list may know, Matthew put forward the idea of starting to move some discussion over to discussion.fedoraproject.org (our hosted dicourse instance) instead of the mailing list. For those of you who don't know: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… (and the long thread after it). Please do read that. I'll wait. ok. So, my question is: Should we look at moving to discussion.fedoraproject.org instead of this list? We have a tag there already. I've personally setup discourse to email me things, so it actually ends up being very similar to a list, with a few corner cases. I'm happy to help anyone who has trouble with that setup. Thoughts? kevin

7 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure May 2023