Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

Enabling koji for internal machines

Browse source 
Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
This commit is contained in:
Samyak Jain 2024-08-13 21:25:31 +05:30
parent 0e4e647574
commit 9465ff33a1
2 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

4
inventory/group_vars/koji
View file

@ -1,8 +1,8 @@
---
# Define resources for this group of hosts here.
custom_rules: [
# Needed for keepalived
'-A INPUT -d 224.0.0.0/8 -j ACCEPT', '-A INPUT -p vrrp -j ACCEPT']
# block proxy01 / proxy10 for branching
'-A INPUT -s 10.3.163.74/32 -j REJECT', '-A INPUT -s 10.3.163.75/32 -j REJECT']
docker_registry: "candidate-registry.fedoraproject.org"
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:

6
roles/koji_hub/templates/hub.conf.j2
View file

@ -74,11 +74,11 @@ MissingPolicyOk = False
# KojiTraceback = normal
## These options are intended for planned outages
ServerOffline = True
#ServerOffline = True
#OfflineMessage = 'planned outage see https://www.fedorastatus.org'
#OfflineMessage = 'koji is being migrated to a new datacenter'
OfflineMessage = 'We are in the middle of branching new fedora release'
LockOut = True
#OfflineMessage = 'We are in the middle of branching new fedora release'
#LockOut = True
## If ServerOffline is True, the server will always report a ServerOffline fault (with
## OfflineMessage as the fault string).