Meeting started at 2024-07-31 17:00:56 UTC

The Meeting name is 'fedora-server'

Let's wait a moment. I'll post the agenda in 2-3 minutes with a new business to deal with in addition to the agenda as sent earlier today.

!hello

Emmanuel Seyman (eseyman) - he / him / his

Hi, Peter

!hello

Steve Daley (mowest)

ngompa has already given cookies to dcavalca during the F40 timeframe

Hi Emmanuel, hi Steve

!hi

John Himpel (jwhimpel)

Hi John

Well, I think we can start.

Anything to add?

OK, none.

I'm goof

I'm good

I'm good

We have basically the same state as last week.

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

I did find out who to talk to in order to do a survey on discission.fedoraproject.org so when we have the questions ready I can start putting that together.

Anything gto add here?

not me

Sorry, wife just called and is locked out of the house. Need to go "rescue" her.

Some progress on NFS ansible stuff and some progress on pagure stuff. Will send update via mailing list when I return.

One thing from me.

Unfortunately I cannot take part in Flock. I was badly hit by a car and everything still has to heal. I can't even sit for more than 2 hours, too little for a flight. And too little for a day at Flock. I am very sad.

That is very sad news. I hope you get better soon

Oh no, I'm so sorry to hear that. Car accidents are horrible, or it sounds like you were a pedestrian hit by a car which is equally horrible.

I was riding my bike. and my doctor estimates that I will need at least another 4 weeks.

oh man, I hope your healing goes well

I'm an avid bicycle rider, and here in the states with cell phone distracted driving this is becoming more dangerous, and in the US cars are not as used to seeing or looking out for bicycles because we have few who dare to ride them in most areas of the US, some bigger cities with good bike infra are better though.

Yes it is the second accident this year and the worst so far.

Conan Kudo: Thanks. I do my best :-)

All my bicycle accidents and injuries were rider error, my fault, and never involved an auto.

Blessings on getting and feeling better soon.

Well, I did everything right. The car just switched to the bike road to overtake another car.

Well, probably we can have a chat via Matrix.

Let's move on and hope for the next year.

there's the issue of the talks you were going to do at Flock

Yeah, I think the committee had cancelled them. Really bad.

I hoped until the end that everything would heal more quickly.

Still, the rest of the group can mett there and chat. As you said, l'ets hope for next year

Still, the rest of the group can meet there and chat. As you said, l'ets hope for next year

Yeah, let's go on.

as discussed, I tried to write down our goal:

jwhimpel just left

He was trying to update the git repo yesterday and today

Yeah. I think he should use ssh. It's much more convinient.

I looked at that too, doesn't pagure give you either an https or an ssh URL to copy and do a "git clone" with?

Yes, you can choose

I wrote a short guide for our documentation:

I agree, using the ssh URL is the best way to interact with pagure IMHO.

https://docs.fedoraproject.org/en-US/server-working-group/usr-docs-maintenance/local-authoring/

It includes the steps necessary to work with git.

I think we have to wait for John to successfully upload the scripts he developed.

But maybe we can discuss, it I met our goals correctly in the proposal?

I'll read the guide by the end of the week and supply feedback

By guide you mean the article about how to contribute to our docs?

yes

OK. thanks. I wrote a longer version as part of docs team at:

https://docs.stg.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-local-authoring-env/

Maybe, we can expand and update our server doc a bit.

But regarding Ansible, the questions is whether we agree about our goal according the my comment to issue 138 where I tried to summerize our discussion.

I agree 100% with the goal

Good, an other comments?

The goal looked good. (Not sure how ansible scripts work and are formatted). Could we simply add a comment to the ansible playbook that gives examples of different ways to set up when the playbook is run where your "directories, stores, or remote stores" are located, so that the playbook becomes "self-documenting"?

That might simplify any documentation that we would have to do for that Ansible setup.

I feel like a number of Linux configuration files act in this way, giving example options in the comments of the config file.

We can try this way. allthough I think it is easier to find for users to have in in the documentation. Probably a shorter version in docs and a longer one as part of the code.

I think, we'll have to try out.

I was also thinking since the playbook is just text we could use the ASCIIDOC "code" formatting to display the Ansible Playbook in the documentation, of course, as the playbook is updated, the documentation would need to be updated separately.

oh, there's definitely going to be some growing pains wrt Ansible. Be prepared to move things around...

Well, let's focus on our goal for the moment:

proposed !agreed WSG agrees to the goal as defined in comment https://pagure.io/fedora-server/issue/138#comment-920322 to issue 138

I understand, there is no objections. Therefore

3

2

1

!agreed WSG agrees to the goal as defined in comment https://pagure.io/fedora-server/issue/138#comment-920322 to issue 138

!agreed Server WG agrees to the goal as defined in comment https://pagure.io/fedora-server/issue/138#comment-920322 to issue 138

OK.

Another item to discuss here?

Let's go on then

link https://pagure.io/fedora-server/issue/138

Current status so far:

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

I prepared 2 corresponding empty documents.

How do we proceed?

On Fedora Server, NFS is already installed, is Ansible? I guess I could take a stab at writing some docs next week when I'm at Flock.

@mowest NFS client is installed, not NFS server

Since I never use NFS I would not be able to do a lot with the "configuration" until I see the Ansible Playbook file that John Himpel is working on.

Ok, so I would need to step through the "required packages" for the "Installation Page" then configuration options I imagine would be clearer when I see the Playbook.

Yes, I agree. So let's postpone this until we discussed the first playbook version.

I agree that would be best to first review the first playbook before proceeding with docs.

OK, so next topic

still TBD

I really would like to a dnsmasq/tftp role with test cases so that we know that works on release

Ok, so we should probably focus on Ansible support for the next weeks to bring this substantly forward?

I would love podman module for cockpit installed by default. But I'm also wondering if Ansible support and then a series of playbooks to add the desired role for the Fedora server is the way to go, then we could have a lean mean server install that is hopefully easy to build on top of with Ansible playbooks.

next sure we're going to be able to get a lot of work done during the next few weeks, between Flock and vacation

Also under release criteria, is there a reason why the default server install doesn't create a logical volume that expands to fill the whole hard drive? I think by default it currently limits the logical volume to 16gigs or something like that. I always end up expanding the logical volume when I realize that I'm running out of space but still have GB's of space unused and inaccessible.

mowest: Yes, there is a good reason. Look at the installation introduction. We want to separate system data and workload data.

Okay, I will explore that further. Thanks for letting me know there is a reason.

Well, I think out time is up.

We should candel the meeting next week because of Flock an meet again in 14 days.

and I still have a million more things to do before Flock...

Feel better soon, I was looking forward to meeting you Peter Boy at Flock, rest and get better.

Agreed that we should cancel next meeting

I agree with canceling next weeks meeting.

OK, then, let's close

Many thanks for the good wishes. I hope I recover quickly.

See you next time

Bye bye!