#meeting:fedoraproject.org log

<@pboy:fedora.im>

17:00:18

!startmeeting fedora-server

<@meetbot:fedora.im>

17:00:19

Meeting started at 2025-05-07 17:00:18 UTC

<@meetbot:fedora.im>

17:00:19

The Meeting name is 'fedora-server'

<@pboy:fedora.im>

17:00:27

!topic Welcome / roll call

<@pboy:fedora.im>

17:00:36

<@pboy:fedora.im>

17:00:36

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

<@pboy:fedora.im>

17:00:36

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

<@jwhimpel:fedora.im>

17:00:39

!hi

<@zodbot:fedora.im>

17:00:40

John Himpel (jwhimpel)

<@eseyman:fedora.im>

17:00:44

!hello

<@zodbot:fedora.im>

17:00:46

Emmanuel Seyman (eseyman) - he / him / his

<@pboy:fedora.im>

17:01:08

Hi, both of you!

<@pboy:fedora.im>

17:01:57

I think, we should start.

<@pboy:fedora.im>

17:02:07

!topic Agenda

<@eseyman:fedora.im>

17:02:09

let's go, then

<@pboy:fedora.im>

17:02:19

!info Follow-up actions & announcements

<@pboy:fedora.im>

17:02:29

!info Ansible assisted installation and configuration of NFS service

<@pboy:fedora.im>

17:02:42

!info Server user poll

<@pboy:fedora.im>

17:02:52

!info Follow-up of the F42 server development and test cycle.

<@pboy:fedora.im>

17:03:00

!info New Anaconda WebUI and how to make progress with our distribution media

<@pboy:fedora.im>

17:03:00

!info Open Floor

<@pboy:fedora.im>

17:03:26

Anything do add or to remove?

<@eseyman:fedora.im>

17:04:00

That sounds enough to me

<@jwhimpel:fedora.im>

17:04:07

Workstation WG is talking about moving to all flatpaks for apps. Will that affect us?

<@pboy:fedora.im>

17:05:00

I don't know. Maybe we'll miss a lot of rpms. Lets discuss in Open Floor

<@jwhimpel:fedora.im>

17:05:41

It can even wait until next meeting. Just don't want to lose track of topic.

<@pboy:fedora.im>

17:06:09

John Himpel: ++1

<@zodbot:fedora.im>

17:06:11

pboy gave a cookie to jwhimpel. They now have 4 cookies, 1 of which were obtained in the Fedora 42 release cycle

<@pboy:fedora.im>

17:06:31

!topic 1. Follow-up actions & announcements

<@pboy:fedora.im>

17:06:43

!link https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2025/

<@pboy:fedora.im>

17:06:43

Regarding the action, nothing new. See

<@pboy:fedora.im>

17:06:54

Next Tuesday and Wednesday, some friends are visiting me and we're going on a bike ride. I'm not sure if I'll be able to attend our meeting on Wednesday evening. Eseyman probably won't be able to make it either (as far as I know, the second Wednesday of the month is his Perl meeting). Can someone else take over as chair and send out the invitations, or should we cancel the meeting because there probably won't be enough participants?

<@pboy:fedora.im>

17:06:54

Info from me:

<@eseyman:fedora.im>

17:07:28

Indeed, I probably will not be able to attend the next meeting

<@pboy:fedora.im>

17:07:37

nirik: 😀

<@jwhimpel:fedora.im>

17:08:04

I would suggest skipping next meeting as MOWEST will probably not be there either.

<@pboy:fedora.im>

17:09:00

!agreed: we skip next meeting (May 14)

<@eseyman:fedora.im>

17:09:15

yes, agreed

<@pboy:fedora.im>

17:09:34

Zodbot sleeping?

<@pboy:fedora.im>

17:10:05

!agreed we skip next meeting (May 14)

<@pboy:fedora.im>

17:10:05

<@pboy:fedora.im>

