17:00:33 #startmeeting fedora-server 17:00:33 Meeting started Wed Sep 6 17:00:33 2023 UTC. 17:00:33 This meeting is logged and archived in a public location. 17:00:33 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:33 The meeting name has been set to 'fedora-server' 17:00:46 #topic Welcome / roll call 17:00:57 Welcome to our Server WG IRC meeting today! 17:01:10 „Same procedure as every year“ We'll give a few minutes for folks to show up 17:01:36 hello, everybody ! 17:01:42 .hello2 eseyman 17:01:43 eseyman: eseyman 'Emmanuel Seyman' 17:01:58 .hello2 abbra 17:01:59 ab: Sorry, but user 'ab' does not exist 17:02:15 .hello 17:02:15 ab: (hello ) -- Alias for "hellomynameis $1". 17:02:22 weird 17:02:24 .hello2 jdubby 17:02:25 jdubby: Sorry, but user 'jdubby' does not exist 17:02:27 anyway, hello 17:02:37 .hello 17:02:37 jdubby: (hello ) -- Alias for "hellomynameis $1". 17:02:58 .hello jdubby 17:02:58 jdubby: Sorry, but user 'jdubby' does not exist 17:04:03 Zodbot seems to be recalcitrant today. 17:04:09 :-) 17:04:52 Hello everybody and a big welcome. 17:05:50 I had already feared, after the non-regular 3 week break, many would have overlooked this date. 17:05:59 OK, thew Agenda 17:06:10 #topic Agenda 17:06:23 #info Follow up actions 17:06:35 #info F39 Work Project: Fedora Server on (ARM) SBC 17:06:35 #info Work Project: Using Ansible to install and configure Wildfly 17:06:35 #info Fedora release 39 test planning 17:06:35 #info F39/40 Work Project: Fedora Server in a virtualized runtime environment 17:06:35 #info Open floor 17:06:47 Any topic to add? 17:07:16 obviously none 17:07:25 #topic 1. Follow up actions 17:07:33 #action pboy will write a info about changing the timeout value and nirik will review – still work in progress 17:07:42 That's finally a running gag. But, good things come to those who wait. 17:08:05 Anything to ask or to announce here? 17:08:38 OK, next topic 17:08:47 #topic 2. F39 Work Project: Fedora Server on (ARM) SBC 17:08:58 #link https://pagure.io/fedora-server/issue/108 17:09:19 I had send a summary previously: 17:09:29 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/B275Q5GOX5FIBDQ464CGSGJXWWEY7NXQ/ 17:10:07 I suspect it's time we went to the ARM SIG and asked 'What do you feel comfortable supporting the install on?' 17:10:27 Lots of SBC's with more power than Rpi hitting the market now. Unfortunately almost none are completely FOSS. 17:11:48 jdubby yeah, but a lot of capable alternatives already exist. e.g. by pine64 17:13:14 We have a list at 17:13:17 When I get done remodeling a rental property that I own, I will look at purchasing a pine64 or something like that. The VIM4 looks promising, but not yet supported. 17:13:18 #link https://docs.stg.fedoraproject.org/en-US/fedora-server/server-on-sbc/reference-list/ 17:14:42 eseyman Do you have access to the vim1 you spoke about some weeks ago? 17:15:01 yes, it's still on my 'tech' shelf 17:15:32 So you could perform some tests? And provide an installation report / remark? 17:15:42 oh yes 17:16:02 I Can try to do this by next meeting 17:16:05 Very good! 17:16:49 Propably you can fill in the first line of the table in our stg docs? I have put in all questions marks for now. 17:17:31 yes 17:17:57 jdubby ypu may consider Libre Computer mdel Roc RK 3399 PC, either original or by firefly 17:18:10 It has some advantages over the pine64 17:18:45 Pine64 is most interesting with the big case to include to hard disks and to build a home server. 17:18:46 pboy: Thanks 17:19:02 to hard -> two hard... 17:19:44 It is an ideal candidate for a follow up project "a power efficient home server appliance". 17:20:02 pboy: What is the difference between +1 and +2 in your ARM SBC Devices Rererence List? 17:20:55 +2 is "best rated". +1 "Good with some inconveniences" 17:21:05 pboy: Thx 17:22:51 The idea is, to comment on the inconveniences in an additional, short profile below the table. See the comments about the Rock Pi 4 17:23:23 Well, what to do next? 17:23:38 In my email I specified 3 tasks: 17:23:49 If we can find more that are supported, then this looks like a great format. 17:23:52 1. checking the power consumpption argument 17:23:52 2. Checking the performance argument: 17:24:05 . checking price argument 17:24:05 i.e. make a small market analysis on recommended manufacturer pricing (or large reseller). 17:24:49 Can we split this between us? 17:25:09 E.G. 2. performance 17:25:12 I really think we need the ARM SIG's input on this 17:25:36 eseyman: Yes, probably. 17:26:14 I really can't see us supporting anything they're not OK with 17:26:20 eseyman: when I finish my intro text, could you organize to contact ARM Sig? 17:26:30 yes, I can do that 17:26:40 eseyman: Out table only consists of device they fully support. 17:27:03 Fully support was an initial criteria 17:27:35 Well, so we agree with 17:27:49 a) pboy completes the intro text 17:28:06 b) eseyman will take over an contact ARM Sig 17:28:15 Any onjection? 17:29:04 #action pboy will complete the intro text about Fedora Server and ARM SBC 17:29:24 #action eseyman will then take over and contact ARM SIG 17:29:49 Anything else at the moment? 17:30:16 no, that looks good 17:30:20 OK, next topic 17:30:41 #topic 3. Work Project: Using Ansible to install and configure Wildfly 17:30:50 #link https://pagure.io/fedora-server/issue/60 17:31:01 I'm a little uncertain about the state of things. If I remember correctly, it's now about an nginx proxy and the Ansible playbook. 17:31:19 Isn't it? 17:31:44 yes 17:32:04 ab arn't you involved in the Java app server as tomcat, tomee, etc? 17:32:07 this used to be a hard requirement, I'm not so sure it is these days 17:32:47 pboy: as a user of Dogtag but I don't do configuration of tomcat there 17:33:15 dogtag configures tomcat for us 17:34:24 Could it help with wildfly, too? (Unfortunately, I don't know dogtag) 17:34:40 Sorry, I had to step away for a moment. 17:34:53 unlikely, unless you'd extract that logic from dogtag's installer code 17:35:06 If you want to access Wildfly vi port 80, then you need a proxy in front of it. 17:35:30 yep, in FreeIPA we proxy from apache to dogtag on higher ports 17:36:38 From an architectural standpoint, do you want the proxy (NGINX) to run on the same host as Wildfly or on a separate host? 17:37:19 Also, can deployments of JEE applications occur from hosts other than local to Wildfly? 17:37:25 in a SOHO or homelab setting, it probably makes sense to run both on the same host 17:38:19 The clients such as JBOSS plugin for maven, JBOSS-CLI, etc ass assume they can address Wildfly via localhost. 17:38:20 jdubby ad the former: We should support both 17:39:06 Ad the latter: With tomcat you need local access. Im not sure with wildfly 17:39:27 I think Wilsdfly's admin supports remote access. 17:39:38 I need to do some more research on how to co configure JBOSS plugin to use something other than localhost. 17:39:43 But I'm not sure at the moment. I always use local. 17:40:39 Can we determine what to do next? 17:40:54 Wildfly does support remote admin, but I'm not sure what config files need changing to support maven driven app deployments. I suspect the issue will be the same with Gradle. 17:41:32 I will try to deploy some of the quickstarts via localhost and report at our next meeting. 17:41:47 jdubby OK 17:42:24 #action jdubby will deploy some of the wildfly quickstarts via localhost and report at our next meeting. 17:42:52 Just a question: Is the nginx proxy currently working? 17:44:25 yes 17:44:41 OK, thanks. 17:44:53 Anything else here? 17:45:32 Obviously not, next topic. 17:45:48 #topic 4. Fedora release 39 test planning 17:46:00 Change Set: https://fedoraproject.org/wiki/Releases/39/ChangeSet 17:46:12 Overview: https://docs.fedoraproject.org/en-US/releases/f39/ 17:46:21 No issue created yet. 17:46:32 In the short term, I think we need someone to investigate whether any of the changes might affect servers in a way that we need to specifically address. 17:46:44 We plan a test day for passkey integration in SSSD and FreeIPA in two weeks 17:46:44 In the long term, we need someone to look at whether and how we want to systematize beta testing, e.g. with a test week and the corresponding work structures (e.g. https://testdays.fedoraproject.org/events/131 or https://testdays.fedoraproject.org/events/132 17:46:57 #link https://pagure.io/fedora-qa/issue/747 17:47:36 test cases are being prepared and all the material for that as well 17:49:02 I seem to recall a discuss on one of the Fedora Mailing Lists about booting and xfs partitions early in the boot/grub phases. Would that affect us? 17:49:04 Oh, interesting!" I hadn't thought of that before! 17:49:29 I mean issue 747 17:50:42 ab I guess (hope) you take care ot this? 17:50:56 And can we do something? 17:51:19 this is mostly informational, you are very welcome to participate. At the moment we don't need any help 17:51:45 OK, that's good! 17:52:11 we have all stuff working but I know people tend to find interesting ways of break things ;) 17:52:31 Unfortunately, I have a lot Fedora related on my todo list. But I'm interested and will try. 17:54:21 ab According to your knowledge, is that the only item that can affect us? Is there anything else we should be concerned about? 17:55:46 NetworkManager's profile migration might be disruptive 17:56:21 That's another one I didn't notice yet. 17:56:22 since it affects upgrades (servers are tend to be upgraded from previous Fedora releases) and also ifcfg format is something often used by servers 17:57:39 there is also fwupda-refresh.timer by default for server edition 17:57:39 Is there a 2nd step now? A first step away from sysconfig/network-scripts was with F37 or so. Wasn't it? 17:58:47 OK, I see, we should urgently open a mail thread about this! 17:59:05 Our time is nearly up, therefore 17:59:26 #action pboy will open a mailing list thread about F39 change set. 17:59:35 I think an action item would be to review changes and come up with a list of those that affect server edition 17:59:44 exactly 18:00:23 #undo 18:00:23 Removing item from minutes: ACTION by pboy at 17:59:26 : pboy will open a mailing list thread about F39 change set. 18:01:01 #action pboy will open a mailing list thread about F39 change set to review changes and come up with a list of those that affect server edition 18:01:20 ab thanks! 18:01:44 pboy: did you solve your NFS issues? 18:02:17 eseyman. unfortunately not, it is still on my todo list. 18:02:32 But I could resolve the Perl issue. :-) 18:02:33 ok 18:02:56 I skip to Open Floor 18:03:17 #topic 5. Open Floor 18:03:36 the floor is open. anything to discuss here? 18:04:26 ah, fixing the Perl issue is a good thing. :-) 18:04:38 I'm all topic-ed out 18:05:46 OK I think I can close with 5 mins overdraft 18:06:25 Thanks everyone for coming! 18:06:35 #endmeeting