etc/celeryconfig.py is used by both the region controller code and the worker code.
Bug #1056250 reported by
Raphaël Badin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
Bug Description
The file etc/celeryconfig.py is currently used by the region controller and the cluster worker.
The region controller uses it to get BROKER_URL and the cluster worker uses everything else in that file (the MAAS-specific parameters and the celery config options).
That file should be split into 3 files:
- one for the celery config of the region controller, containing only the BROKER_URL setting (that is overridden by a the custom value put in maas_local_
- one for the cluster workers
- one for the master worker (compared to the "normal" cluster workers, only the CELERYBEAT_SCHEDULE setting should be different)
Related branches
lp:~rvb/maas/refactor-celerysettings
- Jeroen T. Vermeulen (community): Approve
-
Diff: 485 lines (+241/-122)11 files modifiedMakefile (+5/-3)
etc/celeryconfig.py (+6/-72)
etc/celeryconfig_cluster.py (+43/-0)
etc/celeryconfig_common.py (+65/-0)
etc/democeleryconfig.py (+9/-24)
etc/democeleryconfig_cluster.py (+35/-0)
etc/democeleryconfig_common.py (+33/-0)
services/celeryd/run (+0/-22)
services/cluster-worker/run (+20/-0)
services/region-worker/run (+22/-0)
setup.py (+3/-1)
| Changed in maas: | |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
