16:00:54 #startmeeting Infrastructure (2022-02-10) 16:00:54 Meeting started Thu Feb 10 16:00:54 2022 UTC. 16:00:54 This meeting is logged and archived in a public location. 16:00:54 The chair is dtometzki. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:54 The meeting name has been set to 'infrastructure_(2022-02-10)' 16:00:54 #meetingname infrastructure 16:00:54 The meeting name has been set to 'infrastructure' 16:00:54 #chair nirik siddharthvipul mobrien zlopez pingou bodanel dtometzki jnsamyak computerkid 16:00:54 #info Agenda is at: https://board.net/p/fedora-infra 16:00:54 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:00:54 Current chairs: bodanel computerkid dtometzki jnsamyak mobrien nirik pingou siddharthvipul zlopez 16:00:55 #topic greetings! 16:01:09 .hi 16:01:10 dtometzki: dtometzki 'Damian Tometzki' 16:01:11 .hi 16:01:13 mobrien: mobrien 'Mark O'Brien' 16:01:18 .hello zlopez 16:01:19 mkonecny: zlopez 'Michal Konecny' 16:01:43 .hi 16:01:44 phsmoura: phsmoura 'Pedro Moura' 16:01:48 .hello petebuffon 16:01:49 petebuffon: petebuffon 'Peter Buffon' 16:03:02 hello together :-) 16:03:06 morning 16:03:15 morning nirik 16:03:50 * nirik 🌊s 16:04:00 #topic New folks introductions 16:04:00 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:04:00 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:04:30 Any newcomers here ? 16:05:59 please say hello and give us a short intro 16:07:21 ok no one , let´s go to the next topic 16:07:32 #topic Next chair 16:07:32 #info magic eight ball says: 16:07:32 #info chair 2022-02-10 - dtometzki 16:07:32 #info chair 2022-02-17 - mkonecny 16:07:32 #info chair 2022-02-24 -petebuffon 16:08:08 Anyone for 2022-03-03 ? 16:08:48 come on :-) 16:09:01 If we don't have a volunteer I think 2 weeks ahead is good 16:09:17 ok then let us go forward 16:09:26 #topic announcements and information 16:09:26 #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:09:26 #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:09:26 #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:09:28 #info matrix sig is forming, see https://discussion.fedoraproject.org/t/bi-weekly-meeting-for-matrix-sig-or-matrix-team/35947/3 if interested 16:09:31 #info Mass rebuild for F36 finished 16:09:41 any new news to add ? 16:10:08 i think the mass rebuild we can remove or ? 16:10:16 #info branched (f36) composes running fine 16:10:18 dtometzki: yep. 16:10:31 #info rawhide composes (f37) waiting on signing to finish to resume. 16:11:23 thanks nirik 16:11:53 #info API breaking change in bugzilla will happen 28th February 16:12:11 yeah, we really need to get going on that, not much time. ;( 16:12:18 #info mass update/reboot next week 16:12:22 yeah 16:12:31 #info Red Hat recharge day next friday 16:13:02 thanks 16:13:18 #topic Oncall 16:13:18 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:13:18 #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/ 16:13:18 ## .oncalltakeeu .oncalltakeus 16:13:18 #info nirik on call from 2022-01-27 to 2022-02-03 16:13:19 #info mobrien on call from 2022-02-04 to 2022-02-10 16:13:21 #info dtometzki on call from 2022-02-11 to 2022-02-17 16:13:33 @nirik I already prepared the-new-hotness for it, but need new API key 16:13:36 oh I need to send the mail on those reboots.. 16:14:16 Anyone for the week from 2022-02-18 ? 16:15:20 I can take it 16:16:09 #info mkonecny on call from 2022-02-18 to 2022-02-24 16:16:23 great mkonecny thanks 16:17:18 #info Summary of last week: (from current oncall ) 16:17:27 I had a couple of pings 16:17:50 a short summary = 16:17:52 ? 16:17:55 Friday night there was an issue with mirrorlist which nirik fixed 16:18:11 Tuesday morning pagure was down, a httpd reload fixed it 16:18:38 There was also one earlier today about dns but was answered before I could respond 16:18:44 self solved 16:18:51 yes 16:19:09 ok 16:19:20 I noticed that the pagure prod instance is not in nagios 16:20:04 it actually is... it's just called pagure02.fedoraproject.org 16:20:24 but we aren't monitoring any specific pages or anything, just the normal disk space/etc... 16:21:06 I tried to filter services by name in nagios and it only found stg instance 16:21:53 its a good point to to the next topic 16:21:54 https://nagios.fedoraproject.org/nagios/cgi-bin//status.cgi?navbarsearch=1&host=pagure02 16:22:05 #topic Monitoring discussion [nirik] 16:22:05 #info https://nagios.fedoraproject.org/nagios 16:22:05 #info Go over existing out items and fix 16:22:32 nirik: Strange, not sure why I didn't found it :-/ 16:23:01 so, it's pretty much standard... the usual few arm boxes down, and misc other things... nothing too out of the ordinary. 16:23:13 So if you are searching for pagure, it doesn't find pagure02 :-D 16:23:22 I did make some changes to try and reduce alerts recently, might keep doing that... the alerts about low swap are kind of useless. 16:23:33 mkonecny: nice. ;( 16:24:02 For next time I need to search for pagure* :-) 16:24:04 we have some certs that are expiring soon... but I had to switch back to an old cert for a rawhide compose bug. ;( 16:24:36 mobrien: SSL WARNING - Certificate 'apps.ocp.fedoraproject.org' expires in 20 day(s) (2022-03-02 23:26 +0000/GMT). needs renewing 16:25:08 othewise pretty much as usual.... we cna move on unless folks have any questions. 16:25:26 any questions ? 16:25:27 I will update that cert 16:26:03 For today we have no learning topic 16:26:28 next week docs pipline 16:26:38 cool. 16:27:27 We can do backlog refinement then 16:27:32 yes 16:27:35 * nirik nods 16:27:35 #topic Fedora Infra backlog refinement 16:27:35 #info Refine oldest tickets on https://pagure.io/fedora-infrastructure/issues 16:28:04 .ticket 9691 16:28:05 mkonecny: Issue #9691: STG: Move vmguests from vmhost-x86-01/02/03 to vmhost-x86-11/12 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9691 16:28:31 still needs doing.... just haven't had a chance due to so many other things going on. 16:28:47 * nirik can update the ticket 16:29:00 perhaps we could do this next week when we do stg updates/reboots. 16:29:58 Oh yes, I went to do that before christmas but ran into firewall issues 16:30:01 Could phsmoura do this? 16:30:20 They have since been fixed but I haven't had time to get back to it 16:30:40 .tcket 9692 16:31:03 is in the same area 16:31:22 mkonecny: it needs perms and following the sop, but otherwise sure. 16:32:12 * nirik waits for that ticket... hello pagure? 16:32:12 He can at least shadow you :-) 16:32:28 definitely. 16:32:32 .ticket 5478 16:32:33 mkonecny: Issue #5478: Establishing a new FAS group for Python-SIG - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/5478 16:32:48 oh yeah, I never got back to this. It did get unblocked I think. 16:33:27 It seems like everything was solved, it was just forgotten 16:33:40 so far. ;) But there's blockers on many other things. 16:33:57 anyhow, I will try and just do this one too... it's the oldest open ticket we have I think. 16:34:06 mkonecny: sure, Id like to work on something new and learn more about fedora infra. Just need to talk to you guys what I should prioritize cause I started working in another issue and still stuck on it and I yes need perms 16:34:07 5 years. sheesh 16:35:16 It brings memories :-D 16:35:31 mkonecny, which order do you use in the list ? 16:35:59 Last modified date 1->9 16:36:23 It should be described in the agenda 16:36:55 9892 is next... 16:37:08 nirik: Do you want to comment on 5478? 16:37:26 yeah, I will do that. 16:37:48 Ok 16:37:51 .ticket 9892 16:37:52 mkonecny: Issue #9892: Centralise and update Fedora infra and releng SOPs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9892 16:38:26 Infrastructure documentation is already moved to docs.fedoraproject.org 16:38:33 we did move the infra stuff, but releng isn't right? 16:38:36 RelEng documentation is being migrated 16:38:51 @pbokoc is working on that 16:38:55 I will update the ticket 16:39:31 ah, ok. Are mboddu and jednorozec aware? :) 16:40:33 We were talking about this on planning meeting 16:40:55 At least jednorozec should be aware 16:41:21 Yeah, I heard about it, but jednorozec was more involved than me in that 16:41:27 ok. In any case I think it needs doing... ;) 16:41:56 I need to ping Petr 16:42:14 because there was bunch of updates to the SOPs in last few weeks 16:42:41 jednorozec: I pinged him around this two days ago and he replied that he is working on it 16:42:54 s/around/about/ 16:43:39 Anything else regarding this ticket? 16:43:40 mkonecny, that is fine, but we want to dropt some sops and update others 16:44:11 He will probably ping you as well 16:44:30 So next ticket 16:44:39 .ticket 8213 16:44:40 mkonecny: Issue #8213: fedmsg -> fedora-messaging migration tracker - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8213 16:45:04 datagrepper is done now right? 16:45:27 Let me check 16:45:38 but all the rest in the last comment are still to be done. ;( 16:46:49 It seems like the badges-backend is done as well 16:47:19 oh? when was that done? 16:47:21 Hm, the datagrepper still has fedmsg/base in playbook 16:47:54 Not sure, it's just not showing on the grep in playbooks/group 16:48:38 yeah, I guess datagrepper is still fedmsg. I thought it was changed, but I guess that was just the db... 16:48:47 Datagrepper is in openshift now so that playbook may be out of date 16:49:02 and badges-backend01 is still definitely fedmsg 16:49:13 Ok, badges-backend is still there, it's just not on the top 16:49:14 mobrien: oh right, we should nuke it then. 16:49:46 I see resultsdb as well, which is not on the list 16:50:00 We might want to confim with Aurélien B just to be 100% 16:50:10 yeah, thats moving to openshift really soon I hope. 16:50:14 I will reply to the ticket then 16:50:16 mobrien: yeah. 16:50:56 We skipped resultsdb on purpose on the list? 16:51:24 well at the time I think it wasn't clear if qa was going to keep running it or not... 16:51:27 datagrepper servers are commented out in the ansible inventory too 16:51:53 I see that it was marked as done in the past 16:51:56 leor is working on the openshift version... 16:52:36 ah it is using fedora-messaging 16:52:42 even the vm one thats live now. 16:53:02 so, resultsdb doesn't need to be on the list. 16:53:25 It has the fedmsg/base which just confused me 16:53:47 it shouldn't need it... 16:54:01 I see that it has both 16:54:27 it's only running fedora-messaging. 16:54:47 So it's just a leftover in the playbook 16:54:54 yeah. 16:55:13 I see that the datagrepper has rabbit/user role and fedmsg/base as well 16:55:59 Commented on the ticket 16:56:19 Hey folks! 16:56:30 huh, where do you see it for datagrepper? 16:56:33 Just finished a meeting, I can answer questions if needed 16:56:36 I would say that we can go to open floor now 16:56:54 abompard: datagrepper is fedora-messaging now right? 16:56:55 yep for the last 4 minutes 16:57:03 nirik: it is 16:57:09 #topic Open Floor 16:57:12 as well as datanommer 16:57:12 nirik: In playbooks/groups/datagrepper.yml 16:57:32 Let me update the comment 16:57:35 playbooks/groups/datagrepper is probably the old one, the new one is running in openshift 16:57:44 as well as datanommer 16:58:00 yeah, thats the old vm one, we need to clean it up. 16:59:16 I updated the ticket 16:59:41 We still have 16 services to migrate 17:00:10 :( 17:00:28 And I'm wondering why FMN isn't on the list 17:00:42 it is... its just called notifs there. 17:01:27 ok we have now 6:00 o´clock and i will close the meeting shortly. many thanks for joining 17:01:53 This is why I'm struggling to find it each time :-D 17:02:11 dtometzki: Thanks for running this :-) 17:02:17 yeah, no idea why it was called that... ;) 17:02:22 #endmeeting