Meeting started at 2026-02-25 18:00:13 UTC

The Meeting name is 'fedora-server '

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

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

Welcome to our weekly Server WG meeting.

!hi

Jocelyn Gould (korora) - she / her / hers

!hi

Emmanuel Seyman (eseyman) - he / him / his

!hi

Steve Daley (mowest)

!hi

John Himpel (jwhimpel)

OK. welcome everybody.

I'm just a bit distracted. My Apple search app just informed me my laptop was turned on in Bruessels exactly at the same place as it was after the "kidnapping". Wondering what I can do now.

But let's start.

Besides the fact, that it is no longer branched, but Beta, we already basically agreed about it. Anything to add / remove??

OK. let's start

Not from my end

Nothing new from me.

Nothing new from me. I'm going to do testing on virtualization stuff tonight

https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2026/

The state of actions is on our WG page at

I have a spare laptop I secured for testing. I will start this weekend

I can dust off my old BIOS boot equipment and test it over the weekend.

My testing rig is still on my desk,

And I can test an aarch64 SBC (Rockchip).

I have an old Dell Desktop that I will use as my testing rig.

mowest: is it a bios boot or UEFI?

I think it might be bios boot, but I'm unsure how to tell the difference to be honest with you.

In our installation script, there is a query

my hardware can do either bios or uefi

Wait a moment:

Another way to tell is if you do a bios install there will be no /boot/efi diectory

I think this old Dell can be either, but I think that UEFI doesn't often work for the install of Fedora on this machine.

# [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS on the command line

mowest: can you post on Matrix, what you can test, bios Boot or UEFI? And do you have 2 HD for testing RAID?

Is there something before "[ -d" that looks like an incomplete bash command.

no, it is the root command prompt

"[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS" is standard bash

I just have two hard drives, but I often install at one the root drive, and the second is the data drive.

They are different sizes

Thanks for this command Peter Boy (ServerWG, Docs) and Emmanuel Seyman

For testing the installation different sizes are no problem. The smaller one is the size of the raid.

I have to step away from the keyboard for 10/15 minutes. BRB.

I only have single drives in all of my machines, so I'm no good for RAID testing

Jocelyn (she/her) (Server WG: Docs): I guess, you have UEFI?

I can do both

Oh good! Please, do both.

and i'll get the virtualization tests

Then can I focus on testing raid installation.

Can somebody test the KVM? And please, check if the partition with the root FS is of type LVM and there is no gap 0f 16b or 16m between the partition table and the start of the disk and/or a gap between the first and the second partition

I will get the KVM tests

OK, so we've allocated the work. 👍️

Maybe, we can talk about our findings on Matrix.

Anything else here?

I think we have it covered

proposed !eseyman ??? (please help here)

proposed !action pboy will test on aarch64

proposed !action Jocely will test single disk on UEFI and BIOS and KVM

proposed !action pboy will test RAID on bios and/or UEFE, depending on what mowest can do

proposed !action mowest: will test either bios or ufi depending what his test equipment allows

OK, let's wrap up:

+1

+1

!action mowest: will test either bios or ufi depending what his test equipment allows

!action pboy will test RAID on bios and/or UEFE, depending on what mowest can do

!action: Jocely will test single disk on UEFI and BIOS and KVM

!zodbot ???? sleeping???

● send-message <room_id> <text> - Send a message to a room

● list - List Rooms this bot is in

● leave <room_id> - Leave a Room

● !zodbot <subcommand> [...] - Admin Commands

**Usage:** !zodbot <subcommand> [...]

● join <room_id_or_alias> - Join a Room

!help

!help

OK, no help. :-)

here are the commands

was about to do that, thx

!action pboy will test RAID on bios and/or UEFE, depending on what mowest can do

OK, so we have it now. Obviously, zodbot doesn't like a space in front of !

it does not like a space, but it does not mind text

saying from expierience

And please, while testing, have a look on our documentations and make note, what we have to update.

So I guess, we can proceed?

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/186

Shall I do a !link?

yes, please

Yes, that's the place where we should track our findings! We should try to make it better as the last release. Se we have as early as possible an overview obout issues or bugs, and don't need to make a fuss at last minute.

An we either should collect the doc update requirements here, too.

Sounds like a plan

(If needed)

Btw, is a Forgejo issue template planned?

(maybe also an issue chooser, as seen in a screenshot I will send)

