17:00:26 #startmeeting fedora-server 17:00:26 Meeting started Wed Jun 2 17:00:26 2021 UTC. 17:00:26 This meeting is logged and archived in a public location. 17:00:26 The chair is pboyHB. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:26 The meeting name has been set to 'fedora-server' 17:00:35 #topic Welcome / roll call 17:00:39 .hello2 eseyman 17:00:40 eseyman: eseyman 'Emmanuel Seyman' 17:00:42 hi everyone! 17:00:48 Hi 17:00:49 hello, all 17:00:53 .hi 17:00:54 cyberpear: cyberpear 'James Cassell' 17:00:56 Everybody who is lurking, please say either .hello2 or .hello , too 17:01:07 .hello2 17:01:08 swefredde: swefredde 'Fredrik Arneving' 17:01:27 .hello chrismurphy 17:01:28 cmurf: chrismurphy 'Chris Murphy' 17:01:32 .hello2 17:01:33 langdon: langdon 'Langdon White' 17:01:35 wasm 17:01:46 wasn't sure if we were here or in freenode 17:03:00 I'm glad we're here, I'm no longer connected on Freenode 17:03:21 #topic Agenda 17:03:30 #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/GEX3READTR5QNZRL3QY5QJI3F2CGSBBM/ 17:03:37 1. Welcome 17:03:43 2. Agenda 17:03:49 3. Explore opportunities for cooperation with Cloud WG / Cloud Base Images as Fedora Server VM 17:04:00 3. Explore opportunities for cooperation with Cloud WG / Cloud Base Images as Fedora Server VM 17:04:12 Fedora Server Documentation review 17:04:19 Open Floor 17:04:46 #topic Explore opportunities for cooperation with Cloud WG / Cloud Base Images as Fedora Server VM 17:05:03 Current Status: 17:05:10 We discussed opportunities of a cooperation with Dusty Mabe in early March 17:05:16 Dusty raised the topic at the first „new“ cloud meetings March 30. 17:05:23 Now we are at the beginning of June, without any progress 17:05:30 We as Server WG have clearly expressed our interest several times 17:05:36 Additionally 17:05:43 Brief discussion on the relationship between Fedora Server and cloud images: 17:05:50 #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/LVBLTCDDR3EGDCFQZJY5OPWUONWNCCOZ/ 17:05:58 Summary: Cloud and server too different, there is a (good) reason that both groups exist, a VM based on cloud will never be anything like Fedora Server. 17:06:08 Proposal: Defer the topic „explore opportunities for cooperation with Cloud WG“ (low in priority) and wait to see what Cloud WG comes up with. 17:06:14 Regarding a VM version of Fedora Server, we might have to seek an interim solution. 17:06:27 That's sso far. The floor is open 17:06:31 vagrant images are also a challenge 17:09:39 I see no comment so far. I would agree the proposael in a minute or so. 17:09:51 i wonder if it might be, in the near term, to have a "monthly" conjoined meeting of the 2 groups 17:10:11 Dusty isn't here, and I've discovered the matrix IRC bridge isn't working reliably. 17:10:20 a little discussion might show us what work we can share 17:10:33 langdon: I would like that. But I don't see it. in tghe moment. 17:10:43 i know when i was involved in the discussion of combining the two editions/wgs it was really about things like "containerization of all the things".. and if we coudl make sure we are both heading in the same direction and learning from each other i wonder if this would accomplish the same goal 17:11:50 right.. we have a lot of overlap.. but very little on the fundamental of "edition".. e.g automated install of mail server would be very practical to both.. but btrfs/xfs while fundamental and distinct in editions is actually kinda "boring" re: goals of the editions 17:12:41 so maybe regular alignment/prioritization would just make sure we aren''t both trying to build "easy install of mail server" or whatever 17:12:52 cmurf: Do you propose to wait for Dusty? Does this provide additional insight? 17:12:57 and... sorry for my examples.. ignore the content as much as "where in the stack" 17:13:27 langdon: That would be at least some progress. 17:13:40 and might actually address the real goal.. 17:13:57 My position is that Cloud+Server collaboration is orthogonal to the Cloud Btrfs by default change proposal, contrary to Peter's assertions on devel@ list. 17:14:14 cmurf: i knew i shouldn't use btrfs as an example :) 17:14:31 If anything it makes the more alike, because Btrfs has an integrated volume manager and supports reflinks and snapshots. So does Server via LVM and XFS, whereas ext4 supports none of that. 17:14:33 i just meant its a fundamental 'edition building" difference.. not whether its a good or bad choice 17:14:37 s/the/them/ 17:15:28 im with you on btrfs ... been running it on my daily driver for more than a year ... and haven't noticed.. except that i don't have to allocate space to my vms virt disk all the time :) 17:16:19 cmurf: I could agree with the thesis of orthgonality. 17:16:44 but.. if btrfs2 comes along.. i would be happier running that in the cloud edition .. on disposable machines.. than i would be on a bare metal server 17:16:59 so.. a reason for edition separation exists 17:17:34 murf: Nevertheless, instead of dropping it at all, I would prefer to defer it for now. 17:17:47 Sorry 17:17:49 cmurf: Nevertheless, instead of dropping it at all, I would prefer to defer it for now. 17:18:04 Or what is your suggestion? 17:18:09 that sounds fair 17:19:06 unless i misunderstand the proposal.. you can still *choose* to not-btrfs.. btrfs just becomes the default so it gets in to wider use in places where people don't care 17:19:28 Since you stated a "coup" has occurred as a result of the Btrfs by default change proposal, that's scuttled this alignment/merger question, I think it's relevant now to see if any other Server working group member agrees with that assessment. 17:19:41 Because I always try to give the contrary/minority view a voice. 17:19:50 but if it's just one voice, then we need to move on. 17:19:52 Yes, for the time being i would prefer to stay with LVM /XFS. 17:20:09 why? if you can still choose it? 17:20:15 I don't think Btrfs for Server is really on the table. There's no change proposal for it. 17:20:52 ok.. so table it.. but any which way.. i don't think merging the editions is a good idea.. at least now.. and, im starting to think, ever 17:21:26 cmurf: BTRFS ist just one item. And it must not be a show stopper, in my view 17:21:56 Ok, I see we agree 17:21:59 3 17:22:07 2 17:22:14 agreemnet? 17:22:20 yyes 17:22:22 like what do you want to #agred 17:22:29 i can't type today apparently 17:22:47 #agreed. Defer the topic „explore opportunities for cooperation with Cloud WG“ (low in priority) and wait to see what Cloud WG comes up with. 17:23:11 #topic Deploying services via RPM and Ansible (continuation) 17:23:14 i don't agree with that 17:23:35 I'm not in either SIG strictly speaking, I just poke my head in when it comes to bootloader and filesystem things :P but I rather like the idea of Cloud restoring its Edition status. 17:23:42 #undo 17:23:42 Sorry, made a copy & paste error in the Agenda above. This is the topic as in the email 17:24:27 langdon: What do you mean ? 17:24:29 i think cooperation should be a high priority ... with a formal relationship like monthly conjoined meetings.. i don't think a merger is something we want to pursue at this time 17:24:50 you #agreed and switched topics before anyone had a chance to comment :) 17:25:03 I think cooperation among editions and spins is so important it's effectively "built-in" to the process. 17:25:11 OK, whats your exact proposal? 17:25:19 Even primarily Workstation changes, I consider at minimum deconfliction with other spins and editions. 17:25:46 Like, how could a change negatively impact others... 17:25:52 maybe #undo the topic switch so the logs aren't messed up (im not a chair so mine didn't matter) 17:26:24 langdon: how do i do that? 17:26:32 literally "#undo" 17:26:40 #undo 17:26:40 Removing item from minutes: 17:26:49 cmurf how do you think the cooperation is built in the process? 17:26:59 if you do it again, it will do the #agreed as well 17:27:08 pboyHB, langdon: "actively explore opportunities for cooperation with Cloud WG through discussions"? 17:27:20 i can't remember when workstation coordinated with cloud or server :) 17:27:30 change proposals are brought to devel@ for review, all the stake holders get a chance to ack/nack/patch any proposal. 17:27:31 eseyman: We tried that several times 17:28:14 But insofar as Cloud+Server specifically I think the issue is saying you want to collaborate isn't specific enough. It's a glittering generality. It sounds good but doesn't describe next steps. 17:28:22 cmurf: well.. thats after the fact and makes sure we don't actually shoot ourselves in the foot.. not exactly leading the cooperation :) 17:28:32 I think you need a particular something you want or need to collaborate on. 17:28:45 cmurf: the exact wording is: exploring .... 17:28:45 cmurf: im not sure of the "you" in that .. but i agree... 17:29:25 you = the two parties 17:29:40 i would say something like "seek to create a monthly meeting between the cloud and server wgs" and "defer the exploration of a merger of the cloud and server wgs until collaboration has been explored as independent groups" 17:29:46 "wait to see what Cloud WG comes up with" sounds barely better than nothing at all 17:29:49 so kinda like what eseyman said but more 17:30:10 that's my issue with the original proposal 17:31:12 new proposal: defer the exploration of a merger of the cloud and server wgs until collaboration has been explored as independent groups and seek to create a monthly meeting between the cloud and server wgs 17:31:31 yeah.. but i would lose the "and" and just do 2 17:31:40 +1 on that 17:32:14 new proposal: Defer the exploration of a merger of the cloud and server wgs until collaboration has been explored as independent groups. Seek to create a monthly meeting between the cloud and server wgs 17:32:31 3 17:32:33 sorry if i wasn't clear.. i meant: 17:32:51 cow-#agreed: Defer the exploration of a merger of the cloud and server wgs until collaboration has been explored as independent groups. 17:32:53 and 17:33:04 cow-#agreed: Seek to create a monthly meeting between the cloud and server wgs 17:33:34 OK: Propoal is 2 agrees as langdon said. 17:33:37 s/cow/foo ... i started using "cow" as a default var name a LONG time ago 17:33:44 3 17:33:53 2 17:34:03 1 17:34:15 #agreed Defer the exploration of a merger of the cloud and server wgs until collaboration has been explored as independent groups. 17:34:33 #agreed Seek to create a monthly meeting between the cloud and server wgs 17:35:02 As for action: who volunteers to seek? 17:35:34 well.. the first one is easy.. don't do anything :) 17:35:50 the second one.. one or more of us ask to add it to their next agenda? 17:36:00 Yes, woh does the second on, seek to create ... 17:36:24 i can certainly help as i know dusty well.. but.. i am not the "leadership" of this group at the moment 17:36:34 langdon: do you take it? 17:36:42 sure... i can 17:36:50 or cmurf? 17:37:00 #action: Langdon will contact Cloud WG 17:37:01 doesn't matter to me, I also know Dusty 17:37:10 super :) 17:37:33 #topic Deploying services via RPM and Ansible (continuation) 17:37:46 Status: 17:37:54 I added / refined use case „Wildfly“ as described by jwhimpel (via email) 17:38:02 Unfortunately didn’t manage to complete the other use cases so far. 17:38:20 So, the floor is open 17:39:24 I'm still interested in making a Bugzilla deployment as easy as possible 17:39:31 I still volonteer to contribute but prefer the sysadm tasks before java/developer stuff 17:40:30 That would be a use case of its own. Could you elaborate a bit? here a bit short, longer on mailing list? 17:41:06 Not really, Anything in line with what jwhimpel descrbes when it comes to mail services. 17:41:17 swefredde: We could elaborade the other usecases, mail, IPA etc. 17:41:21 I guess whatever it will be I'll need to read up a bit to start with 17:41:41 postfix + amavis + spamassassin + dkim +... 17:42:12 koji + bodhi? 17:42:32 ...will start with some reading... LOL 17:42:33 as a java programmer for many years.. i would probably be able to stand up wildfly on my own.. but a mail server? no way 17:42:52 koji+bodhi seems low on the list.. why not just use fedora's 17:42:59 langdon: it's the other way round for me 17:43:10 swefredde: I could send you a step-by-step documentation how to set up manually. 17:43:33 I was thinking of making it easy to set up a Fedora downstream 17:43:34 swefredde: may be an inital guide 17:43:54 Sure, but have we agreed on what to set up exactly? 17:44:10 langdon: I would join the wildfly project 17:44:16 eseyman: is that really the target audience? isn't it people who want to have a small office server 17:44:59 pboyHB: ohh... i shouldn't do it.. we should get some expert.. whatever way i set it up would work but would have massive security holes and baling wire :) 17:45:01 not sure, TBH 17:45:22 thats what the prd said :) 17:45:30 sorry, what is TBH? 17:45:37 to be honest 17:45:47 oh, thanks 17:46:07 if you haven't used/seen https://www.acronymfinder.com/ is really good 17:46:29 langdon: Thanks, copied to bookmarks 17:46:32 in case you see TLAs where you don't want to ask :) (three letter acronyms) 17:46:36 so SOHO mail service and what? a file server setup 17:46:45 ? 17:47:13 files, maybe sso, dns, dhcp, things like that 17:47:41 * langdon couldn't remember the soho acronym :) 17:47:53 small office, home office 17:48:05 Proposal: I'll sort this discussion in the wiki page and we continue on mailing list? 17:48:14 as we are running out of time 17:48:15 yeah... else i would have used it above.. but had MOBO stuck in my head :) 17:48:19 pboyHB: +1 17:48:22 well 17:48:36 +1 17:48:41 yeah, let's continue on the list 17:48:43 i think "whats in a soho server" might eb a good wiki page.. and then link out to get to the installs 17:48:43 #action pboy will sort out this discussion on the wiki page. 17:49:00 and then people could add/argue "whats in soho" 17:49:05 #topic Fedora Server Documentation review 17:49:10 Status: 17:49:18 We have now sufficient content to start and make the content publicly available (Marked as beta for now). 17:49:25 We need to review each of them. 17:49:39 There a 5 articles to be reviewed. 17:49:55 #link https://fedoraproject.org/wiki/Server/Documentation 17:50:17 Section "Content to start with" 17:50:45 * langdon adds to his reading list 17:51:03 who can take one of the articles 17:51:11 * eseyman adds to his reviewing list 17:51:53 pboyHB: I'll take "Server Administration" 17:52:10 eseyman: thanks" I'll add it do the list 17:52:38 I go with the SBC 17:53:11 swefredde: thanks 17:53:34 FTR, that "Communicating and Getting Help" gets me a 404 17:55:02 Sorry, will correct is after our meeting 17:55:08 np 17:55:56 Someone else? 17:56:18 Guys, I spend a lot of time in writing. 17:57:05 OK, Hope dies last. 17:57:06 ill try to look at them all.. but i don't want to sign up to be a reviewer atm 17:57:27 #topic Open Floor 17:57:34 I can go through Virt as well 17:57:43 swefredde thanks 17:57:49 langdon thanks 17:58:06 finally managed to attend a meeting \o/ 17:58:28 Congratulations 17:58:46 well, time is up 17:59:02 in a minute I'close if there is nothing else 17:59:36 OK, many thanks to everybody! 17:59:44 #endmeeting