!startmeeting fedora-server

Meeting started at 2024-07-03 17:01:34 UTC

The Meeting name is 'fedora-server'

Well, let's wait a moment for everybody to shop up. I’ll post the agenda in about 2-3 minutes.

!hi

John Himpel (jwhimpel)

!hi

Jason Beard (cooltshirtguy) - he / him / his

Welcome John, welcome Jason

I think, we should wait 2 mins more :-)

Hi, folks !

!hi

Emmanuel Seyman (eseyman) - he / him / his

!hi

Neal Gompa (ngompa) - he / him / his

Well, we meet our quorum. And I hope, moweist is not lost on IRC

Hi Neal!

Have you been at Suse Open in Nuernberg?

Unfortunately I couldn't join this year

Well, let's start

Anything to add?

OK. Let's start

I have finally managed to put everything together.

DONE !action jwhimpel will check the details of the procedure (regarding Elevating Server VM distribution) and report back next meeting - to deal with today.

Still open because of an ongoing discussion about improving Server first boot process

action pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification - ongoing

DONE !action pboy will create an additional directory fedora-ansible in fedora-server repo

See:

Anything to add here?

or to comment or to ask?

no

OK, let's move on.

I forgot to follow-up. I will attempt to do so before next meeting.

John Himpel: Thanks! That will do easily

No tracking entry yet

We need a decision here

I'm back on. :-)

mowest: 1++

I'm all for it but I won't be able to attend each and every meeting

still, 1++ for me

+1

I'm for every week, but I will also miss a number of the meetings, but might be easier to remember to put it into my calendar if it is every week even if I have to miss some.

Emmanuel Seyman: I think your proposal is fine to adjust the agenda respecting who dan't join a meeting

I think you can't join the 2nd meeting a month

We can take that into account.

Well, we vote +4 / 0 / -0

Therefore:

!undo

doesnt work

Items to discuss:

- What we need to provide for a Change Proposal

- Current status

cooltshirtguy: I think, you are the expert here?

lol. definitely not an expert. I don't even know how that works. :)

IIRC, There was a recent conversation including Adam W. He was pretty adamant that he only wanted "Fedora Workstation" to be a blocking image. My memory isn't the best, so I could be wrong.

I remember something about that,.. he wanted or its currently the only blocker?

I remember something about that.. he wanted it to be or its currently the only blocker?

I remember Adam told me we would have to elevate the VM.

cooltshirtguy: You've produced a first draft, haven't you?

I'm not sure I would like the VM image to be a blocking image. In a similar way I wouldn't want one of the "spins" to be a blocking image.

no I haven't. i remember we discussed it but I don't remember anyone taking ownership. I remember discussing samaba

mowest: Our goal is to promote Fedora Server in virtualized environments as a modern alternative to classic hardware.

So we need it as a blocking deliverable

I can look it but will need some help with it. I have no idea how the process works

Well, I think I'm the one with the most experience in this process. So I'll make a proposal next meeting.

(Allthough its only one)

Peter Boy: Is Fedora CoreOS or Fedora Cloud considered a blocking image? If so aren't we already promoting Fedora in a VM environment, because I'm guessing those are used frequently in a VM cloud environment.

I dont mind learning new things, but honestly I've never really had any overview how things work around here.

they are both used in VM cloud environment

@mowest I don't know

I do.

They are both common.

davdunc: Thanks!

absolutely!

So I think we should tread server the same way. Many people asked me about Server in a VPS (i.e. not in a cloud system)

davdunc: Do you work at Amazon or do I remember wrong?

I do work at Amazon. :)

Good, I would like to ask you about available options vor VPS later

Take a look at Lightsail.

that's my target for our efforts.

KIWI builds to replace Bitnami.

Yes, several users asked me about lightsail. And I mentioned it last Flock in Cork.

It's very close.

I'm working with the team.

davdunc: Thanks!

OK. What will we do?

proposas: !agreed pboy will make a proposal how to proceed with Fedora Server VM

proposas -> proposal

for right now, just help us build your kiwi definition.

we have a kiwi builder in koji.

Yes, we discussed that some weeks ago and basically decided to switch to kiwi for images, except that releng prefers something else.

https://pagure.io/fedora-kiwi-descriptions

Thanks, will study those

cool. Look forward to unblocking anything you need for the composition.

Yeah, I'll come back to you. I hope you will not regret to help us :-)

(Must a joke)

Just a joke

