Meeting started at 2026-08-26 17:00:10 UTC

The Meeting name is 'fedora-server '

!group members server-wg

!hello

Emmanuel Seyman: Emmanuel Seyman (eseyman) - he / him / his

!hi

Ro: Rowan Puttergill (goroboro) - he / him / his

!group members server-wg

Members of server-wg: Alexander Bokovoy, Adam Williamson, Paul Maconi, Brett Weir, Emmanuel Seyman, Rowan Puttergill, jwhimpel, Kevin Fenzi, korora (@korora:fedora.im, @korora1981:matrix.org), mowest, ngompa (@conan_kudo:matrix.org, @ngompa:fedora.im, @pharaoh_atem:opensuse.org, @ngompa:kde.org, @ngompa:almalinux.im), Peter Boy, Stephen Gallagher

!hi

Jocelyn Gould (UTC-4): Jocelyn Gould (korora) - she / her / hers

!hi

Ro: Rowan Puttergill (goroboro) - he / him / his

OK, we already meet our quorum. So let's start.

!hi

Brett: Brett Weir (brettweir) - he / him / his

As of our Matrix discussion we came up with the following agenda

We already discussed the agenda, so I think, we can start.

Regarding the action, see the list in our

meetings overview:

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

The current status:

The recordings of our Flock talks are now on Youtube:

https://www.youtube.com/watch?v=-M_5iQah5VA

https://www.youtube.com/watch?v=cQI0Ta8VOMc

Sadly, the first one has no sound

Great news!

Oh, besides the sound issue

Something else to announce?

OK

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

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/193 (image issue)

Ro: Do you gtake over?

Also https://forge.fedoraproject.org/server/tickets/projects/701

So Emmanuel has shared the new project for new features... this is basically tracking tickets for features that he identified as important for Server

!hi

John Himpel: John Himpel (jwhimpel)

these are already in progress and some completed already. We could really do with help testing... just self-assign tickets or if a ticket isn't on the board already, please just add it

for the latest build, I have updated all of the existing tickets in the project at https://forge.fedoraproject.org/server/tickets/projects/615 so that the titles reflect the currently available build and I commented all of the tickets to provide the link to the build tracking page

there are a few tickets particularly around install with RAID filesystems that are looking for owners

Re: ticket #193, I need to pull the newest image and check on the partitioning. My health has been rather wonky of late.

I don't have the hardware for some of these installation tests

Ro: which one you are lacking?

I can't help with the SBC Arm stuff for sure

I take the ARM tickets.

and I don't really have the disks to do a RAID based install

I can't do RAID nor ARM

I can take RAID 1 as well

Thanks

I have also Risc V hardware, but they are not official yet

Currently Emmanuel and I have been testing features... I think we are making progress slowly... more help would definitely be appreciated.

I can take the mariadb & mysql tickets.

I think that these can be one off tests... unless we run into issues

I am happy to pick off a few more on that list, but will see how next week progresses

Probably Lua and maybe LLVM

Okay...

If you plan to test a feature, please move it to the 'TODO' column and assign the ticket to yourself

!action: @pboy to take mariadb & mysql feature tickets; and to work on RAID1 and Arm based tickets for install testing

mmmm not sure if I messed up that action... maybe the : isn't required

I miss in our tickets the kmsmon issue, Jocelyn had brought up.

https://bugzilla.redhat.com/show_bug.cgi?id=2484542

What's the status here? Or is it completely unrelated to Server (as was my first impression)?

I will do my testing this weekedn

FYI, I will do my testing this weekend

The kmscon issue is unrelated to Server. IT's not present in the KVM install

I got the feeling unrelated... Arm specific... or am I thinking of something else

Regarding kvmcon: Did you check if it is present in the iso install?

I have not, but I've not done any isntalls from the iso yet, I will test that when I test the current build.

INFO: We should switch to next topic in about 5 mins. How can we wrap up the disussion so far?

If this is Arm specific... definitely hardware required :)

Given what kmscon is, I'm watchign for it across the board.

!propose Testing is ongoing, @pboy will pick up some of the remaining To Do tickets in the Install testing queue. Open request to help with Feature testing.

closest thing would be to propose an !agreed

Anything I should add?

proposed !agreed: !propose Testing is ongoing, @pboy will pick up some of the remaining To Do tickets in the Install testing queue. Open request to help with Feature testing.

proposed !agreed: Testing is ongoing, @pboy will pick up some of the remaining To Do tickets in the Install testing queue. Open request to help with Feature testing.

and once everyone agrees just remove the colon and the proposed

That's what I meant... I guess... I haven't taken this role before... thanks :)

I've learned this stuff from lurking in meeting rooms

+1

alr gtg, take care

I lurk and I still wouldn't be able to run a meeting without a cheetsheet...

Any other changes?

Probably: !agreed Testing is ongoing No new issues have been found so far. Because of hardware dependencies pboy will pick the ARM tickets. Open request to do further tickets.

Better summary than mine... +1

Assuming no new issues have been found...

I forgot to mention the bug I found around kickstart

https://bugzilla.redhat.com/show_bug.cgi?id=2520986

We should add that. And probably instead of !agreed. !info

It is minor and non blocking

nevertheless, hopefully gets fixed

particularly since inst.rdp is being slowly replaced with web install

We should make a repo for the bots where people can suggest ideas and report bugs ig

So: !info Testing is ongoing. One issue found:

