Meeting started at 2024-07-10 17:00:26 UTC

The Meeting name is 'fedora-server'

let's wait a moment for everybody to shop up. I’ll post the agenda in about 2-3 minutes.

!hi

John Himpel (jwhimpel)

Welcome John!

Obviously, we are not too many participants today. But let's wait a bit.

!hi

Tomáš Hrčka (humaton) - he / him / his

John Himpel: by the way, did you got the book about python which I mail to you?

Welcome Tomas! I missed you a lot!

I got your book. Haven't had a change to use it yet. Hopefully next week.

tons of work everywhere :/

yeah, same here.

and PTO and conferences. Will try to make my presence better.

jednorozec: Can we have a email discussion about the Ansible driven performance test siut, you mentioned some weeks ago?

I have to prepare myself a bit before

OK, we are 3 now, and we should be at least more than three. I suggest, we start with Open Floor and can discuss some topics spontaneously?

OK, let's start with OpenFloor

John Himpel: Do you think we can continue with NFS / Ansible next week or better in 2 weeks (or 3)?

Oh I now remember some email thread.

Hopefully, next week. I have a simplified NFS Server & NFS Client working. But I need to allow for more options. I also need to figure out how to create a "Ansible Collection" instead of the simpler "Ansible Role"

There's a discussion now in the "Development" M/L regarding generating the KDE aarch64 live iso image using KIWI. That help us with migrating Server to KIWI.

That discussion involves FESCO being asked to elevate KDE ARM to be a blocking release. There is some pushback unless the ARM folks agree to provide better support. I will follow this discussion as I think it will eventually affect Server.

John Himpel: As I read it is is specifically yout the VM image, not the iso image to boot on hardware.

I started working on kiwi definition for server dvd

The ARM image in question is a raw file, not an iso (unless I missed something).

but its just template no builds done yet

jednorozec: ++1

pboy gave a cookie to humaton. They now have 62 cookies, 8 of which were obtained in the Fedora 40 release cycle

it does not matter kiwi should be able to produce multiple artifacts

https://osinside.github.io/kiwi/building_images/build_simple_disk.html

Yeah, *virtual* disk image, but not a "real" ?

SUSE has an "add-on" to KIWI that claims to generate "real" images.

OK, didn't know that

what do you mean by real image?

But back to NFS / Ansible: So I plan at least a short topic next week.

Fine. I'll try to get my work into our repo by then.

"Real" image = boot on hardware, not in a virtualized environment

jednorozec: Could you help us with an issue ticket, https://pagure.io/fedora-server/issue/114 ?

What would you call a "live iso" image? That's what they are talking about at FESCO today.

I don't know enough about that area. What can we do here?

btw you can copy qcow image to hdd using dd and boot from it

John Himpel: QWorkstation has to types, one live image booting on hardware and one in a virtualized environment, as far as I know. But I may be wrong.

Anyhow that issue you mentioned

!ticket fedora-server 114

Issue querying Pagure: Issue not found

hm

Never tried that. But ok, you can dd a complete, preinstalled image, but not "compose" an installation as Anaconda does, I think

ok so I am looking into the issue

Thanks a lot!

!wikipedia says M/S is phasing out LLMR. If that's complete, then we ought to either the systemd folks to remove it. They will probably want a patch.

s/either/ask/

looking at the discussion on github they dont want to remove it

https://github.com/systemd/systemd/pull/28263

Yes, there is a long ongoing discussion about LLMR. Unfortunately, I don't know anyhing about this. :-)

from the PR "now we will do mDNS->wait->then-LLMNR-NBNR"

But we should reply / act to the issue in a nice and constructive way.

they did LLMR first previously and updated the code

so the sollutions is to add LLMNR=no to /etc/systemd/resolved.conf

I think the default config is comming from systemd package right?

jednorozec: Could you deal with the issue? Probably close it nicely, because it is F39 and more or less outdated. But at the same time handle in constructively? Just closing it feels unpolite to me. And not not honor the commitment of the OP.

Let me write comment there, because they are also talking about other releases.

And propably the systemd parameter is a copnstructive solution? Would it be system wide for all editions, or is it useful specifically for server?

jednorozec: Thanks!

that is the thing its global if changed in package, but we might change the config during compose...

Well, any other topic at the moment?

I will look into options and write a comment there

jednorozec: ++1

pboy has already given cookies to humaton during the F40 timeframe

oh it's limited :-)

Yeah, 1 per release per user :)

If we have nothing else at the moment, we should probably close the meeting. But I think it is very useful, to have such an open opportunity. We should do it maybe once a month.

3

2

1