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