Closed Bug 568329 Opened 10 years ago Closed 10 years ago
[sumo] Install Rabbit
Much like AMO (bug 561459) we're going to be using RabbitMQ with Celery very soon. I hope we can piggyback on everything in that bug.
I don't think this is going to happen today because of the network issues. Dropping sev to stop the bug from paging. No guarantees though, might get to it anyway if things calm down. Please bump the severity back to major if it hasn't been touched by tomorrow morning.
Severity: major → normal
Per comment 1, we've just landed code in bug 563991 that depends on this. After we get RabbitMQ set up, you'll need to add the following line to the settings_local.py to get it to actually use Rabbit/Celery. CELERY_ALWAYS_EAGER = False
Severity: normal → major
This is really blocking testing. Can anyone take care of this?
Assignee: thardcastle → server-ops
Severity: major → critical
Re-assigning per mrz
Assignee: server-ops → jeremy.orem+bugs
10 years ago
Severity: critical → blocker
10:48 < oremj> jsocol: hey, what is going to be talking to rabbit and celery? 10:49 < oremj> app servers or the admin box? 10:49 < oremj> Do you guys have cron jobs?
(In reply to comment #5) > 10:48 < oremj> jsocol: hey, what is going to be talking to rabbit and celery? > 10:49 < oremj> app servers or the admin box? > 10:49 < oremj> Do you guys have cron jobs? App servers will send jobs. We don't have cron jobs (at the moment). Do we have an admin box?
This is up and running on stage.
Severity: blocker → normal
(In reply to comment #7) > This is up and running on stage. What's left to do, here? Is it open for installing the same thing on prod?
Yeah, open for installing on prod.
(In reply to comment #9) > Yeah, open for installing on prod. Any chance you can get to this ahead of time so we can minimize the downtime during the push?
Jeremy, is this still up and running for prod after the push yesterday?
Yes, it's ready to go.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.