16:00:15 #startmeeting Infrastructure (2023-10-05) 16:00:15 Meeting started Thu Oct 5 16:00:15 2023 UTC. 16:00:15 This meeting is logged and archived in a public location. 16:00:15 The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:15 The meeting name has been set to 'infrastructure_(2023-10-05)' 16:00:15 #meetingname infrastructure 16:00:15 The meeting name has been set to 'infrastructure' 16:00:15 #chair nirik zlopez nb bodanel dtometzki jnsamyak lenkaseg patrikp 16:00:15 Current chairs: bodanel dtometzki jnsamyak lenkaseg nb nirik patrikp zlopez 16:00:15 #info Agenda is at: https://board.net/p/fedora-infra 16:00:15 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:00:16 #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra 16:00:18 #topic namaste 16:00:50 hey all... who's around for a meeting? 16:03:33 any FPC meeting today? 16:03:49 wait, is it infra? 16:03:54 .hi 16:03:55 darknao: darknao 'Francois Andrieu' 16:04:00 silly me :P 16:04:00 .hi 16:04:01 phsmoura: phsmoura 'Pedro Moura' 16:04:02 .hello salimma 16:04:04 michel-slm: salimma 'Michel Lind' 16:04:31 .hi 16:04:32 patrikp: patrikp 'Patrik Polakovič' 16:04:51 #topic New folks introductions 16:04:51 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:04:51 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:04:59 any new folks today? 16:05:01 .hi 16:05:03 zlopez: zlopez 'Michal Konecny' 16:05:36 I thought we will run this on matrix today, now that the zodbot is available there 16:06:12 well... it's still missing the meetingminutes email... 16:06:33 I suppose some might consider that not important, but IMHO its nice 16:07:29 anyhow, guess no new folks today... 16:07:42 #topic Next chair 16:07:42 #info magic eight ball says: 16:07:43 #info chair 2023-10-05 nirik 16:07:43 #info chair 2023-10-12 dtometzki 16:07:43 #info chair 2023-10-19 pcreech 16:07:43 #info chair 2023-10-26 ??? 16:07:57 anyone want 10-26? or later? 16:09:12 I can take it 16:09:41 sounds good 16:10:13 #topic announcements and information 16:10:14 #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 0730 UTC in #meeting-3:fedoraproject.org 16:10:14 #info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3 16:10:14 #info Zodbot is now available on matrix 16:10:14 #info Fedora 39 final freeze in effect 16:10:28 any other announcements? 16:11:27 ok then... moving on 16:11:31 #topic Oncall 16:11:32 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:11:32 #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/ 16:11:32 ## .oncalltakeeu .oncalltakeus 16:11:32 #info dtometzki is on call from 2023-09-29 to 2023-10-05 16:11:32 #info nirik is on call from 2023-10-06 to 2023-10-12 16:11:34 #info dtometzki is on call from 2023-10-13 to 2023-10-19 16:11:36 #info pcreech is on call from 2023-10-20 to 2023-10-26 16:11:38 #info Summary of last week: (from current oncall ) 16:11:45 .oncalltakeus 16:11:45 nirik: Kneel before zod! 16:12:09 I guess dtometzki isn't here, so moving on 16:12:18 #topic Monitoring discussion [nirik] 16:12:18 #info https://nagios.fedoraproject.org/nagios 16:12:18 #info Go over existing out items and fix 16:13:01 I noticed some issues value01 16:13:20 yeah, we need to remove that check 16:13:41 mote is in openshiift now, doesn't need to be there on value01 16:13:59 and value01 itself is going away after freeze 16:14:23 although I guess we could do that with a freeze break too 16:14:52 meetbot-raw is still on value01 I think? 16:15:07 should be on 02? 16:15:58 oh, it is.. but it should be on 02 16:16:12 or... can we just move that to openshift too? 16:16:38 it's basically just a httpd server, so yeah, I guess we could 16:16:46 then if we replace zodbot, value02 could go away too 16:17:09 What is actually emitting the alerts in fedora-noc, is this done by bot or it is configured directly in Nagios? 16:17:21 its fedmsg-irc... 16:17:27 well, wait... 16:17:38 the nagios alerts you mean? 16:17:44 Yes 16:18:04 I'm missing those in matrix, this is why I'm asking 16:18:18 nagios just sends them to a listening port on value02 and zodbot sends them to the irc channel. I talked with ryan about this and the new matrix zodbot should be able to do the same thing no problem 16:18:44 * zlopez is pleased by the answer 16:18:45 also, there's a zabbix plugin/integration that could easily be used 16:19:05 there is also fedmsg-irc running on value01... thats the thing that sends to releng channel about composes and prs and tickets. 16:19:37 I think we pretty much decided to just drop it and come up with some better way to do that (I guess in the matrix bot) 16:19:48 releng is the only irc channel still using it. 16:21:03 That's great 16:21:13 I think it would be nice to have some way for channels/groups to run that, but thats all to be determined. 16:21:54 oh, and fedmsg-irc is also the thing that sends all fedmsgs to #fedora-fedmsg irc channel (and #fedora-fedmsg-stg) 16:22:02 but we also I think were ok with dropping that. 16:23:19 I don't watch them anymore, I did in the past, but now I'm only using datagrepper when I need to check something 16:23:41 I'm not sure how useful is the constant flow of messages 16:24:04 yeah, I liked it because my irc client could log it and I could easily grep it... but yeah, datagrepper is there and... it's often really behind now and it doesn't have all messages. 16:24:53 ok, it's about 10 hours behind right now it seems. 16:25:09 which one is behind, fedora-fedmsg or datagrapper? 16:25:22 fedora-fedmsg 16:25:31 fedora-fedmsg. Because IRC limits the amount it can spew without being dropped 16:26:03 datagrepper is pretty much 100% up to date. 16:26:35 or you can run fedora-messaging listener locally pretty easily. 16:26:51 Datagrepper should be, it has direct access to timescale DB 16:27:18 Yeah, the listener is nice as well :-) 16:28:14 anyhow, anything more on this? I can file a ticket about dropping value01/value01.stg and possibly value02/value02.stg 16:28:23 +1 16:28:36 I don't have anything else to this topic 16:29:12 So, do we want to do backlog today? or call it an early meeting ? or ? 16:30:15 I wasn't here the last week, so I'm not sure what happened, was there backlog refinement? 16:30:56 was a learning topic... 16:31:05 I talked about backups 16:31:32 I think we can end it early, we can look at the backlog next time 16:31:48 yeah, I'd be ok with that. 16:31:51 #topic Open Floor 16:32:45 * zlopez falling through open floor 16:33:33 careful! 16:34:16 ok then, thanks everyone! have a great day 16:34:19 #endmeeting