14:00:59 #startmeeting Infrastructure (2018-10-17) 14:00:59 Meeting started Thu Oct 18 14:00:59 2018 UTC. 14:00:59 This meeting is logged and archived in a public location. 14:00:59 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:59 The meeting name has been set to 'infrastructure_(2018-10-17)' 14:00:59 #meetingname infrastructure 14:00:59 #topic aloha 14:00:59 #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny 14:00:59 The meeting name has been set to 'infrastructure' 14:00:59 Current chairs: cverna mkonecny nirik pingou puiterwijk relrod smooge tflink threebean 14:01:24 hi smooge 14:01:37 morning 14:01:47 hello all 14:01:57 morning 14:01:57 morning all 14:02:17 hey folks! 14:02:20 o/ 14:02:29 good morning Europe 14:02:37 s/morning/afternoon/ 14:03:06 #topic New folks introductions 14:03:06 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:03:07 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 14:03:13 any new people this week 14:05:03 #topic announcements and information 14:05:04 #info tflink is on extended PTO 14:05:04 #info Final Freeze has started 2018-10-09 14:05:04 #info version 0.13.2 of release-monitoring.org deployed in production - mkonecny 14:05:17 we are currently in final freeze 14:05:29 any other info for this week? 14:06:10 #topic Oncall 14:06:10 #info relrod is on call from 2018-10-18 -> 2018-10-25 14:06:10 #info smooge is on call from 2018-10-25 -> 2018-11-01 14:06:10 #info ??? is on call from 2018-11-01 -> 2018-11-08 14:06:11 #info Summary of last week: (from smooge ) 14:06:52 ok I am on call and will be turning it over to relrod shortly. I will be on call the week after that also. I need someone to sign up for the 1st and probably the next week 14:07:16 this week had 2 major problems: 14:07:32 1. cogent decided to make a routing loop and took down our secondary data center 14:08:12 2. someone left a default password cloud system up and someone found it. They then decided to use it as a scanner for other bad hosts 14:08:29 that caused network problems and nirik finally found fixed yesterday 14:08:50 I can take the 1st-08th... 14:10:15 ok thanks. 14:10:21 #topic Apprentice Open office minutes 14:10:22 #info A time where apprentices may ask for help or look at problems. 14:10:31 Any questions from apprentices this week? 14:11:11 * nirik thinks it's pretty quiet this morning... almost... too quiet. ;) 14:11:37 ok.. well I think we are at 14:11:40 #topic Open Floor 14:11:56 I don't think this is the record fastest infrastructure meeting but close to it 14:12:04 I have a small troll considering what is going on on devel list :) 14:12:15 no 14:12:24 should we have a infra category https://discussion.fedoraproject.org/ 14:12:35 smooge: ok :) 14:12:39 well, I am kinda doing 'wait and see' about that... 14:12:40 we could but I am not going to look at it 14:13:02 I think if we move too many things to it before we have decided anything we just split our attention. 14:13:36 yes wait and see sounds like a good position 14:13:53 I was looking at it's rss feeds, and they are... not ideal. ;( 14:15:08 I have one ticket I want to ask about 14:15:15 https://pagure.io/fedora-infrastructure/issue/7313 14:15:16 mkonecny, okie dokie 14:15:40 yeah, I don't know whats going on there. ;( 14:15:52 Another user reported this today, this time the-new-hotness didn't received fedmsg 14:16:19 is it worth waiting for fedora-messaging ? 14:16:35 it's only 'sometimes' right? sometimes it works? 14:16:38 jcline is already working on PR for Anitya 14:16:50 * jcline looks up 14:16:53 (the worst kind of problem) 14:17:01 nirik: sometimes it works 14:17:13 I see messages in fedmsg channel 14:17:37 hi jcline :-) 14:17:43 do the ones hotness didn't see show up there in fedmsg channel? 14:18:06 nirik: You mean in datagrepper? 14:18:57 either in datagrepper or in #fedora-fedmsg.... 14:19:07 ie, that would show they were emited, but hotness didn't get them 14:19:27 Didn't checked 14:20:04 But according to one user, who reported this they didn't 14:21:30 could we add some debugging to log when it emits a message and to what? 14:21:31 Hmm. Well, some messages are making it, so I'd say it's probably the huge chain of unreliable sockets we've got going. Plus yeah, I'm nearly done with the anitya conversion 14:22:27 I think it sounds fair to wait for fedora-messaging and see if that improve things 14:22:28 nirik: I can try to get fedmsg-tail running on pod and compare this to datagrepper 14:22:54 nirik, sadly it looks like there's no log statement on publish in fedmsg 14:23:04 bummer 14:23:55 zmq might log it 14:23:55 yeah, fedmsg-tail might be good... 14:24:07 but yeah, if we can move it over that might be best 14:24:28 But it will take long before all listening clients will switch to fedora-messaging, or is fedora-messaging compatible with fedmsg? 14:25:11 mkonecny, there are bridges so anything on fedmsg makes it to the broker and anything on the broker goes to fedmsg 14:25:30 So the-new-hotness could change now, even though anitya hasn't yet 14:25:42 Although we need to get the broker deployed in production 14:26:12 ok, so if Anitya will emit only fedora-messaging messages even the fedmsg consumers will get it? 14:26:32 Yep 14:26:36 Super 14:26:46 ok anything else? 14:27:30 #endmeeting