infrastructure/ansible
1
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/group_vars/relvalconsumer

13 lines
660 B
Text
Raw Normal View History

More cleanup on the openQA AMQP stuff nirik and I went around and around a bit today and ended up back where we started, but with a clearer understanding of where that this. This explains it a bit better, and makes what's actually going on in various places clearer with the use of appropriate shared variables. This should not actually *change* anything at all when deployed. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-06-22 23:20:22 +02:00
# we use the openQA rabbitmq account for this role as they run
# on the same server and it's convenient. this means it's also
# safe and appropriate to use variables defined in the openqa
# group_vars. if we ever split the roles up we will have to create
# a separate account with separate creds
relvalamiconsumer_amqp_queue: "{{ openqa_amqp_this_username }}_relvalamiconsumer"
relvalconsumer_amqp_queue: "{{ openqa_amqp_this_username }}_relvalconsumer"
openqa etc: fix up and improve AMQP messaging configuration This is triggered by https://pagure.io/fedora-infrastructure/issue/11375 , but the changes are rather extensive. Unfortunately, some of the relevant files got messed up by the alphabetical sort thing that got run on several group variable files a while ago, so that confuses the diff a bit - I had to unwind those changes to make the files readable again in order to make these changes. Ultimately the goal here is to make the config more consistent and more functional - the variables used and their names should be more consistently related to what they're actually *for*, which I didn't entirely understand when setting this up. So we have variables for the username being used in each case and we use that variable where we're referring to the username, for instance. This should also make the whole thing about the cases where listeners on the openQA stg/lab instance need to listen to prod messages clearer, too. It also makes the user creation clearer by doing it explicitly, just once per user, instead of haphazardly doing it implicitly through the queue definitions. And finally it should also actually fix 11375, by giving the appropriate write permissions to each user. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-06-21 11:54:03 +02:00
Add a relvalconsumer role, run it on openQA servers for now relvalconsumer is the fedmsg consumer bot that creates Wikitcms release validation test events. Up till now it's just been running on one of my personal boxes; we should really move it to infra. Run it on the openQA servers for now, as there's nowhere more obviously correct, and I have root access there to fix problems. We add new inventory groups because it's *really important* that there be exactly one (no more, no less) production consumer at any given time. I don't want to just use the 'openqa' group for this because it's vaguely possible it could contain more than one host in future, and we really wouldn't want that to result in there being two production relvalconsumers running.
2016-11-30 13:21:24 -08:00
# This var should never be set for more than one machine
openqa etc: fix up and improve AMQP messaging configuration This is triggered by https://pagure.io/fedora-infrastructure/issue/11375 , but the changes are rather extensive. Unfortunately, some of the relevant files got messed up by the alphabetical sort thing that got run on several group variable files a while ago, so that confuses the diff a bit - I had to unwind those changes to make the files readable again in order to make these changes. Ultimately the goal here is to make the config more consistent and more functional - the variables used and their names should be more consistently related to what they're actually *for*, which I didn't entirely understand when setting this up. So we have variables for the username being used in each case and we use that variable where we're referring to the username, for instance. This should also make the whole thing about the cases where listeners on the openQA stg/lab instance need to listen to prod messages clearer, too. It also makes the user creation clearer by doing it explicitly, just once per user, instead of haphazardly doing it implicitly through the queue definitions. And finally it should also actually fix 11375, by giving the appropriate write permissions to each user. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-06-21 11:54:03 +02:00
relvalconsumer_prod: true
relvalconsumer: handle reporting image size bugs to Bugzilla This relies on changes in relvalconsumer itself and relval. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-09-19 13:00:09 -07:00
# this one probably shouldn't either
relvalconsumer_bugzilla_api_key: "{{ prod_relvalconsumer_bugzilla_secret_api_key }}"
Copy permalink