It would be useful to be able to "schedule" an exit to happen when an application is stopped. This allows application writers to start the Orchestrator, run a batch script to start an application (which stops itself using the supervisor API), and have the Orchestrator return control to the caller without having to end the process from the outside.
It would also be useful to "schedule" an exit when the batch queue is empty, to better resolve errors from scripts.
The primary beneficiary would be for people using the batch capabilities of the Orchestrator to perform multiple similar runs in sequence (parameter sweeps for example).
It would be useful to be able to "schedule" an exit to happen when an application is stopped. This allows application writers to start the Orchestrator, run a batch script to start an application (which stops itself using the supervisor API), and have the Orchestrator return control to the caller without having to end the process from the outside.
It would also be useful to "schedule" an exit when the batch queue is empty, to better resolve errors from scripts.
The primary beneficiary would be for people using the batch capabilities of the Orchestrator to perform multiple similar runs in sequence (parameter sweeps for example).