ansible/inventory/group_vars/mbs_frontend_stg
Kevin Fenzi 580cd252c5 Inventory group/host variables: Sort yaml
This was done using yq (
https://mikefarah.gitbook.io/yq/operators/sort-keys )

Doing things this way makes it much easier to see if a variable is set
in a file or if two hosts differ in what variables they set. Hopefully
we can keep things sorted moving forward.

Basically this means just sort a-z anything you add to any host or group
vaiable and it will be in the right place.

Additionally, this enforces 'normal' intent rules for all the variable
files which we should also try and obey. 2 spaces for first level, 3 for
next, etc. When in doubt you can run yq on it.

This should cause NO actual vairable changes, it's all just readability
fixing for humans, ansible parses it exactly the same.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00

39 lines
1.4 KiB
Text

---
csi_primary_contact: Modularity WG - modularity-wg-members@fedoraproject.org
csi_purpose: Run the module-build-service frontend API.
csi_relationship: |
The apache/mod_wsgi app is the only thing really running here
This host relies on db01 for its database of activity (what module builds
are in flight?)
It has no special credentials itself. When a module build it submitted, it
makes a note in the DB and publishes a fedmsg message. The mbs backend
nodes do all the work of talking to koji.
# For the MOTD
csi_security_category: Moderate
# Neeed for rsync from log01 for logs.
custom_rules: ['-A INPUT -p tcp -m tcp -s 10.5.126.13 --dport 873 -j ACCEPT', '-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j ACCEPT']
# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
- can_send:
- mbs.module.state.change
# Only the backend sends this message..
#- mbs.component.state.change
group: fedmsg
owner: fedmsg
service: mbs
lvm_size: 20000
mbs_broker_url: ""
mbs_frontend: true
mbs_num_workers: 3
mem_size: 4096
num_cpus: 1
tcp_ports: [80]
# Definining these vars has a number of effects
# 1) mod_wsgi is configured to use the vars for its own setup
# 2) iptables opens enough ports for all threads for fedmsg
# 3) roles/fedmsg/base/ declares enough fedmsg endpoints for all threads
wsgi_fedmsg_service: mbs
wsgi_procs: 2
wsgi_threads: 2