Execution scheduler

Andy
Dear Carlo,
do you have a specification of your needs? I would be interested in reading them. It would be useful for us to know what has to be scheduled, how often, and what happens to the output, errors, logs etc. Are we talking about a cron type scheduler? If this is the case I would write a device server which implements similar functionalities as cron. Having it as a device server instead of standalone cron means is part of the control system and it can be configured using the standard tango tools.
Ciao
Andy

Dear Andy,
sorry for late answer
I' very interested in a standard Tango device which work more or less as the *nix AT command, or cron daemon. Simone is implementing an Orb Based multi-threading version with somehow different inner working and different specs, I think.
In my view both approaches will resolve my problem, but I fear it is a waste of efforts to have two similar versions. I think we need to check if we can merge the efforts.

For us the specifications are:
We need multi-threading
We expect to have priorities but not more than one queue
We need possibility to list/change/remove pending command
Our expected granularity is 1sec or better, The optimal precision is better than .1sec
We need commands (we can implement write_attributes as a command)

I think this answer also contains the answer to Ingvord.

Bye
Carlo
—-
Carlo Baffa INAF - Osservatorio Astrofisico di Arcetri
baffa@arcetri.astro.it Largo Fermi 5
http://www.arcetri.astro.it/~baffa/ I-50125-Firenze ITALY
What about the usage of a continuous integration server like Jenkins, originally made as a cron interface on steroid?

We use such approach at MAXIV for the start/shutdown of the RF modulator and many other things. It's easy to configure, has the advantage to keep a log, to be accessible from any web browser. The actions can be programmed with PyTango directly in Jenkins or execute any program of the system. It even logs the user with an ldap integration.

my 20 cts,
Vincent
Vincent Hardion
Control System
MAX IV Laboratory
hardion
What about the usage of a continuous integration server like Jenkins, originally made as a cron interface on steroid?

We use such approach at MAXIV for the start/shutdown of the RF modulator and many other things. It's easy to configure, has the advantage to keep a log, to be accessible from any web browser. The actions can be programmed with PyTango directly in Jenkins or execute any program of the system. It even logs the user with an ldap integration.

Dear Vincent
Thank you for your suggestion. I had in mind a more 'at-like' and integrated solution, but this can be a nice approach, I will look into it.
Bye
Carlo
—-
Carlo Baffa INAF - Osservatorio Astrofisico di Arcetri
baffa@arcetri.astro.it Largo Fermi 5
http://www.arcetri.astro.it/~baffa/ I-50125-Firenze ITALY
 
Register or login to create to post a reply.