18:00:21 #startmeeting fedora-server 18:00:22 Meeting started Wed Mar 1 18:00:21 2023 UTC. 18:00:22 This meeting is logged and archived in a public location. 18:00:22 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:22 The meeting name has been set to 'fedora-server' 18:00:30 #topic Welcome / roll call 18:00:38 .hello2 18:00:38 Welcome to our Server WG IRC meeting today! 18:00:38 mowest: mowest 'Steve Daley' 18:00:50 .hello2 18:00:50 lease, everybody who is lurking, say either .hello2 or .hello 18:00:50 jdubby: Sorry, but user 'jdubby' does not exist 18:00:59 I’ll post the agenda in 2 minutes. 18:01:07 hello, folks! 18:01:08 .hello jwhimpel 18:01:09 jdubby: jwhimpel 'John Himpel' 18:01:16 .hello2 18:01:19 eseyman: eseyman 'Emmanuel Seyman' 18:02:09 Welcome everybody 18:02:21 We already meet our quorum 18:02:25 * nirik is lurking, but busy with other stuff too. 18:02:27 Therefore: 18:02:35 #topic Agenda 18:02:43 #info Follow up actions 18:02:51 #info Fedora Website revamp – Fedora Server Edition pages 18:02:58 #info Using Ansible to install and configure Wildfly 18:03:05 #info F38: Shorter Shutdown Timer 18:03:34 #info Open floor 18:03:49 .hello2 18:03:50 SORRY, wrong order! Bad copy & paste! 18:03:52 cooltshirtguy: cooltshirtguy 'Jason Beard' 18:04:13 Shorter shutdown timer first, Website last !! 18:04:29 Anything to add? 18:04:47 OK 18:04:50 no, that works for me 18:05:04 #topic 1. Follow up actions 18:05:13 Both open actions, nirik and me, are part of the agenda items. 18:05:20 So we sskip theme here. 18:05:26 Anything else to announce here? 18:06:01 #topic 2. F38 - Shorter Shutdown Timer 18:06:09 #link issue #96: https://pagure.io/fedora-server/issue/96 18:06:17 #link Mailing list discussion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/N6TW6EBPG5Q6D6SEV4FFGQH3E6HUTVE2/ 18:06:39 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/O35T2YYLSXC6YAV5LRYBPZENW3AX4GEP/ 18:06:47 see specifically Colin Wolters (CoreOS) post on the former 18:07:00 Lets spend about 20 min at max. here so we will have time for the following agenda items 18:07:06 the floor is open 18:07:32 Hi guys 18:07:43 I'm back 18:07:51 +1 and Welcome 18:07:53 If I can help with something, please let me know 18:08:15 We'll find something, for sure 18:08:19 :-) 18:08:27 I will be doing my server installation 18:08:49 I think nirik researched most of our core services and they seem configured for no limit on shutdown time. 18:08:50 One question was, what are our core services. 18:09:09 I picked up those whoich are listed in our technical specification 18:09:22 And regarding alternative progs: 18:09:25 But it might be nice to document on our web page (or somewhere) how to make changes to the .service file if someone has an issue. 18:09:25 I started with an i3 installation that become into server, now I want to reinstall as server, let's see how is the process, to give better input to the team 18:09:28 yeah, I tried to look at the ones listed... but yeah, there's some question about what should be 'core' here. 18:10:17 Basically, our core services are listed in the technical specification. 18:10:40 We kind of "guarantee" that these will work. 18:10:58 Ans they are protential release blockers. 18:11:11 So we should not have too much of those 18:11:46 jdubby Yes 18:11:51 yeah, the more there are, the more testing needed... 18:12:10 and if there's choices, the more we have to explain what one people might want to use. 18:12:23 agreed 18:12:32 I'll sum up all the findings in the ticket, so will get an overview 18:13:12 And as Adam said, we will have to specify, if the service is able to get roughly interrupted, e.g. for Cockpit it is OK 18:13:30 +1 18:15:42 OK, I'll prepare the summary and we can discuss that next meeting. Any objection? 18:16:13 works for me 18:16:20 #action pboy will create a summary of our discussion about service specific timeouts. 18:16:33 Another question is, what about interdependencies between services. That is the argument of Collin Walters (CoreOS) 18:16:42 CoreOS decided to use the overwrite option and to keep the pld default. 18:17:14 Maybe, we discuss that on mailing list and make a final decision next meeting? 18:18:55 +1 18:19:09 OK 18:19:44 #action pboy will open a mailing list discussion about interdependencies between services and the consequences. 18:20:10 I think we are done with this topic? 18:20:28 yes (just in time, too) 18:20:38 Yeah 18:20:49 #topic 3. Using Ansible to install and configure Wildfly 18:20:59 That's our Ansible pilot project!! 18:21:07 #link https://pagure.io/fedora-server/issue/60 18:21:13 We had some discussion here: 18:21:22 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/2022/12/ 18:21:29 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/HEHEXBYFVD6E6SG33SOGJBREAEBJHGLE/ 18:21:38 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/HEHEXBYFVD6E6SG33SOGJBREAEBJHGLE/?sort=thread 18:21:49 My current issue is various blogs/how-to want you to add xml snippets to standalone.xml. But they don't tell you where in the file to add the snippet. 18:22:53 I've to admit, I'm a bit lost after all these unfortunate postponed discussion. 18:22:59 The snippets they want you to add don't seem to be found in any of the schema parts distributed with wildfly. 18:23:48 I tried to "ansibleize" the blog found at https://developer.jboss.org/people/fjuma/blog/2018/08/31/obtaining-certificates-from-lets-encrypt-using-the-wildfly-cli#jive_content_id_Obtaining_a_certificate_from_Lets_Encrypt 18:24:15 Seems we have to find a Wildfly expert, or an aAnsible expert? 18:24:27 But I am having issues with getting wildfly to use tls between the browser and wildfly. 18:24:46 this looks like a wildfly issue more than it is an ansible one 18:24:58 It clearly is a wildfly issue. 18:26:32 So we have 2 unresolved issues: 18:26:56 a) TLS between apache and Wildfly web app 18:27:17 b) Tiansiblefy Wildfly 18:27:20 right? 18:28:16 Correct. I have a great deal of the ansiblification done. Without tls, I can get wildfly to execute. 18:28:34 very good! 18:28:48 jdubby Do we have a publicly accessible installation anythere ? 18:28:52 jdubby: this is yours, right? https://gitlab.com/jwhimpel/wildfly-ansible 18:29:28 Yes, I still need to update the "inventory" files in the repo. I'll get that done today or tomorrow. 18:29:29 s/anythere/anywhere 18:30:07 I think if we could identify a wildfly configuration expert, this issue could be quickly solved. 18:30:08 jdubby, please ping the mailing list once the repo is current. I'll clone then and take a look 18:30:44 Will do. 18:30:50 thank you 18:31:47 jdubby I tried to install it on one of my (public) servers. Do already you have a public server anywhere? 18:32:03 with Wildfly installed 18:32:50 No. It's only installed in my home behind a nat firewall. 18:33:44 OK. Would it be helpfull to have a public server where anybody of us can login (with admin privs) so we can share alle the details? I can provide one. 18:34:22 Let me know how to access and I will work on getting an instance up and running. 18:34:52 jdubby OK, I'll do it tomorrow (Thursday) and provide you with the login data. 18:35:15 I have been using nginx but I think it should not be too hard to convert to httpd. 18:35:45 We can configure that server freely. It's just for our Wildfly project. 18:36:34 As an Resume: 18:36:58 a) eseyman will look at the updated repo 18:37:32 b) pboy will provide a public server where we can work in a cooperative work on all the details 18:37:56 That's so far. 18:38:02 Anything else? 18:38:10 c) jdubby will update his repo 18:38:23 +1 18:38:45 #action jdubby will update his repo 18:38:55 #action eseyman will look at the updated repo 18:39:07 #action pboy will provide a public server where we can work in a cooperative work on all the details 18:39:57 Are we done with this topic so far? 18:40:38 OK 18:40:41 I'm done for now 18:40:45 same here 18:40:49 #topic 4. Fedora Website revamp – Fedora Server Edition pages 18:41:03 #link Issue #66: https://pagure.io/fedora-server/issue/66 18:41:16 #link Mailing List: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/7QJHY6E422W6SGLMETH5VFOUY6IKJA3P/ 18:41:46 It look as if we have a status that can go online? 18:41:53 I summarized the current status and issues in the email I sent to the server list this morning. The only thing that I will add is that Emma is hoping to have the last of the graphic assets done by tomorrow, and then the team wants to take a break from our landing page and move onto other website revamp issues. 18:41:56 mowest the floor is yours 18:42:39 Is there time to discuss that in 14 days? 18:42:57 Or is there a deadline? 18:43:37 mowest: so this is near-final? https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/server 18:43:55 I think the team would like to call our current landing page done for now and ready for the F38 rollout. We will have opportunities to make changes after the rollout I believe. 18:44:13 Yes, what is there is considered by the team to be near final. 18:44:23 I like it 18:44:40 me too 18:44:57 +1 18:45:16 Good I'm glad everyone is okay with the 1.0 version of the revamp. 18:46:00 I have requested new graphic assets for the last three "features" that is what Emma is working on today and tomorrow. 18:46:36 mowest Is there a chance for a better Logo the the current? 18:46:50 s/the/then 18:47:20 @pboy, I don't know if we can get a better logo at this stage. I know you aren't crazy about the orange. :-) 18:47:54 OK. let's hope, and maybe you can nag a bit? 18:48:19 Anything else here? 18:48:27 Do you have any suggestions to give them some direction. 18:48:45 not really at the moment 18:48:54 I don't have anything else at this time, I'm thankful for all of the work the website team has put into our page. 18:49:13 yes, huge congrats to the website team 18:49:17 maybe a small version of the header graphic (stacked servers)? 18:49:37 mowest +1 18:49:40 In what color @pboy? 18:50:25 mowest I don't know, not orange :-). I think a designer knows best (even if it is orange) 18:50:42 Ok :-) 18:50:48 I'm done. 18:50:59 Something else? 18:51:13 Otherwise I'll switch 18:51:15 You can move to the next topic. 18:51:55 #topic 5. Open Floor 18:52:27 I visited Fosdem this year. It was very interesting. 18:52:41 There will be a Fedora Magazine article. 18:52:50 * luna was also there helping out in the Fedora booth :) (looking forward to the article) 18:53:10 Next year we should have a speech about Fedora Server 18:53:28 luna +1 to your work We have met, haven't we? 18:53:47 pboy: yeah i think so you where the one asking for the getting starting guide stuff right? 18:54:15 Yes, it was me. :-) 18:54:20 then we did :) 18:54:28 good! 18:54:42 pboy: I would have reconsidered not going if I had known you would be there 18:55:21 As I said, we should aim to have a talk about Fedora server next year, maybe about our Ansible project. 18:56:02 eseyman thank you. I must admit, it was quite spontaneous 18:56:39 I had some concerns about Covit and the Deutsche Bundesbahn (train company) 18:57:36 I think there is a meeting in August in Europe (Spain?) 18:57:49 x3mboy as an ambassador, do you know details? 18:57:49 we'll need to plan ahead of FOSDEM 2024 a meeting 18:58:02 eseyman +1 18:59:57 Obviously, we don't know about this summer at the moment. 19:00:09 OK,. time is up 19:00:15 anything else? 19:00:29 I'm good 19:00:36 Thanks to everyone who participated today. Good Meeting! 19:00:54 OK, Thanks to everybody for comming 19:01:02 See you in 14 days! 19:01:16 #endmeeting