21:00:14 #startmeeting Fedora Server SIG Weekly Meeting (2017-12-19) 21:00:14 Meeting started Tue Dec 19 21:00:14 2017 UTC. The chair is sgallagh. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:14 Useful Commands: #action #agreed #halp #info #idea #link #topic. 21:00:14 The meeting name has been set to 'fedora_server_sig_weekly_meeting_(2017-12-19)' 21:00:14 #meetingname serversig 21:00:14 The meeting name has been set to 'serversig' 21:00:14 #topic Roll Call 21:00:18 .hello2 21:00:19 sgallagh: sgallagh 'Stephen Gallagher' 21:00:28 .hello2 21:00:29 smooge: smooge 'Stephen J Smoogen' 21:00:42 Thinks this will be a lonely meeting 21:00:49 * langdon sorta here 21:00:52 .hello dperpeet 21:00:53 dperpeet: dperpeet 'None' 21:01:49 dperpeet: What, really? Didn't your wife just have a child? Why are you here? 21:02:21 * smooge goes for the 1950's joke.. "His wife just had a child" 21:02:30 sgallagh, it's night here, no child of mine likes to sleep at night when they're young :) 21:02:37 Well, we don't have a lot to discuss anyway. 21:02:42 #topic Agenda 21:03:08 #info Agenda Item: Hybrid Modularity 21:03:17 anyone else want to bring up a topic? 21:03:30 * Server testing 21:03:42 hmm 21:03:53 should I rephrase with info? 21:03:59 #char dperpeet 21:04:02 #chair dperpeet 21:04:02 Current chairs: dperpeet sgallagh 21:04:08 (sorry, didn't mean to cook you) 21:04:15 #info Agenda Item: Fedora Server testing 21:04:23 no problem, cuts down the heating costs 21:04:36 ha! 21:04:44 OK, let's get rolling 21:04:57 #topic Hybrid Modularity 21:04:59 I read your article 21:05:12 #link https://communityblog.fedoraproject.org/modularity-dead-long-live-modularity/ 21:06:39 tl;dr: We've come up with a way to adapt the modularity plan such that it can live atop the traditional Fedora release rather than fully replacing it. 21:06:46 yay 21:06:48 Though replacing it may remain a long-term goal 21:07:36 I submitted this blog post as a first introduction to the new plan. I'll be writing a series of more technical posts after the New Year to describe the actual implementation in greater detail. 21:07:52 this will have an interesting impact on CI, probably 21:07:59 But I wanted to get this information out to the general public before the holidays so that people have time to internalize this informatino. 21:08:44 I expect we will need to bring it up a couple of times 21:09:43 I've also sent a text-only version to the devel-announce list just now. 21:10:15 mainly because people have internalized multiple different versions of how modularity is going to do X (or fail to) 21:10:18 There are several big advantages to this new approach, not least of which is that it can be applied to all of Fedora at once. So Server Edition doesn't need to go it alone any more 21:10:24 yes 21:11:01 Anyway, the only action item here is 21:11:31 #info Server SIG members should read this blog entry and come prepared to ask questions at the Jan. 2 meeting 21:11:50 #topic Server Testing 21:11:58 dperpeet: You have the floor 21:12:08 thanks, I will try not to leave scorch marks 21:12:12 (being charred and all) 21:12:34 I'm still working on CI 21:12:49 and my question is, do we want to have any CI specific to Fedora Server as a whole? 21:12:57 a lot of tests are focused on specific packages 21:13:08 but there might be a few overarching, important stories 21:13:13 that we can link to changes in multiple repos 21:13:18 err... packages 21:13:41 so if there are stories / tests like that, I would like to know about them 21:14:05 with the goal that they are run on all dist-git changes of involved packages 21:14:39 dperpeet: So, that's a really good question, but I think it might be best started as a thread on the list. 21:14:48 sure 21:14:51 And then in a future meeting we can winnow it down to the set we want to focus on. 21:14:55 I don't think this has to be discussed here 21:15:02 but I wanted to put it out as food for thought 21:15:28 you can also file things like that under https://pagure.io/fedora-ci/AtomicCi/ 21:15:32 don't let the atomic fool you :) 21:16:02 * sgallagh nods 21:16:28 I guess the question I have is how this would work. Would this be post-compose testing? 21:16:39 And if so, what is different from openqa? 21:16:46 the CI pipeline will update the compose for every change 21:16:58 and we want to move this towards pull request testing 21:17:11 ok 21:17:19 Define a "change" in this context, please 21:17:29 anything that changes dist-git 21:17:37 for a (set of) packages 21:17:57 e.g. rebasing a package, such as sed, to a new version 21:18:01 or adding a patch 21:18:12 or changing the spec file 21:18:13 et cetera 21:19:11 I can certainly see this being a boon to dealing with the FreeIPA stack, if nothing else. 21:19:18 (Since it touches so many pieces) 21:19:37 good point 21:19:42 I'll keep that in mind as one story 21:19:43 Ditto Cockpit, but I kind of assume dperpeet has that covered already 21:20:11 I hope I won't forget Cockpit, heh 21:20:32 the suggestion of the mailing list is good, I'll follow that in the new year 21:23:06 that's it from me on that topic :) 21:23:09 dperpeet: If possible, start the thread beforehand. Give people something to think about while avoiding their least-favorite relatives :) 21:23:53 heh 21:23:58 I will try, but no promises 21:25:08 #topic Open Floor 21:25:08 one of the items I would like to work out before hand is how the package flow works in the CI. The various CI/koschei/etc tools have really picked up the amount of diskspace used for logging 21:25:14 Whoops. 21:25:19 no rpoblem 21:25:23 #topic Server Testing 21:25:40 this is a long term request versus a "oh we need to solve this in this meeting" 21:25:52 #chair smooge 21:25:52 Current chairs: dperpeet sgallagh smooge 21:25:53 yes, but data retention is indeed an important topic 21:26:00 smooge: Mind capturing the request in the minutes? 21:26:12 I have a few thoughts on this 21:26:24 and some experience from Cockpit testing 21:26:38 #info Need to work out network webflow of how CI works so that logging is done in a way which is useful for metrics 21:26:54 #info also so that we can budget disk space needs and such 21:28:08 that was it 21:28:11 :) 21:28:17 OK, anything else on this topic? 21:28:24 in short, existing tools shouldn't be affected much currently 21:28:38 thank you for rewinding over that 21:28:39 but this deserves more attention in the future 21:30:14 OK 21:30:20 #topic Open Floor 21:30:44 #info There will be no meeting on 2017-12-26 21:30:57 Other Open Floor topics? 21:31:10 Happy New Year? 21:31:36 For those on a European calendar 21:32:20 yeah, and a Merry Christmas :) 21:32:22 And to anyone celebrating a holiday over the next couple weeks, enjoy yourselves! 21:32:46 Be kind to one another, for we all have to sober up on Monday 21:33:56 I think we are done here :) 21:35:21 Thanks for coming, folks! 21:35:23 #endmeeting