17:00:17 #startmeeting fedora-server 17:00:17 Meeting started Wed Jun 15 17:00:17 2022 UTC. 17:00:17 This meeting is logged and archived in a public location. 17:00:17 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:17 The meeting name has been set to 'fedora-server' 17:00:26 #topic Welcome / roll call 17:00:35 Welcome to our Server WG IRC meeting today! 17:00:42 „Same procedure as every year“ We'll give a few minutes for folks to show up 17:00:50 Please, everybody who is lurking, say either .hello2 or .hello 17:00:58 I’ll post the agenda in a few minutes. 17:01:40 .hello2 17:01:41 cooltshirtguy: cooltshirtguy 'Jason Beard' 17:02:20 Welcome cooltshirtguy 17:03:03 hello pboy 17:03:47 .hi 17:03:48 salimma: salimma 'Michel Alexandre Salim' 17:04:07 Welcome salimma! 17:04:57 We seem to be in a small group today 17:05:38 But we now meet the quorum 17:05:58 I'll start with the agenda. Maybe some will be late. 17:06:16 #topic Agenda 17:06:24 #link https://pagure.io/fedora-server/report/Meeting 17:06:32 #info Follow up actions 17:06:39 #info Further processing of GPT as default partitioning switch 17:06:47 #info Test planning for Fedora 37 17:06:54 #info How to proceed with Cockpit File Sharing module (continued) 17:07:01 #info Open Floor 17:07:12 Any additional topic / issue / comment ? 17:07:25 You may get an overview of our ongoing and outstanding tasks at 17:07:32 #link https://pagure.io/fedora-server/boards/Works%20in%20progress 17:08:40 OK, no additions so far. 17:08:50 #topic Follow up actions 17:08:59 #info Change proposal to add Server VM is still processing 17:09:06 #link Proposal https://fedoraproject.org/wiki/Changes/Supplement-server-by-kvm-vm-image 17:09:16 #link Discussion https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/M2YQMVVUCFCV4MMOQ32UMSM5WBBVE2H7/ 17:09:43 Discussion is a bit exaggerated. Nothing so far 17:09:54 #info There is now a Change Proposal regarding the default hostname configuration 17:10:02 #link Proposal https://fedoraproject.org/wiki/Changes/FallbackHostname 17:10:13 #link Discussion https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Y2TT6VZPGTD5UVGPA6PLNYW2BU4JOC77/ 17:10:29 Anyone for a break to read the Default hostname configuration discussion thread? 17:11:24 yes 17:12:01 OK. we wait. 17:12:28 I expect, the change will be accepted. 17:13:39 As a follow up we then should adjust the naming of our volume group, I guess. I suppose, it's not that complicated. 17:14:43 .hello dcavalca 17:14:44 davide: dcavalca 'Davide Cavalca' 17:15:05 Hello dcavalca! Welcome" 17:15:53 dcavalca We have just a break to read the Default hostname change discussion on devel 17:16:14 catching up on that now, thanks 17:16:17 .hello2 17:16:18 mowest: mowest 'Steve Daley' 17:16:26 .hello2 eseyman 17:16:27 eseyman: eseyman 'Emmanuel Seyman' 17:16:41 Welcome mowest and eseyman ! 17:16:56 sorry, I'm late 17:17:14 Better late then not at all. :-) 17:17:59 We just have still a break to read the Default hostname configuration discussion thread 17:19:38 I'm ok with localhost or getting a hostname from dhcp. being a server the hostname will set to a standard via cloud-init or some kind of automation 17:19:43 OK, are we ready? Any comment / idea to the hostname topic? 17:20:28 Yes, I think it is in any case better as the current fixed "fedora". 17:20:48 anyone has thoughts on the other suggestion that came up in the thread (using fedora-)? 17:20:50 Agreed 17:20:53 agreed 17:20:56 I like the idea of leveraging systemd-hostnamed for this down the road, and just generate a unique fqdn 17:20:59 hostname from dhcp is my normal so I'm fine with that 17:21:02 but yeah IMHO just localhost is strictly better than 'just fedora' 17:21:12 but in the meantime, localhost is also fine, and better than fedora 17:21:23 look at that, everyone is saying the same thing :) 17:21:51 I tend to change to hostnames of my servers, so a generic default like localhost or getting from dhcp seems good. 17:21:53 agree that localhost is better than fedora 17:22:08 I think a unique default hostname would be fine, especially for desktops. 17:22:17 But that#s for F38, I think. 17:23:14 #agreed Server WG is content with the default hostname change proposal 17:23:40 No additional new actions to follow up. Or did I miss an open action? 17:23:55 +1 17:24:02 not really, apart from testing once the change is implemented I guess? 17:24:23 per usual 17:24:30 Yes, testing is another case. 17:24:41 Well. let's proceed then. 17:24:52 #topic Further processing of GPT as default partitioning switch 17:25:01 We have currently no issue for this topic. 17:25:08 But we have a discussion: 17:25:16 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/XHFJ67E7PXR2WHMR2766TSM7VUWCO6PF/ 17:25:32 My intention is: Agreement on the further course of action 17:25:46 Should we make break for reading? 17:26:14 yes please 17:26:26 OK 3 mins. :-) 17:26:37 document what works and what doesn't; promote Fedora Server keeping this in mind 17:27:50 Right. documenting as soon as we can what's known not to work will help drive the implementation of "GPT by default" e.g. maybe it might have to be Workstation first, and/or fixing software RAID needs to be prioritized 17:29:15 OK, I take that as a task to create a bugzilla entry for the uefi bot right now (it topic (b) ) 17:29:16 do we have any idea how prevalent software RAID is? this is 'traditional' software RAID, right, as opposed to LVM RAID? 17:29:22 https://www.systutorials.com/docs/linux/man/7-lvmraid/ 17:29:58 ah, I thought we were talking about LVM RAID all along 17:30:15 Personally, in the home lab I use software raid with btfs on the data drives. I don't use RAID on my boot drive. 17:30:18 salimma: It's a traditional raid, with a vg ont top of it. 17:31:30 That's the way Anaconda offers. 17:31:36 As far as I know 17:32:26 eseyman: yeah, I wanted to clarify because I'm assuming LVM RAID would work fine. that could be an option - we might want to look into if Anaconda can support LVM RAID or not 17:32:26 I personally only use RAID for data drives not boot drives. I might mirror the boot drive with LVM 17:32:56 We don't know how many use SW raid. We have no data. I just know a lot of discussions and questions about sw raid. It seems specifically used in private use cases. 17:33:16 salima: good idea. I'll try it before I file a bug. 17:33:23 right, for production use I'd expect hardware RAID to be more typical 17:33:53 Yes, I think every server hardware has it onboard. 17:34:08 Hey all 17:34:09 .hello ngompa 17:34:10 Eighth_Doctor: ngompa 'Neal Gompa' 17:34:29 Hi Neal 17:34:44 Hardware raid is often present even on consumer boards these days 17:35:48 OK, we had until now: 17:36:14 #action pboy to add test of uefi sw raid with LVM RAID 17:37:15 And I think, we agree to file a bug about uefi sw raid now and don't wait until the biosboot case is resolved? 17:37:29 yes, agree 17:37:31 agreed 17:37:34 That's item (b) of the mail thread 17:37:54 agreed 17:38:12 action pboy files a bug about sw raid in uefi mode 17:38:44 #action pboy files a bug about sw raid in uefi mode 17:39:20 So, what about (c)? 17:39:57 beyomd my typo is is about universal boot, to combine biosboot and efi partition 17:40:15 Neil is the expert here, I think. 17:40:26 Neal. .... sorry 17:40:37 this is out of my comfort zone; I'll abstain on c) 17:40:42 Eighth_Doctor: ^^ 17:41:57 I think he's AFK 17:43:00 I don't see a specific opinion. So let's postpone this until the current boat issues are resolved. 17:43:43 Anything else on this topic? 17:43:50 for what it's worth the UEFI case for RAID is difficult because the installer can only do some suboptimal things 17:43:52 3 17:44:02 2 17:44:11 1 17:44:21 it's largely an unsolved problem without a service that takes responsibility for syncing multiple EFI System partitions 17:44:21 #topic Test planning for Fedora 37 17:44:30 We have currently no issue for this topic. 17:44:39 Proposal: We should aim for a test *week* with Fedora QA and make this a permanent practice for the next releases. 17:44:46 We would get something like: 17:44:54 https://testdays.fedoraproject.org/events/132 17:45:31 This would be a significant improvement over our approach to F36 17:45:39 huge +1 from me 17:45:45 First time preparation is a lot of work and will be incomplete in a first shot. But we can carry it further to the next releases and improve it step by step. 17:45:51 One advantage I see: We can offer our users a way to participate and also contribute their problem cases or important elements. 17:45:58 And hopefully we will succeed in gaining one or the other active new member. 17:46:27 +1 from me, having a specific time frame and clear goals for testing would help me focus my limited time for QA. 17:47:41 agree with mowest 17:47:56 OK 17:48:07 #agreed Server WG will strive for a test week for F38 and follow up releases 17:48:28 The plan would be: 17:48:36 1. Next meeting discussion of our Technical Specification 17:48:43 2. In 4 week’s meeting discussion of release criteria and a first collection of tests. 17:48:58 3. Contact Adam for implementation 17:49:21 3. Improve the test setup 17:49:32 3. -> 4. 17:50:19 Any additional comment. / idea here? 17:50:32 3 17:50:40 2 17:50:46 1 17:50:46 looks good to me 17:50:55 #topic How to proceed with Cockpit File Sharing module 17:51:04 #link https://pagure.io/fedora-server/issue/86 17:51:10 As discussed I created 2 documentation stub regarding the NFS part that we needs to complete 17:51:26 https://docs.stg.fedoraproject.org/en-US/fedora-server/service-filesharing-nfs-installation/ 17:51:33 https://docs.stg.fedoraproject.org/en-US/fedora-server/service-filesharing-nfs-administration-cockpit/ 17:52:03 It's difficult topic. Anyone any idea? 17:53:13 I can only report that after my upgrade to F37 I saw the NFS file sharing in Cockpit, haven't tried setting it up through Cockpit. Not normally something I use, but I should try it to do QA on it. 17:54:19 my NFS needs are trivial and I don't need an admin module for Cockpit. I'll sit this one out 17:54:39 Yeha, QA test is on thing. Another is to document, for what is is usable, and for what it is not. 17:54:40 personally i would setup NFS server through automation. 17:55:03 there's a push for cockpit for doing administrator tasks 17:55:11 though 17:55:46 Well, Cockpit is one of our featured administration tools, beside CLI 17:56:31 cooltshirtguy: Could you provide some ideas / hints we should include in an NFS installation article? 17:57:03 agreed but some things (apache and nginx also come to mind) can be configured 1000s of ways 17:57:26 so WebUI/GUI interfaces are hard to do 17:57:44 eseyman: yes, but we should provide at leas one tested way of those thousends. :-) 17:58:03 I could give some. I haven't configured all the ways you can do NFS 17:58:42 coolshirtguy: OK, let'do it on mailing list or so. So we will have a start. 17:58:57 Well, we are running out of time 17:59:18 Let's make a quick switch to open floor. 17:59:25 #topic Open Floor 17:59:37 So, any idea here? 18:00:17 Obviously not. 18:00:23 hahaha 18:00:28 Time is up, anyway 18:00:31 We are end of time, so I'm good 18:00:44 all good 18:00:48 same here 18:00:51 Yeah, was a good session today! 18:00:59 Thanks everybody for comming. 18:01:13 #endmeeting