https://bugzilla.redhat.com/show_bug.cgi?id=2520986. Because of hardware dependencies pboy will pick the ARM tickets. Open request to do further tickets.

Sounds good

!info Testing is ongoing. One issue found:

https://bugzilla.redhat.com/show_bug.cgi?id=2520986. Because of hardware dependencies pboy will pick the ARM tickets. Open request to do further tickets.

Let's move onto the next item on the agenda

OK, so we go forward now.

Tracking project: https://forge.fedoraproject.org/server/tickets/projects/436

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

Emmanuel Seyman: your floor

This week, I've mostly focused on Wildfly support

That led to https://github.com/ansible-middleware/wildfly/issues/394

where the middleware-automation seemed willing to support Fedora

We should decide what the next steps are. I think the post-install role is working, isn’t it?

I then tested their wildfly_install role on Fedora 44 and, after setting the Java version to 25, their role completed and I had Wildfly 40 up and running on my server

more on post-install after

the middleware-automation team wants to update their Wildfly version to 41 which officially supports Java 25

f the post-install role works, then we should decide on the next steps for that. Or, as a fallback, that will be our test model.

Then it should work out of the box

In any case, we would need an instruction how to start working with it.

Re postinstall, I have had no time to work on it. I haven't even reviewed the changes that were made during my vacation

I should be able to do that this week

Does their role install wildfly manually, from DNF, or some other way?

I did some testing on this and some updates... I think there are still a couple of gaps. I am happy to look at this a bit further.

Wildfly was retired from Fedora packages around Fedora 30 so they download it and install manually

I think we need as soon as possible a description about steps 1 - x, so everybody can setup a VM and try to install Wildfly that way (or postinstall). Like my ticket https://forge.fedoraproject.org/server/tickets/issues/255

!info. pboy is working on bringing Wildfly back to Fedora

This sounds fair. Presumably this should be in the Install section to describe what you should do post-install if you would prefer to allow ansible to set things up for you.

Anyway, lots of work done, lots of work left to do

And because of the many todos left, we should agree about the next step.

And because of the many todos left, we should agree about the next ONE step.

So the 'Post Install' section of the install docs should have a top level section that describes setting up ansible for fedora server ansible roles, and how to progress from there.

I think, that's a doc of it own

All of the other post-install topics then become options if ansible isn't set up.

mmmm okay... at least post install should reference that doc then :)

@Brett You already did a lot about various Ansible item. Could make a first draft as of #255?

Sure, I'd love to, yes, I did have a draft. 🙂

I think we should really aim at own role, either postinstall or Wildfly. whatever is easier. And then make that working for everyone.

So we have a Fedora Server Ansible Roles doc... an initial topic on setting up ansible etc and how things work. Then a section for each repo...

I have a lot of content floating around that I'm still trying to figure out how to incorporate

I would much rather we finish the role before trying to document its use but YMMV

I think we should really aim at one role, either postinstall or Wildfly. whatever is easier. And then make that working for everyone.

the post-install section in the install doc can then reference that

Emmanuel Seyman: As I understood, both post-install and Wildfly (with your addition) are basically working?

post-install doesn't seem that far from complete - at least insofar as it does all the steps that are in the doc

I think there are a few very small gaps and then the booleans to select which tasks should run

We should be comfortable with more and smaller roles. I ran into a situation this week where I needed to include a role multiple times with different settings. That gets harder to do when roles have a broader scope.

My Ansible-foo isn't all that good. I have a local copy of the ansible repo. How do I apply PR's in the fedora-server repo again my local repo?

Yep.... it gets messy having to learn a million variables for a role because it is doing too much

In function, yes. I suspect how you use them will change as we make more changes

I've got a growing army of stuff here for my homelab that I'd like to upstream parts of:

https://codeberg.org/brettweir/ansible/src/branch/main/roles

They all do very specific things.

> In function, yes. I suspect how you use them will change as we make more changes

Can't we use it as a pilot project? So we can see the shape everything will take on, and get a feeling how it would work? Or should be better wait 2 weeks (the next possible meeting)?

This httpd_vhost one was very interesting because once the httpd one has been run on a server, I can keep including this one with different domain names

https://codeberg.org/brettweir/ansible/src/branch/main/roles/httpd_vhost/tasks/main.yml

Ro can we aim, to make it function in the next 2 weeks?

Or can we aim, to make it function in the next 2 weeks?

Let's wait 2 weeks. The postinstall role will be finished. With luck, wildfly will as well. So we will have 2 pilot projects

proposed. !info We currently have two modules that are suitable for a pilot scheme and are almost complete: post-install and Wildfly. Both are expected to be ready for a beta user test within the next two to three weeks.

Emmanuel Seyman: does this sound suitable?

I see no objection.

Yes, this is fine

Brett: Would you make a very first draft about #255? Based on the current state of development and discussion?

Yes, I can do that.

OK

!action. Brett will develop a very first draft of a docs article as proposed in #255

sorry

Phew, we’ve got a lot done today.

SFaulken: I see you typing ??

eh?

glitch. I'm just watching, nothing to add.

and we even finished on time

OK, sorry, I just got a line in Matrix and didn't want to miss an action.

Huzzah!

indeed, on time.

There was a glitch in the Matrix? Anyone? 🙃

Let's finish and continue in Server room.

Bye everybody and thanks for coming and doing all the work.

_gets her key card out to get into the server room_