#meeting:fedoraproject.org log

<@pboy:fedora.im>

17:00:08

!startmeeting fedora-server

<@meetbot:fedora.im>

17:00:10

Meeting started at 2025-03-26 17:00:08 UTC

<@meetbot:fedora.im>

17:00:10

The Meeting name is 'fedora-server '

<@pboy:fedora.im>

17:00:11

!topic Welcome / roll call

<@pboy:fedora.im>

17:00:23

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

<@pboy:fedora.im>

17:00:23

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

<@eseyman:fedora.im>

17:01:10

hello, folks.

<@eseyman:fedora.im>

17:01:48

!hi

<@zodbot:fedora.im>

17:01:49

Emmanuel Seyman (eseyman) - he / him / his

<@pboy:fedora.im>

17:02:27

Yeah, hi! Zodbot woke up

<@pboy:fedora.im>

17:06:31

We are in a very small club at the moment. But nirik is lurking as usual. So, we have our quorum (morfe or öe.

<@pboy:fedora.im>

17:06:51

We are in a very small club at the moment. But nirik is lurking as usual. So, we have our quorum (more or less.

<@eseyman:fedora.im>

17:07:13

and we need to discuss the size of the aarch64 image...

<@pboy:fedora.im>

17:08:36

Emmanuel Seyman: Yes, that's urgent.

<@pboy:fedora.im>

17:10:35

Hm, I see, Nirik is typing for a while now ??

<@nirik:matrix.scrye.com>

17:10:49

I am typing into about 3 other rooms. ;) don't mind me

<@pboy:fedora.im>

17:10:56

OK.

<@pboy:fedora.im>

17:11:05

So let's start for now!

<@pboy:fedora.im>

17:11:16

!topic Agenda

<@pboy:fedora.im>

17:11:25

!info Follow-up actions & announcements

<@pboy:fedora.im>

17:11:34

!info Bug: Fedora 42: Server boot aarch64 image exceeds maximum size

<@pboy:fedora.im>

17:11:48

!info Status / progress Beta Testing

<@pboy:fedora.im>

17:11:56

!info Ansible assisted installation and configuration of NFS service

<@pboy:fedora.im>

17:12:05

!info Open Floor

<@pboy:fedora.im>

17:12:20

Well, leg's start.

<@pboy:fedora.im>

17:12:29

!topic 1. Follow-up actions & announcements

<@pboy:fedora.im>

17:12:55

Nothing new here, so we can skip to the next. ??

<@pboy:fedora.im>

17:13:23

OK.

<@pboy:fedora.im>

17:13:41

!topic 2. Bug: Fedora 42: Server boot aarch64 image exceeds maximum size

<@pboy:fedora.im>

17:13:52

no tracking issue yet

<@pboy:fedora.im>

17:14:01

!link https://bugzilla.redhat.com/show_bug.cgi?id=2352679

<@pboy:fedora.im>

17:14:18

And we have a discussion on mailing list

<@eseyman:fedora.im>

17:14:23

Well, there issue #158

<@eseyman:fedora.im>

17:14:32

Well, there's issue #158

<@eseyman:fedora.im>

17:14:49

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

<@eseyman:fedora.im>

17:15:56

According to Adam's comment in the bug, the increase in firmware and kernel modules is what pushed us over the limit

<@pboy:fedora.im>

17:16:10

Sorry, I missed that, somehow

<@eseyman:fedora.im>

17:16:33

https://bugzilla.redhat.com/show_bug.cgi?id=2352679#c6

<@eseyman:fedora.im>

17:18:43

Given this, I'm tempted to say we should increase the maximum size of the image

<@mowest:fedora.im>

17:18:45

If the kernel is what is pushing us over the limit, I think we need to up the limit.

<@eseyman:fedora.im>

17:18:57

Hi, Steve!

<@mowest:fedora.im>

17:19:02

Hello

<@pboy:fedora.im>

17:20:54

Welcome Steve!

<@pboy:fedora.im>

17:21:10

I also tend to accept this as an exception in any case, provided that Peter Robinson considers the current extent to be tolerable for the average hardware. And that's how I interpret his post on the mailing list.

<@pboy:fedora.im>

17:21:49

We must then take our time to determine the necessary size.

<@pboy:fedora.im>

17:22:16

For x86_64 we should leave the size unchanged.

<@eseyman:fedora.im>

17:24:45

Honestly, I would just go for 1200000 bytes

<@pboy:fedora.im>

17:25:21

I'm fine with that, too.

<@eseyman:fedora.im>

17:26:19

Now to find out how one goes about increasing the max size

<@pboy:fedora.im>

17:27:51

I think, we can decide something like:

<@pboy:fedora.im>

17:28:06

proposed !agreed If the ongoing attempts to reduce the size are not successful, Server WG is in favor of an increase to 1.2 GB as an exception.

<@mowest:fedora.im>

17:28:15

I bow before others on the right size, but I'm okay with whatever the exact amount that is picked for the reasons mentioned on the mailing list.

<@aggraxis:fedora.im>

17:29:54

works for me. will 1.2gb cover the f42 release size?

<@aggraxis:fedora.im>

17:30:19

I imagine the final release artifact might get a tiny bit bigger

<@jwhimpel:fedora.im>

17:30:26

!hi

<@zodbot:fedora.im>

17:30:27

John Himpel (jwhimpel)

<@jwhimpel:fedora.im>

17:30:44

Sorry I am late. Was sleeping due to pain medication

<@aggraxis:fedora.im>

17:30:49

Oh yeah, I just saw the size in the bug

<@pboy:fedora.im>

17:31:40

The current size of the image is 1.02 GB

<@pboy:fedora.im>

17:32:06

Welcome John. Hope you are well now!

<@jwhimpel:fedora.im>

17:32:24

Adam gave a detailed step-by-step to diagnose the issue in an email

<@pboy:fedora.im>

17:33:32

Yes, abnd it revealed some unnesssary code in the image (only frelefant for x86)

<@pboy:fedora.im>

17:34:02

nirik: , you are the most experienced in this matter. Your opinion on the proposal? Or a better decision?

<@pboy:fedora.im>

17:36:25

Hm, Nirik seems to be too busy

<@pboy:fedora.im>

17:36:55

Any objections about the proposal or a better one?

<@pboy:fedora.im>

17:38:53

Well, I see no objections. Therefore:

<@pboy:fedora.im>

17:39:00

<@pboy:fedora.im>

17:39:00

!agreed If the ongoing attempts to reduce the size are not successful, Server WG is in favor of an increase to 1.2 GB as an exception for now.

<@pboy:fedora.im>

17:39:29

Anything else to discuss here?

<@pboy:fedora.im>

17:39:58

(it took much more time as I planned :-) )

