14:00:19 #startmeeting Infrastructure (2018-09-06) 14:00:20 Meeting started Thu Sep 6 14:00:19 2018 UTC. 14:00:20 This meeting is logged and archived in a public location. 14:00:20 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:20 The meeting name has been set to 'infrastructure_(2018-09-06)' 14:00:20 #meetingname infrastructure 14:00:20 The meeting name has been set to 'infrastructure' 14:00:20 #topic aloha 14:00:20 #chair nirik pingou puiterwijk relrod smooge tflink threebean 14:00:20 Current chairs: nirik pingou puiterwijk relrod smooge tflink threebean 14:00:25 .hello2 clime 14:00:26 morning 14:00:26 clime: clime 'clime' 14:00:31 hi 14:00:43 Morning 14:00:44 .hello2 14:00:45 bcotton: bcotton 'Ben Cotton' 14:00:48 morning 14:00:55 mornng all 14:01:07 .hello2 14:01:09 puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' 14:01:37 morning 14:02:49 Hi all 14:02:55 #topic New folks introductions 14:02:55 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:03:10 hello any new people here this week? 14:03:43 Me, kind of. 14:03:56 Been poking around for the last couple of weeks but this is the first time I've been on time to this meeting lol 14:04:32 .hello2 14:04:33 I'm a dba/dev who would love to get involved with Fedora 14:04:33 creaked: creaked 'Will Chellman' 14:05:11 welcome. 14:05:19 .hello2 14:05:20 bowlofeggs: bowlofeggs 'Randy Barlow' 14:05:25 welcome wilsonj 14:05:34 hi 14:06:11 hello everyone 14:06:45 .hello2 14:06:46 abompard: abompard 'Aurelien Bompard' 14:06:59 I've looked at the "easy-fix" tickets and thought this one sounded neat: https://pagure.io/fedora-infrastructure/issue/5316 14:07:05 wilsonj, you may want to hang out on #fedora-apps as most of the applications which use a DB are developed there. You can also enjoy our weekly db lockup on fas 14:07:49 cool. we will discuss that ticket later this meeting 14:07:58 #topic announcements and information 14:07:58 #info tflink is on extended PTO 14:07:58 #info Beta Freeze is in effect. All changes to frozen systems in Infrastructure will require +1 14:07:58 #info Bodhi 3.10.0 beta in staging https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html 14:07:58 #info odd network problem on arm network needing to be tracked down. 14:08:03 What is fas? I'm not sure what yu mean by "weekly db lockup on fas" 14:08:28 #info stats and logging now available in staging openshift. 14:09:04 Fedora Accounts System. We have a saturday night short outage because the db gets into a state where it is trying to compress things while it is deleting sessions while it is ... we aren't exactly sure :) 14:09:25 fun times, fun times 14:09:39 Nice lol 14:09:48 #info bugzilla upgrade this friday, hopefully we are ready 14:10:21 So is that a scheduled meeting? 14:10:33 nirik: didn't we get an email that it's postponed? 14:11:07 abompard: I didn't? but it's 7am for me, I just woke up and headed to this meeting. ;) 14:11:13 yeah, I think it was postponed 14:11:21 and the banner on bz doesn't show a date anymore 14:11:33 ah bummer. 14:11:37 ok, thanks. 14:11:38 Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed. 14:11:53 #undo 14:11:53 Removing item from minutes: INFO by nirik at 14:09:48 : bugzilla upgrade this friday, hopefully we are ready 14:11:57 hooray? 14:11:58 it's been such a long time waiting for this, oh well... 14:12:00 #info Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed. 14:12:28 #topic Oncall 14:12:28 #info Nirik is on call from 2018-08-30->2018-09-06 14:12:28 #info Relrod is on call from 2018-09-06->2018-09-13 14:12:28 #info Smooge is on call from 2018-09-13->2018-09-20 14:12:29 #info ??? is on call from 2018-09-20->2018-09-27 14:12:29 #info Summary of last week: (from Nirik) 14:13:02 :( 14:13:10 nothing too big to note... just normal oncall pings and such. 14:15:21 OK I took the time frame of next week because no one had gotten it. Who wants it or the 09-20 -> 09-27 timeframe? 14:15:34 I can take it 14:16:14 ok will put you down as tentative in case bowlofeggs says 'oh I would rather do that than bear wrestling' 14:16:59 #topic Tickets discussion 14:16:59 #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 14:17:24 I marked a few for meeting... 14:17:36 .ticket 7226 14:17:37 smooge: Issue #7226: DNS for fedoraproject.org email alias forwarding - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/7226 14:18:02 there was a bit more discussion in this one... 14:18:49 I'm waiting for more info from the reporter, so I guess we can just move on, unless anyone has thoughts... 14:19:04 drop @fedoraproject.org email aliases? 14:19:38 * smooge takes the kerosene out and the matches 14:20:30 heh. well, we could... but there are at least some people who really like/use them... 14:21:03 move them to @fedorapeople.org and let the reporter run email ? 14:21:07 Isn't this used as admin mail in some of the Fedora apps? 14:21:21 They're also littered throughout people's spec file %changelog sections. A lot of immutable history 14:21:40 some users also use them in bugzilla... 14:21:48 hello 14:21:50 well foo 14:21:58 ok.. well the asbestos suit was hot anyway 14:22:37 .ticket 5316 14:22:39 smooge: Issue #5316: New package review tickets page - RFE for filter - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/5316 14:23:19 wilsonj, I think you were interested in this one? 14:23:25 Yes :) 14:24:11 * nirik happy to try and give some background and pointers here. 14:24:12 It looks like there was a patch proposed in the comments on the ticket. Was that enough, or do we still need to work on this ticket? 14:24:41 smooge: haha @ bear wrastling 14:24:45 nirik, can you give some background first 14:24:47 huh, I missed that there was a patch. ;( 14:25:16 well, this is for: https://fedoraproject.org/PackageReviewStatus/ 14:25:34 basically a script runs and scrapes bugzilla and then provides a fast way to see those tickets. 14:25:52 I don't know if the patch works, we should test it and see. 14:26:43 basically this was about adding another search field/query 14:26:55 or filtering the existing ones. 14:27:14 https://pagure.io/fedora-infrastructure/issue/5315 is a very similar ticket 14:28:46 so how would wilsonj work on this? apply the patch to the code and see if it still applies? Then have us push it to stg? 14:28:49 As for the first ticket, it looks like there is a field to filter by package ("Enter a source package name to search for any relevant review tickets"), so that might be done? 14:29:29 wilsonj: they wanted a way to filter the 'NEW' search by another criteria 14:29:46 yeah, test locally, if it applies/looks ok, we can apply to staging then prod 14:31:15 Cool, I can do that 14:32:21 awesome. 14:32:46 cool 14:33:00 So if the patch works and we push it, that'll be in atrevino's name right? I'm not sure how everything works here, but I wouldn't want to start out by stealing the credit lol 14:33:22 yeah, definitely could make sure they get the credit for the patch. 14:34:08 ok that is it for tickets we know about.. there are 94 other tickets which people can look at and see if they should be discussed at next weeks meeting. Please choose a random one and see if it is something which could be discussed. 14:34:20 #topic Apprentice Open office minutes 14:34:20 #info A time where apprentices may ask for help or look at problems. 14:34:28 which bridges well into this part. 14:36:12 are there any other questions or ideas people want to ask about? 14:36:37 relrod: were there any of your thoughts on on-boarding that we wanted to try out ? 14:37:11 hm 14:37:17 Circling back to the Saturday outages: Is there anywhere I can go to shadow the process? 14:38:59 nirik: Well once we have *some* kind of newcloud solution we can start playing with some of my ideas regarding that. We could also start doing some videos/screencasts for teaching things, people seemeed to like that idea... I guess that's something we can discuss - where to put those. 14:39:00 I know getting db rights isn't an immediate privilege, but being able to see what's going on would be cool 14:39:15 well, we have a cron that runs every 10min to clean out old sessions. Normally that works fine, but for some reason on saturday night it gets messed up and we have tons of things locking the session table waiting to delete. But I am not sure why. 14:39:52 I know for the Flock videos they use youtube, are we okay with having a youtube channel for tutorial/screencast videos? Or do poeple have issues with using that? 14:39:59 relrod: cool...and what tools to use for them... 14:40:20 well, I would prefer to avoid that in favor of something free, but perhaps it's just me 14:40:27 peertube? 14:40:44 * nirik hasn't heard of that one 14:40:52 same 14:41:04 https://joinpeertube.org/en/ 14:41:31 the marketing team is trying to push to have content on youtube 14:41:36 whole bunch of new apps like that offering federated alternatives 14:41:39 will look. But if we are just doing videos/screencasts we could just stick them up at infrastructure.fedoraproject.org no? 14:42:14 since the Fedora channel is pretty empty compared to other distributions 14:43:48 * nirik has no idea where the cool place is for tutorials type stuff these days. I personally don't like videos, but likely thats just me. 14:44:48 I had positive feedback from that idea. I think it appeals to visual learners to have an actual demonstration of what is happening and an explanation to go with it 14:45:15 nirik, it is just us being old.. in our day they threw us in a pit with a PDP-11 and made us fight it out to find out who was a sysadmin.. people don't like that anymore 14:45:17 won't know the response unless you try 14:45:32 ha 14:46:01 ok with that 14:46:05 #topic open flood 14:46:16 * aikidouke took apart a PDP-11 and storage a couple years ago for someone 14:46:19 what sort of thing would people like to see as a screencast? we could try and make a sample one and see how popular it is? 14:46:25 smooge: I'd be okay with that. But if you're doing that, throw actual V7 on it, just so I can really get the learning experience. ;) 14:46:48 I'm interested in tools and workflow 14:47:04 I mostly use vim with some plugins and tilix 14:47:34 but following one playbook to the next and keeping a mental model in my head of what is happening is tough 14:47:52 does anyone do anything significantly different? 14:48:38 I can try do one about OSBS 14:48:42 not really. Could try and capture a 'apply patch and run playbook' type run next time that happens... not sure how interesting it will be. ;) 14:48:53 cverna: I would personally find that useful 14:49:05 Showing the playbooks, how things works :) 14:49:10 I've looked at tools that map inventory and such, but that's not really what I'm going for.. 14:49:22 +1 on cverna idea 14:49:25 cverna: sounds nice. :) 14:49:45 ok I add that on my task list :) 14:49:56 cverna++ 14:50:47 So related to nirik's question: Who do we want these to target? I kind of left that open at Flock, but I think my original idea was to target the whole range of contributors. i.e. we can do one showing how DNS updates work, so that in the future if a new contributor gets DNS access they can quickly see how we take proxies out during an outage. And at the same time, we could have one showing 14:50:47 "here's how you submit your first Ansible patch to us for review" 14:50:53 but that scope might be too big. 14:51:26 I'm hoping we are close to having PR's for ansible, which would help a lot. 14:51:38 +100 14:51:43 then it's just the PR workflow... which would be another nice one 14:51:53 yeah PR for ansible :) 14:52:50 ansible PR for president 14:52:58 I would like to see how to deploy an application to our openshift 14:53:24 yeah, that would be another good one. 14:53:27 what needs to be done, playbooks, troubleshooting etc .. 14:53:47 or a complete RFR (long video) 14:53:51 * relrod nods 14:54:09 that could be multiple videos like part1, part2 etc 14:54:15 yep 14:54:17 I'm not sure a video of that would be a good idea, given that it's still in flux. But I can give an IRC "classroom" on it at some point.. 14:54:26 ("that" being "fedora infra openshift") 14:54:49 FYI, my next plan is to enable multitennant networking in our staging openshift. 14:55:00 ok we are coming to the end of the hour so I would like to move this to the mailing list 14:55:22 relrod, could you send out an email to the list going over the items? 14:55:34 sure 14:55:42 thanks 14:56:13 OK thank you all for coming this week. I will see you same Bat Time, same Bat Channel 14:56:16 #endmeeting