18:00:07 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:07 Meeting started Fri Sep 25 18:00:07 2020 UTC. 18:00:07 This meeting is logged and archived in a public location. 18:00:07 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:07 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:07 #chair mboddu nirik smooge pingou mobrien 18:00:07 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:07 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:07 Current chairs: mboddu mobrien nirik pingou smooge 18:00:07 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:08 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:09 #topic Tickets needing review 18:00:10 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:39 Hello 18:00:44 * mboddu can update the tickets 18:00:48 morning. 18:00:55 .ticket 9347 18:00:56 nirik: Issue #9347: Copr should be accessible via IPv6 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9347 18:01:07 I think we can do this, just needs sorting. 18:01:25 med/med/ops ? 18:01:32 +2 18:01:35 +1 18:01:46 +1 18:01:50 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9347: medium-gain, medium-trouble, and ops https://pagure.io/fedora-infrastructure/issue/9347 18:01:58 .ticket 9348 18:02:00 nirik: Issue #9348: staging rabbitmq certs and key - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9348 18:02:16 I added a comment since I am not 100% sure what this is for. ;) 18:02:22 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9347 https://pagure.io/fedora-infrastructure/issue/9347 18:02:30 but if I am right, just needs doing, med/low/ops? 18:02:52 +1 18:03:20 Leo asked me about it 18:03:27 He said "I was trying to setup a rabbitmq instance myself for fedora-messaging.. but I am hitting my head against the wall" 18:03:55 yeah, we should use the cluster we have where we can. 18:03:59 Since I dont know much on fedora-messaging, I asked him to create a ticket 18:04:19 I just wasn't ssure if there was some plan to deploy mbbox in out clusters... which I don't think makes too much sense. 18:04:26 pagure.issue.tag.added -- mohanboddu tagged ticket fedora-infrastructure#9348: low-trouble, medium-gain, and ops https://pagure.io/fedora-infrastructure/issue/9348 18:04:27 pagure.issue.edit -- mohanboddu edited the priority fields of ticket fedora-infrastructure#9348 https://pagure.io/fedora-infrastructure/issue/9348 18:04:53 ok, thats it on infra... any releng ones today? 18:04:57 Yeah, I dont think thats the problem 18:04:59 Yes 18:05:06 .releng 9766 18:05:07 mboddu: Issue #9766: Unretire rpms/osslsigncode - releng - Pagure.io - https://pagure.io/releng/issue/9766 18:05:14 Just unretirement, low,low,ops? 18:05:17 +1 18:05:37 .releng 9767 18:05:38 pagure.issue.comment.added -- lrossett commented on ticket fedora-infrastructure#9348: "staging rabbitmq certs and key" https://pagure.io/fedora-infrastructure/issue/9348#comment-688400 18:05:39 mboddu: Issue #9767: Cleanup master mirror alt/stage - releng - Pagure.io - https://pagure.io/releng/issue/9767 18:05:39 +1 18:05:53 I am doing it as we speak 18:06:01 So, low trouble, medium gain, ops? 18:06:14 +1 18:06:20 ah I was going to ask.. mboddu I updated the docs for archives 18:06:32 smooge: Awesome 18:06:42 smooge: Can you link it? 18:06:46 also you know, that reminds me of an old ticket... 18:07:21 .ticket 6801 18:07:22 nirik: Issue #6801: run hardlink on fedora-secondary - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/6801 18:07:47 there was one in infra-docs/sysadmin/sops so I updated and put it in https://pagure.io/fedora-infra/howtos/blob/master/f/archiving_a_fedora_release.md 18:08:14 nirik, thanks I remembered that one and was going to ask where/when to run it 18:08:27 so, I think there's 2 things there... 18:09:21 1) just running hardlink over it all to help mirrors. 2) 1 is not going to do any good long term unless we make sure the normal sync stuff hardlinks everything it should... ie, rawhide/branched syncs, updates-sync. 18:10:20 agreed 18:11:00 Yeah, agreed 18:11:34 I wonder if compose-partial-copy is not doing its thing? https://pagure.io/pungi-fedora/blob/master/f/nightly.sh#_171 18:11:35 where is compose-partial-copy upstream? 18:11:49 yeah, jinx. Thats just where I was going. 18:11:54 nirik: Haha, we are thinking the same thing - compose-utils 18:12:20 ^ I mean compose-partial-copy is part of compose-utils 18:13:36 so, how about we do a little investigation (perhaps hardlink -n) and refile this on compose-utils? 18:13:44 * nirik can do that 18:14:43 tha hard part is that branched/rawhide may have to know about each other... but it should be possible 18:15:24 ok, any other tickets? or blockers? or ? 18:15:43 None from me 18:16:57 none from me 18:17:21 oh, looks like compose-partial-copy passes any arguments it doesn't know to rsync... so perhaps we can just add some --link-dest calls. 18:17:26 ok, thanks everyone 18:17:29 #endmeeting