17:00:29 #startmeeting fedora-server 17:00:29 Meeting started Wed Apr 5 17:00:29 2023 UTC. 17:00:29 This meeting is logged and archived in a public location. 17:00:29 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:29 The meeting name has been set to 'fedora-server' 17:00:39 #topic Welcome / roll call 17:00:44 let's go, let's go, let's go! 17:00:50 Welcome to our Server WG IRC meeting today! 17:00:51 .hello2 eseyman 17:00:52 eseyman: eseyman 'Emmanuel Seyman' 17:01:08 Welcome eseyman! 17:01:39 and on time, too! 17:01:43 .hello2 cooltshirtguy 17:01:44 cooltshirtguy: cooltshirtguy 'Jason Beard' 17:01:51 congratiulation. :-) 17:02:25 Mowest is prevented from participating today, maybe he'll make it later towards the end. 17:02:38 Let's start anyway with the agenda 17:02:47 #topic Agenda 17:02:54 #info Follow up actions 17:03:01 #info F38 Beta testing. 17:03:10 #info F38 Beta testing. 17:03:18 #undo 17:03:18 Removing item from minutes: INFO by pboy at 17:03:10 : F38 Beta testing. 17:03:38 #info F38 - Shorter Shutdown Timer 17:03:51 #info Fedora Website revamp – Fedora Server Edition pages 17:03:59 #info Using Ansible to install and configure Wildfly 17:04:06 #info Open Floor 17:04:18 Anything to add ? 17:04:33 I'm good 17:04:38 OK 17:04:40 #topic 1. Follow up actions 17:04:48 #info ACTION: pboy to open a thread about meeting time change on mailing list – outdated by decision 17:04:57 #info ACTION: pboy will write a info about changing the timeout value and nirik will review – still work in progress 17:05:06 Any open action I forgot? 17:05:29 .hello copperi 17:05:30 copperi[m]: copperi 'Jan Kuparinen' 17:05:33 dont think so 17:05:37 OK 17:05:40 #info No further open actions 17:05:52 #topic 2. F38 Beta testing 17:06:02 #link https://pagure.io/fedora-server/issue/99 17:06:16 Lets spend about 15 min at max with this, most ist done now. 17:06:25 I tested the various installation methods and virualization with branched 2023-03-31 and everything works. 17:06:34 Expecially ServerVM which had an issue with the Beta version. 17:06:45 Maybe, we have a new issue with IPA. See irc discussion Apr 4, 2023 15:42 (UTC) sgallagh / tflink 17:06:55 sgallagh any news about it? 17:07:11 postgresql works perfectly with the beta 17:07:32 cooltshirtguy Best, thanks. 17:07:34 installed last weekend, will play with postgresql, mariadb, apache and nginx this weekend 17:08:25 eseyman good idea, we have freeze now, but in case of issues may still be able to do something. 17:08:40 So it's worthwhile 17:09:15 Hm, sgallagh seems to be busy. 17:09:36 I'm here 17:09:47 Oh, good! 17:10:05 I was unable to reproduce the issue and Tim also couldn't reproduce it after we walked through it together. 17:10:17 So we're assuming it was operator error at some point in his initial testing 17:10:37 OK, that's the best outcome. :-) 17:11:22 So, so guess we are fine with F38 and should not experience any surprises. 17:11:49 any further comment? 17:12:27 OK, next topic 17:12:39 #topic 3. F38 - Shorter Shutdown Timer 17:12:47 #link issue #96: https://pagure.io/fedora-server/issue/96 17:13:03 #link Mailing list discussion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/N6TW6EBPG5Q6D6SEV4FFGQH3E6HUTVE2/ 17:13:15 Current status: Kevin created a PR 17:13:24 #link https://src.fedoraproject.org/rpms/fedora-release/pull-request/256 17:13:35 It is basically the same as proposed by CoreOS / siosm (#249) that we missed to join due to a misreading (by me). 17:13:46 We checked and provided karma before freeze time, but the merge couldn't be made in time. 17:13:55 #link https://bodhi.fedoraproject.org/updates/FEDORA-2023-814ffcaf1b 17:14:04 There is still a way to get it on the installation media as Kevin said. 17:14:20 Question is, how do we have to proceed? 17:14:50 nirik Do you take care of it? 17:15:59 Well nirik is very busy these days with all the infra and release work. 17:16:06 Yeah, it went in right before freeze I think 17:16:27 yep. it should be in f38 now... testing welcome of course. 17:17:46 so it should be all set. 17:17:51 Oh yes, I see "This update has been pushed to stable." This means, we are done? 17:18:40 nirik many thanks for you action fo fix my initial mistake ! 17:19:26 A successful last minute action. :-) 17:19:47 Anythink else here? 17:20:32 OK, next topic. We are quick today! 17:20:53 #topic 4. Fedora Website revamp – Fedora Server Edition pages 17:21:03 #link Issue #66: https://pagure.io/fedora-server/issue/66 17:21:11 Current draft: 17:21:20 #link https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/server/ 17:21:30 Developer discussion 17:21:41 #link https://discussion.fedoraproject.org/t/fedora-server-front-page-revamp-looking-for-feedback/79037/9 17:21:51 Text snippets 17:22:00 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/RUBKGEFG3OWHQXOZNBNDAE7VJJQ2YDA7/ 17:22:07 Graphics 17:22:16 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/42HPTYDERGRWVHJFKBMGO545C5WXYNDZ/ 17:22:24 Current status: 17:22:45 The text descriptions are probably not yet optimal, various of our proposals are not included. But this is a minor issue, IMHO 17:22:54 My biggest issue: A documentation button is still not in a prominent and highly visible position 17:23:02 neither on our our hero graphic nor in the top bar. 17:23:10 A professionally usable server needs documentation as important as download. 17:23:25 +1 on that 17:23:33 (That's all from me, so far. sorry for all the text) 17:24:40 that said, there's a lot to like in that page 17:24:45 agreed 17:25:17 Yes, it is a great improvement 17:27:00 Well, what do you think about my wish for a "documentation" button in the hero between Download and Community? 17:27:36 Should we continue to ask for it? 17:28:17 that would be great 17:28:36 I think so 17:28:49 OK, so we 17:29:27 #agreed Server WG would like to get a "Documentation" button/link between Download and Community in the herfe graphic 17:30:18 I'll discuss this with mowest later, how we can proceed. Probably open an issue about it. 17:30:53 (Mowest said, he may be back from his errant at the end of our meeting) 17:31:26 What about the descriptions? 17:32:46 I like them 17:33:37 their fine 17:34:05 OK, so I suppose we agree to accept them as is, leaving maybe possible improvement to next version. 17:34:48 #agreed Server WG is content with the feature list and descriptions. 17:35:26 Anything else here? 17:35:46 nope 17:35:52 don't think so 17:36:03 OK, next topic 17:36:12 #topic 5. Using Ansible to install and configure Wildfly 17:36:21 #link https://pagure.io/fedora-server/issue/60 17:36:36 atest status: 17:36:53 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/AVVCF266QN43SRQ4LDCYITZC5ZVJFALD/ 17:37:04 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/SYVECUPODIYQRS5IVQIMXRV7HFDRSYWB/ 17:37:46 Latest Action: We have a public test server (sisyphos.resdigita.eu) with a running Wildfly and basically a Ansible script. 17:38:27 jwhimpel Are you watching? 17:39:15 The server is a VM on one of my server with the only purpose to serve as our test bed. 17:39:44 I can provide anybody who wants to have a look with an (adminstrative) account. 17:41:30 Well unfortunately, jwhimpel couldn't make it today, obviously. 17:42:35 Any idea / any plan how to proceed? (besides postponing to next meeting when John hopefully can attend) 17:45:06 We should probably start thinking about how we're going to get these ansible roles/playbooks into our users' hands 17:45:23 eseyman +1 17:45:46 I really don't know what options we have. 17:46:26 Should we create a kind of server admin package as a workstation rpm? 17:46:52 put them on ansible galaxy ? create an rpm ? both 17:47:11 Or distribute it as part of server media do download the local part? 17:48:13 anyway, there's nothing urgent but we should think it through 17:48:19 I'm not sure if ansible galaxy alone is "too far away" for every day server admin. 17:48:41 Yes, we should make it a separate topic on one of our next meetings. 17:48:41 package to install for fedora server 17:49:40 cooltshirtguy As fas as I know there are two parts, you need some support code on the server and some code on your workstation. 17:49:52 But maybe I#m wrong with that 17:50:36 there's the control node (on which you run ansible) and the managed nodes (ansible connects to them via ssh and run python code on them) 17:51:06 the control node can be a server or a workstation 17:51:26 OK, so I was not "so much" wrong. :-) 17:52:02 What about a Mac as control node, do you know? 17:53:30 not sure 17:53:46 OK, we'll learn 17:54:05 you'd have to install community ansible at least. then install the package with the roles 17:54:05 ansible has criteria on what makes a good control node; I know RHEL is a first-class citizen here 17:54:16 not sure for anything else 17:54:16 I think, wie should make a break here and continue on mailing list and next meeting? 17:54:30 sure 17:54:43 I will give the issue some thought 17:54:55 but, yes, we can stop there 17:55:01 eseyman 1+ 17:55:26 OK, next topic 17:55:35 #topic 5. Open Floor 17:56:25 I found some information that Fedora is planing an Event in Spain, beginning of August 17:56:37 Does anyone know more details? 17:56:45 Or is it misinformationß 17:56:52 it's news to me 17:57:10 beginning of August sounds like the Gnome conference to me 17:57:23 i have no idea 17:58:23 There was some discussion in the Council matrix room. 17:58:30 Guadec is in Riga this year 18:00:44 OK, let's look around, wheather there some planing. 18:00:50 Anything else here? 18:01:10 not to my knowledge 18:01:51 Well, I just found: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-426-flock-2023-finalize-dates-and-venue-for-our-next-in-person-contributor-conference/44620 18:03:45 It would be Ireland, not Spain. More rain, less sun. :-) 18:04:43 August 1-4 2023 in Cork, Ireland 18:05:15 Yeah, if it really will happen, we should participate with Server! 18:05:44 But time is up. Let's continue in 2 weeks.! 18:05:59 #endmeeting