Refactor #2158
closed
Remove pulp_celerybeat use of scheduled calls from database
Added by mhrivnak over 7 years ago. Updated over 4 years ago.
100%
Description
pulp_celerybeat (2.Y) currently loads scheduled calls from mongodb. The 3.0 MVP will not load any scheduled tasks from the database. The code that handles the loading of schedule from DB should be removed.
Related issues
Updated by mhrivnak over 7 years ago
- Blocked by Refactor #2087: create django models for task system added
Updated by mhrivnak over 7 years ago
- Related to Issue #1641: unit.server.db.model.test_dispatch.TestScheduledCallSave.test_new is non-deterministic added
Updated by bmbouter over 7 years ago
- Description updated (diff)
- Groomed changed from No to Yes
Updated by bmbouter over 7 years ago
This PR would be merged after the work I am doing on my branch. I've left the scheduler.py and worker_watcher.py untouched[0]. Those should be moved to pulp.tasking here[1].
Also this story does not mention that the pulp_celerybeat needs to record the workers correctly in addition to handling scheduled calls. If that is supposed to be a separate story please file one.
[0]: https://github.com/bmbouter/pulp/tree/2154-Belgian-Dubbel/server/pulp/server/async
[1]: https://github.com/bmbouter/pulp/tree/2154-Belgian-Dubbel/tasking/pulp/tasking
Updated by bmbouter over 7 years ago
- Related to Task #1978: Change the name of the scheduler worker from "scheduler" to "pulp_celerybeat" added
Updated by dkliban@redhat.com over 7 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Updated by mhrivnak over 7 years ago
- Related to Task #2176: Remove auto-disable feature of scheduled tasks added
Updated by mhrivnak over 7 years ago
Per PulpCon planning discussion, the MVP does not include the ability for a user to schedule tasks. We should revise this "refactor" issue accordingly.
Updated by dkliban@redhat.com over 7 years ago
- Subject changed from Convert pulp_celerybeat to use scheduled calls from django to Remove pulp_celerybeat use of scheduled calls from database
- Description updated (diff)
Updated the description and title to reflect the fact that 3.0 MVP will not execute any tasks using schedule data in the database.
Updated by dkliban@redhat.com over 7 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com over 7 years ago
Added by dkliban@redhat.com over 7 years ago
Revision 365f9fd0 | View on GitHub
Removes database backed celerybeat schedule
This change also converts worker watcher to use Django. This patch renames the scheduler to pulp_celerybeat.
closes: #2158 https://pulp.plan.io/issues/2158 closes: #2156 https://pulp.plan.io/issues/2156 closes: #1978 https://pulp.plan.io/issues/1978
blah
Updated by dkliban@redhat.com over 7 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|365f9fd0a0b09969e65ef6f112a7a973e2bb63cc.
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Removes database backed celerybeat schedule
This change also converts worker watcher to use Django. This patch renames the scheduler to pulp_celerybeat.
closes: #2158 https://pulp.plan.io/issues/2158 closes: #2156 https://pulp.plan.io/issues/2156 closes: #1978 https://pulp.plan.io/issues/1978
blah