16:04:01 <eddiejenningsjr> #startmeeting Infrastructure (2023-02-16)
16:04:01 <zodbot> Meeting started Thu Feb 16 16:04:01 2023 UTC.
16:04:01 <zodbot> This meeting is logged and archived in a public location.
16:04:01 <zodbot> The chair is eddiejenningsjr. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:04:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:04:01 <zodbot> The meeting name has been set to 'infrastructure_(2023-02-16)'
16:04:01 <eddiejenningsjr> #meetingname infrastructure
16:04:01 <eddiejenningsjr> #chair nirik zlopez nb bodanel dtometzki jnsamyak
16:04:01 <zodbot> The meeting name has been set to 'infrastructure'
16:04:01 <zodbot> Current chairs: bodanel dtometzki eddiejenningsjr jnsamyak nb nirik zlopez
16:04:01 <eddiejenningsjr> #info Agenda is at: https://board.net/p/fedora-infra
16:04:01 <eddiejenningsjr> #info About our team: https://docs.fedoraproject.org/en-US/cpe/
16:04:02 <eddiejenningsjr> #info Fedora Infra documentation: https://docs.fedoraproject.org/en-US/infra
16:04:02 <eddiejenningsjr> #topic greetings!
16:04:36 <eddiejenningsjr> zlopez: I am.  I just got here :(
16:04:39 <Penguinpee> .hello gui1ty
16:04:40 <zodbot> Penguinpee: gui1ty 'Sandro .' <gui1ty@penguinpee.nl>
16:04:47 <eddiejenningsjr> #topic New folks introductions
16:04:47 <eddiejenningsjr> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
16:04:47 <eddiejenningsjr> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
16:04:55 <nirik> morning everyone
16:05:03 <jednorozec> hello
16:05:12 <eddiejenningsjr> Ok.  <phew>  Again, my apologies for being late, and greetings all!
16:05:21 <mkonecny> Now we know :-D
16:05:27 <Penguinpee> good morning|day|afternoon|evening
16:05:39 <eddiejenningsjr> Do we have any new folks with us today?  If so, make yourself be known and tell us a little about yourself.
16:05:44 <phsmoura> .hi
16:05:45 <zodbot> phsmoura: phsmoura 'Pedro Moura' <pmoura@redhat.com>
16:06:01 <darknao> .hi
16:06:02 <zodbot> darknao: darknao 'Francois Andrieu' <darknao@drkn.ninja>
16:06:38 <eddiejenningsjr> I remember seeing someone new from the Infra mailing list.  Not sure if they're with us at the meeting today.
16:07:42 <eddiejenningsjr> Hearing none, let us move along. :)
16:07:46 <eddiejenningsjr> #topic Next chair
16:07:46 <eddiejenningsjr> #info magic eight ball says:
16:07:46 <eddiejenningsjr> #info chair 2023-02-16 - eddiejennings
16:07:46 <eddiejenningsjr> #info chair 2023-02-23 - ???
16:07:46 <eddiejenningsjr> #info chair 2023-03-02 - ???
16:08:27 <eddiejenningsjr> I encourage everyone to consider chairing a meeting.  It's a fun way to be involved with Fedora Infra.  If I can do it, anyone can :D
16:08:46 <Penguinpee> I believe that list has not been updated. There were takers last meeting.
16:09:07 <jasonbraganza> i’d volunteered for the 3rd
16:09:09 <eddiejenningsjr> I see.  Board.net has lied to me!
16:09:20 <eddiejenningsjr> re-sold to jasonbraganza
16:09:28 <jasonbraganza> XD
16:09:35 <eddiejenningsjr> #info chair 2023-03-02 - jasonbraganza
16:09:37 <nirik> We should perhaps make it clear who is updating the thing... ie, is it the chair, or the person willing to take the thing? ;)
16:09:46 <jasonbraganza> oh!
16:09:57 <eddiejenningsjr> When I chair, I usually update board.net as the meeting goes along.
16:10:55 <Penguinpee> Yeah. I think the chair should do that.
16:11:06 <eddiejenningsjr> Do we remember who the volunteer was for next week (2023-02-23)?
16:11:30 <eddiejenningsjr> I agree on current chair updating board.net during the meeting they chair.  Since, if they're like me, they're following board.net as they go through the meeting.
16:11:33 <Penguinpee> I don't but it's in the log for sure.
16:11:42 * Penguinpee is going to look it up
16:12:44 <eddiejenningsjr> Thanks Penguinpee .  We'll come back to it after the log search.
16:12:57 <mkonecny> Looking at the logs
16:13:09 <mkonecny> It was me :-D
16:13:11 <eddiejenningsjr> sold to zlopez!
16:13:20 <mkonecny> I have it in my own TODO
16:13:20 <Penguinpee> Confirmed!
16:13:36 <eddiejenningsjr> #info chair 2023-02-23 - zlopez
16:14:36 <eddiejenningsjr> We're covered for the next two weeks.  So that should be fine.  Be thinking about if you want to be the chair for 2023-03-09.  The seat is quite comfortable :D
16:15:23 <Penguinpee> If you keep it warm I'll take it! ;)
16:15:56 <eddiejenningsjr> Sold to Penguinpee !
16:16:20 <eddiejenningsjr> #info chair 2023-03-09 - penguinpee
16:16:41 <eddiejenningsjr> And with that, let's move on to announcements :)
16:16:55 <eddiejenningsjr> #topic announcements and information
16:16:55 <eddiejenningsjr> #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:16:55 <eddiejenningsjr> #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:16:55 <eddiejenningsjr> #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:16:55 <eddiejenningsjr> #info oncall should also handling #fedora-releng pings if possible
16:17:15 <eddiejenningsjr> Are there any new announcements?
16:17:58 <nirik> #info tomorrow is a 'day of learning' at Red Hat. Many folks will be off learning something.
16:18:14 <nirik> #info next tuesday starts Fedora 38 beta freeze.
16:19:30 <eddiejenningsjr> I have a client with F35 servers,  I've been working for 3 months to try to get them upgraded :(
16:20:03 <nirik> Maintaining things is always harder than deploying them in the first place. ;)
16:20:19 <eddiejenningsjr> Yep. ;)
16:20:22 * mkonecny agree
16:20:25 <eddiejenningsjr> Any other announcements?
16:20:31 <igorjagec> tell me about it :D
16:21:39 <eddiejenningsjr> Hearing none, let's move to everyone's favorite. . .
16:21:42 <eddiejenningsjr> #topic Oncall
16:21:42 <eddiejenningsjr> #info https://fedoraproject.org/wiki/Infrastructure/Oncall
16:21:42 <eddiejenningsjr> #info https://docs.fedoraproject.org/en-US/cpe/day_to_day_fedora/
16:21:42 <eddiejenningsjr> ## .oncalltakeeu .oncalltakeus
16:21:42 <eddiejenningsjr> #info mkonecny is on call from 2023-02-09 to 2023-02-16
16:21:42 <eddiejenningsjr> #info ??? is on call from 2023-02-17 to 2023-02-23
16:21:42 <eddiejenningsjr> #info ??? is on call from 2023-02-23 to 2023-03-02
16:22:08 <jednorozec> I can be on call this week
16:22:12 <eddiejenningsjr> I am going out of town for a few days starting tomorrow, so I cannot take this next week
16:22:23 <jednorozec> .oncalltakeeu
16:22:23 <zodbot> jednorozec: 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:30 <eddiejenningsjr> sold to jednorozec
16:22:46 <eddiejenningsjr> #info ?jednorozec is on call from 2023-02-17 to 2023-02-23
16:22:59 <jednorozec> .oncalltakeeu
16:22:59 <zodbot> jednorozec: Kneel before zod!
16:23:08 <nirik> I can take the one after if no one else wants it.
16:24:01 <eddiejenningsjr> sold to nirik and, I'll take the one after, so we're set for a while
16:24:51 <eddiejenningsjr> #info nirik is on call from 2023-02-23 to 2023-03-02
16:24:51 <eddiejenningsjr> #info eddiejennings is on call from 2023-03-02 to 2023-03-09
16:25:55 <eddiejenningsjr> For those interested, on-call is another way to contribute to Fedora Infra.  It's a way to be triage for sysadmin-main folks, so they're not pinged all the time.  Even if you're not able to affect a fix, you can direct the petitioner to submit a ticket.
16:26:21 <nirik> yep. It's another nice way to help out. :)
16:26:45 <eddiejenningsjr> Speaking of, it's time for . . .
16:26:46 <eddiejenningsjr> #info Summary of last week: (from current oncall )
16:26:48 <jasonbraganza> can i assist someone whos is on call to get the lay of the land first? (not this week, but the week after thatt)
16:27:13 <mkonecny> It was a quiet week, I didn't got any ping
16:28:28 <eddiejenningsjr> jasonbraganza: Sure.  Probably the best way is to just keep an eye on the fedora-infra fedora-noc,and fedora-releng chats and see how the current on-call responds to things.
16:28:43 <jasonbraganza> thank you eddiejenningsjr, i’ll do that.
16:28:52 <eddiejenningsjr> and reference this doc:  https://fedoraproject.org/wiki/Infrastructure/Oncall
16:29:25 <eddiejenningsjr> And great news Zlopez.  Glad your week was quiet :)
16:29:27 <jasonbraganza> am reading those docs slowly. thank you eddiejenningsjr.
16:30:22 <eddiejenningsjr> According to the board, we have
16:30:22 <eddiejenningsjr> #info 2023-02-16 Automating SCM Requests [mkonecny]
16:30:22 <eddiejenningsjr> Will we have the learning topic today?
16:30:35 <mkonecny> Yes
16:30:41 <mkonecny> I can start
16:31:33 <eddiejenningsjr> Take it away :D
16:31:59 <mkonecny> Ok, so let's start
16:32:04 <mkonecny> This topic will be about the automation of SCM requests
16:32:27 <mkonecny> For those who don't know the SCM is acronym for Source Content Management
16:33:04 <mkonecny> Basically those are requests for new repositories or branches for packages
16:33:37 <mkonecny> Till recently this was done manually by releng folks
16:34:39 <mkonecny> We automated it by creating a new toddler handling specific messages in Fedora infra
16:35:23 <mkonecny> I will not go in detail about what toddlers are, but we are using them to automate various things in Fedora Infra
16:35:41 <mkonecny> You can find them here https://pagure.io/fedora-infra/toddlers
16:37:04 <mkonecny> The toddler handling the SCM request is named scm_request_processor and you can find this specific toddler here https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/scm_request_processor.py
16:37:45 <mkonecny> The documentation for it is here https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
16:38:09 <mkonecny> And I prepared a nice diagram to describe how it works https://pagure.io/fedora-infra/toddlers/blob/main/f/docs/scm_request_processor.png
16:38:55 <mkonecny> Feel free to ask any question during the learning topic
16:39:08 <mkonecny> So now for how it works
16:39:35 <mkonecny> It waits for a new issue to be opened in https://pagure.io/releng/fedora-scm-requests/issues
16:40:14 <mkonecny> It parses the JSON in the first post of the issue and validates it
16:41:56 <mkonecny> Then it will check if the request is valid (has valid bugzilla ticket, the package branch doesn't exist in mdapi and PDC (it creates it) and validates if the user is a valid user to make this requets)
16:42:32 <Penguinpee> Wow, these are some extensive flow charts...
16:43:15 <mkonecny> If everything is OK, it will create the requested repo/branch, updates PDC and let the user know that everything is done
16:43:23 <mkonecny> In case something is not OK, it will let the user know as well
16:44:23 <mkonecny> The third option is that it asks maintainers of fedora-scm-requests repository to validate the requests, but this doesn't happen that often and they just need to respond that it's valid in the ticket
16:45:11 <mkonecny> Penguinpee: Thanks I used them to map the functionality of the original script used by releng, so the scm_request_processor is doing the same
16:45:41 <mkonecny> We already have few tickets on toddlers for enhancements for scm_request_processor
16:46:40 <nirik> long ago in the dark ages... it was just a simple script that the person running it had to check everything manually before running it. ;) Then we got a better script that did a bunch of the checks... then... this processor. :)
16:47:09 <mkonecny> It's evolution :-)
16:47:45 <Penguinpee> "It's evolution" <-- Where would we be without it...
16:47:47 <mkonecny> Before deploying to production we tried to test most of the cases on staging, but the start in production was rough anyway
16:48:38 <mkonecny> We missed a bunch of tokens with correct permissions and it took two days to figure everything out
16:48:57 <mkonecny> Till then there were only a few issues
16:49:41 <mkonecny> The most troubling one is that if some of the services are unavailable, the data end up in inconsistent state
16:50:00 <mkonecny> Like PDC has the info, but the package is not created yet
16:50:20 <mkonecny> There is already a ticket with possible solution for that
16:50:42 <mkonecny> https://pagure.io/fedora-infra/toddlers/issue/150
16:50:43 <nirik> (and ideally we could kill pdc someday)
16:51:10 <mkonecny> Hopefully :-)
16:51:28 <mkonecny> So next time you will request anything through fedpkg, it will be processed by this bot
16:51:39 <mkonecny> Be kind to him :-)
16:51:53 <mkonecny> Any questions?
16:53:14 <eddiejenningsjr> Right now, no, but after I dig through the links, I might :)
16:53:47 <mkonecny> Feel free to ask, I'm always around somewhere, just ping me
16:54:22 <Penguinpee> Same here. Need to process the information first. But thanks for the learning topic.
16:55:25 <mkonecny> The toddlers are interesting thing, the only issue is that they are Fedora specific and not really usable outside
16:56:24 <eddiejenningsjr> Thank you for the information zlopez !  Let's move to
16:56:24 <eddiejenningsjr> #topic Open Floor
16:56:41 <eddiejenningsjr> Any other questions or topics top of mind before we close out the meeting?
16:56:42 <Penguinpee> That begs the questions if this could not be done with generic tools.
16:57:11 <mkonecny> Penguinpee: I wasn't the one who designed them, so I'm not sure
16:57:32 <Penguinpee> I don't have anything for open floor.
16:57:37 <mkonecny> Even with generic tools we would still need to integrate them with Fedora messaging for our purpose
16:58:19 <Penguinpee> True. But you could lean on the experience of others.
16:58:24 <mkonecny> But the toddlers are not that complex and the concept itself is usable in other places
16:59:04 <Penguinpee> I will take a good look at toddlers. If nothing else, I like the name. 👶
16:59:24 <mkonecny> The name was stroke of genius :-D
17:00:05 <mkonecny> nirik: When you will have time, just look at https://src.fedoraproject.org/rpms/fedmsg/pull-request/7
17:00:24 <mkonecny> I was able to make some progress, but I would like answer to some questions
17:00:45 <eddiejenningsjr> And with that we've reach the top of the hour.  Thank you everyone for attending and for zlopez with the learning topic!
17:01:10 <Penguinpee> And thanks to eddiejenningsjr for chairing!
17:01:14 <mkonecny> Glad to share my knowledge :-)
17:01:14 <eddiejenningsjr> #endmeeting