18:00:30 #startmeeting fedora-server 18:00:30 Meeting started Wed Dec 6 18:00:30 2023 UTC. 18:00:30 This meeting is logged and archived in a public location. 18:00:30 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:30 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:30 The meeting name has been set to 'fedora-server' 18:00:43 #topic Welcome / roll call 18:00:52 Welcome to our Server WG IRC meeting today! 18:01:06 „Same procedure as every year“ We'll give a few minutes for folks to show up 18:01:20 We have to coninue with topics we skipped last meeting. 18:01:26 humm... I was in #fedora-meeting-1 wondering where everybody was 18:01:30 hi, folks! 18:01:31 I’ll post the agenda in 2 minutes. 18:01:48 .hello2 18:01:50 jdubby: Sorry, but user 'jdubby' does not exist 18:01:56 .hello2 18:01:57 eseyman: eseyman 'Emmanuel Seyman' 18:02:06 Hi eseyman! Yes, sometimes quick to get the wrong cxhannel 18:02:43 .hello2 18:02:44 jdubby: Sorry, but user 'jdubby' does not exist 18:04:58 Hi John: zodbod seems to be a bit disoriented today. 18:06:18 We are obviously „thin provisioned“ today. But we met the quorum and can start. 18:06:30 #topic Agenda 18:06:42 #info Follow up actions 18:06:42 #info Fedora Server release and quality criteria 18:06:42 #info Work program and goals for F40 18:06:42 #info Test planning for F40 18:06:42 #info Open floor 18:06:53 Any topic to add? 18:07:09 I'm good 18:07:13 OK, let's go on 18:07:27 topic 1. Follow up actions and announcements 18:07:33 #topic 1. Follow up actions and announcements 18:07:42 A still running gag is: 18:07:53 #action pboy will write a info about changing the timeout value and nirik will review – still work in progress 18:08:04 And we have a new one, I guess ongoing, too? 18:08:16 * pboy Mowest will take care of discussed modifications of the Server download page. 18:08:37 Mowest is unable to attend today, so 18:08:46 #action Mowest will take care of discussed modifications of the Server download page. 18:08:57 For all to know: 18:09:09 Next big OSS meeting: FOSDEM, 3 & 4 February 2014 Brussels, Belgium, Europe 18:09:20 Fedora will be present with a stand and is planing some actions. 18:09:37 Unfortunately, the deadline for submitting proposals for contributions was very short and has passed. 18:09:46 Would be nice if we could contribute to the Fedora stand and presentation and hopefully some of us can take the opportunity to meet. 18:09:58 And by the way: France and Germany are close by and also a worthwhile destination for a visit before or after. 18:10:07 Any thjoughts? 18:11:27 it's complicated 18:12:09 Yeah, probably for anyone to think about it. 18:12:18 I'll attend in any case. 18:12:51 I'll attend if I can convince my SO 18:13:04 What is SO? 18:13:25 SO == Significant Other 18:13:42 Oh yeah, fortunately I could manage that already :-) 18:14:00 Well, Last one here: Next meeting? 18:14:10 roposal: xskip Dec 20 and Jan 3 and start with Jan 17 18:14:23 into new year 18:14:32 sounds like a good call 18:15:21 OK I guess jdubby is still struggeling with zodbot, but would agree, too. 18:15:34 #agreed Next meeting will be held January 17, 2024 18:15:54 topic 2. Fedora Server release and quality criteria 18:16:00 #topic 2. Fedora Server release and quality criteria 18:16:17 I must practise copy&paste, obviously 18:16:34 #link https://pagure.io/fedora-server/issue/63 18:16:43 #link https://pagure.io/fedora-server/issue/61 18:17:02 One special topic here: naming of distribution media, the "DVD topic" 18:17:16 We agreed upon std instead, but that has a unfortunate connotation as well, as we detected later. 18:17:55 new idea: a) maybe full or fullinst (like netinst) or full and just net (and kvm) 18:18:06 b) same naming convemtion for full install and vm install 18:18:29 c) one checksum file for all variants (currently 2 separate, but the same name) 18:19:32 Any thoughts? 18:21:21 not a lot, tbh 18:22:32 Yeah, and we need native speakers, I think. Last time, if I remember, Nirik came up with the bad connotational meaning 18:22:55 OK, we discuss that on server list. 18:23:46 jwhimpel are you with us? 18:23:50 yes 18:23:58 Thanks! 18:24:30 The other think is to review and to extend our quality and release criteria. 18:25:13 I suppose, we need someone of us who takes on the organisation and to encourage the discussion. 18:25:42 Sgallagh madew some suggestion a long time ago. 18:26:39 For sure, he will work with us, but we need a "discussion lead". 18:27:46 I see, no idea here. 18:28:26 Does anyone know, what we have to do to extend those criteria? 18:29:04 no idea 18:29:26 OK. me neither 18:29:55 same 18:30:06 So, I'll contact Stephen to help us out. 18:30:46 #topic 3. Work program and goals for F40 18:30:59 #topic 3. Work program and goals for F40 18:31:14 #link https://pagure.io/fedora-server/issue/102 18:31:14 #link https://pagure.io/fedora-server/issue/101 18:31:37 Problem, we did not finish our goal for F39 yet. 18:32:40 Nevertheless, I would like to start with another one, e.g. the installation in virtual environments 18:33:14 Hopefully, we can provide new installation media so will produce something new. 18:33:38 'Fedora Server Edition on SBC' can by recycled for F41 18:34:02 eseyman, good idea! 18:34:15 specifically, the installation issues are not resolved yet. 18:35:42 I see no objections about 'installation in virtual environments' 18:36:09 But I think, we should this put on mailing list as well. 18:36:27 So let's switch here. 18:36:36 #topic 4. Test planning for F40 18:36:57 We should discuss and organize 2 topics, I think 18:36:57 a) What do we want to manually test? I suppose, at least a regular "smoke test" of the mist important features 18:36:57 b) What are the potentially critical changes that we should specifically monitor and test? 18:37:13 I don't know if this is off topic now, but it appears anaconda changes (first boot) and Unified Kernel Support may both affect us. We need to test often and early. 18:37:24 agreed 18:37:49 jwhimpel, it is not off topic. but paet of b) 18:37:58 And there are others: 18:38:06 announced change in Anaconda, allthough not yet for F40 18:38:06 UKI image 18:38:06 change in cron 18:38:37 And we will get a new Anaconda install GUI, not in 40 I gues, but later. 18:39:03 We should start to cooperate early. We want to update the installationmenues anyway. 18:39:21 We probably need to test new install as well as upgrade. Also test ARM as well as Intel/AMD. 18:39:43 jwhimpel agreed 18:40:34 I'm trying to set up virtualisation on my m1 Mac so i can at least limited the aarch64 distrib 18:40:59 Should we test DVD (or other media) install along with netinstall? 18:41:13 I think, yes. 18:41:26 I think, one of us should take the organisation of this in his hand. 18:41:26 Someone should watch the devel list, bring potentially disruptive changes to our attention (mailing list) and collect them in a ticket. 18:41:39 I don't have any ARM architecture at the moment, but I hope to procure a Pi5 soon. 18:42:15 We also need to monitor the workstation meeting logs as they seem inclined lately to assume how changes will affect server. 18:42:26 Yeah, but as far as I know, the Pi5 has the same boot methods as Pi4. 18:42:44 So you can 't test dvd and netinst 18:43:18 On a new Mac that would be possible, at least virtually 18:43:43 I think I can test ARM stuff if I don't try to use LVM. But I could be very wrong. 18:45:10 The problem is, that Pi5 / aarch64 SBCs dont have a BIOS or a "system ready" firmware. As far as I know. 18:45:46 So it will not boot our standard installation media / isos 18:47:15 do people actually do this? I suspect that vast majority of Pi5 users are going to burn Fedora to an SD card and plug it in 18:48:22 esseyman: I agree 18:48:38 eseyman Yes I think so, because it is the only way, currently. There is a kind of system ready stand in but unsupported in Fedora. 18:49:31 For information: The current installation problem with Pi and other SBCs has not yet been resolved. 18:49:46 It is probably an LVM problem. (with lvscan) 18:49:59 I am working on it with the ARM sig and releng 18:50:35 I would really like the testing to focus on stuff that Fedora users will actually use 18:50:58 eseyman agreed! 18:51:05 That is why I volunteered to test NOT using lvm. Just raw partitions. 18:52:00 jwhimpel currently LVM is our default method for "real" Fedora Servers. Do you propose to change that? 18:52:36 Not necessarily. Just wanted to offer a way to use Fedora Server until the issue is resolved. 18:52:54 OK. yeah. 18:53:31 I think it will be resolved soon via update (I'm an optimistical guy) 18:53:58 Well, let's continue on mailing list and switch 18:54:01 I also seem to remember an article on phoronix that btrfs has some patches that make it perform better under typical server loads. 18:54:14 #topic 5. Open Floor 18:54:51 What do you think about setting up one of our next meetings as a video meeting? 18:55:02 instead of IRC 18:55:13 I was able to get ansible to deploy wildfly with ssl certs. Then use maven to deploy a simple quickstart app. 18:55:31 jwhimpel ++1 18:55:36 pboy That would be so much better for those of us observing! 18:55:39 I spent the day at the Open Source Experience event in Paris 18:55:46 pboy: Video meetup sounds good to me. 18:56:09 my attempts to convince the Centreon guys to add Fedora Server as a supported platform was a bust 18:56:27 eseyman what a pitty 18:56:45 if it's one-time-only, a video meeting sounds good 18:57:27 eseyman, yes, one time at least at the moment. And a test how it works for us. 18:57:51 I'll try it either for our January meeting of the firstr February. 18:58:46 jwhimnpel regarding Wildfly, we should discuss that on our next meeting! 19:00:00 OK, time is up now. 19:00:11 pboy: I'll try to be prepared. 19:00:36 I wish a good christmas and a happy new year.! 19:00:54 same here, see you in 2024, folks! 19:01:09 And see you in January in new freshness and energy 19:01:30 #endmeeting