Meeting started at 2026-01-07 18:00:57 UTC

The Meeting name is 'fedora-server'

Happy New Year to everyone! Let's start the new year as well as we finished the old one.

!hi

Jocelyn Gould (korora) - she / her / hers

I've added one topic I forgot earlier today.

As usual, let's wait a moment for everybody to show up.

I'll post the agenda in 2-3 minutes.

!helo

!hello

Emmanuel Seyman (eseyman) - he / him / his

Happy new year to all!

Happy new year everyone!

OK, nirik is lurking around as usual. So we can start.

Sorry, I didn't manage to mail the agenda proposal in advance.

I will do better

!hi

John Himpel (jwhimpel)

Any comment / idea?

I'm good

OK, let's start.

I see here, korora, John, Emmanuell, and Paul & nirik in the Background. So we are good

I opened a PR regarding our webservice issues / topic. Unfortunately, I have at least one error in the rather complex spec file, in the %file section, I think.

https://src.fedoraproject.org/rpms/httpd/pull-request/45

The the log file is noting for the faint hearted. It reminds me on my early days when working with IBM big iron with Assembler and Fortan. You must really be used to it. Fortunately, Kevin was helping out.

I'm not sure, when I'll be able to work on it. Maybe, not until end of January. If anyone feels like embarking on a log file adventure, you're welcome.

I'll try and take a look tomorrow

That would be really really good!

Another topic, Fedora Flock, end of CfP is end of January.

We should discuss it later with topic 4#

Will you be there, Peter?

Yes, I plan to join Flock.

I suspect this counts as an announcement: Voting for FESCO members ends tonight. If you can please vote!

I did it this afternoon.

Did it yesterday

If anyone else needs to vote, you are excused from here for 10 minutes. 😀

I have some issue with the new graphics theme. My MacOS Safari is unusable with that. But Firefox works.

Any new idea / comment at the mean time here? New experiences with the forge?

The browser problem is strange. I thought the days of the browser wars were over.

I'm liking it so far

My only experiences are the parts abut learning how to use git with others. LOL

Yeah, Git is always fun

I couldn't find out how to create personal repos. I suspect it can't be done

!Hello

I have the same question. I would like to create some repos for my work, e.g. a RPM for TomEE. Last time I looked, there was a discussion about the criteria a personal repo should meet.

Hi mowest!!!

Well, so I think, we can close the issue 173. Any objection?

Is the new forge only accessible through https? Or ssh? Or Either?

John Himpel: currently https only.

Okay to close issue 173

And a special access token, you can generate in your account.

Seems okay to close.

!agreed: We close issue 173.

Peter Boy (ServerWG, Docs): I already have obtained the access token. Just need to find time to try and login.

In the ui you log in with your usual password.

I agree on closing 173

When you push to the repo, you are ssked for your user name and password. As password you must pass in the token.

Just one time, then git knows about it and provide it when needed.

Peter Boy (ServerWG, Docs): Thx

OK, let's proceed.

I noticed today, that the stg address points to the main site, too. That's the default for all subsites that doesn't use an stg branch.

o I will remove stg at all. Or has someone something on stg that they would thes to save?

If I remember, korana as had apreversion there and wanted to work on it?

I have nothing on stg to save, I also have a backup of the stg branch

Sorry, not korona -> korora

OK, so I can remove the stg branch now.

!agreed: The stg branch can now finally be removed.

+1

Hm, zodbot is tired again.

I did vote this morning as well, thanks for the reminder to do so.

Let's proceed

Tracking ticket: https://forge.fedoraproject.org/server/tickets/issues/178

Now comes the exciting part.

What shall we do? (not with a drunken ...)

