13:59:55 <smooge> #startmeeting Infrastructure (2018-05-03) 13:59:55 <zodbot> Meeting started Thu May 3 13:59:55 2018 UTC. 13:59:55 <zodbot> This meeting is logged and archived in a public location. 13:59:55 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:55 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:59:55 <zodbot> The meeting name has been set to 'infrastructure_(2018-05-03)' 13:59:55 <smooge> #meetingname infrastructure 13:59:55 <zodbot> The meeting name has been set to 'infrastructure' 13:59:55 <smooge> #topic aloha 13:59:55 <smooge> #chair smooge relrod nirik pingou puiterwijk tflink 13:59:55 <zodbot> Current chairs: nirik pingou puiterwijk relrod smooge tflink 14:00:06 <x3mboy> .hello2 14:00:07 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com> 14:00:10 <nirik> morning 14:00:26 <smooge> hello everyone. 14:00:29 * relrod_cld waves 14:00:29 <clime> hello 14:00:33 <creaked> hello 14:00:36 * sayan waves 14:00:37 <x3mboy> Hello people! 14:01:00 <puiterwijk> hello. In fixing stuff, so not realyl here. 14:01:15 <bowlofeggs> .hello2 14:01:16 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com> 14:01:17 <tflink> .hello2 14:01:19 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com> 14:01:24 <bowlofeggs> i'm breaking stuff, so i am really here 14:01:44 <smooge> nirik, can you move the fedocal time and channel to this channel and time? 14:01:58 <dustymabe> .hello2 14:02:00 <nirik> yep. 14:02:01 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dusty@dustymabe.com> 14:02:16 <ksinny> .hello sinnykumari 14:02:17 <sayan> .hello sayanchowdhury 14:02:18 <zodbot> ksinny: sinnykumari 'Sinny Kumari' <ksinny@gmail.com> 14:02:21 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com> 14:04:24 <smooge> #topic New folks introductions 14:04:25 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:04:52 <sapo> helo 14:05:27 <smooge> hello sapo 14:05:39 <smooge> how are things for you? 14:06:11 <sapo> Good, thanks for asking. 14:06:31 * aikidouke_ is here 14:06:33 <sapo> I'm working on the network map ticket. 14:06:35 <nirik> welcome sapo 14:06:58 <sapo> I may have some questions when we reach the topic 14:07:13 <smooge> sapo, ok thanks 14:08:35 <x3mboy> Do I still count as new? 14:08:38 <smooge> I would like to thank Anatoli for offering pull requests 14:08:47 <dustymabe> THanks Anatoli! 14:09:08 <smooge> OK next up as I focus on one ping at at a time 14:09:11 <smooge> #topic announcements and information 14:09:11 <smooge> #info Fedora 28 released! Kudos to everyone! 14:09:12 <smooge> #info Freeze is over 14:09:12 <smooge> #info Pagure 4.0 being deployed 14:09:12 <smooge> #info New openshift being deployed 14:09:13 <smooge> #info A Bodhi 3.7.0 release is being worked on. It mostly addresses some usability issues with test gating, and also adds support for links to privacy/legal. currently targeting a release early next week. 14:09:36 <nirik> #info mass update/reboot cycle next tuesday 14:10:33 <smooge> #info Ibiblio data move 2018-05-09. Fedora people and other systems will be down for N hours 14:10:59 <nirik> #info short switch outage later today (21UTC) 14:11:17 <smooge> #info who gets the last info 14:11:36 <smooge> any other announcements? 14:12:13 <bowlofeggs> i announce that i enjoy working with all of you. 14:12:22 <nirik> awww 14:12:33 <dustymabe> bowloftapioca - thanks! 14:12:40 <bowlofeggs> :) 14:12:54 <smooge> ok I think we are now into mushy stuff so next topic 14:12:58 <smooge> #topic Tickets discussion 14:12:58 <smooge> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 14:13:08 <jwf> bowloftapioca++ 14:13:11 <nirik> There's only a few left from last week... 14:13:24 <nirik> oh, one actually. 14:13:34 <smooge> so it looks like we have 1 to discuss this week 14:13:52 <nirik> we ran out of time last week and didn't really get to this one much 14:14:03 <smooge> https://pagure.io/fedora-infrastructure/issue/6241 14:14:44 <smooge> My first question comes from trying to figure out where this sits. To me this looks like releng, but we write the apps 14:15:07 <nirik> yeah, the state is not super clear. ;) 14:15:32 <nirik> so the orig case was say you maintain package foo and don't want to maintain it's epel branches. 14:15:33 <bowlofeggs> wihtout per-branch ACLs i don't see how we could do this 14:15:51 <nirik> you can make bugs get assigned to orphan 14:15:53 <bowlofeggs> well i guess i don't mean ACL exactly, but we don't have per branch "point of contacts" 14:15:58 <nirik> we do tho 14:16:05 <nirik> oh, well, sorta only 14:16:15 <nirik> it's epel vs fedora only 14:16:23 <bowlofeggs> yeah 14:16:29 <bowlofeggs> but epel is still a branch 14:16:38 <smooge> I expect this is going to also happen for other types of branches 14:16:48 <bowlofeggs> i ugess there's that weirdo yaml file in some releng repo somewhere that defines some of this stuff 14:17:10 <nirik> so you can set orphan to be assigned all epel bugs... but then the only way we know to retire it or have someone take it is that assignment 14:17:21 <bowlofeggs> i am not a fan of the way that works btw - i wanted to adjust that once and finding the docs was hard, and then it took over a week to get my PR merged (all so i could have the-new-hotness file bugs for me) 14:17:48 <bowlofeggs> another problem is that we don't have anything or anyone looking for orphaned things anymore 14:18:01 <bowlofeggs> there was a fesco discussion about this sometime recently 14:18:08 <nirik> they are supposed to be retired after X time... 14:18:17 <bowlofeggs> so if they get orphaned they will stay 4eva as it is 14:18:18 <nirik> and I think some folks were looking into reviving that 14:18:21 <bowlofeggs> unless someone fixes that 14:18:22 <bowlofeggs> yeah 14:19:07 <nirik> So, I guess I am kinda at: lets document this and move on... 14:19:08 <bowlofeggs> should we mark this ticket as waiting on someone to fix that? 14:19:23 <bowlofeggs> "that" being the orphan reaper script? 14:19:36 <bowlofeggs> or yeah, we could just document how to make it an orphan 14:19:44 <bowlofeggs> i guess we need to document it anyway 14:19:53 <smooge> ok who is documenting it? 14:19:56 <nirik> yeah, at least in the 'new' docs 14:20:08 <bowlofeggs> is it already documented in those docs i said were hard to find? 14:20:12 * bowlofeggs isn't sure he could find it again 14:20:23 <nirik> ha 14:20:30 <nirik> I can document it somewhere 14:20:55 <bowlofeggs> it's this i think? https://pagure.io/releng/fedora-scm-requests 14:21:22 <bowlofeggs> though i don't know if that talks about orphaning 14:21:40 <smooge> ok I hae assigned it to nirik who has no tickets 14:21:44 <nirik> yep.. thats where to do it... docs might be wiki or the new packager area 14:21:48 <bowlofeggs> so are we suggesting that they just change the BZ assignee for epel to orphan? 14:22:03 <nirik> yeah, and then whoever is retiring packages also look at that 14:22:08 <bowlofeggs> cool 14:22:50 <nirik> ok, shall we move along? 14:22:53 <smooge> Next up 14:22:58 <smooge> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=3 14:23:10 <smooge> These are tickets which are looking for people to fix them 14:23:52 <bowlofeggs> i would appreciate that waiverdb token for staging bodhi in the next couple days if it's a possibility - it would help me test the 3.7 beta i'm working on. it's not a huge deal if that's not possible 14:24:14 <bowlofeggs> i.e., it'd be real nice, but i've been living without it and the world hasn't ended :) 14:24:17 <nirik> or better: https://pagure.io/fedora-infrastructure/issues?status=Open&priority=3&assignee=0 14:24:29 <nirik> (ones with no assignee) 14:24:35 <smooge> thanks 14:24:49 <nirik> bowlofeggs: I am not 100% sure where to get that... so I have left it alone. 14:25:09 <bowlofeggs> i fear that only patrick knows how to do it and i don't want to pile too much on him :/ 14:25:15 <smooge> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=3&assignee=0 [Tickets that need assignment] 14:25:20 <bowlofeggs> as i said, it's not critical 14:25:28 <bowlofeggs> and i don't want to pull him off more important things 14:25:31 <puiterwijk> What do I know? 14:25:32 <smooge> Please look at these and see if you can adopt one. We will start reviewing them next week 14:25:44 <bowlofeggs> patrick you know way too much :) 14:25:44 <puiterwijk> bowlofeggs: what ticket do I know? 14:25:54 <bowlofeggs> puiterwijk: https://pagure.io/fedora-infrastructure/issue/6891 14:26:00 <puiterwijk> checking 14:26:16 <puiterwijk> Okay. Right. Ping me post-meeting, and I can take care of that 14:26:26 <bowlofeggs> i can take #6872 14:26:34 <puiterwijk> Takes about 5 minutes, but I'm currently trying to fix repo stuff so I need to focus 14:26:35 <bowlofeggs> now that we are unfrozen 14:26:54 <bowlofeggs> puiterwijk: yeah you are working on More Important Things™ 14:27:17 <smooge> OK next topic? 14:27:38 <smooge> #topic Apprentice Open office minutes 14:27:38 <smooge> #info A time where apprentices may ask for help or look at problems. 14:27:52 <smooge> Are there any questions from apprentices on items? 14:28:11 <sapo> o/ 14:28:21 <smooge> hello sapo. 14:28:26 <creaked> Any tasks/projects coming up that need assistance? 14:28:31 <sapo> So about that network map ticket. 14:29:03 <sapo> I planned to make actually two different ones: 14:29:19 <sapo> 1: Virthosts / VMs 14:29:38 <sapo> 2: Actual network map with all machines all IPs 14:29:40 <nirik> creaked: see the lists above. ;) Some likely require access or the like, but some might be possible to do a lot on without any access. 14:30:22 <sapo> I already wrote a script that collects all the VM Host / VM relations 14:30:26 * nirik realizes he owes a review to an apprentice too. 14:30:56 <sapo> I used the virthost-list.out file from Nagios 14:31:04 <sapo> Is that OK in your opinion? 14:31:30 <nirik> https://pagure.io/fedora-infrastructure/issue/6505 <- nagios plugin for review... I just keep not getting to it if anyone else wants to help test. 14:31:34 <nirik> sapo: sounds fine to me. 14:31:56 <sapo> OK. The second part. 14:32:09 <creaked> @nirik hehe I've been checking that list daily/ github for things to fix. I just did not know if there was anything outside of pague, etc. 14:32:11 <sapo> Where could I collect all the IP addresses? 14:32:17 <sapo> ..from? 14:32:31 <x3mboy> Hello 14:32:34 <nirik> sapo: ansible has them in inventory/host_vars/ 14:32:37 <smooge> sapo, on batcave there is also /var/log/virthost-lists.out 14:32:46 <x3mboy> I was looking for something to do 14:32:55 <sapo> OK Thanks I'll look into it. 14:33:47 <smooge> sapo for ip addresses. I think you can read-only clone the dns db. on batcave: git clone /git/dns 14:34:01 <nirik> https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix 14:34:29 * nirik is happy to expand on whats needed for any of those easyfix tickets if any sound interesting 14:35:14 <sapo> OK thanks smooge 14:35:58 <smooge> thanks nirik and sapo 14:36:27 <smooge> also apprentices can look at the ones in https://pagure.io/fedora-infrastructure/issues?status=Open&priority=3&assignee=0 and see if any of them might be things they could comment on 14:37:54 <smooge> #topic Open Floor 14:38:05 <smooge> OK I have one announcement from a different meeting I was just in 14:38:14 <nirik> I had a quick thing to bring up.. can after smooge 14:38:20 <puiterwijk> bowlofeggs: other idea about the tokens: how about we have a talk about how to issue the tokens later, and you try to write a small py script to generate them? 14:38:26 <puiterwijk> Sorry. 14:38:41 <smooge> #info Outage 2018-05-15 for systems on virthost-cc-rdu01 14:39:08 <smooge> will put in announcement for that after this meeting. Should be a 'short' outage. I will be onsite to fix problems 14:39:23 <smooge> that is all. over to you nirik 14:39:28 <nirik> networking stuff? 14:39:35 <smooge> yep. 14:39:38 <bowlofeggs> puiterwijk: sure we can do that - it'd be good for someone else to know how to do it :) 14:39:49 <puiterwijk> bowlofeggs: absolutely. 14:40:08 <bowlofeggs> puiterwijk: can i schedule a meeting with you to transfer that knowledge? maybe tomorrow since today sounds slammed for you? 14:40:16 <nirik> I just read the other night https://blogs.akamai.com/2013/10/you-must-try-and-then-you-must-ask.html (pointed at from https://medium.com/@michaeldehaan/achieving-agility-in-engineering-processes-d7e929e65b59 ) and thought it was a good think we should all try and do... 14:40:33 <nirik> basically the idea is that you work on something, if you get stuck... 14:40:35 <puiterwijk> bowlofeggs: I'll talk to you in a bit 14:40:43 <bowlofeggs> cool thanks for the offer! 14:40:45 <nirik> try 15min more and then ask others to help. 14:41:16 <nirik> and during those 15min you document all that you tried or did or what the problem is. so you can show it to whoever you ask 14:41:23 <bowlofeggs> nirik: +1 14:41:24 <nirik> anyhow, I thought it was a nice rule of thum 14:41:32 <bowlofeggs> yeah very much agreed 14:41:36 <ksinny> +1 14:41:40 <bowlofeggs> i have some thoughts to piggy back on that too 14:41:43 <bowlofeggs> two thoughts 14:41:43 <smooge> Rules of the Ancient Pharoah Thum 14:41:58 <bowlofeggs> 0) oncall seems to be awesome - we should keep doing it and get people used to it more 14:42:03 <puiterwijk> nirik: that reminds me: I think most of openshift should be good. We might want to rerun to be sure, but there's a bunch of manual things to do in the middle... 14:42:19 <bowlofeggs> 1) i think it'd be good for more of our requests to be tickets and fewer of them to be "irc support" (if that makes sense) 14:42:20 <nirik> puiterwijk: I was going to ask after the meeting. 14:42:23 <puiterwijk> ack 14:42:29 <bowlofeggs> i.e., the oncall person could very frequently direct people to file a ticket 14:42:37 <nirik> bowlofeggs: agreed on both counts 14:42:40 <bowlofeggs> that way we have a good way to prioritize work, and keep track of things 14:42:51 <bowlofeggs> it also gives more visibility into the work being done 14:43:02 <bowlofeggs> which is nice when you want to tell your manager what you've been working on :) 14:43:12 <nirik> we need to protect Brent^Wpuiterwijk and the rest of us. ;) 14:43:17 <bowlofeggs> hahah 14:43:19 <bowlofeggs> yes 14:43:29 <bowlofeggs> i'm guilty of bothering the sage myself 14:43:38 <bowlofeggs> i've been trying to remember to file tickets more and ask for IRC support less 14:43:53 <nirik> yeah, a big problem with irc is focus 14:43:58 <bowlofeggs> yeah 14:44:07 <nirik> even just asking someone to look at something later means they stopped doing what they were to reply 14:44:10 <bowlofeggs> sometimes i close my client when i need to focus on something 14:44:20 <smooge> OK next up 14:44:20 <bowlofeggs> and just check it like once and hour or so 14:45:09 <smooge> who is oncall starting Monday? 14:45:19 <smooge> puiterwijk has done it for a week 14:45:33 <bowlofeggs> does oncall person need to be sysadmin-main? 14:45:34 <nirik> I can take it, or relrod if he's ready for it 14:45:34 <puiterwijk> Well... I've done 3.5 days and I'm already going crazy 14:45:53 <smooge> puiterwijk will have done it for a week 14:46:00 <puiterwijk> bowlofeggs: I'd say it doesn't need to be, but it should be someone who knows enough to prioritize stuff 14:46:11 <puiterwijk> (and then probably know who to ask) 14:46:14 <bowlofeggs> i can't volunteer to do it next week because i'm kinda overloaded right now, but i could do it in the future. maybe the week after? 14:46:23 <nirik> and someone who is on irc a lot to direct people 14:46:33 * puiterwijk thinks we can write a doc for that, and get random people to do that. Maybe call it a service desk 14:46:39 <bowlofeggs> i wouldn't mind getting in the rotation to help out with that 14:46:45 <nirik> puiterwijk++ 14:46:45 <zodbot> nirik: Karma for puiterwijk changed to 15 (for the f28 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:46:46 <bowlofeggs> and i can direct people to file tickets too :) 14:47:03 * ksinny is curious to know what works an oncall person needs to do 14:47:06 <smooge> I will be writing our helldesk sop after this meeting 14:47:12 <bowlofeggs> it's basically level 1 support :) 14:47:19 <smooge> it is a bit more than that 14:47:24 <bowlofeggs> "can i speak to your manager?" 14:47:31 <ksinny> haha 14:47:38 <bowlofeggs> haha helldesk 14:47:52 <bowlofeggs> smooge: was that a hilarious typo or a hilarious on-purpose? 14:47:58 <nirik> answer questions on irc. try and fix things if possible. direct people to file tickets. talk to others to find out how to fix the things you didn't know how to fix 14:48:10 <bowlofeggs> yeah true 14:48:15 <smooge> it was a typo that I kept so it became on-purpose 14:48:44 <smooge> check nagios regularly, ack issues and answer pages 14:48:57 <ksinny> Thanks for the info 14:48:57 <bowlofeggs> actually i can't do the week after next, or at least not one afternoon, because i am paying a man to put a hole in my tooth one day that week 14:49:06 <bowlofeggs> so i can do all but one afternoon 14:49:28 <bowlofeggs> ugh, and i need to pick up someone from the airport another day 14:49:34 <smooge> yeah so 14:49:35 <nirik> we can figure it out. 14:49:39 <puiterwijk> I don't think we need you to always be a full week 14:49:39 <smooge> that 14:49:42 <ksinny> bowlofeggs: I am postponing my dentist appointment from past 1 month :/ 14:49:45 <bowlofeggs> but! in 3 weeks my calendar looks much more clear 14:49:56 <puiterwijk> bowlofeggs: that's why we tell people to try .oncall rather than trying to remember who's on call 14:49:58 <bowlofeggs> ksinny: :) 14:50:04 <puiterwijk> We can switch that like every minute 14:50:10 <bowlofeggs> puiterwijk: true 14:50:18 <bowlofeggs> well i'm willing to do a lot of the week in two weeks :) 14:50:25 <smooge> thanks 14:50:36 <smooge> we are at 10 minutes until the end of the meeting. 14:50:41 <smooge> nirik, did we get your item? 14:50:49 <smooge> wait we did 14:50:54 <nirik> yeah, just wanted to note that post for folks. 14:51:04 <smooge> were there any other open floor items? 14:51:16 <puiterwijk> Just one 14:51:30 <smooge> your turn 14:51:35 <puiterwijk> There havce been some issues with Fedora 28 repos today and yesterday, those should be fixed. There's been metalink issues today, those should be fixed now too 14:51:42 <puiterwijk> If you still have trouble, please call the oncall 14:52:07 <smooge> ok thanks puiterwijk 14:52:33 <smooge> and with that.. bowlofeggs say goodnight 14:52:34 <clime> puiterwijk: I can confirm it's fixed. 14:53:19 <smooge> ah sorry I messed up the George Burns straight line 14:53:32 <smooge> ok I will call it an end of meeting 14:53:36 <smooge> thank you all for coming 14:53:40 <smooge> #endmeeting