openerp-community team mailing list archive

[ferdinand <office@xxxxxxxxxx>]

On 03/04/2013 07:15 PM, Daniel Reis wrote:

Hello Daniel!
We have developed a very robust timed_job module (instead of the 
standard cron)
it is especially usefull for long running jobs (client has data 
transfers of multiple hours, possible line failures etc)

http://bazaar.launchpad.net/~camptocamp/c2c-rd-addons/6.1/files/head:/timed_job/
http://bazaar.launchpad.net/~camptocamp/c2c-rd-addons/7.0/files/head:/timed_job/ 
(not tested yet)

Executes job at a specific point in time and repeats this at a 
time-interval.

Main features:
 - Executes a function "Function" on object "Object" with arguments 
"Arguments"
 - Starts the function at precise time "Start Time" (or on following 
periods, see below)
 - Periodic execution according to specified, precise intervals (see below)
 - Jobs may be executed in parallel, according to their start time
 - Double-start protection (do not execute the same job more than once 
in parallel)
 - The termination of the last successful execution is stored ("Last 
Execution Time")
 - Jobs are terminated when the server terminates
 - Insertion, deletion of jobs take immediate effect
 - Optionally, the missed executions can be repeated after a server 
outage ("Repeat Missed")
 - Optionally, a fixed number of execution times can be specified 
("Number of Calls")
 - Optionally, a notification mail will be sent in case of errors
 - Optionally, an execution dependency between jobs during 
server-startup can be specified ("Startup Predecessor")
   This specifies the job that has to be executed in advance during a 
server-startup.


Interval Types:
 - 'Minutes'       : Jobs are executed at "Interval Number" minutes 
relative to "Start Time"
 - 'Hours'         : Jobs are executed at "Interval Number" hours 
relative to "Start Time"
 - 'Days'          : Jobs are executed at "Interval Number" days at 
"Start Time"
 - 'Days of Week'  : Jobs are executed at specified weekday (according 
to ISO-numbering: 1=monday, 2=tuesday, ..., 7=sunday) at "Start Time"
 - 'Days of Month' : Jobs are executed at specified day of month at 
"Start Time" (1=first day, 2=second day, -1=ultimo).


Notes:
Carefully planned time-triggered jobs can be very resource-efficient.

When using interval type 'Days', it is assumed that the start day is 
irrelevant.
Note that - depending on the calendar and on the interval - this day 
will shift anyway over years.
The implementation calculates the interval relative to the "Last 
execution time".
Therefore, by deleting/reinserting of a job this day can be specified.

With "Startup Predecessor" complex dependency trees can be specified.
Circular dependencies are (obviously) not allowed.

"Repeat Missed" and "Startup Predecessor" have a necessary - but not 
obvious - drawback:
During server startup, those jobs have to be executed prior to any other 
job - this may take a long time.
Use those features judiciously.

Depending on the log_level of the server, information (elapsed time / 
CPU time) about the executed jobs are written to the server log.

The specified 'Function' must be known to the 'Object'.

The object 'Timed Job' provides two convenience functions for testing 
and sanity:
 - test(self, cr, uid, args=[]) : for testing
   - args[0] is a floating point number of seconds that this function 
will last
   - args[1] is a String that will be written to the server log

 - thread_watchdog(self, cr, uid, args=[]) : checks all threads and 
their states and writes anomalies to the server log


Programmatic interface :
 - _time_granule: A datetime.timedelta (default 10sec) that specifies 
the sparse time base (a value of 0 will not work!)
 - _max_scheduler_delta: A datetime.timedelta (default 6hours) that 
specifies the maximum interval for the scheduler to be executed

> Hello all,
>
> I need for OpenERP to create recurring tasks - to use for maintenance 
> plans (monthly, yearly, ...).
> The standard "subscription" module is too limited.
>
> So I'm considering building a "subscription" module alternative, with 
> more capabilities. It would be enough to work with any Model.
>
> I wonder if someone already did that, and if someone also also has the 
> same need?
>
> Regards
> Daniel Reis
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp