#meeting-2:fedoraproject.org log

<@yselkowitz:fedora.im>

19:02:37

!startmeeting ELN SIG 13 Mar '25

<@meetbot:fedora.im>

19:02:38

Meeting started at 2025-03-13 19:02:37 UTC

<@meetbot:fedora.im>

19:02:38

The Meeting name is 'ELN SIG 13 Mar '25'

<@salimma:fedora.im>

19:02:40

!hi

<@zodbot:fedora.im>

19:02:42

Michel Lind (salimma) - he / him / his

<@yselkowitz:fedora.im>

19:02:47

!meetingname eln

<@meetbot:fedora.im>

19:02:48

The Meeting Name is now eln

<@yselkowitz:fedora.im>

19:02:55

!topic Init process

<@sgallagh:fedora.im>

19:05:02

!hi

<@zodbot:fedora.im>

19:05:03

Stephen Gallagher (sgallagh) - he / him / his

<@yselkowitz:fedora.im>

19:06:54

are people tied up in go/no-go too?

<@yselkowitz:fedora.im>

19:07:10

Stephen Gallagher: just noticed https://sgallagh.fedorapeople.org/dbs_status.html hasn't updated in a week

<@sgallagh:fedora.im>

19:07:44

Yeah, they are decommissionining the shell server that my sync script is running on.

<@sgallagh:fedora.im>

19:07:49

I'm trying to figure out what to do about that.

<@yselkowitz:fedora.im>

19:07:53

again?!?

<@sgallagh:fedora.im>

19:08:08

Yeah, looks like they're killing them ALL off

<@sgallagh:fedora.im>

19:09:21

We may need to just go ahead and move EBS to the Fedora OpenShift and worry about the build submission endpoint after the fact. (The worst case is submitting a lot of build requests that EBS ignores or Koji cancels for reuse of NVRs)

<@yselkowitz:fedora.im>

19:10:57

we can't leave that endpoint open, but I'm wondering if there's a way to use it within the openshift context?

<@tdawson:fedora.im>

19:11:09

!hi

<@zodbot:fedora.im>

19:11:09

Troy Dawson (tdawson)

<@yselkowitz:fedora.im>

19:11:23

iow something that could only be accessed with `oc` or the web console?

<@sgallagh:fedora.im>

19:11:26

yselkowitz: Sorry, I don't understand what you're asking

<@sgallagh:fedora.im>

19:12:06

<@sgallagh:fedora.im>

19:12:26

No. It's just a separate path on the built-in webserver.

<@sgallagh:fedora.im>

19:12:45

If we were using something like Apache, I suppose we could add auth to a subdirectory.

<@yselkowitz:fedora.im>

19:13:00

oh ☹️

<@sgallagh:fedora.im>

19:13:08

But this is just a simple python-twisted webserver. If we want authn, it has to be implemented in the EBS code

<@sgallagh:fedora.im>

19:13:43

The endpoint is VERY limited in what it can do.

<@sgallagh:fedora.im>

19:13:58

It can only trigger builds for packages that EBS already has on the lists from Content Resolver.

<@yselkowitz:fedora.im>

19:14:14

we still can't leave that open imo

<@sgallagh:fedora.im>

19:14:40

So yes, someone could try to DDoS it by constantly sending the same package name over and over, but we deduplicate in the code, so it probably wouldn't really succeed.

<@sgallagh:fedora.im>

19:15:23

The worst-case would be if someone managed to send the complete CR list to us just as we bumped the buildroot number. That would lead to an unplanned mass-rebuild.,

<@sgallagh:fedora.im>

19:15:27

Which is not great.

<@yselkowitz:fedora.im>

19:16:44

!info we need to revisit this as a possible solution to the above, but the trigger endpoint needs authn first

<@yselkowitz:fedora.im>

19:16:44

!info dbs_status is not syncing again

<@yselkowitz:fedora.im>

19:16:44

!link https://github.com/fedora-eln/eln/issues/11

<@yselkowitz:fedora.im>

19:16:44

!topic New business

<@yselkowitz:fedora.im>

19:16:44

!link https://github.com/fedora-eln/eln/issues/217

<@yselkowitz:fedora.im>

19:17:00

just to summarize the discussion we just had

<@yselkowitz:fedora.im>

19:17:08

anything else on this point?

<@sgallagh:fedora.im>

19:17:35

One thing

<@sgallagh:fedora.im>

19:17:57

I will not have any cycles to do any work on EBS until at least May.

<@yselkowitz:fedora.im>

19:18:42

understood, we have some new people coming on board that I hope will be able to take on our tooling

<@sgallagh:fedora.im>

19:19:11

I can try to carve out some time for code review here and there. I can't promise more than that.

<@yselkowitz:fedora.im>

19:19:22

ack, thanks for the headsup

<@yselkowitz:fedora.im>

19:19:44

!info kernel-rt packages are now available in RT and NFV repos

