Project

Profile

Help

Issue #443

closed

pulp.server.managers.event.remote requires qpid.messaging

Added by rbarlow almost 8 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

I noticed today that pulp.server.managers.event.remote has these two import statements:

16 from qpid.messaging import Connection
17 from qpid.messaging.exceptions import ConnectionError, MessagingError

I believe we should strive to be message broker agnostic as an upstream project, so we should not require qpid.messaging. Here are two suggested fixes:

1) It has been proposed that we could simply remove the feature provided by this module. It may not be very useful, especially since users can now monitor Celery tasks.

2) We could rework this module to use Kombu for message broker abstraction.

I would like to suggest that we make this low priority on 2.4. It's not a regression, since we didn't support rabbitmq in 2.3. It would be nice though since we are trying to allow users to choose rabbitmq for 2.4.

+ This bug was cloned from Bugzilla Bug #1103354 +

Also available in: Atom PDF