14:00:00 #startmeeting Infrastructure (2018-05-17) 14:00:00 Meeting started Thu May 17 14:00:00 2018 UTC. 14:00:00 This meeting is logged and archived in a public location. 14:00:00 The chair is relrod. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:00 The meeting name has been set to 'infrastructure_(2018-05-17)' 14:00:00 #meetingname infrastructure 14:00:00 The meeting name has been set to 'infrastructure' 14:00:00 #topic aloha 14:00:00 #chair smooge relrod nirik pingou puiterwijk tflink 14:00:00 Current chairs: nirik pingou puiterwijk relrod smooge tflink 14:00:10 .hello2 14:00:11 puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' 14:00:12 .hello2 14:00:12 good morning everyone. 14:00:14 tflink: tflink 'Tim Flink' 14:00:34 * nirik isn't one of the cool people who can use hello2. ;) 14:00:37 .hello kevin 14:00:38 Morning all, rise and shine, it's meeting time ;) 14:00:38 nirik: kevin 'Kevin Fenzi' 14:00:40 .hello2 14:00:40 abompard: abompard 'Aurelien Bompard' 14:01:05 .hell pingou 14:01:07 .hello sinnykumari 14:01:08 .hello pingou 14:01:08 ksinny: sinnykumari 'Sinny Kumari' 14:01:11 pingou: pingou 'Pierre-YvesChibon' 14:01:14 I guess that typo says it all 14:01:20 pingou: ;) 14:01:24 .hello2 14:01:25 bowlofeggs: bowlofeggs 'Randy Barlow' 14:01:37 hello 14:01:47 hello my infrastructure accomplices 14:02:27 #topic New folks introductions 14:02:28 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:02:48 hi 14:02:49 Any newcomers who would like to introduce themselves and give a quick introduction, as people filter in? 14:02:52 whats the collective noun for an infrastructure? a datacenter of... 14:03:05 computers? 14:03:15 infrastuff 14:03:23 hi, i am sundeep from i18n-devel team 14:03:26 network? meh... sorry, derailing, more coffee. ;) 14:03:34 welcome suanand 14:03:41 thanks nirik 14:03:47 greeting suanand :) 14:03:51 (s) 14:04:04 welcome suanand 14:04:14 o/ suanand 14:04:14 thanks bowlofeggs, relrod 14:04:23 hi pingou 14:05:40 suanand: do hang out in #fedora-admin and ask questions :) 14:06:01 sure will do, thanks relrod :) 14:06:52 Okay moving on to announcements 14:07:03 #topic announcements and information 14:07:03 #info relrod moving vh01 and vh03 hosts to new boxes 14:07:03 #info relrod PTO 9 Jun - 19 Jun 14:07:03 #info Pagure updated 14:07:04 #info armv7 Builders downgraded to fedora 27 - kevin 14:07:20 #info bowlofeggs is working on bodhi-3.8.0 beta, but isn't quite deployed yet 14:07:31 #info hopefully metalink is now more resilient to bad pkls by just not serving them to users 14:07:49 https://github.com/fedora-infra/bodhi/blob/develop/docs/user/release_notes.rst 14:08:30 Anyone have questions/comments, or other announcements to add? 14:09:24 okay 14:09:27 #topic Oncall reminder and discussion - kevin 14:09:35 * relrod passes nirik the talking stick 14:10:09 I just wanted to note the post to the infra list... and discussion after... 14:10:22 if anyone has questions or comments. 14:10:40 Hopefully it will help us out 14:11:21 There was talk about having people shadow the oncall or be mentored by them... 14:11:38 oncall++ 14:11:49 +1 14:11:52 IMHO folks are welcome to ask questions or follow anything we are doing in public channels. ;) If people are busy they might wait to respond. 14:12:37 Thats all unless others have more to discuss. 14:12:40 nirik: yeah. I guess one question I had is who all should be in the oncall rotation? Is it just -main? Or are others supposed to be able to do it as well in the future, since a lot of it is triaging? 14:13:09 i would think they don't need to be in main, as a non main member 14:13:23 yeah, good question... I'm not sure. I think perhaps we could have others do it... if they have been around for a while... 14:13:25 as long as they have enough familiarity to know whether an issue is worth interrupting someone over 14:13:32 yeah. 14:14:00 perhaps be at least in sysadmin-noc or sysadmin-vetren? 14:14:21 I was the one who came up with the idea. 14:14:52 nirik: +1 I think they would need some kind of access to be able to quickly take a look if they so desire 14:14:53 I understand that mentoring is not comfortable during outages. 14:15:34 What about some kind of classroom like mentoring during silent periods? 14:15:58 sapo: we've done things like that before...apprentice days 14:16:00 I mean describing recurring activities... 14:16:07 they usually have less-than-great turnout 14:16:13 To me mentoring means a longer term one on one teaching relationship... I think we susbscribe to a more group model where we want everyone to help people, but they need to ask questions and get involved... 14:16:21 OK. I didn't know that. 14:16:33 yeah, we could do another one of those. 14:16:50 and/or also we have a 'learn about' session in the end of the meeting... 14:17:09 thats a good way to learn about stuff, but often we don't have anyone lined up. 14:17:35 * relrod nods 14:17:52 should we return the question? 14:18:04 instead of a learn about, do a "ask me anything" ? 14:18:41 well, that gets back to forcing people to ask when they don't know what to ask. ;) 14:18:50 pingou: well we do have apprentice office hours at the end too... 14:19:12 nirik: fair 14:19:24 relrod: yeah I was also wondering if it doesn't overlap is the open-floor 14:21:00 There's lots of things we could do... it's hard to know which ones will work best 14:21:08 * relrod nods 14:21:16 okay any futher questions/discussion on this? 14:21:19 probibly depends on the folks who are apprentices at the time too... 14:21:50 If people come up with ideas later, please add them to the mailing list thread 14:22:02 h 14:22:22 (ignore that) 14:22:24 puiterwijk: oh really now :P 14:22:40 okay 14:22:41 #topic Tickets discussion 14:22:42 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 14:22:51 .ticket 3983 14:22:55 relrod: Issue #3983: fedmsg enablement - replace the updates sync on releng04 - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/3983 14:22:56 So, I added our oldest ticket here. ;) 14:23:22 Hey, that script got replaced 14:23:23 I was wondering if perhaps we could just do this in meeting or soon. ;) We just need a fedmsg-hub listener right? 14:23:27 haha 14:23:33 puiterwijk: but it is still not fedmsg based. :( 14:23:43 we might need a bodhi fedmsg to be sent too, not sure 14:23:46 Ah, right 14:23:46 and releng04 doesn't exist anymore and... 14:23:55 bowlofeggs: nah, that's there. 14:24:21 nirik: so, I'm honestly not entirely sure what the advantage of fedmsg-based would be over this, except for that we then need to implement more locking. 14:24:23 oh yeah, sync.wait gets sent 14:24:41 Right now, it just runs every 5 minutes, and if there's nothing to do, it's like 20 IOPS and done. Less then a second 14:24:46 puiterwijk: well, right now it sends an email every 5min when one is running 14:24:49 it does introduce one more way the system can fail 14:24:52 fedmsgs can get lost 14:24:58 so I guess we could change the locking 14:24:59 nirik: huh, it shouldn't email if nothing hchanged 14:25:00 cron polling is more reliable, but less efficient 14:25:01 That's a bug 14:25:08 Ooooh, right. The locking outputs 14:25:11 it's the lock wrapper 14:25:16 Yeah, we can silence the lock wrapper 14:26:07 would it be ok to just run it every minute then? 14:26:13 if it only takes a second or two 14:26:20 Yep. 14:26:29 That was one of my goals, just never got there 14:27:15 is doing that cron silence + change an easyfix that an apprentice can do? 14:27:29 I'd say yes. Should be pretty simple 14:27:50 just silence the existing one? well... 14:27:59 then we don't get errors, but I guess thats ok 14:28:23 I think that it still checks the process, so if the process that locked it died, it'll say so and still run the tool 14:28:31 I can just do this... I want to get rid of it. ;) 14:28:37 yeah, it does. 14:29:06 So then the warning for "lock is taken and process is running" is just for detecting if one particular run takes several hours or the like 14:29:39 right. 14:29:52 and if it dies with the lock, it will see the pid doesn't exist and unlock 14:30:10 Yep 14:30:36 Done 14:30:38 anyhow, I'll just do this. :) we can move on... unless there's other tickets anyone wants to discuss 14:30:44 or puiterwijk can. ;) 14:31:06 .ticket 6241 is still listed as a meeting ticket, but I think that's just from a few weeks ago? 14:31:06 relrod: Error: "6241 is still listed as a meeting ticket, but I think that's just from a few weeks ago?" is not a valid integer. 14:31:11 ... 14:32:07 it takes the entire argument. ;) 14:32:13 .ticket 6241 14:32:15 nirik: Issue #6241: How to orphan in EPEL only ? - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/6241 14:32:27 * cverna is a bit late but here :) 14:32:28 oh yeah, I keep not doing this. :) I will change the tags 14:32:56 ok 14:33:14 Any other tickets for discussion? 14:33:47 actually need some help - to speed up transtats deployment 14:33:53 .ticket 6459 14:33:55 suanand: Issue #6459: [RFR] transtats - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/6459 14:34:05 should we take at end of this meeting? 14:34:58 I think now is ok... puiterwijk was last looking at this... 14:35:05 where is the status now? 14:35:06 puiterwijk, what should be the next step? how can I help? 14:35:10 * nirik looks at the ticket 14:35:47 Someone needs to fix up the openshift templates and work with suanand through the RFR. I have not had time to do so, and have tried various times to hand it over to someone, without luck 14:36:55 I'm not sure I am up to speed on openshift enough... I could try, but not sure how far I would get 14:37:07 relrod: would you be willing to give it a go? you did a few apps? 14:37:09 Well, the openshift part should be pretty much done 14:37:21 (not sure) if I re-attach objects (with Dockerfile) 14:37:34 which is currently for s2i 14:37:40 And it's down to fixing the last environment var things, and then going through RFR (getting people on the books for maintaining it, writing SOPs, etc) 14:37:42 oh, I didn't realize that... ok, so it's just a matter of tweaking it to get it working? 14:37:48 Yes 14:37:52 yes 14:37:57 And then the RFR process stuffs 14:38:13 It should all be in ansible as well 14:38:33 I can try to work with suanand on it...but I'm not 100% up to speed on openshift stuff either, so depending on what kinds of tweaks I might not be useful.. 14:38:39 maybe puiterwijk, you get some time (not very urgent tough) 14:38:54 (though) 14:39:00 relrod: you can always ask me on the openshift stuff. That should be like one or two variable names. 14:39:56 Also, suanand knows how the openshift stuff works (he got the initial thing in his openshift), so you can ask him. 14:40:55 okay 14:42:14 alright, anything else here? 14:42:23 i am good.. 14:42:31 #topic Apprentice Open office minutes 14:42:32 #info A time where apprentices may ask for help or look at problems. 14:42:56 Any apprentices have questions, want to show off what they've been doing, want to check in and say hi? 14:43:27 I wanted to add another way apprentices could help if they are interested in packaging... 14:43:47 .tiny https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&email1=infra-sig&emailassigned_to1=1&emailcc1=1&emailtype1=substring&list_id=8012091&order=bug_id&product=Fedora&query_based_on=&query_format=advanced 14:43:48 nirik: http://tinyurl.com/y8pn93p6 14:44:18 thats a list of all the 'infra-sig' bugzilla bugs. :) Patches against those packages to fix those things on src.fedoraproject.org welcome 14:44:19 I am interested in helping packaging 14:44:21 * puiterwijk waits for .tiny to become da.gd 14:44:34 puiterwijk: hahah 14:44:40 :-) 14:44:44 creaked: cool. :) Take a look at those and ask if you have questions on the fixing workflow. 14:44:46 Hello! 14:44:52 .hello2 14:44:53 x3mboy: x3mboy 'Eduard Lucena' 14:44:59 and tiny should do https:// ☺ 14:45:14 puiterwijk: That was my first thought as soon as I saw tinyurl.com, so you're not wrong. :P 14:45:29 nirik: Ok will do 14:45:36 relrod: I knew it would be your first thought, which is why I wondered how long it'd take to get that fixed :D 14:45:42 puiterwijk: and I have good justification, da.gd is open source ;) 14:47:19 okay 14:47:24 nirik: oh, and I think nobody tried their hand at the "prize question" yet, where the price was a cookie, right? :) 14:47:43 #topic open floor 14:47:56 puiterwijk: indeed. want to ask that again here? 14:48:01 Sure! 14:48:21 So, for any apprentices, for the price of a cookie: what's the difference between "service httpd restart" and "systemctl restart httpd"? 14:49:04 apprentices: Make him give you stroopwafel instead of a cookie, it's way better ;) 14:49:28 Well for a stroopwafel I can answer one of them 14:49:29 haha 14:49:51 Oh yeah, these cookies are exchangable when we meet in person for a stroopwafel :) (only apprentices eligible) 14:50:22 (also, conditions apply, like a max etc. :) ) 14:52:11 14:52:29 Well, if anyone wants to answer it later, just come by on #fedora-admin, and make sure to refer to this meeting. :) 14:53:00 I wonder... could we line up a learn about for next week? 14:54:48 I'd love to see an IPA one (sorry puiterwijk) but not sure if a meeting is enough time to really learn about it. 14:55:55 i'd like openshift one, as our way of deploying apps there is not very typical 14:56:03 relrod: that's fine, feel free to ask me if you think I can give a let's learn you're interested in. I'm not sure IPA is all that interesting as it stands now, but sure. 14:56:27 mizdebsk: right... I did an ad-hoc "learn about" at the infra hackfest, but that's a longer session then just a 10-minute thing... 14:56:32 Maybe we should schedule something else for that 14:57:21 mizdebsk: however, I think the opinionated roles should help making things significantly simpler there. 14:59:12 okay have about a minute left before top of the hour. Anything else to discuss quickly? 14:59:23 the openshift thing could be a good flock talk :) 14:59:31 bowlofeggs++ 14:59:32 and those get recorded, i think? 14:59:36 Yeah, they do 14:59:37 usually yeah 14:59:41 I can totally submit one there 14:59:45 \o/ 14:59:57 okay, thanks all for coming! 15:00:00 #endmeeting