16:01:05 <dtometzki> #startmeeting Infrastructure (2022-12-08)
16:01:05 <zodbot> Meeting started Thu Dec  8 16:01:05 2022 UTC.
16:01:05 <zodbot> This meeting is logged and archived in a public location.
16:01:05 <zodbot> The chair is dtometzki. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:01:05 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:05 <zodbot> The meeting name has been set to 'infrastructure_(2022-12-08)'
16:01:05 <dtometzki> #meetingname infrastructure
16:01:05 <zodbot> The meeting name has been set to 'infrastructure'
16:01:05 <dtometzki> #chair nirik zlopez nb bodanel dtometzki jnsamyak
16:01:05 <dtometzki> #info Agenda is at: https://board.net/p/fedora-infra
16:01:05 <dtometzki> #info About our team: https://docs.fedoraproject.org/en-US/cpe/
16:01:05 <zodbot> Current chairs: bodanel dtometzki jnsamyak nb nirik zlopez
16:01:05 <dtometzki> #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra
16:01:07 <dtometzki> #topic greetings!
16:01:14 <zlopez> .hello
16:01:14 <zodbot> zlopez: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:01:19 <zlopez> .hi
16:01:20 <zodbot> zlopez: zlopez 'Michal Konecny' <michal.konecny@pacse.eu>
16:01:20 <nirik> good morning everyone.
16:01:25 <eddiejenningsjr> .hello eddiejennings
16:01:26 <zodbot> eddiejenningsjr: eddiejennings 'Eddie Jennings' <eddie@eddiejennings.net>
16:01:38 <dtometzki> .hi
16:01:39 <zodbot> dtometzki: dtometzki 'Damian Tometzki' <linux@tometzki.de>
16:01:47 <smooge> hello
16:02:27 <dtometzki> hello together
16:03:14 <dtometzki> let us start with the first topic
16:03:18 <dtometzki> #topic New folks introductions
16:03:18 <dtometzki> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
16:03:19 <dtometzki> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
16:03:34 <dtometzki> Every new people say hello ?
16:05:46 <dtometzki> Ok no one new here
16:06:16 <dtometzki> #topic Next chair
16:06:16 <dtometzki> #info magic eight ball says:
16:06:16 <dtometzki> #info chair 2022-12-08 - dtometzki
16:06:16 <dtometzki> #info chair 2022-12-15 - ??
16:06:16 <dtometzki> #info chair 2022-12-22 - no meeting / holidays
16:06:16 <dtometzki> #info chair 2022-12-29 - no meeting / holidays
16:06:18 <dtometzki> #info chair 2023-01-05 - ??
16:06:31 <dtometzki> anyone available for next week ?
16:07:02 <eddiejenningsjr> I can chair next week, but have an onboarding meeting for new job at the same time, so I'll either be a bit late, or will nee someone to start the meeting for me
16:07:27 <eddiejenningsjr> need*
16:07:29 * nirik is going to actually be out both the 15th and the 5th.
16:07:49 <nirik> we could cancel one or both of those two if folks prefer.
16:08:29 <dtometzki> what are the meaning of other ?
16:08:30 <zlopez> I'm not sure if I will be here next week, but I will definitely miss the 5th
16:08:37 <dtometzki> for me ok too
16:08:58 <eddiejenningsjr> I suspect I'll be around for them all :P
16:09:21 <nirik> That would make the next meeting the 12th
16:09:38 <dtometzki> on 15 and 01.05 maybe
16:09:40 <nirik> so, whatever folks want to do.
16:10:25 <eddiejenningsjr> If it's ok to take a month off, I say we start fresh on January 12th
16:10:37 <dtometzki> ok
16:10:46 <dtometzki> +1
16:11:06 <nirik> sure.
16:11:17 <dtometzki> others ?
16:11:18 <nirik> anyone want to sign up to run the meeting on the 12th?
16:11:51 <eddiejenningsjr> I'll do it. :D
16:11:51 <dtometzki> i cant my wife hhas birthday
16:12:32 <dtometzki> #info chair 2022-12-15 - no meeting
16:12:52 <dtometzki> #info chair 2023-01-05 - no meeting
16:13:08 <dtometzki> #info chair 2023-01-12 - eddiejenningsjr
16:13:20 <dtometzki> great and thanks to eddiejenningsjr
16:14:00 <dtometzki> perhaps we have anyone for 01-19 ?
16:14:27 <dtometzki> #info chair 2023-01-19 - dtometzki
16:14:37 <dtometzki> ok i will take it :-)
16:14:47 <dtometzki> #topic announcements and information
16:14:47 <dtometzki> #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:14:47 <dtometzki> #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:14:47 <dtometzki> #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:14:47 <nirik> thanks dtometzki and eddiejenningsjr!
16:14:48 <dtometzki> #info oncall should also handling #fedora-releng pings if possible
16:14:50 <dtometzki> #info New design of Anitya available to try on https://stg.release-monitoring.org
16:15:08 <dtometzki> next topic any add. news ?
16:15:19 <zlopez> #info SCM Request Automation will be deployed 10th January
16:15:35 <nirik> #info tomorrow is a Red Hat day of learning - many rh'ers will be away learning something
16:15:53 <nirik> #info nirik out on PTO after tomorrow until jan 9th. ;)
16:16:02 <nirik> I'll be around for emergencies and such...
16:16:18 <dtometzki> for what stand PTO ?
16:16:44 <zlopez> Paid Time Off
16:17:09 <nirik> vacation basically.
16:18:23 <dtometzki> ok thanks
16:19:07 <dtometzki> when no more infos then lets go to the next topic
16:19:12 <dtometzki> #topic Oncall
16:19:12 <dtometzki> #info https://fedoraproject.org/wiki/Infrastructure/Oncall
16:19:12 <dtometzki> #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/
16:19:12 <dtometzki> ## .oncalltakeeu .oncalltakeus
16:19:27 <dtometzki> #info  phsmoura is on call from 2022-12-02 to 2022-12-08 -> didnt receive any pings
16:19:27 <dtometzki> #info ? is on call from 2022-12-08 to 2022-12-15
16:19:28 <dtometzki> #info ? is on call from 2022-12-15 to 2022-12-22
16:19:28 <dtometzki> #info ? is on call from 2022-12-22 to 2022-12-29
16:19:52 <eddiejenningsjr> I'll take this week.
16:19:55 <dtometzki> phsmoura, it isnt available because it was in the agenda
16:20:11 <nirik> so, what we typically do over the holidays is have no one on call...
16:20:12 <jednorozec> I can take the one before holidays
16:20:39 <dtometzki> #info eddiejenningsjr is on call from 2022-12-08 to 2022-12-15
16:20:40 <zlopez> nirik: +1
16:20:45 <eddiejenningsjr> and I'll take 2023-01-05 to 2021-01-12
16:21:06 <dtometzki> jednorozec, you are are from 12-15 to 12-22
16:21:13 <dtometzki> ?
16:21:14 <jednorozec> ack
16:21:27 <nirik> then 22-05 we can set it to just tell people to file a ticket.
16:22:17 <eddiejenningsjr> Sounds good
16:22:17 <dtometzki> #info jednorozec is on call from 2022-12-15 to 2022-12-22
16:22:27 <smooge> #info there will be a short network outage with IAD2 (ventral Fedora servers) on 2022-12-13
16:22:32 <smooge> 1900 UTC
16:22:51 <eddiejenningsjr> .oncalltakeus
16:22:51 <zodbot> eddiejenningsjr: 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:22:56 <dtometzki> #info eddiejenningsjr  is on call from 2023-01-05 to 2023-01-12
16:23:01 <eddiejenningsjr> .whoami
16:23:01 <zodbot> eddiejenningsjr: I don't recognize you. You can message me either of these two commands: "user identify <username> <password>" to log in or "user register <username> <password>" to register.
16:23:16 <nirik> eddiejenningsjr: register a user and I can add alias.add to it.
16:23:43 <eddiejenningsjr> Yeah.  This usually happens when I'm using Matrix.  Let me talk to Zod for amoment
16:24:50 <eddiejenningsjr> .whoami
16:24:50 <zodbot> eddiejenningsjr: eddiejennings
16:24:54 <eddiejenningsjr> .oncalltakeus
16:24:54 <zodbot> eddiejenningsjr: Kneel before zod!
16:25:41 <dtometzki> Hallo Phil,
16:25:55 <dtometzki> sorry wrong window
16:26:19 <dtometzki> #topic Monitoring discussion [nirik]
16:26:19 <dtometzki> #info https://nagios.fedoraproject.org/nagios
16:26:19 <dtometzki> #info Go over existing out items and fix
16:26:28 <dtometzki> nirik, your part ?
16:26:29 <nirik> ok, lets see...
16:26:51 <nirik> nothing down (hurray)...
16:27:03 <dtometzki> ok thanks
16:27:20 <dtometzki> so then
16:27:24 <dtometzki> #topic Revisit blocked tickets
16:27:24 <dtometzki> #info Check if any blocked ticket is unblocked
16:27:24 <dtometzki> #link https://pagure.io/fedora-infrastructure/issues?status=Open&tags=blocked&priority=0&close_status=
16:27:58 <nirik> nothing changed here, all those are still blocked.
16:28:00 <dtometzki> i see 4 tickets
16:30:07 <dtometzki> So what we wil do now
16:30:10 <nirik> I'd say we move on, unless someone has info on them I don't know.
16:30:41 <dtometzki> one open learning topic zabbix nirik ?
16:31:15 <nirik> I've not gotten anything ready on that yet. Perhaps after the holidays.
16:31:24 <dtometzki> ok
16:31:34 <nirik> I could pontificate on some other learning topic I know well perhaps.
16:31:52 <nirik> or we could close early.
16:32:04 <dtometzki> Or backlog ?
16:32:11 <nirik> or backlog yeah...
16:32:17 <dtometzki> what are the meaning ?
16:32:23 <nirik> votes anyone/? or topic ideas?
16:32:57 <nirik> 1) some learning topic from nirik, 2) end early, or 3) do backlog
16:33:12 <zlopez> I'm for 3)
16:33:22 <eddiejenningsjr> I do have a question about a backlog ticket :)
16:33:37 <nirik> fine with me.
16:33:47 <dtometzki> ok then lets do it
16:34:08 <dtometzki> #topic Fedora Infra backlog refinement
16:34:08 <dtometzki> #info Refine oldest tickets on Fedora Infra tracker
16:34:08 <dtometzki> #link https://pagure.io/fedora-infrastructure/issues?status=Open&order_key=last_updated&order=asc
16:34:36 <dtometzki> .ticket 10358
16:34:37 <zodbot> dtometzki: Issue #10358: IPA backup fails on ipa03 and ipa02.stg - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10358
16:35:20 <zlopez> IT seems that this was at least partially solved
16:35:56 <nirik> no, i think it's still broken?
16:35:59 <nirik> but let me check
16:36:42 <zlopez> From what you wrote last time, it seems that only ipa03 is now problem
16:37:10 <nirik> yeah, thats still the case... 03 still has it.
16:37:27 <nirik> I do plan to move the ipa cluster to rhel9 after the holidays. perhaps that will fix it?
16:37:53 <zlopez> We'll see
16:38:25 <nirik> the way you upgrade a cluster is add a new server thats rhel9, let it sync then replace the others one by one...
16:38:45 <eddiejenningsjr> I'd like to tag along / watch the movement of said cluster.  I will likely be using IPA in new job :D
16:38:49 <zlopez> Commented on the ticket
16:39:02 <nirik> sure.
16:39:25 <dtometzki> good
16:39:28 <dtometzki> .ticket 8455
16:39:29 <zodbot> dtometzki: Issue #8455: Move mailman to newer release of Fedora or CentOS - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8455
16:40:04 <zlopez> This is tagged as blocked
16:40:13 <nirik> yeah, although...
16:40:41 <dtometzki> .ticket 10426
16:40:42 <zodbot> 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:45 <nirik> no, it's still broken. I was thinking it had been fixed.
16:41:28 <nirik> on this one I think no one has had time to look.
16:41:56 <zlopez> It seems like it
16:42:52 <zlopez> ngompa said it should be packaged in Fedora, not sure if it is yet
16:43:55 <nirik> don't see it, but we should be able to deploy to openshift
16:44:39 <zlopez> We can
16:44:53 <nirik> so someone could deploy to communishift and get it working, then stg -> prod...
16:45:28 <zlopez> Wouldn't it be enough to just give them namespace in staging, so they can start deploying there
16:46:15 <nirik> no, because we deploy to stg with playbooks. I mean sure, you could just set it up in ansible, but thats a higher learning curve
16:46:39 <zlopez> Ok
16:47:33 <dtometzki> .ticket 8167
16:47:34 <zodbot> dtometzki: Issue #8167: Adding topic authorization to our RabbitMQ instances - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8167
16:47:40 <zlopez> nirik: And it's usually trial and error till you get it right
16:47:58 * nirik nods
16:48:17 <nirik> so, on this one abompard was working on it and set a number of them... but I don't think it was finished yet
16:48:45 <dtometzki> ok
16:48:56 <dtometzki> .ticket 10386
16:48:57 <zodbot> dtometzki: Issue #10386: Investigate moving registry.fp.o to quay.io - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10386
16:49:34 <zlopez> mobrien started looking into that, but didn't finished the investigation
16:49:54 <nirik> yeah.
16:49:56 <zlopez> And he is now working in other team
16:50:30 <nirik> so another one for the new year. ;)
16:50:42 <zlopez> Probably
16:51:25 <eddiejenningsjr> What's the general appetite for moving something outside the direct control of Fedora project and Fedora Infra?
16:51:30 <dtometzki> what we will do ?
16:51:45 <nirik> as with many things in life.. it depends. :)
16:51:57 <dtometzki> :-)
16:52:07 <nirik> I think we want to do this, just need to get cycles to look more into it and start moving.
16:52:23 <dtometzki> ok
16:52:28 <nirik> in this case quay.io is run by red hat, so we are not moving far.
16:52:41 <eddiejenningsjr> Ah, yes.  You're right.
16:53:02 <dtometzki> ok then let us go to the last one for today
16:53:15 <dtometzki> .ticket 10383
16:53:17 <zodbot> dtometzki: Issue #10383: Upgrade Venus to Pluto - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10383
16:53:35 <nirik> this one phsmoura had made progress on.
16:53:52 <nirik> he had a docker container with a setup showing it... but I haven't had the time to run it and look yet. ;(
16:54:16 <dtometzki> ok but good
16:54:42 <dtometzki> let us stop here and we go to
16:54:47 <dtometzki> #topic Open Floor
16:55:07 <dtometzki> any other points to discuss ?
16:55:25 <zlopez> Warning: Floor is a hot lava!
16:56:11 <eddiejenningsjr> <-- waiting for Fedex to supposedly deliver a package in the next 5 minutes. :(
16:56:32 <dtometzki> so no then many thanks for joining and have a nice day or evening
16:56:36 * zlopez is trying to not touch the floor
16:56:42 <dtometzki> #endmeeting