18:00:01 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:01 <zodbot> Meeting started Tue Aug  4 18:00:01 2020 UTC.
18:00:01 <zodbot> This meeting is logged and archived in a public location.
18:00:01 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:01 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:01 <nirik> #chair mboddu nirik smooge pingou
18:00:01 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:01 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:01 <zodbot> Current chairs: mboddu nirik pingou smooge
18:00:01 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:02 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:03 <nirik> #topic Tickets needing review
18:00:04 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:13 <pingou> ó/
18:00:15 <smooge> hallo
18:01:03 <smooge> I have tickets and am ready to do them
18:01:22 <smooge> .ticket 9196
18:01:23 <zodbot> smooge: Issue #9196: arm packager hardwar not accessible (32 bit and 64 bit) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9196
18:01:47 <smooge> This is going to need the RDU-CC cage set up which is not going to happen by the time the person asked for it to be
18:02:31 <nirik> yeah, I'd say close and point to the still down stuff page.
18:02:43 <nirik> and i would really like to at least get a plan for it someday
18:03:07 <smooge> so would I.. my week got sidelined
18:03:12 <nirik> want me to mod tickets?
18:03:52 <fm-admin> pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#9196 https://pagure.io/fedora-infrastructure/issue/9196
18:03:53 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#9196: groomed, hardware, and 2 others https://pagure.io/fedora-infrastructure/issue/9196
18:03:54 <fm-admin> pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#9196: "arm packager hardwar not accessible (32 bit and 64 bit)" https://pagure.io/fedora-infrastructure/issue/9196#comment-669150
18:04:07 <smooge> sorry was typing in items
18:04:16 <smooge> probably needs something nicer than what I put in
18:04:31 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#9196: "arm packager hardwar not accessible (32 bit and 64 bit)" https://pagure.io/fedora-infrastructure/issue/9196#comment-669152
18:04:51 <smooge> that was it for tickets in infra
18:05:04 <smooge> I am not sure mboddu is available for releng tickets
18:05:13 <nirik> .releng 9653
18:05:14 <zodbot> nirik: Issue #9653: new GPG keys for Fedora 34 - releng - Pagure.io - https://pagure.io/releng/issue/9653
18:05:43 <nirik> there is this one ^ which we should do in the next few days. We also need to resign things with it so we can have rawhide resigned after branching
18:05:50 <smooge> so I was thinking.. why make new keys anymore.. just use the same ones until they get broken
18:06:41 <nirik> Lets just stop signing things... would save a ton of work. ;)
18:06:48 <smooge> also we should move to 512 bit keys.. there are tons of prime numbers below that which were never used.
18:06:49 <nirik> anyhow, thats it that I see for releng.
18:06:52 <smooge> that wokrs too
18:07:33 <smooge> who makes new keys?
18:07:49 <smooge> any existing tickets needing discussion?
18:07:53 <nirik> me or mohan
18:08:04 <nirik> there's a sop.
18:08:27 <nirik> so, due to working on s390x all day yesterday, I haven't gotten very far with stg...
18:08:37 <nirik> also it's kinda needing proxy01.stg to work
18:08:55 <nirik> I'll start building out other things this week
18:09:05 <nirik> we need to file and announce outages next week
18:09:18 <smooge> mgalgoci looks booked solid til next week so I am not sure when it will happen
18:09:45 <smooge> I was going to have a meeting with him this afternoon but I had to cancel due to other issues
18:09:57 <smooge> I will try to get an answer by tomorrow
18:10:34 <nirik> ok
18:10:50 <nirik> we also need to meet on budgets and to do our talk for nest. ;)
18:11:21 <nirik> anyhow, nothing more here from me.
18:11:33 <mobrien> I have a question
18:11:56 <mobrien> its about a new region for the proxies
18:12:01 <smooge> sure
18:12:26 <mobrien> I created this PR earlier after having a look at the SOP https://pagure.io/fedora-infra/ansible/pull-request/190#
18:13:03 <mobrien> If that is correct and accepted and run is there more to do or is that it?
18:13:21 <smooge> .. oh the dns git repo
18:13:49 <nirik> yeah, in dns git there's more changes needed.
18:14:53 <mobrien> I was thinking there would be some stuff on the DNS repo. Would I be able to get one of you to help me with that some time in the future and I can document it afterward?
18:15:27 <smooge> basically each of the /srv/git/dns/*.cfg files will need to know of the AFR region and so will the check-domains and do-domains scripts. Then it needs to be run twice to create the region and push it out
18:15:41 <smooge> then the update to the named.conf can be done
18:16:34 <mobrien> Ok. I can have a look at it myself and create a patch for you guys to review.
18:16:52 <mobrien> It will need to be done for South America afterward as well
18:16:53 <smooge> mobrien, does that make sense? It is not under pagure and is a repo that needs some serious work someday
18:17:49 <smooge> sees dns repo is 4.3 GB in size again
18:17:53 <mobrien> Ya, I have some familiarity with the dns repo.
18:17:56 <nirik> yeah.
18:18:19 <smooge> ok cool
18:18:54 <mobrien> ok thanks. I'll hopeully have something for you to review Thursday/Friday
18:19:09 <smooge> cool. thank you for your work
18:19:27 <mobrien> No prob, glad to be useful
18:19:30 <darknao> I also have a question :)
18:20:18 <darknao> I've not been here long enough to know if it's a real issue or not, but the mail queue on bastion01 seems a little bit saturated
18:20:20 <smooge> darknao, hi.
18:20:33 <darknao> hi :)
18:20:52 <smooge> yeah.. that is 'normal'. Maybe not good.. but 'normal'
18:21:28 <nirik> often we get people who subscribe to everything and then their provides throttles them
18:21:32 <darknao> the active queue is full, and there is like 140k mail in it, all going to the same email
18:22:03 <smooge> I am thinking we were looking to go to multi-queue..
18:22:13 <smooge> but never got to it. Do you have any ideas on it?
18:22:15 <nirik> and indeed... 138k emails are going to one user
18:22:39 <nirik> and gmail is throttling them
18:23:02 <darknao> I think this is slowing down all other mail deliveries, including those for redhat domain
18:23:04 <smooge> nirik, when I see this I usually wipe the queue of those messages as it usually means i will get 138k bounce emails to admin
18:23:33 <nirik> well, ideally we:
18:23:40 <nirik> disable notifications for them
18:23:46 <nirik> wipe all the emails out of queue
18:23:53 <nirik> mail them that they shouldn't enable *
18:24:37 <smooge> mailq | tail +2 | awk 'BEGIN { RS = "" } / foobaz@\gmail.com/ { print $1 }' | tr -d '*!' | postsuper -d -
18:24:47 <smooge> darknao, thanks for the heads up on that.
18:24:55 <smooge> now to go figure out how to disable notifications
18:24:59 <smooge> that is the part I never figure out
18:25:05 <darknao> you're welcome :)
18:25:17 <darknao> glad to help
18:25:22 <smooge> ok going to end this meeting and we can discuess htis more out of standup
18:25:25 <smooge> #endmeeting