14:00:17 #startmeeting Infrastructure (2018-06-14) 14:00:17 Meeting started Thu Jun 14 14:00:17 2018 UTC. 14:00:17 This meeting is logged and archived in a public location. 14:00:17 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:17 The meeting name has been set to 'infrastructure_(2018-06-14)' 14:00:18 #meetingname infrastructure 14:00:18 The meeting name has been set to 'infrastructure' 14:00:18 #topic aloha 14:00:18 #chair nirik pingou puiterwijk relrod smooge tflink threebean 14:00:18 Current chairs: nirik pingou puiterwijk relrod smooge tflink threebean 14:00:24 Hello all 14:00:26 Hello everyone 14:00:31 .hello2 14:00:32 creaked: creaked 'Will Chellman' 14:00:36 .hello2 14:00:36 .hello psabata 14:00:37 tflink: tflink 'Tim Flink' 14:00:40 contyk: psabata 'Petr Šabata' 14:00:45 morning 14:00:55 * threebean has to miss today. cheers! 14:00:57 * pingou here 14:01:08 o/ folks 14:01:14 .hello2 14:01:17 puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' 14:01:31 .hello2 14:01:32 bowlofeggs: bowlofeggs 'Randy Barlow' 14:01:32 * vgolwala says "hello everyone!" 14:02:31 #topic New folks introductions 14:02:32 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:02:40 hello any new people this week? 14:02:45 .hello bex 14:02:45 bexelbie: bex 'Brian (bex) Exelbierd' 14:03:30 .hello aikidouke 14:03:31 aikidouke: aikidouke 'None' 14:04:19 ok then next up 14:04:22 #topic announcements and information 14:04:22 #info relrod PTO 9 Jun - 19 Jun # this is ongoing. 14:04:22 #info smooge PTO 15 Jun -> 18 Jun 14:04:22 #info Office hours relaunch 19 Jun 18:00 to 19:00 UTC 14:05:06 anything else to announce or cover? 14:05:30 nirik, do you have an idea when our next update/reboot cycle will be? mid july? 14:05:37 * cverna waves 14:05:56 well, I was just thinking about that the other day... 14:06:09 * bexelbie has an item for open floor/app time 14:06:19 some more firmware just came out the other day 14:07:00 yeah I saw that. 14:07:13 The next big schedule milestone is mass rebuild in july. 14:07:24 so, we might want to do one next week or the week after 14:07:32 so the week before that? 14:07:42 or yeah, we could do first week in july too... 14:08:01 cverna: you need something in it? 14:09:15 * mboddu is here 14:09:28 so I would say that either the first week or the week around the 24th look good at the moment 14:09:50 yeah, lets decide next week or so... 14:10:12 I expect the weeks after rebuild is going to be the "why did you turn off the builders??!!?! why do you hate me when I need this done to deal with FTBFS and Flock" 14:10:41 oooh there is a perfect time for reboots 14:10:43 nirik: in the update/reboot 14:10:45 ? 14:11:07 cverna: well, you asked when it was... just curious? or you had some item you needed to reboot? 14:11:08 cverna, I think nirik was asking if your wave was a "I would like to add something" or a "hello all" 14:11:25 ah misread 14:11:26 nevermind. 14:11:30 ha I was saying hello :) 14:11:35 * nirik goes back to coffee. 14:11:40 no pb 14:12:02 #topic Oncall 14:12:02 #info Nirik is on call from 2018-06-07->2018-06-19 14:12:02 #info Relrod is on call from 2018-06-20->2018-06-26 14:12:02 #info Smooge is on call from 2018-06-27->2018-07-05 14:12:03 #info ?? is on call from 2018-07-06->2018-07-12 14:12:34 So we will be rotating another person in from the 6th to the 12. We can decide it next meeting when everyone is back 14:12:45 sure. 14:12:51 ooh! a regex is on call! 14:12:53 smooge: bowlofeggs also was willing to take oncall :) 14:13:04 He is on PTO then I think 14:13:12 Right 14:13:17 Just saying in general 14:13:19 so its your time 14:13:24 yeah i'm willing to start taking it when i get back 14:13:35 so, mid julyish 14:13:44 I could take up an option on that week, but would prefer confirming that next week 14:14:02 no need to decide yet 14:14:06 ye 14:14:09 eyp 14:14:15 dead god fingers.. type 14:14:54 dead god fingers sounds like a metallica album 14:15:02 sounds awesome 14:15:14 may change my nick now 14:15:15 nirik the next topic is about flock.. i didn't remember if that was a new one or last week 14:15:31 oh oops. no, that was last week... didn't remove it 14:15:47 #topic Tickets discussion 14:15:47 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 14:15:48 Well, still good to tell people: submit talks to Flock! 14:16:01 * puiterwijk is sure bexelbie agrees 14:16:13 * bexelbie agrees 14:16:31 .ticket 5136 14:16:33 smooge: Issue #5136: Add the BackTick extention to Fedora Wiki, - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/5136 14:17:36 so this needs: a) to know if we still want it, b) someone to package it up and get it in fedora c) profit 14:18:00 but it was wanted still 2 months ago at least 14:19:14 anyone interested in packaging it up? :) 14:19:30 the submitter? :) 14:20:35 perhaps, unclear 14:20:44 Im not a proven (or even unproven packager) but I could add that to my todo list 14:20:55 are you a packager? 14:20:59 no 14:21:11 sorry my coffee ran out 2 minutes ago so was having a hard time parsing 14:21:20 I would need to go through the whole process and get sponsored, etc 14:21:23 got it 14:21:28 :) 14:21:39 it should be a pretty easy package. Just look at one of the other mediawiki extension packages and copy it. ;) 14:21:45 ok that sounds like a good starting package as most of the work is going to be the package 14:21:52 spec file 14:21:56 thanks nirik :) that was my thinking 14:21:58 yeah. 14:22:13 ok - will add to my list 14:22:14 happy to review/help out with it. 14:22:26 aikidouke: i can sponsor you :) 14:22:31 or nirik can :) 14:22:34 much appreciated sirs! 14:22:47 nirik++ 14:22:47 aikidouke: Karma for kevin changed to 20 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:22:53 Or I can. No shortage of sponsors :) 14:22:54 bowlofeggs++ 14:22:54 aikidouke: Karma for bowlofeggs changed to 15 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:23:05 that said, I want to be clear, that the package may not get used.. we would need to enable it and then see if it broke the wiki because people are expecting ` to do something else 14:23:05 :) thanks puiterwijk! 14:23:09 or I can 14:23:14 quite a few of us :) 14:23:20 :) thanks pingou 14:23:29 indeed. Thanks everyone. :) 14:23:36 next bug? 14:23:39 @smooge - I have no expections either way, someone will use it or not 14:23:46 s/bug/issue/ 14:24:02 .ticket 5125 14:24:04 smooge: Issue #5125: make changes such that qa.fedoraproject.org is a valid MX record - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/5125 14:24:14 bwa? 14:24:50 yeah, I am not sure I understand this one... but can we do it and get it off our list? ;) 14:24:53 that can be closed 14:24:56 man I say a lot of things years ago 14:25:14 we aren't using phab anymore 14:25:24 easy peasy then. :) 14:25:30 nice and easy 14:26:24 #topic: FBOM to loopabull? 14:26:42 * nirik is liking reviewing the old tickets in meeting. Its helping moving them forward. 14:26:50 yep 14:26:54 FBOM? 14:27:16 it doesn't say who put this in.. I am guessing pingou from the text color 14:27:19 the Flag Build-o-matic :) 14:27:30 ahhhh. ok 14:27:36 so this is a left over from tests/test_pagure_flask_ui_app_index.py 14:27:40 https://pagure.io/fedora-infrastructure/issue/6717 14:27:49 almost the right paste at the first attempt 14:28:00 and https://pagure.io/fedora-infrastructure/issue/7033 brings back the need for it 14:28:12 at the hackfest we discussed moving fbom to be loopabull-based 14:28:24 which is fine w/ me 14:28:33 or we can make it something on openshift 14:28:36 or... 14:28:41 any preferred option? 14:28:55 loopabull sounds fine to me... any problems/blockers there? 14:29:14 last time I look it seemed there was basically nothing using it atm 14:29:27 there's a 'demo' task that doesn't do anything 14:29:37 the ansible playbook would basically install a python script and run it 14:29:44 well, listens for something then echos it 14:29:46 and I need to figure out secrets with it 14:30:32 * nirik nods 14:30:53 the current repo loopabull is pointed to could also be changed 14:31:10 do we want an infra-loopabull specific repo, on pagure or elsewhere? 14:32:10 it's releng specific now? 14:32:31 it contains a number of things that aren't related to loopabull 14:33:12 ok, infra-loopabull or fedora-loopabull-data or something is fine with me. 14:34:13 cool, thanks 14:34:20 fedora-infra-data-loopabull 14:34:29 I'll try to prepare things and send a recap to the list before I change anything 14:34:30 fidl? 14:34:38 rome burns 14:34:44 lol 14:34:50 while ansible fidls 14:35:31 thank you for setting up the joke 14:35:38 eof for me 14:35:45 #topic Apprentice Open office minutes 14:35:45 #info A time where apprentices may ask for help or look at problems. 14:35:58 hello any apprentice questions towards tickets? 14:36:07 .ticket 5290 14:36:10 aikidouke: Issue #5290: Generate infrastructure map - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/5290 14:36:36 Sooo...the gist of this is, the requester wants to be better able to drill down into the nagios map 14:37:24 there are a couple things we can do to solve this without creating a new app, the one idea I had was to create links to maps for hostgroups 14:37:50 but in the 30 seconds of grepping i did, it looks like our nagios has 7 hostgroups? 14:38:07 There's a number... and some of them are very large 14:38:24 would it be here> roles/nagios_server/templates/nagios/hostgroups ? 14:38:59 it's generated from ansible inventory... but yeah, the templates are there 14:39:17 oh...RIGHT! cuz variables... 14:39:43 anyway - my question is, do the hostgroups we have now make sense to generate custom status maps? 14:39:59 or is that a $BADIDEA? 14:40:39 or does that require noodling and discussion later? 14:40:41 so the hostgroups are mainly defined from being whatever groups in ansible we have.. so some of them make a good idea and some would be bad 14:41:11 * aikidouke nods 14:41:23 I would look at doing it with a variable.. so that the all hostgroup doesn't get one but the xyz one does 14:41:24 yeah, the 'all' group is basically all hosts. 14:42:07 nagios_statusmap = false by default and you can have it turned on for groups you want 14:42:26 does that sound ok? 14:43:05 do the groups we want status map have anything to do with service level expectations? or basic function of the role? 14:44:06 I think this map was more for new folks to see what all we had where 14:44:12 but I could be mistaken 14:44:16 @smooge - if you are asking me, it sounds fine...im just making notes here 14:44:23 ok cool 14:44:27 any other questions? 14:44:27 good point nirik 14:44:46 not a question, just a reminder about the impending doom of libravatar 14:44:57 * bexelbie has a badges question 14:45:17 i think someone volunteered to rewrite the app with the latest django 14:45:38 I can take that to the list tho 14:45:48 aikidouke: clime was going to run a test instance and see how much work was involved 14:46:10 thanks :) I'll check with clime 14:46:52 https://pagure.io/libravatar2 is the project/rewrite 14:47:01 oh - ty 14:47:50 * pingou had missed a repo got created, cool 14:48:07 oh, looks like another person has been working on a rewrite too 14:48:12 https://git.linux-kernel.at/oliver/ivatar 14:49:16 if libravatar goes away before a replacemtn have we looked at what needs to be turned off so we don't have a ton of pages waiting? 14:51:14 it should fall back to gravatar... 14:52:12 ok cool 14:52:23 #topic Open Floor 14:52:34 @bexelbie had a badges Q 14:52:46 bexelbie, your up 14:52:52 you are up 14:52:56 I am working on two patches to fedbadges, one is trivial, one is a bit more complex (but still reasonably simple) 14:52:57 in response to the "submit talks!" part of this meeting, i just filed https://pagure.io/flock/issue/36 14:52:59 how can we test these? 14:53:03 (about our use of OpenShift) 14:54:10 it's been a while, but I remember that badges-staging needed refreshed or ??? 14:55:00 depending on what you are doing, but I think it could be tested there? 14:55:01 bowlofeggs++ 14:55:10 aikidouke, I am hoping that the trivial change will be merged relatively soon - someone who I think has merge rights has commented on the issue 14:55:15 s/issue/pr 14:55:22 the other change is now open in an issue for feedback pending a PR 14:55:22 yeah, we can definitely test in stg... 14:56:58 nirik, that is awesome ... when the time comes it'd be nice to get some guidance on how to get the code loaded there and to put a custom yaml rulefile in as a test for the second patch, if accepted 14:57:16 i'd love collaboration for that flock talk if it gets accepted - i think patrick might be interested in cospeaking? 14:57:28 bowlofeggs: yep 14:57:42 * nirik still hasn't decided what he wants to submit 14:57:42 i also sent one about using fedora to free your smart phone 14:58:04 i think i might do one about how you shouldn't run rawhide to balance out all the rawhide talks that nirik likes to do 14:58:10 bexelbie: sayan should be able to help there... I think he's the one maintaining these days... unless I am mistaken 14:58:17 the audience needs to hear a different perspective! 14:58:29 nirik: bexelbie: sayan is the maintainer yes 14:58:39 maybe i'll call it "the non-rawhide super highway" as opposed to "the rawhide trail" 14:58:41 the truth is out there! 14:58:44 haha 14:58:47 * bexelbie says sayan just to see if three times makes them appear 14:58:51 ok it is coming up to the end of this meeting 14:59:14 I would like to thank you all for coming today. please tip the waiter.. he has to hear bowlofeggs jokes all day 14:59:14 +1 to the non rawhide talk ... as it goes toward our you don't need rolling or LTS story 14:59:35 hahaha 14:59:45 and good night 14:59:48 #endmeeting