[katello-devel] Batch Jobs?

[Justin Sherrill]

On 03/26/2013 10:44 AM, Tom McKay wrote:
>
> ----- Original Message -----
>> From: "Cliff Perry"<cperry at redhat.com>
>> To: "Bryan Kearney"<bkearney at redhat.com>
>> Cc: "katello-devel"<katello-devel at redhat.com>
>> Sent: Tuesday, March 26, 2013 10:40:49 AM
>> Subject: Re: [katello-devel] Batch Jobs?
>>
>> On 26/03/13 11:11, Bryan Kearney wrote:
>>> What is the current thinking around batch jobs? Is this cron which
>>> calls
>>> into a REST call, or build a built in scheduling engine?
>> not using the OS cron daemon should be solution, IMHO. Something like
>> quartz.
>>    - Just because it makes the app more portable vs tied to the OS and
>> potentially being broken future Fedora's, such as if they
>> dramatically
>> change cron for say systemd - or some such. :)
>>
>> Cliff
And you have auth concerns, tying up other things from happening 
potentially, editing of cron files if you want user-scheduled tasks.

>>
>>
>>> Examples I can think of include:
>>> * manifest update
>>> * duplicate checking
>>> * orphan checking
>>> * syncing
>>>
>>> -- bk
>>>
>
> How are repo sync plans done now?
Pulp has built in scheduling with its own (ISO approved!) date/schedule 
format.   We just tell pulp what the schedule is and it does its thing.

-Justin
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel