20:00:14 #startmeeting Server SIG Weekly Meeting (2017-08-15) 20:00:14 #meetingname serversig 20:00:14 #chair nirik sgallagh mhayden dperpeet smooge jds2001 vvaldez adamw mjwolf 20:00:14 #topic Roll Call 20:00:15 Meeting started Tue Aug 15 20:00:14 2017 UTC. The chair is sgallagh. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:15 The meeting name has been set to 'server_sig_weekly_meeting_(2017-08-15)' 20:00:15 The meeting name has been set to 'serversig' 20:00:15 Current chairs: adamw dperpeet jds2001 mhayden mjwolf nirik sgallagh smooge vvaldez 20:00:22 .hello sgallagh 20:00:24 sgallagh: sgallagh 'Stephen Gallagher' 20:00:24 .hello mhayden 20:00:25 .hello adamwill 20:00:26 mhayden: mhayden 'Major Hayden' 20:00:26 .hello kevin 20:00:29 adamw: adamwill 'Adam Williamson' 20:00:32 but unless someone pings me specifically i'm not likely to be watching, sorry 20:00:32 nirik: kevin 'Kevin Fenzi' 20:00:35 too much stuff exploding 20:00:42 adamw: Uh oh 20:02:13 .hello mjwolf 20:02:13 mjwolf: mjwolf 'Michael Wolf' 20:02:28 .hello2 20:02:29 langdon: langdon 'Langdon White' 20:02:38 * langdon was looking for the mtg in #f-m 20:03:16 Wait, when did .hello2 become a thing? 20:03:43 anyway... 20:03:49 #topic Agenda 20:04:09 We have one proposed item for the agenda today: langdon wants to discuss Modularity plans for Fedora 27 20:04:10 sgallagh, don't know.. but it works.. 20:04:17 * linuxmodder here 20:04:19 yeah.. such as it is.. 20:04:30 I'm sure this will be a very short and precise meeting /s 20:05:07 Do we have other pressing topics to discuss today? 20:05:33 Alright, let's get started. 20:05:43 #topic Magical Modularity Tour 20:05:47 ha 20:05:48 langdon: ? 20:06:01 ok.. so basically, we just wanted to confirm: https://github.com/fedora-modularity/f27-content-tracking 20:06:04 with y'all 20:06:31 i also realized it would be good to track all the other work going on as issues on that repo 20:06:57 but.. i only just thought of that 20:07:53 as sgallagh knows.. there is also significantly more in the platform module than there used to be.. so some of your items may be covered there 20:07:56 e.g. less 20:08:04 comments, thoughts? 20:08:15 * nirik looks at link 20:08:19 You're saying that less is more? 20:08:21 ;-) 20:08:48 exactly 20:08:52 and pine is not elm 20:08:53 no none is more 20:09:31 Kidding aside, I think the section on Server WG requirements looks accurate from a "let's not regress" perspective 20:09:43 yeah 20:09:48 list looks OK to me, at least as regards critical content. 20:10:19 just to be clear.. you also don't have to be 100% right now.. just this is what we are working towards.. 20:10:33 and we would love help.. but, we can't really tell you how to help til next week :/ 20:12:14 langdon: For context, you are referring to the document you just submitted to FESCo? 20:12:48 sgallagh, correct.. and needing adam's (poorly named IMO) dependency report dealio to be done 20:13:34 For the minutes: 20:13:35 sgallagh, unless you know how people could help now? or have ideas how they could? 20:13:47 #link https://github.com/fedora-modularity/f27-content-tracking 20:13:48 #link https://fedoraproject.org/wiki/Module:Review_Process 20:14:30 langdon: The set of people currently serving on the Server SIG would be a good set of people to review those docs 20:14:45 #link https://github.com/fedora-modularity/dependency-report 20:15:09 s/SIG/WG/ but thats nitpicking. ;) 20:15:15 ahh yes.. please do.. 20:16:01 file issues that you can't just "fix" here: https://pagure.io/modularity/issues 20:16:22 wiki isn't very conducive to having issues/comments (imo) 20:16:25 With my FESCo cap on, anyone who could provide feedback on the Module Review Process this week before FESCo discusses it would be greatly appreciated 20:17:41 it is basically a clone of the container one (thanks maxamillion :) ) .. which, i think, was a clone of the rpm one.. 20:17:50 Also (at the risk of self-promotion), please consult https://sgallagh.wordpress.com/2017/05/30/sausage-factory-an-introduction-to-building-modules-in-fedora/ for basic information on creating modules. 20:17:56 Followed by https://sgallagh.wordpress.com/2017/06/30/sausage-factory-advanced-module-building-in-fedora/ 20:18:21 unfortunately, reading neither of those ACTUALLY results in getting any sausage :/ 20:18:44 the sausage is a lie! 20:18:46 Anyone who has a vested interest in seeing the Server modules get delivered is advised to join #fedora-modularity and assist us 20:19:41 Also, if you happen to have access to atypical hardware architectures, it wouldn't hurt to get some testing of both builds and actual binaries on them 20:19:48 +1 .. we are way behind 20:19:48 * sgallagh looks directly at mjwolf 20:19:54 ha 20:20:31 mjwolf: I will take a look 20:20:53 sgallagh: we will be able to test on ppc in openQA fairly soon (it'd probably all be deployed already if i didn't have five other goddamn things going wrong with openqa to worry about) 20:21:14 adamw: ack and thank you 20:21:17 adamw, otherwise, you would get bored.. 20:21:43 I'm actually terrified of the day adamw is bored 20:21:51 sgallagh, right?!!?? 20:22:16 langdon: Do you want to call out any specific actions people could volunteer to take? 20:22:21 (Or be volunteered FOR) 20:22:25 * adamw dearly wishes to be bored right now 20:22:42 ha.. /me thinks 20:23:45 anything anyone can contribute to the infra work would definitely help.. bodhi changes, arbitrary branching, etc.. nirik, I think you would know if there is anything anyone could "do" that is low hanging fruit on the factory 2 work. 20:24:14 not entirely sure... this last week has been a blur. Lots of little stuff to fix from pagure over dist git... 20:24:30 but I think we are finally starting to catch up. Hopefully before the next truck hits us. ;) 20:25:15 here's wishing... 20:25:18 nirik: Is that truck the branch? 20:25:29 ralph is out today who would know best 20:25:35 ... probably should have made a joke about swinging a branch at your head 20:25:36 naw, that truck is here now. ;) 20:26:43 but as far as "actual" modules.. dependency help is very useful.. if you know any of the items on the list well, let's #info it and let adam know so he has another channel for questions 20:27:05 the branch, the flock, the mass rebuild because we found something broke in gcc, the rebuild of the rebuild because... 20:28:22 #info sgallagh is a resource for SSSD, FreeIPA and Cockpit dependencies 20:28:26 * langdon is finding flock very inconvenient this year.. if mattdm isn't willing to move f27.. maybe we could just move flock 20:29:12 langdon: Don't even joke about that 20:29:25 I was trying to get it moved to devconf 20:29:29 ha 20:29:31 You would have a riot on your hands 20:29:37 nothing like brno in feb 20:30:39 so.. any other #info peeps? 20:30:48 Well, the advantage of Flock this year is that we have time dedicated to hacking on things while everyone is in one place right before the big Freeze 20:31:18 #action asamalik to review the meeting minutes for people who can act as experts on the packages he is working with 20:31:19 Since historically, everything lands 48-to-negative-twelve hours before Freeze, we are in good shape :) 20:31:36 * langdon not #chair.. but the fedbot liked it... am i? 20:32:02 #action asamalik to review the meeting minutes for people who can act as experts on the packages he is working with 20:32:06 there 20:32:26 cool 20:32:31 Do we have anyone around with considerable experience with PostgreSQL, NetworkManager or udisks2? 20:32:32 * langdon will forget to tell him 20:32:44 langdon: Oh, sidebar: storaged merged back to udisks2 20:32:50 ha 20:33:06 yeah, I expect a new name a year from them now. ;) 20:33:18 udisks.next FTW 20:33:32 * nirik has used all those things, but wouldn't say he is any kind of expert on them 20:33:58 nirik: Personally, I liked the storaged name better, as it was more accurate. Ah well 20:34:06 udisks -> storaged -> udisks2 -> storaged2 -> udisks3 :) 20:34:30 nirik: The actual history of that was more complicated still :) 20:34:35 yes, I know 20:35:31 nirik, mild sidebar, do you know the fedora-change that is the bodhi changes for modules? 20:36:19 i may have found it "bodhi non-rpm artifacts" 20:36:20 https://fedoraproject.org/wiki/Changes/BodhiNonRPMArtifacts 20:36:24 thanks! 20:36:57 langdon: Oh, that's another concern 20:37:22 Last I heard, the work was on the way to make Bodhi capable of non-RPM artifacts, but not specifically prepared for module artifacts. 20:37:23 Any comment? 20:37:42 Because I feel like that's a blocker to a supportable release of Server 20:37:51 err, Boltron 20:38:02 sgallagh, yeah.. i think i was in that "thread" .. was supposed to follow up with ralph today .. but couldn't 20:38:05 I was thinking we would call the new storage.. StorageTech 20:38:33 smooge: "Where'dIPutThatAgain" 20:38:45 "InfiniteMonkeys" 20:39:05 smooge: I have a story about that, remind me to tell you at Flock :) 20:39:52 "zipdrive100" 20:40:01 langdon: Well, do we have any idea how likely it is that this will get sorted before Beta Freeze? 20:40:24 Because as of right now, I'd call our status "orange" (yellow tinged with red) over this 20:40:24 sgallagh, which? the bodhi stuff? 20:40:27 yes 20:40:53 we don't actually need it by beta freeze, right? we don't need it til ga+1-second? 20:41:47 but.. i would say we are kinda orange already 20:41:54 rather.. for lots of reasons 20:42:15 langdon: Well, we need it by bodhi activation point 20:42:57 sgallagh, sorry.. i am not sure what you mean by "activation point" 20:42:59 Which is actually *before* Beta Freeze :-| 20:43:14 #link https://fedoraproject.org/wiki/Releases/27/Schedule 20:43:36 langdon: There's a point in the dev cycle where we stop inheriting from Koji automatically and all builds need to go through bodhi to end up in a repo 20:44:05 Now, it's possible that this is not true for the MBS pipeline, but I don't have that information 20:44:09 sgallagh, ohh.. right.. i see.. i don't think i knew what that "step" was called 20:44:11 And we need to 20:44:26 That date is currently two weeks from today 20:44:30 (just prior to Flock) 20:44:41 right 20:46:00 sgallagh, langdon: bodhi is ready for modules with one exception - it needs a way to "mash" them (for lack of a better term) 20:46:26 sgallagh, langdon: there's an open pull request that needs more work to do that from mcurlej - afaik he's working on it and considers it high priority 20:46:42 bowlofeggs, ahh right 20:46:45 https://github.com/fedora-infra/bodhi/pull/1697 20:47:03 i knew there was a reason it wasn't keeping me up at night 20:47:24 it should be possible to create module updates in bodhi already 20:47:32 you just can't "ship" them when they get stable yet 20:47:52 ok, that's a little less frightening 20:47:59 bowlofeggs: Do we have an ETA on that? 20:48:04 very little integration testing has been done though, because koji in fedora stg doesn't have modules in it yet 20:48:17 bowlofeggs: yes it does 20:48:22 sgallagh: i've not been told an ETA - i'd recommend reaching out to the factory 2.0 team to find out 20:48:26 bowlofeggs: just may not have any built 20:48:27 I thought they tested it in stg a bunch 20:48:32 * sgallagh reaches 20:48:44 afaik they tested extensively in stg 20:48:45 dgilmore: oh neat, in that case, we should try to create a module update in bodhi stg 20:50:20 bowlofeggs, any reason you can think of that i can't tag you in pagure either by your nic or last name? 20:50:44 langdon: no, i should be @bowlofeggs 20:50:52 (that's my FAS name) 20:50:56 weird.. ok.. ill try again 20:51:38 yeah.. works fine.. just no popup :/ 20:52:36 OK, do we have anything further to discuss in this group today? 20:52:44 We're getting close to the top of the hour 20:55:10 I'll take that as a no 20:55:23 #topic Open Floor 20:55:33 I'll leave the floor open for a couple minutes, then close the meeting. 20:57:52 Thank you for coming. 20:57:52 #endmeeting