614159 - [BAMO] Hook up a celeryd in prod

Status: RESOLVED INCOMPLETE

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Wil Clouser [:clouserw]]

We need a celeryd in production too.  I'm separating this from bug 614156 because I'm not sure if you need more hardware or what.  If this lives on the same cluster as AMO's celeryds we might need another box (not sure what kind of load we're looking at there, but this is processing high priority, albeit fast, jobs).

Comment 1

[Jeremy Orem [:oremj]]

If this is going to be super CPU intensive we may need more hardware. As far as processing in high priority I know Jeff has been using separate queues. We should ask him which would be best.

Comment 2

[Wil Clouser [:clouserw]]

(In reply to comment #1)
> If this is going to be super CPU intensive we may need more hardware. As far as
> processing in high priority I know Jeff has been using separate queues. We
> should ask him which would be best.

Yeah, this will be it's own queue.  I'm just saying it can't be sharing a lot of resources on the box.  FWIW, it's not particularly CPU intensive, just time sensitive.

Comment 3

[Jeremy Orem [:oremj]]

Please reopen when builder support celery.

Comment 4

[Jeremy Orem [:oremj]]

It looks like production builder still doesn't have a celery command.

Comment 5

[Daniel Buchner [:dbuc]]

It has been implemented in our edge builds and will be there for the next release in early Feb.

Comment 6

[Jeremy Orem [:oremj]]

Let's address this in the release. I've already set it up in preview.