Meeting started at 2024-05-01 17:00:37 UTC

The Meeting name is 'fedora-server'

Welcome to our Server WG meeting today! „Same procedure as every year“ We'll give a few minutes for folks to show up

!hi

No Fedora Accounts users have the @jwhimpel:matrix.org Matrix Account defined

!hi jdubby

!hello

Sorry, but Fedora Accounts user 'jdubby' does not exist

Emmanuel Seyman (eseyman) - he / him / his

Oh, Zodbot is being picky again

John, I think we believe that you are here 😀

"There is no spoon"

:-) It was the first i found in a hurry :-)

We are a little short on members today, but I think we should start anyway.

Any objections?

Nope, let's go

OK, then

Any comment?

Obviously not

No specific action pending.

Announcements:

UNISON will hopefully come back.

That would be really handsome for Fedora Server as file server.

Anything else for announcements?

Not to my knowledge

OK, let's move on

!https://pagure.io/fedora-server/issue/126

Lets have a shoort break for reading the current state in the issue

There is some additional info at the mailing list:

Does online replace "net install"?

jwhimpel: Yes

and offline replaces DVD

If we can attach a short explanation of online vs offline to the download pages, then I'm fine with this.

I wonder how much effort it would be to create a rescue variant that you could burn to a USB drive (or boot off the network) in order to repair an installation

jwhimpel: https://fedoraproject.org/server/download

We can add a short explanation

Emmanuel Seyman: Great idea!

We should add that to our working plan.

It should be not too difficult.

I suspect it would be very similar to the offline version

I think it would more like a live CD? So you have all tools to fix issues at hand?

And we should check the current rescue system. If I remember correctly, it's quite sparse.

well, the contents would be very similar to the offline install media but, yes, it would function like a live CD

Yeah, with the offline image you can <ctrl><alt><F2> into a root shell. But I don't know what tools are available there.

I think we should discuss about that in a dedicated topic next meeting.

And continue with the name convention topic???

OK Back to the naming convention.

Any additional comment?

Indeed. FTR, your proposal works for me

What do you thine about the "sbcdevs" idea instead of rawsbc?

rawsbc works better for me

Would one image work on any sbc <arch> or would each sbc need a custom image? ie Rpi4 vs Rpi5 vs a pine4 sbc?

jwhimpel: One image for all sbc's. The differentiation is done during installation by arm-image-installer by installing the corresponding uboot files

Thx for the info.

Rasberry uboot files are preinstralled.

jwhimpel: Any comment about sbcdevs vs. rawsbc? If I reconsider, rawsbc is a bit more a type like online / offline or virt.

As a newbie, I think I would better understand rawsbc

OK, ao rawsbc is it

And what about offline / online vs. offlineinst / onlineinst ? I would prefer the shorter.

offline/online by a mile

agree with offline/online

OK, then we have:

an 'inst' does not bring anything to the table

proposed: !agreed Server WG decides to rename the installation media: DVD -> offline , netboot -> online, KVM -> virt, and rawsbc for ARM raw image. proposed: !agreed Server WG decides on a consistent naming convention according to the scheme: "Fedora-Server-<rel>-<method>-<arch>-<version>.<filetype>"

Do we agree about the agrees ?

an 'inst' suffix brings nothing to the table

+1

+1

Emmanuel Seyman: ?? We need 3 votes :-)

+1 here

thanks.

So lets move to the next topic.

Oh I forgot:

No issue created yet

Any idea / comment?

I like the idea but do not use VMs so will not commit to doing the work...

Well, until now I took care about the VM. So I suppose it would be my job.

If RelMgnt and QA are willing to do this, then I think it's a good idea. I make rather extensive use of VM's.

Or John, would you like to take over?

What would be involved? Right now I am trying to sell a bunch of real estate that I own and finish rehabbing a couple of houses. I also run a not-for-profit corporation that provides "fix-it" services for people unable to afford or unable by themselves provide home/apartment repairs. I also lead a group of volunteers that respond after a natural disaster occurs. So my time is quite limited until September.

jwhimpel: Thats sounds to be much work. There is a procedure for that, but I don't know the details our of my head. At the end it is a discussion with FESCo and FESCo has to make a final decision about it. I'm not sure how much time is will consume.

Between now and the next meeting, let me communicate with NIRIK to see what is required. I will report back at the next meeting.

John Himpel: +1 !

#action jwhimpel will check the details of the procedure and report back next meeting.

Sorry:

Nextg topic:

We have not much time left. But nevertheless, any ideas / comment here?

Obviously, no ideas at the moment. I think we postpone for now and continue discussion on mailing list?

Changing the label to "Fedora Everything" is the only suggestion I have at the moment

It seems we need to somehow educate persons doing downloads for Fedora Server no NOT use Everything, but instead of Fedora Server. Other groups seem adamant that if we went our install to be different, we need to not be using Everything as that is controlled by the Desktop/Workstation group. All of the settings and images produced by Everything will be according to their wants and needs.

jwhimpel: yes agreed. Let's discuss on mailing list or in the ticket, and on next meeting.

Lets at least short discuss about the next topic.

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

Any questions for now that we can discuss shortly or should discuss on mailing list?

Last I checked, those groups were indeed in the comps.xml file

Yes, one task is to review the comps groups. Some of them were rather suspicious to me when I worked on the VM

There was some explanation of what groups were used by dnf and what groups are used by the build process and they were different. QA knows which set of groups are used by dnf and which are used by the build.

Yes there are some differences. At the moment we have to decide how to proceed. I would propose we contact Kevin for more information.

This issue was referenced in the video presentation. Or it was referenced in the mailing list. I forget which (My memory isn't as good as it was years ago when I was younger.

yes, that's where I got the idea of installing several rescue tools with a single dnf command which led to my thinking "can't I just netboot off something and get a rescue env?"

I can try to investigate for our next meeting

@eseyman +1

Our time is up. I would like to change to Open Floor Or do we have more discussion with this topic at the moment?

John Himpel: did you find the time to review the nfs docs?

Lets switch to Open Floor, that would be the right place accordinmg to our agenda

I was able to get nfs up and running via ansible, but it was a very simple use case (no id mapping). I found a couple of typos,, but they were not a big issue. I was using the net-install iso and I think I should be using the Fedora Server iso. I ran into some issues. I will use the proper iso and try again this weekend.

ok, thanks

Typos should be fixed, imho

John, I read your mail but couldn't manage to answer yet.

I think, if you found suitable ansible books, we should integrate them.

And yes, typos are my speciality - and have to be fixed :-)

Peter, Don''t worry about it. Let me try again this weekend and get back to you on Tuesday (I am fully booked on Monday).

OK!

For the mailing list: Lets have a discussion of Ansible vs cockpit. Both have their strengths, but writing common docs would be a PITA.

that works for me

I need to leave now.

Yes, for me too

I have another question: I'm wondering if we should go back to a weekly schedule for some times. We have such a huge backlog and we have to take action in a limited time frame.

Originally, we started with a weekly schedule. But changed to be-weekly, because we didn't had so much to do.

John: bye bye!

I will not be present on the second Wednesday of the month (Paris Perl Mongers meeting)

OK, so we could take the first, third and fourth wednesday.

That would be a progress

I'll out that on the mailing list.

We have badly overdrawn and should close now. Or anything urgent to discuss now?

Maybe there is any onlooker with a question or comment?

Ok, I don't see someone and will close in

3

OK, eseyman??

you were typing?

Oh, yes

Just to see that we can close

OK closing now.