Opened 8 years ago
Last modified 7 years ago
#904 closed task
Implement an Open Grid Scheduler service extension — at Initial Version
| Reported by: | Nicklas Nordborg | Owned by: | Jari Häkkinen |
|---|---|---|---|
| Priority: | critical | Milestone: | Open Grid Scheduler service v1.0 |
| Component: | net.sf.basedb.opengrid | Keywords: | |
| Cc: |
Description
Reggie already has a lot of functionality for submitting and monitoring jobs on an Open Grid Scheduler cluster. In the future we may want to do the same from other extensions. For a number of reasons it is not a good idea to simply duplicate the functionality from Reggie:
- Each extension would need it's own monitoring service. It would be better to have a single service for this.
- Each service need to be able to identify which jobs it should monitor. Could for example be done by defining multiple queues on the cluster. It would be better to not require any special configuration on the cluster.
- Duplicating configuration files for accessing the cluster (though this also has the benefit that different user accounts can be used).
The new extension should include functions for submitting, monitoring and aborting jobs. Some sort of notification system must be implemented so that the extension that submitted the job is notified when the job has finished.
Reggie is also using the cluster for some simple operations not related to the Open Grid Scheduler. For example the "Check data files" functionality which uses a single node to execute a script immediately and the "Auto-analyze" functionality to monitor sequencing progress which is piggy-backed onto the Open Grid Scheduler monitoring but is executing a different script.
It will not be easy to untangle this and decide which functionality that should go where. We need to think about the details a bit more and we also need more support in the BASE core http://base.thep.lu.se/ticket/2027.
