[Pulp-dev] Task Scheduling for Pulp 3
mhrivnak at redhat.com
Wed Sep 7 12:02:31 UTC 2016
Cron syntax is a great idea. There appears to be at least one nice python
library to parse and work with cron schedules:
There are a surprising number of edge cases to handle with task scheduling.
It would be helpful to just handle all of those in the same way cron does,
and document just that. It would save dev time and make the user experience
That said, I worry about migrating existing schedule data. ISO8601 allows
for a lot of possibilities. One that I don't think cron has is the ability
to run a task a specific number of times. If we do switch to something
different, we'll need to figure out up-front how to handle migration.
On Tue, Sep 6, 2016 at 4:52 PM, Brian Bouterse <bbouters at redhat.com> wrote:
> +1 to cron. The syntax is super simple , and I believe sysadmins
> already think of schedules in terms of cron.
> : https://en.wikipedia.org/wiki/Cron#Overview
> On 09/06/2016 04:47 PM, Patrick Creech wrote:
>> During the course of the Task modeling work for Pulp 3, it was mentioned
>> that some discussion should
>> he had around the use of ISO8601 date fields to control task scheduling.
>> So to start this conversation, I pose two questions:
>> 1) Should we do away with the use of ISO8601 date fields for scheduling
>> 2) If yes to 1, what scheduling format should we move to? There were
>> talks about utilizing a system
>> similar to cron to specify the schedules
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev