Difference between revisions of "SmartExecutor"
Luca.frosini (Talk | contribs) |
Luca.frosini (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | The SmartExecutor | + | The SmartExecutor service allows to execute "gCube Tasks". Each instance of the SmartExecutor service can run the "gCube Tasks" related to the plugins available on such an instance. |
| + | |||
| + | Each instance of the SmartExecutor service publishes descriptive information about the co-deployed plugins. | ||
| + | |||
| − | |||
Clients may interact with the Executor service through a library of high-level facilities that subsumes standard service stubs to simplify the discovery of available tasks in those instances. | Clients may interact with the Executor service through a library of high-level facilities that subsumes standard service stubs to simplify the discovery of available tasks in those instances. | ||
Each client can request to execute a Task or getting informations about the state of their execution. | Each client can request to execute a Task or getting informations about the state of their execution. | ||
| − | + | == General Information == | |
| − | |||
| − | === | + | == Plugins == |
| + | The SmartExecutor uses a ServiceEndpoint with Category: VREManagement and Name: SmartExecutor to publish information regarding the co-deployed plugins and their own information. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | == SmartExecutor interaction == | ||
The SmartExecutor service provides a client library to simplify the following procedures: | The SmartExecutor service provides a client library to simplify the following procedures: | ||
| Line 18: | Line 25: | ||
* monitor the execution of the running task. | * monitor the execution of the running task. | ||
| − | === | + | === Instance Discovery === |
| − | + | === Launching Tasks === | |
| − | === | + | |
| Line 28: | Line 34: | ||
| − | === | + | === Monitor Task Execution === |
| − | + | ||
| + | == Plugin Development == | ||
SmartExecutor plugins may have arbitrary size and dependencies but '''must''' include the following components: | SmartExecutor plugins may have arbitrary size and dependencies but '''must''' include the following components: | ||
* | * | ||
| − | |||
* | * | ||
| − | |||
* | * | ||
| − | |||
== Tasks == | == Tasks == | ||
| − | '''Note:''' | + | '''Note:''' Plugins are instantiated by the Executor and thus must have have a zero-argument constructor. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 12:19, 19 October 2015
The SmartExecutor service allows to execute "gCube Tasks". Each instance of the SmartExecutor service can run the "gCube Tasks" related to the plugins available on such an instance.
Each instance of the SmartExecutor service publishes descriptive information about the co-deployed plugins.
Clients may interact with the Executor service through a library of high-level facilities that subsumes standard service stubs to simplify the discovery of available tasks in those instances.
Each client can request to execute a Task or getting informations about the state of their execution.
Contents
General Information
Plugins
The SmartExecutor uses a ServiceEndpoint with Category: VREManagement and Name: SmartExecutor to publish information regarding the co-deployed plugins and their own information.
SmartExecutor interaction
The SmartExecutor service provides a client library to simplify the following procedures:
- discover service instances that can execute the target task. This requires interaction with the Information System.
- launch the execution of the task with one the discovered instances.
- monitor the execution of the running task.
Instance Discovery
Launching Tasks
Task Inputs
Monitor Task Execution
Plugin Development
SmartExecutor plugins may have arbitrary size and dependencies but must include the following components:
Tasks
Note: Plugins are instantiated by the Executor and thus must have have a zero-argument constructor.
Development Environment and Testing
This [Eclipse project] may be used to kick-off plugin development and testing.
