16:01:00 #startmeeting Infrastructure (2023-02-09) 16:01:00 Meeting started Thu Feb 9 16:01:00 2023 UTC. 16:01:00 This meeting is logged and archived in a public location. 16:01:00 The chair is dtometzki. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:01:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:00 The meeting name has been set to 'infrastructure_(2023-02-09)' 16:01:00 #meetingname infrastructure 16:01:00 The meeting name has been set to 'infrastructure' 16:01:00 #chair nirik zlopez nb bodanel dtometzki jnsamyak 16:01:00 Current chairs: bodanel dtometzki jnsamyak nb nirik zlopez 16:01:00 #info Agenda is at: https://board.net/p/fedora-infra 16:01:00 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:01:01 #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra 16:01:03 #topic greetings! 16:01:06 hello 16:01:11 .hi 16:01:12 dtometzki: Something blew up, please try again 16:01:15 dtometzki: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:01:21 .hi 16:01:22 darknao: Something blew up, please try again 16:01:25 darknao: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:01:39 .hi 16:01:40 dherrera: Something blew up, please try again 16:01:43 dherrera: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:02:03 .hello zlopez 16:02:04 mkonecny: Something blew up, please try again 16:02:07 mkonecny: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:02:20 I need to learn how to restart zodbot 16:03:18 zodbot, Does not like us today 16:03:23 :-) 16:03:46 I will try to restart it 16:03:54 hello together nice to meet you 16:04:09 morning 16:05:44 morning nirik[m] 16:05:44 no need to restart it 16:05:44 zodbot: refresh 16:05:44 I asked it to reload 16:05:44 ah, so did I. oops. 16:05:44 Thanks 16:05:44 ah sorry I was doing that out of channel 16:05:44 well we will see which one of us kneels before Zod first 16:05:44 FYI, this is: https://github.com/fedora-infra/supybot-fedora/issues/94 16:05:50 nirik[m]: Downloading caches. This could take a while... 16:05:51 I see the requests on the machine :-) 16:05:55 after some time it seems to not be able to talk to fasjson. 16:06:25 .hi 16:06:56 nirik[m]: Kneel before zod! 16:06:57 ok during refresh of zodbot let us go to the next topic 16:07:00 smooge: smooge 'Stephen Smoogen' 16:07:10 #topic New folks introductions 16:07:10 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:07:10 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:07:19 I will add this to list of tasks to fix 16:07:54 hello any new one here. Please say hello 16:07:59 ? 16:08:04 Hello, hello, folks! I’m Jason from Mumbai, India. mid 40s looking to pivot to a career in devops. come here to learn and try to pitch in and help 16:08:31 hello jasonbraganza 16:08:57 hello dtometzki :) 16:09:07 welcome jasonbraganza! 16:09:12 Welcome to world of devops 16:09:19 thank you nirik[m] 16:10:29 hi and welcome jasonbraganza 16:10:31 mkonecny, looking to learn :) i was a sysadmin for lans in the late 90s, early oughts. then turned to it consulting. an accident ruined my back. so cannot commute. hence the need to pivot :) nearest adjacent career seems to be devops :) 16:10:38 hello darknao :) 16:10:38 jasonbraganza, what are you interest to learn ? 16:11:06 ohh ok 16:11:44 dtometzki, all the cloud stuff XD on a more serious note, i want to learn to be able to learn to write code to manage machines. so that’d be ansible and terraform and docker and kubernetes and its ilk? 16:12:24 We are using ansible a lot in Fedora 16:12:25 i want to be able to get a job this year. so, all ears for what you suggest. i’ll be hangiing out in infra and asking questions and guidance 16:12:43 And we are running our own openshift instance 16:13:19 oh, hurrah! will ask you folk for a way to pitch in and help later? 16:13:41 i can write docs. i can python. :) 16:13:53 Feel free to ask in any fedora infra channel :-) 16:14:05 thank you folks for such a warm welcome! 16:14:05 great then let us start 16:14:41 #topic Next chair 16:14:41 #info magic eight ball says: 16:14:41 #info chair 2023-02-09 - dtometzki 16:14:41 #info chair 2023-02-16 - eddiejennings 16:14:41 #info chair 2023-02-23 - ??? 16:14:42 #info chair 2023-03-02 - ??? 16:15:30 I’m all set for next week :) 16:16:10 jasonbraganza, every week someone else leads through the meeting if you have time then feel free ? 16:16:27 by all means. if someone can coach me through it first. 16:16:35 anyone for 02-23 or 03-02 ? 16:16:52 .hi gui1ty 16:16:53 Penguinpee: Sorry, but user 'Penguinpee' does not exist 16:17:04 .hello gui1ty 16:17:05 Penguinpee: gui1ty 'Sandro .' 16:17:11 can i volunteer for 23rd? or too early? 16:17:19 dtometzki: I can take 23-02 16:17:54 jasonbraganza, you can check the agenda. It is most described 16:17:58 https://board.net/p/fedora-infra 16:18:18 then i can do 03-02 16:18:32 #info chair 2023-02-23 - mkonecny 16:18:36 i will have seen two more meetings by then too. 16:18:54 great and thanks to mkonecny and jasonbraganza 16:19:00 thank you both 16:19:17 #info chair 2023-03-02 - jasonbraganza 16:20:00 next topic 16:20:02 #topic announcements and information 16:20:02 #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:20:02 #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:20:02 #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:20:04 #info oncall should also handling #fedora-releng pings if possible 16:20:22 any additional news or information ? 16:20:36 yes 16:20:56 this weekend there will be a 1-3 day power outage at the Red Hat Boston facility. 16:20:57 #info Fedora 38 mass branching in progress 16:21:11 it's actually all done... except for composes. 16:21:29 this houses the s390x system 16:21:29 yeah, I filed an outage ticket on that... but I can't remember now if I sent it out or not. 16:21:49 https://pagure.io/fedora-infrastructure/issue/11082 16:22:08 starting tomorrow right? 16:22:10 the outage will start at 1300 UTC on 2023-02-10 and is hope to end by 2023-02-12 16:22:17 how many systems are down ? 16:22:31 and what is the reason ? 16:22:32 this will affect all builds because they will need to pause until the s390x comes back 16:22:51 See the ticket? ;) 16:23:02 my understanding is that it was an 8 hour window. 16:23:07 power breakers to the building melted last year. A fix was put into place and final work on it is to be completed 16:24:01 nirik[m]: I saw an email that they extended it 16:24:08 my understanding is that they want to power it off and then look at/measure things for a perm fix. 16:24:27 I see an email with an outage between 8:00 UTC and 22:00 UTC tomorrow ... 16:24:36 After feedback from GWS I understand that the 4pm EST return to service is 16:24:36 a bit optimistic. The expected resolution time is now ~8pm EST/ 1am UTC. 16:24:40 BOS, starting: 2023-02-11 05:00, ending: 2023-02-12 04:59 16:25:00 So, can someone review the ticket/adjust it and I can send it. Or if they want to send it that would be great too. 16:25:16 i will review and send 16:26:27 So, should be: starting 2023-02-10 08UTC - 2023-02-11 01 UTC 16:26:52 builds should queue up... but won't finish 16:27:12 there is a network outage scheduled after the power comes on 16:27:38 which is where the extra time comes in. 16:28:01 huh, I see no mention of it on outage list. 16:28:56 ok good 16:29:03 #topic Oncall 16:29:03 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:29:03 #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/ 16:29:03 ## .oncalltakeeu .oncalltakeus 16:29:03 #info jednorozec is on call from 2023-02-02 to 2023-02-09 16:29:04 #info mkonecny is on call from 2023-02-09 to 2023-02-16 16:29:06 #info ??? is on call from 2023-02-17 to 2023-02-23 16:29:08 #info ??? is on call from 2023-02-23 to 2023-03-02 16:29:08 anyhow, we can move on... and sort this out of meeting 16:29:34 I completely forgot I'm oncall next week :-D 16:29:41 .oncalltakeeu 16:29:41 mkonecny: Error: You don't have the alias.add capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified. 16:29:55 yes the Oncall topic anyone from 02-17 - ... 16:30:17 .oncalltakeeu 16:30:17 mkonecny: Kneel before zod! 16:30:36 i checked my calendar and i can take 16:30:45 #info dtometzki is on call from 2023-02-23 to 2023-03-02 16:31:29 anyone from 02-17 until 02-23 ? 16:31:30 I can take the 23-3 16:31:43 or 17-23 16:32:17 #info jednorozec is on call from 2023-02-17 to 2023-02-23 16:32:35 great thanks then we have the next weeks planed 16:32:57 #info Summary of last week: (from current oncall ) 16:33:14 jednorozec, your part ? 16:33:44 I dont recall getting pinged 16:34:08 then it was a nice week :-) 16:34:32 except for the last 30hrs of branching ;) 16:34:45 the next topic is for nirik[m] 16:34:54 #topic Monitoring discussion [nirik] 16:34:54 #info https://nagios.fedoraproject.org/nagios 16:34:54 #info Go over existing out items and fix 16:35:08 nirik[m], ? 16:35:34 so, nothing too exciting here this week. Pretty much same old same old. There's a ticket to fix some long standing alerts... if anyone wants to work on it. 16:35:39 we can just move on 16:36:07 ok good 16:36:12 #topic Revisit blocked tickets 16:36:13 #info Check if any blocked ticket is unblocked 16:36:13 #link https://pagure.io/fedora-infrastructure/issues?status=Open&tags=blocked&priority=0&close_status= 16:36:56 any news to the 4 tickets ? 16:37:29 ope 16:37:34 nope even. 16:38:51 so for today we have no learning topic planned 16:39:08 then i think we will do 16:39:11 #topic Fedora Infra backlog refinement 16:39:12 #info Refine oldest tickets on Fedora Infra tracker 16:39:12 #link https://pagure.io/fedora-infrastructure/issues?status=Open&order_key=last_updated&order=asc 16:39:58 .ticket 10426 16:40:00 dtometzki: Issue #10426: Setting up Cavil for automated legal checks for packages - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10426 16:40:37 still just needs someone to have cycles to look into it. 16:40:52 we could use communishift for a proof of concept setup 16:41:57 I can update it, we can move to next? 16:42:12 ok 16:42:30 .ticket 8167 16:42:31 dtometzki: Issue #8167: Adding topic authorization to our RabbitMQ instances - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8167 16:42:57 abompard worked on this some, but I am not sure what the status is. 16:43:04 I can ask in ticket. 16:43:35 thanks nirik[m] 16:43:37 .ticket 10383 16:43:38 dtometzki: Issue #10383: Upgrade Venus to Pluto - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10383 16:44:07 it is a great subject :-) 16:44:22 phsmoura was working on this 16:44:33 phsmoura: can you update the ticket with the current status? 16:45:29 .ticket 10284 16:45:30 dtometzki: Issue #10284: Provide better metadata via meta tags for web applications we run - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10284 16:46:11 I am not sure how to do this. :) Let me update it and ping ryan out of band. 16:47:05 .ticket 10372 16:47:06 dtometzki: Issue #10372: [proposal] Move Pagure (pagure.io and src.fp.o) to use OIDC for web login - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10372 16:48:07 So, perhaps we should mark this blocked? since it needs ipsilon changes? and link to the ipsilon ticket? 16:48:16 what do you think zlopez 16:48:29 +1 16:48:59 Do you know what ipsilon ticket needs to be implemented, I will add it to lisk of highlighted tasks 16:49:03 zlopez: can you mark it? 16:49:06 let me see 16:49:38 https://pagure.io/ipsilon/issue/307 16:49:50 ^ this I think. It needs a scope per project 16:50:54 Thanks adding it 16:51:16 ok 16:51:19 .ticket 10845 16:51:50 dtometzki: Issue #10845: reply by email to Pagure issues bounce - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10845 16:51:50 zodbot ? 16:52:52 so, I started looking at this but got sidetracked. 16:53:01 I think it needs someone to investigate it more deeply. 16:53:32 can update the ticket asking if it's still happening and that we have it on our backlog 16:54:34 perfekt 16:55:00 .ticket 10878 16:55:01 dtometzki: Issue #10878: AWS: EKS IRSA for Route53-hosted zones - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10878 16:55:09 nirik: sorry, was having lunch. Sure Ill update it 16:55:57 the last ticket for today 16:56:41 There isn't even any response to this one 16:56:56 yes 16:56:59 I wasn't sure the answer here... I was leaving it for Mark at the time. 16:57:12 I guess I can try and investigate. 16:57:29 will update it. 16:57:40 I'm surprised we tagged it as low/low, when it's just lying there for 5 months 16:59:00 updated asking them if they still need it and saying we will try and investigate. 16:59:07 * nirik[m] notes we are out of time 16:59:11 so short info about the next learning topic. If anyone has a learning topic feel free 16:59:14 #topic Upcoming learning topics 16:59:14 #info 2023-02-16 Automating SCM Requests [mkonecny] 16:59:14 #info 2023-03-02 Installing vm's with ansible [nirik] 16:59:40 short minute for open flor 16:59:43 short minute for open floor 16:59:45 #topic Open Floor 17:01:21 when nothing more then many thanks for joining 17:01:29 Have nice day 17:01:32 #endmeeting