What problem would this feature solve? ====================================== The django-celery package helps integrate Celery with Django. It was deprecated with Celery 3.1, and is no longer maintained. It will require changes to the Kuma code base to stop using it. Who has this problem? ===================== Code Maintainers How do you know that the users identified above have this problem? ================================================================== The last change to django-celery is July 2015. It may be incompatible with future versions of Django How are the users identified above solving this problem now? ============================================================ There is a migration path for some of django-celery's features to ones provided by the Celery package. Other features need to be abandoned or changed. Some of these require additional infrastructure, such a new result store (Redis, etc.), or a monitoring service behind the VPN Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== * Migrate Kuma out of SCL3 and into AWS, duplicating the current infrastructure * Add new services as needed to replace django-celery features * Migrate the code to use the new services * Migrate django-celery and django-celery-transactions functionality to built-in Celery functionality * Drop the django-celery and django-celery-transactions functionality. Is there anything else we should know? ====================================== I do not recommend making the needed infrastructure changes in SCL3, because it would require a large effort from operations and negatively impact the current stability of the SCL3 celery environment.
You need to log in before you can comment on or make changes to this bug.