<@patrikp:matrix.org>
16:00:00
!startmeeting RELENG (2024-11-18)
<@meetbot:fedora.im>
16:00:05
Meeting started at 2024-11-18 16:00:00 UTC
<@meetbot:fedora.im>
16:00:05
The Meeting name is 'RELENG (2024-11-18)'
<@meetbot:fedora.im>
16:00:28
Sorry, `!startmeeting` must be called by itself
<@patrikp:matrix.org>
16:00:54
Oops, copied that twice. No worries. Good evening.
<@jnsamyak:matrix.org>
16:01:07
0/
<@amedvede:fedora.im>
16:01:15
!hi
<@zodbot:fedora.im>
16:01:16
Anton Medvedev (amedvede)
<@nirik:matrix.scrye.com>
16:01:39
morning
<@patrikp:matrix.org>
16:01:52
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@patrikp:matrix.org>
16:01:52
!topic Init process.
<@nirik:matrix.scrye.com>
16:03:00
so, we are behind on the post release stuff (due to that mm script not working).
<@nirik:matrix.scrye.com>
16:03:18
we should try and catch Aurélien B to look at it (unless he already did... I haven't caught up on email yet)
<@jnsamyak:matrix.org>
16:04:19
And yes, I was sick last week, i need to send over the compose tracker cleanup email etc, so will do that today/tomorrow
<@jnsamyak:matrix.org>
16:04:29
before going on the PTO :D
<@jnsamyak:matrix.org>
16:04:46
And will finish up cleanup work
<@abompard:fedora.im>
16:05:21
What's the ticket about the thing I should do?
<@nirik:matrix.scrye.com>
16:05:23
👋
<@nirik:matrix.scrye.com>
16:05:49
https://pagure.io/releng/issue/12449
<@patrikp:matrix.org>
16:05:51
!releng 12449
<@zodbot:fedora.im>
16:05:52
● **Last Updated:** 3 days ago
<@zodbot:fedora.im>
16:05:52
● **Assignee:** patrikp
<@zodbot:fedora.im>
16:05:52
● **Opened:** 6 days ago by patrikp
<@zodbot:fedora.im>
16:05:52
<@zodbot:fedora.im>
16:05:52
**releng #12449** (https://pagure.io/releng/issue/12449):**Fedora Linux 41 Post Release Clean Up Tracker**
<@abompard:fedora.im>
16:06:04
Oh, got it
<@nirik:matrix.scrye.com>
16:06:14
the script to move development/41 to use releases/41 isn't working right (Or I was holding it wrong)
<@nirik:matrix.scrye.com>
16:07:56
anyhow, once thats sorted we need to do the rest... but thats probibly all on this topic
<@jnsamyak:matrix.org>
16:08:06
+1
<@abompard:fedora.im>
16:08:22
probably my bad, I'll fix it
<@patrikp:matrix.org>
16:09:13
Next topic then?
<@patrikp:matrix.org>
16:09:32
<@patrikp:matrix.org>
16:09:32
!topic Scheduled actions coming up in the next week.
<@patrikp:matrix.org>
16:09:32
!info Here we list/discuss anything about items that are due to be done in the next week.
<@patrikp:matrix.org>
16:09:32
<@nirik:matrix.scrye.com>
16:10:21
tomorrow is f39 eol I guess? or was it not right on that schedule
<@nirik:matrix.scrye.com>
16:10:54
right, 26th.
<@nirik:matrix.scrye.com>
16:11:09
so, nothing until then I think (except the post 41 cleanup)
<@patrikp:matrix.org>
16:11:52
!info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.
<@patrikp:matrix.org>
16:11:52
!topic Tickets that need attention.
<@nirik:matrix.scrye.com>
16:12:36
The h264 stuff is heating up again.
<@nirik:matrix.scrye.com>
16:12:54
!releng 12466
<@zodbot:fedora.im>
16:12:55
● **Last Updated:** Never
<@zodbot:fedora.im>
16:12:55
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:12:55
<@zodbot:fedora.im>
16:12:55
**releng #12466** (https://pagure.io/releng/issue/12466):**Please update `openh264`to 2.5.0 in F41**
<@zodbot:fedora.im>
16:12:55
● **Opened:** 7 hours ago by abitrolly
<@nirik:matrix.scrye.com>
16:13:10
!releng 12385
<@zodbot:fedora.im>
16:13:11
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:13:11
● **Last Updated:** a month ago
<@zodbot:fedora.im>
16:13:11
● **Opened:** a month ago by kalev
<@zodbot:fedora.im>
16:13:11
<@zodbot:fedora.im>
16:13:11
**releng #12385** (https://pagure.io/releng/issue/12385):**Please send openh264-2.4.1-1.el10_0 to Cisco**
<@jnsamyak:matrix.org>
16:13:52
yeah, patrikp any updates on this?
<@jnsamyak:matrix.org>
16:14:00
Did you try to experiment?
<@patrikp:matrix.org>
16:15:08
So far I've read the doc and some documentation.
<@nirik:matrix.scrye.com>
16:16:00
perhaps you and jednorozec could meet up and work on it? I'd be happy to help, but...timzeones and busyness are anoying
<@jnsamyak:matrix.org>
16:16:48
but this will not work, just reading the documentation, we need to experiment with this on priority and see how far we can go, and what resources we need more on this
<@jnsamyak:matrix.org>
16:17:08
so please start somewhere, and discuss your blockers
<@humaton:fedora.im>
16:17:18
!hi
<@zodbot:fedora.im>
16:17:19
Tomáš Hrčka (humaton) - he / him / his
<@humaton:fedora.im>
16:18:09
I am happy to help with this
<@jnsamyak:matrix.org>
16:18:27
awesome possum!
<@jnsamyak:matrix.org>
16:19:53
Let's move on to next items?
<@patrikp:matrix.org>
16:20:06
Any other tickets that need attention?
<@jnsamyak:matrix.org>
16:20:51
Anton Medvedev: are you facing any blockers from your work whille finishing old tickets for unretirement toddlers etc?
<@jnsamyak:matrix.org>
16:21:03
that you want to bring it up to todayy's meeting
<@jnsamyak:matrix.org>
16:21:15
!releng 12455
<@nirik:matrix.scrye.com>
16:21:17
there was a discussion item at some point... 12454
<@amedvede:fedora.im>
16:21:20
no, got review from Michal
<@zodbot:fedora.im>
16:21:29
● **Assignee:** jnsamyak
<@zodbot:fedora.im>
16:21:29
**releng #12455** (https://pagure.io/releng/issue/12455):**F42 Self-Contained Change: LXQt 2.1**
<@zodbot:fedora.im>
16:21:29
<@zodbot:fedora.im>
16:21:29
● **Opened:** 6 days ago by ngompa
<@zodbot:fedora.im>
16:21:29
● **Last Updated:** 5 days ago
<@jnsamyak:matrix.org>
16:21:55
I reviewed this and I think there is nothing that releng can do; so I'll close this but wanted to bring to meeting first
<@jnsamyak:matrix.org>
16:22:05
Anton Medvedev: Can you link it here for others too?
<@nirik:matrix.scrye.com>
16:23:07
+1 to thank and close
<@jnsamyak:matrix.org>
16:23:07
!releng 12454
<@zodbot:fedora.im>
16:23:09
<@zodbot:fedora.im>
16:23:09
**releng #12454** (https://pagure.io/releng/issue/12454):**Discuss how to integrate OCI artifacts**
<@zodbot:fedora.im>
16:23:09
● **Opened:** 6 days ago by lzap
<@zodbot:fedora.im>
16:23:09
● **Last Updated:** 5 days ago
<@zodbot:fedora.im>
16:23:09
● **Assignee:** Not Assigned
<@jnsamyak:matrix.org>
16:23:19
Let's discuss it here now :D
<@nirik:matrix.scrye.com>
16:23:39
I don't see lzap off hand... ;(
<@nirik:matrix.scrye.com>
16:23:47
might be our time change messed that up
<@jnsamyak:matrix.org>
16:24:50
Okay starting with dumb questions, we added sercia etc in f40 and so, the process should have to similar right? Making sure pungi has those changes, and once those artificats are build it should be signed properly, that means we have to update the robosignatory
<@lzap:matrix.org>
16:24:59
thanks for the ping, sorry for the trouble
<@jnsamyak:matrix.org>
16:25:14
Okay starting with dumb questions, we added sercia etc in f40 and so, the process should have to similar right? Making sure pungi has those changes, and once those artificats are build it should be signed properly, that means we have to update the robosignatory from the ansible playbook? I might be missing context here
<@nirik:matrix.scrye.com>
16:25:21
jnsamyak: this is new. It's kickstarts and stuff for pxe boot/installs.
<@jnsamyak:matrix.org>
16:25:35
ohhh!
<@nirik:matrix.scrye.com>
16:25:35
lzap: welcome. we changed time recently, so sorry for any confusion
<@jnsamyak:matrix.org>
16:25:49
lzap: hello hello, welcome!
<@nirik:matrix.scrye.com>
16:26:29
I guess I'd love to hear how this is working now? github actions or something?
<@lzap:matrix.org>
16:27:03
sure let me describe how it is now, the feature in question is at https://fedoraproject.org/wiki/Changes/KickstartOciArtifacts
<@lzap:matrix.org>
16:28:03
so when we asked around, folks from bootc team recommended we would start a gitlab CICD pipeline that does extraction of these files and push to registry, this is exactly what we did. the repo is here: https://gitlab.com/fedora/bootc/artifacts/kickstart-artifacts/-/tree/main?ref_type=heads
<@lzap:matrix.org>
16:28:25
ipanova: feel free to fill me in
<@jnsamyak:matrix.org>
16:28:48
thanks for these references, I'll add these to ticket as well
<@lzap:matrix.org>
16:30:36
we are hoping for something fully integrated into the Fedora release pipeline, so e.g. when grub2 is updated the pipeline would check SHAs and push a possible update when necessary
<@lzap:matrix.org>
16:31:04
PXE files do not get updated in the mid-release I suppose so no problems there
<@lzap:matrix.org>
16:32:23
to what we do, it is extremely simple: we install few RPMs in a container (grub, pxelinux) plus we download some PXE files from the images/ HTTPS directory and bundle them as OCI artifacts, we plan to sign them that is also an open question maybe for today
<@jnsamyak:matrix.org>
16:32:47
hmm
<@lzap:matrix.org>
16:32:48
you can pretty much see it all in the .gitlab-ci.yml and push.sh
<@jnsamyak:matrix.org>
16:33:18
is the gitlab repo public?
<@lzap:matrix.org>
16:33:44
ah does not appear to be, I haven’t realized that
<@jnsamyak:matrix.org>
16:34:01
yep looks like it's not :(
<@lzap:matrix.org>
16:34:44
yeah looks like bootc images is, ipanova we need to reconfigure it: https://gitlab.com/fedora/bootc/base-images
<@lzap:matrix.org>
16:35:29
I do not have permissions for that but we can arrange that, good point
<@ipanova:matrix.org>
16:36:01
i fix that up
<@ipanova:matrix.org>
16:36:06
i;ll fix that up
<@jnsamyak:matrix.org>
16:36:59
awesome I'll look into that
<@ipanova:matrix.org>
16:38:16
should be public now
<@lzap:matrix.org>
16:38:26
if there is easier way to integrate this (e.g. via pungi "plugin") let us know, it is essentially a small script
<@jnsamyak:matrix.org>
16:38:38
Can you add these details to ticket as well, it will be very easier for everyone to follow up, and ask questions, this is the first time Im getting introduces to it
<@jnsamyak:matrix.org>
16:38:47
Sure!
<@lzap:matrix.org>
16:38:48
sure
<@jnsamyak:matrix.org>
16:39:24
thank you so much for the rundown lzap ipanova
<@ipanova:matrix.org>
16:39:47
since the main motivation for kickstart file as oci artifacts were to add so they are available alongside with fedora-bootc images we thought we'd just follow same ci/cd as fedora-bootc
<@ipanova:matrix.org>
16:40:23
as lzap we can change as needed, but this this the background for our first choice
<@ipanova:matrix.org>
16:41:09
as lzap said we can change as needed, but this this the background for our first choice
<@lzap:matrix.org>
16:41:09
also we are aware of Konflux and I did look into it, the thing is, Konflux is currently heavily Containerfile-app based. meaning if you want to do anything different than build a container, it is challenge. thus we would like to wait with possible conversion of this into Konflux for later.
<@nirik:matrix.scrye.com>
16:41:18
we may be able to integrate it into the compose pipeline... not sure. will have to think on it and look at it more. ;)
<@nirik:matrix.scrye.com>
16:42:09
yeah... it may be that if composes moved to konflux this could just be a part of the publishing pipelines... but I think thats a ways off.
<@jnsamyak:matrix.org>
16:43:20
yeah
<@lzap:matrix.org>
16:44:56
it looks like bootc pipeline is renovate bot driven, we were hoping to do the same. but that I think sums it up nicely where we are currently.
<@nirik:matrix.scrye.com>
16:46:34
Thanks for all the info...
<@ipanova:matrix.org>
16:47:30
any preferred way how to follow up on this? should we wait to hear from you?
<@nirik:matrix.scrye.com>
16:47:45
I think we can coordinate in ticket?
<@nirik:matrix.scrye.com>
16:47:56
after we look things over and have any ideas...
<@ipanova:matrix.org>
16:48:26
we got through all the FC proposal changes and got needed repo created with perms on quay.io so the only part which is missing is to agree how to push those assets to the registry
<@ipanova:matrix.org>
16:48:52
nirik: sounds good
<@lzap:matrix.org>
16:48:53
what we can do now is to start pushing 41 files and integrate renovate so it is automatic or semi-automatic
<@lzap:matrix.org>
16:49:53
this is new for us, but we were told renovate allows to hook into an event of package update, that would be when we would trigger rebuild
<@lzap:matrix.org>
16:50:13
I expect that major releases would require us to setup a new branch in gitlab
<@nirik:matrix.scrye.com>
16:51:13
might start with f42/rawhide?
<@ipanova:matrix.org>
16:51:28
i guess what we're asking is if it ok if we proceed with the gitlab pipeline and configure renovate that would be building and pushing automatically new images based on the changes in fedora repos or you prefer that we hold-on until you guys say what's your preference
<@lzap:matrix.org>
16:52:22
if you prefer, tho, with rawhide there is a slight problem - in daily composes the PXE files (anaconda image) gets regenerated (or maybe every week), this can put a lot of stress on the quay.io fedora account. i was thinking not doing rawhide, or we need to figure out early garbage collection
<@jnsamyak:matrix.org>
16:52:27
I say the same as to start experimenting things on rawhide first, since it's a good candidate for development etc
<@ipanova:matrix.org>
16:52:29
yes but then once all is tested and stable we'd like to retroactively also push to fc 41/40
<@nirik:matrix.scrye.com>
16:53:40
so for 41/40, is that going to regenerate on updates? or just the GA content?
<@ipanova:matrix.org>
16:53:52
lzap: we need to look into quay's repo setting but i think those images that do not have tags are automatically garbage collected after some expiration time
<@lzap:matrix.org>
16:53:55
well sure then let’s start with rawhide and setup a weekly or daily (?) event that will push a tag in the 2024-11-18 form or something and also figure out garbage collection of old commits
<@nirik:matrix.scrye.com>
16:54:23
yeah, I think that would be best... and yeah, I think there is some GC on the quay side. I don't recall what it is tho.
<@lzap:matrix.org>
16:54:27
ipanova: yes but we need to delete old tags for rawhide
<@ipanova:matrix.org>
16:55:12
tags will shift, i don't think we'll apply tags with timestamps embedded
<@ipanova:matrix.org>
16:55:26
so it will be :40 :41 :latest :rawhide
<@ipanova:matrix.org>
16:55:27
etc
<@lzap:matrix.org>
16:55:37
right that makes sense
<@lzap:matrix.org>
16:56:15
since PXE files really do not change too much (only grub2 occasionally) I wonder if we can do it simply every week
<@jnsamyak:matrix.org>
16:56:25
we can use this meeting every week to discuss blockers on this?
<@nirik:matrix.scrye.com>
16:56:57
well, kernel changes...
<@ipanova:matrix.org>
16:57:06
so tldr we'll continue with gitlab and experiment with rawhide content, we can give updates next week?
<@lzap:matrix.org>
16:57:11
nirik: on your regenerate on updates - PXE files are static what can possibly change is grub2 or shim. we can hook via renovatebot or we can just do a daily/weekly rebuild. if SHAs are the same, there is nothing to push so it is really cheap
<@patrikp:matrix.org>
16:57:18
On this topic, since both Samyak and Kevin are on PTO next week, next meeting will be 2nd of Dec?
<@lzap:matrix.org>
16:57:40
nirik: but are anaconda images really regenerated on a kernel update? I don’t think so.
<@lzap:matrix.org>
16:57:51
nirik: I mean on stable release, not on rawhide of course
<@jnsamyak:matrix.org>
16:58:00
sure, but meanwhile we can discuss blockers on #releng:fedoraproject.org if required
<@nirik:matrix.scrye.com>
16:58:18
right, rawhide yes, stable no. ;) stable it's always the GA content people use.
<@lzap:matrix.org>
16:59:35
ok to sum it up: we will write a summary in the ticket, start building and pushing rawhide into the official repo, let’s meet on the #releng:fedoraproject.org channel if we have an issue and let’s hook up together once we have the content pushed.
<@lzap:matrix.org>
16:59:58
we need to figure out signing but for rawhide i guess there will be no signatures
<@lzap:matrix.org>
17:00:13
thanks you all!
<@nirik:matrix.scrye.com>
17:00:14
👍
<@patrikp:matrix.org>
17:00:32
And we are at time.
<@patrikp:matrix.org>
17:00:35
!endmeeting
<@patrikp:matrix.org>
17:00:35
!info Thank you all for coming!