17:00:25 #startmeeting fedora-server 17:00:25 Meeting started Wed May 3 17:00:25 2023 UTC. 17:00:25 This meeting is logged and archived in a public location. 17:00:25 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:25 The meeting name has been set to 'fedora-server' 17:00:36 #topic Welcome / roll call 17:00:46 Welcome to our Server WG IRC meeting today! 17:00:57 „Same procedure as every year“ We'll give a few minutes for folks to show up 17:01:08 I’ll post the agenda in 2 minutes. 17:01:49 hello, all 17:01:57 .hello2 eseyman 17:01:58 eseyman: eseyman 'Emmanuel Seyman' 17:02:28 .hello2 cooltshirtguy 17:02:29 cooltshirtguy: cooltshirtguy 'Jason Beard' 17:02:56 might be slow to reply, in a virtual customer meeting 17:02:58 .hello 17:02:58 jwhimpel: (hello ) -- Alias for "hellomynameis $1". 17:03:11 .hello2 17:03:12 jwhimpel: jwhimpel 'John Himpel' 17:03:59 Welcome everyone 17:04:08 I start with the agenda 17:04:16 #topic Agenda 17:04:24 #info Follow up actions 17:04:31 #info Fedora Server goal(s) for F39 17:04:39 #info Each Edition has a story for each release 17:04:48 #info Using Ansible to install and configure Wildfly 17:04:56 info Open floor 17:05:16 #info Open floor 17:05:27 Any topic to add? 17:05:33 nope 17:05:45 Yeah, it's enough as is. :-) 17:05:54 #topic 1. Follow up actions 17:06:04 #info ACTION: pboy will write a info about changing the timeout value and nirik will review – still work in progress 17:06:12 #info ACTION: eseyman will try and think up something for next meeting 17:06:23 The latter is part of our agenda today 17:06:39 Any open action I forgot? 17:06:50 Anything else to announce here? 17:07:01 I did promise to review one of our documents 17:07:31 hehe 17:07:41 Yeah, I suppose you are not yet finished? 17:08:04 almost done but not yet finished 17:08:18 yes, thanks! 17:08:30 well. next topic 17:08:43 #topic 2. Fedora Server goal(s) for F39 17:08:51 #link https://pagure.io/fedora-server/issue/102 17:08:59 Lets spend about 30 min at max. here 17:10:00 Honestly, I think using the SBC as a story is the best option 17:21:12 Obviously, I got disconnected somehow. Still someone around? 17:21:52 jwhimpel is still here 17:22:03 OK, thanks! 17:22:36 eseyman you OK? 17:22:49 im here 17:22:53 cooltshirtguy ? 17:22:55 yes, still here 17:23:18 OK. don't know why my connection died. 17:23:26 Well, any comment? 17:23:59 Honestly, I think using the SBC as a story is the best option 17:24:56 yes, the story is the next topic. 17:24:56 for me SBC is the best 17:25:21 I like the SBC story also. But I don't know if we have enough expertise in this group to make informed recommendations. We would probably have to engage with Paul Whelan and Peter Robinson, who are both very busy already. 17:26:06 jwhimpel agreed. But we can make our own criteria. 17:26:38 E.G. for a server you would need SPI to access storage like NVMe or SATA 17:27:10 And we can check, it it's available, if it's supported by Fedora, etc. 17:27:33 And I suppose, ARM Sig is willing to discuss questions with us. 17:28:49 Currently, I own 2 models, Radxa Rock Pi and pine64 rockpro64. 17:29:18 And I know of 2 manufectures wha had been willing to send test devices. 17:29:31 Anyone else with an SBC? 17:29:46 pboy: It's more the u-boot issues and need for proprietary modules that I think might be problematic. 17:29:56 i have a pi2 pi3 and pi4 17:30:25 I learnt last night that Khadas boxes are compatible with Fedora so that's very good 17:30:42 jwhimpel yes u-boot is the biggest issue. But then kernel modules as well, e.g. to support SATA 17:31:28 Humm... racking a server on a SKÅDIS... 17:31:31 cooltshirtguy that very good, pi2 is no longer supported by Fedora (arm7 as fas as I know), but the others are. 17:31:53 they'r starting to collect dust 17:32:01 *they're 17:32:09 eseyman khadas is vey powerful and makes a nice impression 17:32:41 apart from the purse 17:32:47 :-) 17:32:52 I'm running one as my HTPC using CoreElec and I'm a very happy user 17:33:03 yes, the newer one are not cheap 17:33:12 s/one/ones/ 17:33:28 OK, I think we can agree: 17:33:29 a lot of sbc's are hard to get right now 17:33:53 cooltshirtguy> indeed? 17:34:04 ? ->! 17:34:10 :) 17:34:13 Regarding agree: 17:34:24 1. prrority: SBC 17:34:47 2. priority: virtualized environment 17:34:58 as goals for F39. 17:35:15 objections? 17:36:13 looks good to me 17:36:32 nope 17:36:44 #agreed WG will pursue SBC as first priority for F39, and servers in virtualized environment as 2nd priority. 17:37:10 so let's switch to next topic. 17:37:23 #topic 3. Each Edition has a story for each release 17:37:32 #link https://pagure.io/fedora-server/issue/101 17:37:39 same thing, really 17:38:01 I really don't like this idea at all, btw 17:39:07 I am "split". :-) 17:39:39 The marketing push could be nice, but to get it done vor every release is a challenge 17:40:38 But for the next 2 releases we would have something already 17:40:53 Sorry, but I have to leave now for a previous commitment. 17:40:55 true 17:41:46 jwhimpel sorry about the delay today., we will start next meeting with wildfly. 17:42:50 #proposed WG will pursue SBC as the 'story' for F39 with first priority, servers in Virtuialized environment with 2nd priority. 17:42:58 Any objections? 17:43:20 +1 from me 17:43:44 #agreed WG will pursue SBC as the 'story' for F39 with first priority, servers in Virtuialized environment with 2nd priority. 17:44:05 How will we proceed? 17:45:53 I could put an abstract with suggestions on key content points and some usability theses on the mailing list or maybe b etter on hackmd.io? 17:46:10 Or do we have an etherpad on Fedora infra? 17:46:43 i have no idea 17:47:15 given the technology behind etherpad, I doubt it 17:47:33 OK, so mailing list or hackmd.io 17:47:48 Maybe hackmd would be better 17:47:50 Please tell me I don't have to use Fedora Discussion for this 17:48:12 We used it already successfully with PRD und technical spec. 17:48:26 eseyman no, better not. :-) 17:49:45 I guess hackmd is better then mailing list. you can comment directly to each sentence. 17:50:01 yes 17:50:42 OK, then 17:51:03 ok 17:51:11 #action pboy will post a first draft regarding SBC on hackmd.io. 17:51:48 so, I think we are done with this topic? 17:52:57 I think, we should discuss Ansible/wildfly next meeting as first topic, when jwhimpel can participate. 17:53:04 sounds good 17:53:12 Without him it makes not much sence. 17:53:18 OK, so 17:53:59 #agreed. skipping topic 4. Using Ansible to install and configure Wildfly 17:54:07 topic 5. Open Floor 17:54:17 #topic 5. Open Floor 17:54:44 FTR, I'm still working on my NAS project 17:54:59 Uh, we have time for this! Last time we had was long ago. 17:55:24 That's the backup / restore project, isn't it? 17:56:40 yes, the goal is to set up a remote server and have a set of backups over there as well as locally 17:57:15 Sounds exciting 17:57:23 This is IMHO one of the excellent usage options for SBC 17:57:52 I think, an SBC is still too slow for interactive applications 17:58:20 agreed 17:58:34 eseyman Do you use a khadas board? 17:59:48 I have a Vim 1 that's a few years old at this point 18:00:29 i'll have to look that one up. never heard of it 18:00:49 Oh yeah, a vim 1 is quite old, indeed. It is in the range of pi 3, isn't it? 18:01:07 that should be about right 18:01:39 So, we can include it in our F39 story. 18:01:58 it runs Coreelec right now, not Fedora 18:02:19 Hopefully, you can test it with Fedora? 18:02:19 the vim4 has some nice specs 18:02:56 cooltshirtguy yes. I'll try to get a test device for us. 18:03:39 OH, I see our time is up! 18:04:20 I'll put a draft on hackmd about at the weekend. And then let's discuss it over there. 18:04:34 k 18:04:38 See you in 2 weeks! 18:04:57 #endmeeting