15:01:45 #startmeeting Infrastructure (2019-04-11) 15:01:45 Meeting started Thu Apr 11 15:01:45 2019 UTC. 15:01:45 This meeting is logged and archived in a public location. 15:01:45 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:45 The meeting name has been set to 'infrastructure_(2019-04-11)' 15:01:45 #meetingname infrastructure 15:01:45 The meeting name has been set to 'infrastructure' 15:01:45 #topic aloha 15:01:45 #chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs 15:01:45 Current chairs: abompard bowlofeggs cverna mizdebsk mkonecny nirik pingou puiterwijk relrod smooge tflink 15:01:51 morning 15:02:00 .hello2 15:02:00 hello o/ 15:02:00 tflink: tflink 'Tim Flink' 15:02:02 .hello2 15:02:02 morning 15:02:03 mizdebsk: mizdebsk 'Mikolaj Izdebski' 15:02:06 hello 15:02:24 .hello zlopez 15:02:24 morning 15:02:25 mkonecny: zlopez 'Michal Konečný' 15:02:52 hello 15:02:54 .hello2 15:02:55 bowlofeggs: bowlofeggs 'Randy Barlow' 15:03:04 * bowlofeggs is in two meetings at once, so limited attention 15:03:55 bowlofeggs: Split personality? 15:04:03 yes, and both of us agree for once 15:04:14 bowlofeggs: just two? :) 15:04:19 * nirik would be in another meeting if the video conferencing tool wasn't such a pile of junk 15:04:21 for once or for one? 15:04:34 #topic New folks introductions 15:04:34 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 15:04:34 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 15:06:28 any new people? 15:07:30 #topic announcements and information 15:07:30 #info Beta Freeze Is Finished. 15:07:30 #info Final Freeze Starts on 2019-04-16 15:07:30 #info Taskotron production upgrade completed on 2019-04-09 15:07:30 #info Another blogpost about release-monitoring.org was published https://communityblog.fedoraproject.org/stories-from-the-amazing-world-of-release-monitoring-org-2/ - mkonecny 15:07:31 #info update reboots happened this week 15:07:33 #info uploads of packages to look-aside cache were broken for some people. 15:07:35 #info git.centos.org/src.fedoraproject.org progressing 15:08:00 abompard: how is the bodhi 3.14.0 release coming along? 15:08:07 mkonecny++ for the blog post, I really enjoy reading these :) 15:08:33 bowlofeggs: still testing in staging, I'll ask for a thing or two after the meeting if you don't mind 15:08:37 cverna: Next one is in preparation phase :-) 15:08:42 abompard: cool, thanks! 15:08:49 #info bodhi-3.14.0 beta in staging 15:09:06 I was going to wait for open floor but I suppose it makes more sense here 15:09:29 #info QA planning to decommission beaker setup in Fedora infra 15:11:55 #topic Oncall 15:11:55 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 15:11:55 #info smooge is on call from 2019-04-04 -> 2019-04-11 15:11:55 #info nirik is on call from 2019-04-11 -> 2019-04-18 15:11:56 #info ????? is on call from 2019-04-18 -> 2019-04-25 15:11:57 #info ????? is on call from 2019-04-25 -> 2019-05-02 15:11:58 #info Summary of last week: (from relrod ) 15:12:09 hopefully we can get bodhi 3.14.0 in prod soonish so we can do the flatpak work this week 15:12:59 nirik: yeah though typically i would recommend not doing a deployment on a thursday or friday 15:13:18 this is a small diff from 3.13 though, so maybe less risky 15:13:35 we could do monday, but that leaves 0 runway before freeze. ;( 15:13:56 nirik, I am not sure we have a runway anyway 15:14:14 which is worse, deploying before a freeze but when you will at least be around to deal with issues, or deploying before a weekend when you won't be around? ☺ 15:14:15 there might be some rocks and an oil slick in it. ;) 15:14:36 are bowlofeggs/abompard around tomorrow, Saturday and Sunday 15:14:45 I think I'm taking too long to test bodhi and if we're time-constrained it may be better for you Randy to test it quickly like you usually do and be done with it 15:14:45 they usually aren't as available on those days 15:14:47 i won't be around on the weekend 15:15:14 it is just us who are usually here :) 15:15:41 abompard: well the goal is to get you to do a deployment and this is going to be one of the easiest ones we'll get, if not the easiest 15:15:46 Hopefully it'll go smoother next time, most of the time was spent setting up my staging testing capabilities anyway 15:15:52 yeah 15:15:56 it's complex 15:15:58 bowlofeggs: yeah I think so too 15:17:22 OK for the last week.. the major oncall items have been the failures for people to upload to src.fedoraproject.org 15:17:38 I don't know if puiterwijk has found the root cause since last night or if it is still an unknown? 15:18:03 I'm looking at it. 15:18:09 (as much as I get time to, anyway) 15:18:17 the suspect is still libcurl? 15:18:19 I have an idea what's going on, but need to check 15:18:21 no 15:18:34 The suspect is Apache stuff at this moment 15:18:55 sneaky apache 15:18:57 :/ 15:19:02 Anyway, I hope I'll get more info later today 15:19:13 ok let us know if we can help any 15:19:24 #topic Monitoring discussion 15:19:24 #info https://nagios.fedoraproject.org/nagios 15:19:24 #info Go over existing out items and fix 15:19:36 Get those thousands of people off my lawn (proxy01), so I can actually get useful debug output? :P 15:19:39 There's a nice new greenwave alert. ;) 15:19:40 15:20:32 notifs-backend01.phx2.fedoraproject.org / Check fedmsg-hub consumers backlog 15:21:23 that one has a ? on it and I am not sure 15:23:24 that means the file doesn't even exist I think 15:23:34 I think it might need restarting? 15:24:08 I will look at it after meeting, but otherwise all the checks looked standard 15:24:14 #topic Tickets discussion 15:24:14 #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 15:24:14 https://pagure.io/fedora-infrastructure/issue/7704 15:24:24 so 7704 was already talked about. 15:25:05 I think relrod isn't around for the geoip one... 15:25:10 7661 is one I am hoping to focus on after th e 18th 15:25:29 it basically needs me to put some packages into EPEL/etc and then us coding to use mmdb 15:25:33 versus geoip 15:26:19 #topic Priorities for next week? 15:26:19 #info please put tickets or projects needing to be focused on here 15:26:32 I will be on travel starting tomorrow til next weeks meeting 15:26:52 could someone else run the meeting? 15:27:09 I can find someone or do it. 15:27:23 we have freeze next week... 15:27:56 ok I 'should' be around for the meeting.. I just won't be able to set it up 15:28:00 Could we freeze the meeting then? 15:28:20 I thaw what you did there 15:28:53 #topic Open Floor 15:29:20 ok so I don't see us having a lot to discuss this week. We did have a lot done in the last 72 hours 15:29:48 the next 48 will be cleaning up after that. :) 15:30:17 do we want to discuss bugzilla sync script ? 15:30:36 or just point folks to nirik's email 15:30:39 cverna: yeah, I need to reply to you and pingou on that... but it sounds good to me to do week after next 15:30:49 or if someone has time before. :) 15:31:17 welcome to others :) the more the merrier :) 15:31:33 It might be better to rewrite it... it's pretty old now... it's from pkgdb1 days I think 15:32:08 there was some thoughts about having this is pagure dist-git directly 15:32:28 having an interface for folks to set this up 15:33:26 well, then that would have to sync that info right? 15:33:35 pingou has worked on a plugins system for pagure, that would let us customize it for dist-git use case 15:33:40 but yeah, we need to see if we can improve anything we can... 15:33:50 ok anything else for this meeting? 15:34:31 so it would default to main admin ->poc and commit/watchers -> cc but you could edit any of that? how could we tell if it was valid? 15:34:59 anyhow, perhaps we could do a short meetup to discuss it soon? 15:35:11 nirik: all good questions we need to think about :) 15:35:23 nirik: yes that would be good 15:35:36 * pingou needs to head out 15:35:47 do we want to schedule a brainstorm before the tiger team starts 15:36:03 or should the brain storm be the first work of the tiger team? 15:36:16 pingou, when would you be available for scheduling? 15:36:21 I would say before 15:36:27 smooge: the week after next 15:36:39 I think before also.... 15:36:48 having it before while being open to adjustment may help letting the idea settle 15:36:55 yeah 15:37:19 in that case, I'll let you folks organize the brain storm :) 15:37:36 I can be around later today, pingou would you have some time later today ? 15:38:02 post 18:30 UTC doable 15:38:05 today is not great for me, tommorrow might be better... or next week after tue 15:38:42 ok so lets find out the best time off this meeting :) 15:38:46 I have to head out, cverna can you text me if we reconvein later? 15:38:47 +1 15:38:58 sure :) 15:39:00 thanks 15:39:03 folks :) 15:39:43 ok with that I think I would close this out 15:39:55 Thank you all for coming. Please make sure to add items for next weeks meeting 15:40:16 #endmeeting