<@abompard:matrix.org>
20:00:40
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@abompard:matrix.org>
20:00:42
!info invitees @smilner:fedora.im
<@abompard:matrix.org>
20:00:42
!info Reminder: Speak up if you want to work on a ticket!
<@abompard:matrix.org>
20:00:42
<@abompard:matrix.org>
20:00:42
!info Agenda is at https://board.net/p/fedora-infra-daily
<@abompard:matrix.org>
20:00:42
<@abompard:matrix.org>
20:00:42
!info Meeting is 30 minutes MAX. At the end of 30, its stops
<@abompard:matrix.org>
20:00:42
<@abompard:matrix.org>
20:00:42
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@abompard:matrix.org>
20:00:42
!chair @nirik:matrix.scrye.com, @phsmoura:fedora.im, @james:fedora.im
<@abompard:matrix.org>
20:00:42
<@abompard:matrix.org>
20:00:42
<@meetbot:fedora.im>
20:00:45
Meeting started at 2026-02-10 20:00:40 UTC
<@meetbot:fedora.im>
20:00:46
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@meetbot:fedora.im>
20:00:47
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@smoliicek:fedora.im>
20:00:53
!hi
<@zodbot:fedora.im>
20:00:54
Vít Smolík (smoliicek) - he / him / his
<@james:fedora.im>
20:00:56
Hey
<@smoliicek:fedora.im>
20:01:03
hello
<@phsmoura:fedora.im>
20:01:18
hello
<@nirik:matrix.scrye.com>
20:01:25
morning. I am sort of here, sort of in the fesco meeting thats finishing up
<@james:fedora.im>
20:01:53
Luckily not much will be happening here, so it's good :)
<@james:fedora.im>
20:01:56
!next
<@abompard:matrix.org>
20:02:03
<@abompard:matrix.org>
20:02:03
!topic Tickets needing review
<@abompard:matrix.org>
20:02:03
Run `!ticket #<number>` for each ticket, discuss and classify. DON'T DO THIS FOR PRIVATE TICKETS.
<@abompard:matrix.org>
20:02:03
<@abompard:matrix.org>
20:02:03
!info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
<@james:fedora.im>
20:02:14
No unlabaed tickets
<@smoliicek:fedora.im>
20:02:16
no new tickets
<@james:fedora.im>
20:02:18
!next
<@abompard:matrix.org>
20:02:21
!topic Planning, Upcoming work and Open floor
<@james:fedora.im>
20:03:15
Had a weird anubis issue with downloading repos.
<@nirik:matrix.scrye.com>
20:03:16
there was some cloudfront problems this morning sadly. ;(
<@nirik:matrix.scrye.com>
20:03:38
anubis has been more aggressive lately it seems like... and people also have seen errors from it.
<@nirik:matrix.scrye.com>
20:03:56
but nothing has changed on our side. So, not sure... perhaps it's a resource thing? but I am not sure how
<@smoliicek:fedora.im>
20:04:11
can confirm, the anubis errors at least
<@smoliicek:fedora.im>
20:04:27
although a cache wipe & refresh fixed it
<@james:fedora.im>
20:04:55
Yeh, the fix also seems temporary (or do you think we can keep all the repos. downloadable for a bit?)
<@nirik:matrix.scrye.com>
20:05:38
well, I changed it to allow cloudfront agent...
<@james:fedora.im>
20:05:47
Ahh, fair enough.
<@nirik:matrix.scrye.com>
20:06:07
just reloading has fixed anubis errors here... but again, not sure why we are seeing them all of a sudden
<@nirik:matrix.scrye.com>
20:06:19
it might be also that scrapers are hitting more aggresively (if thats possible)
<@nirik:matrix.scrye.com>
20:07:46
it keeps challenges in memory, but it should have lots of memory...
<@james:fedora.im>
20:08:58
Is there any kind of mailing list or something where people who deploy anubis talk about experiences?
<@nirik:matrix.scrye.com>
20:09:16
not that I know of. There are github discussions I think?
<@james:fedora.im>
20:10:29
Yeh, not sure ... was hoping there'd be something like the old nanog newsgroup, or even the distro. security lists.
<@nirik:matrix.scrye.com>
20:11:29
There might be, but I am not aware of them... let me know if you find one
<@james:fedora.im>
20:12:25
haha, fair enough.
<@james:fedora.im>
20:13:51
For me: I have an initial version of the mirror forge for ansible repo. ... will almost certainly do a PR for it, maybe try to deploy it somewhere in staging first?
<@nirik:matrix.scrye.com>
20:15:45
normally yeah... but we have no staging batcave... and no staging ansible repo messages. So, I would say just lets schedule a time for the migration and expect to debug if there's problems?
<@nirik:matrix.scrye.com>
20:16:13
I mean worst case we manually run 'git pull' to update it while we fix the sync
<@james:fedora.im>
20:17:30
Okay ... anyone have anything else?
<@nirik:matrix.scrye.com>
20:17:31
it would definitely be nice to get ansible repo moved.
<@nirik:matrix.scrye.com>
20:18:18
storinator01 is finally moved and up and working in rdu3. ;) Just some last network acls and it will be all done
<@nirik:matrix.scrye.com>
20:20:08
I don't have much else.
<@james:fedora.im>
20:20:44
!endmeeting