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

Give an extra fedmsg endpoint for koschei-watcher.

Browse source
This commit is contained in:
Ralph Bean 2015-06-24 19:59:38 +00:00
parent 6a6d3ab34e
commit d26b6e837d
3 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

4
inventory/group_vars/koschei
View file

@ -18,8 +18,8 @@ koschei_bugzilla: bugzilla.redhat.com
tcp_ports: [ 80, 443,
# These 3 are for fedmsg. See also /etc/fedmsg.d/endpoints.py
3000, 3001, 3002,
# These 4 are for fedmsg. See also /etc/fedmsg.d/endpoints.py
3000, 3001, 3002, 3003,
]
custom_rules: [

4
inventory/group_vars/koschei-stg
View file

@ -18,8 +18,8 @@ koschei_bugzilla: partner-bugzilla.redhat.com
tcp_ports: [ 80, 443,
# These 3 are for fedmsg. See also /etc/fedmsg.d/endpoints.py
3000, 3001, 3002,
# These 4 are for fedmsg. See also /etc/fedmsg.d/endpoints.py
3000, 3001, 3002, 3003
]
custom_rules: [

5
roles/fedmsg/base/templates/endpoints.py.j2
View file

@ -78,13 +78,14 @@ config = dict(
for i in range(2)
],
# mizdebsk says he thinks we'll need three sockets. Two services
# mizdebsk says he thinks we'll need four sockets. Two services
# (koschei-resolver and koschei-polling) are only sending messages, one
# service (koschei-watcher) can both send and receive them. The wsgi
# webapp doesn't use fedmsg at all and all services are single-threaded
# koschei-watcher uses two endpoints
"koschei.koschei01": [
"tcp://koschei01.%s:30%02i" % (suffix, i)
for i in range(3)
for i in range(4)
],
# koji is not listed here since it publishes to the fedmsg-relay