<@pboy:fedora.im>

17:40:32

OK, let's move on

<@pboy:fedora.im>

17:40:33

!topic 3. Status /progress Beta Testing

<@pboy:fedora.im>

17:41:13

I tested network and DVD for lokal interactive installation. There are some minor setbacks.

<@eseyman:fedora.im>

17:41:58

I tested the Workstation Live iso on my laptop. I must say I'm not a huge fan of the changes in Anaconda...

<@pboy:fedora.im>

17:42:30

E.G. after switching to the first summary screen after language selection it takes more than 1 minute with greyed items "Sojurce selection", install target" etc.

<@pboy:fedora.im>

17:42:49

I didn't check Workstation yet.

<@pboy:fedora.im>

17:43:17

But that doesn't sound good.

<@eseyman:fedora.im>

17:43:32

Maybe it's just me

<@eseyman:fedora.im>

17:44:19

So installation of Workstation took longer than expected which means I've haven't tested Server yet

<@eseyman:fedora.im>

17:44:23

Will do this weekend

<@pboy:fedora.im>

17:45:02

We should take a look at the anaconda changes in the next few weeks and possibly ask the developers.

<@pboy:fedora.im>

17:45:36

And I still have to test the remote installation. There are some major changes. I'm curious.

<@pboy:fedora.im>

17:46:11

Any other experiences with the release?

<@pboy:fedora.im>

17:46:47

