Meeting started at 2026-03-11 17:00:40 UTC

The Meeting name is 'fedora-server '

!hello

Emmanuel Seyman (eseyman) - he / him / his

!hi

Peter Boy (pboy)

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

Welcome to our weekly Server WG meeting.

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

!hi

John Himpel (jwhimpel)

Welcome Emmanuel, welcome John and welcome Nirik who is lurking around as usual.

So I think, we have our quorum and can start.

We discussed that previously, so I think there is nothing to add or to remove ??

OK. Let's start

meetings overview:

Regarding the action, I'll include the list in our

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

This means that the clock is now ticking to move the projects involved forward.

We should try these infos and works over the next days, so we can discuss it at next meeting.

That's all from me.

Any comment or any addition?

Same here

Regarding Flock, I think Emmanuel, Alexander and me are the ones to do the work. And I hope Nirik and Stephan will be present as well.

I suppose, for our US-non-red-hat members is may be too much to travel to Europe these days.

OK, lets proceed.

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

We had a lot of actions here:

3. !action korora: Test the F44 Beta single-disk installation on both UEFI and BIOS, and perform KVM virtualization tests.

4. !action eseyman: Test PostgreSQL and MariaDB on a fresh installation of F44 Server.

1. !action mowest: Test the F44 Beta installation on his Dell desktop (either BIOS or UEFI) with two hard drives if possible.

2. !action pboy: Test the F44 Beta RAID installation (BIOS and/or UEFI dependend on mowest’s hardware capabilities) and also test on an aarch64 SBC.

5. !action: All: While testing, make note of any documentation that needs to be updated.

What is the current status?

I tested BiosBoot single drive default as well as Raid. Everything worked.

Pg and MariaDB installed fine. I was able to create databases and users in both

And didn't you test UEFI single drive, too? Or do I remember that falsely?

yes, this was a UEFI single drive laptop

So I will test UEFI RAID after our meeting.

Korora tested the KVM VM and found no problemes.

What about aarch64 SBC?

mowest: Are you online?

I guess, the aarch64 testing is still left.

I can do that later, too. I have 2 currently unused devices here.

Well, nn summary, the tests have been successful so far, but UEFI Raid and aarch64 are still missing.

So, I think we are done here, arn't we?

I think so

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

I think, we have here to align our ideas and plannings. In the ticket, there are 3 proposals.

I hope that Emmanuel's initial ideas are now also reflected in this.

I need to contact the maintainers of timeshift in Fedora. Will do that tomorrow

Yeah, and do you agree with the proposals?

And maybe we have a better title / wording for each?

Yes, I'm good with the proposals

I hope we have aligned our ideas of "steamlining backup&restore". 😀

OK, any objections?

John?

It seems as though each scenario requires a different solution. My needs for backup/restore are rather minimal. I use rsync for volatile data and ansible playbooks for non-volitile data. So my needs are pretty basic and I don't have much experience with the more sophisticated proposals. So I'm not sure my opinion would be very well informed.

Also, I think most database backups/restores require package specific solutions.

Ok, but you obiously don't object against one of the projects. And how to manage databases, is a matter of implementation, I think. According to our technical Specs Postgres is what matters. But mysql/mariadb is important for many, too. So we may focus on both of them.

No objection

Agreed: The working group agrees with the proposals in Ticket #184.

Agreed The working group agrees with the proposals in Ticket #184.

!Agreed: The working group agrees with the proposals in Ticket #184.

!agreed: The working group agrees with the proposals in Ticket #184.

OK, zodbot is not willing today.

We have to agree about who is doing what. Es discussed so far:

Strenghtening update: Emmanuel & Peter

Streamling. Emmanuel and Jocelyn

FTR, I'll be concentrating on the backup & restore ansible roles

I filed https://github.com/robertdebock/ansible-role-backup/issues/4 yesterday

homeserver: mowest and Peter

LocalKDC abbra & ??

Emmanuel Seyman: Yes, That is part of the project "streamlining", isn't it?

yes

Well, do we agree upon the pairing of people for the projects?

that looks good to me

Emmanuel Seyman: would you join the LocalKDC?

Se we have always 2 leads for each projects

I'm actually quite busy at the moment, mostly on Perl-related things and do want to overcommit

OK, same for me, not Perl but e.g. Docs

So, we leave that open at the moment.

I mean, the LocalKDC project

mowest: Welcome, you are online, I see.

Do you agree with our pairing?

Yes, just got on

!hi

Jocelyn Gould (korora) - she / her / hers

!hi

Steve Daley (mowest)

Hi Jocelyn!

the internet is stable at the moment

Sorry about four more weeks of hit or miss participation for me because of work obligations.

Re F44 Testing: I have not gotten a chance to do any thing with the Beta, I will hopefully get there this week. My health has led me to be... not very productive

I like the idea of pairing so that someone can give updates if the other can't be there.

So we agree upon: proposal !agreed about projects leads: Strengthening Server updates eseyman & pboy, Streamlining regular Server backups: eseyman & korora, Homeserver spinn-off: pboy & mowest

+1

+1

All these projects are part of out Flock activities. So they are very important and time restricted,

!agreed: Projects leads: "Strengthening Server updates": eseyman & pboy, "Streamlining regular Server backups": eseyman & korora, "Homeserver spinn-off": pboy & mowest

+1

Well, next topic:

The floor is open

I've not seen any input on templates for ticket types. I am going to look around and other aspects of the project and see what they have and what we can borrow

Yes, "borrow" is always a good idea!

What concerns me somewhat is how we can move forward with our Ansible projects.

We have a lot to do the next months.

I have no idea about it.

So I wil say that I stopped using ansible to update my machines as I think that was part of what led to my server becoming inop

Well, that is not the goal of Ansible 😀

Tell me about it. LOL

Jocelyn (she/her) (Server WG: Docs): can I convince you to give it one last chance?

Probably.

Jocelyn (she/her) (Server WG: Docs): I would also volunteer to help with your ansible issues.

Our time is up. Let's close on time today.

bye

And continue discussion in ou Matrix room.

bye bye