Refactor #1084
Updated by bmbouter over 9 years ago
Historically, Pulp has used the celery Results backend, but I don't think its needed anymore. By using it we are having mongoDB issues (see #956). The results backend was used in Pulp 2.4 so the resource_manager could tell httpd which queue to send a task into but that is being done differently now. h2. Deliverables * Remove the "create_mongo_config()":https://github.com/pulp/pulp/blob/01fcf261c38f9b4b057839980f892f85a8697a27/server/pulp/server/async/celery_instance.py#L36-L70 function and it's associated tests * Have Pulp stop having celery connect to MongoDB at all by removing "the mongodb and results config":https://github.com/pulp/pulp/blob/01fcf261c38f9b4b057839980f892f85a8697a27/server/pulp/server/async/celery_instance.py#L75-L76 and fixup associated tests. * Write a migration to delete the celery_taskmeta collection * Write a release note for this change * Run the integration suite before and after and ensure that this change does not break anything. h2. QE instructions: * Verify that the migration removes the celery_taskmeta collection * Verify the release notes * Verify that the fix which includes this change passes a full regression test
.