:) No regerts!

I believe Release Engineering said KIWI was fine for VM images, but they were unsure about using KIWI for .iso images. Neil Gupta responded in a ticket, that he thought KIWI could possibly generate by using a SUSE product (after packaging such in Fedora) to generate install DVD images.

Yes, I think we should wait here and look, what's evolving. At least, I have no preferences.

But back to the proposal:

John Himpel: Neal Gompta

I warned everyone earlier, my memory was sometime faulty :-)

Gompa! Oh my goodness!

I followed you right into the hole!

Neal Gompa -- his moniker is Conan_Kudo.

Well, back to my proposal: !agreed pboy will make a proposal how to proceed with Fedora Server VM

We need to switch to the next topic!

We are late

I see no objections to the proposal ?

3

2

no, sounds good

OK

Current agreements so far

- we want to synchronize our manual installation guide, the Ansible doc/guide, and the Ansible process results (i.e. Ansible should create the same as the manual doc describes).

-- Do we want to have a separate Administration guide / page?

- We want to collect an alpha version in the new ansible directory of our fedora-server repository

- We want to split the current NFS draft in 2 parts: Installation and (Basic) Configuration.

- Should we detail our requirements for an NFS server playbook?

We probaby have to:

- Discjuss and process the change of the curent NFS doc (split into installation and configuration)

And I provided a Server Docs template

I have two ansible roles working (server & client) on F40 between different servers. I need to add one more feature (map different useri numbers between servers). Then I need to convert it to a collection. ETA two weeks.

OK, so we should wait for this.

We could use the time to enhance our docs draft?

yes, good idea

I like the idea of have a separate docs "Installation" and "Configuration" with a subsection under "Configuration" with "With Ansible"

What is the url for the Fedora Server repo, so that I can post Work In Progress and "Final" version for others to see and review?

Then we could have NFS with Ansible, Samba with Ansible, Webserver with Ansible, Podman Containers with Ansible...

John Himpel: stg is https://docs.stg.fedoraproject.org/en-US/fedora-server/services/filesharing-nfs-installation/

There is no public version in main yet.

That's for docs. Where should I put ansible code.

mowest: Yes, that the Goal.

John Himpel: https://pagure.io/fedora-server/tree/main

Therin fedora-ansible with some subdirs

Question: My role currently assumes userid info is kept in /etc/passwd. Should I have options for that info stored in LDAP and/or FreeIPA?

I suspect this would be useful

I am not familiar with PAM, so I suspect I would need some assistance with that part.

I'm not seeing the consequences at the moment. So I can'tg say anything here

Note that we can always add that part later. Ours docs are not set in stone.

I'll finish what I have and we can discuss "add-ons" later.

OK, so back to docs for a short time

I have written the current NFS docs draft. Someone else should do the revision, I think.

Who will start to split the current draft in to installation and configuration?

I'm not an author, but I can at least add bullet points and some text. It may be a couple of weeks before I can make much progress there.

John Himpel: That would be perfectly OK.

Someone else to support the review / reworking?

I'll be glad to help

Emmanuel Seyman: ++1

pboy gave a cookie to eseyman. They now have 15 cookies, 1 of which were obtained in the Fedora 40 release cycle

I will take a look at the docs too, I'm working on getting a new machine up and running for doc editing for when I go to flock. I have Fedora installed, and one of the next steps will be to set up the local writing environment. I can take a look at server docs then.

mowest: Very good. Maybe we can use your experience to improve the docs about how to contribute to Fedora Server Docs.

mowest: ++1

Well I think we are done for now. I switch to Open Floor

Registration for Flock is now open.

https://www.eventbrite.com/e/flock-2024-tickets-906515701867

Yes, don't miss the opportunity!

I'm arriving on the 6th and staying until the 11th

My tickets are not fixed, yet. But I think, it's the same for me.

I'm arriving on the 6th and heading back home after Saturday's sessions, might need to scoot out in the afternoon sometime to head back home.

So that would be 6-10

Well I hope we have a lot of opportunities to meet and to "socialize" :)

We are overdue and should end the meeting now.

Anything left last minute?

yes, I need to go hunt for food...

I typed and ate at the same time :-)

is there a schedule of presentation yet for flock?

I probably won't be at next week's meeting

talks have been approved/denied but I don't know about a schedule

OK, see you next week (besides Emmanuel)

bye

I'm off. I will post the minutes to the list later tonight

Thanks!