18:00:17 #startmeeting fedora-server 18:00:17 Meeting started Wed Feb 7 18:00:17 2024 UTC. 18:00:17 This meeting is logged and archived in a public location. 18:00:17 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:17 The meeting name has been set to 'fedora-server' 18:00:31 #topic Welcome / roll call 18:00:36 hello, pboy 18:00:43 Welcome to our Server WG IRC meeting today! 18:00:43 This is an out of order meeting to follow up on our Jan 19 meeting. 18:00:43 „Same procedure as every year“ We'll give a few minutes for folks to show up 18:00:47 .hello2 eseyman 18:00:48 eseyman: eseyman 'Emmanuel Seyman' 18:00:53 hello eseyman 18:01:05 just in time, mowest 18:01:10 hello mowest! Glad to see you! 18:01:19 Good to be back 18:01:33 .hello2 18:01:36 mowest: mowest 'Steve Daley' 18:02:25 Let's start. I post the agenda 18:02:34 .hello2 18:02:35 jdubby: Sorry, but user 'jdubby' does not exist 18:03:09 #topic Agenda 18:03:22 #info LVM2 default configuration change 18:03:22 #info Test planning for F40 18:03:23 #info A "story" for each release) 18:03:23 #info Work program and goals for F40 18:03:23 #info Revisiting Fedora Server release criteria 18:03:23 #info Open Floor 18:03:33 Any topic to add? 18:03:45 I'm good 18:03:54 OK 18:04:03 #topic 1. LVM2 default configuration change 18:04:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=2258764 18:04:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246871 18:04:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=2247872 18:04:12 .hello jwhimpel 18:04:13 jdubby: jwhimpel 'John Himpel' 18:04:23 Hi John! 18:04:44 so this has been a massive disappointment 18:05:04 eseyman Do you have news here? 18:06:00 no, I've just followed what little has happened 18:06:31 yeah, the main processing is now https://bugzilla.redhat.com/show_bug.cgi?id=2247872 18:06:49 I discussed the issue on Monday on the QA meeting. 18:07:20 adamw will try to get some information from LVM group. 18:07:36 I hope he has better luck than I did 18:07:54 Yeah. 18:08:45 Next Monday starts blocker discussion. And this bug should be or already is a blocker. I'll participate in that session. 18:09:09 what time is that meeting? 18:09:45 eseyman, i don't know yet, around 17:00 european time, if I remember correctly 18:10:03 I'll forward the announcement as soon as I get it. 18:10:51 ok, I can attend that meeting 18:11:16 I made a rather specific proposal in https://bugzilla.redhat.com/show_bug.cgi?id=2247872 #8 18:11:33 #link https://bugzilla.redhat.com/show_bug.cgi?id=2247872#c8 18:12:01 Any idea about it here? Could that be the current Server WG position? 18:12:02 None of those thrill me, FWIW 18:14:59 Any question or comment about #8? Any objection? 18:15:42 Did you get to discuss the issue with anyone at FOSDEM? 18:15:59 Unfortunately not. 18:16:56 But there is other good news, will talk about it with topic 4 18:17:55 Well, I see no objection, so we agree about it. 18:19:19 #agreed WG agrees about the proposal https://bugzilla.redhat.com/show_bug.cgi?id=2247872#c8 , according to our current information we currently have. 18:19:32 Next topic. 18:19:44 #topic 2. Test planning for F40 18:19:54 #link https://pagure.io/fedora-server/issue/125 18:19:54 #link https://hackmd.io/NtO4O9vRT3a71UMZMkceoA?both 18:20:12 We should discuss the task list, the item list and potentially critical change proposals., I think. 18:20:34 That hackmd.io link gives me a 403 18:21:04 Hm, I suppose you must login? 18:21:44 I am logged in 18:22:43 OK,. i changed the permissions. Obviously, the default changed. 18:22:51 Does it work now? 18:22:59 YES, MUCH BETTER 18:23:09 sorry, caps lock was on 18:23:20 I'll just ask on matrix if adamw is available 18:24:13 I can reach the mackmd.io link just fine. 18:25:17 OK, so it works now, reading everyone, writing logged in usersers 18:26:45 When I updated bare metal from F39 to F40, I could no longer access the VM's on that host via virt-manager. I finally figured out that I had to relabel everything for selinux. 18:27:35 jdubby that's bad. relabel the host or the vm? 18:28:05 Would someone else please see if they can replicate the issue before I file a bugzilla. I had to relabel the host not the VM. 18:28:41 Yes, we need a 2nd pair of eyes. 18:29:15 And is it specific to virt-manager or is Cockpit and CLI affected, too? 18:29:20 Virt-manager could not access /run/libvirt/common/system.token 18:29:32 I only tried virt-manager. Sorry 18:30:31 No problem, if I remember correctly, virt-manager is deprecated now, but still widely used on graphical desktops. So it is important. 18:32:33 Question is, where we collect the findings. There use to be a QA result page, but I can't find it at the moment. And Adam is obviously not online. 18:34:38 jdubby can you ask on users, what the status of virt-manager is (deprecated or not) and what the supported way on graphical desktops is? 18:35:01 Sure 18:35:12 ++1 18:35:31 Well, any other comment? 18:37:46 Regarding the results, for the time being we should add a foot note number in the Remark column and a short description beyond the table. 18:39:21 Well, I see no generic comments. 18:39:48 So do we agree about the test tasks and the test items so far? 18:40:18 yes, this is fine 18:40:23 OK. 18:40:55 #agreed WG agrees about the test task and test items list in https://hackmd.io/NtO4O9vRT3a71UMZMkceoA?both 18:41:25 virt-manager is a thin veneer over libvirt, so it's highly unlikely that cockpit or virsh would have worked where it didn't 18:41:59 Well, in the next step it would be good, if erveryone cold take on 1 or 2 items and add himself in the tester columnr 18:43:31 I already took the raid task, because I have the equipment to do it. Otherwise, I'll let others select first. 18:44:11 sgallagh thanks for the info! 18:44:53 Sorry, only checking the logs here every few minutes. Busy day with the EL10 fork next week 18:46:03 sgallagh Yes, I read about it. So I am all the happier that you are thinking of us, too :-) 18:46:55 Part of the reason I'm here was to suggest that future meetings be held on Matrix where I don't have to make a conscious effort to dig out an IRC client to join :) 18:47:03 (I was going to suggest that during Open Floor) 18:47:10 Well, I think, the next issue to check the change proposal set for potential critical items. 18:47:20 sgallagh I too 18:47:48 Would someone check the list for our next meeting? 18:48:18 I can do that 18:48:19 Next Mondoy (13.) is the branching date. 18:48:55 Then the list should be final (more or less) 18:49:02 eseyman thanks 18:49:45 #action eseyman will check the change proposal set for items we should aware of and care about. 18:50:20 Next topic 18:50:30 #topic 3. A "story" for each release 18:51:13 I guess, I'll open a thread on our mailing list, so we can exchange ideas there. 18:51:28 Our time is nearly up 18:52:13 Same is true for topic 4 18:52:46 And we should postpone topic 5 until we managed the urgent ones for F40 18:53:00 Any objections? 18:53:07 nope 18:53:15 ok 18:53:25 #topic 6. Open Floor 18:53:44 As noted above, I was going to suggest moving the meetings to Matrix 18:54:03 One think we have to discuss it the move of Fedora to matrix as the preferred communication channel and what we want to do about it. 18:54:15 There are 2 parts: 18:54:18 There is now support for meeting commands (see https://fedoraproject.org/wiki/FESCo_meeting_process for example usage) 18:54:32 Yes, there are 2 parts: 18:54:52 What matrix client is recommended for Fedora users? 18:54:54 For those of us using Fedora Workstation, what are our choices in GUI Matrix clients? TUI clients? 18:55:02 I thought that Matrix and IRC channels were supposed to be linked or bridged. 18:55:18 mowest: was true at one point but no longer is 18:55:29 1. our meetings, moving from IRC meeting to Matrix meeting 18:55:42 and the bridge isn't coming back 18:55:45 2. our communication, mailing list or Matrix chant 18:56:34 Right, the IRC-to-Matrix bridge has been down for a year and there are no plans to reconnect them (and at this point, most people have migrated to Matrix) 18:56:37 and regarding Matrix clients: the browser plugin works really good. The preferred app is elements. Works very fine, too 18:56:58 I'm probably the only one, but the death of IRC is a bummer to me. I like CLI interfaces. 18:57:12 mowest 1++ 18:57:17 I'm in weechat right now. 18:57:17 As for a Matrix client, it doesn't really matter. They're all going to the same place. I use the Elements browser app via https://chat.fedoraproject.org myself. 18:57:40 But I have to admit, for chat and arguments Matrix is better than IRC, more comfortable. 18:57:40 mowest: https://xkcd.com/1782/ 18:58:51 sgallagh: Nice :-) 18:59:03 My idea is: meeting on Matrix, communication still using mailing list. 18:59:21 pboy: +1 18:59:28 I'm willing to bend to the will of the WG. 18:59:53 mowest you shouldn't "bend" 19:00:10 Okay submit... 19:00:13 but be "happy" with exciting new ways :-) 19:00:56 I was reluctant first, too. And I live CLI, I have more than 100 key to do the work, not just 3 as with a mouse 19:00:57 Just include a link that will open Matrix in the announcement email. 19:01:06 pboy: Wayland folks will be happy to hear that ;-) 19:01:39 yeah, I'm going to need an alternative to the Web UI... 19:02:03 OK, we switch to Matrix with the next session and I include the correct link. 19:02:04 https://matrix.org/ecosystem/clients/ 19:02:16 #agreed WG will continue meetings on Matrix 19:02:27 There are CLI clients there, notably gomuks 19:03:02 Other topic: next Flock 19:03:47 Flock 2024 will be in first half of August, somewhere in America 19:04:32 Would be nice we we could use the opportunity to meet in-person, at least some of us. 19:04:45 I intend to be there 19:05:09 sgallagh me too 19:05:25 I can try to make it 19:05:57 Or we could organize a hybrid talk or workshop, half in-person, half via video conference 19:06:12 eseyman ++1 19:06:49 Under specific circumstances there may be a chance to get some funding. 19:06:49 looks like a duel between Rochester, Montréal and Ciudad de México 19:06:53 I found that workshops with a 5-10 minute intro session worked best for things like Fedora Server and Modularity at Flock 19:07:45 Yes, the default duration of a workshop is 90 mins. 19:07:53 Flock (for me, at least) has always been a great conference for Getting Things Done 19:08:16 vs. DevConf, RH Summit and such which are more like showcases 19:08:37 Yes! It was my first Flock last year, and it was great! 19:09:30 Well, even the talk was quite productive. I talked about our plans, and how to do it. And I got a lot of good feedback and proposals. 19:10:16 Oh, I see, our time is up! We have already overdrawn. 19:10:33 So, anything here to add? 19:11:29 I see none 19:11:58 So, meet you in 2 weeks again, on Matrix than (what an adventure) 19:12:09 bye bye 19:12:14 bye, folks 19:12:25 #endmeeting