18:00:58 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:58 Meeting started Wed Oct 14 18:00:58 2020 UTC. 18:00:58 This meeting is logged and archived in a public location. 18:00:58 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:58 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:59 #chair mboddu nirik smooge pingou mobrien 18:00:59 Current chairs: mboddu mobrien nirik pingou smooge 18:00:59 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:59 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:59 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:59 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:00 #topic Tickets needing review 18:01:03 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:01:12 I had it set, just got distracted. 18:01:18 no problem 18:01:46 Oh man, its time already, time is passing away very quickly 18:01:48 #info no new infra tickets to triage today 18:01:54 any releng ones mboddu ? 18:01:57 Yup 18:02:13 .releng 9808 18:02:15 mboddu: Issue #9808: Remove private branch ddiskit/private-ckalina-1885256 - releng - Pagure.io - https://pagure.io/releng/issue/9808 18:02:23 It should be low,low,ops? 18:02:37 yep. +1 18:03:28 .releng 9809 18:03:29 mboddu: Issue #9809: Drop special restictions on fedora-release - releng - Pagure.io - https://pagure.io/releng/issue/9809 18:03:53 I'm 100% fine with this, but I can't remember us agreeing to it... might just not be remembering tho. 18:04:47 I dont remember agreeing to it, but we definitely talked about it on non dist-git repos like releng, pungi-fedora and others.. 18:05:52 we did drop fedora-release from the secure-boot channel in koji... 18:06:00 perhaps we agreed to more then... can't recall. 18:06:06 anyhow, I'm in favor. 18:06:17 I am in favor and I dont recall as well 18:07:59 I had a couple of old ones but most of them are political storms which can wait. 6801 was one which I didn't know where we got to (and where one should run hardlink and on what directories /pub/fedora-secondary and /pub/archive ? 18:08:25 .ticket 6801 18:08:25 nirik: Issue #6801: run hardlink on fedora-secondary - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/6801 18:09:19 ah yeah. so... our rawhide/branched compose scripts don't hardlink aarch64 with the other arches... because they are done seperately since they don't have everything in the same place 18:09:55 again I wish we could put everything in the same tree... 18:10:08 I remember you were looking at this recently 18:10:21 yeah, I don't know that there is any easy way to fix it. 18:10:41 without putting all the stuff in one tree and copying it with one rsync 18:10:44 ok for me to put that info on the ticket and move it to high-trouble 18:11:17 sure, or we could just close it and say 'sorry, we can't hardlink everything because we split composes up' 18:11:29 or... 18:11:40 could we make a cron to run hardlink every week or something? 18:11:42 one thing we could do is run hardlink after we rsync the content. 18:11:58 yeah 18:12:15 nb: 100% useless, unless it's right after composes, because they would just unhardlink everything the next compose 18:12:22 oh 18:12:28 so we'd have to do it after every compose 18:12:46 yes, and it would make composes take a lot longer and it would hit the storage pretty hard also 18:13:04 but we could try it and see how bad it is. 18:14:29 I guess I'd say lets try and see how bad, then if it's bad we revert it and close CANTFIX. 18:15:27 thoughts? 18:15:34 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#6801: "run hardlink on fedora-secondary" https://pagure.io/fedora-infrastructure/issue/6801#comment-696211 18:15:41 added something 18:15:51 I am not 100% sure, but nothing wrong in trying 18:17:20 I have a quick question regarding #9388 18:17:42 I can make a PR. I wonder if we shouldn't wait until after f33 tho... in case it hammers the storage too much for f33 compsoes to finish, etc 18:17:47 nirik, where would this change in hardlink etc occur? in admin scripts or releng scripts 18:18:11 I am ok with waiting til afterwords.. I just had a window that had me looking at doing a hardlink of /pub/archive 18:18:25 smooge: pungi-fedora/nightly.sh script... I guess 3 times... once after syncing to pub/ once for alt/ and once for fedora-secondary 18:18:30 and I was like.. do I need to do this still, did nirik do it, what ticket? 18:19:12 wait till after F33 18:19:16 nirik: Better do it post f33 release 18:19:19 mobrien, what was the question 18:19:31 ok, can put in the PR and mark it post-freeze... 18:19:36 .ticket 9388 18:19:37 nirik: Issue #9388: AWS: create S3 bucket for Testing Farm - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9388 18:19:37 +1 18:19:54 ah yeah, I was working on that before the meeting... sorry if you already were. 18:20:10 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#6801: "run hardlink on fedora-secondary" https://pagure.io/fedora-infrastructure/issue/6801#comment-696212 18:20:40 I was going to take it earlier but I wanted to ask first, is it a case generally where we create a new bucket or have 1 main fedora bucket and do subdirs? 18:21:06 we have been making new seperate buckets for things. 18:21:24 and then roles/users get perms to only access their bucket arn 18:22:20 If they need it to be public tho, we have to go to s3 and uncheck the 'deny all public access' thing. I guess they put that in because people were leaking things to the public they didn't intend to... 18:22:53 I read an article before about the things you can find on public S3 buckets 18:23:12 yeah, pretty crazy. 18:24:25 We could do permissions based on dirs in a bucket if we need to, I know there is a limit for buckets per account/region 18:25:05 ok, yeah, if thats better we could look at it... or if we hit the limit? 18:25:32 alright we are hitting meeting limit 18:25:54 Ya, just soemthing to keep in mind for future but I'm getting off topic. 18:26:22 #info smooge will be unable to attend meetings regularly until 26th 18:26:33 #endmeeting