16:00:03 <nirik> #startmeeting Infrastructure (2022-05-19)
16:00:03 <zodbot> Meeting started Thu May 19 16:00:03 2022 UTC.
16:00:03 <zodbot> This meeting is logged and archived in a public location.
16:00:03 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:03 <zodbot> The meeting name has been set to 'infrastructure_(2022-05-19)'
16:00:03 <nirik> #meetingname infrastructure
16:00:03 <zodbot> The meeting name has been set to 'infrastructure'
16:00:03 <nirik> #chair nirik siddharthvipul mobrien zlopez bodanel dtometzki jnsamyak computerkid
16:00:03 <nirik> #info Agenda is at: https://board.net/p/fedora-infra
16:00:03 <nirik> #info About our team: https://docs.fedoraproject.org/en-US/cpe/
16:00:03 <zodbot> Current chairs: bodanel computerkid dtometzki jnsamyak mobrien nirik siddharthvipul zlopez
16:00:04 <nirik> #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra
16:00:06 <nirik> #topic greetings!
16:00:36 <darknao> .hi
16:00:36 <zodbot> darknao: darknao 'Francois Andrieu' <darknao@drkn.ninja>
16:00:38 <eddiejennings> .hi
16:00:39 <zodbot> eddiejennings: eddiejennings 'Eddie Jennings' <eddie@eddiejennings.net>
16:00:40 <nirik> and so our story begins... what brave adventurers do we have in our party today?
16:01:00 <mkonecny> .hello zlopez
16:01:00 <zodbot> mkonecny: zlopez 'Michal Konecny' <michal.konecny@psmail.xyz>
16:02:51 <smooge> .here
16:03:26 <lenkaseg> .hi
16:03:27 <zodbot> lenkaseg: lenkaseg 'Lenka Segura' <lenka@sepu.cz>
16:03:29 <petebuffon> .hello petebuffon
16:03:30 <zodbot> petebuffon: petebuffon 'Peter Buffon' <pabuffon@gmail.com>
16:03:59 <lenkaseg> dot here is a thing? :)
16:04:08 <nirik> greetings everyone! lets start down the trail into the everdark forest. Keep to the path.
16:04:26 <nirik> #topic New folks introductions
16:04:26 <nirik> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
16:04:26 <nirik> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
16:04:39 <petebuffon> do we have a light?
16:04:52 <nirik> any new adverturers with us today? or are well are seasoned troops?
16:04:55 <mkonecny> I hope so
16:05:12 * nirik passes out a lantern and a bundle of torches.
16:05:29 * mkonecny lights up torch
16:05:55 <petebuffon> not new, but back after a few weeks of relentless coursework
16:05:56 <nirik> who shall leed our party in the future?
16:05:59 <nirik> #topic Next chair
16:05:59 <nirik> #info magic eight ball says:
16:05:59 <nirik> #info chair 2022-05-19 - nirik
16:05:59 <nirik> #info chair 2022-05-26 - mobrien
16:05:59 <nirik> #info chair 2022-06-02 - ?
16:06:01 <nirik> #info chair 2022-06-09 - ?
16:06:11 <eddiejennings> I haven't done any D&D since pandemic.  I sooo need to get back into a game :)
16:06:18 <nirik> anyone want to step forward for 06-02 or 06-09?
16:06:20 <eddiejennings> I can do 2022-06-02
16:06:27 <nirik> thanks eddiejennings.
16:07:13 <nirik> we walk down the path to the woods. Just before the trees there's a large board. On it it says:
16:07:16 <nirik> #topic announcements and information
16:07:17 <nirik> #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:07:17 <nirik> #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:07:17 <nirik> #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:07:18 <nirik> #info please help us with improving contribution to fedora infra https://discussion.fedoraproject.org/t/improving-contribution-to-fedora-infrastructure/38294/8
16:07:21 <nirik> #info oncall should also handling #fedora-releng pings if possible
16:07:41 <nirik> There's a pad of paper and a quill tied to the post. Anyone want to add anything ?
16:07:48 * austinpowered slips in quietly
16:08:03 <phsmoura> .hello
16:08:03 <zodbot> phsmoura: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:08:19 <austinpowered> .hi
16:08:20 <zodbot> austinpowered: austinpowered 'T.C. Williams' <fedoraproject@wootenwilliams.com>
16:08:35 <phsmoura> .hi
16:08:36 <zodbot> phsmoura: phsmoura 'Pedro Moura' <pmoura@redhat.com>
16:09:15 <nirik> pass some torches to those who just came in the back. ;)
16:10:06 <nirik> we walk into the dark and forbidding forest for a while, but then it comes to a clearing... standing there is the oncall person on a small hill...
16:10:08 <nirik> #topic Oncall
16:10:08 <nirik> #info https://fedoraproject.org/wiki/Infrastructure/Oncall
16:10:08 <nirik> #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/
16:10:08 <nirik> ## .oncalltakeeu .oncalltakeus
16:10:08 <nirik> #info mkonecny on call from 2022-05-13 to 2022-05-19
16:10:09 <nirik> #info eddiejennings on call from 2022-05-20 to 2022-05-26
16:10:11 <nirik> #info darknao on call from 2022-05-27 to 2022-06-02
16:10:13 <nirik> #info ? on call from 2022-06-03 to 2022-06-10
16:10:17 <nirik> anyone want to take that last oncall
16:10:17 <nirik> ?
16:10:34 <eddiejennings> .oncalltakeus
16:10:34 <zodbot> eddiejennings: 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:10:43 <eddiejennings> .whoami
16:10:43 <zodbot> eddiejennings: 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:11:03 <nirik> #info Summary of last week: (from current oncall )
16:11:18 <nirik> we ask mkonecny to tell us what happened this last week in the forest?
16:11:31 <eddiejennings> .oncalltakeus
16:11:31 <zodbot> eddiejennings: Kneel before zod!
16:12:39 <nirik> sadly he seems to have wandered into the woods. ;( Lets hope he finds his way back to the path
16:12:45 <mkonecny> I'm here
16:12:59 <nirik> ah, didn't see you back there
16:13:04 <mkonecny> There were few pings, but all of them outside my hours
16:13:46 <mkonecny> So I just found them later and they seemed to be already solved
16:13:59 <nirik> excellent.
16:14:34 <nirik> we head down the path, past a even darker area with spiderwebs hanging from the trees.
16:14:43 <nirik> lets stop here and listen
16:14:46 <nirik> #topic Monitoring discussion [nirik]
16:14:47 <nirik> #info https://nagios.fedoraproject.org/nagios
16:14:47 <nirik> #info Go over existing out items and fix
16:15:01 <nirik> so we had the mass update/reboot... and of course some things are now down.
16:15:38 <nirik> all those are fixable, just need to do it.
16:15:50 <nirik> we continue to hear badges alerts. ;(
16:16:08 <nirik> nothing else stands out.
16:16:42 <nirik> so, after listening for a few minutes, we all walk on.
16:17:01 <nirik> We get to a big pile of wood... it's all stacked hap hazardly.
16:17:13 <nirik> lets clean this up!
16:17:15 <nirik> #topic Fedora Infra backlog refinement
16:17:15 <nirik> #info Refine oldest tickets on Fedora Infra tracker
16:17:15 <nirik> #link https://pagure.io/fedora-infrastructure/issues?status=Open&order_key=last_updated&order=asc
16:17:38 <nirik> .ticket 5478
16:17:39 <zodbot> nirik: Issue #5478: Establishing a new FAS group for Python-SIG - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/5478
16:17:54 <nirik> this one is now ready to do, but I forgot about it. ;( can try and get it soon
16:17:58 * nirik adds to his todo list
16:18:32 <nirik> .ticket 9892
16:18:34 <zodbot> nirik: Issue #9892: Centralise and update Fedora infra and releng SOPs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9892
16:18:50 <nirik> what do we want to do with this one? infra is moved, but releng still needs to be?
16:19:08 <mkonecny> The releng still needs to be moved
16:19:29 <mkonecny> I need to contact pbokoc
16:19:44 <mkonecny> I will add it to my todo list
16:21:22 <nirik> ok.
16:21:33 <nirik> .ticket 8213
16:21:34 <zodbot> nirik: Issue #8213: fedmsg -> fedora-messaging migration tracker - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8213
16:22:25 <nirik> so, the list is likely a little smaller...
16:22:42 <mkonecny> I don't think there is any change
16:23:10 <nirik> yeah, perhaps you are right
16:23:44 <nirik> I mean some of them should go away when we retire those things...
16:23:45 <austinpowered> What is needed here? If I learned how to do one on the list would the rest be the same?
16:23:56 <nirik> or rewrite them
16:25:11 <mkonecny> austinpowered: It should be similar, but some of those apps weren't touched for long time
16:27:45 <nirik> it's not a trivial amount of work... ;(
16:27:55 <nirik> and many of these apps are old python2 stuff.
16:28:27 <nirik> perhaps we should just say we are never going to finish it? and just get them as the get re-written/retired?
16:28:38 <mkonecny> And we want to replace some of them
16:29:57 <mkonecny> FMN was already investigated by ARC, so this could be probably rewritten soon
16:30:03 <nirik> right
16:30:32 <mkonecny> About MBS, I know that MBS team has it on their TODO list
16:30:53 <x3mboy> .hello x3mboy
16:30:54 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
16:32:20 <nirik> and we are hoping to drop pdc someday
16:32:39 <mkonecny> Yes
16:33:15 <austinpowered> At first glance, 8213 doesn't appear to be just s/fedmsg/fedora-messaging/g
16:33:51 <nirik> it's not... they are very different systems
16:34:09 <austinpowered> At least the updated roles I looked at weren't done that way.
16:37:02 <nirik> so, I guess either a) we just keep this around to track and hope someday to focus on it, or b) close it and stop caring directly, but work to replace the old apps
16:38:09 <mkonecny> I would leave it for now
16:38:16 <nirik> ok
16:38:38 <nirik> .ticket 9691
16:38:39 <zodbot> nirik: 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:38:51 <nirik> mobrien: was gonna work on this, just I think it's been low pri...
16:40:01 <mobrien> yep, I started it and did some but then it got moved down my backlog again
16:40:23 <nirik> and now it would have been nice to put rhel9 on those before moving. oh well.
16:41:00 <mkonecny> We can update the ticket and just add this as note
16:41:33 <nirik> sure
16:41:56 <nirik> .ticket 10514
16:41:58 <zodbot> nirik: Issue #10514: Retire nodejs-sig group - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10514
16:42:43 <nirik> this needs more investigation i guess... see what would removing the group mean.
16:43:27 * smooge feels like everytime someone says 'we are hoping to drop pdc someday' they need to put a quarter in a jar for the party when it finally happens
16:43:32 <nirik> perhaps this is more a releng thing... we could see if jednorozec would be interested
16:43:44 <nirik> smooge: indeed
16:44:49 <jednorozec> I can look into that
16:45:04 * jednorozec lost his naivity about dropping PDC
16:45:23 <nirik> hey. thanks!
16:46:27 <nirik> .ticket 9940
16:46:29 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information.
16:46:37 <nirik> .ticket 9944
16:46:38 <zodbot> nirik: Issue #9944: Generate AWS images for ELN composes - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9944
16:46:50 <nirik> so, cloud sig is working on a fedimg replacement...
16:46:58 <nirik> in the mean time we just have fedimg. ;(
16:48:22 <nirik> so, I guess this is just waiting for anyone to look into it.
16:48:54 * mkonecny updating tickets as we go through them
16:49:43 <nirik> thanks for that.
16:49:58 <nirik> .ticket 10577
16:50:00 <zodbot> nirik: Issue #10577: get backups working on db-datanommer02 and retire db-datanommer01 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10577
16:50:15 <nirik> I am even a bit more confused after the outage yesterday.
16:50:29 <nirik> I see some things like busgateway connecting to db-datanommer01...
16:50:43 <nirik> so I am not sure if we really cleaned up things fully.
16:50:57 <nirik> I need to drop abompard an email and see what the status is.
16:52:43 <nirik> shall we walk out of the forest on the far side back into the sun now?
16:53:27 <smooge> sounds good
16:53:46 <mkonecny> Yes
16:54:20 <nirik> we escape the darkness of the trees and walk into a big clearing. The ground has been packed down from years of feet, it's a...
16:54:23 <nirik> #topic Open floor
16:54:39 <nirik> anyone have anything they would like to bring up?
16:55:29 <mkonecny> I have one thing
16:55:32 <eddiejennings> I will *try* to be ready for the learning topic next week.  New job has me touching RHEL, which is great, but I have to be on-prem 3 days a week, so that's 9 hours of commute time :(
16:55:48 <nirik> mkonecny: go ahead
16:55:50 <nirik> eddiejennings: :(
16:55:56 <mkonecny> I recently moved hotness to OCP4 and want to deploy redis there
16:56:27 <mkonecny> The OCP4 should have redis operator, but I'm unable to setup it with current permissions
16:57:16 <mkonecny> But my question is, will the operator be a good way to deploy it? Or it is better to have the deployment in ansible
16:57:40 <mkonecny> Or could we move the redis deployed by operator to ansible?
16:58:17 <nirik> good questions... hum.
16:58:51 <nirik> could you make a list thread on it? I am not sure what answer to give off the top of my head, would want to consider it a bit...
17:00:49 <mkonecny> Yes, I can sent it to mailing thread
17:01:35 <nirik> on the one hand it should be in ansible for reproducability.
17:01:43 <nirik> but the operator is likely much easier to do
17:02:07 <nirik> ok, we are over time. thanks for adventuring with us!
17:02:10 <nirik> #endmeeting