zlopez/ansible
1
0
Fork 0
forked from infra/ansible
Code Pull requests Activity
ansible/inventory/group_vars/relvalconsumer_common

27 lines
1.3 KiB
Text
Raw Normal View History

Convert relvalconsumer to fedora-messaging Following the basic scheme I set up for fedora_openqa, hope it's all right... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-18 16:40:07 -07:00
# we need this for our fedora-messaging consumer as it is not allowed
# to create queues on the infra AMQP broker, by broker config
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_amqp_passive: true
# fedora-messaging email error reporting settings
relvalconsumer_amqp_mailto: ["adamwill@fedoraproject.org", "lruzicka@fedoraproject.org"]
relvalconsumer_amqp_smtp: bastion
# fedora-messaging relvalconsumer settings: most of these are the same
# for prod and stg as they both must listen for prod messages. Only
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
# the queue names differs (so is set in the non-common files).
#
# 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
relvalconsumer_amqp_url: "{{ openqa_amqp_prod_url }}"
relvalconsumer_amqp_cacert: "{{ openqa_amqp_prod_cacertfile }}"
relvalconsumer_amqp_cert: "{{ openqa_amqp_prod_certfile }}"
relvalconsumer_amqp_key: "{{ openqa_amqp_prod_keyfile }}"
Inventory group/host variables: Sort yaml This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2021-11-16 13:27:57 -08:00
relvalconsumer_amqp_routing_keys: ["org.fedoraproject.prod.pungi.compose.status.change"]
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: update AMI consumer routing keys This should cover both before and after https://pagure.io/cloud-image-uploader/pull-request/28 if it gets merged. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-09-12 16:58:36 -07:00
relvalamiconsumer_amqp_routing_keys: [
"org.fedoraproject.prod.fedora_image_uploader.published.v1.aws",
"org.fedoraproject.prod.fedora_image_uploader.published.v1.aws.#"
]
Copy permalink