koji_hub: put in hotfixed kojira and config for it

The stock 1.21.1 kojira has a number of problems.
It only does deletes rarely as part of the main thread, so if you are
needing to delete a ton of old repos it will never get to them all.
Also, it checks for it's running newrepos at a place in the loop that
causes it to take a lot longer to notice when it's hit the max for
newrepos.

So, this is the 1.21.1 version, and we will check in the diff/hotfix
which is upstream head version + several patches.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2020-06-27 11:16:21 -07:00
parent 97878de974
commit 5521021287
3 changed files with 1165 additions and 1 deletions

1148
roles/koji_hub/files/kojira Executable file

File diff suppressed because it is too large Load diff

View file

@ -463,3 +463,16 @@
tags:
- files
- koji_hub
# for now we have a patched version of kojira
# Based on the 1.21.1 version
# With:
# https://pagure.io/koji/pull-request/2140.patch
# https://pagure.io/koji/pull-request/2340.patch
# Hopefully all merged in 1.22.
#
- name: copy in patched kojira
copy: src=kojira dest=/usr/sbin/kojira
tags:
- files
- koji_hub

View file

@ -36,6 +36,9 @@ repo_tasks_limit=15
krb_rdns=false
serverca = /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
;how soon (in seconds) to clean up expired repositories. 1 week default
deleted_repo_lifetime = 604800
;how soon (in seconds) to clean up dist repositories.
;we want this super long so we don't delete latest repos
;just set this to 6 months for now.
@ -53,4 +56,4 @@ check_external_repos = True
; every cycle. File would contain information about how long these
; tags are expired and what is the computed score for them. This can
; be used to debug and check in realtime the actual performance.
;queue_file = /var/tmp/kojira-queue
queue_file = /var/tmp/kojira-queue