18:04:12 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:04:12 Meeting started Wed May 13 18:04:12 2020 UTC. 18:04:12 This meeting is logged and archived in a public location. 18:04:12 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:04:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:04:12 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:04:12 #chair cverna mboddu nirik smooge 18:04:12 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:04:12 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:04:12 #info agenda is at https://board.net/p/fedora-infra-daily 18:04:12 Current chairs: cverna mboddu nirik smooge 18:04:12 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:04:13 #topic Tickets needing review 18:04:14 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:04:26 .ticket 8914 18:04:27 nirik: Issue #8914: Please grant membership to Fedora DNS Sysadmin Group (sysadmin-dns) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8914 18:04:49 * mboddu can update the tickets 18:04:55 I guess we need to discuss this one. 18:05:23 Yeah, may be at fedora infra meeting? 18:05:30 Tomorrow? 18:06:04 we could yeah. I think it's probibly fine but we should definitely do it's own zone to reduce chance of problems. 18:06:08 * mboddu wondering where it will fall under, low trouble or high trouble? 18:06:21 it's pretty low... 18:06:25 Doing is easy 18:06:31 But should we do it or not is the problem 18:06:37 yeah 18:06:44 right. well, we could just leave that out for now 18:06:48 I have added some people in the past, but I don't know the person who is asking this time 18:07:01 Right, hence my dilemma :) 18:07:14 just move it to waiting on assignee, metion we are going to discuss in our meeting tomorrow and add to adjenda there for the metting? 18:07:23 Adding someone gives them access to the DNSSEC keys, which is generally pretty restrictive 18:07:25 no need to groom it yet 18:07:33 ack 18:07:43 well, and the ability to mess up all public facing things. ;) 18:08:17 but also should be easy to recover from mistakes 18:08:41 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#8914 https://pagure.io/fedora-infrastructure/issue/8914 18:08:43 pagure.issue.comment.added -- mohanboddu commented on ticket fedora-infrastructure#8914: "Please grant membership to Fedora DNS Sysadmin Group (sysadmin-dns)" https://pagure.io/fedora-infrastructure/issue/8914#comment-652164 18:09:29 thats all in need review. 18:09:33 any releng ones today mboddu ? 18:09:48 Yes 18:09:56 .releng 9451 18:09:57 mboddu: Issue #9451: rework koji channels / policy - releng - Pagure.io - https://pagure.io/releng/issue/9451 18:10:04 nirik: ^ its the one you created :) 18:10:23 Definitely it has to wait until dc move is done 18:10:26 ah yeah. I think doing that after the move is best 18:10:28 yeah 18:10:47 But, is that sort of policy available? 18:10:58 Looking at it, it seems possible but messy 18:11:01 But I am missing something 18:11:12 I might be missing something* 18:11:53 well, we can define channels and put whatever machines in them we want and we can define hub policies that put some things in some channels. 18:12:01 but yeah, the noarch thing is likely messy. 18:12:26 Okay, we will get it when we can get to it 18:12:41 we are going to have to do some similar work to this as part of the move too. 18:12:50 There are unretirement tickets, which I will work later today 18:12:50 since we will have fewer builders for a while. 18:13:10 Okay, maybe we could find easy ways to do it then 18:13:19 yeah, or at least learn from it. 18:13:36 Anyway, groomed and comment on the ticket to work on it after dc move 18:13:49 any reviews needed, other tickets to discuss, etc? 18:14:01 Nothing from me 18:14:16 I have a question 18:14:26 .ticket 8905 18:14:27 mobrien[m]: Issue #8905: Globally ban `elitetorrent1.com` - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8905 18:14:28 sure, fair away 18:14:32 fire 18:15:14 With this kind of ticket, is that something that's done with group consensus or does it need management/legal approval first? 18:15:36 just group consensus I think... 18:16:02 but it's also kinda new, as we aren't blocking any other domains 18:17:00 Ok I think I should have permissions for that now. I'll investigate it and see can I see an obvious method for doing it and comment a possible solution on the ticket if I find it 18:17:47 so, aside from just blocking it at the postfix level... we could also consider adjusting our spamassassin config to just mark it spam 18:18:41 our mailman config just drops posts that are spam. it would still send to aliases, but at least people could filter it... 18:18:56 thanks for taking it on! 18:19:28 No problem. 18:19:42 as far as DC move, not too much new to report. smooge and networking have been trying to isolate a issue that prevents pxe booting from working from other than 1 vlan. ;( 18:19:59 I'm working on getting a proxy installed. 18:20:17 we will see if we can get openshift installed tomorrow. ;) 18:20:29 Woah, thats good news 18:20:52 Well, other than the pxe booting not working :) 18:21:03 storage is almost done syncing. if we can get networking going to the new netapp we can start testing that r/o 18:21:34 next week hopefully networking will be stable and we can start building out everything else we need to. 18:21:52 +1 18:21:59 thats all I have. If no one has anything else, will close out in a min 18:22:40 I know I said this before, but I will say it again, thanks nirik and smooge for all you are doing with the dc move 18:23:01 no problem. I am looking forward to the day it's over. :) 18:23:21 And thanks mobrien[m] for offering your help on openshift cluster :) 18:23:37 well Matthew found a way to get dhcp/tftp to work.. and that was to use the old format we had of putting in a specific host in the dhcpd versus the general purpose one 18:23:57 smooge: weird. so a dhcpd bug? 18:24:04 not sure yet.. 18:24:22 it looks like something a little bit with dhcpd and little bit switch/router 18:24:32 yuck. ;( 18:24:57 the dhcpd server is sending out a gateway and netmask but something else in the packet is screwey 18:26:12 ok, thanks for digging that rabbit hole down smooge. :) 18:26:19 Thanks for coming everyone. 18:26:21 #endmeeting