SmartExecutor
The SmartExecutor acts as a container for gCube tasks, i.e. functionally unconstrained bodies of code that lack a network interface but can be deployed into the service and executed through its interface. In particular, gCube tasks are designed, packaged, and deployed as plugins of the SmartExecutor service.
An instance of the SmartExecutor publishes descriptive information about the co-deployed plugins, can execute them on demand on behalf of clients. 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.
The SmartExecutor uses a ServiceEndpoint with Category: VREManagement and Name: SmartExecutor to publish information regarding the co-deployed plugins and their own infroamtion.
Contents
Design
Sample Usage
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.
Launching Tasks
Best Effort and Known Endpoints
Task Inputs
Monitoring Tasks
Plugin Development
SmartExecutor plugins may have arbitrary size and dependencies but must include the following components:
Tasks
Note: Tasks are instantiated by the Executor and thus must have have a zero-argument constructor.
Contexts
Plugin Profiles
Development Environment and Testing
This [Eclipse project] may be used to kick-off plugin development and testing.