17:10:23

OK, w/o the :

<@pboy:fedora.im>

17:10:36

!topic 2 Ansible assisted installation and configuration of NFS service

<@pboy:fedora.im>

17:10:46

!link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/ANSAGBZNK4LN72OWJLGCD2AFNSFGPFKW/

<@pboy:fedora.im>

17:10:57

!link https://pagure.io/fedora-server/c/5647c4d701ab3d2b0cc95806bba3d4f2c5fbc162?branch=stg

<@pboy:fedora.im>

17:10:57

!link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/7KUVM6SC5A4SQWP4QMFFRWRNNP6F6AUV/

<@pboy:fedora.im>

17:11:16

I think, we are making great progress now.

<@jwhimpel:fedora.im>

17:12:08

Kevin suggested I follow the patterns of the already packaged ansible collections and roles. I didn't get time to implement those changes for today's meeting, but should be no problem to have something ready for out meeting on the 21st.

<@jwhimpel:fedora.im>

17:12:51

I will post status updates on m/l. I will checkin code to the dev branch of our repository.

<@pboy:fedora.im>

17:13:32

Our roles a very special to the Server Edition, i think. I unsure, it it finds in a general collection.

<@pboy:fedora.im>

17:13:51

Our roles a very special to the Server Edition, i think. I unsure, it it fitts in a general collection.

<@jwhimpel:fedora.im>

17:14:14

Esseyman suggested using "wheel" for userid (and group?). That would restrict access to the collection or role. Should I implement this? Or should I create a new "group id" to restrict access?

<@nirik:matrix.scrye.com>

17:14:49

I think it makes sense to not reinvent things. ;)

<@eseyman:fedora.im>

17:15:07

I get the feeling collections never took off in the Ansible ecosystem the way they were supposed to

<@jwhimpel:fedora.im>

17:15:24

I can reflect the "specialness" in the name of the package and collections/roles.

<@pboy:fedora.im>

17:16:12

nirik: Agreed. Our roles include very special steps, e.g. providing the logical volumes or equivalent to create the storage space in the Server Edition disk space.

<@nirik:matrix.scrye.com>

17:16:16

I'm not sure why you think that...

<@nirik:matrix.scrye.com>

17:16:21

there's tons of collections

<@jwhimpel:fedora.im>

17:16:35

Emmanuel Seyman: I seem more references to collections lately.

<@eseyman:fedora.im>

17:17:05

Maybe that's just from what I've seen

<@nirik:matrix.scrye.com>

17:18:12

the ansible package in fedora is a collection of collections... not sure how many its up to right now, but its... a lot

<@pboy:fedora.im>

17:18:38

Regarding the directory, may first idea is to create a directory "Serveradmin" in the users home dir and put therein all the roles for the services, the admin user wants no use.

<@jwhimpel:fedora.im>

17:18:41

Peter Boy: I need to review the collections/roles that Kevin suggested. Those collections/roles are rather specific also. If they don't restrict access, I'm not sure we need to either.

<@nirik:matrix.scrye.com>

17:20:03

note that fedora packaging forbids touching anything in users homedirs. ;) But of course your playbook could copy something there I guess.

<@jwhimpel:fedora.im>

17:20:24

Peter Boy: I would vote for just following the "/usr/share" pattern as all of the other collections/roles already packaged.

<@pboy:fedora.im>

17:21:08

Yes, probably we should discuss some of the existing roles. And we may use them it usful. My first impression when looking at some of those roles, they try to cover everything, installing in Debiyn, Suse, etc. and some other things. Not necessarly useful for us.

<@eseyman:fedora.im>

17:21:17

we could ship a small script that creates our suggested layout

<@jwhimpel:fedora.im>

17:22:16

The roles/collections currently packaged as rpms are very fedora/centos/RHEL specific

<@pboy:fedora.im>

17:22:29

We have some things very individually for the server to maintain. That doesn't fit into /usr/share I thing

