17:00:13 #startmeeting fedora-server 17:00:13 Meeting started Wed Apr 28 17:00:13 2021 UTC. 17:00:13 This meeting is logged and archived in a public location. 17:00:13 The chair is pboyHB. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:13 The meeting name has been set to 'fedora-server' 17:00:23 #topic roll call 17:00:30 hi everyone! 17:00:37 As usual we should give a few minutes for folks to show up 17:00:42 .helo jwhimpel 17:00:45 #info please say either .hello2 or .hello 17:00:51 I’ll post the agenda in a few minutes. 17:00:54 .hello jwhimpel 17:00:55 jwhimpel: jwhimpel 'John Himpel' 17:01:15 .hi 17:01:16 dcavalca: dcavalca 'Davide Cavalca' 17:03:08 #topic Agenda 17:03:18 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/32IQLMZDPUS7JCF2FFRVJO5IAYYQLEL4/ 17:03:24 1. Welcome 17:03:30 2. Agenda 17:03:37 3. Status Server PRD (Info) 17:03:44 4. Fedora release criteria and process 17:03:53 5. Issue: Release composition 17:03:59 6. Planing for next Fedora release 17:04:07 7. Marketing Improvement / Ambassadors Material 17:04:14 8. Open Floor 17:04:45 #topic Status Server PRD 17:04:54 #link https://hackmd.io/@x3mboy/HyB92cVl_ 17:05:02 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/NAQLPATYHK3EPY3DHHU7HS5CQ7NPLVVR/ 17:05:09 .hi 17:05:10 x3mboy: x3mboy 'Eduard Lucena' 17:05:14 Short summary: 17:05:21 Latest version at first link above 17:05:28 Waiting for Text from ab and michel_slm 17:05:36 Planning: final decision next meeting or 12 May latest 17:05:47 Now and in the next 3-4 days it is still possible to make substantial changes / additions / deletions without delaying everything even further. 17:05:57 Any ideas / comments / concerns? 17:06:40 I'll work on my part this week but I didn't have much time yet, sorry. Family care. 17:06:52 * ab is not really present here due to that 17:07:27 ab: that's fine for me. Maybe, we should directly target May 12? 17:08:23 perhaps. I'll respond to the thread on server mailing list 17:08:36 I'd like to give some time for discussion 17:09:37 OK. We should not rush. Therefore: last chance for any modification: May 5, final discussion and voting: May 12 17:09:44 objections? 17:09:50 +1 17:10:12 +1 17:10:13 #agreed last chance for any modification: May 5, final discussion and voting: May 12 17:10:20 +1 17:11:02 langdon is working on the wording, so he will finalize after May 5 17:11:03 Can't make this meeting, I have some urgent errands. What text do we need? I think I updated the markdown 17:11:43 It is the latest version at https://hackmd.io/@x3mboy/HyB92cVl_ 17:12:13 That is not the side-by-side version, but a follow-up 17:13:58 OK, obviously nothing else, I'll switch topic next 17:14:18 #topic Fedora release criteria and process 17:14:26 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/GSJM6TE76QKSNPNU7EX63AATOB4ZP5IU/ 17:14:57 see the post by Stephen Gallagher, April 19 in that thread 17:15:09 The issue came up when Cockpit did not work correctly in Fedor34 release candidate. 17:15:23 Was a bit of a mess 17:16:41 Any comment? Any idea? 17:17:17 Did the missing service show up in the menu as "dimmed" or did it not show up at all? 17:18:23 In cockpit the device list was missing, You couldn't create a new LV, could do hothing but create a partition (but no filesystem in a created partition) 17:19:12 Reason was: A package was declared as "recommended" and not included in installation by default. 17:19:46 And recommended packages are not included in the current Server installation due to space restrictions (DVD capacity) 17:20:20 It seems that if documented functionality is not "enabled" or the required sub-package isn't installed, that should somehow be communicated back to the user. 17:21:16 jwhimpel: Yes, it was in the release note- burried. :-) 17:22:05 I wasn't specific enough. It should be communicated back to the user via the user interface. 17:22:15 I suppose nobody read that Cockpit release note, and most ot us including me knew, that recommended packages get not included in hull install image 17:22:44 But are included in network install (That is the issue of next topic) 17:24:48 Any suggestion how to proceed here? 17:25:06 Anyone want to make a guestimate of how many server installs do not have access to the internet? Maybe we just support netinstall? 17:26:05 Yes, I mostly use netinstall. But it is sometimes skimpy to enter the repo address. 17:28:52 Any idea on how much work to put a text based gui into netinstall that allowed the Admin to select an installation and the installer find the appropriate repo? 17:28:56 I think we should open an issue about Stephen suggestion. So we can tack the issue later and ask Stephen about it? 17:29:44 jwhimpel: I don't know, but my impression is that the Anaconda team is quite busy. 17:30:17 But indeed, we should try that and make netinstall the recommended way. 17:31:21 But we are know on the next topic. So i'll create an issue about that and switch for now 17:31:28 Stephen's suggestion seems reasonable. 17:31:45 topic: Issue: Release composition 17:32:02 This also came up because of the same problem. Question is whether we should change the composition of the server release. 17:32:12 Due to the trend towards smaller images for containers and cloud images, it should be attractive for packages to reduce the number of dependencies. Thus, this problem could occur more often in the future and is hardly manageable. 17:32:44 Therefore, making netinstall the preferred method, is another solution here 17:34:10 the DVD media does not preclude making smaller installs possible 17:35:02 I personally would not object to just enough packages to bring up the server with the standard server modifications, configure the internet, and dnf. Everything else could could be added via dnf. 17:35:36 Eighth_Doctor: Of course not. Smaller images are a plus 17:36:00 I basically never use the netinstall ISO and pretty much use the DVD media 17:36:11 it's faster and reproducible 17:36:39 the netinstall exists for people who have more extreme bandwidth requirements 17:36:59 another option that we could add is a way to use the Fedora Cloud images to make a Fedora Server 17:37:17 we've never really had that before, but nothing technically stops that from being a workable solution 17:37:27 Eighth_Doctor: then we should either drop the DVD image size or drop some of the additional optionsß 17:37:35 no 17:37:40 I'm saying we should not touch the DVD media 17:37:55 because it doesn't actually solve the problem you're trying to solve 17:38:22 you have not stated an actual problem you are solving by doing this 17:39:13 we even promote both the regular DVD ISO and the netinstall ISO on the download page 17:39:25 Eighth_Doctor: What#s your solution how we find such issues as the Cockpit installation case? 17:39:46 fix the pungi bug? 17:39:54 like, the issue is known, someone just has to fix it 17:40:21 DVD media should be including weak deps in the repo generation, but they're not 17:40:29 that's a bug that should be fixed 17:40:51 It was no pungi bug. It was the decision not to include recommended packages 17:41:18 then reverse that decision 17:41:25 inclusion of packages != installation of packages 17:41:40 i see no reason that the server dvd has to be container to 2G or less as long as its less than the 4.7G space of a DVD 17:41:43 Eighth_Doctor: @DVD media: than we have to accept, that the DVD images doesn't fit onto a DCD anymore. II'm ok with that. 17:41:43 the whole point of weak deps is to be able to split those two parts of the decision tree 17:42:10 DCD? 17:42:17 sorry DVD 17:42:38 Was the DVD size issue just for Desktop DVD's or is there a size issue for Server DVD's also. 17:43:21 we still have ~2GB of wiggle room 17:43:28 (if we're counting single-layer DVDs) 17:43:35 live have been limited to 2Gish, but i dont think anyone would complain about a 4G server iso 17:43:44 and ~6GB of wiggle room for double-layer DVDs 17:43:54 fwiw, RHEL DVDs are 8GB 17:43:57 Eighth_Doctor, single layer 4.7G 17:44:33 We should ask sgallagh. He saw the need to limit the size of the full install image. 17:44:36 one of the reasons for the limits for the live ISOs was so we can stuff them all into an omnibus DVD image 17:44:51 that practice stopped a very long time ago, and we never included Server in that anyway 17:45:16 Anyone have a pointer to the discussion where the decision was made, so I can better understand their rationale? 17:45:22 Southern_Gentlem: You are right. I dn't know at the moment, why there is a limit of 2 gb. 17:45:46 That limit was based on the availability of cheap thumb drives 17:45:46 well that and at one time usbkeys where expensive where now you can get a 32GB for cheaper than 2G used to be 17:45:54 indeed 17:46:06 We should just include even recommended packages and accept an image size up to 4 gb. 17:46:09 4GB USB sticks are starting to die out in favor of 8GB ones at that price point 17:46:25 Eighth_Doctor, want to try 16-32G 17:46:31 hehe 17:46:41 I'm thinking of Asia where things are bit slower on the uptake 17:46:42 Eighth_Doctor: That another question. Who is using DVDs today? 17:46:44 However, keeping the size down is still advantageous for folks in countries with poor broadband (like much of the USA) 17:46:48 i am buying 64G at walmart for $12 each 17:47:18 sgallagh, but all other server isos have been 4G for years 17:47:28 pboyHB: I suspect a lot of folks like myself who have to deploy in places with less than ideal bandwidth prefer the DVD ISO 17:47:51 or people setting up pxeboot 17:48:09 Eighth_Doctor: 'Yes, but do you really use a DVD nowadays? 17:48:11 I’m open to increasing the maximum, but not to using that as a justification to grow the size too much. 17:48:21 pboyHB: not the physical DVD no, mostly on USB sticks 17:48:30 sgallagh: +1 ! 17:48:42 sgallagh: I'm saying we should just go from 2GB to 4GB for now 17:49:05 and see if we can get what we need to fit in there 17:49:51 Yeah, I'm fine with setting that as the maximum, but ideally I think we still want to *try* to stay smaller. 17:50:00 A small server image is a valid selling point 17:50:09 Do we know how big the image will be when we include recommended packages? 17:50:57 No 17:50:58 not yet 17:51:07 lets find that out 17:51:37 I think it would be good if net install and full install lead to the same result. They do not now. 17:51:46 yup 17:51:51 +1 17:51:59 fixing how the DVD iso repo is populated should fix that 17:52:11 How can we find out the size? 17:52:57 good question 17:53:15 it's been a long time since I've messed with the install media creation process, and I'm pretty sure it's been rewritten a couple of times since then 17:53:37 Perhaps a ticket to "Release Mgmt"? 17:54:41 yeah likely a releng ticket to help figure that out 17:54:53 Eighth_Doctor: Could you organize how to find out? 17:55:01 sure 17:55:38 #agreed: Eighth_Doctor checks the size of a install image including all recommends. 17:55:51 #action: ighth_Doctor checks the size of a install image including all recommends. 17:56:05 #topic Planing for next Fedora release 17:56:18 We have commited to a number of goals in the new PRD. What of these should be tackled? 17:56:46 But we are running out of time now. So we should delay this. 17:56:48 To know that we need to actually finish the PRD 17:56:58 most likely we will have to look at the server dvd ks 17:57:23 x3mboy: wee decided: final discussion and voting May 12 17:57:36 #topic Open Floor 17:57:45 Next chair? 17:58:10 Eighth_Doctor>? Can you do it? 17:59:47 I have done it 3 times in a row now. 18:00:17 pboyHB: I can't, I have too many meeting conflicts around this time 18:00:29 OK. I see, it's me again. 18:00:33 sorry :( 18:00:40 Thanks anyway. 18:00:55 OK, time is up. 18:01:09 Thanks to anybody for coming. 18:01:16 See you again next week. 18:01:30 #endmeeting