Bug #4753
closed
create gui for scheduled execution of sensor workflows on server
Added by Daniel Crawl over 14 years ago.
Updated over 13 years ago.
Description
Provide a GUI to specify workflows to periodically run on a server. Configuration parameters include: the workflow xml, how often to run the workflow, etc. Note that the gui should provide a read-only view of the workflow: allow the user to see the workflow, but not edit it (this helps disambiguate the functionalities of engineering view and vanilla kepler). Additionally, include a template capability to allow the same workflow for multiple sensors.
See figures 6 and 7 in https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans
This should have an option to run a workflow continuously.
Another idea is, can we change the frequency of a workflow execution based on sensor data? This might require adding a parameter for automatic management, e.g., if a value goes above a threshold, run x times faster.
This would be useful for any type of workflow, not just for the Engineering View.
Here are suggestions from Matt:
1)I in the scheduler, the list on the left should only show WF objects that can be scheduled.
2) Only being able to schedule wfs that have already been uploaded seems limiting. A better model would be to allow the user to schedule any wf (even local ones), but then prompt them that it will have to be uploaded to continue if its a local WF.
The third one - I make it as a new bug.
This a general bug. The specific bugs have been created and fixed.
changing bugs from REAP to Kepler product
Original Bugzilla ID was 4753
Also available in: Atom
PDF