OK, let's move on

<@pboy:fedora.im>

17:47:00

topic 4 Ansible assisted installation and configuration of NFS service

<@eseyman:fedora.im>

17:48:00

I reviewed the roles this weekend and honestly could not find any suggestions to make

<@pboy:fedora.im>

17:49:05

That sounds good!. Unfortunately, I have not yet been able to summarize my experiments properly. Somehow it didn't work the way I thought it would. This is probably due to my inexperience with Ansible.

<@jwhimpel:fedora.im>

17:49:24

I have held off generating/updating the docs till I had more feedback on roles. In about a week I will begin working on the docs.

<@jwhimpel:fedora.im>

17:50:11

Peter Boy: What was different than you expected?

<@mowest:fedora.im>

17:50:12

Where are the current docs on using the Ansible roles?

<@jwhimpel:fedora.im>

17:50:57

The docs for ansible are most usually stored in the README.md files for each role.

<@pboy:fedora.im>

17:51:37

John Himpel: I didn't get it to work. This is possibly because I haven't got my Ansible control node right yet.

<@jwhimpel:fedora.im>

17:51:59

I think I need to do a rough draft of a "best practices" doc for our ansible roles. I can draw from the many currently published "best practices" docs.

<@pboy:fedora.im>

17:52:32

"best practices" sounds good ;:-)

<@jwhimpel:fedora.im>

17:53:55

Ansible is not hard. It's just that everything and it's brother are configurable. So no two setups are often alike.

<@mowest:fedora.im>

17:54:04

Perhaps I'm confusing some terminology. But can't you use "Ansible Pull" to bring in the playbooks without having a control node? Wouldn't this be a great way to use it on the home servers.

<@eseyman:fedora.im>

17:56:05

You can specify a local connection and the playbook will run locally. You will still need "/usr/bin/ansible-playbook" on your system

<@jwhimpel:fedora.im>

17:56:35

There are multiple ways to use Ansible. One is rather simple and rudimentary (just playbooks). A step up is Roles. A step beyond that is Ansible modules. Then RedHat has developed a "controller" to help manage sites that have large ansible setups (I haven't used that feature yet). I find it best to start with playbooks and roles.

<@aggraxis:fedora.im>

17:57:23

you could just box up the roles and specific playbooks in an rpm and distribute them. it doesn't have to be complex with a controller. ansible will ansible itself if you ask it to.

<@pboy:fedora.im>

17:58:18

I tried a local server on my home network as control node and to install NFS on one of my public servers. The classic use case, so to speak.

<@pboy:fedora.im>

18:02:04

I have tried to set up the control node as briefly described in https://docs.stg.fedoraproject.org/en-US/fedora-server/services/ansible-support-intro/.

<@pboy:fedora.im>

18:02:27

nirik: Tnanks!

<@jwhimpel:fedora.im>

18:03:10

Peter Boy: Let me review that document and get back to you.

<@jwhimpel:fedora.im>

18:03:53

It would be helpful if you could send me any error messages you are seeing.

<@pboy:fedora.im>

18:04:41

John Himpel: I'll continue on Friday with my Ansible "experiments". And send you a mail.

<@pboy:fedora.im>

18:07:25

Hm, Emmanuel is typing for a while ??

<@eseyman:fedora.im>

18:07:42

No. Not at all

<@pboy:fedora.im>

18:07:57

OK, bug in Element here.

<@pboy:fedora.im>

18:08:45

Our time is up and my family is waiting for the dinner. We should continue next week and start with this topic.

<@eseyman:fedora.im>

18:08:54

This just in. Our proposal talk for Flock has been accepted

<@pboy:fedora.im>

18:09:28

Oh, wonderfull!

<@mowest:fedora.im>

18:09:31

Ok, let's end, and enjoy your family dinner.

<@pboy:fedora.im>

18:10:10

We should start next week with this topic, So that this is not just too short again.

<@pboy:fedora.im>

18:10:37

By bye, see you next week!

<@eseyman:fedora.im>

18:10:50

bye, folks!

<@pboy:fedora.im>

18:10:55

!endmeeting