I have a cluster of celery nodes with different celery configurations (celeryconfig.py & celery.py) along with different start & stop scripts. It is getting cumbersome to manage the different files.
Right now I hacked up my ansible automation to incorporate different config files but this seems dirty and will not scale.
Is there any way to handle all different configurations, a centralized way to manage the config files?
Any help appreciated, thanks!
Ansible is usually pretty good at this kind of thing.
There are several ways you can deal with this:
/path/to/celeryconfig.py --> /path/to/configs/<hostname>-celeryconfig.py