18:00:03 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:03 Meeting started Wed Apr 14 18:00:03 2021 UTC. 18:00:03 This meeting is logged and archived in a public location. 18:00:03 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:03 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:03 #chair mboddu nirik smooge pingou mobrien nb 18:00:03 Current chairs: mboddu mobrien nb nirik pingou smooge 18:00:03 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:03 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:03 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:03 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:04 #info reminder: speak up if you want to work on a ticket! 18:00:05 #topic Tickets needing review 18:00:07 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:35 I am here, but needs 2 min 18:01:21 .hi 18:01:22 dtometzki: dtometzki 'Damian Tometzki' 18:01:46 here 18:02:17 morning all. lets wait for mboddu to get back 18:02:41 yay I have 2 factor again 18:05:24 Okay, I am here 18:05:27 .ticket 9868 18:05:28 nirik: Issue #9868: Create second IPA instance in staging to more closely mirror prod - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9868 18:05:39 just needs waiting on asignee and assigned to mobrien 18:05:52 there's a private one, but I can deal with that one. 18:06:00 Done 18:06:01 .ticket 9871 18:06:03 nirik: Issue #9871: remove group svnendoculator - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9871 18:06:12 low/low/ops and waiting on us having a policy 18:06:27 I did enable audit logging on ipa01. 18:06:47 so now we can at least see when people are added/removed/the group is deleted. 18:08:32 +1 18:10:19 I guess I am leaning toward being able to delete groups, as long as we can make sure and save the audit logs for a long long time 18:10:19 .ticket 9872 18:10:19 nirik: Issue #9872: FAS OIDC keys for forum.mojefedora.cz - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9872 18:10:19 hum. 18:10:29 lag big time. ;( 18:10:37 low/low/ops? 18:10:59 .ticket 9873 18:11:00 nirik: Issue #9873: Can not log into lists.fedorapreoject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9873 18:11:01 Done 18:11:06 med / med / ops? 18:11:21 ^ is closed as invalid 18:11:30 ah yes, they were using email. 18:11:38 we need to close that out sometime. 18:11:50 thats all the new ones on the infra side... releng? 18:12:09 No new releng one's 18:12:16 hi 18:12:16 great! 18:12:23 ih 18:12:33 #topic work plans 18:12:33 #info everyone should note what things they are hoping to work on over the next day/week 18:12:46 so, whats everyone planning on working on the rest of this week? 18:13:06 I'm waiting still for my hardlink to finish on archive volume, then will be swapping it in place. 18:13:27 F34 release work and CentOS Stream work for me 18:13:49 * nb is not working on anything particular 18:14:00 woops I had to step away for a few minutes and mised it 18:14:03 I was looking at figuring otu a way for users to entroll a HOTP on their yubikey themself 18:14:12 nb: There's always day to day stuff. 18:14:14 but it looks like hte keys that IPA generates are longer than what yubikey wants 18:14:33 nirik yeah, i'll try to help with whatever comes up 18:14:36 nb: yeah, sad. Perhaps it will be easier to implement now in noggin. 18:14:47 we should update the ticket with our findings. 18:15:03 https://github.com/fedora-infra/noggin/issues/202 18:15:07 I will do that staging ipa server tomorrow and also add some tuning in ipa for testing. Also a pr for the otp script tomorrow 18:15:45 Have to try catch smooge again before the end of the week too. 18:15:47 I was able to enroll my hotp from a gist document but I also screwed it up twice in doing so..[and was glad I did not log out from the console when I did it] 18:15:52 which otp script? 18:16:05 smooge did you enroll as admin? or as your user? 18:16:09 or actually, your user is admin I think 18:16:17 I had to do it via the admin interface 18:16:36 so not useful for general users 18:16:42 nirik the one to check which sysadmins don't have an otp emrolled 18:16:57 the one I was trying to get something in the system before it was run 18:17:05 Actually that brings up something from audit logs: people doing admin things: please try and do them as your own user if you are an admin... this will help audit logs have who actually did something. 18:17:29 Good point 18:17:35 Ah yes, I am guilty of the that 18:17:44 me too to be clear. ;) 18:18:48 #topic Discussion items 18:18:59 any tickets, prs or anything to discuss? 18:20:09 smooge: whats the state of the new openshift servers? can you hand off to me, or someone on those? would be nice to have them ready to pxe 18:20:24 and anything else you want to handoff on? 18:21:17 I guess perhaps longer than the scope of this meeting. ;) 18:23:03 * nirik might be lagged out again 18:23:13 I guess if nothing else can close out in a min 18:24:20 * nb has nothing else 18:24:35 nirik are there any cases where people would need to be in sysadmin when they aren't in sysadmin-*? 18:24:51 I've removed a few people that are no longer in sysadmin-* from sysamin 18:25:06 after I removed them from sysadmin-whatever 18:25:09 no, but we may just revisit this setup now... 18:25:12 used to be: 18:25:31 nirik, so the hardware is in place. none of the network ports are active and 1 of the mgmt ports does not work 18:25:32 sysadmin got you commit to ansible + alerts/emails on git commits, etc 18:25:57 sysadmin-* got you ssh access to actually be able to have the ansible repo and commit to it and access to machines, etc. 18:25:59 sorry didn't mean to talk over you 18:26:09 It may be 'sysadmin' is something we can drop now. 18:26:23 smooge: no, no problem at all. so it's a 'when matt is there next' thing? 18:26:55 it might be. the wiring was all done at 11 pm before he drove home sick 18:27:07 :( 18:27:36 idea: open a 'next handson at iad2' ticket and keep it updated with list of items we want someone to do next time they are on site? 18:27:38 so I don't know if all the ports were done and I definitely do not know which level. I will write up what I know after this meeting in a markdown doc 18:27:54 or I can put it in that ticket 18:28:17 I think ticket is good because we triage/poke/look at them more. 18:28:33 and I assume no word on the s390x networking ticket. 18:29:59 ok then, lets all get back to whatever we were working on. ;) 18:30:03 #endmeeting