<@jnsamyak:matrix.org>
16:00:26
!startmeeting RELENG (2024-06-25)
<@meetbot:fedora.im>
16:00:27
Meeting started at 2024-06-25 16:00:26 UTC
<@meetbot:fedora.im>
16:00:27
The Meeting name is 'RELENG (2024-06-25)'
<@jnsamyak:matrix.org>
16:00:34
!meetingname releng
<@meetbot:fedora.im>
16:00:35
The Meeting Name is now releng
<@jnsamyak:matrix.org>
16:00:43
!chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec jnsamyak patrikp
<@jnsamyak:matrix.org>
16:00:49
!info Meeting is 60 minutes MAX. At the end of 60, it stop
<@jnsamyak:matrix.org>
16:00:56
!info agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw
<@nirik:matrix.scrye.com>
16:01:01
morning
<@jnsamyak:matrix.org>
16:01:06
!topic init process
<@jnsamyak:matrix.org>
16:01:18
Hello folks, how's everyone doing today?
<@jnsamyak:matrix.org>
16:01:24
Welcome to releng weekly :D
<@patrikp:matrix.org>
16:01:31
Hi.
<@jnsamyak:matrix.org>
16:02:24
Do we have anything for the init? Any blockers, tasks, issues, requests, features that needs releng intervention?
<@nirik:matrix.scrye.com>
16:02:30
👋
<@jnsamyak:matrix.org>
16:03:18
Okay so skipping it, to our next item!
<@jnsamyak:matrix.org>
16:03:24
!topic scheduled actions coming up in the next week
<@jnsamyak:matrix.org>
16:03:31
!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:03:51
Mass Rebuilding is scheduled for next month
<@nirik:matrix.scrye.com>
16:04:47
rhel7/epel7 eol is sunday...
<@jnsamyak:matrix.org>
16:05:00
we have various proposals coming on releng tracker, and the changes that are expected to be taken care of at rebuilding, I'm trying to add them with `massr ebuild` tag
<@nirik:matrix.scrye.com>
16:05:03
I'm probibly going to look at upgrading builders to f40 after that
<@jnsamyak:matrix.org>
16:05:22
nirik: thanks for bringing this up, does this needs releng(ers) to do something?
<@jnsamyak:matrix.org>
16:05:37
releng(engers) === fedora_release power rangers
<@jnsamyak:matrix.org>
16:05:38
hehe
<@nirik:matrix.scrye.com>
16:06:05
:)
<@jnsamyak:matrix.org>
16:06:10
nirik: when you do that, do you actually talk about that in the noc channel?
<@jnsamyak:matrix.org>
16:06:31
I'm not sure what all the acls etc are needed but I would love to spectate at that sometime while you do
<@jnsamyak:matrix.org>
16:06:46
to look how it is done and what are the things that are taken care of
<@nirik:matrix.scrye.com>
16:07:16
I don't think we need to do too much for epel7... just removing the target and carl can likely do that... and then archiving it might be something we need to do
<@nirik:matrix.scrye.com>
16:07:28
the builders? yes, we have a SOP on it...
<@jnsamyak:matrix.org>
16:08:34
this: https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/koji-builder-setup/#_upgrading_builders?
<@nirik:matrix.scrye.com>
16:08:52
yeah.
<@jnsamyak:matrix.org>
16:09:09
theoretically we do staging first and then the prod?
<@nirik:matrix.scrye.com>
16:09:24
yep
<@nirik:matrix.scrye.com>
16:09:33
we have to wait for epel7 to go away tho
<@jnsamyak:matrix.org>
16:09:47
awesome, would see how you do it this time
<@jnsamyak:matrix.org>
16:09:50
thanks!
<@jnsamyak:matrix.org>
16:10:06
!link https://pagure.io/releng/issue/12147
<@jnsamyak:matrix.org>
16:10:21
!info The buildroot for EPEL 8 Next is CentOS Stream 8, which itself went EOL on 2024-05-31.
<@nirik:matrix.scrye.com>
16:11:01
I added my thoughts.
<@jnsamyak:matrix.org>
16:11:14
yeah
<@nirik:matrix.scrye.com>
16:11:36
I can ask folks to look in the epel meeting tomorrow
<@jnsamyak:matrix.org>
16:11:42
but once this is done, i think we should ask them or create a sop out of it seprately what say?
<@jnsamyak:matrix.org>
16:11:46
thanks nirik
<@nirik:matrix.scrye.com>
16:12:31
well, we could I guess... there is only epel9-next left of those tho and there won't be any more
<@nirik:matrix.scrye.com>
16:12:41
of you mean a generic 'epelX end of life' ?
<@jnsamyak:matrix.org>
16:13:34
the generic
<@nirik:matrix.scrye.com>
16:13:52
sure, that would be good to have... or a section in the main fedora one...
<@nirik:matrix.scrye.com>
16:14:02
whatever works
<@jnsamyak:matrix.org>
16:14:10
yeah +1 that were my thoughts
<@jnsamyak:matrix.org>
16:14:22
yeah but that's all that i have for the release items
<@jnsamyak:matrix.org>
16:14:42
Anything else, that folks want to bring up or can we jump to our next item?
<@nirik:matrix.scrye.com>
16:14:55
next
<@jnsamyak:matrix.org>
16:15:19
aye aye captain
<@jnsamyak:matrix.org>
16:15:25
!topic Tickets needing attention
<@jnsamyak:matrix.org>
16:15:30
!info this is the time where you can bring releng tickets to discuss if there are blockers etc
<@jnsamyak:matrix.org>
16:15:58
some quick change proposal that i went through and think can be closed
<@jnsamyak:matrix.org>
16:16:06
!releng 12177
<@zodbot:fedora.im>
16:16:07
**releng #12177** (https://pagure.io/releng/issue/12177):**F41 System-wide change: Reduce the amount of "dontaudit" rules pertaining to unlabeled_t**
<@zodbot:fedora.im>
16:16:07
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:16:07
● **Last Updated:** 10 hours ago
<@zodbot:fedora.im>
16:16:07
● **Opened:** 19 hours ago by vmojzis
<@zodbot:fedora.im>
16:16:07
<@nirik:matrix.scrye.com>
16:16:17
yeah. +1 close
<@jnsamyak:matrix.org>
16:17:40
done
<@nirik:matrix.scrye.com>
16:17:42
there are several more
<@jnsamyak:matrix.org>
16:18:01
!releng 12175
<@zodbot:fedora.im>
16:18:03
● **Last Updated:** 21 hours ago
<@zodbot:fedora.im>
16:18:03
**releng #12175** (https://pagure.io/releng/issue/12175):**https://fedoraproject.org/wiki/Changes/RetirePython2.7**
<@zodbot:fedora.im>
16:18:03
<@zodbot:fedora.im>
16:18:03
● **Opened:** a day ago by churchyard
<@zodbot:fedora.im>
16:18:03
● **Assignee:** Not Assigned
<@jnsamyak:matrix.org>
16:18:14
yes just quickly adding a comment and closing parralely
<@nirik:matrix.scrye.com>
16:18:20
yep. close. +1
<@jnsamyak:matrix.org>
16:19:15
!releng 12138
<@zodbot:fedora.im>
16:19:16
**releng #12138** (https://pagure.io/releng/issue/12138):**F41 System-wide change: Anaconda as native Wayland application**
<@zodbot:fedora.im>
16:19:16
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:19:16
<@zodbot:fedora.im>
16:19:16
● **Last Updated:** 3 weeks ago
<@zodbot:fedora.im>
16:19:16
● **Opened:** 3 weeks ago by jkonecny
<@nirik:matrix.scrye.com>
16:19:41
yep. close. +1
<@jnsamyak:matrix.org>
16:20:17
!releng 12077
<@zodbot:fedora.im>
16:20:18
● **Opened:** 2 months ago by mattkae
<@zodbot:fedora.im>
16:20:18
● **Last Updated:** 6 days ago
<@zodbot:fedora.im>
16:20:18
**releng #12077** (https://pagure.io/releng/issue/12077):**F41 Self-Contained Change: Fedora Miracle spin**
<@zodbot:fedora.im>
16:20:18
<@zodbot:fedora.im>
16:20:18
● **Assignee:** Not Assigned
<@jnsamyak:matrix.org>
16:20:30
so i reached out
<@jnsamyak:matrix.org>
16:20:48
in case of any hekp required i haven't heard from them yet
<@nirik:matrix.scrye.com>
16:21:10
yeah. ;( ok
<@jnsamyak:matrix.org>
16:21:31
btw
<@jnsamyak:matrix.org>
16:21:34
!link https://pagure.io/releng/issues?tags=changes
<@jnsamyak:matrix.org>
16:22:11
some of the change tag mentions are years old and i want to discuss if they are valid changesets
<@jnsamyak:matrix.org>
16:22:13
!releng 10110
<@zodbot:fedora.im>
16:22:14
**releng #10110** (https://pagure.io/releng/issue/10110):**RFE: Integration of Anitya to Packager Workflow**
<@zodbot:fedora.im>
16:22:14
● **Last Updated:** 2 years ago
<@zodbot:fedora.im>
16:22:14
● **Opened:** 3 years ago by amoloney
<@zodbot:fedora.im>
16:22:14
<@zodbot:fedora.im>
16:22:14
● **Assignee:** Not Assigned
<@nirik:matrix.scrye.com>
16:23:22
I have no idea here...
<@nirik:matrix.scrye.com>
16:23:35
we should mention @zlopez in it? or just close it...
<@jnsamyak:matrix.org>
16:24:12
I'll talk to Zlopez about it tomorrow and close this
<@nirik:matrix.scrye.com>
16:24:31
ok.
<@jnsamyak:matrix.org>
16:24:45
!releng 10399
<@zodbot:fedora.im>
16:24:46
● **Last Updated:** 3 weeks ago
<@zodbot:fedora.im>
16:24:46
**releng #10399** (https://pagure.io/releng/issue/10399):**tracker issue for ostree native containers**
<@zodbot:fedora.im>
16:24:46
<@zodbot:fedora.im>
16:24:46
● **Opened:** 2 years ago by walters
<@zodbot:fedora.im>
16:24:46
● **Assignee:** Not Assigned
<@jnsamyak:matrix.org>
16:25:20
I think adam is working on this looking at the latest comments
<@nirik:matrix.scrye.com>
16:26:35
well, yeah...
<@nirik:matrix.scrye.com>
16:27:04
this ticket is sort of a overall tracker i guess... which isn't great... but ok
<@nirik:matrix.scrye.com>
16:27:46
I mean, we are actually making oci images for everything now... but they aren't the default yet in some cases.
<@jnsamyak:matrix.org>
16:28:29
make sense, I'll understand this and discuss maybe in the next meeting
<@jnsamyak:matrix.org>
16:29:28
moving on, to the next item i think the prs related to this is merged but not sure how releng is part of it
<@jnsamyak:matrix.org>
16:29:32
!releng 11398
<@zodbot:fedora.im>
16:29:34
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:29:34
● **Last Updated:** 8 months ago
<@zodbot:fedora.im>
16:29:34
● **Opened:** a year ago by mhayden
<@zodbot:fedora.im>
16:29:34
**releng #11398** (https://pagure.io/releng/issue/11398):**Publish Fedora images in Azure 💙 ⛅**
<@zodbot:fedora.im>
16:29:34
<@nirik:matrix.scrye.com>
16:29:52
yeah, I think we can close this now... the cloud-image-uploader is uploading to azure
<@nirik:matrix.scrye.com>
16:30:16
want me to close with that note?
<@jnsamyak:matrix.org>
16:30:48
yes please! one question if you know, do you happen to know ow this is done,a nd who maintains thw work behind this?
<@jnsamyak:matrix.org>
16:31:40
yes please! one question if you know, do you happen to know how this is done, and who maintains thw work behind this?
<@nirik:matrix.scrye.com>
16:31:45
yes, I think it is... and the cloud-sig has been working on cloud-image-uploader (app in our openshift). It listens for image build complete messages and uploads them... it does azure now and aws is being worked on (so we can kill fedimg)
<@jnsamyak:matrix.org>
16:32:43
i get to know about the aws way while talking to neal and duncan at devconf
<@jnsamyak:matrix.org>
16:32:51
awesome thanks for the info
<@jnsamyak:matrix.org>
16:33:56
okay last one from changes and it's more of progress question
<@jnsamyak:matrix.org>
16:34:01
!releng 12098
<@zodbot:fedora.im>
16:34:02
**releng #12098** (https://pagure.io/releng/issue/12098):** Renaming distribution media for Fedora Server**
<@zodbot:fedora.im>
16:34:02
<@zodbot:fedora.im>
16:34:02
● **Assignee:** patrikp
<@zodbot:fedora.im>
16:34:02
● **Last Updated:** 4 days ago
<@zodbot:fedora.im>
16:34:02
● **Opened:** a month ago by jwhimpel
<@jnsamyak:matrix.org>
16:34:30
patrikp: what's the status to this? were you able to figure out the bits? blockers/question?
<@patrikp:matrix.org>
16:36:20
I left a comment on the issue. I looked at the bits from the doc we have (and Kevin's comment) but that kind of sounds like doing the entire investigation. I think the most sensible way to approach this is for the guys to ask questions in the ticket whenever they run into issues. That way everyone can see it and answer as necessary.
<@nirik:matrix.scrye.com>
16:36:52
sure... also it might make sense to just do one at a time...
<@nirik:matrix.scrye.com>
16:37:08
ie, look at first one, figure out how/if we can rename it, then the next, etc.
<@jnsamyak:matrix.org>
16:38:03
yeah the tickets for questions are good but how the renaming can happen what are the composes changes necessary that's something we have to figure out
<@jnsamyak:matrix.org>
16:38:15
and that should be what investigation is about
<@jnsamyak:matrix.org>
16:40:03
I would love to see something on the doc that states the process so we can actually document that also in future for such requests, and the bits written in the document we all can verify and chime in
<@jnsamyak:matrix.org>
16:40:33
!link https://docs.google.com/document/d/1MbEQFaCNnGpDIp7NDExvrvSXwCfu7TD-xXTKjU6NBiA/edit#heading=h.2scm2ejca9af
<@nirik:matrix.scrye.com>
16:40:40
well, it's going to be a bunch of different things most likely because they want to change a bunch of different things.
<@jnsamyak:matrix.org>
16:40:55
this is the doc for people reading the meeting logs
<@jnsamyak:matrix.org>
16:42:35
nirik: for sure, but renaming X name(s) will result in changing those from Y different places, so mostly the Y places should be/mostly same right?
<@patrikp:matrix.org>
16:43:19
I suppose we will have the process documented by the time the ticket is finished. I'm not sure how to plan it out in advance.
<@jnsamyak:matrix.org>
16:43:35
patrikp: why?
<@patrikp:matrix.org>
16:43:45
The areas that need to be looked into are already listed.
<@nirik:matrix.scrye.com>
16:43:53
not sure I follow... I mean to change the dvd/install media is pungi config/changes, to change the live media could be pungi but also lorax and other things... etc
<@jnsamyak:matrix.org>
16:45:16
yes absolutely this will require early on investigation right? for the places we need to make changes
<@nirik:matrix.scrye.com>
16:45:29
sooner the better
<@jnsamyak:matrix.org>
16:45:55
or we have to wait for the server group to tell us this is something we change which they have ideally mentioned in there server ticket
<@jnsamyak:matrix.org>
16:45:59
here
<@jnsamyak:matrix.org>
16:46:16
https://pagure.io/fedora-server/issue/126
<@jnsamyak:matrix.org>
16:46:22
!link https://pagure.io/fedora-server/issue/126
<@jnsamyak:matrix.org>
16:48:09
I can see the references on the document that kevin mentioned in the email or is it something else you are referncing to here? does that also mean you happen to have an idea on how to get these changes done?
<@jnsamyak:matrix.org>
16:48:27
I can see the references on the document that kevin mentioned in the email or is it something else you are refering to here? does that also mean you happen to have an idea on how to get these changes done?
<@patrikp:matrix.org>
16:50:32
"2. We need help in developing a detailed statement of work for each of the areas requiring change."
<@patrikp:matrix.org>
16:50:32
<@patrikp:matrix.org>
16:50:32
They need help in developing. And they already asked a question regarding Kiwi in the ticket so it sounds like they're looking into it and are welcome to ask if they have any questions.
<@patrikp:matrix.org>
16:50:32
<@patrikp:matrix.org>
16:50:32
"1. We need help in identifying all the areas within Fedora Project that would require change."
<@patrikp:matrix.org>
16:50:32
Kevin listed the areas in the mailing list and it's also copied over to the ticket.
<@patrikp:matrix.org>
16:50:32
From the original ticket.
<@patrikp:matrix.org>
16:50:32
<@patrikp:matrix.org>
16:51:32
I'm not sure what the insights from the investigation are supposed to be. "Change X, Y and Z"? It doesn't sound so simple.
<@nirik:matrix.scrye.com>
16:52:03
I guess ideally it would all end in a PR/PR(s)
<@patrikp:matrix.org>
16:53:24
Doesn't the proposal come first?
<@nirik:matrix.scrye.com>
16:54:57
I thought they already proposed the changes?
<@nirik:matrix.scrye.com>
16:55:10
but could be reviewed in a pr before merging too.
<@nirik:matrix.scrye.com>
16:55:25
but I would guess it would be a number of pr's... since it's different places
<@patrikp:matrix.org>
16:55:48
The ticket says they began research in preparation of a system-wide change proposal.
<@nirik:matrix.scrye.com>
16:56:01
ah.. ok.
<@nirik:matrix.scrye.com>
16:56:11
then yeah, misunderstood
<@patrikp:matrix.org>
16:57:02
So they're asking for help with their investigation, sounds like to me.
<@patrikp:matrix.org>
16:57:22
Before they make the proposal.
<@jnsamyak:matrix.org>
16:58:33
sorry i had a power cut
<@jnsamyak:matrix.org>
16:58:43
and yes eventually we have to make those changes
<@jnsamyak:matrix.org>
16:58:58
from what i read from the feedbacks
<@jnsamyak:matrix.org>
16:59:08
hence this investigation is not for them
<@jnsamyak:matrix.org>
16:59:19
but for us to be ready to make those changes once it comes
<@jnsamyak:matrix.org>
17:00:08
I mentioned this in document as well
<@jnsamyak:matrix.org>
17:00:13
If not already, get a quick glimpse of how composes work.
<@jnsamyak:matrix.org>
17:00:13
Think of this as an arc investigation and try to find out the things to do before actually implementing it. Note down all the necessary details and ask relevant folks for another pair of eyes, once that goes through a review, break it down into pieces and start working on it.
<@jnsamyak:matrix.org>
17:00:13
Task individuals with documenting the findings, highlighting areas that will be affected by the proposed changes.
<@patrikp:matrix.org>
17:00:57
Do you have a link to the change proposal?
<@jnsamyak:matrix.org>
17:01:25
but we are out of time, and we could take this to our releng channel, I really like to have such discussions not only in the releng meetinfs
<@jnsamyak:matrix.org>
17:01:40
i gave you the server link
<@jnsamyak:matrix.org>
17:01:47
earlier it has the changes proposed
<@jnsamyak:matrix.org>
17:02:01
!info Thank you all for coming.
<@patrikp:matrix.org>
17:02:07
Let's move it to a different chat. 👍️
<@jnsamyak:matrix.org>
17:02:10
!endmeeting