2024-05-28 16:01:37 <@jnsamyak:matrix.org> !startmeeting RELENG (2024-05-28)
2024-05-28 16:01:41 <@meetbot:fedora.im> Meeting started at 2024-05-28 16:01:37 UTC
2024-05-28 16:01:41 <@meetbot:fedora.im> The Meeting name is 'RELENG (2024-05-28)'
2024-05-28 16:01:46 <@jnsamyak:matrix.org> !meetingname releng
2024-05-28 16:01:47 <@meetbot:fedora.im> The Meeting Name is now releng
2024-05-28 16:01:52 <@jnsamyak:matrix.org> !chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec jnsamyak patrikp
2024-05-28 16:02:04 <@jnsamyak:matrix.org> !info Meeting is 60 minutes MAX. At the end of 60, it stop
2024-05-28 16:02:09 <@jnsamyak:matrix.org> !info agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw
2024-05-28 16:02:18 <@jnsamyak:matrix.org> !topic init process
2024-05-28 16:02:27 <@jnsamyak:matrix.org> Hi folks, how's everyone doing today?
2024-05-28 16:02:37 <@humaton:fedora.im> !hi
2024-05-28 16:02:38 <@zodbot:fedora.im> Tomáš Hrčka (humaton) - he / him / his
2024-05-28 16:02:52 <@patrikp:matrix.org> Hi.
2024-05-28 16:02:59 <@nirik:matrix.scrye.com> morning
2024-05-28 16:03:06 <@nirik:matrix.scrye.com> here, but listening into another meeting too.
2024-05-28 16:03:15 <@jnsamyak:matrix.org> The count has increased today yay!
2024-05-28 16:03:33 <@jnsamyak:matrix.org> I have one thing to discuss for the init process - 
2024-05-28 16:04:07 <@jnsamyak:matrix.org> So we moved stuff from /pub/fedora/ and /pub/fedora-secondary for F38 last tuesday as per the EOL schedule
2024-05-28 16:04:26 <@jnsamyak:matrix.org> while doing that i found that we did not do this part for 37 that time
2024-05-28 16:04:36 <@jnsamyak:matrix.org> and later on the week jens also opened a ticket for that
2024-05-28 16:05:27 <@jnsamyak:matrix.org> I did acted on it and oved stuff from /pub/fedora/ and /pub/fedora-secondary for F37 last wednesday, and informed the mirror-admin mailing lit folks today on the same email for f38
2024-05-28 16:06:07 <@jnsamyak:matrix.org> the concern that was raised and was a valid one is about removal for those releases from /pub/fedora/ and /pub/fedora-secondary which we should in the release manner
2024-05-28 16:07:06 <@jnsamyak:matrix.org> so we should ideally remove 37 first maybe in two weeks? and then wait another two weeks to remove 38? I'm open for suggestions here, and wanted to discuss the timeline for the removal of these releases from the intended places
2024-05-28 16:07:47 <@nirik:matrix.scrye.com> I think either way, removing them there is right...
2024-05-28 16:07:54 <@jnsamyak:matrix.org> https://lists.fedoraproject.org/archives/list/mirror-admin@lists.fedoraproject.org/thread/ZXJIGXJOSXXEEOITTIC44GC6OTC4RX5M/
2024-05-28 16:08:40 <@jnsamyak:matrix.org> nirik: so question 1, since i informed offically to mirror-admin folks is it wise to wait two whole weeks or we could do removal of 37 on next tuesday?
2024-05-28 16:08:58 <@nirik:matrix.scrye.com> I think next week would be fine.
2024-05-28 16:09:11 <@nirik:matrix.scrye.com> just want to allow time to sync from archive...
2024-05-28 16:09:40 <@jnsamyak:matrix.org> awesome, I think so to as well, coming to my next question - Once we do that, removal of 37 do we wait another week for 38?
2024-05-28 16:10:37 <@nirik:matrix.scrye.com> I think we could do them at the same time since you moved them at the same time?
2024-05-28 16:10:59 <@humaton:fedora.im> do them both at same time both are EOL anyway
2024-05-28 16:11:28 <@jnsamyak:matrix.org> okay if we are on that argument I'll do both on the same day first 37 and then 38!
2024-05-28 16:11:33 <@jnsamyak:matrix.org> awesome, sorted!
2024-05-28 16:11:56 <@jnsamyak:matrix.org> !action - jnsamyak to do removals for 37 and 38 together next Tuesday as per the 38 schedule
2024-05-28 16:12:04 <@jnsamyak:matrix.org> that's all I had to discuss
2024-05-28 16:12:15 <@jnsamyak:matrix.org> Any other things folks want to bring up for the init topic?
2024-05-28 16:13:05 <@humaton:fedora.im> yeah
2024-05-28 16:13:28 <@jnsamyak:matrix.org> stage is yours :D
2024-05-28 16:13:42 <@humaton:fedora.im> so, we merged some changes lately that might break blocked packages automation
2024-05-28 16:14:14 <@humaton:fedora.im> Most of it will go live with the pagure release but some are already in place
2024-05-28 16:14:48 <@humaton:fedora.im> I will keep eye on the compose and the script runs, but if something fails horribly please dont revert it I will fix things 
2024-05-28 16:14:50 <@jnsamyak:matrix.org> anything in specific to look out for, anything obvious? 
2024-05-28 16:15:35 <@humaton:fedora.im> https://pagure.io/pungi-fedora/blob/main/f/nightly.sh#_58
2024-05-28 16:15:57 <@humaton:fedora.im> that sctip and all things it triggers
2024-05-28 16:16:40 <@humaton:fedora.im> I am not expecting things to break obviously, but more like some packages not getting blocked properly 
2024-05-28 16:17:20 <@jnsamyak:matrix.org> sure thing, I'll try to keep eye on composes as well thanks for the heads up
2024-05-28 16:17:44 <@humaton:fedora.im> that is all for this thing.
2024-05-28 16:17:49 <@humaton:fedora.im> But I have moar
2024-05-28 16:19:01 <@humaton:fedora.im> of course I loose all the links and important windows
2024-05-28 16:19:02 <@humaton:fedora.im> so
2024-05-28 16:19:11 <@humaton:fedora.im> this app is under releng namespace https://pagure.io/releng/compose-tracker
2024-05-28 16:20:01 <@humaton:fedora.im> the app it self is simple, thats why I picked it for the candidates to build using konflux.
2024-05-28 16:20:17 <@humaton:fedora.im> are you opened to that, or should I bring this up on fedora-ingfra meeting?
2024-05-28 16:20:51 <@humaton:fedora.im> are you opened to that, or should I bring this up on fedora-infra meeting?
2024-05-28 16:21:19 <@humaton:fedora.im> konflux can output image on quay that can be deployed in openshift
2024-05-28 16:21:36 <@nirik:matrix.scrye.com> hum.
2024-05-28 16:22:05 <@nirik:matrix.scrye.com> I am not sure that gets us much off hand.
2024-05-28 16:22:24 <@humaton:fedora.im> so we dont have to ever update fedora delease on the docker image 
2024-05-28 16:22:30 <@jnsamyak:matrix.org> seems like a good candidate, i was reading about konflux today only
2024-05-28 16:23:32 <@humaton:fedora.im> but yeah its not saving ton of man hours, but the procedure to update the image is regular(each release) and simple enough to be automated
2024-05-28 16:23:39 <@jnsamyak:matrix.org> need to dig more, but as long as we don't have to create a VM/Bootable Container etc to test it out i guess konflux support 
2024-05-28 16:24:09 <@nirik:matrix.scrye.com> well, it adds another thing, but not sure what advantage...
2024-05-28 16:24:11 <@humaton:fedora.im> I will bring this up on the infra weekly meeting later this week, or in releng chanel
2024-05-28 16:24:42 <@humaton:fedora.im> I see 2 advantages
2024-05-28 16:25:12 <@humaton:fedora.im> no more manual edits of Docker file, and we get rid of build config that is going away from openshift
2024-05-28 16:25:40 <@jnsamyak:matrix.org> we have a dockerfile, jednorozec when you said you picked it up did you by any chance started to play around konflux with this, I'm curios to know the results?
2024-05-28 16:26:08 <@humaton:fedora.im> I only build it didnt have chance to compare the outputs
2024-05-28 16:26:16 <@humaton:fedora.im> but the images ***should*** be the same
2024-05-28 16:26:52 <@jnsamyak:matrix.org> interesting 😍 will poke you more about it once i had a chance to play with it as well 
2024-05-28 16:27:34 <@humaton:fedora.im> I think this concept is getting dropped from openshift https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/compose-tracker/templates/buildconfig.yml
2024-05-28 16:27:51 <@humaton:fedora.im> and replaced by stuff like konflux
2024-05-28 16:28:42 <@nirik:matrix.scrye.com> thats very surprising to me.
2024-05-28 16:28:55 <@humaton:fedora.im> the thing is as you can see that we are running it now on f38, if we plug it into konflux it can always run on the stable release without anybody from releng doing anything...
2024-05-28 16:30:10 <@nirik:matrix.scrye.com> well, if we switched to fedora:latest we would just need to trigger a build at release time. ;)
2024-05-28 16:31:34 <@humaton:fedora.im> sure but without the SBOM with dependency list from pyp
2024-05-28 16:31:46 <@jnsamyak:matrix.org> i think that's where the konflux comes in and automate this step right?
2024-05-28 16:32:36 <@humaton:fedora.im> wel one thingis the build it self, the other is if you look at compose tracker there is no lockfile just requirements.txtx without versions
2024-05-28 16:32:49 <@humaton:fedora.im> this means ecah build can ponentially be different and we dont know that
2024-05-28 16:33:39 <@humaton:fedora.im> I am just saying it might be useful for apps that are not really activelly developed to keep eye on the images
2024-05-28 16:35:01 <@humaton:fedora.im> but I agree with nirik that there is not absolute benefit all of the thing I mentioned can be done in various ways...
2024-05-28 16:35:14 <@humaton:fedora.im> that is it
2024-05-28 16:35:37 <@jnsamyak:matrix.org> looks good to me for starting on a simple app like this and see the potential and benefits\ it gives, if it's worthed we could expand otherwise keep doing what we do? :)
2024-05-28 16:37:32 <@jnsamyak:matrix.org> Alright, good discussion folks anyone wants to add anything or we could move on to our next items from the agenda?
2024-05-28 16:38:11 <@jnsamyak:matrix.org> moving in 
2024-05-28 16:38:12 <@jnsamyak:matrix.org> 3
2024-05-28 16:38:13 <@jnsamyak:matrix.org> 2
2024-05-28 16:38:15 <@jnsamyak:matrix.org> 1
2024-05-28 16:38:23 <@jnsamyak:matrix.org> !topic scheduled actions coming up in the next week
2024-05-28 16:38:29 <@jnsamyak:matrix.org> !info Here we list/discuss anything about items that are going to be due to be done in the next week
2024-05-28 16:38:48 <@jnsamyak:matrix.org> nothing much here as discussed already we will do the removal for 38&37 both next tuesday
2024-05-28 16:39:07 <@jnsamyak:matrix.org> nothing off hand i know apart from this 
2024-05-28 16:39:59 <@jnsamyak:matrix.org> so moving on to the most interesting sections, tickets!
2024-05-28 16:40:01 <@jnsamyak:matrix.org> !topic Tickets needing attention
2024-05-28 16:40:08 <@jnsamyak:matrix.org> !info this is the time where you can bring releng tickets to discuss if there are blockers etc
2024-05-28 16:40:38 <@jnsamyak:matrix.org> !releng 12098
2024-05-28 16:40:40 <@zodbot:fedora.im> ● **Assignee:** Not Assigned
2024-05-28 16:40:40 <@zodbot:fedora.im> **releng #12098** (https://pagure.io/releng/issue/12098):** Renaming distribution media for Fedora Server**
2024-05-28 16:40:40 <@zodbot:fedora.im> 
2024-05-28 16:40:40 <@zodbot:fedora.im> ● **Opened:** 2 weeks ago by jwhimpel
2024-05-28 16:40:40 <@zodbot:fedora.im> ● **Last Updated:** 2 weeks ago
2024-05-28 16:41:15 <@jnsamyak:matrix.org> patrikp: did you get time to look into it, started somewhere'?
2024-05-28 16:41:44 <@patrikp:matrix.org> So far I've read through the Google doc and the ticket...
2024-05-28 16:42:36 <@jnsamyak:matrix.org> okay anything regarding that you wanna bring up, blockers etc?
2024-05-28 16:42:46 <@patrikp:matrix.org> So step 1 (the investigation part) is:
2024-05-28 16:42:46 <@patrikp:matrix.org> "Conduct a thorough analysis to pinpoint all components within the compose mechanism that would require modification due to the proposed renaming of distribution media for the Fedora Server."?
2024-05-28 16:43:01 <@patrikp:matrix.org> Kind of overwhelming and I'm unsure where to even start to be honest.
2024-05-28 16:44:40 <@carlwgeorge:matrix.org> if i want to bring something up, should i add it to that agenda hackmd myself or just bring it up here in channel once the rest of the agenda has been completed?
2024-05-28 16:45:28 <@jnsamyak:matrix.org> Carl George: any is fine, we had open floor but it seems we are running out of time for that, how about after this ticket?
2024-05-28 16:46:22 <@jnsamyak:matrix.org> But look how composes are done, i think we have discussed this earlier with jednorozec as well see pungi, how the config is there and how it triggers the compose, start connecting the docs
2024-05-28 16:46:22 <@jnsamyak:matrix.org> patrikp: Ahh no worries, we don't have just this meeting we have various places to discuss this so don't feel obligated to only ask thing in the meeting, we could do it on the releng channel etc
2024-05-28 16:46:31 <@jnsamyak:matrix.org> instead of looking for the places to rename
2024-05-28 16:47:02 <@jnsamyak:matrix.org> look for the compose process, have an outline around it, and then look how the compose stuff are being build
2024-05-28 16:47:16 <@jnsamyak:matrix.org> once you get that, look for the things to rename
2024-05-28 16:47:16 <@patrikp:matrix.org> Right on.
2024-05-28 16:47:20 <@jnsamyak:matrix.org> break into parts
2024-05-28 16:48:00 <@nirik:matrix.scrye.com> yeah, it's a bit of a blob...
2024-05-28 16:48:28 <@jnsamyak:matrix.org> okay so that's all for this one then!
2024-05-28 16:48:30 <@humaton:fedora.im> well more like spaghetti blob
2024-05-28 16:48:38 <@jnsamyak:matrix.org> Carl George: shooot!
2024-05-28 16:48:48 <@nirik:matrix.scrye.com> a haystack of needles
2024-05-28 16:48:54 <@jnsamyak:matrix.org> XD
2024-05-28 16:49:02 <@carlwgeorge:matrix.org> several times in the past i have been granted admin permissions in staging koji to work out things like epel next and epel9.  each time it seems i eventually lose that permission and need to re-request it.  i'm at that point again for epel10.
2024-05-28 16:49:16 <@carlwgeorge:matrix.org> short term ask: please grant me (fas: carlwgeorge) admin permissions in staging koji again.
2024-05-28 16:49:16 <@carlwgeorge:matrix.org> long term ask: if it is expected that these permissions get reset to what is in prod, i am interested in pursing whatever requirements are necessary to be granted admin for production koji.
2024-05-28 16:49:47 <@nirik:matrix.scrye.com> just needs adjusting in the prod->staging sync script...
2024-05-28 16:50:25 <@nirik:matrix.scrye.com> and perhaps it's worth doing another sync now before you start?
2024-05-28 16:50:42 <@carlwgeorge:matrix.org> sure
2024-05-28 16:51:01 <@nirik:matrix.scrye.com> it takes a really long time... like a day or so...
2024-05-28 16:51:21 <@carlwgeorge:matrix.org> eh in that case we can skip it, it won't make a difference for this demo i have in mind
2024-05-28 16:51:53 <@nirik:matrix.scrye.com> ok
2024-05-28 16:52:18 <@carlwgeorge:matrix.org> honestly the long term idea is worthwhile to me regardless, as it would come in handy for some pending epel next cleanup (untagging builds)
2024-05-28 16:52:30 <@carlwgeorge:matrix.org> but i can imagine that is a longer discussion
2024-05-28 16:54:23 <@nirik:matrix.scrye.com> I don't know that we have a process. ;) I'm ok with adding you, but would want input from jnsamyak and jednorozec at least
2024-05-28 16:54:52 <@nirik:matrix.scrye.com> especially if you want to take on some of the epel releng work with that access. ;)
2024-05-28 16:56:02 <@carlwgeorge:matrix.org> absolutely
2024-05-28 16:56:36 <@jnsamyak:matrix.org> what do you mean by `epel releng work` I am also unaware if there is a process but +1 from me if that signifies :P
2024-05-28 16:57:13 <@nirik:matrix.scrye.com> well, there's going to be a lot more of that with epel10... as when rhel minor releases happen we need to make new branches and setup new koji stuff.
2024-05-28 16:57:22 <@humaton:fedora.im> from time to time there is some tagging work 
2024-05-28 16:58:06 <@carlwgeorge:matrix.org> and each minor release will need a snapshot of the c10 sync to temporarily build against for about a month or two, until the real rhel10 minor release comes out
2024-05-28 16:58:08 <@humaton:fedora.im> but yeah the release cadence for epel is much slower
2024-05-28 16:58:25 <@humaton:fedora.im> yeah lot new stuff with el10
2024-05-28 16:58:45 <@carlwgeorge:matrix.org> if you remember the dance we did for epel9 at the rhel9 release time, it will be similar, expanded out to every minor
2024-05-28 16:59:08 <@jnsamyak:matrix.org> the same request that came in the ticket recently about the snapshot and the sync script?
2024-05-28 16:59:35 <@jnsamyak:matrix.org> that reminds me the sop part of it is on me
2024-05-28 16:59:35 <@carlwgeorge:matrix.org> the recent ticket was just getting the c10 sync setup, no snapshotting yet
2024-05-28 16:59:51 <@jnsamyak:matrix.org> yep
2024-05-28 16:59:58 <@carlwgeorge:matrix.org> if you like i can fill you in more outside of this meeting, whatever time works best for you
2024-05-28 17:00:40 <@jnsamyak:matrix.org> yep it's almost 10:30 pm for me, but what i can do is create an issue on releng and discuss there async or a call tomorrow whatever works
2024-05-28 17:00:48 <@jnsamyak:matrix.org> it's good to have it documented somewhere
2024-05-28 17:00:49 <@nirik:matrix.scrye.com> ideally we would script as much of this as possible.
2024-05-28 17:01:01 <@jnsamyak:matrix.org> +1
2024-05-28 17:01:03 <@nirik:matrix.scrye.com> I don't think any of this is urgent.
2024-05-28 17:01:39 <@jnsamyak:matrix.org> Carl George: quick request if you can file a ticket please with the description on releng?
2024-05-28 17:01:51 <@jnsamyak:matrix.org> i dont want to loose info while drafting one
2024-05-28 17:02:13 <@carlwgeorge:matrix.org> it's larger than just one ticket, i have a high level overview here https://discussion.fedoraproject.org/t/epel-10-proposal/44304
2024-05-28 17:02:34 <@carlwgeorge:matrix.org> definitely will file tickets for each individual item of work as it makes sense
2024-05-28 17:02:39 <@jnsamyak:matrix.org> awesome this is super nice
2024-05-28 17:02:47 <@jnsamyak:matrix.org> thanks Carl George 
2024-05-28 17:03:04 <@jnsamyak:matrix.org> !info related epel10 + releng work https://discussion.fedoraproject.org/t/epel-10-proposal/44304
2024-05-28 17:03:10 <@carlwgeorge:matrix.org> should i file a ticket about getting admin perms in koji, so that doesn't get lost?
2024-05-28 17:03:27 <@nirik:matrix.scrye.com> I'm fine with just doing it if everyone else is ok with it. ;)
2024-05-28 17:03:30 <@jnsamyak:matrix.org> nirik: that's for you^
2024-05-28 17:03:38 <@jnsamyak:matrix.org> yep
2024-05-28 17:03:40 <@jnsamyak:matrix.org> +1
2024-05-28 17:04:05 <@jnsamyak:matrix.org> btw time check folks we are minutes over
2024-05-28 17:04:17 <@jnsamyak:matrix.org> thanks for the awesome discussions today!
2024-05-28 17:04:34 <@jnsamyak:matrix.org> we can always take this to releng channel
2024-05-28 17:04:45 <@jnsamyak:matrix.org> !info Thank you all for coming.
2024-05-28 17:04:52 <@jnsamyak:matrix.org> !endmeeting