remove fedmsg variables which define endpoints on other fedmsg systems

This commit is contained in:
Stephen Smoogen 2020-07-22 12:28:44 -04:00
parent e8c43f5663
commit 6e92ba25a7
4 changed files with 0 additions and 31 deletions

View file

@ -5,14 +5,6 @@ num_cpus: 2
freezes: true
# 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: odcs
wsgi_procs: 2
wsgi_threads: 2
tcp_ports: [
80,
# These ports all required for gluster

View file

@ -6,14 +6,6 @@ num_cpus: 2
# Set this to True for the F28 release and onwards.
freezes: false
# 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: odcs
wsgi_procs: 2
wsgi_threads: 2
tcp_ports: [
80,
# These ports all required for gluster

View file

@ -9,14 +9,6 @@ tcp_ports: [ 80, 443 ]
# To make things easy on the listening side (so avoid contention of binding ports), let's set the pkgs boxes to active fedmsg.
fedmsg_active: True
# 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: pagure
wsgi_procs: 6
wsgi_threads: 6
pagure_static_uid: 600

View file

@ -5,13 +5,6 @@ max_mem_size: 32768
num_cpus: 4
tcp_ports: [ 80, 443, 8444, 8443, 8445 ]
# 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: pagure
wsgi_procs: 4
wsgi_threads: 4
pagure_static_uid: 600