18:00:10 #startmeeting fedora-server 18:00:10 Meeting started Wed Mar 15 18:00:10 2023 UTC. 18:00:10 This meeting is logged and archived in a public location. 18:00:10 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:10 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:10 The meeting name has been set to 'fedora-server' 18:00:19 #topic Welcome / roll call 18:00:20 .hello2 18:00:20 mowest: mowest 'Steve Daley' 18:00:33 Welcome to our Server WG IRC meeting today! 18:00:41 Hi mowest 18:01:03 Please, everybody who is lurking, say either .hello2 or .hello 18:01:09 Hello pboy, thanks for leading our meeting once again. 18:01:23 Thanks, I do my best. :-) 18:01:31 And I’ll post the agenda in 2 minutes. 18:02:09 .hi 18:02:10 pboy: pboy 'Peter Boy' 18:02:58 mowest thanks for comming 18:03:10 I guess many missed the time changing 18:03:42 Well let's start nevertheless with the agenda 18:03:47 * nirik is as usual busy other places, but lurking in the back if he can help any 18:04:01 nirik Thanks! 18:04:02 Yes, the time change confused me a bit, an hour later for me today which is okay for my schedule. 18:04:32 Yeah, but many might run into difficulties 18:04:40 #topic Agenda 18:04:50 #info Follow up actions 18:04:58 #info Change of timing of our meetings in summer 18:05:07 #info F38 Beta testing 18:05:20 #info F38: Shorter Shutdown Timer 18:05:29 #info Fedora Website revamp – Fedora Server Edition pages 18:05:38 #info Using Ansible to install and configure Wildfly 18:05:46 #info Open Floor 18:06:04 Anything else to add? 18:06:10 Nothing from me 18:06:14 OK 18:06:25 #topic 1. Follow up actions 18:06:38 #info DONE action nirik to look up the services in our technical specification and check for time out value 18:06:48 #info DONE pboy to create a ticket to collect our central messages for the new web site 18:06:58 #info DONE action pboy will create a summary of our discussion about service specific timeouts 18:07:07 #ingo DONE pboy will open a mailing list discussion about interdependencies between services and the consequences 18:07:29 So, there arfe no open actions. Or did I miss something? 18:07:52 None that I know of 18:07:57 OK 18:07:58 #info No further open actions 18:08:22 #topic 2. Change of timing of our meetings in summer 18:08:52 .hello2 18:08:53 cooltshirtguy: cooltshirtguy 'Jason Beard' 18:08:57 Well,formaly we can't decide anything, because we miss the quorum. 18:09:16 Hi Jason! now we have the quorum. 18:09:25 cool 18:09:56 What do we do with our meeting time change? 18:10:39 Any objection here? 18:10:45 Since US had its time change, if you wanted to go back to 17:00 UTC I would be okay with that. 18:11:23 I like either 17:00 UTC or 18:00 UTC because I'm usually in the office at those times on a Wednesday and can be in IRC. 18:11:51 Keeping it at 18:00 UTC would be fine for me too. 18:12:15 17 or 18 UTC is fine with me. 18:12:33 Last fall we decided to adjust the time, winter time it was, so it is the same time for everones everyday :-) 18:13:07 i joined at noon. i forgot about the time change 18:13:20 If 18:00 UTC you could just leave it even with the time changes for me. When it is 17:00 UTC in the Fall that lands during the lunch hour and I'm hit or miss at that time. 18:14:13 cooltshirtguy, you must be Central time zone? 18:14:37 .hello2 18:14:40 copperi[m]: Sorry, but user 'copperi [m]' does not exist 18:14:44 yep 18:14:52 The experience from winter was, so long as we kept with 18:00 UTC, we had significant less participants. 18:15:55 I'm fine with 17:00 UTC during the summer then, and 18:00 UTC during the winter if you think we can have better participation. 18:16:04 Well, I think the best way is to open a thread on the mailing list. We are not enough people at the moment. 18:16:37 mowest that's the idea, to switch with each time chane so it's the same in everyday life. 18:17:14 any objection to open a thread on mailing list? 18:17:22 No objection 18:17:40 nope 18:17:50 #action pboy to open a thread about meeting time change on mailing list. 18:18:01 OK, next topic 18:18:11 #topic 3. F38 Beta testing 18:18:27 #link https://pagure.io/fedora-server/issue/99 18:18:44 I created a list of things to test in additin to the automatic tests. 18:18:53 Anything to add here? 18:20:03 OK none 18:20:15 And the magic question: who will take case of which item? 18:20:26 s/case/care 18:22:00 I can handle all the installation and virutalization topics 18:22:20 What about postgresql? 18:22:42 Looking at this list I don't think I normally do any of those tasks on my servers. 18:23:33 mowest OK, you are out of the game (Leonard Cohen. :-) ) 18:23:47 :-: 18:23:50 :-) 18:24:03 I know i did install on a pi last time. 18:24:15 sgallagh are you online? Can you care about IPA again? 18:26:11 Hm, probably not online. 18:26:29 We will check next meeting again. 18:26:45 We have currently a slight issue with Server VM 18:27:06 postgresql just install it? 18:27:40 coolshirtguy yes, install and start postgres, following the documentation. 18:28:07 sure i can do that 18:28:19 OK! thanks! 18:28:48 Regarding server VM, we have a kind of missunderstanding, hopefully 18:28:58 #link https://pagure.io/fedora-kickstarts/pull-request/949 18:29:06 #link https://pagure.io/fedora-kickstarts/pull-request/948 18:29:37 nirik Do you think we get it into the next beta? Do you need additional information? 18:30:00 I have not yet had time to get back to it. 18:30:14 I just wanted to know what the problem was so I could review the change. 18:31:07 Yeah, I added complete information. There is no bug at all, I did it just the wrong way at first. 18:31:47 And after studying virt-install documentation I found the mistake and fixed it with the PR 18:32:37 * nirik will add feedback there/merge when I get a chance. 18:32:47 OK, thanks 18:32:59 Anything else here? 18:33:26 Obviously not. 18:33:28 nope 18:33:39 #topic 4. F38 - Shorter Shutdown Timer 18:33:52 #link issue #96: https://pagure.io/fedora-server/issue/96 18:35:04 First we should not forget our intention to include a text in our documentary "how to make changes to the .service file if someone has an issue." (jdubby last meeting). 18:35:15 A section in the "Post Installation Guide" would be a convenient spot 18:35:28 Who can write a short appropriate text? I could include it in the documentation if that should be a problem. 18:37:48 nirik Can you provide me with 2-3 sentences shat to do where and I can add it to documentation? 18:38:07 I have currently no idea where to start. 18:38:19 s/shat/wwhat 18:38:33 are we following coreOS and not using the new timer? still connfused on which way were going 18:38:36 I think it's just one line in the service file... 18:39:01 nirik yeah, which service file? 18:39:10 or a /etc/systemd/systemd.conf to change globally. 18:39:37 OK, I think the proposal is to do it globally 18:39:45 the service file for the service you want to change? just add TimeoutSec=infinity to the [Service] section 18:40:44 in /etc/systemd/system.conf: DefaultTimeoutStopSec=infinity 18:40:45 (or number of seconds) 18:41:12 nirik I'll take all this information and write a text. Would have a short look onto it? 18:41:35 To ensure I don't write soemething completly wrong. :-) 18:41:38 sure, I can. I wonder... could this be a quick doc? or is it too specific? 18:42:11 We could make a quick doc and will add a section to our post-install guide. 18:42:39 happy to help review (although I am traveling all next week) 18:42:45 I like the idea of adding it to the Post-Install guide which I think has similar tweaks. 18:42:58 that's the next question we have to discuss 18:43:40 ok 18:43:40 #action pboy will write a info about changing the timeout value and nirik will review 18:44:05 So, nest item here. 18:44:39 I wrote a summary of the current status of time out value configuration. 18:44:54 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/O35T2YYLSXC6YAV5LRYBPZENW3AX4GEP/ 18:45:00 at the end. 18:46:12 In short: the situation is mixed and not a solid and reliable overall configuration 18:47:30 And therefore my proposal to follow CoreOS 18:47:43 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/ERF2MR7NMO44FWIHUJFF3NW7LAMK7SMM/ 18:48:22 Any ideas? comments? 18:48:30 I'd personally say stick to default, but if I am in the minority thats fine, I will move on with life. ;) 18:48:59 follow coreOS 18:49:12 +1 18:49:13 I would prefer to stick with as many defaults as we can have with Workstation. It brings us in line with the majority of installs and users then. 18:49:54 I would prefer o follow coreOS, too. 18:50:40 so follow CoreOS +3, 0, -2 18:50:48 Did I count right? 18:51:10 looks right to me 18:51:13 Looks like you did count correctly. 18:51:15 yep 18:51:50 OK, so let's do it. 18:52:40 #agreed to take the same oute as CoreOS and keep the old default value. +3, 0, -2 18:52:47 undu 18:52:50 undo 18:52:55 #undo 18:52:55 Removing item from minutes: AGREED by pboy at 18:52:40 : to take the same oute as CoreOS and keep the old default value. +3, 0, -2 18:53:00 pboy: Sorry, my ping notification just went off now 18:53:02 What did you need? 18:53:10 #agreed to take the same route as CoreOS and keep the old default value. +3, 0, -2 18:54:03 sgallagh We need someone to test the IPA criterium for beta. You used to do that some release ago* 18:54:37 I stopped because it's exercised very thoroughly by autoqa at this point. 18:55:30 OK, so you think we can it remove from the manual testing list? 18:56:43 Yes 18:56:58 OK, then I'll do that. Thanks. 18:57:10 Well, next topic 18:57:28 #topic 4. Fedora Website revamp – Fedora Server Edition pages 18:57:51 #link Issue #66: https://pagure.io/fedora-server/issue/66 18:58:00 Current draft: 18:58:10 #link https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/server/ 18:58:18 Developer discussion 18:58:29 #link https://discussion.fedoraproject.org/t/fedora-server-front-page-revamp-looking-for-feedback/79037/9 18:58:51 We have to decide about the graphics and specifically about the descriptive texts 18:59:07 mowest how do you see it? 18:59:41 I would like to see us happy with the graphics for the F38 release because I think they have limited time at this point to make major graphics changes. 18:59:46 I'm impressed 19:00:10 mowest +1 19:00:20 I can live with the current wording, but I read your email and we would have to do some work to recraft your ideas with the current graphics. 19:01:13 mowest We should make compromises. We should take the graphics as given. And work with those / around those. 19:01:52 Problem is, our time is up. 19:01:58 It looks lovely. Thanks for all the hard work on it! 19:02:11 pboy, I know that you would like to expose the docs more, but from the mockups that I have seen they seem to want to keep the docs under the "Help" menu. 19:02:34 mowest. yes to ma chagrin 19:02:57 The docs team decided to open an issue about it. 19:03:12 nirik +1 ! 19:03:44 I could see a "Download" button next to a "Documentation" button, I think that would look nice, but the website design team would have to go for that idea. 19:04:20 For all the editions 19:04:27 I'm very content with the page. It's just a bit of fine tuning I would like to get done 19:05:29 Well, we have to continue the discussion by email or in our chat room. 19:05:32 I like it 19:05:37 I'm okay with the current being version 1 if we can't get any other wording changes in before F38, but I know the website team wants to open up being able to change the text. 19:05:46 It looks nice 19:05:51 to the WG's 19:06:27 mowest that would be cool and helpful 19:07:19 mowest can we chat tomorroy at 18:00 UTC in our chat room? 19:08:07 Yes I can try to be there for a bit 19:08:08 So we can discuss how to proceed in detail? 19:09:05 OK, than let's try that. Of course, everyone is invited !! 19:09:15 mowest is our designee for this, so we need him. 19:09:20 :-) 19:09:43 see you tomorrow in #fedora-server 19:09:57 OK, I close now. Let's meet in our chat room or in 3 weeks !!!!!!! in April 19:10:16 #endmeeting