<@yselkowitz:fedora.im>

19:20:09

!info RT repo is now available for aarch64, with kernel-rt (but not kernel-rt-64k yet)

<@yselkowitz:fedora.im>

19:21:30

^^^ that mostly completes the RT and NFV repos, which were deficient until now. that leaves HA still needing work (see #229)

<@yselkowitz:fedora.im>

19:22:40

go/no-go just ended (f42 beta is go!)

<@salimma:fedora.im>

19:22:56

we might as well stay here right

<@yselkowitz:fedora.im>

19:23:11

yeah we'll stay here for today

<@yselkowitz:fedora.im>

19:24:16

!link https://github.com/fedora-eln/eln/issues/234

<@yselkowitz:fedora.im>

19:24:16

!info llvm-20 has landed in ELN with llvm19 as compat, most packages just need a rebuild

<@sgallagh:fedora.im>

19:24:24

The sync script is back up and running for now, but I don't know how long it'll stay running. The machine it's on only has a six-day uptime. I'll try to keep an eye on it at least until it's decommissioned at the end of the month

<@yselkowitz:fedora.im>

19:25:21

thanks!

<@yselkowitz:fedora.im>

19:25:46

anything else for new business?

<@tdawson:fedora.im>

19:26:24

Nothing from me

<@yselkowitz:fedora.im>

19:26:44

!topic Old business

<@yselkowitz:fedora.im>

19:26:58

!link https://github.com/fedora-eln/eln/issues/192

<@yselkowitz:fedora.im>

19:27:18

do we have a quorum to continue the votes on the background?

<@tdawson:fedora.im>

19:27:42

I think there is just the 3 of us ... does that constitute a quorum?

<@salimma:fedora.im>

19:27:54

let's see - Yaakov, Troy, Stephen, me ... who else is here

<@salimma:fedora.im>

19:28:31

Davide sends his regrets, he's at the office today which means it's "lunch with colleague" time

<@yselkowitz:fedora.im>

19:29:16

we don't have official rules on this, I was hoping for vast majority of the regulars

<@yselkowitz:fedora.im>

19:30:01

defer this another week?

<@tdawson:fedora.im>

19:30:29

Ya ... although I might start getting the rpm setup, so when it passes I can just plop in the picture.

<@yselkowitz:fedora.im>

19:31:30

sure, and I would like to suggest naming it `fedora-eln-backgrounds`, so that all the `fedora-` packages are grouped together and easy to notice when filtering out what not to branch come c11s

<@tdawson:fedora.im>

19:32:04

Sounds good to me. I'll put that in the ticket.

<@yselkowitz:fedora.im>

19:32:50

!info new prototype has been posted. decision deferred another week due to lack of quorum

<@yselkowitz:fedora.im>

19:33:49

!link https://github.com/fedora-eln/eln/issues/209

<@yselkowitz:fedora.im>

19:34:41

Stephen Gallagher: do you think the package.cfg issues with the SB pkgs would be connected to your issue yesterday?

<@yselkowitz:fedora.im>

19:36:25

!action Yaakov to ping releng on granting SB privs to EBS

<@sgallagh:fedora.im>

19:38:21

Sorry, was looking at another screen.

<@sgallagh:fedora.im>

19:38:52

I don't think so. The exact OPPOSITE problem seems to be happening there for some reason.

<@sgallagh:fedora.im>

19:39:14

In my case, packages that should NOT have been built for ELN were triggered, whereas the secureboot packages aren't triggering for ELN when they are explicitly listed.

<@sgallagh:fedora.im>

19:39:30

Except it works when *I* do it, and not when the secureboot maintainers do.

<@yselkowitz:fedora.im>

19:41:01

ok we'll see what releng comes back with, perhaps it will be moot

<@yselkowitz:fedora.im>

19:43:31

!topic Next Meeting

<@yselkowitz:fedora.im>

19:43:59

after last week, I thought we should check the next week in advance for conflicts

<@yselkowitz:fedora.im>

19:44:37

the next meeting would normally be next Thursday 20 Mar 15:00 EDT (US/Canada)

<@yselkowitz:fedora.im>

19:44:53

any conflicts for then?

<@salimma:fedora.im>

19:45:12

someone else should answer that, I personally have no conflict even today

<@tdawson:fedora.im>

19:45:54

No conflicts for me.

<@yselkowitz:fedora.im>

19:46:05

!info next meeting is on regular schedule, Thu 20 March 15:00 EDT

<@yselkowitz:fedora.im>

19:46:14

!topic Open floor

<@yselkowitz:fedora.im>

19:46:32

anyone have anything else to discuss today?

<@tdawson:fedora.im>

19:46:44

Nothing from me

<@yselkowitz:fedora.im>

19:49:03

guess we'll end early then, hopefully next time we can get more attendees

<@yselkowitz:fedora.im>

19:49:19

thank you all for joining today

<@yselkowitz:fedora.im>

19:49:21

!endmeeting