#meeting-1:fedoraproject.org log

<@siosm:matrix.org>

16:32:28

!startmeeting fedora_coreos_meeting

<@meetbot:fedora.im>

16:32:31

Meeting started at 2024-11-27 16:32:28 UTC

<@meetbot:fedora.im>

16:32:31

The Meeting name is 'fedora_coreos_meeting'

<@siosm:matrix.org>

16:32:46

!topic roll call

<@gurssing:matrix.org>

16:33:13

!hi gursewak

<@zodbot:fedora.im>

16:33:15

Gursewak Singh (gursewak)

<@jlebon:fedora.im>

16:33:31

!hi

<@zodbot:fedora.im>

16:33:32

None (jlebon)

<@ravanelli:matrix.org>

16:33:34

!hi ravanelli

<@zodbot:fedora.im>

16:33:35

Renata Ravanelli (ravanelli)

<@marmijo:fedora.im>

16:33:42

!hi

<@zodbot:fedora.im>

16:33:43

Michael Armijo (marmijo)

<@siosm:matrix.org>

16:33:48

!hi

<@zodbot:fedora.im>

16:33:50

Timothée Ravier (siosm) - he / him / his

<@hricky:fedora.im>

16:34:11

!hi

<@zodbot:fedora.im>

16:34:11

Hristo Marinov (hricky) - he / him / his

<@aaradhak:matrix.org>

16:34:40

!hi aaradhak

<@zodbot:fedora.im>

16:34:42

Aashish Radhakrishnan (aaradhak)

<@siosm:matrix.org>

16:38:55

Let's start

<@siosm:matrix.org>

16:39:10

!topic Action items from last meeting

<@siosm:matrix.org>

16:39:25

!link https://discussion.fedoraproject.org/t/fedora-coreos-community-meeting-minutes-2024-11-20/137979

<@siosm:matrix.org>

16:39:48

No action items from the last meeting

<@siosm:matrix.org>

16:40:10

Any topic we should discuss first?

<@siosm:matrix.org>

16:41:05

I vaguely remember that we should talk about the release schedule for the releases during the end of the year break

<@siosm:matrix.org>

16:41:27

But I don't see an issue for that

<@marmijo:fedora.im>

16:42:21

I brought that up in the CoreOS channel a few days ago. We can probably wait until next week to discuss when more people are here

<@siosm:matrix.org>

16:42:52

👍️ makes sense

<@siosm:matrix.org>

16:43:05

Can you file an issue so that we don't forget it?

<@marmijo:fedora.im>

16:43:15

Will do!

<@siosm:matrix.org>

16:43:42

Let's go to our currently listed meeting items

<@siosm:matrix.org>

16:43:51

!topic Configure kdump to exclude some coreos modules in generated kdump initramfs

<@siosm:matrix.org>

16:43:56

!link https://github.com/coreos/fedora-coreos-tracker/issues/1832

<@siosm:matrix.org>

16:45:21

ah, it looks like https://github.com/coreos/fedora-coreos-tracker/issues/1837 could be a solution for this one

<@siosm:matrix.org>

16:46:05

So, the general use case here is that when using kdump, we don't need most of the coreos dracut modules for the initramfs generated just for kdump usage

<@siosm:matrix.org>

16:46:13

it does not need ignition, etc.

<@siosm:matrix.org>

16:47:06

keeping those modules out as value as it makes the initramfs smaller and thus the amount of memory that has to be reserved for kdump on a node smaller and thus makes using kdump more attractive

<@siosm:matrix.org>

16:47:41

(as it takes less memory away from workloads/containers)

<@siosm:matrix.org>

16:48:58

related to https://github.com/coreos/fedora-coreos-tracker/issues/1729 as well

<@ravanelli:matrix.org>

16:49:13

when you say out, do you mean not load them?

<@siosm:matrix.org>

16:49:25

keeping those modules out has value as it makes the initramfs smaller and thus the amount of memory that has to be reserved for kdump on a node smaller and thus makes using kdump more attractive

<@siosm:matrix.org>

16:49:58

I mean completely not included in the initramfs generated for kdump

<@siosm:matrix.org>

16:50:09

they won't be in it at all

<@ravanelli:matrix.org>

16:52:23

Any cons? If this initramfs is generated only for kdump, it seems there is no issues in removing it

<@siosm:matrix.org>

16:53:29

I don't see any disadvantages right now. From the ticket, the question was mostly about where this would be configured and it appears that the kdump team is working on a solution for that so that should be good.

<@siosm:matrix.org>

16:53:50

Unless someone wants to add something, I think we can move on.

<@siosm:matrix.org>

16:54:43

!topic Platform Request - Apple native hypervisor

<@siosm:matrix.org>

16:54:49

!link https://github.com/coreos/fedora-coreos-tracker/issues/1533

<@jlebon:fedora.im>

16:54:59

this sgtm. i would probably analyze the size of the different modules and focus on the top ones instead of trying to be comprehensive, to reduce the maintenance burden also

<@jlebon:fedora.im>

16:56:50

i think dusty added this one because we don't have docs yet for it?

<@siosm:matrix.org>

16:57:17

Yes, appears to be the case. If folks are interested in this platform, a docs contribution would be appreciated!

<@siosm:matrix.org>

16:57:43

and I think that's it

<@jlebon:fedora.im>

16:59:45

any new f42 change proposals?

<@marmijo:fedora.im>

17:00:26

I ran the script yesterday and no new changes came through

<@siosm:matrix.org>

17:00:46

Thanks! Then let's go to open floor

<@siosm:matrix.org>

17:00:57

!topic Open Floor

<@siosm:matrix.org>

17:01:26

I'll close the meeting in 5 minutes if we don't have anything else :)

<@siosm:matrix.org>

17:03:23

gursewak: signing you up for next week meeting as JB will likely still be on PTO

<@siosm:matrix.org>

17:09:20

Alright, closing :)

<@siosm:matrix.org>

17:09:26

!endmeeting