I mean, that part is fun too. (I just don't happen to have a long boat handy...)

Now that's stuck in my head... Thanks for that. LOL

I think the current plan is good. is the 44 release in the first part of the year?

I have an x86 machine that I can dedicate to testing homelab installs. I'm unsure how to navigate getting our Fedora Infra to create a new iso or image. I'm guessing it starts with a package list, and then goes from there. What do I need to learn to start the ball rolling?

I have not found a resonable SBC that I want to purchase for testing ARM images though. So I would focus on this point on the x86 platform.

I should be able to test the ARM boards I already have

mowest: I think, wie should use kiwi to create an installation image. I can provide a kiwi server, where we can collaborate to get it running.

And yes, my first idea was to concentrate on ARM, the Argument: environment friendly.

Great. So I should look into learning something about kiwi?

I did some comperison between newer ARM and Intel N100 boards. The Arm power consumption is about 50% of Intel (depending on usage, of coarse).

I agree that running on ARM boards would be great, but homelabs also run a lot of old desktops or servers from companies that get new machines and those will be x86.

mowest: Yes, kiwi.

mowest: agreed regarding old server / hardware. We have to work on X86, too.

I would love to find a SBC that we can get running on well, like really well that is around $100 US. That would be awesome.

My son just moved our whole homelab over to RPI 5 with 8GB of RAM, and it is awesome, but we have to run on Raspberry PI OS because of the lack of compatability with Fedora.

My son just moved our whole homelab over to RPI 5 with 8GB of RAM, and it is awesome, but we have to run on Raspberry PI OS because of the lack of compatibility with Fedora.

mowest: For 100 you get a fairly performand SBC, e.g. Rockship / Radxa Roc PI 4 a or b.

It is not the latest generation, but the previous. And it is a lot more powerful as the Rasp Pi 4

Rockship -> Rockchip (I' sailing in my free time)

In the past, we were usually not very eh ... "consistent" with our planning.

But a step back, how do we want to proceed?

Is this what you are talking about? https://www.amazon.com/WayPonDEV-Single-Compter-Support-Twister/dp/B0BX9FBGNV/

Yes, my main issue is that there's a small timeframe during which to test and it is sometimes hard to get to it in time

mowest: That's my model: https://www.reichelt.de/de/de/shop/produkt/raspberry_pi_4_b_4x_1_8_ghz_4_gb_ram_wlan_bt-259920?PROVID=2788&gad_source=1&gad_campaignid=18342381572&gbraid=0AAAAADwnxtY7MS-IJyQArlDwB8xUUCM1w

about 70 Euros.

Emmanuel Seyman: agreed.

But how can we do better?

I think, we should concentrate on max. 2 item and high priority.

One can be the home server, the other one must be a professional related topic.

A reminder about the schedule cannot hurt

Yeah, maybe we try to make a plan with milestones first?

Let's try that

Can we agree on homelab server and PXE boot? or homelab and NFS Ansible?

Definatly homelab and PXE Boot

I think PXE/NFS are two that should coincide (from a standpoint of use.

What would homelab server mean?

+1 to Emmanuel Seyman

homelab server: for usage at home: private date, media server, something like that. And including semi professional use (for free lancer).

I have a proposal at ...

https://hackmd.io/9FjTMT67Q_Cut0MgW91aZg

OK, homeserver / homelab & PXE complete doku and Ansible support.

Reminder for the F44 schedule: https://fedorapeople.org/groups/schedule/f-44/f-44-key-tasks.html

+1

Emmanuel Seyman: yeah, F44 may be a bit short range.

I would be fine with F45

We might be able to get the PXE stuff done for 44, but i think a hard goal of 45 might be better

I think this is an admirable goal, but in previous conversations, I recall that changing the package list and generating new iso's for testing is an exercise in "black magic". I think first we ought to transition to using KIWI for generating all deliverables. Right now it doesn't generate iso's (at Fedora). SUSE has a module that proports to generate isos as well at qcow, etc. But it is written in Python and my Python foo is not sufficient to do the port.

We should set some (small) goals for F44. We've haven't even branched yet...

John Himpel: exactly because that I think we should start with ARM and kiwi. That not that black magic.

And as far as I know there is currently no plan to migrate everything to Kiwi.

Peter Boy (ServerWG, Docs): Are you talking qcow, etc and NOT iso for arm?

I would like to have the dnsmaq/pxe boot stuff finalized by 44. (I've been working on it, but cognitive issues are... slowing me down.

Emmanuel Seyman: a small goal would be to synchronzie net and DVD. Nirik and I want to do that.

John Himpel: Yes, qcow2

iso would be a second step.

Sorry pulled into a brief meeting, but I agree to limited focus, I think that would be great.

Maybe we use an existing live medium and push an image

Jocelyn (she/her) (Server WG: Docs): What type of image needs to stored on the pxe server for that to work? I've never tried to implement that functionality.

I use the kernel and initramfs and then basically do a network boot

you'll need a kernel, an initrd and a link to the yum repository of the packages

I *think* you can deliver a local mirror or isos, but I've not branched into that yet

Folks, our time is more or less up.

Indeed

To summarize:

For F44, a small goal: synchronize net and DVD boot. For F45, home server and PWE boot (documentation and Ansible).

Can we agree about that?

quick question : can someone point me to documentation about NetworkManager's dnsmasq plugin?

Emmanuel Seyman: Look at Fedora Server Edition documentation :-)

+1

Our documentation was for F36. I was hoping for something more recent

https://docs.fedoraproject.org/en-US/fedora-server/administration/dnsmasq/

Yeah, but is is still working.

It's one of the things i'm going to be working on and trying to update as I do the PXE stuff. I have goals for this I'll get with you about them

I will sent you some of my notes about dnsmasq plugin!

Yeah but I wanted to know if there were any new features since then

Please do.

Can you send me your notes as well, please?

Yes, I'll do.

So I take it, we agree upon my summerize.

We should write a working plan next. I can do it for home server.

a proposal, of course.

Who can do that for PXE?

Agreed +1

I can write the plan

I'll get with you on it.

Sure

Of course we cooperate! Nevertheless, it is mostly one person who has to write an initial proposal, so we have something specific to discuss about.

Anything else?

Probably we should close in some minutes at latest.

I'm all good. I have on my todo, learn about kiwi. :-)

I would really like to have dinner before my Perl meeting

I have reviewed the Hackmd doc as well about the homelab effort.

OK, so let's close now.

It was one of our better and productive meetings, I think!

FYI, I don't think I can attend the next meeting

OK, yes, we get used to it :-)

I think a lot of discussion about out topics today is in 2 weeks. We all need some time to do the work.

So, bye bye for now. And let's meet in our Matrix room in the mean time.