18:00:31 #startmeeting fedora-server 18:00:31 Meeting started Wed Jan 17 18:00:31 2024 UTC. 18:00:31 This meeting is logged and archived in a public location. 18:00:31 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:31 The meeting name has been set to 'fedora-server' 18:00:48 #topic Welcome / roll call 18:01:03 Welcome to our Server WG IRC meeting today! 18:01:22 „Same procedure as every year“ We'll give a few minutes for folks to show up 18:01:24 .hi 18:01:25 sgallagh: sgallagh 'Stephen Gallagher' 18:01:45 I’ll post the agenda in about 2 minutes. 18:02:07 Hi Stephen! 18:02:15 I’m only kind of here. I’m suffering from a migraine and can only look at the screen for a few minutes at a time. Please mention me directly if you need my input. 18:02:27 .hello2 18:02:28 cooltshirtguy: cooltshirtguy 'Jason Beard' 18:02:28 OK git it 18:02:43 Hi Jason! 18:02:52 Hello! 18:04:37 OK, we meet the quorum, so let's start 18:04:47 #topic Agenda 18:04:55 .hello2 18:04:56 jwhimpel: jwhimpel 'John Himpel' 18:05:05 #info Follow up actions & announcements 18:05:05 #info Add module cockpit-navigator to default Installation 18:05:05 #info LLMNR should be disabled in systemd-resolved in f39 (and later) 18:05:05 #info LVM configuration 18:05:05 #info Test planning for F40 18:05:14 #info Work program and goals for F40 18:05:14 #info Open floor 18:05:35 I suppose, we have enough topics and don't need some more :-) 18:05:42 Hi John! 18:05:58 i think that's plenty 18:06:18 Yeah, let's go on. 18:06:28 #topic 1. Follow up actions and announcements 18:06:36 A still running gag is: 18:06:48 #action pboy will write a info about changing the timeout value and nirik will review – still work in progress 18:07:04 There will be a time we get this done. hope dies last 18:07:13 nd we have a new one, I guess ongoing, too? 18:07:24 CTION: Mowest will take care of discussed modifications of the Server download page. 18:07:47 We are missing mowest at the moment 18:08:05 #action Mowest will take care of discussed modifications of the Server download page. - still work in progress 18:08:16 And there is a Proposal: 18:08:25 proposed #agreed We schedule an additional meeting at Wednesday, January 31 18:00 UTC 18:08:36 January has 5 Wednesdays. We should use the additional Wednesday in 14 days for an additional meeting to discuss and make upcoming decisions soon. 18:08:52 Any thoughts about it? 18:09:08 I agree that we ought to meet. 18:09:20 additional meeting is fine 18:09:25 thanks, eseyman agreed as well. 18:09:29 OK, so 18:09:39 #agreed We schedule an additional meeting at Wednesday, January 31 18:00 UTC 18:09:50 For all to know: 18:09:59 Next big OSS meeting: FOSDEM, 3 & 4 February 2014 Brussels, Belgium, Europe 18:10:09 Fedora will be present with a stand, see 18:10:09 #link https://fedoraproject.org/wiki/FOSDEM_2024 18:10:27 I'll participate 18:10:38 aybe one or the other can still take part at short notice. A dinner is planned for Saturday evening. :-) 18:10:53 #topic 2. Add module cockpit-navigator to default Installation 18:11:03 #link https://pagure.io/fedora-server/issue/111 18:11:17 We have to decide whether we want to include the module in its current state and who will take care of it. 18:11:37 I checked it shortly, I think it works fine. 18:11:45 Did anybody check the module? 18:12:23 I maintain it. I do want to point out that upstream hasn’t made a new release in over a year. I’m not sure whether they consider it stable or abandoned. 18:12:41 i completely missed it. 18:13:09 sgallagh I think it is a new module, developed by an Google intern last sommer, isn't it? 18:14:12 Maybe I’m confused. Are we not talking about the one from 45Drives? 18:14:54 The name is cockpit-navigator and it is listed on the project page amoung the core modules, not the third party 18:15:18 Ah, then I probably need to retire the 45Drives one and make sure the official one replaces it. 18:15:43 Ok, to be sure I'll check with Martin Pit. 18:16:15 Question, de we need a Change prososal to make it a part of our installtion media? 18:16:48 https://github.com/cockpit-project/cockpit-navigator appears to be an updated version of the 45Drives one, but merged into the main Cockpit project. 18:17:14 Need? No. It would be good to do it for publicity reasons though. 18:18:15 Oh,thanks. First I'll check with Martin and come back next meeting with the topic. And if it is good for public, w'll make a proposal, I think. 18:18:35 Any objections against this procedure? 18:18:49 nope 18:19:00 OK, next topic. 18:19:04 sgallagh: The https:cockpit-project.org/applications page shows the 45Drives module is the Navigation feature for cockpit. 18:19:37 It looks like Cockpit took over the maintenance 18:20:40 Yes, and I had a wrong look at that page, sorry about it. 18:21:09 I think I was so eager about navigator, I overlooked the most import item. 18:21:33 Martin Pit advised against the module last sommer. 18:21:56 Let us ask him again. 18:22:46 Do we agree about asking Martin for advise and decide next meeting? 18:23:00 +1 18:23:20 +1 18:23:33 hi, folks. Sorry I'm laste 18:23:34 +1 18:23:39 #agreed pboy will ask Martin Pitt for advise about cockpit-navigator 18:23:40 s/laste/late/ 18:23:47 .hello2 eseyman 18:23:48 eseyman: eseyman 'Emmanuel Seyman' 18:23:53 eseyman welcome, better late then not 18:24:10 well, next topic 18:24:22 #topic 3. LLMNR should be disabled in systemd-resolved in f39 (and later) 18:24:33 #link https://pagure.io/fedora-server/issue/114 18:24:35 sorry, the weather made biking a no-go and the bus went kind of nuts 18:24:51 I'm completely lost with this topic. 18:25:02 But there is some severe discussion. 18:25:58 eseyman I enjoy working from home 18:27:35 I like going to the office 40% of the time but it really needs to be by bike 18:29:00 Any idea how to proceed with this topic? We already had a discussion some time ago, but I don't remeber the details. 18:30:15 And I think, there was a change proposal or a FESCo discussion. But I can't find it. 18:30:54 it does look sensible to disable LLMNR 18:31:14 There’s a discussion on the devel list about a dnsmasq default change that’s conflicting with resolved. It may or may not be related. 18:32:41 Well, maybe we postpone until the devel discussion comes to an end, and maybe FESCo says something abou it? 18:33:07 And we should coordinate with CoreOS and IoT, I suppose. 18:33:44 Probably best to start a new discussion on the devel list 18:34:15 With the intent of getting FESCo to make a decision clearly stated. 18:34:29 OK, that's a good idea. 18:34:45 yes, sounds fair 18:34:54 sound good 18:35:18 *sounds good 18:35:48 proposal #agreed pboy will start a new discussion on the devel list and maybi involve FESCo to make a Fedora wide decision 18:36:14 and a final decision 18:36:59 I see no objections 18:37:38 #agreed pboy will start a new discussion on the devel list and maybe involve FESCo to make a Fedora wide final decision 18:37:53 #topic 4. LVM configuration 18:38:04 was Aarch64 SBC Installation bug on Fedora Server 18:38:15 #link https://bugzilla.redhat.com/show_bug.cgi?id=2258764 18:38:23 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246871 18:38:30 ome info: 18:38:41 It's clear now, it is not a bug, but a new 'feature' in LVM configuration. 18:38:51 LVM is since F38 configured to just 'see' devices listed in /etc/lvm/devices/system.devices 18:39:02 The arm-image-installer issues are a follow up of this re-configuration. 18:39:11 You connect a new devise, usually an SD card or SD card adapter, and copy the installation image onto it. 18:39:20 So the new SD card device has a partition with a new VG, which is now not visible for LVM by default configuration 18:39:28 I suppose, if you use vgscan for new VGs there is a big chance it is on a new device. 18:39:38 On the other hand I think, LVM maintainer had a good reason to change the default configuration. But I don't know what it could be. 18:39:48 The proposal is, to switch back to the behavior of F37. 18:39:59 Alternatively, arm-image-installer would have to reconfigure LVM temporarily. But I don't know if it's that easy. 18:40:06 So we dont know why the change was made? 18:40:22 End of info 18:40:53 At least I dopn't know. And there was no info in the bug reporet discussion. 18:40:59 yes, I wonder what the purpose of /etc/lvm/devices/system.devices is 18:42:09 Well, we could try to get some information from the maintainers. 18:42:36 I think, it could be helpful 18:42:58 I think it's critical before making a decision 18:43:10 You arfe right. 18:43:13 i think it's important to know 18:43:45 eseyman, could you try to make contact? E.g. by adding a comment /question to the bug report? 18:45:16 (I'm still a bit annoyed about the many hours of wasted work just because no information was provided.) 18:45:44 pboy: yes, I can do that 18:45:55 eseyman 1++ 18:46:23 #agreed eseyman will try to contact the maintainers and get information why the change was made. 18:46:36 #action eseyman will try to contact the maintainers and get information why the change was made. 18:47:03 We will pick up the topic next meeting 18:47:16 Ready for next topic? 18:47:40 Go! 18:47:46 no objections we go on 18:47:52 go on 18:47:55 #topic 5. Test planning for F40 18:48:07 #link https://pagure.io/fedora-server/issue/125 18:48:12 Some input 18:48:22 We should discuss and organize 2 topics, I think 18:48:31 a) What do we want to manually test? 18:48:42 At the very least, we should conduct a "smoke test" of the installation media and also of the most important functions. 18:48:53 b) What are the potentially critical changes that we should specifically monitor and test? 18:49:01 what is the preferred method to install F40 Server for testing at this time? Install F39 Server, then update from rawhide? 18:49:04 I think, one of us should take the organisation of this in his hand. 18:49:42 A Test Day seems to be the best of doing this 18:49:47 jwhimpel I always installed from branched, ifavailable 18:50:11 it does require coordination with the QA team 18:50:23 eseyman yes veery much agreed. We should prepare that for next release 18:50:35 for f40 it is too late 18:50:38 I test the Workstation Beta but not the server. I should really include this in my workflow 18:50:56 Where would one find a new installable ISO? Is the cli upgrade path ready to upgrade to F40? 18:51:34 jwhimpel there is a mail from rawhide regurlarly with all the links to server isos. 18:51:55 I think, you have to subscribe the devel list 18:51:59 the isos are available when Beta lands, for sure 18:52:16 Or maybe another list, let me have a look .... 18:52:51 pboy: Thanks for the info about the ISOs. But Beta is getting awfully late to start testing. I am subscribed to fedora-devel list. 18:54:27 jwhimpel it is test-announce@lists.fedoraproject.org there is a about biweekly mail with all the links. I forward the latest to you. 18:55:05 pboy: I subscribe to that list also, so I will pay more attention seeking out those emails. 18:55:30 jwhimpel ++1 18:56:28 Anyone happy to watch the changeset and arganize our tests for f40 (NOT to do all the test. We should share that part) 18:57:22 If I wanted to test "DNS System Plugin Upgrade" from F39 to F40, which repository should I enable? 18:58:34 I think, if you download the latest installation media friom said list, the correct repo is enabled. 18:58:51 Have a look at that address. 18:58:57 I have zero knowledge on how any of this works. 18:59:41 cooltshirtguy Best occasion to make a first step :-) I had a steep learning curve 19:00:41 The docs for DNF System Plugin Upgrade say to use either "Branched" or "Rawhide". Is there a rule of thumb or a timing constraint as to which one to use? 19:01:02 Well, our time is up. We should continue on mailing list and next meeting in 14 days. 19:01:15 bye 19:01:46 jwhimpüel yes, branched is available after the branch step is done, as far as I know. You see that on the name of the installation media. 19:01:57 bye bye 19:02:06 l8r 19:02:12 #endmeeting