Project

Profile

Help

Story #2341

As a Jenkins user, I can choose whether qpid or rabbitmq is used as the AMQP broker

Added by Ichimonji10 about 3 years ago. Updated almost 2 years ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

By default, Pulp uses qpid as its AMQP broker. However, at least one other AMQP broker is supported: rabbitmq. As a Jenkins user, I'd like to be able to provision a Pulp system with rabbitmq as the AMQP broker, and use that system for automated tests.

The motivation for this feature is the ongoing investigation into whether or not qpid locks up, and therefore causes Pulp to become unresponsive.

The steps for making rabbitmq the default AMQP broker are detailed here.

The steps boil down to the following:

dnf install rabbitmq-server python-gofer-amqp
# In [messaging] section, set "transport" 
# In [tasks] section, set "broker_url" 
vi /etc/pulp/server.conf
systemctl stop qpidd
systemctl disable qpidd
systemctl start rabbitmq
systemctl enable rabbitmq

History

#1 Updated by dalley almost 2 years ago

  • Project changed from Packaging to Infrastructure

Please register to edit this issue

Also available in: Atom PDF