# User Schedulable Tasks ## Jan 4th 2023 ### Attendees: dkliban, dralley, bmbouter ## Agenda * Discussed PoC commit from @x9c4 * https://github.com/pulp/pulpcore/compare/main...mdellweg:pulpcore:dispatch_tasks * Overall it seems fine, but what to do about the arguments? * Recap of the main use cases: * Have periodic scheduling of sync's * Have periodic scheduling of orphan cleanup * Scheduling Task Sync as an attribute on a Repository seems workable * Scheduling Orphan cleanup does not seem workable because there isn't a persistant "orphan cleanup object" to attach the schedule onto * Overall to be generally useful tasking will need arguments to be part of the dispatch * This is really hard because... * The arguments need RBAC and Domains validation. The viewsets themselves provide this, but if users start handing object references for example to various viewsets each of those will need to be "revalidated" * Question? Why are we building this into Pulp? * One reason is because bmbouter overall believes users should not be configuring a second "cron dispatcher" for this feature set to work * why? * idea: let's explore separate containers that can be deployed next to pulp that can perform API interaction with Pulp at specified times * https://hub.docker.com/r/mcuadros/ofelia/ * we could bundle cron into the pulp docker image and use a different entry point like cron.sh, e.g. this is what nextcloud does