[Pulp-dev] "Internal" periodic tasks in Pulp3?

[Brian Bouterse]

This came out of IRC and discussion on a Pulp3 MVP call...

In Pulp2 we had three "internal" periodic tasks [0] that would do things
like database maintenance. The "nice to have" maintained periodic tasks can
be left out of the Pulp3 MVP, but @mhrivnak identified that '
download_deferred_content' is required for lazy downloading correctness.

Can others confirm that for Pulp3 we will require the
download_deferred_content Celery task?

Once we confirm ^, I want to discuss why we should not implement it in
Pulp3 how we did in Pulp2.

Note, internal periodic calls is not the same as "user scheduled calls".
Pulp3 will is not supporting user scheduled calls for reasons identified in
these blog posts [1][2].

[0]:
https://github.com/pulp/pulp/blob/fba39f1a82bbf8666df64999e89bc21d6d5ec897/server/pulp/server/async/celery_instance.py#L24-L40
[1]: http://pulpproject.org/2016/12/07/deprecating-nodes/
[2]: http://pulpproject.org/2016/10/31/pulp-3.0-mvp/

-Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170328/a348ab1f/attachment.htm>