16:00:07 #startmeeting Infrastructure (2022-07-21) 16:00:07 Meeting started Thu Jul 21 16:00:07 2022 UTC. 16:00:07 This meeting is logged and archived in a public location. 16:00:07 The chair is eddiejennings. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:07 The meeting name has been set to 'infrastructure_(2022-07-21)' 16:00:07 #meetingname infrastructure 16:00:07 The meeting name has been set to 'infrastructure' 16:00:27 #chair nirik siddharthvipul mobrien zlopez bodanel dtometzki jnsamyak computerkid 16:00:27 Current chairs: bodanel computerkid dtometzki eddiejennings jnsamyak mobrien nirik siddharthvipul zlopez 16:00:27 #info Agenda is at: https://board.net/p/fedora-infra 16:00:28 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:00:28 #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra 16:00:28 #topic greetings! 16:00:43 .hi 16:00:44 eddiejennings: eddiejennings 'Eddie Jennings' 16:00:54 .hello zlopez 16:00:55 mkonecny: zlopez 'Michal Konecny' 16:00:58 .hi 16:00:59 phsmoura: phsmoura 'Pedro Moura' 16:01:35 Welcome aboard, all! :) 16:01:56 morning 16:03:11 #topic New folks introductions 16:03:11 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:03:12 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:03:20 Do we have any new folks with us today? 16:03:37 If so, lets yourself be known, and tells us a little bit about you :) 16:03:37 hey everyone 16:03:45 We're a friendly lot and don't bite :D 16:05:41 Looks like there aren't any new folks today, so let's get down to business. 16:05:43 #topic Next chair 16:05:44 #info magic eight ball says: 16:05:44 #info chair 2022-07-21 - eddiejennings 16:05:44 #info chair 2022-07-28 - phsmoura 16:05:44 #info chair 2022-08-04 - ???? 16:06:05 Do we have any volunteers for 2022-08-04? 16:06:29 Chairing the meeting is a fun way to be involved with the project :). If *I* can do it, anyone can :D 16:07:41 As a note that date is the first day of Fedora Nest 16:07:57 yeah ,wonder if we should cancel? 16:08:01 Ah, that may be why no one is biting. 16:08:08 Probably would be wise to cancel 16:08:14 +1 16:08:21 Reminds me, I need to register for Nest :D 16:09:22 * nirik nods. it's usually a pretty fun conference. 16:09:32 By the power vested in me as chair, we'll cancel on 2022-08-04 due to Fedora Nest. 16:09:36 #info chair 2022-08-04 - Meeting cancelled due to Fedora Nest 16:09:57 It is a great power 16:10:00 👍 16:10:02 Looking ahead, any interest in 2022-08-11? If not, that's fine, we have time 16:11:14 Hearing none, let's move along 16:11:15 #topic announcements and information 16:11:28 #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1030 Europe/paris in #centos-meeting 16:11:29 #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:11:29 #info If your team wants support from the Fedora Program Management Team, file an isssue: https://pagure.io/fedora-pgm/pgm_team/issues?template=support_request 16:11:29 #info please help us with improving contribution to fedora infra https://discussion.fedoraproject.org/t/improving-contribution-to-fedora-infrastructure/38294/8 16:11:31 #info oncall should also handling #fedora-releng pings if possible 16:11:33 #info 1/2 day 'barcamp' infra and releng workshop: https://pagure.io/flock/issue/393 (please add your throughts!) at nest approved 16:11:38 #info nest registration open now (aug 4th-6th): https://communityblog.fedoraproject.org/nest-with-fedora-2022-registration-now-open/ 16:12:21 I'd like to note the 1/2 day hackfest at nest... do think of ideas on what you would like to discuss/hear/learn/do... 16:13:15 for those of you who never heard of barcamp... it's a way to self organize a group of folks. You gather then everyone puts up ideas on what they would like to discuss/do/talkabout... then everyone votes, then you start doing them in vote order. 16:13:38 Ah 16:13:41 dunno if it will work for this, but I thought I would give it a try. 16:13:45 * Southern_Gentlem loved fudcon barcamps 16:14:03 Worst that happens is you learn what doesn't work 16:14:12 * eddiejennings is registered for Fedora Nest. 16:14:25 I'll try and find some tool(s) we can use and update the ticket with them... 16:14:38 I will also be there, hopefully we get a decent few people 16:15:14 nest has been pretty popular in the past. :) 16:15:27 Any other announcements? 16:15:28 I will be there as well 16:16:29 Hearing none, we'll keep on moving :) 16:16:30 #topic Oncall 16:16:50 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:16:50 #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/ 16:17:07 #info eddiejennings on call from 2022-07-15 to 2022-07-21 16:17:07 #info mkonecny is on call from 2022-07-22 to 2022-07-28 16:17:07 #info ??? is on call from 2022-07-29 to 2022-08-04 16:18:11 .oncalltakeeu 16:18:11 mkonecny: Kneel before zod! 16:18:11 Can't do that one but willing to take the one after 16:18:21 Do we have any volunteers for the week before Nest? and the week of 2022-08-05 - 2022-08-11? 16:18:46 sold! 16:19:08 I can take that last one if no one else wants it 16:19:10 I can take the 07-29 16:19:23 #info mobrien is on call from 2022-08-05 to 2022-08-11 16:19:28 is that right mobrien? 16:19:35 sold to darknao! 16:19:51 Yep, good with me. Thanks eddiejennings 16:20:06 #info darknao is on call from 2022-07-29 to 2022-08-04 16:20:59 Thank you both for your willingness! :) 16:21:01 #info Summary of last week: (from current oncall ) 16:21:22 while I haven't been able to attend stand-ups this week, I've been watching the rooms via Element. 16:21:34 There has been activity, but not specific pings to oncall for this week 16:22:31 And with that we turn it over to nirik! 16:22:33 #topic Monitoring discussion [nirik] 16:22:33 #info https://nagios.fedoraproject.org/nagios 16:22:33 #info Go over existing out items and fix 16:23:41 so, we are looking better here than we have in a while. 16:23:55 managed to get all lthe mgmt interfaces and such that were down fixed, so we have nothing down. 16:24:06 then there's the random small things. 16:24:12 Great news :D 16:24:13 Overall not too bad... 16:26:40 I do not believe we have a learning topic for this week, correct? 16:27:10 I'll be putting F36 onto my laptop today and will be setting up my BTRFS snapshot backups soon thereafter; thus, I'll be ready for my next one about BTRFS "soon" :D 16:28:06 yeah, I don't think we had any planned... unless someone wants to jump in with one. 16:28:36 Ok. Let's do a quick check of blocked tickets. 16:28:38 #topic Revisit blocked tickets 16:28:38 #info Check if any blocked ticket is unblocked 16:28:38 #link https://pagure.io/fedora-infrastructure/issues?status=Open&tags=blocked&priority=0&close_status= 16:28:54 * nirik looks 16:29:11 .ticket 7361 16:29:14 eddiejennings: Issue #7361: Signing infrastructure for aarch64 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7361 16:29:30 nope, all still blocked 16:29:40 as far as I know. 16:29:48 noted. 16:29:52 .ticket 8291 16:29:53 eddiejennings: Issue #8291: Fedora messaging - Translation platform topics review - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8291 16:29:55 unless mobrien found anything on 10723 16:30:31 Actually looking at the list, the only other that would seem somewhat pressing is 10676 16:31:33 I'm working on it, but its dealing with a big company. 16:31:57 its now blocked on me filing yet another ticket another place 16:32:05 I can empathize 16:32:06 I will try and do that today 16:33:30 I do want to discuss a ticket real quick before we move on. 16:33:41 .ticket 9549 16:33:42 eddiejennings: Issue #9549: Tor hidden service for update metadata - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9549 16:33:54 I put a small book into the fedora-infra chat about it. 16:34:50 the tl;dr = I need to be taken off the ticket, and as far as the request itself. I don't see much gain from it for the seeming non-trivial amount of work that will need to be done. 16:35:49 I don't know if there's a closure option of "This seems interesting, but it's not happening," but if there is, that's my recommendation for the ticket. 16:36:25 Or maybe it add it to a suggestion list, so it's not an open "Issue" 16:37:42 alright. 16:38:03 it may be worth pinging the submittor in case they have information/desire to directly work on it... 16:38:17 but yeah, could close it out too. 16:38:54 nirik: I did discuss with the osbuild folks and the suggestion was to use a channel in koji to assign certain builders to os build tasks and have those dedicated with looser firewalls 16:39:17 True. They haven't added anything in a year, and I think it would be good to get their idea of the how, because for what I see, the end result will be a kind of split-brain proxy thing. But mind you, that's the opinion of a person who is not a master of Tor services, but has relied on docs and some testing 16:40:05 mobrien: ok, so that means they would do all of the osbuild? ie, take the request, do the api call, get the request from osbuild and do the acutal build? or just the api call 16:40:34 eddiejennings: worth asking and if they don't answer we can close... 16:40:44 I'll do that. 16:41:23 Just the api call for the IOT stuff so they could be low resource. If we branch out to use imagebuilder for more stuff and use bring your own builder for other arches we may need more 16:41:31 And for other backlog tickets... 16:41:32 #topic Fedora Infra backlog refinement 16:41:32 #info Refine oldest tickets on Fedora Infra tracker 16:41:32 #link https://pagure.io/fedora-infrastructure/issues?status=Open&order_key=last_updated&order=asc 16:42:43 Unfortunately, I've been summoned to a work call, so I have a hard stop in 10 minutes :( 16:43:16 mobrien: so, other builders take the actual build jobs? if we only have to dedicate like 2 builders I suppose it's workable... if it's more than that, I really don't like it. ;( 16:45:10 The actual builds take place on their infrastructure. We just send the api call from ours and receive the artifact back. I would agree 2 builders should be enough. We have 2 other possible solutions but they would involve some work from our side 16:45:31 either a script to constantly update the firewall or a proxy 16:45:52 I thought we were going to use our builders because they lack a bunch of arches we needed? 16:46:47 For Fedora IOT they only support 2 arches. We'll only need our own buiilders if/when we start to use it for more 16:46:52 all in all it's a pretty frustrating problem. ;( 16:47:21 Yes, I wish they would solve this on their side 16:49:52 Even though we're already there, let's move to open floor :) 16:50:04 #topic Open Floor 16:51:29 Any other things to discuss? 16:51:57 Otherwise, I'll need to wrap up early to be ready for work call (for having to touch a few of our Windows systems :( 16:52:38 Nothing here, thanks as always eddiejennings 16:53:12 nothing here 16:53:21 In that case. . . 16:53:24 #endmeeting