Not specifically, yet. I'm still writing my doc about forgejo installation on Server. There is an issue with your rpm

But it would be good to have a template !!!

Peter Boy (ServerWG, Docs) I'll start working on that

I think that would be a good idea.

That looky wonderful! We should try to develop that for our various issues.!

Thanks Jocelyn (she/her) (Server WG: Docs) for volunteering to create something like that.

I can find the template for the design team since there is a PR open

Nik Nikovsky: In short about the rpm: you create a elaborated app.ini. That prevents the configuration sreen, so yopu can't create the admin user. You either have to do it on CLI (needs to be documented)or you can patch forgejo not to look at existence of app.ini, but of admin user to come up with the configuration screen.

I was never talking about any sort of RPM..?

I just showed what the infra team has on their issue tracker

https://forge.fedoraproject.org/design/tickets/pulls/2

Oh, sorry, a Nik created the rpm, seems to be a confusion on my side.

[@nbhirud:matrix.org](https://matrix.to/#/@nbhirud:matrix.org) seems to be the only other one in this room

OK, thanks. I'll take a look. :_)

Let's continue with next topic.

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/184

We have to discuss, if we agree upon the project goal proposal. See the wiki page more details.

I propose we punt the decision to next week and spend this week reviewing and discussing in our matrix channel

The wiki page ?

Emmanuel Seyman: You are the project lead

Emmanuel Seyman: https://forge.fedoraproject.org/server/tickets/wiki/Streamlining-Backup-%26-Restore

I just wanted to write documentation about duplicity, BackupPC and rsync+tar

and the backup/restore roles in my ansible rpms

OK, I see, we need more discussion. Let's punt it to next week and discuss on Matrix.

+1

+1

+1

OK, next topic.

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/185

There is a wiki page, too:

https://forge.fedoraproject.org/server/tickets/wiki/Planning+a+home+server+%28or+homelab%29+spin-off.-

A few comments have already been added to this issue. I liked the points made by others.

I believe I still need to research kiwi and learn how spins are created, and what we have the ability to control as far as the installed image.

Yes, I agree, we should consider BTRFS. There are Pro and Cons. Pro: it is easier for part time homelab admins. Con: we wight want to keep it as much similiar to the professional version as possible.

I think, the homelab admin has more weight.

First, wie have to agree about the plan and the goals, as off wiki part one and two

BTRFS for normal filesystems is fine with me. However, there are still cautions about using it for database storage. Would probably need to have a separate filesystem for that functionality.

I would like to see the home server be as close to the minimal install as possible with clear documentation for installation of suggested/supported services.

I didn't know about the WIKI entry till now. I will look at that with more depth. I can put some thought into the goals.

Should we put our thought into the wiki or into the ticket?

John Himpel: Do you have references to BTRFS and databases that I could read up on, I have not heard that? In the home lab groups that I am a part of there has never been anything said about database issues in the home labs using BTRFS.

I think, into the wiki, in this stage of planning.

I don't have one handy, but in the past couple of months I have read comments about performance in databases on BTRFS.

Okay, so use the one wiki page to collect all of our thoughts, and then we can decide together the top 1-5 priorities?

mowest: I can post the link about this. I have to search my notes.

Does everyone else agree with this?

And John, would be helpful if you coult post your links, too

+1 for wiki

+1 for wiki, we can use it like a HackMD doc I would think.

yes, include as alternatives, or addons

Time is up. OK, so let's punt this, too. (Nik, your turn. :-). )

Thanks!

niknikovsky gave a cookie to pboy. They now have 47 cookies, 6 of which were obtained in the Fedora 43 release cycle

Let's have at lease a short open floor

Above all, many thanks to Nik! Would great to see you next week again!

As in easy for a beginner to use and perfect for education

I think fedora server could be like Ubuntu server.

I just patrol Element sometimes and help if needed

Plate is full for me with my focus on getting my thoughts into the Home server spin WIKI.

I have nothing to add to the hole in the floor...

Peter Boy (ServerWG, Docs): Note on the wildfly web pages under the heading of "guides" is an discussion of using their ansible role for installing wildfly.

Regarding server: Basically we aim at the professional usage. In the back auf my head I'm planning an office spin-off aspart of the digital Sovereignty initiatives in Europe

John Himpel: Good to know, that's on our plate, too.

I see, fedora could make an "educational" ish release for educational use

bye

OK, let's end. bye bye everybody. Let's meet in our Matrix room the next days.