On Wed, Jul 29, 2015 at 09:22:56AM -0600, Kevin Fenzi wrote:
The addition of mm-frontend02 yesterday meant that all the dynamically
generated fedmsg config needs to add a entry for it.
This means the check/diff daily report is pretty large because all
these are pending.
I would like to run the master playbook with -t fedmsgdconfig and then
I don't think there will be any issues.
This will make the following changes on fedmsg enabled hosts:
--- before: /etc/fedmsg.d/endpoints.py
+++ after: /srv/web/infra/ansible/roles/fedmsg/base/templates/endpoints.py.j2
@@ -41,20 +41,24 @@
"tcp://ask02.%s:30%02i" % (suffix, i)
for i in range(6)
# The mirrormanager2 frontend runs as 2 processes with 1 thread each.
"tcp://mm-frontend01.%s:30%02i" % (suffix, i)
+ for i in range(2)
+ "mirrormanager2.mm-frontend02": [
+ "tcp://mm-frontend02.%s:30%02i" % (suffix, i)
for i in range(2)
# 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
"tcp://koschei01.%s:30%02i" % (suffix, i)
+1 for me