17:00:31 #startmeeting fedora-server 17:00:31 Meeting started Wed Dec 1 17:00:31 2021 UTC. 17:00:31 This meeting is logged and archived in a public location. 17:00:31 The chair is pboyHB. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:31 The meeting name has been set to 'fedora-server' 17:00:40 #topic Welcome / roll call 17:00:48 Welcome to our Server WG IRC meeting! 17:00:52 .helo 17:00:59 As usual, we'll give a few minutes for folks to show up 17:00:59 Please, everybody who is lurking, say either .hello2 or .hello 17:01:02 .hello 17:01:02 jwhimpel: (hello ) -- Alias for "hellomynameis $1". 17:01:26 I’ll post the agenda in a few minutes. 17:01:39 .hello copperi 17:01:39 copperi[m]: copperi 'Jan Kuparinen' 17:01:42 .hello chrismurphy 17:01:46 cmurf[m]: chrismurphy 'Chris Murphy' 17:01:49 .hi 17:01:49 dcavalca: dcavalca 'Davide Cavalca' 17:02:39 Hello everyone. 17:03:32 .hello2 17:03:33 jwhimpel: jwhimpel 'John Himpel' 17:03:41 .hello 17:03:41 mowest[m]: (hello ) -- Alias for "hellomynameis $1". 17:04:07 A hearty welcome to everyone. 17:04:14 #topic Agenda 17:04:23 #link https://pagure.io/fedora-server/report/Meeting 17:04:30 1. Follow up actions 17:04:38 2. New WG Doc Landing Page and Navigation Items 17:04:39 * nirik is doing other stuff, but trying to be here a bit too. 17:04:45 3. Migration of unmodified Wiki content 17:04:53 4. Decommissioning of (old) SIG Wiki pages 17:05:02 6. Facilitated and improved support for Fedora Server Edition VMs 17:05:09 7. Using Ansible to install and configure Wildfly 17:05:15 8. Open Floor 17:05:23 Any additional topic ? 17:05:44 .hi 17:05:47 salimma: salimma 'Michel Alexandre Salim' 17:06:02 #topic Follow up actions 17:06:08 * salimma mostly afk 17:06:15 #info action Moving Wiki Pages to docs.fedoraproject.org (#52) (pboy,mowestusa) done 17:06:23 Everything has gone very fast this time. 17:06:34 No sooner had I written to the docs mailing list than we were online. Many thanks to Ben. 17:06:42 #info New address: https://docs.fedoraproject.org/en-US/server-working-group/ 17:07:08 Any comment? Any other open action that i missed? 17:08:04 OK 17:08:07 The skeleton is there for the Server Working Group. Is there a specific page that you would like me to start working on to "flesh" things out. 17:08:07 #topic New WG Doc Landing Page and Navigation Items 17:08:16 #link https://pagure.io/fedora-server/issue/56 17:08:23 Maybe we start with the =content= of the new page. 17:08:31 (and then later with the navigation menu) 17:08:40 The Floor is open 17:10:52 Ok, so just do some comparisons between the old wiki pages and our current page in docs and flesh that out with information? Is there new information that we would like up there? 17:11:52 I would like to add at the end: The last 3 IRC protocols / links. 17:12:32 It would be nice to keep the landing page of the Server Working Group short and sweet with other content on the pages of the navigation menu. I would think anyway, just looking at the current structure. 17:12:41 And I would like to transfer the details of our work projekts to pagure and not add them as sub pages to docs. 17:13:11 mowest +1 17:13:15 That makes sense. There could always be just a link to the pagure issue 17:14:36 Ok, thanks for the direction. 17:14:38 Well, obviously there is no need to change anything in the current version 17:14:50 #proposed the current landing page is accepted with addition of the last 3 IRC meeting links. 17:15:13 3 17:15:21 2 17:15:22 1 17:15:37 #agreed the current landing page is accepted with addition of the last 3 IRC meeting links. 17:16:00 What about the navigation items? 17:16:56 do you envision server admins locating server documentation via this landing page? 17:17:40 I think it gives us a good structure to work with right now, and see how those pages develop over time if we need to create different categories or sub pages. 17:18:12 jwhimpel: No, therefore the note on the top about user documentation. But Google may find them. 17:18:35 I believe this is page is meant more for introducing people to the Fedora Server Working Group in the hopes that they join the fun. 17:19:06 #proposed: We start with the navigation items as is 17:20:19 .hello 17:20:19 eseyman: (hello ) -- Alias for "hellomynameis $1". 17:20:25 .hello2 17:20:25 3 17:20:25 eseyman: eseyman 'Emmanuel Seyman' 17:20:32 2 17:20:38 1 17:20:54 #agreed We start with the navigation items as is 17:21:16 Question is, do we need staging pages? Or do we rely on mowest and me and then correct / add to it later. 17:22:50 I feel staging pages are more necessary for Server Documentation than these pages that will remain mostly static after add the information that is missing. 17:23:16 Yes, I guess no one has need for stating pages. 17:23:28 +1 on that 17:23:35 #agreed no staging pages needed 17:24:11 #action mowest and pboyHB continue to migrate the wiki pages. 17:24:26 #topic Migration of unmodified Wiki content 17:24:36 #link https://pagure.io/fedora-server/issue/57 17:25:20 The issue lists those pages we should migrate unmodified. 17:25:37 Concerns? 17:26:28 none here 17:26:32 #agreed as of issue #57 pages will be migrated unmodified 17:26:46 #topic Decommissioning of (old) SIG Wiki pages 17:26:54 #link https://pagure.io/fedora-server/issue/59 17:27:33 There's a way to set a redirect to docs.fp.o on each wiki page 17:27:49 (I think mattdm brought it up in devel@ recently) 17:28:11 Does the SIG page predate this wiki page? https://fedoraproject.org/wiki/Server 17:28:24 Would be good, We should remove outdated content or provide it with warning and link to current content 17:28:40 cool, there should be simple note left on page as well that page has moved in case it does not work. 17:29:02 mowest: At that time there were 2 groups in parallel. 17:29:16 I'm in favor of just removing outdated content and streamline sources of information that search crawlers find. 17:29:48 Are we entiteled to remove that page or do we need to ask council / fesco ? 17:30:03 There might be hard-coded links, so I prefer note and redirect 17:30:50 Could we evaluate the hard-coded links and see if any are still relevant and add those to our docs landing page? 17:30:50 Yeah, one issue I notice with wiki pages that have moved is that references from outside pages are not updated in timd 17:30:51 with other content removed 17:31:05 So having a page that warns and redirect is better than just prematurely yanking 17:31:28 #proposed Old SIG page get a note and redirect to new page 17:31:33 3 17:31:33 Oh, I see links from outside are the issue. 17:31:39 2 17:32:00 1 17:32:17 salimma: {{#fedoradocs: https://docs.fedoraproject.org/en-US/council/fpl/}} 17:32:36 #agreed Old SIG page get a note and redirect to new page, old content removed / archived 17:32:40 +1 to the proposal and to matt 17:32:49 at the top of the page. note that once it's there, it's annoying to edit the page, so get it right hte first time :) 17:32:51 +1 17:33:49 pboyHB: you can redirect any pages that belong to the team (or are related and effecively unclaimed) to docs without asking anyone 17:34:20 If you wanted to redirect to somewhere else, or if it's a shared page or something, then some coordination needed. 17:34:22 mattdm: OK (I'm just being cautious) 17:34:28 yep :) 17:34:54 also: the advantage of using the macro over putting a notice at the top of the page is that Google will understand it and update links 17:35:39 #action mowest and pboyHB modify the old SIG page as agreed 17:36:00 #topic Review current Fedora Server Technical Specification 17:36:10 #link https://pagure.io/fedora-server/issue/58 17:36:42 Our technical specifications are "a bit" outdated. 17:36:47 The floor is open 17:38:08 somewhat outdated, yes 17:39:00 My idea: we proceed as with the PRD. Everyone comments on hackmd and we then merge that into an updated version. 17:39:01 Since these are outdated, what new thing has guided the decision made about the last two releases of Fedora Server 34 and 35? 17:39:52 good question. :-). business as usual and an implicit agreement 17:40:32 and our discussion of the PRD gave a lot of guidance. 17:40:50 So, just wondering, do we need a technical specification if it hasn't been used? I don't want us to go through a lot of work if we it will just get dusty like the last one. 17:42:10 We have to discuss and enhance our release criteria next. We need a explicit specification to determine release criteria 17:42:55 I like the idea of a tech spec. I just think we should review every 2/3/4 releases to keep it fresh 17:43:28 Great, sounds like it would go to good use, and we already have a nice format to start with on hackmd. 17:43:58 eseyman: +1 17:44:43 #proposed Everyone will work through the technical specification and comments on hackmd over the next 14 days and then we will discuss details at the next meeting. 17:44:45 .action eseyman hit hackmd this week and comment on tech spec 17:45:01 #action eseyman hit hackmd this week and comment on tech spec 17:45:43 #proposed eseyman hit hackmd this week and comment on tech spec, discussion next meeting Dec 15 17:46:16 3 17:46:22 2 17:46:26 1 17:46:38 #agreed eseyman hit hackmd this week and comment on tech spec, discussion next meeting Dec 15 17:47:06 #action eseyman hit hackmd this week and comment on tech spec 17:47:27 #topic Facilitated and improved support for Fedora Server Edition VMs 17:47:35 #link https://pagure.io/fedora-server/issue/53 17:47:45 #info On Mailing List: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/3Z7YAUSYPTZ5HME4OW7WK67L67AM7KHE/ 17:47:56 #info In particular: experience of the Fedora infra Team: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/Y7QX3FKUWCPAYWMJYLLHTUHUK3L627MI/ 17:48:28 One general idea „install thats just enough to boot, have NetworkManager/be on the network and have dnf working so we can install whatever we want. The smaller the better here.“ (nirik) 17:48:36 Another idea: have an image as close as possible to the default Anaconda install 17:48:43 (both are practically not so different) 17:48:52 Floor is open 17:48:54 well, we control what anaconda installs. ;) 17:49:16 Kickstart FTW 17:49:50 actually, Kevin's description pretty much matches what I want on my new home server 17:50:22 FWIW I think this is what the cloud image was orig going for (but with cloud-init added I suppose). 17:51:25 Yes, but cloud image drifted into a somehow different direction, unfortunately. 17:52:29 My wish: the admin experience of a VM image should be as similar as possible to an Anaconda default installation. 17:53:49 About kickstart: Then we should provide a (default / template) kick start file. 17:54:32 pboyHB: Do you mean an interactive anaconda install or an unattended anaconda install? 17:54:54 :) 17:55:11 I mean an interactive one 17:55:20 I suspect we'll need several ks files 17:55:38 eseyman: +1 17:56:10 time is draining 17:56:50 I would like to switch soon to Open floor, just in case someone comes up 17:56:55 That doesn't work for bringing up new VM's quickly to handle surges in volume. Or for using ansible and other configuration management tools to do the installation. 17:57:54 jwhimpel: could you elaborate? 17:58:22 jwhimpel: YES, indeed. The result of an interactive discussion should be available as an image or kickstart template, or something else 17:58:56 OK, let's continue discussion next meeting ! 17:58:59 We often have a pig going through a snake (large surges of transactions) where we need to spin up a significant number of vm's to handle the surge. 17:59:19 #topic Open Floor 17:59:22 jwhimpel: sure but in that case you'd start with a full VM image, and skip anaconda, no? 17:59:28 i think you could have one or more "VM centric" kickstarts hosted in Fedora somewhere, and provide install media with boot options for each kickstart 17:59:59 cmurf: +1 18:00:01 where Fedora Server VM's are customized via kickstart, and Cloud is customized via cloud-init 18:00:28 sure, but if you are going to do that, why not just make your own kickstart? 18:01:04 we want to make it easy for the not so skilled admin as well 18:01:51 OK, time is up. Let's continue in 14 days! 18:01:57 Thanks to anybody 18:02:06 bye, all 18:02:08 Thanks pboy 18:02:15 #endmeeting