Code review comment for lp://staging/~caio1982/capomastro/celery-fixes

Awesome, Zygmunt! About the scheduler, we already use Rabbit anyway but it seemed the simplest way to go for such simple scenario, but I'll take a look at that today. As for the concurrency change, the Celery documentation says you can't spawn more than one beat otherwise you'll have unexpected runs of it (like I was seeing and Hexr also avoids with the same "hack" apparently). The only possible alternative I see is really having two separate initscripts, one for beat one for the worker, but I kind of feel it's not worth the trouble here. Comments?