Package: ztfy.scheduler
ContentsWhat is ztfy.scheduler ?How to use ztfy.scheduler ?Changelog0.5.20.5.10.5.00.4.90.4.80.4.70.4.60.4.50.4.40.4.30.4.20.4.10.4.00.3.40.3.30.3.20.3.10.3.00.2.20.2.10.20.1What is ztfy.scheduler ?ztfy.scheduler is a base package for those which need to build scheduled tasks which can run inside
a ZTK/ZopeApp based environment (ZEO is required !). These tasks can be scheduled:on a cron-style base,at a given date/time (like the “at” command)or at a given interval.Scheduling is done through the APScheduler (http://packages.python.org/APScheduler/) package and
so all these kinds of tasks can be scheduled with the same sets of settings. But tasks management
is made through a simple web interface and tasks running history is stored in the ZODB.On application start, the scheduler is run in a dedicated ZeroMQ process, which is also used to
handle synchronization between tasks settings and scheduler jobs.Tasks logs can be stored in the ZODB for a variable duration (based on a number of iterations).
These log reports can also be sent by mail, on each run or only when errors are detected.How to use ztfy.scheduler ?A set of ztfy.scheduler usages are given as doctests in ztfy/scheduler/doctests/README.txtChangelog0.5.2allow multiple recipients of task execution report0.5.1removed condition on debug mode run button0.5.0added task execution menu to run in debug mode without using ZMQ process0.4.9updated french translation0.4.8added tasks attributes relatives to empty reports handling0.4.7use “tztime” function in history sorting0.4.6added one second before checking ZMQ processes startup0.4.5remove ZTFY.security resources dependencies0.4.4convert roles edit forms to dialogs0.4.3register ZMQ scheduler process exit callback function0.4.2added system command execution task (local, or remote throught SSH)added option to execute a task immediately on user’s request0.4.1removed title from jobs list template0.4.0complete package refactoring, with tasks and scheduler jobs synchronization based on a
dedicated ZeroMQ process0.3.4changed package source layout0.3.3implement ztfy.security ILocalRoleManager interface0.3.2start and stop scheduler when scheduler utility is registered or unregistered, instead
of when it’s added or removedremove scheduler from schedulers handler when scheduler is stopped0.3.1update ShelveJobStore to take care of specific file systems configurations, because
sometimes shelve modification time is not updated when “sync()” is called. From now on
jobs configuration timestamp is stored in shelve and a blocking file lock is used to
prevent concurrent modifications in it. At least it seems to work on Linux, any feedback
concerning other OS is still welcome…0.3.0refactoring to follow last releases of ztfy.skin and ztfy.jqueryui packagesredefined interfaces so that tasks scheduling mode (cron-style,
interval-style…) can be defined on a per-task basis and is not bound
to the task class; new scheduling modes can also be added via registered
utilitiesstore tasks execution log in tasks historyadd an “URL getter” task, which can be used to call a remote “management”
URL on periodic basisadd username/password/realm to ZEO connectionsmodify ZODB packer task to be able to pack another remote database
instead of only those to which scheduler is definedimproved handling of transactions and conflict errors0.2.2changed ISite package import0.2.1updated database automatic upgrade code0.2migrated to ZTK-1.1integrated ZODBPackerTask (moved from ztfy.blog package)0.1initial release