<@pboy:fedora.im>

17:22:52

We have some things very individually for the server to maintain. That doesn't fit into /usr/share I think

<@pboy:fedora.im>

17:24:04

As an example, the amount of storage space to create a lv to store exported files.

<@jwhimpel:fedora.im>

17:25:23

Peter Boy: Suggest you look at "dnf5 list ansible-collection-\*". I think you will see those rpms are pretty sysadmin specific.

<@pboy:fedora.im>

17:25:45

On the other hand, maybe several admins may want to share some information.

<@jwhimpel:fedora.im>

17:27:11

Also look at the spec file for linux-system-roles rpm. Again, they are almost all sysadmin related packages.

<@pboy:fedora.im>

17:28:46

Yes,but what does that mean for our project? Can / should we reuse some of those roles (or tasks within)? Or do those roles alkready everything we want to achive with our Ansible project?

<@jwhimpel:fedora.im>

17:29:33

I'd have to do more research to answer that question. If there is anything pertinent to us, we can certainly use it.

<@eseyman:fedora.im>

17:31:11

I've said this multiple times but we don't have the resources to reinvent the roles already on Ansible Galaxy. We should package existing roles.

<@jwhimpel:fedora.im>

17:31:42

Emmanuel Seyman: +1

<@pboy:fedora.im>

17:32:42

My question here: Why didn't we do it, then? What would you propose for our NFS administration?

<@pboy:fedora.im>

17:33:17

My question here: Why didn't we do it, then from thje begining? What would you propose for our NFS administration?

<@pboy:fedora.im>

17:33:35

My question here: Why didn't we do it, then from the beginning? What would you propose for our NFS administration?

<@eseyman:fedora.im>

17:34:33

That said, there will be some things that don't exist in Galaxy and that we will have to produce ourselves

<@eseyman:fedora.im>

17:34:33

I advocated robertdebock's nfsserver role from the start.

<@pboy:fedora.im>

17:35:55

OK, so you think we can use robertdebock's nfsserver role like I would use a generic library in C++ or Java? That would look fine for me.

<@pboy:fedora.im>

17:37:17

You know, I'm not an export for Ansible

<@pboy:fedora.im>

17:37:29

You know, I'm not an expert for Ansible

<@eseyman:fedora.im>

17:37:58

The only issue I have with his nfsserver role is that it does not handle shares with a space in them (yes, I live dangerously)

<@jwhimpel:fedora.im>

17:38:51

We can certainly use his nfsserver. But be aware it does not address the nfs client side.

<@eseyman:fedora.im>

17:40:08

Indeed

<@pboy:fedora.im>

17:40:09

I'm a little surprised now. And it's already late. How do you want to proceed?

<@pboy:fedora.im>

17:40:22

I'm a little surprised now. And it's already late. How do we want to proceed?

<@eseyman:fedora.im>

17:41:43

Let's start small. I will submit a package of robertdebock's users role before the end of the week

<@eseyman:fedora.im>

17:42:04

Once that is in Fedora, I should be able to package any of his roles easily

<@pboy:fedora.im>

17:43:48

I think, we could discuss independently from a rpm ready to use, how to (re)use that role and what we may have to provide additionlly to get out goal up and working.

<@pboy:fedora.im>

17:44:05

I think, we could discuss independently from a rpm ready to use, how to (re)use that role and what we may have to provide additionlly to get our goal up and working.

<@pboy:fedora.im>

17:45:44

Can / shoud we discuss on mailing list, or should we wait until robertdebock's rpm is available?

<@eseyman:fedora.im>

17:47:32

I can send an email to the list after having submitting it. We can discuss then

<@pboy:fedora.im>

17:48:00

OK, proposed !agreed We postpone the project until eseyman has a robertdebock rpm ready and a proposal how to (re)use it for our purposes.

<@pboy:fedora.im>

17:48:15

