WarlockFish/fedora-infra_ansible
1
0
Fork 0
mirror of https://pagure.io/fedora-infra/ansible.git synced 2026-02-02 20:59:02 +08:00
Code Issues Packages Projects Releases Wiki Activity

rabbitmq: switch datacenter out for rdu3

Browse Source 
This was useful when we had clusters in iad2 and rdu3, but it didn't
actually quite work then and it definitely doesn't now. :)

Datacenters like 'aws' do not have their own clusters, they use the one
in rdu3. So, just switch it back to hard coding.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi
2025-07-17 18:00:47 -07:00
parent ca1185ec42
commit 72789a919f
6 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
roles/rabbitmq_cluster/tasks/main.yml
View File

@@ -418,7 +418,7 @@
vhost: /public_pubsub
vars:
federation_upstream_value:
uri: "amqps://pubsub_federation:@rabbitmq01{{env_suffix}}.{{datacenter}}.fedoraproject.org/%2Fpubsub?cacertfile=%2Fetc%2Frabbitmq%2Fca.crt&certfile=%2Fetc%2Frabbitmq%2Fpubsub_federation%2Fclient_cert.pem&keyfile=%2Fetc%2Frabbitmq%2Fpubsub_federation%2Fclient_key.pem&verify=verify_peer&server_name_indication=rabbitmq{{env_suffix}}.fedoraproject.org&auth_mechanism=external"
uri: "amqps://pubsub_federation:@rabbitmq01{{env_suffix}}.rdu3.fedoraproject.org/%2Fpubsub?cacertfile=%2Fetc%2Frabbitmq%2Fca.crt&certfile=%2Fetc%2Frabbitmq%2Fpubsub_federation%2Fclient_cert.pem&keyfile=%2Fetc%2Frabbitmq%2Fpubsub_federation%2Fclient_key.pem&verify=verify_peer&server_name_indication=rabbitmq{{env_suffix}}.fedoraproject.org&auth_mechanism=external"
ack-mode: "on-confirm"
- name: Configure a policy to federate the pubsub topic exchange to public_pubsub

8
roles/rabbitmq_cluster/templates/rabbitmq.conf.j2
View File

@@ -67,7 +67,7 @@ default_user_tags.administrator = true
## Clustering
## =====================
##
cluster_name = {{env_prefix}}{{datacenter}}.fedoraproject.org
cluster_name = {{env_prefix}}rdu3.fedoraproject.org
cluster_partition_handling = autoheal
## Make clustering happen *automatically* at startup. Only applied
@@ -77,9 +77,9 @@ cluster_partition_handling = autoheal
##
cluster_formation.peer_discovery_backend = rabbit_peer_discovery_classic_config
cluster_formation.classic_config.nodes.1 = rabbit@rabbitmq01{{env_suffix}}.{{datacenter}}.fedoraproject.org
cluster_formation.classic_config.nodes.2 = rabbit@rabbitmq02{{env_suffix}}.{{datacenter}}.fedoraproject.org
cluster_formation.classic_config.nodes.3 = rabbit@rabbitmq03{{env_suffix}}.{{datacenter}}.fedoraproject.org
cluster_formation.classic_config.nodes.1 = rabbit@rabbitmq01{{env_suffix}}.rdu3.fedoraproject.org
cluster_formation.classic_config.nodes.2 = rabbit@rabbitmq02{{env_suffix}}.rdu3.fedoraproject.org
cluster_formation.classic_config.nodes.3 = rabbit@rabbitmq03{{env_suffix}}.rdu3.fedoraproject.org
## This node's type can be configured. If you are not sure
## what node type to use, always use 'disc'.

6
roles/rabbitmq_cluster/templates/rabbitmq.config.j2
View File

@@ -14,9 +14,9 @@
{auth_mechanisms, ['EXTERNAL']},
%% Here goes the cluster config
{cluster_nodes, {['rabbit@rabbitmq01{{env_suffix}}.{{datacenter}}.fedoraproject.org',
'rabbit@rabbitmq02{{env_suffix}}.{{datacenter}}.fedoraproject.org',
'rabbit@rabbitmq03{{env_suffix}}.{{datacenter}}.fedoraproject.org'],
{cluster_nodes, {['rabbit@rabbitmq01{{env_suffix}}.rdu3.fedoraproject.org',
'rabbit@rabbitmq02{{env_suffix}}.rdu3.fedoraproject.org',
'rabbit@rabbitmq03{{env_suffix}}.rdu3.fedoraproject.org'],
disc}},
%% How to respond to cluster partitions.