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

Turn off fedmsg on ci-cc

Browse source 
This is done for two reasons:
a) We do not really care about sending fedmsg messages from this resultsdb
instance, they should rather be sent via the official one once they have
been synced accross.
b) Installing the base fedmsg role leads to a huge number of hosts that
fedmsg will try to listen to, in fact, it results in too many hosts that
fedmsg will try to connect to, leading to the core app of this host
(resultsdb-listener) to not listen to the host it is designed to listen
to (ci.centos.org) making this service effectively not working.

So by removing the base fedmsg role we'll ensure fedmsg only connects
to the hosts we care about and by removing resultsdb-fedmsg we won't try
to have resultsdb send fedmsg messages upon receiving new test results.

Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
This commit is contained in:
Pierre-Yves Chibon 2018-10-17 14:12:28 +02:00
parent ae3f91a0eb
commit a947f2ad13
1 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
playbooks/groups/ci.yml
View file

@ -28,7 +28,6 @@
when: deployment_type == "prod", tags: ['openvpn_client'] }
- postgresql_server
- apache
- { role: fedmsg/base }
tasks:
# this is how you include other task lists
@ -50,7 +49,6 @@
- /srv/web/infra/ansible/vars/{{ ansible_distribution }}.yml
roles:
- { role: taskotron/resultsdb-fedmsg, tags: ['resultsdb-fedmsg']}
- { role: taskotron/resultsdb-backend, tags: ['resultsdb-be'] }
- { role: taskotron/resultsdb-frontend, tags: ['resultsdb-fe'] }
- { role: taskotron/execdb, tags: ['execdb'] }