OK, proposed !agreed We postpone the NFRS Ansible project until eseyman has a robertdebock rpm ready and a proposal how to (re)use it for our purposes.

<@pboy:fedora.im>

17:48:22

OK, proposed !agreed We postpone the NFS Ansible project until eseyman has a robertdebock rpm ready and a proposal how to (re)use it for our purposes.

<@pboy:fedora.im>

17:49:11

OK, proposed !agreed We postpone the NFS Ansible project until eseyman has a robertdebock rpm ready and eseyman and jwhimnpel have a proposal how to (re)use it for our purposes.

<@jwhimpel:fedora.im>

17:49:14

Emmanuel Seyman: Can you post it in our repository before you submit it to be an official rpm?

<@eseyman:fedora.im>

17:49:27

Sure

<@pboy:fedora.im>

17:49:42

OK, proposed !agreed We postpone the NFS Ansible project until eseyman has a robertdebock rpm ready and eseyman and jwhimpel have a proposal how to (re)use it for our purposes.

<@pboy:fedora.im>

17:50:08

Any objections regarding the proposal?

<@jwhimpel:fedora.im>

17:50:33

No objection here

<@pboy:fedora.im>

17:50:53

OK.

<@pboy:fedora.im>

17:51:03

!agreed We postpone the NFS Ansible project until eseyman has a robertdebock rpm ready and eseyman and jwhimpel have a proposal how to (re)use it for our purposes.

<@pboy:fedora.im>

17:51:30

!topic 3. Server user poll

<@pboy:fedora.im>

17:51:41

!link https://pagure.io/fedora-server/issue/145

<@eseyman:fedora.im>

17:52:51

Peter Boy: I added a couple of questions to your hackmd.io page

<@eseyman:fedora.im>

17:52:58

Also, I have gone through the results for what Fedora Server users want us to focus on and was pleasantly surprised.

<@eseyman:fedora.im>

17:53:15

Lots of people seem satisfied with what we ship

<@eseyman:fedora.im>

17:53:47

The main call for improvement is documentation, use cases, best pratices, ...

<@pboy:fedora.im>

17:54:24

Oh, that's sounds very good.

<@pboy:fedora.im>

17:54:49

I think we have to start to prepare our talk at Flock.

<@pboy:fedora.im>

17:55:26

Did you do some analyses of the date, maybe some tables ?

<@eseyman:fedora.im>

17:56:30

No, just a quick read but I plan to make something for our presentation at Flock

<@eseyman:fedora.im>

17:57:01

Planning my trip to Prague is another thing I have to do over the 4 day weekend...

<@pboy:fedora.im>

17:57:14

OK, maybe we should start to discuss on short notice :-)

<@pboy:fedora.im>

17:57:27

Let's talk via email.

<@pboy:fedora.im>

17:57:43

!topic 4. Follow-up of the F42 server development and test cycle.

<@pboy:fedora.im>

17:57:53

no tracking issue yet

<@pboy:fedora.im>

17:58:27

It's too late now to discuss in ernest. But please, read https://fedoramagazine.org/start-planning-fedora-43-test-days/

<@pboy:fedora.im>

17:59:47

We discussed, to prepare a Server test day (or better test week). Maybe, we should take this occasion to start.

<@eseyman:fedora.im>

18:00:52

That would be nice

<@pboy:fedora.im>

18:00:52

But for now that's a case for the mailing list.

<@jwhimpel:fedora.im>

18:04:34

Sorry, I have to leave now.

<@pboy:fedora.im>

18:04:58

John Himpel: Thanks!

<@pboy:fedora.im>

18:05:06

and bye.

<@eseyman:fedora.im>

18:06:25

I suspect we can end the meeting

<@pboy:fedora.im>

18:06:44

OK, see you in 14 days and via mail!

<@pboy:fedora.im>

18:06:54

!endmeeting

<@pboy:fedora.im>

18:06:54